ADN Framework Overview A Collaboration of ADEPT, DLESE and NASA (2002 Nov. 19)

Slides:



Advertisements
Similar presentations
Foundational Objects. Areas of coverage Technical objects Foundational objects Lessons learned from review of Use Case content Simple Study Simple Questionnaire.
Advertisements

Accessing and Using the e-Book Collection from EBSCOhost ® When an arrow appears, click to proceed to the next slide at your own pace. To go back, click.
Setting the Stage Provide a high-level overview of the accessioning and management processes Depict where/how DLESE tools are used in the processes Identify.
ADN Educational Fields March Educational Purpose Describe educational and pedagogical characteristics of resources where resources are: – Curriculum,
1 ADN Geospatial & Temporal March Geospatial Purpose Describe geospatial coverage of resources where resources are: – Curriculum, activities,
Module 10b: Wrapup IMT530: Organization of Information Resources Winter, 2007 Michael Crandall.
RDF Kitty Turner. Current Situation there is hardly any metadata on the Web search engine sites do the equivalent of going through a library, reading.
1 CS 502: Computing Methods for Digital Libraries Lecture 17 Descriptive Metadata: Dublin Core.
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.
XML Verification Well-formed XML document  conforms to basic XML syntax  contains only built-in character entities Validated XML document  conforms.
Introduction to XML This material is based heavily on the tutorial by the same name at
ISO Standards: Status, Tools, Implementations, and Training Standards/David Danko.
Form Builder Iteration 2 User Acceptance Testing (UAT) Denise Warzel Semantic Infrastructure Operations Team Presented to caDSR Curation Team March.
XP New Perspectives on XML Tutorial 4 1 XML Schema Tutorial – Carey ISBN Working with Namespaces and Schemas.
XP New Perspectives on XML Tutorial 3 1 DTD Tutorial – Carey ISBN
EAD: A Technical Introduction Julie Hardesty, Metadata Analyst June 3, 2014.
8/28/97Organization of Information in Collections Introduction to Description: Dublin Core and History University of California, Berkeley School of Information.
DPC Collection Builder Support March 2004 Katy Ginger Metadata Architect DLESE Program Center (DPC) Univ. Corp. for Atmospheric.
Why XML ? Problems with HTML HTML design - HTML is intended for presentation of information as Web pages. - HTML contains a fixed set of markup tags. This.
1 XML Schemas. 2 Useful Links Schema tutorial links:
Dr. Azeddine Chikh IS446: Internet Software Development.
Metadata: An Overview Katie Dunn Technology & Metadata Librarian
The Metadata Object Description Schema (MODS) NISO Metadata Workshop May 20, 2004 Rebecca Guenther Network Development and MARC Standards Office Library.
What is XML?  XML stands for EXtensible Markup Language  XML is a markup language much like HTML  XML was designed to carry data, not to display data.
1 Tutorial 13 Validating Documents with DTDs Working with Document Type Definitions.
Of 33 lecture 3: xml and xml schema. of 33 XML, RDF, RDF Schema overview XML – simple introduction and XML Schema RDF – basics, language RDF Schema –
1 Collection Specific Vocabularies March Terminology CB - abbreviation for collection builder CV - abbreviation for controlled vocabulary.
Metadata Lessons Learned Katy Ginger Digital Learning Sciences University Corporation for Atmospheric Research (UCAR)
Copyrighted material John Tullis 10/17/2015 page 1 04/15/00 XML Part 3 John Tullis DePaul Instructor
New Perspectives on XML, 2nd Edition
1 DLESE-IMS Metadata, ADN Metadata and the DLESE Catalog System.
2.2 XHTML (cont.). Motto Yea, from the table of my memory I’ll wipe away all trivial fond records. —William Shakespeare.
The Digital Library for Earth System Science: Contributing resources and collections Meeting with GLOBE 5/29/03 Holly Devaul.
Evolving MARC 21 for the future Rebecca Guenther CCS Forum, ALA Annual July 10, 2009.
ADN Framework Overview A Collaboration of ADEPT, DLESE and NASA (2002 Nov. 7)
XML 2nd EDITION Tutorial 4 Working With Schemas. XP Schemas A schema is an XML document that defines the content and structure of one or more XML documents.
1 Tutorial 14 Validating Documents with Schemas Exploring the XML Schema Vocabulary.
Tutorial 13 Validating Documents with Schemas
BEN METADATA SPECIFICATION Isovera Consulting Feb
The Digital Library for Earth System Science: Contributing resources and collections GCCS Internship Orientation Holly Devaul 19 June 2003.
DLESE Metadata Story Katy Ginger Metadata Architect DLESE Program Center Session: Metadata stories – The Creation and Management of Metadata.
OAI Overview DLESE OAI Workshop April 29-30, 2002 John Weatherley
1 Understanding Cataloging with DLESE Metadata Karon Kelly Katy Ginger Holly Devaul
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 and Meta tag. What is metadata? What does metadata do? Metadata schemes What is meta tag? Meta tag example Table of Content.
Metadata Content Entering Metadata Information. Discovery vs. Access vs. Understanding Cannot search on content if it is not documented. Cannot access.
DPC 2002 Retreat Metadata Status Report (2002 Sep. 4)
Statistical Data and Metadata Exchange SDMX Metadata Common Vocabulary Status of project and issues ( ) Marco Pellegrino Eurostat
DLESE Metadata Frameworks March Talk Organizer Terminology DLESE metadata history (DC/IMS to DLESE- IMS to ADN) ADN Collection News-opps Object.
Describing resources II: Dublin Core CERN-UNESCO School on Digital Libraries Rabat, Nov 22-26, 2010 Annette Holtkamp CERN.
SEMI-STRUCTURED DATA (XML) 1. SEMI-STRUCTURED DATA ER, Relational, ODL data models are all based on schema Structure of data is rigid and known is advance.
1 Annotation Framework March Terminology CV - abbreviation for controlled vocabulary CRS - Community Review System (a collection within DLESE)
Developing Metadata Frameworks for Earth System Education NSDL 2003 Annual Meeting October 14, 2003 Katy Ginger and Karon Kelly DLESE Program Center.
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
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.
Geospatial metadata Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
Discovery and Metadata March 9, 2004 John Weatherley
1 XML and XML in DLESE Katy Ginger November 2003.
Metadata Frameworks ADN - for online/offline resources
Metadata Frameworks Fall 2003.
Overview of DLESE Metadata & Catalog System
XML QUESTIONS AND ANSWERS
MUI Purpose Conversion: current vocabulary-ui manager to the metadata-ui manger (MUI). No database and is services oriented Assigns identification numbers.
Attributes and Values Describing Entities.
Database Design Hacettepe University
Attributes and Values Describing Entities.
Semi-Structured data (XML)
New Perspectives on XML
Presentation transcript:

