The NSDL Registry Diane Hillmann Jon Phipps. What We’re Doing Received an NSF grant in Oct. 2006,...

The NSDL RegistryThe NSDL RegistryDiane Hillmann Jon PhippsDiane Hillmann Jon Phipps

What We’re DoingWhat We’re Doing

Received an NSF grant in Oct. 2006, to:Register metadata schemas, vocabularies, application profiles for use and re-use by NSDL projects

Support discovery and reuse of vocabularies at all levels

Build generalized functionality able to be used by others

Explore requirements for distributed registry system

Received an NSF grant in Oct. 2006, to:Register metadata schemas, vocabularies, application profiles for use and re-use by NSDL projects

Support discovery and reuse of vocabularies at all levels

Build generalized functionality able to be used by others

Explore requirements for distributed registry system

Where We AreWhere We Are

Functional requirements and specifications complete

Services definedFramework and technical structure defined

Registration process definedVersioning issues identified (and approach determined)

URI Assignments specified

Functional requirements and specifications complete

Services definedFramework and technical structure defined

Registration process definedVersioning issues identified (and approach determined)

URI Assignments specified

Functional RequirementsFunctional

RequirementsUse cases defined for Schemas, Vocabularies, Application ProfilesVocabulary use cases most well developed

Basic user functions definedRegistry search and browseRegistration of vocabulary users Registration of vocabulary owners and developers, top-level vocabularies, vocabulary terms

Use cases defined for Schemas, Vocabularies, Application ProfilesVocabulary use cases most well developed

Basic user functions definedRegistry search and browseRegistration of vocabulary users Registration of vocabulary owners and developers, top-level vocabularies, vocabulary terms

Services DefinedServices Defined

Vocabulary usersRegistration as users of particular vocabularies

Notifications of changes and updates to those vocabularies

Vocabulary owners and developersStatuses defined to support vocabulary development processes

Notifications of registered users Configurable output mechanisms

Vocabulary usersRegistration as users of particular vocabularies

Notifications of changes and updates to those vocabularies

Vocabulary owners and developersStatuses defined to support vocabulary development processes

Notifications of registered users Configurable output mechanisms

Technical FrameworkTechnical Framework

InfrastructurePHP, MySQL

InterfacesUsers and administratorsREST-style web servicesInter-registry data interchange APIs

OutputsSupports the “Cookbook”

Appropriate responses to machines and browsers

InfrastructurePHP, MySQL

InterfacesUsers and administratorsREST-style web servicesInter-registry data interchange APIs

OutputsSupports the “Cookbook”

Appropriate responses to machines and browsers

URI AssignmentsURI Assignments

Assignment is an aggregation of:agentDomain (specified by owner or defaulted to the Registry domain)

vocabularyToken (based on the DC-UB notion of top-level vocabulary identification)

conceptIdentifier (preference for numeric, rather than semantically meaningful)

Ex.: http://metadataregistry.org/registry/NSDLEdLevel/1002

Assignment is an aggregation of:agentDomain (specified by owner or defaulted to the Registry domain)

vocabularyToken (based on the DC-UB notion of top-level vocabulary identification)

conceptIdentifier (preference for numeric, rather than semantically meaningful)

Ex.: http://metadataregistry.org/registry/NSDLEdLevel/1002

Vocabulary Encodings extant

Vocabulary Encodings extant

Based on need for testing “file upload”GEM vocabulariesNSDL Education Level and Learning Resource Type (already registered)

KMODDL Voigt vocabularyAnimal Behavior Vocabulary (Lab of Ornithology)

Based on need for testing “file upload”GEM vocabulariesNSDL Education Level and Learning Resource Type (already registered)

KMODDL Voigt vocabularyAnimal Behavior Vocabulary (Lab of Ornithology)

Versioning (Basic Level)

Versioning (Basic Level)

Tracking all changesPrimarily for administrative purposes, “diffs” will be available to those with admin privileges

HistoryUsers and maintainers will have access to term changes for vocabularies they use or manage

Tracking all changesPrimarily for administrative purposes, “diffs” will be available to those with admin privileges

HistoryUsers and maintainers will have access to term changes for vocabularies they use or manage

Versioning (Beyond Basics)

Versioning (Beyond Basics)

Snapshots of defined “versions”Versioning needs defined by ownersUseful only for some vocabularies, and as a possible transition between development and “cooked”

Some changes to terms defined as “semantically significant” will require new URIs for terms

Snapshots of defined “versions”Versioning needs defined by ownersUseful only for some vocabularies, and as a possible transition between development and “cooked”

Some changes to terms defined as “semantically significant” will require new URIs for terms

Supporting Vocabulary Quality Review

Supporting Vocabulary Quality Review

Defining semantic significanceYes: changes in hierarchical placement for vocabularies where hierarchy is significant

No: changes in definitions that are primarily cosmetic

Automated validation and error detectionEx.: duplicate prefLabels, conflict conditions for altLabels and prefLabels, lack of expected reciprocity in relationships, etc.

