DLESE Metadata Frameworks March 2004

2 Talk Organizer Terminology DLESE metadata history (DC/IMS to DLESE- IMS to ADN) ADN Collection News-opps Object Framework versions Development Tradeoffs

3 Terminology (1) Metadata - structured descriptive information about resources (e.g. info in a card catalog) Metadata Standard - a representation that is developed & available from a standards body or metadata organization (e.g Dublin Core) Metadata Framework - a representation that may or may not be based on or derived from a standard by a standards body or metadata organization (e.g. collection, annotation)

4 Terminology (2) Resource - actual content (includes web based learning material, annotations, reviews, data, imagery, audio clips, code etc.) Record - an XML file containing metadata describing a resource Collection - a group of metadata records Annotation - additional content or metadata that is appropriate to associate with a resource

5 Terminology (3) Schema - XML schema files (code) of the metadata representation Format - the metadata representation XML metadata files are using (e.g. ADN, IMS) Harvest - any method of getting metadata files to the DPC Ingest - making metadata records accessible in the DLESE Discovery System

6 DLESE/ DPC Frameworks DLESE-IMS - online resources only ADN - online and offline resources Annotation - resource reviews, comments, connecting additional resource content Collection - collection characteristics News-Opps - announcements, conferences Object - FAQ’s, glossary terms, lookup’s SMS - Strand Map Service for AAAS benchmarks

7 DLESE metadata history: DC/IMS to DLESE-IMS to ADN (1) Late 1999-Jan 2000: Investigate simple Dublin Core (DC) and IMS Feb 2000: Use IMS because XML based and has educational components and hints may have geospatial fields soon Feb Jul 2001: Community wants standards, geospatial and temporal. IMS has not yet accommodated these but CBs can extend IMS which DLESE does

8 DLESE metadata history: DC/IMS to DLESE-IMS to ADN (2) Jun-Oct 2000: Extending IMS is cumbersome; IMS changes frequently; Create DLESE-IMS Jul 2001: OAI promoted as a harvesting protocol; means metadata has to be XML schema not DTD like IMS & DLESE-IMS Jul June 2002: Need to accommodate collections raises issues about how to get reliable metadata (need to enforce vocabs)

9 DLESE metadata history: DC/IMS to DLESE-IMS to ADN (3) Jun 2002: DLESE-IMS is frozen Jun-Dec 2002: ADN framework developed Jan-April 2003: Fixes and testing; current version released Aug 2003: Library searching implements ADN

10 Motivation to make ADN Enforce required metadata and controlled vocabs Capture more educational info (tool for, beneficiary) Capture geospatial info (details, place names, event names, polygons, objects in space, other planets) Capture temporal info (relative time, time in the past and named time periods)

11 ADN Framework Overview (1) Purpose: to describe resources typically used in learning environments where resources are: – Modules, lesson plans, activities, courses, curriculum – Datasets (remote sensed, in-situ, model) – Guides, text, reference material, reports – Visuals (illustrations, maps, photos, video, visualizations, imagery) – Audio, tools, code, portals

12 ADN Framework Overview (2) Content: Information in the metadata record – General (title, language, keywords, subjects, description) – Educational (e.g. resource type, grade range) – Geospatial and temporal (more detail later) – Relations (connecting resources to each other) – Rights (resource copyright and cost) – Technical (URL, browser, platform, plug-ins) – Resource catalogers and resource creators – Administrative data (id number, metadata copyright)

13 ADN Framework Overview (3) Technical: – Uses XML schemas to enforce required metadata and controlled vocabularies – Based on IMS, Dublin Core and GEM Possible Developments: – Use NSES to a finer level of granularity – Address special needs/diversity field – Establish cataloging practices for education vocabs

14 Annotation Framework Overview Separate presentation later in the morning

15 Collection Framework Overview (1) Purpose: (each collection has a cllctn record) 1. To provide for the discrete discovery of collections 2. Indicate presence in the DLESE Reviewed Collection 3. Indicate whether the collection can be redistributed (e.g. to National Science Digital Library NSDL) 4. Indicate the metadata format of the collection’s metadata records (ADN, annotation etc.) 5. Indicate how the collection’s metadata records arrive at the DPC ( , OAI or FTP)

16 Collection Framework Overview (2) Content: Information in the metadata record – Collection name, description, keywords, subjects – Responsible party and collection contact – Cost, grade ranges – History of accessioning – URL to the collection’s scope statement – Collection’s discovery system URL (if there is one) – NSDL information (logo, mime types) – Administrative data (cataloger, DRC presence) – Relations (what collections are related)

17 Collection Framework Overview (3) Technical: – Uses XML schemas to enforce required metadata and controlled vocabularies – Based on IMS to serve DLESE needs Possible Developments: – Integrate fully in DLESE systems and services

18 News and Opps Framework (1) Purpose: to describe events or time-sensitive resources with specific start and end dates. Events and resources include: – Grants, scholarships – Conference or workshop notices – Internships, jobs – News, announcements

19 News and Opps Framework (2) Content: Information in the metadata record – Title, description, keywords, subject – URL to the announcement – Dates (event start/stop, post/archive) – Cataloger – Announcement type (grant, job, conference) – Audience

20 News and Opps Framework (3) Technical: – Framework is being revamped to use XML schemas and to work in OAI – Required metadata and controlled vocabularies will be enforced – Based on DLESE needs Future Developments: – Resolve technical issues above

21 Objects Framework Overview (1) Purpose: To describe name-value pairs such as: – Frequently asked questions (FAQs) – Glossary terms Note: Serves internal DPC needs but could be used by all Core Services

22 Objects Framework Overview (2) Content: Information in the metadata record – Record type (choose either FAQ or glossary term) – Object (the FAQ or term like ‘How do I install the DLESE OAI software?’) – Description (the FAQ answer or term definition) – Library area (broad categorization like governance, metadata, infrastructure) – Topic (specific categorization like OAI software)

23 Objects Framework Overview (3) Technical: – Uses XML schemas to enforce required metadata and controlled vocabularies – Based on DLESE needs

24 Framework Versioning (1) All frameworks are independent of each other even though some have the same fields All controlled vocabularies are individual XML schemas to support use in any DLESE metadata framework Frameworks are under individual version control

25 Framework Versioning (2) New framework versions are issued when – Fields change names – Controlled vocabulary terms are added or deleted – The purpose of a field changes – A field is added/deleted from the framework

26 Framework Devel Tradeoffs (1) Enforcement vs. flexibility (applies to frameworks & the metadata content) All frameworks enforce some required metadata and controlled vocabs. Some frameworks more strongly enforce required metadata and controlled vocabs (ADN and collection) than others (news/opps and object)

27 Framework Devel Tradeoffs (2) Enforcement vs. flexibility (applies to frameworks & the metadata content) Strongly enforced frameworks – Less flexible in coping with change – Metadata content is more reliable for some fields Less enforced frameworks – More flexible in coping with change – Metadata content is less reliable for certain fields

28 Access the frameworks ADN: Annotation: Collection: News and Opps: opps/index.htm Objects: