As @dehays notes in #343, we don't have a curation process / UI whereby folks such as @pvangay, who are in contact with study PIs, can add/update metadata without being required to update a source database such as GOLD. Curation events should be possible, and recorded as part of the provenance of metadata, because updating primary source databases is sometimes intractable.
Several metadata errors have been tagged as issues, and developing a workable curation process for use ASAP (this month) has been requested by @kfagnan et al.
I was recently introduced to Corda, which is a system with a built-in web UI for managing collections of JSON-Schema-conformant documents, and for editing (based on the schema) and saving versions of documents.
I don't think the Cordra UI is suitable for metadata submission (#332), but I do think it could be a good fit for metadata curation by NMDC staff, where the curation events recorded by Cordra could feed into the broader NMDC ETL process.
As @dehays notes in #343, we don't have a curation process / UI whereby folks such as @pvangay, who are in contact with study PIs, can add/update metadata without being required to update a source database such as GOLD. Curation events should be possible, and recorded as part of the provenance of metadata, because updating primary source databases is sometimes intractable.
Several metadata errors have been tagged as issues, and developing a workable curation process for use ASAP (this month) has been requested by @kfagnan et al.
I was recently introduced to Corda, which is a system with a built-in web UI for managing collections of JSON-Schema-conformant documents, and for editing (based on the schema) and saving versions of documents.
I don't think the Cordra UI is suitable for metadata submission (#332), but I do think it could be a good fit for metadata curation by NMDC staff, where the curation events recorded by Cordra could feed into the broader NMDC ETL process.