Defining semantic significanceYes: changes in hierarchical placement for vocabularies where hierarchy is significant

No: changes in definitions that are primarily cosmetic

Automated validation and error detectionEx.: duplicate prefLabels, conflict conditions for altLabels and prefLabels, lack of expected reciprocity in relationships, etc.

Additional Quality Supports

Additional Quality Supports

Assisted error resolutionNotifications of error conditions

Appropriate documentationHelpdesk functionality

Support for community vocabulary developmentStatus at the term levelVocabulary browse with filters

Assisted error resolutionNotifications of error conditions

Appropriate documentationHelpdesk functionality

Support for community vocabulary developmentStatus at the term levelVocabulary browse with filters

DemonstrationDemonstration

User/Agent registrationTop-Level Vocabulary registration

Additions of concepts, and propertiesReciprocalityReadability

Administrative functions

User/Agent registrationTop-Level Vocabulary registration

Additions of concepts, and propertiesReciprocalityReadability

Administrative functions

From here ...From here ...

File upload adding already encoded vocabularies

Change history and versioningNotificationsDocumentation and helpInterface refinementsUser testing

File upload adding already encoded vocabularies

Change history and versioningNotificationsDocumentation and helpInterface refinementsUser testing

After that ...After that ...

Metadata SchemasTest non-hosted interactions

Application ProfilesThe Middle Kingdom

CrosswalksVocabulary mappings

Metadata SchemasTest non-hosted interactions

Application ProfilesThe Middle Kingdom

CrosswalksVocabulary mappings

Schemas & APsSchemas & APs

Metadata SchemasDCMI Registry is the basic model“Recommends” vocabularies but is clearly agnostic about usage

Application profiles Includes usage information: obligations, constraints, etc.

May link to content standards, guidelines

Registry needs to support both human and machine-readable versions

Metadata SchemasDCMI Registry is the basic model“Recommends” vocabularies but is clearly agnostic about usage

Application profiles Includes usage information: obligations, constraints, etc.

May link to content standards, guidelines

Registry needs to support both human and machine-readable versions

Working DocumentsWorking Documents

Registry Working DocumentsVersioninghttp://metadataregistry.org

Registry Working DocumentsVersioninghttp://metadataregistry.org

The Metadata Management System

The Metadata Management System

The problem at GEMGEM is essentially an aggregation, with multiple partners

No “back end” for managing metadataMultiple methods for collecting data

Manual methodologies for augmentation and transformation

Legacy data requiring updatingNew partnerships to incorporate

The problem at GEMGEM is essentially an aggregation, with multiple partners

No “back end” for managing metadataMultiple methods for collecting data

Manual methodologies for augmentation and transformation

Legacy data requiring updatingNew partnerships to incorporate

What the MMS doesWhat the MMS does

Provides a cost-effective and efficient method for managing metadata from a variety of sourcesManages data exchange and updatingRationalizes routine and collection-specific transformations

Provides basis for provision of other services (search, etc.)

Provides a cost-effective and efficient method for managing metadata from a variety of sourcesManages data exchange and updatingRationalizes routine and collection-specific transformations

Provides basis for provision of other services (search, etc.)

Broader ApplicabilityBroader Applicability

Support aggregation of metadata from institution-specific content “silos” to improve searching (a metasearch strategy)

Simple collection-item structure supports a “digital collection” registry

MMS development includes a “service orchestration” component, allowing automated management of service interactions

Support aggregation of metadata from institution-specific content “silos” to improve searching (a metasearch strategy)

Simple collection-item structure supports a “digital collection” registry

MMS development includes a “service orchestration” component, allowing automated management of service interactions

OverviewOverview

Operates as a service registry

Manages information necessary for harvesting and managing data from a particular collection “service”

Information available for update by service itself or by system administrator

Operates as a service registry

Manages information necessary for harvesting and managing data from a particular collection “service”

Information available for update by service itself or by system administrator

Harvest HistoriesHarvest Histories

Visible information by harvest, with links to log information

Lists validation checksOptimized for problem solving by non-technical staff

Visible information by harvest, with links to log information

Lists validation checksOptimized for problem solving by non-technical staff

Item DetailItem Detail

Supports review of individual items within collections

All version of the item, from initial harvest through various transformations, available for viewing

Optimized for problem solving by non-technical staff

Supports review of individual items within collections

All version of the item, from initial harvest through various transformations, available for viewing

Optimized for problem solving by non-technical staff

Individual Metadata Record

Individual Metadata Record

Qualified Dublin Core expression

Editable (in theory) but in practice not (would be stepped on by next harvest)

Qualified Dublin Core expression

Editable (in theory) but in practice not (would be stepped on by next harvest)

Working DocumentsWorking Documents

http://metadataregistry.org/wiki/index.php/Metadata_Management_System

http://metadataregistry.org/wiki/index.php/Metadata_Management_System