ADN Framework Overview A Collaboration of ADEPT, DLESE and NASA (2002 Nov. 19)

2 Meeting Purpose Provide the technical overview of ADN. Raise issues or concerns on how ADN will affect DLESE systems. Presentation covers: Constructing the framework XML schema development Metadata use concepts Overview (semantically and technically) of framework categories

3 Framework Purpose Capture resource information in a structured format for discovery emphasizing : Plug-n-play vocabs and framework components Enforcement of vocabs and required metadata Geospatial, time, educational standards, concepts and new educational elements The ability to handle offline resources The use of XML schemas for use with OAI

4 Constructing the Framework Framework is wrapped by 1 overarching schema Framework is broken into 11 category schemas with each defining distinct metadata fields Framework uses ~35 vocabulary schemas An instance document (metadata record) validates against the overarching schema (NOTE: plug-n-play feature of the framework and vocab schemas is used in other DLESE frameworks… e.g. the collection framework uses the metaMetadata section)

5 The XML of the Framework Overarching schema: record.xsd calls general.xsd (mandatory) - general characteristics like title descrp. lifecycle.xsd (optional) - who created the resource metaMetadata.xsd (mandatory) - who cataloged the resource and status technical.xsd (mandatory) - computer and browser requirements educational.xsd (mandatory) - audience, learning goals, standards rights.xsd (mandatory) - copyright relations.xsd (optional) - relationships to other resources geospatial.xsd (optional) - spatial data (boundinb box coordinates) temporal.xsd (optional) - temporal data (time past, present & future) space.xsd (optional) - astronomy data commonfields.xsd (does not appear; used by the above schemas)

