-
Notifications
You must be signed in to change notification settings - Fork 494
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
Comments
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/: |
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. |
I think I overlooked @posixeleni's spreadsheet in my issue #2357. However, it is still relevant in light of @jonc1438's comment. |
@sekmiller - is this part of the export work? It's marked as part of 4.5 but I'm unclear on the status. Thanks! |
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. |
Thanks @sekmiller ! |
Tested and verified with individual issues opened as new tickets. Closing. |
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:
The text was updated successfully, but these errors were encountered: