1 Developing a Metadata Element Set or an Application Profile Image credits: 6Y old Anthony.

Slides:



Advertisements
Similar presentations
Putting the Pieces Together Grace Agnew Slide User Description Rights Holder Authentication Rights Video Object Permission Administration.
Advertisements

International Conference on Dublin Core and Metadata Applications DC-Scholar, 24 th September /10/2014 Scholarly Works Application.
A centre of expertise in digital information management UKOLN is.
Mark Evans, Tessella Digital Preservation Boot Camp – PASIG meeting, Washington DC, 22 nd May 2013 PREMIS Practical Strategies For Preservation Metadata.
3. Technical and administrative metadata standards Metadata Standards and Applications.
1 of 2 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits This document should.
PREMIS What is PREMIS? o Preservation Metadata Implementation Strategies When is PREMIS use? o PREMIS is used for “repository design, evaluation, and archived.
AIP Archival Information Package – Defines how digital objects and its associated metadata are packaged using XML based files. METS (binding file) MODS.
Declare A DTD File. Declare A DTD Inline File For example, use DTD to restrict the value of an XML document to contain only character data.
Descriptive Metadata o When will mods.xml be used by METS (aip.xml) ?  METS will use the mods.xml to encode descriptive metadata. Information that describes,
1 Specification of IT Systems Mandatory Exercise Week 3.
The RDF meta model: a closer look Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations.
The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management Fall 2003 * Bob Boiko * MSIM Associate Chair XML Schemas.
Networked Resources and Metadata Interest Group Diane I. Hillmann Research Librarian Cornell University Library.
Metadata : Setting the Scene or a Basic Introduction Wendy Duff University of Toronto, Faculty of Information Studies.
Part 1. Preparing for the exercises 1-1. Open a Web broswer (suggesting using Internet Explorer or Firefox, not Safari). Go to VRA Core site (Google "VRA.
A centre of expertise in digital information management UKOLN is supported by: XML Schema for DC Libraries AP DC Libraries WG Meeting,
Metadata: Its Functions in Knowledge Representation for Digital Collections 1 Summary.
CEDROM-SNi’s DITA- based Project From Analysis to Delivery By France Baril Documentation Architect.
By Carrie Moran. To examine the Metadata Object Description Schema (MODS) metadata scheme to determine its utility based on structure, interoperability.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 3 Requirements Models.
Chapter 1: The Database Environment and Development Process
Web-Enabled Decision Support Systems
Put the Lesson Title Here A webquest for xth grade Designed by Put your You may include graphics, a movie, or sound to any of the slides. Introduction.
SWAP FOR DUMMIES. Scholarly Works Application Profile a Dublin Core Application Profile for describing scholarly works (eprints) held in institutional.
I Never Met a Data I Didn’t Like Metadata Issues in Local and Shared Digital Collections Presentation to ALCTS Electronic Resources Interest Group January.
The Final Study Period Report on MFI 6: Model registration procedure SC32WG2 Meeting, Sydney May 26, 2008 H. Horiuchi, Keqing He, Doo-Kwon Baik SC32WG2.
PREMIS Rathachai Chawuthai Information Management CSIM / AIT.
Information Systems & Databases 2.2) Organisation methods.
Implementation of PREMIS in METS Rebecca Guenther Sr. Networking & Standards Specialist, Library of Congress PREMIS Implementation Fair San.
1 Metadata –Information about information – Different objects, different forms – e.g. Library catalogue record Property:Value: Author Ian Beardwell Publisher.
Metadata and Documentation Iain Wallace Performing Arts Data Service.
Linked Data by Dr. Barbara B. Tillett Chief, Policy and Standards Division Library of Congress For Texas Library Association Conference April 12, 2011.
RELATORS, ROLES AND DATA… … similarities and differences.
1 Dublin Core & DCMI – an introduction Some slides are from DCMI Training Resources at:
Metadata Registries Registry: authoritative, centrally controlled store of information – W3C Web Services Glossary, 2004
By Visual Resources Association (VRA) VRA CORE CATEGORIES.
The RDF meta model Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations of XML compared.
Metadata “Data about data” Describes various aspects of a digital file or group of files Identifies the parts of a digital object and documents their content,
2.An overview of SDMX (What is SDMX? Part I) 1 Edward Cook Eurostat Unit B5: “Central data and metadata services” SDMX Basics course, October 2015.
Application Profiles Application profiles -- are schemas which consist of data elements drawn from one or more namespaces, combined together by implementers,
OWL Web Ontology Language Summary IHan HSIAO (Sharon)
Chapter 29. Copyright 2003, Paradigm Publishing Inc. CHAPTER 29 BACKNEXTEND 29-2 LINKS TO OBJECTIVES Attach an XML Schema Attach an XML Schema Load XML.
Describing resources II: Dublin Core CERN-UNESCO School on Digital Libraries Rabat, Nov 22-26, 2010 Annette Holtkamp CERN.
Standardized Metadata Standardized Metadata The FGDC Content Standard For Digital Geospatial Metadata The FGDC Content Standard For Digital Geospatial.
Dublin Core Basics Workshop Lisa Gonzalez KB/LM Librarian.
1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005.
Understanding the Value and Importance of Proper Data Documentation 5-1 At the conclusion of this module the participant will be able to List the seven.
Attributes and Values Describing Entities. Metadata At the most basic level, metadata is just another term for description, or information about an entity.
Using LORO A presentation created by Anna Calvi
Metadata Standards - Types
An Overview of Dublin Core Metadata Schema Registry
Introduction to Metadata
Geospatial Metadata, Standards and Infrastructure
Applications of IFLA Namespaces
Attributes and Values Describing Entities.
Metadata to fit your needs... How much is too much?
2. An overview of SDMX (What is SDMX? Part I)
Prepared by Elena Escolano
From Big Bang to beta An overview of the 3R Project
Developing a Metadata Element Set and/or an Application Profile
Metadata in Digital Preservation: Setting the Scene
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS
Content of beta RDA A brief overview Gordon Dunsire, Chair, RSC
Part 1. Preparing for the exercises
The new RDA: resource description in libraries and beyond
EXHIBIT TITLE.
Graduation Project Project Name
Put the Lesson Title Here
Presentation transcript:

