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

Users should be able to download DATS metadata from Export Metadata pulldown #3696

Open
jggautier opened this issue Mar 16, 2017 · 5 comments
Labels
Feature: Harvesting Feature: Metadata GREI 3 Search and Browse Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc. User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh Vote to Close: pdurbin

Comments

@jggautier
Copy link
Contributor

Users should be able to download DATS metadata from the Export Metadata pulldown in each dataset Metadata tab:

screenshot 2017-03-15 21 53 03

DATS specification and examples: https://github.com/biocaddie/WG3-MetadataSpecifications

@jggautier jggautier changed the title Users should be able to download DATs metadata from Export Metadata pulldown Users should be able to download DATS metadata from Export Metadata pulldown Mar 16, 2017
@pdurbin
Copy link
Member

pdurbin commented Jun 25, 2017

My comment at #3697 (comment) applies to this issue as well.

@jggautier jggautier added User Role: Depositor Creates datasets, uploads data, etc. User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh labels Jul 3, 2017
@pdurbin
Copy link
Member

pdurbin commented Oct 5, 2022

@jggautier fast forward five years and we have many more export formats:

Screen Shot 2022-10-04 at 10 01 38 PM

However, we still don't have DATS. Who wants DATS? Who or which installations are going to be excited if we implement this? I looked through issues and the mailing list and couldn't find any hits for DATS. Maybe you're right. Maybe we should code this up. I see "biocaddie" and "bio" make me think of this issue (so maybe we should work on it? I don't know):

In short, I feel like this issue could use some champions or it should be closed with "not right now, maybe later".

@jggautier
Copy link
Contributor Author

I wish I had added more information in this GitHub issue about why I opened this issue in the first place. Why Dataverse repositories should export metadata in the DATS standard.

Someone taking this issue up might investigate it more, answering questions such as will exporting DATS metadata improve discoverability and interoperability? Would it help with data migration? And when would it? Are there discovery systems and other repositories that are interested and are able now or plan to be able to import or export metadata in the DATS standard?

More generally I'm not sure about closing an issue only because no one's working on it now.

@jggautier
Copy link
Contributor Author

jggautier commented Feb 14, 2023

Reviewing articles about searching for biomedical data across repositories, I ran into a 2017 article about DataMed, "a prototype biomedical data search engine." Its goal is to help others more easily discover datasets in many data repositories and data aggregators. It's at https://datamed.org.

The team running the search engine hand picked several repositories and there's a form to let them know about other sources to consider indexing data from. One of the requirements for being indexed in that search engine is that repositories must make dataset metadata available in their DATS model.

Though this issue is about adding a DATS metadata export option to the Export Metadata pulldown, in Dataverse doing that would usually involve making that metadata export available in other ways, too, such as through API calls and over OAI-PMH.

So maybe this issue should be broadened to be about Dataverse exporting metadata in the DATS model in the various ways that Dataverse already does, and contacting the DataMed team to see if they're interested in indexing metadata from Dataverse repositories. Part of their process for inclusion involves an evaluation of user demand for the repository's holdings.

@cmbz cmbz added GREI 3 Search and Browse Feature: Harvesting labels Sep 9, 2024
@cmbz
Copy link

cmbz commented Sep 9, 2024

2024/09/09: Keeping, related to GREI harvesting and search/browse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Harvesting Feature: Metadata GREI 3 Search and Browse Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc. User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh Vote to Close: pdurbin
Projects
None yet
Development

No branches or pull requests

4 participants