6 XML Schema Development 1 Namespaces Uses chameleon approach Means only record.xsd has an explicit target namespace. (aside: NSDL has 4 namespaces) Category schemas use the namespace of any schema that calls them (record.xsd here). Root element Is and is ADNmetadataType

7 XML Schema Development 2 Approach Uses the Venetian Blind approach… means… Fields are defined as built-in, complex or simple types (facilitates for re-use) Elements occuring more than once use wrapper tags ( is wrapped by ) Elements and Attributes Schema elements are generally ADN fields Attributes are used for required additional information or if two bits of info. are required

8 XML Schema Development 3 Controlled Vocabularies Hierarchal vocabularies appear as colon separated text (e.g. DLESE:Forestry) Some elements use fixed vocabs Multiple vocabs must use a simple type element commonfields.xsd Used when metadata fields (elements or attributes) appear in multiple schemas. E.g., title is in general.xsd & relations.xsd; so title defined commonfields.xsd

9 Metadata Use Concepts 1 Required metadata w/o contr. vocabs Element must appear Content must be present and valid Required metadata with contr. vocabs Element must appear with a vocab choice OR Allows the use of a default value like ‘DLESE:To be supplied’ in order to facilitate validation Tag content cannot be null (empty)

10 Metadata Use Concepts 2 Non-required w contr vocabs Element only appears if it has content The content must be from the authorized controlled vocabs is not required. But if vertical info, is entered then becomes required Non-required w/o a contr vocab Element only appears if it has content Generic description field for all categories

11 Fields: tag set Subjects: Required metadata from vocabs Keywords: Non-required, free text terms Concepts: Non-required metadata from vocabs supported by a schema at the DPC OtherTerms: Non-required metadata from a vocab house elsewhere; provide service name, URL and ID # and terms Simple Place & Time: defer to geospatial CatalogEntries: Other classifications

12 Fields: tag set Person info Name (first, last, middle) Institutional name and department Primary and alternate Reference number (if one) to an LDAP directory Organization info Institutional name and department Institutional URL or generic Reference number (if one) to an LDAP directory

13 Fields: CatalogEntries: Required record number Date Info: created, accessioned, modified (and deaccessioned) created and modified are required Status: accessioned etc. and an optional description Scheme, copyright, use, language: All required of the metadata

14 Fields: tag set Online Primary url and mirror urls Medium (mime type) Size, Duration Browser and other requirements Offline Description Access information Object type (rock, book, videotape)

15 Fields: tag set Expanded audience Uses GEM vocabs (toolFor, beneficiary, teaching methods) Educational standards (content, process, and teaching) that are from NSES, NCGE, NCTM Interactivity level and type Old learning context is now gradeRange Audience repeats while gradeRange is the only required audience field

16 Fields: tag set IdEntry: when an ID is known; must be in the same catalog record number set as the item being cataloged URLEntry: when only a URL is known; will include title and description Can these be the same or do we need to keep separate to differentiate ID vs. URL?

17 Fields: tag set 1 big bounding box with multiple detailed geometries Separate place and events now More required elements Use simple place and event when bounding box coordinates are unknown

18 Fields tag set Completely independent of geospatial Each timeAndPeriod allows 1 time value but multiple period names; tag can repeat Choose between timeAD timeBC timeRelative- 30 days ago, 100 million years ago Use simple temporal when time range is non-numeric (e.g. day, fall, morning)

19 Issues Serialization of vocabs: Does it work? Geospatial: NSDL wants us to write: City: Denver, CO, United States Region: Great Plains, United States State: Colorado, United States Relation: can I make identry and urlentry the same? Or keep separate? Namespaces: ADN only has 1 but NSDL annotation will have 4