The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri
Identifieur interne : 000454 ( Istex/Corpus ); précédent : 000453; suivant : 000455The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri
Auteurs : C. Clissman ; R. Murray ; E. Davidson ; J. Hands ; O. Sijtsma ; A. Noordzij ; R. Moulton ; S. Shanawa ; J. Darzentas ; I. PettmanSource :
- New Library World [ 0307-4803 ] ; 1998-02-01.
Abstract
Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas record syntax conversion which covers UNIMARC, SGML and Dublin Core result set deduplication, covering International Standard Book Number ISBN, International Standard Serial Number ISSN, the Universal Standard Bibliographic Code USBC, Serial Item and Contribution Identifier SICI, Digital Object Identifiers DOI and Uniform Resource Names URN and multilingual thesauri.
Url:
DOI: 10.1108/03074809810196707
Links to Exploration step
ISTEX:A23C95B9872708FF9FE79BB0C6F36126D60C8E7FLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title><author wicri:is="90%"><name sortKey="Clissman, C" sort="Clissman, C" uniqKey="Clissman C" first="C." last="Clissman">C. Clissman</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Murray, R" sort="Murray, R" uniqKey="Murray R" first="R." last="Murray">R. Murray</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Davidson, E" sort="Davidson, E" uniqKey="Davidson E" first="E." last="Davidson">E. Davidson</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Hands, J" sort="Hands, J" uniqKey="Hands J" first="J." last="Hands">J. Hands</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Sijtsma, O" sort="Sijtsma, O" uniqKey="Sijtsma O" first="O." last="Sijtsma">O. Sijtsma</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Noordzij, A" sort="Noordzij, A" uniqKey="Noordzij A" first="A." last="Noordzij">A. Noordzij</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Moulton, R" sort="Moulton, R" uniqKey="Moulton R" first="R." last="Moulton">R. Moulton</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Shanawa, S" sort="Shanawa, S" uniqKey="Shanawa S" first="S." last="Shanawa">S. Shanawa</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Darzentas, J" sort="Darzentas, J" uniqKey="Darzentas J" first="J." last="Darzentas">J. Darzentas</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Pettman, I" sort="Pettman, I" uniqKey="Pettman I" first="I." last="Pettman">I. Pettman</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:A23C95B9872708FF9FE79BB0C6F36126D60C8E7F</idno><date when="1998" year="1998">1998</date><idno type="doi">10.1108/03074809810196707</idno><idno type="url">https://api.istex.fr/document/A23C95B9872708FF9FE79BB0C6F36126D60C8E7F/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">000454</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title><author wicri:is="90%"><name sortKey="Clissman, C" sort="Clissman, C" uniqKey="Clissman C" first="C." last="Clissman">C. Clissman</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Murray, R" sort="Murray, R" uniqKey="Murray R" first="R." last="Murray">R. Murray</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Davidson, E" sort="Davidson, E" uniqKey="Davidson E" first="E." last="Davidson">E. Davidson</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Hands, J" sort="Hands, J" uniqKey="Hands J" first="J." last="Hands">J. Hands</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Sijtsma, O" sort="Sijtsma, O" uniqKey="Sijtsma O" first="O." last="Sijtsma">O. Sijtsma</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Noordzij, A" sort="Noordzij, A" uniqKey="Noordzij A" first="A." last="Noordzij">A. Noordzij</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Moulton, R" sort="Moulton, R" uniqKey="Moulton R" first="R." last="Moulton">R. Moulton</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Shanawa, S" sort="Shanawa, S" uniqKey="Shanawa S" first="S." last="Shanawa">S. Shanawa</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Darzentas, J" sort="Darzentas, J" uniqKey="Darzentas J" first="J." last="Darzentas">J. Darzentas</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author><author wicri:is="90%"><name sortKey="Pettman, I" sort="Pettman, I" uniqKey="Pettman I" first="I." last="Pettman">I. Pettman</name><affiliation><mods:affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">New Library World</title><idno type="ISSN">0307-4803</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="1998-02-01">1998-02-01</date><biblScope unit="volume">99</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="10">10</biblScope><biblScope unit="page" to="19">19</biblScope></imprint><idno type="ISSN">0307-4803</idno></series><idno type="istex">A23C95B9872708FF9FE79BB0C6F36126D60C8E7F</idno><idno type="DOI">10.1108/03074809810196707</idno><idno type="filenameID">0720990102</idno><idno type="original-pdf">0720990102.pdf</idno><idno type="href">03074809810196707.pdf</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0307-4803</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas record syntax conversion which covers UNIMARC, SGML and Dublin Core result set deduplication, covering International Standard Book Number ISBN, International Standard Serial Number ISSN, the Universal Standard Bibliographic Code USBC, Serial Item and Contribution Identifier SICI, Digital Object Identifiers DOI and Uniform Resource Names URN and multilingual thesauri.</div></front></TEI><istex><corpusName>emerald</corpusName><author><json:item><name>C. Clissman</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>R. Murray</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>E. Davidson</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>J. Hands</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>O. Sijtsma</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>A. Noordzij</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>R. Moulton</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>S. Shanawa</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>J. Darzentas</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item><json:item><name>I. Pettman</name><affiliations><json:string>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</json:string></affiliations></json:item></author><subject><json:item><lang><json:string>eng</json:string></lang><value>Cataloguing</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>International standards</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Library materials</value></json:item></subject><language><json:string>eng</json:string></language><originalGenre><json:string>case-report</json:string></originalGenre><abstract>Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas record syntax conversion which covers UNIMARC, SGML and Dublin Core result set deduplication, covering International Standard Book Number ISBN, International Standard Serial Number ISSN, the Universal Standard Bibliographic Code USBC, Serial Item and Contribution Identifier SICI, Digital Object Identifiers DOI and Uniform Resource Names URN and multilingual thesauri.</abstract><qualityIndicators><score>6.032</score><pdfVersion>1.1</pdfVersion><pdfPageSize>595 x 842 pts (A4)</pdfPageSize><refBibsNative>true</refBibsNative><keywordCount>3</keywordCount><abstractCharCount>647</abstractCharCount><pdfWordCount>5427</pdfWordCount><pdfCharCount>35024</pdfCharCount><pdfPageCount>10</pdfPageCount><abstractWordCount>86</abstractWordCount></qualityIndicators><title>The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title><genre><json:string>case-report</json:string></genre><host><volume>99</volume><publisherId><json:string>nlw</json:string></publisherId><pages><last>19</last><first>10</first></pages><issn><json:string>0307-4803</json:string></issn><issue>1</issue><subject><json:item><value>Library & information science</value></json:item><json:item><value>Librarianship/library management</value></json:item><json:item><value>Library & information services</value></json:item></subject><genre><json:string>journal</json:string></genre><language><json:string>unknown</json:string></language><title>New Library World</title><doi><json:string>10.1108/nlw</json:string></doi></host><publicationDate>1998</publicationDate><copyrightDate>1998</copyrightDate><doi><json:string>10.1108/03074809810196707</json:string></doi><id>A23C95B9872708FF9FE79BB0C6F36126D60C8E7F</id><score>0.12064864</score><fulltext><json:item><original>true</original><mimetype>application/pdf</mimetype><extension>pdf</extension><uri>https://api.istex.fr/document/A23C95B9872708FF9FE79BB0C6F36126D60C8E7F/fulltext/pdf</uri></json:item><json:item><original>false</original><mimetype>application/zip</mimetype><extension>zip</extension><uri>https://api.istex.fr/document/A23C95B9872708FF9FE79BB0C6F36126D60C8E7F/fulltext/zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/document/A23C95B9872708FF9FE79BB0C6F36126D60C8E7F/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a" type="main" xml:lang="en">The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher>MCB UP Ltd</publisher><availability><p>EMERALD</p></availability><date>1998</date></publicationStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a" type="main" xml:lang="en">The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title><author><persName><forename type="first">C.</forename><surname>Clissman</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">R.</forename><surname>Murray</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">E.</forename><surname>Davidson</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">J.</forename><surname>Hands</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">O.</forename><surname>Sijtsma</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">A.</forename><surname>Noordzij</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">R.</forename><surname>Moulton</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">S.</forename><surname>Shanawa</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">J.</forename><surname>Darzentas</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author><author><persName><forename type="first">I.</forename><surname>Pettman</surname></persName><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></author></analytic><monogr><title level="j">New Library World</title><idno type="pISSN">0307-4803</idno><idno type="DOI">10.1108/nlw</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="1998-02-01"></date><biblScope unit="volume">99</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="10">10</biblScope><biblScope unit="page" to="19">19</biblScope></imprint></monogr><idno type="istex">A23C95B9872708FF9FE79BB0C6F36126D60C8E7F</idno><idno type="DOI">10.1108/03074809810196707</idno><idno type="filenameID">0720990102</idno><idno type="original-pdf">0720990102.pdf</idno><idno type="href">03074809810196707.pdf</idno></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>1998</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas record syntax conversion which covers UNIMARC, SGML and Dublin Core result set deduplication, covering International Standard Book Number ISBN, International Standard Serial Number ISSN, the Universal Standard Bibliographic Code USBC, Serial Item and Contribution Identifier SICI, Digital Object Identifiers DOI and Uniform Resource Names URN and multilingual thesauri.</p></abstract><textClass><keywords scheme="keyword"><list><head>Keywords</head><item><term>Cataloguing</term></item><item><term>International standards</term></item><item><term>Library materials</term></item></list></keywords></textClass><textClass><keywords scheme="Emerald Subject Group"><list><label>cat-LISC</label><item><term>Library & information science</term></item><label>cat-LLM</label><item><term>Librarianship/library management</term></item><label>cat-LISE</label><item><term>Library & information services</term></item></list></keywords></textClass></profileDesc><revisionDesc><change when="1998-02-01">Published</change></revisionDesc></teiHeader></istex:fulltextTEI><json:item><original>false</original><mimetype>text/plain</mimetype><extension>txt</extension><uri>https://api.istex.fr/document/A23C95B9872708FF9FE79BB0C6F36126D60C8E7F/fulltext/txt</uri></json:item></fulltext><metadata><istex:metadataXml wicri:clean="corpus emerald not found" wicri:toSee="no header"><istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration><istex:document><!-- Auto generated NISO JATS XML created by Atypon out of MCB DTD source files. Do Not Edit! --><article dtd-version="1.0" xml:lang="en" article-type="case-report"><front><journal-meta><journal-id journal-id-type="publisher-id">nlw</journal-id><journal-id journal-id-type="doi">10.1108/nlw</journal-id><journal-title-group><journal-title>New Library World</journal-title></journal-title-group><issn pub-type="ppub">0307-4803</issn><publisher><publisher-name>MCB UP Ltd</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.1108/03074809810196707</article-id><article-id pub-id-type="original-pdf">0720990102.pdf</article-id><article-id pub-id-type="filename">0720990102</article-id><article-categories><subj-group subj-group-type="type-of-publication"><compound-subject><compound-subject-part content-type="code">case-report</compound-subject-part><compound-subject-part content-type="label">Case study</compound-subject-part></compound-subject></subj-group><subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-LISC</compound-subject-part><compound-subject-part content-type="label">Library & information science</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-LLM</compound-subject-part><compound-subject-part content-type="label">Librarianship/library management</compound-subject-part></compound-subject></subj-group><subj-group><compound-subject><compound-subject-part content-type="code">cat-LISE</compound-subject-part><compound-subject-part content-type="label">Library & information services</compound-subject-part></compound-subject></subj-group></subj-group></article-categories><title-group><article-title>The UNIverse Project: state‐of‐the‐art of the standards, softwares and systems which will underpin the development. Part 2: record syntax conversion, result set de‐duplication, and multilingual thesauri</article-title></title-group><contrib-group><contrib contrib-type="author"><string-name><given-names>C.</given-names> <surname>Clissman</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>R.</given-names> <surname>Murray</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>E.</given-names> <surname>Davidson</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>J.</given-names> <surname>Hands</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>O.</given-names> <surname>Sijtsma</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>A.</given-names> <surname>Noordzij</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>R.</given-names> <surname>Moulton</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>S.</given-names> <surname>Shanawa</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>J.</given-names> <surname>Darzentas</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><contrib-group><contrib contrib-type="author"><string-name><given-names>I.</given-names> <surname>Pettman</surname></string-name><aff>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</aff></contrib></contrib-group><pub-date pub-type="ppub"><day>01</day><month>02</month><year>1998</year></pub-date><volume>99</volume><issue>1</issue><fpage>10</fpage><lpage>19</lpage><permissions><copyright-statement>© MCB UP Limited</copyright-statement><copyright-year>1998</copyright-year><license license-type="publisher"><license-p></license-p></license></permissions><self-uri content-type="pdf" xlink:href="03074809810196707.pdf"></self-uri><abstract><p>Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas: record syntax conversion which covers UNIMARC, SGML and Dublin Core; result set de‐duplication, covering International Standard Book Number (ISBN), International Standard Serial Number (ISSN), the Universal Standard Bibliographic Code (USBC), Serial Item and Contribution Identifier (SICI), Digital Object Identifiers (DOI) and Uniform Resource Names (URN); and multi‐lingual thesauri.</p></abstract><kwd-group><kwd>Cataloguing</kwd><x>, </x><kwd>International standards</kwd><x>, </x><kwd>Library materials</kwd></kwd-group><custom-meta-group><custom-meta><meta-name>peer-reviewed</meta-name><meta-value>no</meta-value></custom-meta><custom-meta><meta-name>academic-content</meta-name><meta-value>yes</meta-value></custom-meta><custom-meta><meta-name>rightslink</meta-name><meta-value>included</meta-value></custom-meta></custom-meta-group></article-meta></front><body><sec><title>Introduction</title><p>UNIverse is a research and development project supported by the European Commission under the Telematics for Libraries 4th Framework Programme (DG XIII). Its major objectives are to develop software that will present a large number of distributed catalogues in such a way that they appear to be one single union catalogue and offer enhanced services based on these catalogues. The system configuration is being designed to effectively deliver: <list list-type="bullet"><list-item><label>• </label><p>search and retrieve (including record de‐duplication, enhancement of records, the ability to handle records in different languages and the use of thesauri in searching);</p></list-item><list-item><label>• </label><p>ILL;</p></list-item><list-item><label>• </label><p>document delivery (including multimedia capabilities); and</p></list-item><list-item><label>• </label><p>shared cataloguing and record supply.</p></list-item></list></p><p>This 30‐month project commenced in October 1996 and the last nine months (July 1998 to March 1999) will be a large‐scale test involving between 50 and 60 libraries. The system will build on work done under previous EC‐funded projects. A more detailed description of the project and its evolution is given in a previous article (Murray and Pettman, 1997).</p><p>Since the project involves many different libraries and systems it will be developed using emergent open standards. In the previous paper (Clissman <italic>et al</italic>., 1997) we examined the state of the art of Z39.50, WWW integration with Z39.50, and Unicode. In this part we will cover record syntax conversion; result‐set de‐duplication; and multilingual thesauri. In Part 3 we will look at ILL protocols; multimedia document delivery; authentication; and payment schemes.</p></sec><sec><title>Record syntax conversion</title><sec><title>Introduction</title><p>In the 1960s, the first efforts towards the development of machine‐readable records were made, which contributed to the advancement of computerised systems for aiding in the operation of libraries. These efforts culminated in 1968 with the issuance of the MARC standard by the Library of Congress. The recording and presentation of bibliographic data in machine‐readable form raised the expectations for facilitating the exchange of this type of data between libraries locally and even internationally. However, due to the wide variety of information sources that are not restricted only to libraries, and due to the complexities of international bibliographic record keeping, the road to unification and smooth exchange of data proved to be long.</p><p>ISO and EWOS are among the bodies that have been and are dealing with the problems of standardisation of bibliographic records and their exchange. In addition several actions and projects work in this area contributing to the standardisation process and developing solutions that address a variety of related problems. Worldwide, bibliographic records conform to MARC standards. The problem arises from the existence of a number of variations of MARC standards in different countries (Hill, 1996). Although the general structure from country to country is common, these different interpretations have created the need for a tiered overall standard and for conversion facilities between the various existing MARC formats.</p></sec><sec><title>UNIMARC</title><p>The above needs prompted IFLA to derive the UNIMARC standard[<xref ref-type="bibr" rid="b1">1</xref>, <xref ref-type="bibr" rid="b2">2</xref>] which is aimed at unifying the bibliographic record keeping, encouraging all national libraries (and subsequently all libraries) to adhere to this standard. However, in the EC alone, there are about ten standards of variations of the MARC format with the number rising to about 50 worldwide. The sheer size of the existing collections of records among other things make it prohibitive at present to adopt quickly and effortlessly the UNIMARC standard.</p><p>Nevertheless, since UNIMARC was created with the existing formats in mind, the creation of conversion programs/facilities/ tools is a task that can be and is undertaken by several projects. The central point for these conversion programs is to use UNIMARC as the reference standard that the various MARC formats can be converted to and from. There are also some limited efforts to convert from one national format to another directly, but this is limited to the two interacting formats. Conversion between formats is generally limited mostly from the USA, UK, French and German records to other national formats.</p><p>To emphasise further the importance of UNIMARC, it has been officially agreed as the model for the development of new machine‐readable bibliographic formats, e.g., grey literature. Furthermore, the UNIMARC/authorities published in 1991, established UNIMARC as the way to manage the authority format question. A permanent UNIMARC committee is charged with regularly supervising the development of the format. In maintaining the format, care is taken to make changes upwardly compatible, i.e. no records created before a change would be invalid after it. The latest development in the format has come about because of the requirement of European Union countries to produce unified specialised catalogues of their records. In order to produce such unified catalogues they had to adopt a common format for them ‐ UNIMARC.</p><p>Historically, before client/server and networking technologies emerged, the trend was for libraries to attempt to convert their catalogues, so technologies centred on this, and some library automation products are offering just this. The central function of the bibliographic utilities is to make available vast reference databases for use in libraries and other resource organisations. Records may be grabbed from a specific library catalogue or from collective, computerised catalogues. This may be done through an online consultation or using a CD‐ROM medium. These records are presented for sale in many different forms. The cheapest and most efficient of which is the grabbing of the complete record from the extant computerised catalogue. The utilisation of the authority inputs of a catalogue for the creation of another one is also possible. In this case, the full record is not used but only the access standardised points for the author, subject, series etc.</p><sec><title>The UNIMARC format</title><p>The UNIMARC format, like any other version of MARC, involves three elements of the bibliographic record: <list list-type="order"><list-item><label>1 </label><p>record structure;</p></list-item><list-item><label>2 </label><p>content designation; and</p></list-item><list-item><label>3 </label><p>data content.</p></list-item></list></p><p><italic>Record structure </italic>is designed to control the representation of data by storing it in fields. All data in the record must be stored using one or more character sets. UNIMARC allows the use of certain character sets, approved by the ISO. The record structure established by UNIMARC is an implementation of the relevant standard: Format for bibliographic information interchange on magnetic tape (ISO 2709‐1981). This structure utilises record labels and directories.</p><p><italic>Content designation. </italic>Certain conventions are followed in order to identify the data elements within records. Such elements which include author, title and subject access are further characterised where necessary. This supports the manipulation of the data for a variety of purposes: such as, providing multiple access points for searching, allowing the typography and layout to be varied, permitting certain elements of the record to be omitted where this is required. In general, UNIMARC provides content designation only for data that are applicable to all copies of a work.</p><p>However, information which applies only to some copies (or even a single copy) of a work may be of interest beyond the holding institution. In such cases UNIMARC assigns specific fields for such details. These fields are also available for cases where the information is for in‐house purposes only.</p><p><italic>Data content. </italic>The content is the data that are stored in the fields within the record. Data can be coded data or bibliographic data. Coded data are used to represent such items as control numbers, publication type, and main language of text. There is also provision for the characteristics of special types of items such as printed music. Bibliographic data are defined by reference to the International Standard Bibliographic Description for that type of material. In addition, each record can carry a class number and subject headings.</p><p>Thus UNIMARC facilitates the description, retrieval and control of bibliographic items. This is achieved by providing a structure for recording bibliographic information, which is input by reference to international standards.</p></sec></sec><sec><title>Record syntax conversion products</title><p>Various software and consulting firms offer library automation products. It is not always easy to verify the claims made for these products which are sometimes announced well before the product has actually been rolled out.</p><p>The following library automation companies claim to deal with the record syntax conversion problem in some way, i.e. manual versus electronic or automatic: <list list-type="bullet"><list-item><label>• </label><p>OCLC Conversion services. OCLC offer either customised or batch conversion to MARC format. In the case of customised conversion the retro‐conversion service allows for more individualised specification of records ‐ OCLC staff search for and customise matching records. In the case of batch conversion one’s own staff enter search keys on diskettes, which are mailed to OCLC for machine matching against the Online Union Catalogue. Other conversion services offer variations on these two themes, e.g. Online Retrospective Conversion ‐ one’s own staff use the Online Union Catalogue to convert one’s records at reduced rates, giving direct control.</p></list-item><list-item><label>• </label><p>GAYLORD Information Systems claim experience in MARC record conversion. They produce GALAXY, promoted as a complete library automation system, which includes SuperCAT, for MARC cataloguing[<xref ref-type="bibr" rid="b3">3</xref>].</p></list-item><list-item><label>• </label><p>TALX: offers electronic conversion from bibliographic records that are brief MARC or non‐MARC records. TALX loads MARC and non‐MARC formats, extracts search keys and obtains complete MARC records from a bibliographic database[<xref ref-type="bibr" rid="b4">4</xref>].</p></list-item><list-item><label>• </label><p>SIRS Mandarin offers a MARCOUT utility which can take records in MARC and non‐MARC format and export in US MARC communications format, in order to merge the patron library’s record into a union catalogue[<xref ref-type="bibr" rid="b5">5</xref>].</p></list-item></list></p></sec><sec><title>Record syntax conversion and projects</title><p>Projects which have dealt or are dealing with this problem or some aspect of it:</p><sec><title>National Libraries Project on CD‐ROM (1990‐1993)</title><p>A major goal was to promote economies in library cataloguing through an improved interchange of bibliographic records between European national agencies irrespective of different national MARC formats. The project looked at providing conversion from the MARC format of the host CD‐ROM to the MARC format required by the user. The ultimate aim was the development and testing software methodology for the creation of MARC conversion routines[6]. The main objective of the work package was “to bridge the differences in MARC formats so that data can be readily reused irrespective of originating format; and, parallel to this, to investigate and test the feasibility of developing a practical methodology and micro‐based tool for the conversion of MARC data from a source format to a target format”. The project produced a software program, MARCCONV. The basic function of the program is to demonstrate the feasibility of a table driven MARC format conversion program running under DOS. Although the initial prototype used a UKMARC to UNIMARC table alone, the program was flexibly constructed to enable the future implementation of multiple conversion tables by those wishing to develop the program further for their own local needs. The program can: <list list-type="bullet"><list-item><label>• </label><p>import and export multiple bibliographic records in ISO 2709 exchange format, as specified in the <italic>UKMARC Manual</italic>, 3rd Edition, Section 3;</p></list-item><list-item><label>• </label><p>import and export multiple bibliographic records that use, but are not limited to, the full ISO 5426 character set;</p></list-item><list-item><label>• </label><p>optionally, display results of conversion in tagged MARC format on screen;</p></list-item><list-item><label>• </label><p>optionally, re‐direct the tagged screen display to an ASCII text file;</p></list-item><list-item><label>• </label><p>accept new MARC conversion tables with the minimum of modification; and</p></list-item><list-item><label>• </label><p>use conversion tables that are capable of modification using a standard ASCII text editor (e.g., MS DOS 5.0’s “EDIT”).</p></list-item></list></p></sec><sec><title>UseMARCON (User controlled generic MARC converter ‐ ongoing)</title><p>The UseMARCON project as a whole aims to develop a Generic MARC converter that can solve the current conversion problems of MARC formats[7]. The ultimate goal of the project is to develop a toolbox capable of converting bibliographic records from any MARC format into any other MARC format, through a central format. UNIMARC is used as a core format for the converter. In more detail, the objectives of the project are the production of specifications for the conversion functions and conversion tables between different MARC formats and of software tools to convert MARC formats. The definition of how the conversion is to take place between the source and the destination formats is done through the usage of a user‐friendly interface. UseMARCON’s impact expectation is to improve the exchanges of bibliographic information between libraries.</p></sec><sec><title>ONE (OPAC Network in Europe ‐ ongoing)</title><p>The technical objectives of ONE are, among others, to develop a toolkit for functions such as MARC conversion, character conversion, CCL‐RPN translation, etc. “The software produced within ONE will also address issues of diverse record formats and character sets which are currently barriers to seamless access across distributed databases”[8].</p></sec></sec><sec><title>Other formats: SGML and Dublin Core</title><p>Although UNIMARC has been proposed as the standard, there will be cases where records are not held in MARC structures. Although it is probably out of the remit of the UNIverse programme to tackle non‐MARC conversions, utilities for such conversions are mentioned here for the sake of completeness: The Dublin Core and SGML (standard general mark‐up language).</p><sec><title>Dublin Core</title><p>There now exists a crosswalk between the 15 elements in The Dublin Core Element Set and MARC bibliographic data elements[9]. A mapping between these two sets of elements is necessary so that conversion between various syntaxes can occur accurately. Once Dublin Core style metadata records are widely implemented, they might interact with MARC records in at least two ways: <list list-type="bullet"><list-item><label>• </label><p><italic>Enhancement of a simple resource description record. </italic>A cataloguing agency may wish to extract the metadata provided in Dublin Core style, presumably in HTML or SGML, and convert the data elements to MARC fields, resulting in a skeletal record. That record might then be enhanced as needed to add additional information generally provided in the particular catalogue.</p></list-item><list-item><label>• </label><p><italic>Searching across syntaxes and databases. </italic>Libraries have large legacy systems with millions of pieces of invaluable information in MARC bibliographic records (which may also be called metadata). Over the past few years, with the expansion of electronic resources over the Internet, other syntaxes have been considered for providing metadata because of the cost and complexity of creating MARC records in all cases.</p></list-item></list></p></sec><sec><title>SGML</title><p>There is recently much more interest shown in SGML as a means of integrating electronic resources because its potential is to allow the exchange of much more information than bibliographic records, and because of: <list list-type="bullet"><list-item><label>• </label><p>The Text Encoding Initiative. TEI is an international project that has developed guidelines for the preparation and interchange of electronic texts for scholarly research. TEI compliant instances contain headers allowing the extraction of bibliographic information, to allow for the integration of electronic text cataloguing into the traditional technical services operations. This means that bibliographic record data are taken care of as well as much richer representations of the actual item behind the record.</p></list-item><list-item><label>• </label><p>Publishers, subscription agents and document suppliers are starting to distribute journal article references in SGML format for integration in the library catalogue and for the computer‐aided production of current awareness services, or CAPCAS as Elsevier likes to call it.</p></list-item><list-item><label>• </label><p>The RIDDLE (Rapid Information Display and Dissemination in a Library Environment) project’s objectives are the same as those of the CAPCAS project, though it is based on the scanning and optical character recognition of journal table of contents pages. The results from the scanning and OCR‐process are SGML translated files, which can be applied to any target online library catalogue.</p></list-item></list></p><p>Another reason for the interest in SGML by academic libraries and bibliographic institutions is that if current predictions hold, by the year 2000, 80 per cent of publishers will be using SGML, then libraries will be receiving their information in a very different format.</p><p>As for the conversion from/to the SGML format, at present there exists a USMARC to SGML conversion tool (marc2sgml) and the converse, sgml2marc is under development at U C Berkeley Library, again using USMARC[10].</p><p>An example of the usage of SGML rather than MARC format is the VUBIS Antwerp Library network consisting of ten academic or special libraries, producing a union catalogue of approximately 900,000 titles, and increasing by 75,000 titles a year[11]. For the exchange of bibliographic data, usually MARC or UNIMARC are used; however, in this case SGML was used for the following reasons: <list list-type="bullet"><list-item><label>• </label><p>Bibliographic data can be considered as textual data with a logical, even rigorous structure.</p></list-item><list-item><label>• </label><p>The project started from a complex situation with too many different formats (MARC and non‐MARC) based on different cataloguing rules and at different quality levels, provided by too many different libraries. SGML seemed an obvious choice because of its flexibility.</p></list-item><list-item><label>• </label><p>SGML can create an added value for each participating library: once the data are available in SGML, they can easily be reused for other purposes.</p></list-item><list-item><label>• </label><p>By using the technique of entity references, SGML provides possibilities to anticipate all problems with regard to special characters. This is a problem not to be underestimated because library catalogues contain multilingual materials and library systems use different ways of encoding these special characters.</p></list-item><list-item><label>• </label><p>Because data are supplied by different libraries using different systems, it was felt that some process of quality control was necessary. By distributing an SGML parser, all members were able to check the quality of their data, so that a “uniform” quality level was obtained.</p></list-item></list></p><p>As a result of this project, all the universities in Belgium are now exchanging their catalogue records in SGML format for the yearly production of the CD‐ROM of records.</p></sec></sec></sec><sec><title>De‐duplication</title><sec><title>Introduction</title><p>For large‐scale parallel searching of databases that may have significant overlap in coverage, the issue of result set de‐duplication is clearly of paramount importance. The requirements for de‐duplication are complex and sometimes mutually incompatible; they include: <list list-type="bullet"><list-item><label>• </label><p>Accuracy ‐ two records should not be represented as duplicates when they are not.</p></list-item><list-item><label>• </label><p>Thoroughness/completeness ‐ record matching may be detected by a number of criteria, and if a de‐duplication service is to be useful it must check a significant number of these possibilities.</p></list-item><list-item><label>• </label><p>Speed ‐ in an interactive service the de‐duplication process must not noticeably degrade the response time.</p></list-item></list></p></sec><sec><title>Naming</title><p>The key to accurate de‐duplication is the availability of unique naming services for each “information domain”, i.e. the availability of a mechanism by which each object can be assigned a unique persistent name by which it may be referred to in the future. The concept of universal names has been warmly embraced by the networking and library communities, but convergence on the details proved difficult until recently. Three major problems exist with all such naming schemes and any de‐duplication service will undoubtedly encounter these, and must have some way of resolving the issues raised by them. These problems are: <list list-type="bullet"><list-item><label>• </label><p>Not all objects will be named (e.g. books without ISBNs).</p></list-item><list-item><label>• </label><p>The same object may be assigned different names by different agencies (e.g. books with multiple ISBNs).</p></list-item><list-item><label>• </label><p>Errors may be made whereby two different objects are assigned the same name (e.g. two different books have the same ISBN).</p></list-item></list></p><p>While all these problems may be regarded as “legacy issues” that will not occur in the future, any de‐duplication service must allow for existing data problems.</p></sec><sec><title>Naming schemes</title><p>Object naming schemes are generally domain‐specific. The following section provides a description of the major naming schemes that will be encountered by the UNIverse system.</p><sec><title>ISBN</title><p>The ISBN is an identification system for books and other media which allows for order‐processing by booksellers, libraries, universities, wholesalers and distributors. The ISBN identifies a title or edition of a title and is unique to that title or edition.</p><p>The ISBN system was established in 1968 as a standard for books and other monographic publications. Today, the scope of the system has expanded to include other media such as calendars, spoken word audiocassettes, videocassettes and electronic media.</p><p>Virtually every item sold in a bookstore requires an ISBN as increasing numbers of publishing systems base their entire inventory on the ISBN[12].</p></sec><sec><title>International Standard Serial Numbers (ISSN)</title><p>The International Standard Serial Number (ISSN) is the worldwide identification code for serial publications. It is an eight‐digit code, unique to each serial, consisting of seven digits plus a computer check digit. For example, ISSN 1173‐201X.</p></sec><sec><title>The ISSN network: The ISSN system was established in 1971 for the purpose of assigning, registering and controlling ISSNs. The ISSN network consists of more than 55 national and regional centres, co‐ordinated by an international centre situated in Paris.</title><p>An ISSN identifies only one serial title. Therefore, an individual ISSN should be given for: <list list-type="bullet"><list-item><label>• </label><p>Each serial title, whether new or a change of title;</p></list-item><list-item><label>• </label><p>Each continuing, separately numbered, supplement to a serial;</p></list-item><list-item><label>• </label><p>Each numbered monographic series;</p></list-item><list-item><label>• </label><p>Some serials where the issuing body changes its name; and</p></list-item><list-item><label>• </label><p>Each format of a serial issued in more than one medium (i.e. print and CD‐ROM).</p></list-item></list></p></sec><sec><title>USBC</title><p>The Universal Standard Bibliographic Code is a code used to identify bibliographic items, monographs, serials, articles in serials, etc. that are derived from parts of the bibliographic record[13]. In contrast to other identifiers such as the ISBN or ISSN no part of it is allocated. Therefore, a USBC can always be created from a reference, and can also be used for material that has not had an ISBN allocated. Various forms of the code have been developed for different uses and it has been used to match between bibliographic databases to find duplication and to match citations to full‐text databases. A history of the development of the USBC can be found in Ayres <italic>et al</italic>. (1996).</p></sec><sec><title>SICI</title><p>ANSI/NISO Z39.56‐199X defines the requirements for a variable length code that uniquely identifies serial items (e.g. issues) and each contribution (e.g. article) contained in a serial. The acronym “SICI” stands for Serial Item and Contribution Identifier and is used in this standard to refer to the code itself.</p></sec><sec><title>Scope: The standard defines the Serial Item and Contribution Identifier (SICI) for use with serial publications in all formats. The standard is intended for use by those members of the bibliographic community engaged in the functions associated with the management of serials and the contributions they contain. This includes ordering, accessioning, claiming, royalty collection, rights management, online retrieval, database linking, document delivery, etc. The standard describes how to construct a variable length code for the unique identification of a serial item or a contribution. Identifiers constructed according to this standard are used within a wide variety of applications: Electronic Data Interchange (EDI), Serials Industry Systems Advisory Committee (SISAC) barcodes, Z39.50 queries, Uniform Resource Names (URNs ‐ see also section 5.3.6 below), electronic‐mail and human transcription in print.</title><p>The SICI employs the International Standard Serial Number (ISSN) to identify the serial title. The serial must have been assigned an ISSN in order to use this standard to construct item or contribution identifiers for material published in the serial.</p><p>In recognition of the large installed base of serial titles, contributions and derived works (abstracting and indexing) databases, no data elements outside those normally associated with such works are introduced into this standard.</p></sec><sec><title>The model: The SICI is a combination of defined segments, all of which are required and interpretation of which is determined by the CONTROL SEGMENT. These segments are:</title><list list-type="bullet"><list-item><label>• </label><p>ITEM SEGMENT ‐ the data elements needed to describe the Serial Item (including ISSN, enumeration, chronology).</p></list-item><list-item><label>• </label><p>CONTRIBUTION SEGMENT ‐ the data elements needed to identify contributions within an item (including location, title code and other numbering schemes in a specific instance of the SICI).</p></list-item><list-item><label>• </label><p>CONTROL SEGMENT ‐ the data elements needed to record those administrative elements that determine the validity, version, formats and extent of the code representation.</p></list-item></list><p>Three combinations of Segments are currently defined in the standard. They are referred to in the body of the standard as Code Structure Identifiers (CSI). CSI‐1, CSI‐2 and CSI‐3 each have specific requirements for the contents of the various segments. To identify a specific serial item (issue) only, the Code Structure Identifier (CSI) is one (1) and the CONTRIBUTION SEGMENT is null.</p></sec><sec><title>Digital object identifiers</title><p>The DOI system has three parts: an identifying number (DOI), an automated directory, and publisher‐maintained databases. An agency maintains the directory, assigns publisher identifiers (“prefixes”), and promotes the system. Publishers register with the agency to receive their prefixes. A prefix is then combined by the publisher with a publisher‐chosen suffix that can be either a random number or taken from any internal numbering system that a publisher uses (examples include SICI, PII, chronological numbering, sequential numbering, internal catalogue numbers, or any other system). Assigning DOIs can be automated and simple for the publishers to do in the course of normal publishing operations, and then DOIs (prefix plus suffix) can be entered into the directory easily (in a batch mode or individually) at any time.</p><p>The DOI system connects a user (e.g. researcher, scholar, teacher, customer) with the current copyright holder or assignee for immediate online interaction. In most cases, the user will not have to enter a DOI number manually. When a change of copyright ownership occurs, the DOI remains the same but a new pointer (associated address) is entered in the directory to ensure persistence. The DOI numbering syntax is consistent with Internet standards activities in that it complies with the syntax for a URN (Uniform Resource Name).</p></sec><sec><title>Uniform Resource Names</title><p>A good introduction to URNs is Internet RFC 1737, <italic>Functional Requirements for Uniform Resource Names</italic> (Sollins and Masinter, 1994). The following is an extract from their introduction. It describes the function of URNs and, in particular, how they differ from the Uniform Resource Locators (URL) used by the World Wide Web:<disp-quote><p>A URN identifies a resource or unit of information. It may identify, for example, intellectual content, a particular presentation of intellectual content, or whatever a name assignment authority determines is a distinctly nameable entity. A URL identifies the location or a container for an instance of a resource identified by a URN. The resource identified by a URN may reside in one or more locations at any given time, may move, or may not be available at all. Of course, not all resources will move during their lifetimes, and not all resources, although identifiable and identified by a URN will be instantiated at any given time. As such a URL is identifying a place where a resource may reside, or a container, as distinct from the resource itself identified by the URN.</p></disp-quote></p></sec><sec><title>URN requirements</title><list list-type="bullet"><list-item><label>• </label><p><italic>Global scope:</italic> A URN is a name with global scope which does not imply a location. It has the same meaning everywhere.</p></list-item><list-item><label>• </label><p><italic>Global uniqueness: </italic>The same URN will never be assigned to two different resources.</p></list-item><list-item><label>• </label><p><italic>Persistence: </italic>It is intended that the lifetime of a URN be permanent. That is, the URN will be globally unique forever, and may well be used as a reference to a resource well beyond the lifetime of the resource it identifies or of any naming authority involved in the assignment of its name.</p></list-item><list-item><label>• </label><p><italic>Scalability: </italic>URNs can be assigned to any resource that might conceivably be available on the network, for hundreds of years.</p></list-item><list-item><label>• </label><p><italic>Legacy support: </italic>The scheme must permit the support of existing legacy naming systems, in so far as they satisfy the other requirements described here.</p></list-item><list-item><label>• </label><p><italic>Extensibility: </italic>Any scheme for URNs must permit future extensions to the scheme.</p></list-item><list-item><label>• </label><p><italic>Independence: </italic>It is solely the responsibility of a name issuing authority to determine the conditions under which it will issue a name.</p></list-item></list></sec><sec><title>Resolution. To use a URN, there must be a network‐accessible service that can map the name on to the corresponding resource. This process is called resolution.</title><p>Frequently, the resolution system will return the current location of the resource or a list of locations. RFC 1737 concentrates on the case of a URN that resolves to a URL, but a URN can resolve to any network resource or service. For example, in RCDS, a URN may resolve to one or more location‐independent file names (LIFNs), which can themselves be considered a specific type of URN. In the Kahn/Wilensky model a URN, known as a “handle”, resolves to the name of the repository that holds the resource. In other contexts, a URN may resolve to a data structure containing meta‐information about the resource.</p><p>Further details on URNs can be obtained from: <list list-type="bullet"><list-item><label>• </label><p><ext-link ext-link-type="uri" xlink:href="http://www.pacificspirit.com/www">http://www.pacificspirit.com/www</ext-link> ConfNotes/urns.htm</p></list-item><list-item><label>• </label><p><ext-link ext-link-type="uri" xlink:href="http://www.acl.lanl.gov/URI/archive/uri-95q3.messages/0360.html">http://www.acl.lanl.gov/URI/archive/ uri‐95q3.messages/0360.html</ext-link></p></list-item><list-item><label>• </label><p><ext-link ext-link-type="uri" xlink:href="http://www.dlib/org/dlib/february96/02arms.html">http://www.dlib/org/dlib/february96/ 02arms.html</ext-link></p></list-item><list-item><label>• </label><p><ext-link ext-link-type="uri" xlink:href="http://globecom.net/">http://globecom.net/</ext-link>(nobg)/ietf/rfc/ rfc1737.shtml</p></list-item></list></p></sec></sec><sec><title>Clustering</title><p>Most real‐time de‐duplication systems in operation today rely on simple “object name” matching (where object names are defined as above). The simplest and most prevalent version of this is ISBN matching when applied to book databases. This system is, however, restricted due to the imperfections in the naming schemes highlighted above (this is more evident with ISBNs where the legacy situation of book data is the greatest).</p><p>Batch mode de‐duplication systems, like those developed by OCLC, which are generally used for data clean‐up have been developed using more complex and detailed matching algorithms. While these algorithms have greater accuracy, there are speed constraints that have to be taken into account when these are applied to information retrieval systems.</p><p>The notion of “clustering” records that are potential duplicates has been suggested as a more ideal solution for information retrieval. Within such an approach records that are potential duplicates according to some matching algorithm are presented in a “cluster”. Members of a cluster may even represent validly different records that are closely related, for example records with the same uniform title. The cluster can then be exploded to the constituent records. The advantage of this approach is that a more aggressive matching algorithm may be used since no data are lost if duplicates are incorrectly identified.</p></sec></sec><sec><title>Multilingual thesaurus</title><sec><title>Introduction</title><p>The structuring of data in order to improve retrievability has long been the ultimate goal of librarianship. Many instruments for improving access to document collections have been developed in the written history of mankind. Classifications offer us ‐ though not explicitly stated ‐ culturally biased world views, aimed at connecting storage and retrieval systems with our perception of the world.</p><p>Subject heading lists offer a more user‐friendly interface to document information, but do not have the structure of a classification. The combination of classifications and subject heading lists has led to the “thesaurus”, an instrument that offers a conceptual framework that functions as an intermediary between a document collection and a user. The thesaurus was originally conceived as an indexer’s tool to assist in assigning keywords to documents. Since 1989 the emphasis has been shifting towards the thesaurus as an information retrieval aid for end‐user searching. This is still a fertile area for further research and development.</p><p>Recent research aims at developing models that allow for the automatic generation of terms for a thesaurus from a full text‐indexed document collection, combined with several algorithms to express stated relations between terms, concepts and other signifiers in a text.</p><p>With the explosive rise ‐ and internationalisation ‐ of science in the western world it became clear that index languages ‐ because of their cultural bias ‐ fell short on one important aspect: interoperability. Although complicated and labour‐intensive to build and maintain, multilanguage thesauri would allow users to search a (combination of) database(s) with terms in their own language, with the system “translating” the query terms into the other appropriate thesaurus‐languages. The range of multi‐language thesauri is now sufficiently extended to enable UNIverse to explore distributed access to such retrieval tools.</p></sec><sec><title>Multilingual thesaurus structure</title><p>The benefits of using a thesaurus are increased when the thesaurus also maintains hierarchical, synonym and equivalent relationships in other languages. The ideal situation would lead to a thesaurus that acts as a concordance between the term set’s different languages. The concordance is some translation mechanism, be it in the form of a listing, or be it in the form of a combination of algorithms to do the translation “automatically”. The process of building a list‐concordance is comparable to that of building a thesaurus itself. The process of automatic translation is, to date, unreliable. Tests have indicated that an automatic conversion from thesaurus entries to, for example, LC‐Subject Headings, was only successful in about 40 per cent of the entries.</p><p>Another way to “translate” between thesauri is by using an intermediary language. This language has to fulfil several conditions: <list list-type="order"><list-item><label>1 </label><p>it has to be universally accepted;</p></list-item><list-item><label>2 </label><p>cultural biases should be eliminated, or the system has to provide for a mechanism that allows a query term to point to a set of possible descriptors in another language; and</p></list-item><list-item><label>3 </label><p>flexibility in post‐co‐ordination, although within strict limits.</p></list-item></list></p><p>In recent years, the Universal Decimal Classification (UDC) has been suggested as the universal language between different semantic networks. The analytic‐syntactic character of this language provides for the necessary flexibility in assigning specific index terms to (parts of) documents. However, UDC also suffers from a heavy cultural bias, especially where it relates to subjects that are considered “exotic” in the western world.</p><p>Finally, it is possible to generate parts of a thesaurus on a specific domain by using instruments from the world of natural language processing (NLP). This research field focuses on the problematic relationship of the flexible character of a language and the requirements for strictly formalising models that can “understand” natural language requests. NLP is, in the tradition of artificial intelligence research, to date rather experimental.</p><p>Several other research areas are emerging at the moment, but the main focus is on developing an efficient and effective way automatically to generate access that is comparable to the well‐known assigned indexes from the library and database world.</p><p>One other complicating factor is relevant to the UNIverse project: what if the separate thesauri reside on separate machines in different countries?</p><p>This situation is comparable to that of distributed databases, where the search engine is able to retrieve information from several locations and combine it afterwards. The complicating part for thesauri is not so much in the several geographic locations, but in the semantically different spaces. Somehow the search agent has to know what items to search for, where it is not the specific field that is important (as in Z39.50), but the content of the field. With UDC this would mean that the input for the search agent could be a UDC‐string. The agent then searches for the numerical string in several possible combinations. Afterwards only the documents would be shown to the user, not the UDC‐strings nor the thesaurus terms in different languages.</p></sec></sec><sec><title>Conclusion</title><p>In this paper we have considered some of the search and retrieve system requirements for the UNIverse project. The consortium will continue to monitor and contribute to further development in these fields during the life of the project.</p><p>In the next paper (Part 3) we will look at the various systems requirements for the integration of interlibrary loan and multi‐media document delivery services.</p></sec><sec><title>Notes</title><p> 1 <italic>UNIMARC Manual: Bibliographic Format</italic>, 2nd ed., K.G. Saur, München, London, New Providence, Paris, 1994.</p><p> 2 <italic>UNIMARC: An Introduction: Understanding the UNIMARC Format, UBICIM</italic>, <ext-link ext-link-type="uri" xlink:href="http://www.nlc-bnc.ca/ifla/VI/3/p1996-1/unimarc.html">http://www.nlc‐bnc.ca/ifla/VI/3/p1996‐1/unimarc.html</ext-link></p><p> 3 Gaylord, <ext-link ext-link-type="uri" xlink:href="http://www.gaylord.com/">http://www.gaylord.com/</ext-link></p><p> 4 TALX, <ext-link ext-link-type="uri" xlink:href="http://www.talx.com/">http://www.talx.com/</ext-link></p><p> 5 SIRS Mandarin, <ext-link ext-link-type="uri" xlink:href="http://www.sirs.com/">http://www.sirs.com/</ext-link></p><p> 6 National Libraries Project on CD‐ROM Tools for MARC conversion (CDBIB/WP2/RLN/DE/6P), <ext-link ext-link-type="uri" xlink:href="http://www.konbib.nl/kb/sbo/proj/cdbib/wp2.html">http://www. konbib.nl/kb/sbo/proj/cdbib/wp2.html</ext-link></p><p> 7 UseMARCON, <ext-link ext-link-type="uri" xlink:href="http://www.konbib.nl/kb/sbo/proj/en1005.html">http://www.konbib.nl/kb/sbo/proj/en1005.html</ext-link></p><p> 8 ONE Technical Annexe, <ext-link ext-link-type="uri" xlink:href="http://www.bibsys.no/one.ta.html">http://www.bibsys.no/one.ta.html</ext-link></p><p> 9 Dublin Core/MARC Crosswalk Network Development and MARC standards office, <ext-link ext-link-type="uri" xlink:href="http://lcweb.loc.goc/marc/dcross.html">http://lcweb.loc.goc/marc/dcross.html</ext-link></p><p>10 marc2sgml, <ext-link ext-link-type="uri" xlink:href="http://www.library.berkeley.edu/pub/sgml/marcdtd">http://www.library.berkeley.edu/pub/sgml/marcdtd</ext-link></p><p>11 Corthouts, J. and Philips, R., <italic>The Use of SGML in the VUBIS‐Antwerpen Library Network</italic>, <ext-link ext-link-type="uri" xlink:href="http://www.sil.org.sgml.corthou.html">http://www.sil.org.sgml.corthou.html</ext-link>/</p><p>12 The DRA Find product claims to perform result set de‐duplication (this is on a simple ISBN matching algorithm). Information can be found at: <ext-link ext-link-type="uri" xlink:href="http://www.dra.com/textonly/english/products/drafind.htm">http://www.dra. com/textonly/english/products/drafind.htm</ext-link></p><p>13 Further information on USBCs can be found at: <ext-link ext-link-type="uri" xlink:href="http://www.comp.brad.ac.uk/research/database/bib.html">http://www.comp.brad.ac.uk/research/database/ bib.html</ext-link></p></sec></body><back><ref-list><title>References</title><ref id="b1"><mixed-citation><person-group person-group-type="author"><string-name><surname>Ayres</surname>, <given-names>F.H.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Nielsen</surname>, <given-names>L.P.S.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Ridley</surname>, <given-names>M.I.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Torsun</surname>, <given-names>I.S.</given-names></string-name></person-group> (<year>1996</year>, “<article-title><italic>USBC (Universal Standard Bibliographic Code): its origin and evolution</italic></article-title>”, <source><italic>Journal of Librarianship and Information Science</italic></source>, Vol. <volume>28</volume> No. <issue>2</issue>, pp. <fpage>83</fpage><x>‐</x><lpage>91</lpage>.</mixed-citation></ref><ref id="b2"><mixed-citation><person-group person-group-type="author"><string-name><surname>Clissman</surname>, <given-names>C.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Murray</surname>, <given-names>R.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Davidson</surname>, <given-names>E.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Hands</surname>, <given-names>J.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Sijtsma</surname>, <given-names>O.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Noordzij</surname>, <given-names>A.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Moulton</surname>, <given-names>R.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Shanawa</surname>, <given-names>S.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Darzentas</surname>, <given-names>J.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Pettman</surname>, <given-names>I.</given-names></string-name></person-group> (<year>1997</year>, “<article-title><italic>The UNIverse Project: state‐of‐the‐art of the standards, softwares and systems which will underpin the development. Part 1: Z39.50; WWW Integration with Z39.50; and Unicode</italic></article-title>”, <source><italic>New Library World</italic></source>, Vol. <volume>98</volume> No. <issue>1138</issue>, pp. <fpage>267</fpage><x>‐</x><lpage>74</lpage>.</mixed-citation></ref><ref id="b3"><mixed-citation><person-group person-group-type="author"><string-name><surname>Hill</surname>, <given-names>R.W.</given-names></string-name></person-group> (<year>1996</year>, <source><italic>Setting the Record Straight: A Guide to the MARC Format</italic></source>, <publisher-name>NBS</publisher-name>, <ext-link ext-link-type="uri" xlink:href="http://www.bl.uk/nbs/pubs/srs2.tml">http://www.bl.uk/nbs/pubs/srs2.tml</ext-link></mixed-citation></ref><ref id="b4"><mixed-citation><person-group person-group-type="author"><string-name><surname>Murray</surname>, <given-names>R.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Pettman</surname>, <given-names>I.</given-names></string-name></person-group> (<year>1997</year>, “<article-title><italic>The UNIverse Project</italic></article-title>”, <source><italic>New Library World</italic></source>, Vol. <volume>98</volume> No. <issue>1133</issue>, pp. <fpage>53</fpage><x>‐</x><lpage>9</lpage>.</mixed-citation></ref><ref id="b5"><mixed-citation><person-group person-group-type="author"><string-name><surname>Sollins</surname>, <given-names>K.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Masinter</surname>, <given-names>L.</given-names></string-name></person-group> (<year>1994</year>, “<article-title><italic>Functional requirements for uniform resource names</italic></article-title>”, <source><italic>Internet RFC 1737</italic></source>, <publisher-name>December.</publisher-name></mixed-citation></ref></ref-list></back></article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo lang="en"><title>The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title></titleInfo><titleInfo type="alternative" lang="en" contentType="CDATA"><title>The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri</title></titleInfo><name type="personal"><namePart type="given">C.</namePart><namePart type="family">Clissman</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">R.</namePart><namePart type="family">Murray</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">E.</namePart><namePart type="family">Davidson</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">J.</namePart><namePart type="family">Hands</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">O.</namePart><namePart type="family">Sijtsma</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">A.</namePart><namePart type="family">Noordzij</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">R.</namePart><namePart type="family">Moulton</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">S.</namePart><namePart type="family">Shanawa</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">J.</namePart><namePart type="family">Darzentas</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><name type="personal"><namePart type="given">I.</namePart><namePart type="family">Pettman</namePart><affiliation>UNIverse consortium, Data Systems Ltd, Brincliffe House, 861 Ecclesall Road, Sheffield S11 7AE, UK</affiliation></name><typeOfResource>text</typeOfResource><genre type="case-report" displayLabel="case-report"></genre><originInfo><publisher>MCB UP Ltd</publisher><dateIssued encoding="w3cdtf">1998-02-01</dateIssued><copyrightDate encoding="w3cdtf">1998</copyrightDate></originInfo><language><languageTerm type="code" authority="iso639-2b">eng</languageTerm><languageTerm type="code" authority="rfc3066">en</languageTerm></language><physicalDescription><internetMediaType>text/html</internetMediaType></physicalDescription><abstract lang="en">Provides a brief introduction to the UNIverse Project and its major objectives. Continues the overview of the international standards, softwares and systems which will enable bibliographic searching of multiple distributed library catalogues. Part 2 reviews three further areas record syntax conversion which covers UNIMARC, SGML and Dublin Core result set deduplication, covering International Standard Book Number ISBN, International Standard Serial Number ISSN, the Universal Standard Bibliographic Code USBC, Serial Item and Contribution Identifier SICI, Digital Object Identifiers DOI and Uniform Resource Names URN and multilingual thesauri.</abstract><subject><genre>keywords</genre><topic>Cataloguing</topic><topic>International standards</topic><topic>Library materials</topic></subject><relatedItem type="host"><titleInfo><title>New Library World</title></titleInfo><genre type="journal">journal</genre><subject><genre>Emerald Subject Group</genre><topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LISE">Library & information services</topic></subject><identifier type="ISSN">0307-4803</identifier><identifier type="PublisherID">nlw</identifier><identifier type="DOI">10.1108/nlw</identifier><part><date>1998</date><detail type="volume"><caption>vol.</caption><number>99</number></detail><detail type="issue"><caption>no.</caption><number>1</number></detail><extent unit="pages"><start>10</start><end>19</end></extent></part></relatedItem><identifier type="istex">A23C95B9872708FF9FE79BB0C6F36126D60C8E7F</identifier><identifier type="DOI">10.1108/03074809810196707</identifier><identifier type="filenameID">0720990102</identifier><identifier type="original-pdf">0720990102.pdf</identifier><identifier type="href">03074809810196707.pdf</identifier><accessCondition type="use and reproduction" contentType="copyright">© MCB UP Limited</accessCondition><recordInfo><recordContentSource>EMERALD</recordContentSource></recordInfo></mods></metadata><serie></serie></istex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Ticri/explor/TeiVM2/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000454 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000454 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Ticri
|area= TeiVM2
|flux= Istex
|étape= Corpus
|type= RBID
|clé= ISTEX:A23C95B9872708FF9FE79BB0C6F36126D60C8E7F
|texte= The UNIverse Project stateoftheart of the standards, softwares and systems which will underpin the development. Part 2 record syntax conversion, result set deduplication, and multilingual thesauri
}}
| This area was generated with Dilib version V0.6.31. |  |