Resource page - resource relationship is now mandatory?
nfee006 opened this issue · comments
@nfee006, can I move the json files for the scheming into the scheming plugin? I think I've got this straightened out, but it doesn't make sense to me that it spread over 2 repositories
@coleweusthem - go for it. Not quite sure why it was done that way in the first place.
@nfee006, pushed the change, you'll need to fix the scheming settings in your config file:
scheming.dataset_schemas = ckanext.scheming:ckan_dataset.json
ckanext.csa:info.json ckanext.csa:doc.json
scheming.presets = ckanext.scheming:presets.json
ckanext.fluent:presets.json
Didn't break anything on my side and seems to have fixed the relationship type/related record issue/division issue.
These fields are now popping up as required as well (below). I cross-referenced with our prod server and the ones I've highlighted are not required there. Would it be possible to make them optional please? I worry that it may cause some issues when we migrate the metadata. Thanks!
@nfee006, I think i've got those optional now. I think something must have changed that made them required if you didn't specify wether or not they should be.
@coleweusthem looks great on my side. No other issues to flag for this.
Is this bug fixed? I guess so by reading the comments.
@emilinecsa Correct, this is fixed.