<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Creating a Linked Data Infrastructure for Managing Electronic Resources in Libraries</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Natanael Arndt</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Nuck</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andreas Nareike</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Norman Radtke</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Leander Seige</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Riechert</string-name>
          <email>thomas.riechert@htwk-leipzig.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>AKSW, Institute for Applied Informatics (InfAI) e.V. Hainstraße 11</institution>
          ,
          <addr-line>04109 Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Leipzig University Library Beethovenstr.</institution>
          <addr-line>6, 04107 Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Leipzig University of Applied Science (HTWK) Gustav-Freytag-Str.</institution>
          <addr-line>42A, 04251 Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The library domain is currently undergoing changes relating to not only physical
resources (e.g. books, journals, CDs/DVDs) but to the rapidly growing numbers
of electronic resources (e.g. e-journals, e-books or databases) which are contained
in their collections as well. Since those resources are not limited to physical
items anymore and can be copied without loss of information, new licensing
and lending models have been introduced. Current licensing models are
pay-perview, patron-driven-acquisition, short term loan and big deal. In addition, with
changing markets, user expectations and publication formats, new models will
be introduced in the future.</p>
      <p>The existing infrastructure is not prepared for managing those new electronic
resources, licensing and lending models. Software which is developed to meet the
current requirements (cf. section 2) is likely to be outdated in a couple of years,
due to the changing modeling requirements. To develop a future-proof managing
system, a highly flexible data model and software which is adaptable to a changed
data model is needed. The targeted user group are librarians with limited or no
understanding of Semantic Web, Linked Data and RDF techniques.</p>
      <p>
        We present AMSL [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], an Electronic Resource Management System which
is based on the generic and collaborative RDF resource management system
OntoWiki [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. Using RDF as data model makes the application flexible and
thus future-proof, while the changing modeling requirements can be met by
adjusting the used RDF vocabulary resp. application profile. To adapt the generic
OntoWiki to the needs of the domain experts, we have added some
components to support domain specific use cases, while still keeping them agnostic to
the used RDF vocabulary. The current status of the project including links to
the source code and a live demonstration is available at the project web-page:
http://amsl.technology/.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2 State of the Art</title>
      <p>
        Software currently in use in libraries is mainly concerned with managing print
resources, such as the Integrated Library System LIBERO (http://www.libero.
com.au/), which is used at Leipzig University Library. But such software is not
prepared for managing electronic resources with complex licensing and access
models. Recently, some commercial vendors have started providing Next
Generation Library Systems which constitute a new approach to Electronic Resource
Management. Due to their commercial nature, it is dificult to evaluate how
lfexible the used data models are and which requirements are met [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ]. Since
the data models are closed, they can not be extended by the customer as
requirements change, whereas the contract and subscription terms often change
with every new business year. Further, it is more dificult to integrate external
knowledge bases in contrast to Linked Data and the Linked Open Data Cloud [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Another approach is to avoid specific library software but to use generic
resource or document management systems, such as Wikis. OntoWiki was
developed as a Wiki system for collaboratively creating semantic data in RDF and
OWL knowledge bases. Over the time, OntoWiki has evolved towards a highly
extensible development framework for knowledge intensive applications [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>The AMSL Electronic Resource Management System</title>
      <p>
        The AMSL Electronic Resource Management System is based on the OntoWiki
Application Framework. It provides the basic functionality for managing
resources i.e. creating, editing, querying, visualizing, linking and exporting RDF/
OWL knowledge bases. With the Linked Data Server and Linked Data
Wrapper/Importer components, it can publish and consume Linked Data according
to the rules [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. An Application Programming Interface allows the development
of powerful third party extensions.
      </p>
      <p>
        A core part of our application is to use an expressive data model as
application profile which comprises diferent RDF and OWL vocabularies. The
expressiveness of the data model helps to move design decisions from the
program code to the easily adoptable vocabulary definitions, which increases the
lfexibility of the whole system. For expressing the data model we combine well
known existing vocabularies, such as DCMI Metadata Terms (http://purl.
org/dc/terms/), Dublin Core Metadata Element Set (http://purl.org/dc/
elements/1.1/), The Bibliographic Ontology (http://purl.org/ontology/
bibo/), Academic Institution Internal Structure Ontology (http://purl.org/
vocab/aiiso/schema#) and The Friend of a Friend RDF vocabulary (http:
//xmlns.com/foaf/0.1/), to keep the data compatible to already existing
components. With AMSL, we further introduce the Vocabulary for Library ERM
(BIBRM, http://vocab.ub.uni-leipzig.de/bibrm/). It provides terms for
expressing licensing and access models and is aligned to the ideas of the
Electronic Resource Management Initiative (ERMI) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. If new requirements arise in
the future, the data model has to be changed and if necessary new vocabulary
terms can be added.
      </p>
      <p>We have developed data templates to provide a user interface for resource
creation to the domain experts. Since our system does not require technical
RDF knowledge of its users, the data templates provide a form based editing
interface, which further supports the created resources to be compliant to the
defined application profile. The template definition itself is expressed in RDF as
well, to achieve the required extensibility, without need to change the software.</p>
      <p>To support the work-flows for managing meta-data coming with electronic
resources (such as contacts, contracts, packages, agreements and licenses),
special import and integration components are developed. Publicly available
Linked Data and SPARQL services, which have evolved in the library domain
in the past years (e.g. title information, ISSN-history and authority files), are
necessary for the electronic resource management and are imported using the
existing Linked Data import process.</p>
      <p>Being able to restore changes made on triples is one of the existing features of
OntoWiki. In the AMSL project further requirements for reproducibility,
consistency and increased clarity of resource changes where formulated. To meet these
requirements the present versioning system was extended towards a
ChangeSet ontology4. The versioning metadata is stored in a SQL database containing
the ChangeSet elements. Hence, the underlying data model is now capable of
expressing the same amount of information as a ChangeSet. Additions and
removals concerning the same triple are aggregated to a change statement. Even
though the versioning metadata is not stored in form of triples, the information
could be queried and transferred into a ChangeSet knowledge base for further
purposes. Moreover multiple retrieval capabilities for querying extended
versioning information have been added in form of an OntoWiki extension.</p>
      <p>The present search function of the OntoWiki is based on a conventional
SPARQL search, using a bif:contains filter on labels. To improve search speed
and provide additional features like a fuzzy search, the Elastic Search search
engine was integrated as an OntoWiki extension. This full-text search makes use
of a class based index structure. Hence, it provides a faster access to pre-indexed
resources. The underlying index structure is built up by indexing classes of the
knowledge base which contains information that need to be accessed frequently.
That is, classes containing properties such as dc:title are more meaningful to
be searched with a full-text search than classes that only include properties like
e.g. bibo:issn which contain numerical sequences. Additionally to the
autocompletion features search function, an extended search supports an enhanced
fuzzy search which provides the possibility of restricting the result set to the
previously defined classes and is more robust against typing mistakes.
4 http://vocab.org/changeset/schema.html
We demonstrate a novel approach to build up an electronic resource
management system for libraries by using generic RDF resource management technology.
The used generic components are extended and complemented by some domain
adaptable components to provide a customized interface to domain experts.
Consequently using Linked Data and RDF further enables and supports libraries to
build up a Linked Data infrastructure for exchange of meta data across libraries
as well as across institutions using the services provided by library.
5</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgments</title>
      <p>The presented software system was developed in the AMSL project for
developing an Electronic Resource Management System based on Linked Data
technology (http://amsl.technology/). We want to thank our colleagues Lydia
Unterdörfel, Carsten Krahl and Björn Muschall from Leipzig University Library,
Jens Mittelbach from Saxon State and University Library Dresden (SLUB) and
our fellows from Agile Knowledge Engineering and Semantic Web (AKSW)
research group especially Henri Knochenhauer for their support, helpful comments
and inspiring discussions. This work was supported by the European Union and
Free State of Saxony by a grant from the European Regional Development Fund
(ERDF) for the project number 100151134 (SAB index).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Nareike</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arndt</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Radtke</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nuck</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seige</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riechert</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Amsl - managing electronic resources for libraries based on semantic web</article-title>
          .
          <source>In: Workshop on Data Management and Electronic Resource Management in Libraries (DERM</source>
          <year>2014</year>
          ) :
          <article-title>INFORMATIK 2014</article-title>
          . (
          <year>September 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Heino</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dietzold</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Developing semantic web applications with the ontowiki framework</article-title>
          . In Pellegrini, T.,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tochtermann</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schaffert</surname>
          </string-name>
          , S., eds.:
          <string-name>
            <surname>Networked Knowledge - Networked Media</surname>
          </string-name>
          . Volume
          <volume>221</volume>
          of Studies in Computational Intelligence. Springer, Berlin / Heidelberg (
          <year>2009</year>
          )
          <fpage>61</fpage>
          -
          <lpage>77</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Frischmuth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tramp</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riechert</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <string-name>
            <surname>OntoWiki - An Authoring</surname>
          </string-name>
          ,
          <article-title>Publication and Visualization Interface for the Data Web</article-title>
          .
          <source>Semantic Web Journal</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Jewell</surname>
          </string-name>
          , T.D.,
          <string-name>
            <surname>Anderson</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chandler</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Farb</surname>
            ,
            <given-names>S.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parker</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riggio</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robertson</surname>
            ,
            <given-names>N.D.M.:</given-names>
          </string-name>
          <article-title>Electronic resource management - report of the dlf erm initiative</article-title>
          .
          <source>Technical report</source>
          , Digital Library Federation, Washington,
          <string-name>
            <surname>D.C.</surname>
          </string-name>
          (
          <year>2004</year>
          ) http://old.diglib.org/pubs/dlf102/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Jewell</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aipperspach</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anderson</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>England</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kasprowski</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McQuillan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGeary</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riggio</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Making good on the promise of erm: A standards and best practices discussion paper</article-title>
          .
          <source>Technical report, NISO ERM Data Standards and Best Practives Review Steering Committee, One North Charles Street, Suite</source>
          <year>1905</year>
          , Baltimore, MD
          <volume>21201</volume>
          (
          <year>January 2012</year>
          ) http://www.niso.org/apps/group_public/ document.php?document_id=7946&amp;wg_abbrev=ermreview.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked Data. Design issues</article-title>
          ,
          <source>W3C (June</source>
          <year>2009</year>
          ) http://www.w3. org/DesignIssues/LinkedData.html.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>