-
Notifications
You must be signed in to change notification settings - Fork 482
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
harmonize formats for metadata schema and dataset creation #4451
Comments
I keep thinking that if we tweak our tsv files a bit they'll look nice on GitHub but isaacs/github#848 has convinced me that it won't be easy to make them "beautiful and searchable": |
#3168 is related in the sense that perhaps we should document our crazy TSV format before we switch to JSON or YAML or XML or whatever. |
Just adding that #5960 is related to some of the points in this issue. |
Related:
|
I have a question about metadata customization. We have created a new metadata block for our Dataverse installation at the State Archives, but while we can rely on it appearing in the JSON metadata output for now, we would like to see it included in the DDI output (and it would follow the standard by translating into DDI 2.5 approved fields). pameyer wrote:
I believe this means that customizing metadata output is not yet possible but it is under consideration. Is that correct? |
@BPeuch fields in custom metadata blocks can be exported in Dataverse's native JSON format but are not automatically exported in any other format (such as DDI). If you would like to see some new fields appear in DDI output you should open an issue about this. 😄 |
Okay, I will. Thanks @pdurbin. So good to have you back aboard! |
Just reading metadata related issues - fwiw: the OAI-ORE format automatically includes all the metadata in added metadata blocks, and associates them with whatever community vocab URL was specified in the block. |
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'. If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment. |
User stories:
A first step towards addressing this could be replacing the TSV files used for metadatablocks / DatasetFieldTypes with a file format supporting hierarchical structures (JSON, YAML, XML), and updating the APIs in Dataverse reading these (with no additional information provided). This format should be something that either can be, or can be easily transformed into a form to, validate dataset creation/edit API input files.
The text was updated successfully, but these errors were encountered: