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

DC converter and EDM documentation mismatch? #9

Closed
johnjung opened this issue Oct 3, 2019 · 0 comments
Closed

DC converter and EDM documentation mismatch? #9

johnjung opened this issue Oct 3, 2019 · 0 comments

Comments

@johnjung
Copy link
Owner

johnjung commented Oct 3, 2019

The spec includes the following:

<[NOID]/[path/to/providedCHO]>
For dc:coverage use MARCXML 651 fields with second indicator of 7 and subfield $2
with value “fast”. Eg:
651 7 |a Illinois |z Chicago |z Lower West Side. |2 fast
|0 http://id.worldcat.org/fast/01926123
Each subfield should generate a separate dc:coverage element.
dc:coverage [651 $a and $z subfields from MARCXML];

Right now, the DC metadata converter pulls coverage from any subfield in the 255.

In general, should all DC output for maps match the DC fields that are specified in this document? If so, I'll make a maps-specific subclass of the DC metadata converter.

@johnjung johnjung changed the title DC converter and EDM documentation mismatch DC converter and EDM documentation mismatch? Oct 3, 2019
@johnjung johnjung closed this as completed Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant