Hi Melanie,
thank you for your response. Any decision „page“ vs. „pages“ suits our needs. All we need was a clarification on that topic. „pages“ has the charm that we do not need to change anything ;-)
kind regards
Thomas
--
Thomas Scheffler
Friedrich-Schiller-Universität Jena
Thüringer Universitäts- und Landesbibliothek
Bibliotheksplatz 2
07743 Jena
Phone: ++49 3641 940027
FAX: ++49 3641 940022
Am 12.11.2016 um 00:27 schrieb Melanie Wacker <[log in to unmask]<mailto:[log in to unmask]>>:
Hi Thomas,
sorry for the late response. Your question brought up a few issues that we discussed at the MODS Editorial Committee. @unit appears both under <physicalDescription><extent> (where it is defined as a string) and under <part><extent><start> and <end> as well as <total>. Again, under <start> and <end> it is simply defined to be strings. Under the subelement <total> however, it is defined as xs:positiveInteger with the intention of making it machine processible. So in this case, we need to make sure that the value of @unit is understood.
Therefore we are recommending to normalize the name of the unit to the spelled out plural form, because that would semantically make the most sense for values recorded in part/extent@unit=""/total.
The XSLT would be updated accordingly to produce an output that would (for example) look like this:
<mods:part>
<mods:extent unit="pages">
<mods:start>12</mods:start>
<mods:end>24</mods:end>
<mods:total>12</mods:total>
</mods:extent>
</mods:part>
In this example only <total> will be machine processible, that is the machine will know that there are 12 pages, but it won't understand the range.
The documentation will also be updated to make sure all examples will match the output.
Would that address your issue?
Best regards
Melanie Wacker
on behalf of the MODS Editorial Committee<https://www.loc.gov/standards/mods/editorial-committee.html>
Melanie Wacker
Metadata Coordinator
Original and Special Materials Cataloging
Columbia University Libraries
New York, N.Y.
(212) 854 9676
On Fri, Nov 4, 2016 at 2:23 AM, Thomas Scheffler <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi,
we are developing a MODS institutional repository (called MIR) that is used in several instances now in Germany. Recently we ran into an import issue.
https://www.loc.gov/standards/mods/v3/MARC21slim2MODS3-6.xsl
produces this output inside <part>:
<extent unit="page">
<start>3</start>
</extent>
while the user guide (https://www.loc.gov/standards/mods/userguide/part.html) on the other hand suggests
<extent unit="pages">
<start>3</start>
</extent>
You see there is a difference between „page“ and „pages“. During development we try to stay close to the documentation and the supplied examples in case of uncertainty. Others data provider seem to stick with your XSL files when exporting to MODS. It would be nice to get this unit type clarified somehow to improve interoperability.
kind regards,
Thomas Scheffler
--
Thomas Scheffler
Friedrich-Schiller-Universität Jena
Thüringer Universitäts- und Landesbibliothek
Bibliotheksplatz 2
07743 Jena
Phone: ++49 3641 940027<tel:%2B%2B49%203641%20940027>
FAX: ++49 3641 940022<tel:%2B%2B49%203641%20940022>