1 Developing a Metadata Element Set or an Application Profile Image credits: 6Y old Anthony. tml;

2 Major Steps (Overview) 1.Functional requirements What do you want to accomplish with your application? 2.Domain model What kind of things (entities) your metadata will describe, and what are the relationships between those things? 3.Desired metadata elements What elements are desired? 4.Value Space Decisions Cardinality enforcement (Required or not?) Value Space Restriction (Controlled values? How – vocabulary or rule?) Relationship and dependency specification (Sub-elements?) 5.Existing elements Any existing element to consider? 6.Crosswalks 7.Specification /Documentation Put into a complete specification of the element set. 8.Prepare guidelines for use.

3 Major Steps (1-3) Step 1. Functional requirements What do you want to accomplish with your application? Step 2. Domain model What kind of things (entities) your metadata will describe, and what are the relationships between those things? Step 3. Desired metadata elements What elements are desired? List in a table:  Desired Element  Explanation and Description of the Element (This will be the element definition and will be included in the final schema.)  Example (The examples may be included in the best practice guide, either in the schema or in a separate guide.)

1. Communicating about the Functional Requirements 4 An operational system Questions: What do we want to 'search by', 'browse by', 'sort by', 'link to'?

Question: Will the metadata support these functions? 5 No FORMAT information Video? Image? Text? media type Video? Image? Text? media type

Resource Agent About… 2) Select or Design a Domain Model What kind of things (entities) your metadata will describe, and what are the relationships between those things?

Review: Entity Relationship Diagram 7 Source: from CCO

8 Introduction-to-rNews for clearer figure Example: The complete class diagram of the rNews data model. (for embadding metadata within the news pieces)

9 (cont.) Major Steps (4) Step 4. Value Space Decisions Content and value specifications, vocabularies.  Cardinality enforcement (Required or not?) M, O, R (Mandatory /Optional? Repeatable?)  Value Space Restriction Controlled values? How – vocabulary or rule? (A pre- defined list of terms, name of an existing scheme, or rules, may attach a list or link.)  Relationship and dependency specification (Sub- elements?)

10 Step 5. Find existing elements and re-use them in an Application Profile What element in another schema would match your element? Assume your have a namespace (e.g., "ksu" or any other word). Select the namespace you want to reuse (e.g., dc:, dct:, or vra:). List in a table all of the following:  Element Name (The element defined by the last task)  Matched SCHEMA A Element (Schema A is the preliminary source schema, e.g., vra.agent)  Matched SCHEMA B Element and Qualifier (Schema B is the secondary source schema, e.g., dc.langauge)  Un-matched Element (This element will be claimed under ksu Namespace, e.g., ksu.collectionType) (cont.) Major Steps (5)

11 Step 6. crosswalks 1.Create a crosswalk by mapping your element set to another group's element set. 2.Create crosswalks using the new element set just created as the source schema, mapping it to another schema, e.g., MODS, DC. (cont.) Major Steps (6)

12 Step 7. Write a specification for the complete element set. Follow the examples of specifications from the original element sets; write your specification for the element set for postcards. – Examples of original element sets: DC: – Examples of original Application Profiles: NLM: – Scholarly Works Application Profile (SWAP) #Scholarly_Works_Application_Profile Step 8. Prepare guidelines for use. (cont.) Major Steps (7)

13 Review: Major Steps 1.Functional requirements What do you want to accomplish with your application? 2.Domain model What kind of things (entities) your metadata will describe, and what are the relationships between those things? 3.Desired metadata elements What elements are desired? Cardinality enforcement (Required or not?) 4.Value Space Decisions Value Space Restriction (Controlled values? How – vocabulary or rule?) Relationship and dependency specification (Sub-elements?) 5.Existing elements Any existing element to consider? 6.Crosswalks 7.Specification /Documentation Put into a complete specification of the element set. 8.Prepare guidelines for use.

14 In-Class Exercise Team work to make a list of desired elements for either postcards or bookmarks Element Name | Definition | Example We will share the elements and discuss these issues: In preparing your metadata project, what do you foresee as the most challenging decisions for your project? Why do you think they are challenging decisions to make? What factors will affect your decisions?