http://permalink.gmane.org/gmane.comp.text.mods hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.text.mods/1386 <pre>Apologies for cross-posting -------------------------------- 1st Workshop on "Archives in the digital age: standards, policies and tools" (1st Call for Papers) Part of the IC-ININFO 2013 - 3rd International Conference on Integrated Information, 5-9 September 2013, Prague, Czech Republic Submission deadline: June 30, 2013 Proceedings will be published in Elsevier Procedia Social and Behavioral Sciences&lt;http://www.journals.elsevier.com/procedia-social-and-behavioral-sciences/&gt; *AIM AND SCOPE*** The description and dissemination of the archival collections has changed over the last twenty years, mostly due to the standardization of the archival description. The use of the archival standards and metadata schemas, such as ISAD(G), ISAAR(CPF), ISDF, EAD, EAC-CPF, METS, PREMIS etc., has expanded to many archival services worldwide. Currently, we find ourselves in a turning point where new versions of these tools have been created and new technologies are being used in the archives world, such as Linked Open </pre> Lina Bountouri 2013-05-23T08:25:45 http://permalink.gmane.org/gmane.comp.text.mods/1385 <pre>Hi Caitlin Thank you for your comments. The latest MODS 3.4 to MARCXML XSLTs (in XSLT 1.0 and 2.0) were last updated in May of 2012. Transforming from MARCXML &gt; MODS 3.4 &gt; MARCXML will be somewhat lossy in many if not all cases, even if all the XSLTs involved are perfectly up-to-date--that's just the nature of going from MARC&gt;MODS&gt;MARC in general (if that's what you mean by round-tripping). We try to keep all our XSLTs as up-to-date as possible given our resources. If you wouldn't mind sending me your issues with the MODS 3.4 to MARCXML conversion along with info re: XSLT version(s) you are using, directly to me, that would be helpful. We will try to address any issues as soon as possible. Thank you, Tracy Tracy Meehleib Network Development and MARC Standards Office Library of Congress 101 Independence Ave SE Washington, DC 20540-4402 +1 202 707 0121 (voice) +1 202 707 0115 (fax) tmee-+hwoy1Po9Oc&lt; at &gt;public.gmane.org&lt;mailto:tmee-+hwoy1Po9Oc&lt; at &gt;public.gmane.org&gt; From: Metadata Object Description Schema List [ma</pre> Meehleib, Tracy 2013-05-21T15:14:12 http://permalink.gmane.org/gmane.comp.text.mods/1384 <pre>Hello MODS folks, We are adapting several of the MODS transformation stylesheets for use in a new Islandora instance in Florida, namely DC-to-MODS / MODS-to-DC and MARCXML-to-MODS / MODS-to-MARCXML (v 3.4). For the most part things are going well, but I have a question about the MARCXML transformations. The MARCXML to MODS 3.4 stylesheet has very recently been updated and looks great. We are having problems, however, with the MODS to MARCXML stylesheet, which hasn't been updated to reflect the new changes (not updated at all in about a year, it looks like). We have little expectations for a perfect roundtrip, but we're still trying our best. So, two questions: one, will the MODS to MARCXML stylesheet be updated anytime soon? And two, does anyone have stylesheets they'd be willing to share that do a decent job of round-tripping? While we can update the stylesheets here, it would be nice to use work that's already done (or wait for work in process). (Conversely, we are happy to share our stylesheets t</pre> Caitlin Nelson 2013-05-17T20:05:06 http://permalink.gmane.org/gmane.comp.text.mods/1383 <pre>On Fri, May 17, 2013 at 1:47 PM, Jennifer Eustis &lt; Jennifer.Eustis-kwbsJ4lr4Heyum0STUha2w&lt; at &gt;public.gmane.org&gt; wrote: Perhaps this: http://www.loc.gov/standards/mods/modsrdf/xsl-files/modsrdf.xsl Tom </pre> Tom Morris 2013-05-17T18:40:03 http://permalink.gmane.org/gmane.comp.text.mods/1382 <pre>Hello collective MODS wisdom, I just began reading and working through the MODS RDF Ontology primer. I was curious to know if anyone was using MODS RDF expressed in xml. Also, would anyone know where the stylesheet to transform a MODS XML to MODS RDF with xml serialization is? The link provided (http://www.loc.gov/mods/modsrdf/modsrdf.xsl ) didn't work. Thanks, Jennifer </pre> Jennifer Eustis 2013-05-17T17:47:25 http://permalink.gmane.org/gmane.comp.text.mods/1381 <pre>Hello! In the modsrdf.xsl XSLT file, I noticed that the variable declaration xsl:variable name="resourceTypeClass" line 1829 (or nearby) probably could be removed for clarity. Instead, two lines further down, one could replace xsl:value-of select="concat($resourceTypeURI,$resourceTypeClass)" with the content of the declaration of $resourceTypeParts because the for-each used to create xsl:variable name="resourceTypeParts" on lines 1824 to 1828 populates the $resourceTypeParts variable with an already concatenated string (not with a sequence). Furthermore, (at least) one of the vertical bars in the RegEx on line 1825 could be remove. I do not know either in which cases we need any vertical bar. In other words, removing the resourceTypeClass and resourceTypeParts variable declarations, we could write the rdf:type element similarly to: xsl:element name="rdf:type" xsl:attribute name="rdf:resource" xsl:value-of select="$resourceTypeURI" / xsl:for-each select="tokenize(.,'[\s|,\-]')" xsl:value-of</pre> Saašha Metsärantala 2013-05-13T18:23:24 http://permalink.gmane.org/gmane.comp.text.mods/1380 <pre> RFC 5646 http://tools.ietf.org/html/rfc5646 supercedes RFC 4646 as reflected in both http://www.loc.gov/standards/mods/changes-3-5.html and the draft 3.5 schema. (The email announcing the draft may have had a typo.) Ray </pre> Ray Denenberg 2013-05-13T14:07:24 http://permalink.gmane.org/gmane.comp.text.mods/1379 <pre>Hello! Thanks for this highly appreciated information! Thanks for this link. There, one can read that "RFC5646 has superceded RFC4646" The e-mail refers to rfc5656 and RFC5656, though. Regards! Saašha, </pre> Saašha Metsärantala 2013-05-09T23:19:55 http://permalink.gmane.org/gmane.comp.text.mods/1378 <pre>The MODS Editorial Committee would like to announce the availability of a draft schema for MODS 3.5. Version 3.5 will be backwards compatible to 3.4 and therefore only includes changes that do not result in invalidating existing MODS records. Changes listed below include the change, its purpose, examples, and the date approved by the MODS Editorial Committee (this information is also available at: http://www.loc.gov/standards/mods/changes-3-5.html The draft schema is at: http://www.loc.gov/standards/mods/v3/mods-3-5-DRAFT.xsd Please send comments by June 7, 2013, after which we will finalize version 3.5. Changes in this version: 1. Add attribute &lt; at &gt;unit in mods:extent (Approved 2012-03-12) This change makes the extent element more granular by separating units from extent. Example: &lt;physicalDescription&gt; &lt;extent unit=”pages”&gt;12&lt;/extent&gt; &lt;/physicalDescription&gt; 2. Add rfc5656 to languageAuthorityAttributeDefinition (Approved 2012-03-12) Enumerated values reflect earlier stand</pre> Guenther, Rebecca 2013-05-09T19:18:12 http://permalink.gmane.org/gmane.comp.text.mods/1377 <pre>XLink may be used with &lt;note&gt;. Would that work for you? --Ray </pre> Ray Denenberg 2013-05-03T16:20:03 http://permalink.gmane.org/gmane.comp.text.mods/1376 <pre>Thank you very much for your help. Gerrit </pre> Kuehle, Gerrit 2013-05-03T14:34:59 http://permalink.gmane.org/gmane.comp.text.mods/1375 <pre>Thank you, and sorry for this. On Fri, May 3, 2013 at 3:11 PM, Dan Scott &lt;denials-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: </pre> Angela Di Iorio 2013-05-03T13:47:49 http://permalink.gmane.org/gmane.comp.text.mods/1374 <pre>Hi Angela: On Fri, May 3, 2013 at 5:55 AM, Angela Di Iorio &lt;angeladiiorio-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;wrote: Is this just a typo in your MODS documents? "authorithyURI" vs. "authorityURI" (extra 'h') </pre> Dan Scott 2013-05-03T13:11:44 http://permalink.gmane.org/gmane.comp.text.mods/1373 <pre>Dear MODS community, I gathered and labelled some warnings and considerations from our MODS implementation AUTHORITHY and AUTHORITYURI I got the following validation errors on my MODS documents. Theoretically, if I include an authority I should have always the opportunity to include the authority's URI information. Here are listed the elements where we got warnings: Warning: DOMDocument::schemaValidate() [domdocument.schemavalidate]: Element '{http://www.loc.gov/mods/v3}physicalLocation', attribute 'authorithyURI': The attribute 'authorithyURI' is not allowed. Warning: DOMDocument::schemaValidate() [domdocument.schemavalidate]: Element '{http://www.loc.gov/mods/v3}recordContentSource', attribute 'authorithyURI': The attribute 'authorithyURI' is not allowed. Warning: DOMDocument::schemaValidate() [domdocument.schemavalidate]: Element '{http://www.loc.gov/mods/v3}recordContentSource', attribute 'authorithyURI': The attribute 'authorithyURI' is not allowed. For example in mods:phisicalLocation and in mods</pre> Angela Di Iorio 2013-05-03T09:55:33 http://permalink.gmane.org/gmane.comp.text.mods/1372 <pre>A note is defined in MODS as just a string/unstructured text. Here is no authorityURI or valueURI as attributes in the schema. If you want to bring out the owner of a resource, use &lt;name&gt; with a role, e.g. &lt;name valueURI="http://d-nb.info/gnd/118677446" authorityURI="http://d-nb.info/gnd/"&gt; &lt;namePart&gt;Crusius, Martin&lt;/namePart&gt; &lt;role&gt;&lt;roleTerm type="code" authority="marcrelator"&gt;own&lt;/roleTerm&gt;&lt;/role&gt; &lt;/name&gt; (assuming it is ownership you are trying to convey; there are other roles relevant to provenance in the MARC relator list). We could also use authorityURI and valueURI (http://id.loc.gov/vocabulary/relators/own) under role in this example with the appropriate values from id.loc.gov/. Or could use type="text". Rebecca Rebecca S. Guenther Network Development &amp; MARC Standards Office Library of Congress Washington, DC 20540 rgue-+hwoy1Po9Oc&lt; at &gt;public.gmane.org -----Original Message----- From: Metadata Object Description Schema List [mailto:MODS-0lvw86wZMd/ipf4q2MuE5g&lt; at &gt;public.gmane.org] On Behalf Of G</pre> Guenther, Rebecca 2013-05-02T22:04:47 http://permalink.gmane.org/gmane.comp.text.mods/1371 <pre>Dear MODS mailing list subscribers, I have a problem how to add authority data IDs (especially valueURIs) in copy specific provenance information according to MODS SCHEMA. The following example produces a MODS SCHEMA validation report: &lt;mods:note type="ownership" displayLabel="Provenienz" valueURI="http://d-nb.info/gnd/118677446" authorityURI="http://d-nb.info/gnd/" authority="gnd"&gt;Crusius,Martin &lt;/mods:note&gt; MODS SCHEMA validation report: - Attribute 'authority' is not allowed to appear in element 'mods:note'. - Attribute 'authorityURI' is not allowed to appear in element 'mods:note'. - Attribute 'valueURI' is not allowed to appear in element 'mods:note'. I would love to know if there is already any solution in MODS format or whether there are plans to correctly provide authority data IDs in provenance information. Kind regards Gerrit Kuhle Metadata and Data Conversion Göttingen State and University Library 37070 G</pre> Gerrit Kuhle 2013-05-02T08:49:55 http://permalink.gmane.org/gmane.comp.text.mods/1370 <pre>(please excuse duplicate postings) THE UNIVERSITY OF ALABAMA LIBRARIES METADATA LIBRARIAN RESPONSIBILITIES: The University of Alabama Libraries is seeking a dynamic, highly motivated individual for the position of Metadata Librarian. Reporting to the Head of Cataloging &amp; Metadata Services (CMS) and working collaboratively with the 2 current metadata librarians and appropriate units in the Libraries, this position supports the discovery of and access to UA Libraries resources through metadata creation, analysis and enrichment. Specific duties include, but are not limited to: assisting in metadata production work for digital collections (70%); performing original and copy cataloging of non-book materials such as sound recordings and video recordings (15%); participating in the Alabama Digital Humanities Center projects and E-Science initiative (5%); evaluation of the effectiveness of catalog data and metadata for resource discovery (10%); and keeping abreast of current issues and trends in cata</pre> Mary Alexander 2013-04-24T14:09:16 http://permalink.gmane.org/gmane.comp.text.mods/1369 <pre>Hi Vicky, We are attempting to maintain (and keep in sync) two XSLT versions (XSLT 1.0 and XSLT 2.0) for the most current version of MODS, which is MODS 3.4, but we are intending to transition to XSLT 2.0 (only) with the release of MODS 3.5. I am glad that you found the XSLT 2.0 version more precise (i.e., improved)! Thank you for your interest. We welcome feedback on this decision. Best, Tracy Tracy Meehleib Network Development and MARC Standards Office Library of Congress 101 Independence Ave SE Washington, DC 20540-4402 +1 202 707 0121 (voice) +1 202 707 0115 (fax) tmee-+hwoy1Po9Oc&lt; at &gt;public.gmane.org -----Original Message----- From: Metadata Object Description Schema List [mailto:MODS-0lvw86wZMd/ipf4q2MuE5g&lt; at &gt;public.gmane.org] On Behalf Of Vicky Phillips Sent: Friday, April 12, 2013 9:11 AM To: MODS-0lvw86wZMd/ipf4q2MuE5g&lt; at &gt;public.gmane.org Subject: [MODS] XSLT 1.0 and 2.0 Hello, I notice that you are now releasing MODS 3.4 under XSLT 1.0 and 2.0. Although outputs are almost identical there are a few </pre> Meehleib, Tracy 2013-04-12T18:29:44 http://permalink.gmane.org/gmane.comp.text.mods/1368 <pre>Hello, I notice that you are now releasing MODS 3.4 under XSLT 1.0 and 2.0. Although outputs are almost identical there are a few differences, with 2.0 being more precise. Are you maintaining both versions or are you moving to maintaining just the XSLT 2.0 version? Many thanks, Vicky Digital Standards Manager National Library of Wales </pre> Vicky Phillips 2013-04-12T13:10:54 http://permalink.gmane.org/gmane.comp.text.mods/1367 <pre>Hello! I am glad to notice the renewed activity around MODS/RDF! I think it is important to consider these questions carefully. In this e-mail, I won't list my comments about the MODSRDF XSLT. Instead, I consider that a few things still need to be clarified when it comes to the question of hash vs. slash namespaces and possible redirections. The namespace related decisions we take today may have important consequences later on. I am aware of the advantages of slash namespaces, but if we want to avoid overloaded URIs and CN, we may need to use redirections. This is where a couple of questions arise. The number of new or modified HTTP header fields (whether formally standard or not) has been (very roughly) a couple per year during the last twenty years or so. If we want our data to be stored for decades and centuries, we may wish to try to avoid (or at least be aware of) possible tight dependencies on specific HTTP headers. If we choose to recommend the use of redirections, I consider that we s</pre> Saašha Metsärantala 2013-03-26T17:43:43 http://permalink.gmane.org/gmane.comp.text.mods/1366 <pre>Hi Ashley, Your suggestion of converting the $0 to authorityURI and valueURI as in your example is what I have done for an internal conversion in the British Library. &lt;name authorityURI="http://isni.org" valueURI="http://isni-url.oclc.nl/isni/1234567899999799"&gt; I'm afraid I"m out of the office with no access to my network files but I can forward you what I did on Monday when I'm back. Best wishes, Jan -----Original Message----- From: Metadata Object Description Schema List on behalf of Ashley Sanders Sent: Thu 21/03/2013 15:40 To: MODS-0lvw86wZMd/ipf4q2MuE5g&lt; at &gt;public.gmane.org Subject: [MODS] $0 in MODS Hello, I'm wondering how to represent $0 (zero) in MODS, e.g.: 100 1# $aTrollope, Anthony,$d1815-1882.$0(isni)1234567899999799 The LoC MARC to MODS3.4 XSLT seems to mostly ignore the $0, apart for the 648, whence it does the following (this is a very contrived example just created to see what the stylesheet would do with a $0): 648 #7 $a1800-1899$2fast$0(isni)1234567899999799 &lt;subjec</pre> Ashton, Jan 2013-03-21T19:24:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.text.mods