DOCSLIB.ORG

Mets> Metadata Encoding and Transmission Standard: Primer and Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mets> Metadata Encoding and Transmission Standard: Primer and Reference Manual <METS> METADATA ENCODING AND TRANSMISSION STANDARD: PRIMER AND REFERENCE MANUAL Version 1.6 Revised 2010 To the extent possible under law, Digital Library Federation has waived all copyright and related or neighboring rights to METS Primer. This work is published from: United States. - 1 - Table of Contents FOREWORD ................................................................... 10 How to use this publication .................................................... 10 Before there is a METS document......................................... 11 CHAPTER 1: INTRODUCTION AND BACKGROUND .. 15 What is METS?....................................................................... 15 What problem is METS trying to solve? .............................. 15 How is METS maintained? .................................................... 16 What is METS built upon? .................................................... 16 Who is the METS community?.............................................. 16 How can I find out more about METS? ................................ 17 CHAPTER 2: AUTHORING A METS DOCUMENT ........ 18 Structural Map and File Section ............................................ 18 Descriptive Metadata Section ................................................ 21 Administrative Metadata Section .......................................... 22 Technical Metadata ................................................................ 22 - 2 - Conclusion ............................................................................... 24 CHAPTER 3: FROM THE SCHEMA PERSPECTIVE .... 25 <mets> METS root element .................................................. 26 Attributes of the METS root element .................................... 26 Elements contained in the root element ................................ 27 METS root element example ................................................ 27 <metsHdr> METS Header .................................................... 29 Attributes of the METS header ............................................. 29 Elements contained in the METS header .............................. 29 Agent ................................................................................ 30 Agent – attributes .............................................................. 30 Agent – elements .............................................................. 30 Agent – example ............................................................... 30 Alternative identifiers ....................................................... 31 Alternative identifiers – attributes .................................... 31 Alternative identifiers – examples .................................... 31 METS header example ......................................................... 31 <dmdSec> Descriptive metadata ........................................... 33 Attributes of the descriptive metadata section ...................... 33 Descriptive metadata elements ............................................. 34 Metadata reference ........................................................... 34 Metadata reference – attributes ......................................... 34 - 3 - Metadata reference– example ........................................... 35 Metadata wrapper ............................................................. 35 Internal descriptive metadata – attributes ......................... 36 Internal descriptive metadata – elements .......................... 36 Internal descriptive metadata – example ........................... 37 <amdSec> Administrative metadata ..................................... 39 Attributes of the administrative metadata section ................. 40 Elements contained in the administrative metadata section .. 40 Attributes shared by the administrative metadata elements .......................................................................................... 40 Technical metadata ........................................................... 41 Technical metadata – example .......................................... 41 Intellectual property rights metadata................................. 41 Intellectual property rights metadata – example ............... 42 Source metadata ................................................................ 42 Source metadata – example .............................................. 42 Digital provenance metadata ............................................ 43 Digital provenance metadata – example 1: ....................... 44 Digital provenance metadata – example 2 ........................ 45 Complete administrative metadata – example ...................... 45 <file> File section .................................................................... 46 Attributes of the file section ................................................. 47 Elements Contained in the File Section ................................ 47 - 4 - File group ......................................................................... 47 File group – attributes ....................................................... 47 File group – example ........................................................ 48 File (element) .................................................................... 48 File (element) – Attributes ................................................ 48 File (element) – example .................................................. 49 File location ...................................................................... 49 File location – attributes ................................................... 50 File Location – example ................................................... 50 File content ....................................................................... 51 File content – attributes .................................................... 51 File content – example ...................................................... 52 Component byte stream .................................................... 52 Component byte stream – attributes ................................. 52 Component byte stream – example ................................... 52 Transform file ................................................................... 53 Transform file – attributes ................................................ 53 Transform file – example .................................................. 54 Complete file section – examples ......................................... 54 Complete file section – example 1 .................................... 54 Complete file section – example 2 .................................... 55 <structMap> Structural map section .................................... 57 Attributes of the structural map section ................................ 58 - 5 - Elements contained in the structural map section ................. 58 Division ............................................................................ 58 Division – attributes .......................................................... 59 Division – example ........................................................... 60 File pointer........................................................................ 61 File pointer – attributes: .................................................... 61 File pointer – example ...................................................... 61 METS pointer ................................................................... 63 METS pointer – attributes ................................................ 63 Mets pointer – example .................................................... 64 Area .................................................................................. 65 Area – attributes................................................................ 65 Area – example ................................................................. 67 Sequence of files ............................................................... 69 Sequence of files – attribute .............................................. 69 Sequence of files – example ............................................. 69 Parallel files ...................................................................... 71 Parallel files – attributes ................................................... 71 Parallel files – example 1 .................................................. 71 Parallel Files – example 2 ................................................. 74 <structLink> Structural link Section .................................... 76 Structural link - attribute ....................................................... 76 Elements contained in the structural link section .................. 76 - 6 - Structural map link ........................................................... 76 Structural map link – attributes ......................................... 76 Structural links section – examples ....................................... 77 Structral links section – example 1 ................................... 77 Structural links section – example 2 ................................. 77 <behaviorSec> Behavior section ............................................ 81 Attributes of the behavior section ......................................... 81 Elements contained in the behavior section .......................... 82 Behavior (element) ........................................................... 82 Behavior (element) – attributes ......................................... 82 Behavior (element) – example .......................................... 82 Interface definition ........................................................... 82 Interface definition
Load more

