ckan / ckan/ckanext-validation
Schema store
- Dominant language
- Python
- Stars
- 30
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
In some cases, specially on large CKAN instances schemas may be reused when publishing different datasets across organizations, for instance spending data that must adhere to a predefined standard.
A simple interface could be provided to add new schemas (using the same methods as point 6), and store them with some basic metadata like a user friendly title.
Schemas would be validated to endure they have the correct syntax and stored in a dedicated table in the database.
On the resource form then users could choose from the existing schemas when creating the resource. The actual schema object would be stored on the resource, or a publicly accessible endpoint for the relevant schema (eg `/schemas/data/{id}`).
In the future this same interface could be extended to manage metadata schemas (when ckanext-scheming is integrated into core).
*Estimate: 3-6 days (needs proper spec)*
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.