-
Notifications
You must be signed in to change notification settings - Fork 493
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
Support MARC-XML for Export and Harvest #2721
Comments
If you have DDI 3.1/3.2 in as an export you could use the XSLT:s in the project DDI-XSLT to produce MARC-XML: |
@borsna thanks for your help. Unfortunately we do not have DDI 3.1 or 3.2 at the moment. We are still using Codebook but we may be able to reuse some of the XSLT so we may be forking the ddi-marcxml repo. |
Yes, that's a good approach, which we've used in the past. But in general, for export and harvesting from various metadata standard, we need to export to the native JSON (which contains ALL metadata fields), and then map that JSON to all XML standards we want to support. The reason to do this is not to leave out or convert wrongly some fields, which can happen when you convert from one metadata standard to another to another ... |
Scholars Portal has mapped DDI to MARC and have shared with us their documentation |
These days the exporter would be doable using a plugin. https://github.com/gdcc/dataverse-exporters I am interested in an XML-RDF exporter as well, supporting exposing custom metadata, too. |
2024/08/26: Closing because there are alternate ways to address this functionality. @poikilotherm please reopen or create a new issue if you feel this is a must-have feature. |
2024/08/26: Additional note, there is a plan underway to investigate this functionality: IQSS/dataverse-pm#309 |
Use case from Harvard libraries and Harvard Business School to make MARC-XML metadata available for export or harvest at the dataset-level. This would be to make datasets in Dataverse searchable/discoverable in the Hollis Catalog and in OCLC Worldcat.
Need to consider this when planning out which metadata schemas we will support for an upcoming implementation phase of the Harvest feature since we have an active use case from the Harvard community. FRD: https://docs.google.com/document/d/1XZHpTyYUwyPN3FIfJhaSFg5_h-9C415mlE42Fuao38w/edit?usp=sharing
The text was updated successfully, but these errors were encountered: