Closed karlcz closed 2 years ago
This is deployed in app-dev's registry and the schema change plus experimental CLI is in the resource_markdown_simple
branch.
This branch uses a simple approach where an extra resource_markdown
field is added to the registry's CV tables and the CLI allows an admin to upload content to populate that field.
I think we can call this QA'd as @abradyIGS successfully used the tool to register a few resources in production.
Allow storage of "authoritative" resource information in registry, alongside existing persistent tracking of all vocabularies.
The markdown fields will have lots of embedded newlines, so the choice of file format for the CLI should consider what serializations are easy for the admin/curator users to work with...
UX concerns
(copied from another issue which was closed as a duplicate)
We need to consider the following: