Closed acka47 closed 4 years ago
This is basically the same as we already do with notation 99. The relevant part of the morph must be: https://github.com/hbz/lobid-resources/blob/00416a031d0b166cae1054a8c2d0d3f52f463c0e/src/main/resources/morph-hbz01-to-lobid.xml#L7326-L7336
@dr0i, bitte übernehmen Sie.
As this is deployed on staging, I made a functional review. Everything looks as requested. Thanks. +1
Deployed to production, closing.
Reopening: To Do: Write email to NWBib editors.
Mail is out. Closing
Most NWBib records with the spatial notations 35, 36, 37 in
700n.a
also have an entry in700n.b
. Examples:HT017536715 (source, JSON):
HT020082521 (source, JSON):
HT017206874 (source, JSON):
This information in 700n is currently transformed into two objects in the
spatial
array (in the JSON-LD). For example HT017536715:To Do:
The spatial object that is generated from
700n.a
(the 1st one in the above example) has to be removed from the data, for the notations 35, 36, 37.:exclamation: Note
There are also some entries with only information in
700n.a.
. Those records have to retain thespatial
object generated from this subfield. Example BT000071273 (source, JSON):