Your SlideShare is downloading. ×

library Metadata


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 2. METADATA  The term "meta" comes from a Greek word that denotes something of a higher or more fundamental nature. Metadata, then, is data about other data.  The term refers to any data used to aid the identification, description and location of networked electronic resources
  • 3. DEFINING METADATA  Does data about data mean anything?  Librarians equate it with a complete bibliographic record  Information technologists equate it to database schema or definitions of the data elements  Archivists include context information, restrictions and access terms, index terms, etc.
  • 4. WHY METADATA?  Hardware and software come and go—sometimes becoming obsolete with alarming rapidity—but high- quality, standards-based, system-independent metadata can be used, reused, migrated, and disseminated in any number of ways, even in ways that we cannot anticipate at this moment.  Digitization does not equal access. The mere act of creating digital copies of collection materials does not make those materials findable, understandable, or utilizable to our ever-expanding audience of online users. But digitization combined with the creation of carefully crafted metadata can significantly enhance end-user access; and our users are the primary reason that we create digital resources.”
  • 5. BIBLIOGRAPHIC METADATA  Providing a description of the information package along with other information necessary for management and preservation  Encoding  Providing access to this description
  • 6. ENCODING  Surrogate records are encoded by assigning tags, letter, or words  Why encode?  For display  Provide access  Integration of surrogate  Management
  • 7. DIFFERENT COMMUNITIES ….DIFFERENT METADATA  Developers of the Interoperabilty of Data in E- Commerce Systems (indecs) ideintified metadata for protecting intellectual property rights of creators and publishers.  The Research Library Group’s Working Group on Preservation Issues of Metadata identified metadata for “digital master files that have preservation- based intent”.
  • 8. METADATA TO INFORMATION TECHNOLOGISTS  The data that defines the data elements in a table  Data that controls or explains other data  Something that is not part of the bit stream of a record but needed to understand the data in the record  One systems metadata is another systems data
  • 9. SOURCE OF METADATA  Automatically generated  Supplied by creator of electronic resource  Supplied by 3rd party
  • 10. DUBLIN CORE  Metadata to improve information retrieval of internet resources  Developed predominantly by the bibliographic community. Elements similar to bibliographic surrogate
  • 11. CHARACTERISTICS OF DUBLIN CORE  Simplicity  Semantic Interoperability  International Consensus  Extensibility  Metadata Modularity on the Web
  • 12. DUBLIN CORE ELEMENTS  Content  Coverage  Description  Type  Relation  Source  Subject  Title  Intellectual Property   Contributor  Creator  Publisher  Rights
  • 13. DUBLIN CORE ELEMENT  Instantiation  Date  Format  Identifier  Language
  • 14. METADATA AND XML  Provides a means of encoding and exchanging metadata  EAD, TEI, VERS
  • 15. XML EXAMPLE  <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!DOCTYPE FAQ SYSTEM "FAQ.DTD"> <FAQ>  <INFO> <SUBJECT> XML </SUBJECT>  <AUTHOR> Lars Marius Garshol</AUTHOR>  <EMAIL> </EMAIL> <VERSION> 1.0 </VERSION>  <DATE> 20.jun.97 </DATE>  </INFO> <PART NO="1"> <Q NO="1"> <QTEXT>What is XML?</QTEXT> <A>SGML light.</A> </Q> ...</PART> </FAQ>
  • 16. ELECTRONIC RECORDS METADATA PROJECT  Functional Requirements for Evidence in Recordkeeping  The SPIRT Metadata Project  VERS  GILS - and the AGLS  OAIS  InterPares
  • 18. OPEN ARCHIVAL INFORMATION SYSTEMS Figure 4-12: Information Object Taxonomy Information Object Content Information Packaging Information Preservation Description Information Descriptive Information . . .
  • 19. PRESERVATION DESCRIPTION Preservation Description Information Reference Information Provenance Information Context Information Fixity Information
  • 20. TABLE 4-1: EXAMPLES OF PDI TYPES Content Information Type Reference Provenance Context Fixity Space Science Data Object identifier Journal reference Mission, instrument, title, attribute set Instrument description Processing history Sensor description Instrument Instrument mode Decommutation map Software interface specification Calibration history Related data sets Mission Funding history CRC Checksum Reed-Solomon coding Digital Library Collections Bibliographic description Persistent identifier For scanned collections: metadata about the digitisation process pointer to master version For born-digital publications: pointer to the digital original Metadata about the preservation process: pointers to earlier versions of the collection item change history Pointers to related documents in original environment at the time of publication Digital signature Checksum Authenticity indicator Software Package Name Author/Originator Version number Serial number Revision history License holder Registration Copyright Help file User guide Related software Language Certificate Checksum Encryption CRC
  • 21. records data files current technical context provenance original technical context form and structure activities Strategy, methods requirements, rules simplified datamodel INTERPARES PRESERVATION MODEL
  • 22. METADATA FORMATS  Extensible Markup Language (XML)  Allows for combining and interoperability  XML flexibility  Any other conceivable format  MS Word? PDF? Post-it notes?  Excel, FileMaker Pro, Access DB, CSV
  • 23. DEVELOPING METADATA SCHEMES  Identify the purpose of the metadata model  Level of specificity of the elements  Identify resources  Infrastructure - who will supply it?  What type of information package is it?  Who will use the metadata?  Existing metadata models