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
It would be nice to have the POD identifier be a URL to the dataset in CKAN. This would need to be generated with a Wrapper function, as it's not stored in the package.
It should probably use the raw dataset ID from CKAN. Even if a custom URL or alias has been created for the dataset, CKAN still honors the URL with the raw ID.
The text was updated successfully, but these errors were encountered:
inghamn
added a commit
to City-of-Bloomington/ckanext-datajson
that referenced
this issue
Oct 14, 2016
It would be nice to have the POD identifier be a URL to the dataset in CKAN. This would need to be generated with a Wrapper function, as it's not stored in the package.
It should probably use the raw dataset ID from CKAN. Even if a custom URL or alias has been created for the dataset, CKAN still honors the URL with the raw ID.
The text was updated successfully, but these errors were encountered: