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

Export Descriptive Metadata From Dataset #907

Closed
posixeleni opened this issue Sep 8, 2014 · 11 comments
Closed

Export Descriptive Metadata From Dataset #907

posixeleni opened this issue Sep 8, 2014 · 11 comments
Assignees
Labels

Comments

@posixeleni
Copy link
Contributor

posixeleni commented Sep 8, 2014

Need to design an export metadata tool for datasets in Dataverse 4.0 which will allow an end-user the option to export the descriptive metadata of a Dataset into the following formats:

  1. Native JSON Metadata
  2. DDI 2.5 XML (not the full just the "study" metadata? For tabular metadata we may want to export this into a different file especially if dealing with files that are very large see Export File's Variable Metadata From Datasets With Tabular Data #908 )
  3. Data Cite 3.0 XML
  4. Dublin Core XML
    • Simple
    • DC-Terms
  5. VO Metadata XML
  6. ISA-Tab
@posixeleni
Copy link
Contributor Author

Here's an example of a data repository offering multiple metadata export options from Data Univ of East London http://data.uel.ac.uk/3/:
image

@scolapasta scolapasta modified the milestones: Beta 11 - Dataverse 4.0, Dataverse 4.0: Final, TEMP, Beta 12 - Dataverse 4.0 Jan 23, 2015
@scolapasta scolapasta modified the milestones: Beta 12 - Dataverse 4.0, In Review - Dataverse 4.0 Feb 6, 2015
@eaquigley eaquigley modified the milestones: Beta 13 - Dataverse 4.0, In Review - Dataverse 4.0 Feb 9, 2015
@eaquigley eaquigley assigned scolapasta and unassigned posixeleni Feb 9, 2015
@mercecrosas mercecrosas modified the milestones: 4.4, In Review Nov 30, 2015
@jonc1438
Copy link

jonc1438 commented Dec 2, 2015

I just wanted to remind everyone that a key function of the export is not only to share metadata but to store it in the file system in a preservation format.

Currently the version 4.2.1 we are testing only stores metadata in the database. For archives to use the Dataverse the metadata needs to be stored on disk as a preservable format like JSON or XML. That will allow it to be preserved with the digital objects in a preservation system.

@bencomp
Copy link
Contributor

bencomp commented Dec 2, 2015

I think I overlooked @posixeleni's spreadsheet in my issue #2357. However, it is still relevant in light of @jonc1438's comment.

@scolapasta scolapasta removed their assignment Jan 27, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@scolapasta scolapasta added this to the 4.4 milestone Feb 10, 2016
@djbrooke djbrooke added ready and removed ready labels Jul 26, 2016
@djbrooke
Copy link
Contributor

@sekmiller - is this part of the export work? It's marked as part of 4.5 but I'm unclear on the status. Thanks!

@sekmiller
Copy link
Contributor

Yes, This is part of the export work. As it stands now, all supported export formats (DDI, Dublin Core and json) will be saved to the file system at dataset publication time. We might need to run a script to catch everything that hasn't been exported to the file system at the time we deploy 4.5. I think Leonid was adding a timer job for this. (I know he added "lastExportTime" as a field for datasets.) I will check with him.

@djbrooke
Copy link
Contributor

Thanks @sekmiller !

@kcondon
Copy link
Contributor

kcondon commented Aug 19, 2016

Tested and verified with individual issues opened as new tickets. Closing.

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

No branches or pull requests

10 participants