<[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];
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.
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.