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

Support MARC-XML for Export and Harvest #2721

Closed
posixeleni opened this issue Nov 4, 2015 · 7 comments
Closed

Support MARC-XML for Export and Harvest #2721

posixeleni opened this issue Nov 4, 2015 · 7 comments
Labels
Feature: Harvesting Feature: Metadata Type: Feature a feature request User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh

Comments

@posixeleni
Copy link
Contributor

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

@borsna
Copy link

borsna commented Nov 10, 2015

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:
https://github.com/MetadataTransform/ddi-xslt/tree/master/ddi-marcxml

@posixeleni
Copy link
Contributor Author

@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.

@mercecrosas
Copy link
Member

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 ...

@mercecrosas mercecrosas modified the milestone: In Review Nov 30, 2015
@scolapasta scolapasta modified the milestone: Not Assigned to a Release Jan 28, 2016
@posixeleni
Copy link
Contributor Author

Scholars Portal has mapped DDI to MARC and have shared with us their documentation
marc.zip
: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/dataverse-community/iwYEwAJRmtQ/2KIaADLNAAAJ

@poikilotherm
Copy link
Contributor

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.

@cmbz
Copy link

cmbz commented Aug 26, 2024

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.

@cmbz cmbz closed this as not planned Won't fix, can't repro, duplicate, stale Aug 26, 2024
@cmbz
Copy link

cmbz commented Aug 26, 2024

2024/08/26: Additional note, there is a plan underway to investigate this functionality: IQSS/dataverse-pm#309

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Harvesting Feature: Metadata Type: Feature a feature request User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh
Projects
None yet
Development

No branches or pull requests

8 participants