Skip to content

Adjust mapping to DataCite for better machine-actionability #75

@rebeccaringuette

Description

@rebeccaringuette

I would like to see the mapping to DataCite be adjusted for increase machine-actionability.

Mapping to Subject
Specifically any term in PIDINST that could be pulled from a controlled ontology or similar should be mapped to "Subject" in DataCite so the discoverability using that term in the ontology can be preserved in a wider context.

For example, if InstrumentType were mapped into "Subject" instead of "Description", then a landing page for the instrument based on DataCite metadata could turn the term chosen for InstrumentType into a link for the term in the ontology. The landing page for that term could then be used to show the variety of instruments of the selected instrument type. This could be done identically for terms sourced from other ontologies. In search mechanisms, we can use this interlinking behind the scenes to have smarter searches.

The only other existing field this would apply to would be MeasuredVariable in cases where the term chosen comes from a controlled ontology, although others currently being discussed would likely fall into this category (e.g., ExperimentalTechnique).

Funding
It would also be useful to include funding information in PIDINST. Just using the standard structure in DataCite seems fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions