Skip to content
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

[infrastructure] Link Zenodo and DRYAD records #21

Open
4 tasks
gtsueng opened this issue Jan 23, 2025 · 1 comment
Open
4 tasks

[infrastructure] Link Zenodo and DRYAD records #21

gtsueng opened this issue Jan 23, 2025 · 1 comment
Assignees

Comments

@gtsueng
Copy link

gtsueng commented Jan 23, 2025

A request was received via email:

We spoke a few weeks ago on a call with GREI repositories. Since then, a colleague notice that our data was appearing in the portal, which is great! However, the data they originally found was the portal’s description for the Zenodo mirror of the Dryad dataset, and not the original Dryad dataset. Is it possible to merge or link the pages, since they are identified by the same DOI? (I note that one includes the “doi:” prefix, so the portal might not have recognized them as the same) Could this be done for all of the datasets that are mirrored between Dryad and Zenodo?

As Zenodo and DRYAD have different record-level identifiers, it will be tricky to merge the two. Instead, we will automatically link the two records within the DDE using the sameAs property. This can potentially be done via logic post-build

To do:

  • Update DRYAD and corresponding Zenodo metadata records to have sameAs values that point to one another
  • Display the sameAs value prominently on the front end only if the record points to another record within the Discovery Portal
  • Update DRYAD record and append corresponding Zenodo includedInDataCatalog metadata
  • Delete or Hide corresponding (duplicative) Zenodo record (from display/counts)

Related WBS task

https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/14

@gtsueng
Copy link
Author

gtsueng commented Feb 18, 2025

@DylanWelzel the decision on how to handle the DRYAD/Zenodo duplicates is to copy/append the includedInDataCatalog value from the Zenodo record to the DRYAD record and then to delete (or hide) the duplicative Zenodo record from search results/counts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants