Skip to content

idea: Allowing URI's or Curie format ids accompanying metadata fields #768

@Woolly-at-EBI

Description

@Woolly-at-EBI

Why?

To increase interoperability please could URI's or Curie format ids be allowed to accompany metadata fields?
I am mainly thinking of the likes of MIxS ids, but that would also include GeneEpiO, DwC etc.
Ideally multiple would be allowed, e.g. the same field(with slightly different names) is used in several vocabularies for example DwC and MIxS

In the short term, it would make it faster to update ENA's GSC checklist terms to the latest version of GSC, as there would be not matching step needed.


Dependencies

The JSON-LD would need time to have an extra slot added.
The checklist editor would need to allow an id alongside
May want to have a backend way of doing the initial upload of URI/Curie ids for all the terms. IMHO this is not a version of terms or checklists.
That URI/Curie ids are exported in the API generated JSON files.


Other Notes

Many terms will not have a URI or Curie id.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions