Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic CKAN Alias creation #9

Closed
Tracked by #5
jqnatividad opened this issue Apr 27, 2022 · 0 comments
Closed
Tracked by #5

Automatic CKAN Alias creation #9

jqnatividad opened this issue Apr 27, 2022 · 0 comments
Assignees
Labels
roadmap wip Work in Progress

Comments

@jqnatividad
Copy link
Contributor

jqnatividad commented Apr 27, 2022

When a resource is inserted into the Datastore, automatically create a CKAN alias (aka PostgreSQL view) so we have a human-readable name apart from the resource-id we can use in API calls, datastore-choices helper in scheming, etc.

To minimize namespace collisions - the alias should be - resource_name-package_name-owner_org.

However, PostgreSQL by default limits object names to be 63 characters long, so we need to create some biz rules in case of namespace collisions - perhaps, adding a sequence at the end, or flagging it during the datapusher+ job.

@jqnatividad jqnatividad self-assigned this Apr 27, 2022
@jqnatividad jqnatividad added the wip Work in Progress label Apr 27, 2022
@jqnatividad jqnatividad mentioned this issue May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap wip Work in Progress
Projects
None yet
Development

No branches or pull requests

1 participant