You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The initial implementation doesn't take into account if a user provided a custom datapackage.json.
Depending on the feedback and actual use cases, we need to decide what behavior is optimal:
the Data Package endpoint is always autogenerated and custom datapackage.json should be accessed directly from uploaded files
custom datapackage.json replaces the autogenerated one
Another consideration is that the Data Package default endpoint is only capable to reference resources by URL because it's in not the same "virtual plain folder" (in-general, CKAN doesn't have a plain resource folder compared to Zenodo) -- it means the implementation needs to handle path rewriting.
The text was updated successfully, but these errors were encountered:
Overview
The initial implementation doesn't take into account if a user provided a custom
datapackage.json
.Depending on the feedback and actual use cases, we need to decide what behavior is optimal:
datapackage.json
should be accessed directly from uploaded filesdatapackage.json
replaces the autogenerated oneAnother consideration is that the Data Package default endpoint is only capable to reference resources by URL because it's in not the same "virtual plain folder" (in-general, CKAN doesn't have a plain resource folder compared to Zenodo) -- it means the implementation needs to handle path rewriting.
The text was updated successfully, but these errors were encountered: