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.
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.