kg-registry-curation

To update YAML front matter for knowledge-graph registry resources, you must target exactly one stub file under resource/, expand the incomplete metadata using minimal authoritative evidence, and ensure the edits comply with the LinkML schema constraints before committing.

The best way to validate metadata curation changes is to run the prettify and validate commands on the edited resource page. This validation-first workflow catches provenance and formatting issues before you commit the updated YAML front matter and markdown body.

No, KG-Registry curation strictly forbids modifying generated registry/ outputs. You must only update the source markdown file and its YAML front matter located under the resource/ directory to maintain proper provenance and automated generation workflows.

When schema validation blockers prevent confident KG-Registry resource curation, you should record the specific problem in reports/curation_problems.tsv rather than inventing metadata. This ensures traceable curation blockers are documented for future review.

Yes, you can use markdown editing to expand stub knowledge-graph registry pages under resource/. You update the YAML front matter and body text while preserving required LinkML schema fields like at least one products entry, then run prettify and validate commands.

Your KG-Registry metadata curation may fail schema validation if required LinkML schema fields are missing, such as lacking at least one products entry, or if you inadvertently modified generated registry/ outputs instead of restricting edits to the resource/ directory.