-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Guidelines for Defining Data Package Replication #88
Comments
What if we're just replicating metadata? Previously we've tried this when attempting to replicate metadata from EDI to Arctic Data Center. Option 1: Add a snippet of XML into additionalMetadata: <additionalMetadata>
<metadata>
<d1v1:replicationPolicy xmlns:d1v1="http://ns.dataone.org/service/types/v1" numberReplicas="1"
replicationAllowed="true">
<preferredMemberNode>urn:node:ARCTIC</preferredMemberNode>
</d1v1:replicationPolicy>
</metadata>
</additionalMetadata> Option 2: manual process.
Option 1 hasn't worked for a few years. And a manual process like option 2 isn't ideal. Should we just replicate the whole dataset? Or is there a way to just replicate metadata with semantic annotation? |
Thanks for your questions, @twhiteaker . Regarding replicating metadata, I don’t believe this is currently possible because there’s no "subject" element in the EML record that could be used in semantic annotation to references itself. However, it’s possible that I may have missed something. The second challenge is identifying a suitable "object" to reference. One option is using the URL of the metadata record, but this is less than ideal since URLs can change. Ideally, there would be a DOI for the metadata record that could be referenced, which would provide a more stable identifier. This issue is similar to describing entity-level replication within the EDI repository. Since we don’t assign DOIs to individual data entities, the best we can do is reference the data entity’s URL (as seen here). Even if we overcame the above issues, we’d still face a "chicken and egg" problem: the user would need to know the DOI of the data package before it’s published in order to assign it in the metadata using the As for whether there’s a semantic annotation mechanism to facilitate data replication—no, not at this time. The methods you mentioned are the only ones we’re aware of. |
Hi everyone,
We're excited to announce the release of new guidelines for defining data package replication between EDI and other repositories. These guidelines offer solutions for describing replication at both the data package and data entity levels.
To learn more about the release and access the guidelines, please check out the following resources:
These guidelines may be good additions to the data packaging best practices.
Thanks!
The text was updated successfully, but these errors were encountered: