Correct usage of scheming about ckanext-scheming HOT 4 CLOSED

@timgiles for splitting into sections you could look at customizing the templates that generate the form to add a section break where indicated in the schema. any values not used by scheming are passed along, so you can put almost anything you like in there.

If you'd like to contribute a change to ckanext-scheming for section headings (maybe "fields" that have a section_label and no field_name) I'd certainly consider merging it

from ckanext-scheming.

Thanks Ian. I did add it to the extension and we have added a few more
'visual' options. I will look to collect them together and put a merge
request in later this week.

On 23 August 2015 at 20:07, Ian Ward [email protected] wrote:

@timgiles https://github.com/timgiles for splitting into sections you
could look at customizing the templates that generate the form to add a
section break where indicated in the schema. any values not used by
scheming are passed along, so you can put almost anything you like in there.

If you'd like to contribute a change to ckanext-scheming for section
headings (maybe "fields" that have a section_label and no field_name) I'd
certainly consider merging it

—
Reply to this email directly or view it on GitHub
#36 (comment)
.

from ckanext-scheming.

The first thing I see is that you're using
ckanext.scheming:sluschemav014.json as a dataset schema name. That would mean you have to put your schema inside the scheming extension directory. You should use ckanext.mycustomextension:sluschemav014.json or a file path instead.

I also notice you're using a strange looking "dataset_type". The dataset_type field is used to build the URLs for that type of dataset, so stick to lowercase-and-underscores there. Did you read https://github.com/open-data/ckanext-scheming/#dataset_type ?

As for choosing dataset types you need to direct your users to /mycustomtype/new etc. for your custom type by overriding the ckan templates in your own extension.

from ckanext-scheming.

Thanks - after an upgrade to 2.3 and some more work, we have implemented our schema. Works great - although we need to add in a lot of the supplementary info like required etc...

I was wondering, with long schemas:

i) Is there a way to break them up in to sections? Is this planned? either on the dataset page or split into separate pages (I suspect this goes beyound the scope of scheming)

ii) Could this be done with dummy MD fields with a new display snippet?

ii) In a similar thought, do you have a suggestion how to present sectional titles/text in along the schema?

Thanks again for the good work

from ckanext-scheming.