Selecting Schemas for a New Dataset about ckanext-scheming

[wardi]

I'll need this soon so I'll see if there's a clean way to make listing the new types generic. possibly just a separate "new" button for each.

[wardi]

@fibonaki This isn't currenly handled by scheming but it would be great to add. The trick is to use the dataset new page for your type of dataset, so if your dataset_type is "maps" you would visit `http://mysite/maps/new'

[jordipiqueres]

Hi @wardi! Thanks for your response! :)

I am not familiarized with python and I think exists in CKAN a template that is called each time that a user visits http://mysite.org/dataset, and here is where I should to modify content and add each new dataset button (by the default there is only one - http://mysite.org/dataset/new):

1. "Add new dataset A" - http://mysite.org/datasetA/new
2. "Add new dataset B" - http://mysite.org/datasetB/new

I have seen that you have opened a new github's reference for handling multiple dataset schemas. But, could you please tell me as a brief notes by the moment which would be the python file / template of "http://mysite.org/dataset" in CKAN that I should to change for adding these buttons? That's only for testing it... If I'm not wrong I guess it shouldn't require much time.

Thanks.

[gsueur]

Hi,

Does the plugin still works that way ? When I try to add a dataset corresponding to my second schema (/camel_photos/new), I can only get 404.

Thanks

[edmondchuc]

Hi @gsueur the URL should be /camel-photos/new

[kolesarj]

I'll need this soon so I'll see if there's a clean way to make listing the new types generic. possibly just a separate "new" button for each.

Not sure the current state of this issue.
Seems a lot of folks put an extra page in front or a portal to handle navigation for creation for different schemas. This is especially so if you have a CMS or other product in front of CKAN to handle enterprise portal capabilities.

Also could depend how people deal with different schemas (we are shooting for show all datasets option but I have noticed some break down different areas for different schemas or use separate CKAN instances if the logic-per-schema is significantly different).

We followed the approach mentioned by @wardi, for now have implemented multiple buttons for the Add Dataset. For every dataset schema listed in the configuration file...adds buttons alognside the Add Dataset button.
Fits the bill for now - but we may revisit down the road.
Still in Dev - no polish for production ready yet.

[kolesarj]

Actually, someone has made another more recent post with a solution based on maps and redirects:

#155 (comment)

Would this fit better with respect to CKAN/ckanext-scheming direction / road map?