Recommended publications
  • Metadata Demystified: a Guide for Publishers
    ISBN 1-880124-59-9 Metadata Demystified: A Guide for Publishers Table of Contents What Metadata Is 1 What Metadata Isn’t 3 XML 3 Identifiers 4 Why Metadata Is Important 6 What Metadata Means to the Publisher 6 What Metadata Means to the Reader 6 Book-Oriented Metadata Practices 8 ONIX 9 Journal-Oriented Metadata Practices 10 ONIX for Serials 10 JWP On the Exchange of Serials Subscription Information 10 CrossRef 11 The Open Archives Initiative 13 Conclusion 13 Where To Go From Here 13 Compendium of Cited Resources 14 About the Authors and Publishers 15 Published by: The Sheridan Press & NISO Press Contributing Editors: Pat Harris, Susan Parente, Kevin Pirkey, Greg Suprock, Mark Witkowski Authors: Amy Brand, Frank Daly, Barbara Meyers Copyright 2003, The Sheridan Press and NISO Press Printed July 2003 Metadata Demystified: A Guide for Publishers This guide presents an overview of evolving classified according to a variety of specific metadata conventions in publishing, as well as functions, such as technical metadata for related initiatives designed to standardize how technical processes, rights metadata for rights metadata is structured and disseminated resolution, and preservation metadata for online. Focusing on strategic rather than digital archiving, this guide focuses on technical considerations in the business of descriptive metadata, or metadata that publishing, this guide offers insight into how characterizes the content itself. book and journal publishers can streamline the various metadata-based operations at work Occurrences of metadata vary tremendously in their companies and leverage that metadata in richness; that is, how much or how little for added exposure through digital media such of the entity being described is actually as the Web.
    [Show full text]
  • A Web Based System Design for Creating Content in Adaptive
    Malaysian Online Journal of Educational Technology 2020 (Volume 8 - Issue 3 ) A Web Based System Design for Creating [1] [email protected], Gazi University, Faculty of Gazi Content in Adaptive Educational Education, Ankara Hypermedia and Its Usability [2] [email protected], Gazi University, Faculty of Gazi Education, Ankara Yıldız Özaydın Aydoğdu [1], Nursel Yalçın [2] http://dx.doi.org/10.17220/mojet.2020.03.001 ABSTRACT Adaptive educational hypermedia is an environment that offers an individualized learning environment according to the characteristics, knowledge and purpose of the students. In general, adaptive educational hypermedia, a user model is created based on user characteristics and adaptations are made in terms of text, content or presentation according to the created user model. Different contents according to the user model are shown as much as user model creation in adaptive educational hypermedia. The development of applications that allow the creation of adaptive content according to the features specified in the user model has great importance in ensuring the use of adaptive educational hypermedia in different contexts. The purpose of this research is to develop a web- based application for creating content in adaptive educational hypermedia and to examine the usability of the developed application. In order to examine the usability of the application developed in the scope of the study, a field expert opinion form was developed and opinions were asked about the usability of the application from 7 different field experts. As the result of the opinions, it has been seen that the application developed has a high usability level. In addition, based on domain expert recommendations, system revisions were made and the system was published at www.adaptivecontentdevelopment.com.
    [Show full text]
  • Persistent Identifiers (Pids): Recommendations for Institutions Persistent Identifiers (Pids): Recommendations for Institutions
    persistent identifiers (pids): recommendations for institutions persistent identifiers (pids): recommendations for institutions edited by ATHENA ATHENA WP3 general co-ordinator Working Group Rossella Caffo “Identifying standards and developing design recommendations” mt milani, geo graphic sdf texts by Gordon McKenna, Athena logo Collections Trust (UK) Susan Hazan Roxanne Wyms, Royal Museums of Art web version and History (Belgium) http://www.athenaeurope. org/index.php?en/110/ The text of this booklet promotional-material is included in deliverables 3.4 and 3.5, This work by ATHENA of the ATHENA project project is licensed under and is based on a survey a Creative Commons of the content that Attribution ATHENA partners Non-Commercial contracted to provide Share Alike Licence to Europeana through (CC-BY-NC-SA) the ATHENA project. http://creativecommons. org/licenses/by-nc-sa/3.0/ Foreword Introduction 1. Persistent identifiers A briefing note 2. Persistent identifier policy in context 3. Standards landscape 3.1 Physical objects in museums 3.2 Digital objects 3.3 Services 3.4 Collections in museums 3.5 Institutions 4. Managing organisations 5. Persistent identifier systems table of contents Foreword It is the aim of the ATHENA project to support especially museums in providing object data for publication in Europeana. Thus ATHENA is about access to digitised or digital cultural heritage held in museums and other institutions. In order to ensure that information about an object and the object itself, its digital copies can be related to each other and can be retrieved easily at different points in time and from different places it is necessary to use “persistent identifiers” (PIDs).
    [Show full text]
  • Dynamic Adaptive Hypermedia Systems for E-Learning Elvira Popescu
    Dynamic adaptive hypermedia systems for e-learning Elvira Popescu To cite this version: Elvira Popescu. Dynamic adaptive hypermedia systems for e-learning. Education. Université de Technologie de Compiègne, 2008. English. tel-00343460 HAL Id: tel-00343460 https://tel.archives-ouvertes.fr/tel-00343460 Submitted on 10 Dec 2008 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. DOCTORAT TIS Cotutelle de thèse – Nom de l’établissement : Université de Craiova Label européen (nom du pays) : Roumanie Thèse financée par : l’Université de Craiova, Roumanie Dynamic adaptive hypermedia systems for e-learning Directeurs de Thèse (NOM - Prénom) : TRIGANO Philippe (NOM - Prénom) : RASVAN Vladimir. Date, heure et lieu de soutenance : 15 novembre 2008, 12h00, Université de Craiova, Roumanie NOM :Popescu ....................................................... Prénom : Elvira ................................................................ Courriel : [email protected] MEMBRES DU JURY - TRIGANO Philippe, Professeur des Universités (directeur de thèse) Spécialité:
    [Show full text]
  • Metadata Standards
    Chapter 3 METADATA STANDARDS This chapter lists the major metadata standards in use or under development. Standards are subdivided into six areas: general, transportation models, educa- tion, media-specific, preservation, and rights. Each standard lists its official URL, sponsoring agency, community of use, purpose and goals, description, potential for information organizations, and key projects. General metadata standards General metadata standards are the most common, well-known, and univer- sally accepted schemas to date. Some are general and meant to be used as universal or common-denominator standards; others are for specific communi- ties with specific information resources. Most of the metadata standards listed here have emerged as practical applications in use, or will probably emerge as the most commonly applied standards, due to broad international support, history and development, or industry application and acceptance. Dublin Core Metadata Initiative (DCMI) http://dublincore.org The Dublin Core Metadata Initiative (DCMI) is managed by an international board of trustees, but most of the direction and maintenance of the standard has been led by the Online Computer Library Center (OCLC) in Dublin, Ohio. Community of use Library Technology Reports Librarians, Web content providers, Web resource creators, metadata creators, and general public. Purpose and goals Dublin Core assists in the discovery and description of Web and electronic resources. It is designed to provide a simple descriptive metadata standard extensible to Web resources of any format or subject domain. Description www.techsource.ala.org Dublin Core is a set of 15 core elements that assist in simple description and discovery of electronic resources. The standards basic principles are the reasons for its success as a viable common-denominator metadata standard for elec- tronic resources.
    [Show full text]
  • A Framework of Guidance for Building Good Digital Collections
    A Framework of Guidance for Building Good Digital Collections 3rd edition December 2007 A NISO Recommended Practice Prepared by the NISO Framework Working Group with support from the Institute of Museum and Library Services About NISO Recommended Practices A NISO Recommended Practice is a recommended "best practice" or "guideline" for methods, materials, or practices in order to give guidance to the user. Such documents usually represent a leading edge, exceptional model, or proven industry practice. All elements of Recommended Practices are discretionary and may be used as stated or modified by the user to meet specific needs. This recommended practice may be revised or withdrawn at any time. For current information on the status of this publication contact the NISO office or visit the NISO website (www.niso.org). Published by National Information Standards Organization (NISO) One North Charles Street, Suite 1905 Baltimore, MD 21201 www.niso.org Copyright © 2007 by the National Information Standards Organization All rights reserved under International and Pan-American Copyright Conventions. For noncommercial purposes only, this publication may be reproduced or transmitted in any form or by any means without prior permission in writing from the publisher, provided it is reproduced accurately, the source of the material is identified, and the NISO copyright status is acknowledged. All inquires regarding translations into other languages or commercial reproduction or distribution should be addressed to: NISO, One North Charles Street, Suite
    [Show full text]
  • Internet Explorer Users Are Required to Add the Portal URL to Trusted Sites
    CLA Client Portal Browser and Silverlight FAQs 1. Question: I am receiving an “Error 500” when clicking the link to access the CLA Document Portal. Resolution: Verify with your IT department that the portal is not blocked by any internal monitoring or protection applications. 2. Question: How do I know if my computer has Microsoft Silverlight Installed? Resolution: The first time you try and login to the portal you will be prompted to install Silverlight from Microsoft’s website if you don’t have it already installed. The installation typically takes less than one minute and is completely safe. http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx If you cannot, or prefer not to, install Silverlight on your machine, a simplified version of the document portal that does not require Silverlight is available. Click on the Take me to the non- Silverlight login on the CLA Document Portal page (www.claconnect.com/docportal). 3. Question: I cannot access the CLA Document Portal. (Server error/Page not found) Resolution: Check that you are using a Microsoft Silverlight 4 compatible browser on all PC’s or MAC. A complete list of browsers and operating systems that support Silverlight 4 can be found at http://www.microsoft.com/getsilverlight/locale/en-us/html/installation-win-SL4.html Please note: Internet Explorer users are required to add the portal URL to Trusted Sites. Adding to Trusted Sites Internet Explorer settings 1. Open Internet Explorer and browse to https://portal.cchaxcess.com/Portal/. 2. In Internet Explorer, select Tools / Internet Options; then select the Security tab and click Trusted Sites and then Sites.
    [Show full text]
  • Digital Object Identifier (DOI) System for Research Data
    Digital Object Identifier (DOI) System for Research Data A guide explaining what the Digital Object Identifier system does, the advantages of using a DOI Name to cite and link research data and the ARDC DOI minting service. Who is this for? This guide is intended for researchers and eResearch infrastructure support providers. Last updated: May 2019 This work is licenced under a Creative Commons Attribution 4.0 Australia Licence Contents Anatomy of a DOI ....................................................................................................................................................................1 What is the DOI System? ..............................................................................................................................................................1 What are the advantages of DOIs for datasets? ...................................................................................................................2 Digital Object Identifiers (DOIs) .................................................................................................................................................3 DOIs and other persistent identifiers ................................................................................................................................4 DOIs for versioned data .......................................................................................................................................................4 ARDC DOI Minting service...................................................................................................................................................4
    [Show full text]
  • Identifiers and Use Case in Scientific Research
    Submitted on: 19.07.2016 Identifiers and Use Case in Scientific Research Thomas Gillespie Neurosciences, University of California, San Diego, San Diego, CA, USA E-mail address: [email protected] Qian Zhang School of Information Sciences, University of Illinois at Urbana-Champaign, USA E-mail address: [email protected] Chelakara S. Subramanian Department of Mech and Aerospace Engineering, Florida Institute of Technology, Melbourne, FL, USA, E-mail address: [email protected] Yan Han University Libraries, The University of Arizona, Tucson, AZ, USA. E-mail address: [email protected] Copyright © 2016 by Thomas Gillespie, Qian Zhang, Chelakara S. Subramanian, Yan Han. This work is made available under the terms of the Creative Commons Attribution 4.0 International License: http://creativecommons.org/licenses/by/4.0 Abstract: The authors have broad representations across of a variety of domains including Oceanography, Aerospace Engineering, Astronomy, Neurosciences, and Libraries. The article is intended to: a) discuss the key concepts related to identifiers and define identifiers; b) explore characteristics of good and bad identifiers in general, along with an overview of popular identifiers; c) demonstrate a use case in a scientific domain of using identifiers via the data lifecycle; c) raise awareness of data collection, data analysis and data sharing for raw and post-processing data for data producers and data users. It is inevitable for multiple identifiers to co-exist in the data lifecycle, as the case study shows different needs of data producers and data users. Keywords: identifier, use case, data lifecycle 1. Identifiers: Introduction and Definition A lab’s notebook number and page are sufficient for local access in no time.
    [Show full text]
  • Hypervideo and Annotations on the Web
    Hypervideo and Annotations on the Web Madjid Sadallah Olivier Aubert Yannick Prie´ DTISI - CERIST LIRIS - Universite´ Lyon 1 LIRIS - Universite´ Lyon 1 Alger, Algerie´ UMR 5205 CNRS UMR 5205 CNRS Email: [email protected] Email: [email protected] Email: [email protected] Abstract—Effective video-based Web information system de- the hypermedia system. Hypervideo addresses this issue by ployment is still challenging, while the recent widespread of a specialization of hypermedia centered on interactive video. multimedia further raises the demand for new online audiovisual We define hypervideo as being an interactive video-centric document edition and presentation alternatives. Hypervideo, a specialization of hypermedia focusing on video, can be used on the hypermedia document built upon an audiovisual content - a set Web to provide a basis for video-centric documents and to allow of video objects -. Several kinds of related data are presented more elaborated practices of online video. In this paper, we pro- within the document in a time synchronized way to augment pose an annotation-driven model to conceptualize hypervideos, the audiovisual part around which the presentation is organized promoting a clear separation between video content/metadata in space and time. and their various potential presentations. Using the proposed model, features of hypervideo are grafted to wider video- The articulation of video content with navigation facilities based Web documents in a Web standards-compliant manner. introduces new ways for developing interfaces, rendering the The annotation-driven hypervideo model and its implementation content and interacting with the document. By supplying offer a general framework to experiment with new interaction spatio-temporal behaviors to links, hypervideos allow address- modalities for video-based knowledge communication on the Web.
    [Show full text]
  • Referencing Source Code Artifacts: a Separate Concern in Software Citation Roberto Di Cosmo, Morane Gruenpeter, Stefano Zacchiroli
    Referencing Source Code Artifacts: a Separate Concern in Software Citation Roberto Di Cosmo, Morane Gruenpeter, Stefano Zacchiroli To cite this version: Roberto Di Cosmo, Morane Gruenpeter, Stefano Zacchiroli. Referencing Source Code Artifacts: a Separate Concern in Software Citation. Computing in Science and Engineering, Institute of Electrical and Electronics Engineers, In press, pp.1-9. 10.1109/MCSE.2019.2963148. hal-02446202 HAL Id: hal-02446202 https://hal.archives-ouvertes.fr/hal-02446202 Submitted on 22 Jan 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 1 Referencing Source Code Artifacts: a Separate Concern in Software Citation Roberto Di Cosmo, Inria and University Paris Diderot, France [email protected] Morane Gruenpeter, University of L’Aquila and Inria, France [email protected] Stefano Zacchiroli, University Paris Diderot and Inria, France [email protected] Abstract—Among the entities involved in software citation, II. REFERENCING SOURCE CODE FOR REPRODUCIBILITY software source code requires special attention, due to the role Software and software-based methods are now widely used it plays in ensuring scientific reproducibility. To reference source code we need identifiers that are not only unique and persistent, in research fields other than just computer science and en- but also support integrity checking intrinsically.
    [Show full text]
  • Persistent Identifiers: Consolidated Assertions Status of November, 2017
    Persistent identifiers: Consolidated assertions Status of November, 2017 Editors: Peter Wittenburg (RDA Europe), Margareta Hellström (ICOS), and Carlo-Maria Zwölf (VAMDC) Co-authors: Hossein Abroshan (CESSDA), Ari Asmi (ENVRIplus), Giuseppe Di Bernardo (MPA), Danielle Couvreur (MYRRHA), Tamas Gaizer (ELI), Petr Holub (BBMRI), Rob Hooft (ELIXIR), Ingemar Häggström (EISCAT), Manfred Kohler (EU- OPENSCREEN), Dimitris Koureas (NHM), Wolfgang Kuchinke (ECRIN), Luciano Milanesi (CNR), Joseph Padfield (NG), Antonio Rosato (INSTRUCT), Christine Staiger (SurfSARA), Dieter van Uytvanck (CLARIN) and Tobias Weigel (IS-ENES) The Research Data Alliance is supported by the European Commission, the National Science Foundation and other U.S. agencies, and the Australian Government. Document revision history 2016-11-01 v 1.0 (extracted from RDA Data Fabric IG wiki) 2016-12-15 v 2.0, after comments & feedback from Bratislava 2016-11-14 2017-03-29 v 3.0, partially discussed at RDA P9 in Barcelona 2017-04-07 2017-05-10 v 4.0, discussed during GEDE telco on 2017-05-29 2017-06-21 v 5.0 for GEDE PID group review on 2017-06-28 2017-08-29 v 5.1 for GEDE PID group review on 2017-08-30 2017-11-13 v 6.0, for GEDE review on 2017-11-20 2017-12-13 V 6.1, circulated for RDA (Data Fabric IG) review ii Abstract Experts from 47 European research infrastructure initiatives and ERICs have agreed on a set of assertions about the nature, the creation and the usage of Persistent Identifiers (PIDs). This work was done in close synchronisation with the RDA Data Fabric Interest Group (DFIG) ensuring a global validation of the assertions.
    [Show full text]