Up for debate: We are not currently indicating where the DOI/DMPP came from on the DataCite record. Should we use CDL, DMPHub, or? We need to begin passing this infor to DataCite (via EZID) as:
<contributor contributorType="HostingInstitution">
<contributorName nameType="Organizational">California Digital Library</contributorName>
<nameIdentifier nameIdentifierScheme="ROR" schemeURI="https://ror.org">https://ror.org/123abc45y</nameIdentifier>
</contributor>
Extend the data model to allow for fundings to have multiple funded_affiliations. These represent the organizations that have an administrative interest in the DMP that may or may not relate to the creator/contributor affiliations (especially over time since people change jobs).
Begin passing any fundedOrganization through to DataCite (via EZID) as:
<contributor contributorType="Producer">
<contributorName nameType="Organizational">University of Nowhere</contributorName>
<nameIdentifier nameIdentifierScheme="ROR" schemeURI="https://ror.org">https://ror.org/123abc45y</nameIdentifier>
</contributor>
A funded_affiliation can come from the NSF awards API scanner or from the API as:
Up for debate: We are not currently indicating where the DOI/DMPP came from on the DataCite record. Should we use CDL, DMPHub, or? We need to begin passing this infor to DataCite (via EZID) as:
Extend the data model to allow for
fundings
to have multiplefunded_affiliations
. These represent the organizations that have an administrative interest in the DMP that may or may not relate to the creator/contributor affiliations (especially over time since people change jobs).Begin passing any fundedOrganization through to DataCite (via EZID) as:
A
funded_affiliation
can come from the NSF awards API scanner or from the API as: