Search (370 results, page 1 of 19)

  • × theme_ss:"Metadaten"
  1. Hill, L.L.; Janée, G.; Dolin, R.; Frew, J.; Larsgaard, M.: Collection metadata solutions for digital library applications (1999) 0.29
    0.2854793 = sum of:
      0.06354659 = product of:
        0.19063976 = sum of:
          0.19063976 = weight(_text_:objects in 4053) [ClassicSimilarity], result of:
            0.19063976 = score(doc=4053,freq=6.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.6102756 = fieldWeight in 4053, product of:
                2.4494898 = tf(freq=6.0), with freq of:
                  6.0 = termFreq=6.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.046875 = fieldNorm(doc=4053)
        0.33333334 = coord(1/3)
      0.12124394 = weight(_text_:digital in 4053) [ClassicSimilarity], result of:
        0.12124394 = score(doc=4053,freq=8.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.52297866 = fieldWeight in 4053, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.046875 = fieldNorm(doc=4053)
      0.06598064 = weight(_text_:library in 4053) [ClassicSimilarity], result of:
        0.06598064 = score(doc=4053,freq=12.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.42695788 = fieldWeight in 4053, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.046875 = fieldNorm(doc=4053)
      0.03470815 = product of:
        0.0694163 = sum of:
          0.0694163 = weight(_text_:project in 4053) [ClassicSimilarity], result of:
            0.0694163 = score(doc=4053,freq=2.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.27981415 = fieldWeight in 4053, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.046875 = fieldNorm(doc=4053)
        0.5 = coord(1/2)
    
    Abstract
    Within a digital library, collections may range from an ad hoc set of objects that serve a temporary purpose to established library collections intended to persist through time. The objects in these collections vary widely, from library and data center holdings to pointers to real-world objects, such as geographic places, and the various metadata schemes that describe them. The key to integrated use of such a variety of collections in a digital library is collection metadata that represents the inherent and contextual characteristics of a collection. The Alexandria Digital Library (ADL) Project has designed and implemented collection metadata for several purposes: in XML form, the collection metadatada 'registers' the collection with the user interface client; in HTML form, it is used for user documentation; eventually, it will be used to describe the collection to network search agents; and it is used for internal collection management, including mapping the object metadata attributes to the common search parameters of the system
  2. Sturmane, A.; Eglite, E.; Jankevica-Balode, M.: Subject metadata development for digital resources in Latvia (2014) 0.27
    0.26919043 = sum of:
      0.042803407 = product of:
        0.12841022 = sum of:
          0.12841022 = weight(_text_:objects in 1963) [ClassicSimilarity], result of:
            0.12841022 = score(doc=1963,freq=2.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.41106653 = fieldWeight in 1963, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0546875 = fieldNorm(doc=1963)
        0.33333334 = coord(1/3)
      0.14145125 = weight(_text_:digital in 1963) [ClassicSimilarity], result of:
        0.14145125 = score(doc=1963,freq=8.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.61014175 = fieldWeight in 1963, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.0546875 = fieldNorm(doc=1963)
      0.04444293 = weight(_text_:library in 1963) [ClassicSimilarity], result of:
        0.04444293 = score(doc=1963,freq=4.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.28758827 = fieldWeight in 1963, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.0546875 = fieldNorm(doc=1963)
      0.04049284 = product of:
        0.08098568 = sum of:
          0.08098568 = weight(_text_:project in 1963) [ClassicSimilarity], result of:
            0.08098568 = score(doc=1963,freq=2.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.32644984 = fieldWeight in 1963, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.0546875 = fieldNorm(doc=1963)
        0.5 = coord(1/2)
    
    Abstract
    The National Library of Latvia (NLL) made a decision to use the Library of Congress Subject Headings (LCSH) in 2000. At present the NLL Subject Headings Database in Latvian holds approximately 34,000 subject headings and is used for subject cataloging of textual resources, including articles from serials. For digital objects NLL uses a system like Faceted Application of Subject Terminology (FAST). We succesfully use it in the project "In Search of Lost Latvia," one of the milestones in the development of the subject cataloging of digital resources in Latvia.
    Footnote
    Contribution in a special issue "Beyond libraries: Subject metadata in the digital environment and Semantic Web" - Enthält Beiträge der gleichnamigen IFLA Satellite Post-Conference, 17-18 August 2012, Tallinn.
  3. Proffitt, M.: Pulling it all together : use of METS in RLG cultural materials service (2004) 0.25
    0.25125772 = sum of:
      0.06918076 = product of:
        0.20754227 = sum of:
          0.20754227 = weight(_text_:objects in 767) [ClassicSimilarity], result of:
            0.20754227 = score(doc=767,freq=4.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.6643839 = fieldWeight in 767, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0625 = fieldNorm(doc=767)
        0.33333334 = coord(1/3)
      0.11430988 = weight(_text_:digital in 767) [ClassicSimilarity], result of:
        0.11430988 = score(doc=767,freq=4.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.493069 = fieldWeight in 767, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.0625 = fieldNorm(doc=767)
      0.03591531 = weight(_text_:library in 767) [ClassicSimilarity], result of:
        0.03591531 = score(doc=767,freq=2.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.23240642 = fieldWeight in 767, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.0625 = fieldNorm(doc=767)
      0.031851757 = product of:
        0.063703515 = sum of:
          0.063703515 = weight(_text_:22 in 767) [ClassicSimilarity], result of:
            0.063703515 = score(doc=767,freq=2.0), product of:
              0.20581327 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.05877307 = queryNorm
              0.30952093 = fieldWeight in 767, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.0625 = fieldNorm(doc=767)
        0.5 = coord(1/2)
    
    Abstract
    RLG has used METS for a particular application, that is as a wrapper for structural metadata. When RLG cultural materials was launched, there was no single way to deal with "complex digital objects". METS provides a standard means of encoding metadata regarding the digital objects represented in RCM, and METS has now been fully integrated into the workflow for this service.
    Source
    Library hi tech. 22(2004) no.1, S.65-68
  4. Hardesty, J.L.; Young, J.B.: ¬The semantics of metadata : Avalon Media System and the move to RDF (2017) 0.24
    0.24498534 = sum of:
      0.036688637 = product of:
        0.11006591 = sum of:
          0.11006591 = weight(_text_:objects in 3896) [ClassicSimilarity], result of:
            0.11006591 = score(doc=3896,freq=2.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.35234275 = fieldWeight in 3896, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.046875 = fieldNorm(doc=3896)
        0.33333334 = coord(1/3)
      0.12124394 = weight(_text_:digital in 3896) [ClassicSimilarity], result of:
        0.12124394 = score(doc=3896,freq=8.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.52297866 = fieldWeight in 3896, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.046875 = fieldNorm(doc=3896)
      0.026936483 = weight(_text_:library in 3896) [ClassicSimilarity], result of:
        0.026936483 = score(doc=3896,freq=2.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.17430481 = fieldWeight in 3896, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.046875 = fieldNorm(doc=3896)
      0.060116284 = product of:
        0.12023257 = sum of:
          0.12023257 = weight(_text_:project in 3896) [ClassicSimilarity], result of:
            0.12023257 = score(doc=3896,freq=6.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.48465237 = fieldWeight in 3896, product of:
                2.4494898 = tf(freq=6.0), with freq of:
                  6.0 = termFreq=6.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.046875 = fieldNorm(doc=3896)
        0.5 = coord(1/2)
    
    Abstract
    The Avalon Media System (Avalon) provides access and management for digital audio and video collections in libraries and archives. The open source project is led by the libraries of Indiana University Bloomington and Northwestern University and is funded in part by grants from The Andrew W. Mellon Foundation and Institute of Museum and Library Services. Avalon is based on the Samvera Community (formerly Hydra Project) software stack and uses Fedora as the digital repository back end. The Avalon project team is in the process of migrating digital repositories from Fedora 3 to Fedora 4 and incorporating metadata statements using the Resource Description Framework (RDF) instead of XML files accompanying the digital objects in the repository. The Avalon team has worked on the migration path for technical metadata and is now working on the migration paths for structural metadata (PCDM) and descriptive metadata (from MODS XML to RDF). This paper covers the decisions made to begin using RDF for software development and offers a window into how Semantic Web technology functions in the real world.
  5. Kurth, M.; Ruddy, D.; Rupp, N.: Repurposing MARC metadata : using digital project experience to develop a metadata management design (2004) 0.22
    0.21923313 = product of:
      0.29231083 = sum of:
        0.12124394 = weight(_text_:digital in 4748) [ClassicSimilarity], result of:
          0.12124394 = score(doc=4748,freq=8.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.52297866 = fieldWeight in 4748, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.046875 = fieldNorm(doc=4748)
        0.053872965 = weight(_text_:library in 4748) [ClassicSimilarity], result of:
          0.053872965 = score(doc=4748,freq=8.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.34860963 = fieldWeight in 4748, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.046875 = fieldNorm(doc=4748)
        0.11719394 = sum of:
          0.0694163 = weight(_text_:project in 4748) [ClassicSimilarity], result of:
            0.0694163 = score(doc=4748,freq=2.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.27981415 = fieldWeight in 4748, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.046875 = fieldNorm(doc=4748)
          0.047777634 = weight(_text_:22 in 4748) [ClassicSimilarity], result of:
            0.047777634 = score(doc=4748,freq=2.0), product of:
              0.20581327 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.05877307 = queryNorm
              0.23214069 = fieldWeight in 4748, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.046875 = fieldNorm(doc=4748)
      0.75 = coord(3/4)
    
    Abstract
    Metadata and information technology staff in libraries that are building digital collections typically extract and manipulate MARC metadata sets to provide access to digital content via non-MARC schemes. Metadata processing in these libraries involves defining the relationships between metadata schemes, moving metadata between schemes, and coordinating the intellectual activity and physical resources required to create and manipulate metadata. Actively managing the non-MARC metadata resources used to build digital collections is something most of these libraries have only begun to do. This article proposes strategies for managing MARC metadata repurposing efforts as the first step in a coordinated approach to library metadata management. Guided by lessons learned from Cornell University library mapping and transformation activities, the authors apply the literature of data resource management to library metadata management and propose a model for managing MARC metadata repurposing processes through the implementation of a metadata management design.
    Source
    Library hi tech. 22(2004) no.2, S.144-152
  6. Ma, Y.-L.; Liu, W.: Digital resources and metadata application in Shanghai Library (2003) 0.22
    0.21835108 = product of:
      0.29113477 = sum of:
        0.1581473 = weight(_text_:digital in 5506) [ClassicSimilarity], result of:
          0.1581473 = score(doc=5506,freq=10.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.6821592 = fieldWeight in 5506, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5506)
        0.062851794 = weight(_text_:library in 5506) [ClassicSimilarity], result of:
          0.062851794 = score(doc=5506,freq=8.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.40671125 = fieldWeight in 5506, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5506)
        0.07013567 = product of:
          0.14027134 = sum of:
            0.14027134 = weight(_text_:project in 5506) [ClassicSimilarity], result of:
              0.14027134 = score(doc=5506,freq=6.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.5654278 = fieldWeight in 5506, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5506)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    The Shanghai Digital Library (SDL) is a component of the China Digital Library Project. This paper introduces the framework, goals, and contents of the China Digital Library Project. The vision, mission, system architecture, digital resources, and related major technology of the SDL project are discussed. Also, the background of the Chinese metadata application and the metadata scheme of the SDL are described, and the features of metadata application in practical cases are analyzed. Finally, current issues of metadata application and their solutions are suggested.
  7. Cantara, L.: METS: the metadata encoding and transmission standard (2005) 0.22
    0.2168132 = product of:
      0.2890843 = sum of:
        0.08203829 = product of:
          0.24611486 = sum of:
            0.24611486 = weight(_text_:objects in 5727) [ClassicSimilarity], result of:
              0.24611486 = score(doc=5727,freq=10.0), product of:
                0.31238306 = queryWeight, product of:
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.05877307 = queryNorm
                0.7878624 = fieldWeight in 5727, product of:
                  3.1622777 = tf(freq=10.0), with freq of:
                    10.0 = termFreq=10.0
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.046875 = fieldNorm(doc=5727)
          0.33333334 = coord(1/3)
        0.16039065 = weight(_text_:digital in 5727) [ClassicSimilarity], result of:
          0.16039065 = score(doc=5727,freq=14.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.6918357 = fieldWeight in 5727, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.046875 = fieldNorm(doc=5727)
        0.04665536 = weight(_text_:library in 5727) [ClassicSimilarity], result of:
          0.04665536 = score(doc=5727,freq=6.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.30190483 = fieldWeight in 5727, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.046875 = fieldNorm(doc=5727)
      0.75 = coord(3/4)
    
    Abstract
    The Metadata Encoding and Transmission Standard (METS) is a data communication standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML Schema Language of the World Wide Web Consortium. An initiative of the Digital Library Federation, METS is under development by an international editorial board and is maintained in the Network Development and MARC Standards Office of the Library of Congress. Designed in conformance with the Open Archival Information System (OAIS) Reference Model, a METS document encapsulates digital objects and metadata as Information Packages for transmitting and/or exchanging digital objects to and from digital repositories, disseminating digital objects via the Web, and archiving digital objects for long-term preservation and access. This paper presents an introduction to the METS standard and through illustrated examples, demonstrates how to build a METS document.
  8. Yee, R.; Beaubien, R.: ¬A preliminary crosswalk from METS to IMS content packaging (2004) 0.21
    0.20816214 = sum of:
      0.051885568 = product of:
        0.1556567 = sum of:
          0.1556567 = weight(_text_:objects in 4752) [ClassicSimilarity], result of:
            0.1556567 = score(doc=4752,freq=4.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.49828792 = fieldWeight in 4752, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.046875 = fieldNorm(doc=4752)
        0.33333334 = coord(1/3)
      0.08573241 = weight(_text_:digital in 4752) [ClassicSimilarity], result of:
        0.08573241 = score(doc=4752,freq=4.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.36980176 = fieldWeight in 4752, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.046875 = fieldNorm(doc=4752)
      0.04665536 = weight(_text_:library in 4752) [ClassicSimilarity], result of:
        0.04665536 = score(doc=4752,freq=6.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.30190483 = fieldWeight in 4752, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.046875 = fieldNorm(doc=4752)
      0.023888817 = product of:
        0.047777634 = sum of:
          0.047777634 = weight(_text_:22 in 4752) [ClassicSimilarity], result of:
            0.047777634 = score(doc=4752,freq=2.0), product of:
              0.20581327 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.05877307 = queryNorm
              0.23214069 = fieldWeight in 4752, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.046875 = fieldNorm(doc=4752)
        0.5 = coord(1/2)
    
    Abstract
    As educational technology becomes pervasive, demand will grow for library content to be incorporated into courseware. Among the barriers impeding interoperability between libraries and educational tools is the difference in specifications commonly used for the exchange of digital objects and metadata. Among libraries, Metadata Encoding and Transmission Standard (METS) is a new but increasingly popular standard; the IMS content-package (IMS-CP) plays a parallel role in educational technology. This article describes how METS-encoded library content can be converted into digital objects for IMS-compliant systems through an XSLT-based crosswalk. The conceptual models behind METS and IMS-CP are compared, the design and limitations of an XSLT-based translation are described, and the crosswalks are related to other techniques to enhance interoperability.
    Source
    Library hi tech. 22(2004) no.1, S.69-81
  9. Brattli, T.: Fagreferentkonferansen 1998 : nettbaserte bibliotektjenester (1998) 0.20
    0.19504894 = product of:
      0.26006526 = sum of:
        0.11430988 = weight(_text_:digital in 3001) [ClassicSimilarity], result of:
          0.11430988 = score(doc=3001,freq=4.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.493069 = fieldWeight in 3001, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.0625 = fieldNorm(doc=3001)
        0.08030908 = weight(_text_:library in 3001) [ClassicSimilarity], result of:
          0.08030908 = score(doc=3001,freq=10.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.51967657 = fieldWeight in 3001, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0625 = fieldNorm(doc=3001)
        0.06544632 = product of:
          0.13089263 = sum of:
            0.13089263 = weight(_text_:project in 3001) [ClassicSimilarity], result of:
              0.13089263 = score(doc=3001,freq=4.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.52762264 = fieldWeight in 3001, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.0625 = fieldNorm(doc=3001)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    Reports on the conference arranged by Tromso University Library in March 1998. O. Husby described BIBSYS Digital Library, a project aimed at collections, coordinated access to external collections, and integration with the BIBSYS database. H. Geleijnse outlined Tilburg University Library's digital document services. L. Longva presented Tromso University Library, and J.E. Roed Oslo University's new library. J. Hakala described the Nordic Metadata Project. Representatives from journal agents, publishers and libraries discussed electronic journals
    Footnote
    Übers. d. Titels: The subject specialists' conference 1998: netbased library services
  10. Rice, R.: Applying DC to institutional data repositories (2008) 0.19
    0.1892238 = product of:
      0.25229838 = sum of:
        0.024459092 = product of:
          0.073377274 = sum of:
            0.073377274 = weight(_text_:objects in 2664) [ClassicSimilarity], result of:
              0.073377274 = score(doc=2664,freq=2.0), product of:
                0.31238306 = queryWeight, product of:
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.05877307 = queryNorm
                0.23489517 = fieldWeight in 2664, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.03125 = fieldNorm(doc=2664)
          0.33333334 = coord(1/3)
        0.05715494 = weight(_text_:digital in 2664) [ClassicSimilarity], result of:
          0.05715494 = score(doc=2664,freq=4.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.2465345 = fieldWeight in 2664, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.03125 = fieldNorm(doc=2664)
        0.17068435 = sum of:
          0.1388326 = weight(_text_:project in 2664) [ClassicSimilarity], result of:
            0.1388326 = score(doc=2664,freq=18.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.5596283 = fieldWeight in 2664, product of:
                4.2426405 = tf(freq=18.0), with freq of:
                  18.0 = termFreq=18.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.03125 = fieldNorm(doc=2664)
          0.031851757 = weight(_text_:22 in 2664) [ClassicSimilarity], result of:
            0.031851757 = score(doc=2664,freq=2.0), product of:
              0.20581327 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.05877307 = queryNorm
              0.15476047 = fieldWeight in 2664, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.03125 = fieldNorm(doc=2664)
      0.75 = coord(3/4)
    
    Abstract
    DISC-UK DataShare (2007-2009), a project led by the University of Edinburgh and funded by JISC (Joint Information Systems Committee, UK), arises from an existing consortium of academic data support professionals working in the domain of social science datasets (Data Information Specialists Committee-UK). We are working together across four universities with colleagues engaged in managing open access repositories for e-prints. Our project supports 'early adopter' academics who wish to openly share datasets and presents a model for depositing 'orphaned datasets' that are not being deposited in subject-domain data archives/centres. Outputs from the project are intended to help to demystify data as complex objects in repositories, and assist other institutional repository managers in overcoming barriers to incorporating research data. By building on lessons learned from recent JISC-funded data repository projects such as SToRe and GRADE the project will help realize the vision of the Digital Repositories Roadmap, e.g. the milestone under Data, "Institutions need to invest in research data repositories" (Heery and Powell, 2006). Application of appropriate metadata is an important area of development for the project. Datasets are not different from other digital materials in that they need to be described, not just for discovery but also for preservation and re-use. The GRADE project found that for geo-spatial datasets, Dublin Core metadata (with geo-spatial enhancements such as a bounding box for the 'coverage' property) was sufficient for discovery within a DSpace repository, though more indepth metadata or documentation was required for re-use after downloading. The project partners are examining other metadata schemas such as the Data Documentation Initiative (DDI) versions 2 and 3, used primarily by social science data archives (Martinez, 2008). Crosswalks from the DDI to qualified Dublin Core are important for describing research datasets at the study level (as opposed to the variable level which is largely out of scope for this project). DataShare is benefiting from work of of the DRIADE project (application profile development for evolutionary biology) (Carrier, et al, 2007), eBank UK (developed an application profile for crystallography data) and GAP (Geospatial Application Profile, in progress) in defining interoperable Dublin Core qualified metadata elements and their application to datasets for each partner repository. The solution devised at Edinburgh for DSpace will be covered in the poster.
    Source
    Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas
  11. METS: an overview & tutorial : Metadata Encoding & Transmission Standard (METS) (2001) 0.19
    0.18575415 = product of:
      0.2476722 = sum of:
        0.051885568 = product of:
          0.1556567 = sum of:
            0.1556567 = weight(_text_:objects in 1323) [ClassicSimilarity], result of:
              0.1556567 = score(doc=1323,freq=4.0), product of:
                0.31238306 = queryWeight, product of:
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.05877307 = queryNorm
                0.49828792 = fieldWeight in 1323, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.046875 = fieldNorm(doc=1323)
          0.33333334 = coord(1/3)
        0.13555482 = weight(_text_:digital in 1323) [ClassicSimilarity], result of:
          0.13555482 = score(doc=1323,freq=10.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.58470786 = fieldWeight in 1323, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.046875 = fieldNorm(doc=1323)
        0.060231805 = weight(_text_:library in 1323) [ClassicSimilarity], result of:
          0.060231805 = score(doc=1323,freq=10.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.38975742 = fieldWeight in 1323, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.046875 = fieldNorm(doc=1323)
      0.75 = coord(3/4)
    
    Abstract
    Maintaining a library of digital objects of necessaryy requires maintaining metadata about those objects. The metadata necessary for successful management and use of digital objeets is both more extensive than and different from the metadata used for managing collections of printed works and other physical materials. While a library may record descriptive metadata regarding a book in its collection, the book will not dissolve into a series of unconnected pages if the library fails to record structural metadata regarding the book's organization, nor will scholars be unable to evaluate the book's worth if the library fails to note that the book was produced using a Ryobi offset press. The Same cannot be said for a digital version of the saure book. Without structural metadata, the page image or text files comprising the digital work are of little use, and without technical metadata regarding the digitization process, scholars may be unsure of how accurate a reflection of the original the digital version provides. For internal management purposes, a library must have access to appropriate technical metadata in order to periodically refresh and migrate the data, ensuring the durability of valuable resources.
  12. Bartczak, J.; Glendon, I.: Python, Google Sheets, and the Thesaurus for Graphic Materials for efficient metadata project workflows (2017) 0.18
    0.18406567 = sum of:
      0.036688637 = product of:
        0.11006591 = sum of:
          0.11006591 = weight(_text_:objects in 3893) [ClassicSimilarity], result of:
            0.11006591 = score(doc=3893,freq=2.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.35234275 = fieldWeight in 3893, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.046875 = fieldNorm(doc=3893)
        0.33333334 = coord(1/3)
      0.08573241 = weight(_text_:digital in 3893) [ClassicSimilarity], result of:
        0.08573241 = score(doc=3893,freq=4.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.36980176 = fieldWeight in 3893, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.046875 = fieldNorm(doc=3893)
      0.026936483 = weight(_text_:library in 3893) [ClassicSimilarity], result of:
        0.026936483 = score(doc=3893,freq=2.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.17430481 = fieldWeight in 3893, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.046875 = fieldNorm(doc=3893)
      0.03470815 = product of:
        0.0694163 = sum of:
          0.0694163 = weight(_text_:project in 3893) [ClassicSimilarity], result of:
            0.0694163 = score(doc=3893,freq=2.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.27981415 = fieldWeight in 3893, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.046875 = fieldNorm(doc=3893)
        0.5 = coord(1/2)
    
    Abstract
    In 2017, the University of Virginia (U.Va.) will launch a two year initiative to celebrate the bicentennial anniversary of the University's founding in 1819. The U.Va. Library is participating in this event by digitizing some 20,000 photographs and negatives that document student life on the U.Va. grounds in the 1960s and 1970s. Metadata librarians and archivists are well-versed in the challenges associated with generating digital content and accompanying description within the context of limited resources. This paper describes how technology and new approaches to metadata design have enabled the University of Virginia's Metadata Analysis and Design Department to rapidly and successfully generate accurate description for these digital objects. Python's pandas module improves efficiency by cleaning and repurposing data recorded at digitization, while the lxml module builds MODS XML programmatically from CSV tables. A simplified technique for subject heading selection and assignment in Google Sheets provides a collaborative environment for streamlined metadata creation and data quality control.
  13. Lubas, R.L.; Wolfe, R.H.W.; Fleischman, M.: Creating metadata practices for MIT's OpenCourseWare Project (2004) 0.18
    0.1833757 = product of:
      0.24450094 = sum of:
        0.042803407 = product of:
          0.12841022 = sum of:
            0.12841022 = weight(_text_:objects in 2843) [ClassicSimilarity], result of:
              0.12841022 = score(doc=2843,freq=2.0), product of:
                0.31238306 = queryWeight, product of:
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.05877307 = queryNorm
                0.41106653 = fieldWeight in 2843, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  5.315071 = idf(docFreq=590, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=2843)
          0.33333334 = coord(1/3)
        0.031425897 = weight(_text_:library in 2843) [ClassicSimilarity], result of:
          0.031425897 = score(doc=2843,freq=2.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.20335563 = fieldWeight in 2843, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2843)
        0.17027164 = sum of:
          0.114531055 = weight(_text_:project in 2843) [ClassicSimilarity], result of:
            0.114531055 = score(doc=2843,freq=4.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.4616698 = fieldWeight in 2843, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.0546875 = fieldNorm(doc=2843)
          0.055740576 = weight(_text_:22 in 2843) [ClassicSimilarity], result of:
            0.055740576 = score(doc=2843,freq=2.0), product of:
              0.20581327 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.05877307 = queryNorm
              0.2708308 = fieldWeight in 2843, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.0546875 = fieldNorm(doc=2843)
      0.75 = coord(3/4)
    
    Abstract
    The MIT libraries were called upon to recommend a metadata scheme for the resources contained in MIT's OpenCourseWare (OCW) project. The resources in OCW needed descriptive, structural, and technical metadata. The SCORM standard, which uses IEEE Learning Object Metadata for its descriptive standard, was selected for its focus on educational objects. However, it was clear that the Libraries would need to recommend how the standard would be applied and adapted to accommodate needs that were not addressed in the standard's specifications. The newly formed MIT Libraries Metadata Unit adapted established practices from AACR2 and MARC traditions when facing situations in which there were no precedents to follow.
    Source
    Library hi tech. 22(2004) no.2, S.138-143
  14. Jizba, L.; Hillmann, D.I.: Insights from Ithaca : an interview with Diane Hillmann on metadata, Dublin Core, the National Science Digital Library, and more (2004/05) 0.17
    0.17284538 = product of:
      0.23046051 = sum of:
        0.1581473 = weight(_text_:digital in 637) [ClassicSimilarity], result of:
          0.1581473 = score(doc=637,freq=10.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.6821592 = fieldWeight in 637, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.0546875 = fieldNorm(doc=637)
        0.04444293 = weight(_text_:library in 637) [ClassicSimilarity], result of:
          0.04444293 = score(doc=637,freq=4.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.28758827 = fieldWeight in 637, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0546875 = fieldNorm(doc=637)
        0.027870288 = product of:
          0.055740576 = sum of:
            0.055740576 = weight(_text_:22 in 637) [ClassicSimilarity], result of:
              0.055740576 = score(doc=637,freq=2.0), product of:
                0.20581327 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.05877307 = queryNorm
                0.2708308 = fieldWeight in 637, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=637)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    In an interview, Diane I. Hillmann, an expert in metadata for digital libraries and currently co-principal investigator for the National Science Digital Library Registry based at Cornell University, discusses her education and career, and provides overviews and insights on metadata initiatives, including standards and models such as the widely adopted Dublin Core schema. She shares her professional interests from the early part of her career with communications, cataloging, and database production services; highlights key issues; and provides ideas and resources for managing changes in metadata standards and digital projects.
    Date
    2.12.2007 19:35:22
    Footnote
    Beitrag eines Themenheftes "Profiles in digital information"
  15. Lynch, J.D.; Gibson, J.; Han, M.-J.: Analyzing and normalizing type metadata for a large aggregated digital library (2020) 0.17
    0.16815662 = product of:
      0.22420883 = sum of:
        0.12250038 = weight(_text_:digital in 5720) [ClassicSimilarity], result of:
          0.12250038 = score(doc=5720,freq=6.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.5283983 = fieldWeight in 5720, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5720)
        0.04444293 = weight(_text_:library in 5720) [ClassicSimilarity], result of:
          0.04444293 = score(doc=5720,freq=4.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.28758827 = fieldWeight in 5720, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5720)
        0.057265528 = product of:
          0.114531055 = sum of:
            0.114531055 = weight(_text_:project in 5720) [ClassicSimilarity], result of:
              0.114531055 = score(doc=5720,freq=4.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.4616698 = fieldWeight in 5720, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5720)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    The Illinois Digital Heritage Hub (IDHH) gathers and enhances metadata from contributing institutions around the state of Illinois and provides this metadata to th Digital Public Library of America (DPLA) for greater access. The IDHH helps contributors shape their metadata to the standards recommended and required by the DPLA in part by analyzing and enhancing aggregated metadata. In late 2018, the IDHH undertook a project to address a particularly problematic field, Type metadata. This paper walks through the project, detailing the process of gathering and analyzing metadata using the DPLA API and OpenRefine, data remediation through XSL transformations in conjunction with local improvements by contributing institutions, and the DPLA ingestion system's quality controls.
  16. Intner, S.S.; Lazinger, S.S.; Weihs, J.: Metadata and its impact on libraries (2005) 0.17
    0.1664035 = sum of:
      0.012229546 = product of:
        0.036688637 = sum of:
          0.036688637 = weight(_text_:objects in 339) [ClassicSimilarity], result of:
            0.036688637 = score(doc=339,freq=2.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.117447585 = fieldWeight in 339, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.015625 = fieldNorm(doc=339)
        0.33333334 = coord(1/3)
      0.10303753 = weight(_text_:digital in 339) [ClassicSimilarity], result of:
        0.10303753 = score(doc=339,freq=52.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.44444638 = fieldWeight in 339, product of:
            7.2111025 = tf(freq=52.0), with freq of:
              52.0 = termFreq=52.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.015625 = fieldNorm(doc=339)
      0.03477485 = weight(_text_:library in 339) [ClassicSimilarity], result of:
        0.03477485 = score(doc=339,freq=30.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.22502656 = fieldWeight in 339, product of:
            5.477226 = tf(freq=30.0), with freq of:
              30.0 = termFreq=30.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.015625 = fieldNorm(doc=339)
      0.01636158 = product of:
        0.03272316 = sum of:
          0.03272316 = weight(_text_:project in 339) [ClassicSimilarity], result of:
            0.03272316 = score(doc=339,freq=4.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.13190566 = fieldWeight in 339, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.015625 = fieldNorm(doc=339)
        0.5 = coord(1/2)
    
    Content
    What is metadata? - Metadata schemas & their relationships to particular communities - Library and information-related metadata schemas - Creating library metadata for monographic materials - Creating library metadata for continuing materials - Integrating library metadata into local cataloging and bibliographic - databases - Digital collections/digital libraries - Archiving & preserving digital materials - Impact of digital resources on library services - Future possibilities
    Footnote
    Rez. in: JASIST. 58(2007) no.6., S.909-910 (A.D. Petrou): "A division in metadata definitions for physical objects vs. those for digital resources offered in Chapter 1 is punctuated by the use of broader, more inclusive metadata definitions, such as data about data as well as with the inclusion of more specific metadata definitions intended for networked resources. Intertwined with the book's subject matter, which is to "distinguish traditional cataloguing from metadata activity" (5), the authors' chosen metadata definition is also detailed on page 5 as follows: Thus while granting the validity of the inclusive definition, we concentrate primarily on metadata as it is most commonly thought of both inside and outside of the library community, as "structured information used to find, access, use and manage information resources primarily in a digital environment." (International Encyclopedia of Information and Library Science, 2003) Metadata principles discussed by the authors include modularity, extensibility, refinement and multilingualism. The latter set is followed by seven misconceptions about metadata. Two types of metadata discussed are automatically generated indexes and manually created records. In terms of categories of metadata, the authors present three sets of them as follows: descriptive, structural, and administrative metadata. Chapter 2 focuses on metadata for communities of practice, and is a prelude to content in Chapter 3 where metadata applications, use, and development are presented from the perspective of libraries. Chapter 2 discusses the emergence and impact of metadata on organization and access of online resources from the perspective of communities for which such standards exist and for the need for mapping one standard to another. Discussion focuses on metalanguages, such as Standard Generalized Markup Language (SGML) and eXtensible Markup Language (XML), "capable of embedding descriptive elements within the document markup itself' (25). This discussion falls under syntactic interoperability. For semantic interoperability, HTML and other mark-up languages, such as Text Encoding Initiative (TEI) and Computer Interchange of Museum Information (CIMI), are covered. For structural interoperability, Dublin Core's 15 metadata elements are grouped into three areas: content (title, subject, description, type, source, relation, and coverage), intellectual property (creator, publisher, contributor and rights), and instantiation (date, format, identifier, and language) for discussion.
    Other selected specialized metadata element sets or schemas, such as Government Information Locator Service (GILS), are presented. Attention is brought to the different sets of elements and the need for linking up these elements across metadata schemes from a semantic point of view. It is no surprise, then, that after the presentation of additional specialized sets of metadata from the educational community and the arts sector, attention is turned to the discussion of Crosswalks between metadata element sets or the mapping of one metadata standard to another. Finally, the five appendices detailing elements found in Dublin Core, GILS, ARIADNE versions 3 and 3. 1, and Categories for the Description of Works of Art are an excellent addition to this chapter's focus on metadata and communities of practice. Chapters 3-6 provide an up-to-date account of the use of metadata standards in Libraries from the point of view of a community of practice. Some of the content standards included in these four chapters are AACR2, Dewey Decimal Classification (DDC), and Library of Congress Subject Classification. In addition, uses of MARC along with planned implementations of the archival community's encoding scheme, EAD, are covered in detail. In a way, content in these chapters can be considered as a refresher course on the history, current state, importance, and usefulness of the above-mentioned standards in Libraries. Application of the standards is offered for various types of materials, such as monographic materials, continuing resources, and integrating library metadata into local catalogs and databases. A review of current digital library projects takes place in Chapter 7. While details about these projects tend to become out of date fast, the sections on issues and problems encountered in digital projects and successes and failures deserve any reader's close inspection. A suggested model is important enough to merit a specific mention below, in a short list format, as it encapsulates lessons learned from issues, problems, successes, and failures in digital projects. Before detailing the model, however, the various projects included in Chapter 7 should be mentioned. The projects are: Colorado Digitization Project, Cooperative Online Resource Catalog (an Office of Research project by OCLC, Inc.), California Digital Library, JSTOR, LC's National Digital Library Program and VARIATIONS.
    Chapter 8 discusses issues of archiving and preserving digital materials. The chapter reiterates, "What is the point of all of this if the resources identified and catalogued are not preserved?" (Gorman, 2003, p. 16). Discussion about preservation and related issues is organized in five sections that successively ask why, what, who, how, and how much of the plethora of digital materials should be archived and preserved. These are not easy questions because of media instability and technological obsolescence. Stakeholders in communities with diverse interests compete in terms of which community or representative of a community has an authoritative say in what and how much get archived and preserved. In discussing the above-mentioned questions, the authors once again provide valuable information and lessons from a number of initiatives in Europe, Australia, and from other global initiatives. The Draft Charter on the Preservation of the Digital Heritage and the Guidelines for the Preservation of Digital Heritage, both published by UNESCO, are discussed and some of the preservation principles from the Guidelines are listed. The existing diversity in administrative arrangements for these new projects and resources notwithstanding, the impact on content produced for online reserves through work done in digital projects and from the use of metadata and the impact on levels of reference services and the ensuing need for different models to train users and staff is undeniable. In terms of education and training, formal coursework, continuing education, and informal and on-the-job training are just some of the available options. The intensity in resources required for cataloguing digital materials, the questions over the quality of digital resources, and the threat of the new digital environment to the survival of the traditional library are all issues quoted by critics and others, however, who are concerned about a balance for planning and resources allocated for traditional or print-based resources and newer digital resources. A number of questions are asked as part of the book's conclusions in Chapter 10. Of these questions, one that touches on all of the rest and upon much of the book's content is the question: What does the future hold for metadata in libraries? Metadata standards are alive and well in many communities of practice, as Chapters 2-6 have demonstrated. The usefulness of metadata continues to be high and innovation in various elements should keep information professionals engaged for decades to come. There is no doubt that metadata have had a tremendous impact in how we organize information for access and in terms of who, how, when, and where contact is made with library services and collections online. Planning and commitment to a diversity of metadata to serve the plethora of needs in communities of practice are paramount for the continued success of many digital projects and for online preservation of our digital heritage."
    LCSH
    Digital preservation
    Digital libraries
    Series
    Library and information science text series
    Subject
    Digital preservation
    Digital libraries
  17. Hunter, J.: MetaNet - a metadata term thesaurus to enable semantic interoperability between metadata domains (2001) 0.15
    0.15338805 = sum of:
      0.030573865 = product of:
        0.091721594 = sum of:
          0.091721594 = weight(_text_:objects in 6471) [ClassicSimilarity], result of:
            0.091721594 = score(doc=6471,freq=2.0), product of:
              0.31238306 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.05877307 = queryNorm
              0.29361898 = fieldWeight in 6471, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0390625 = fieldNorm(doc=6471)
        0.33333334 = coord(1/3)
      0.07144367 = weight(_text_:digital in 6471) [ClassicSimilarity], result of:
        0.07144367 = score(doc=6471,freq=4.0), product of:
          0.23183343 = queryWeight, product of:
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.05877307 = queryNorm
          0.3081681 = fieldWeight in 6471, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.944552 = idf(docFreq=2326, maxDocs=44218)
            0.0390625 = fieldNorm(doc=6471)
      0.022447068 = weight(_text_:library in 6471) [ClassicSimilarity], result of:
        0.022447068 = score(doc=6471,freq=2.0), product of:
          0.15453665 = queryWeight, product of:
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.05877307 = queryNorm
          0.14525402 = fieldWeight in 6471, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.6293786 = idf(docFreq=8668, maxDocs=44218)
            0.0390625 = fieldNorm(doc=6471)
      0.028923457 = product of:
        0.057846915 = sum of:
          0.057846915 = weight(_text_:project in 6471) [ClassicSimilarity], result of:
            0.057846915 = score(doc=6471,freq=2.0), product of:
              0.24808002 = queryWeight, product of:
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.05877307 = queryNorm
              0.23317845 = fieldWeight in 6471, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                4.220981 = idf(docFreq=1764, maxDocs=44218)
                0.0390625 = fieldNorm(doc=6471)
        0.5 = coord(1/2)
    
    Abstract
    Metadata interoperability is a fundamental requirement for access to information within networked knowledge organization systems. The Harmony international digital library project [1] has developed a common underlying data model (the ABC model) to enable the scalable mapping of metadata descriptions across domains and media types. The ABC model [2] provides a set of basic building blocks for metadata modeling and recognizes the importance of 'events' to describe unambiguously metadata for objects with a complex history. To test and evaluate the interoperability capabilities of this model, we applied it to some real multimedia examples and analysed the results of mapping from the ABC model to various different metadata domains using XSLT [3]. This work revealed serious limitations in the ability of XSLT to support flexible dynamic semantic mapping. To overcome this, we developed MetaNet [4], a metadata term thesaurus which provides the additional semantic knowledge that is non-existent within declarative XML-encoded metadata descriptions. This paper describes MetaNet, its RDF Schema [5] representation and a hybrid mapping approach which combines the structural and syntactic mapping capabilities of XSLT with the semantic knowledge of MetaNet, to enable flexible and dynamic mapping among metadata standards.
    Source
    Journal of digital information. 1(2001) no.8, art.# 42
  18. Hagedorn, K.: OAIster: a "no dead ends" OAI service provider (2003) 0.15
    0.15195559 = product of:
      0.20260745 = sum of:
        0.12124394 = weight(_text_:digital in 4776) [ClassicSimilarity], result of:
          0.12124394 = score(doc=4776,freq=8.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.52297866 = fieldWeight in 4776, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.046875 = fieldNorm(doc=4776)
        0.04665536 = weight(_text_:library in 4776) [ClassicSimilarity], result of:
          0.04665536 = score(doc=4776,freq=6.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.30190483 = fieldWeight in 4776, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.046875 = fieldNorm(doc=4776)
        0.03470815 = product of:
          0.0694163 = sum of:
            0.0694163 = weight(_text_:project in 4776) [ClassicSimilarity], result of:
              0.0694163 = score(doc=4776,freq=2.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.27981415 = fieldWeight in 4776, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4776)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    OAIster, at the University of Michigan, University Libraries, Digital Library Production Service (DLPS), is an Andrew W. Mellon Foundation grant-funded project designed to test the feasibility of using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) to harvest digital object metadata from multiple and varied digital object repositories and develop a service to allow end-users to access that metadata. This article describes in-depth the development of our system to harvest, store, transform the metadata into Digital Library eXtension Service (DLXS) Bibliographic Class format, build indexes and make the metadata searchable through an interface using the XPAT search engine. Results of the testing of our service and statistics on usage are reported, as well as the issues that we have encountered during our harvesting and transformation operations. The article closes by discussing the future improvements and potential of OAIster and the OAI-PMH protocol.
    Source
    Library hi tech. 21(2003) no.2, S.170-181
  19. Shreeves, S.L.; Kaczmarek, J.S.; Cole, T.W.: Harvesting cultural heritage metadata using OAI Protocol (2003) 0.15
    0.15135306 = product of:
      0.20180407 = sum of:
        0.08573241 = weight(_text_:digital in 4775) [ClassicSimilarity], result of:
          0.08573241 = score(doc=4775,freq=4.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.36980176 = fieldWeight in 4775, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.046875 = fieldNorm(doc=4775)
        0.04665536 = weight(_text_:library in 4775) [ClassicSimilarity], result of:
          0.04665536 = score(doc=4775,freq=6.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.30190483 = fieldWeight in 4775, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.046875 = fieldNorm(doc=4775)
        0.0694163 = product of:
          0.1388326 = sum of:
            0.1388326 = weight(_text_:project in 4775) [ClassicSimilarity], result of:
              0.1388326 = score(doc=4775,freq=8.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.5596283 = fieldWeight in 4775, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4775)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    In July of 2001, with funding from the Andrew W. Mellon Foundation, the University of Illinois at Urbana-Champaign undertook a project to test the efficacy of using the Open Archives Initiative Protocol for Metadata Harvesting to construct a search and discovery service focused on information resources in the domain of cultural heritage. To date, the Illinois project has indexed over two million Dublin Core metadata records contributed by 39 metadata repositories in the museum, academic library, and digital library project communities. These records describe a mix of digital and analog primary content. Our analysis of these metadata records demonstrates wide divergence in descriptive metadata practices and the use and interpretation of Dublin Core metadata elements. Differences are particularly notable by community. This article provides an overview of the Illinois project, presents quantitative data about divergent metadata practices and element usage patterns, and details implications for metadata providers and harvesting services.
    Source
    Library hi tech. 21(2003) no.2, S.159-161
  20. Stevens, G.: New metadata recipes for old cookbooks : creating and analyzing a digital collection using the HathiTrust Research Center Portal (2017) 0.15
    0.14610317 = product of:
      0.19480422 = sum of:
        0.112962365 = weight(_text_:digital in 3897) [ClassicSimilarity], result of:
          0.112962365 = score(doc=3897,freq=10.0), product of:
            0.23183343 = queryWeight, product of:
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.05877307 = queryNorm
            0.4872566 = fieldWeight in 3897, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.944552 = idf(docFreq=2326, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3897)
        0.03174495 = weight(_text_:library in 3897) [ClassicSimilarity], result of:
          0.03174495 = score(doc=3897,freq=4.0), product of:
            0.15453665 = queryWeight, product of:
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.05877307 = queryNorm
            0.2054202 = fieldWeight in 3897, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.6293786 = idf(docFreq=8668, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3897)
        0.050096903 = product of:
          0.100193806 = sum of:
            0.100193806 = weight(_text_:project in 3897) [ClassicSimilarity], result of:
              0.100193806 = score(doc=3897,freq=6.0), product of:
                0.24808002 = queryWeight, product of:
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.05877307 = queryNorm
                0.40387696 = fieldWeight in 3897, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  4.220981 = idf(docFreq=1764, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=3897)
          0.5 = coord(1/2)
      0.75 = coord(3/4)
    
    Abstract
    The Early American Cookbooks digital project is a case study in analyzing collections as data using HathiTrust and the HathiTrust Research Center (HTRC) Portal. The purposes of the project are to create a freely available, searchable collection of full-text early American cookbooks within the HathiTrust Digital Library, to offer an overview of the scope and contents of the collection, and to analyze trends and patterns in the metadata and the full text of the collection. The digital project has two basic components: a collection of 1450 full-text cookbooks published in the United States between 1800 and 1920 and a website to present a guide to the collection and the results of the analysis. This article will focus on the workflow for analyzing the metadata and the full-text of the collection. The workflow will cover: 1) creating a searchable public collection of full-text titles within the HathiTrust Digital Library and uploading it to the HTRC Portal, 2) analyzing and visualizing legacy MARC data for the collection using MarcEdit, OpenRefine and Tableau, and 3) using the text analysis tools in the HTRC Portal to look for trends and patterns in the full text of the collection.

Years

Languages

Types

  • a 327
  • el 53
  • m 22
  • s 16
  • b 2
  • x 2
  • r 1
  • More… Less…

Subjects