Difference between revisions of "University of Rochester eXtensible Catalog Project"

From Metadata-Registry
Jump to: navigation, search
Line 5: Line 5:
  
 
====OAI server====
 
====OAI server====
====OAI harvester====
+
* Must provide a single simple data API designed to support drop-in, plug-in data connectors.  
=====Overview=====
+
The integrated OAI harvester is designed to be flexible and forgiving in its handling of common metadata validation errors, allowing otherwise invalid multi-record metadata harvests to be processed on an individual record basis, rejecting only records that can't be processed, and logging the results. Upon completion of a harvest, these error logs are passed to the notification service, and registered Service administrators or technical contacts that have signed up for event notification will receive an email or a notice in their RSS feed. They'll then have the opportunity to correct or delete the invalid records and schedule an immediate one-time incremental harvest to retrieve them for addition to the MR data store.
+
* The server provides a single simple data API designed to support drop-in, plug-in data connectors.  
+
 
* Must support any number of data connectors and can use them to aggregate data from multiple sources into a single feed
 
* Must support any number of data connectors and can use them to aggregate data from multiple sources into a single feed
 
* Can provide data from specific data sources in response to request for specific collections or metadata formats.
 
* Can provide data from specific data sources in response to request for specific collections or metadata formats.
 +
====OAI harvester====
 +
* Must be flexible and forgiving in its handling of common metadata validation errors, allowing otherwise invalid multi-record metadata harvests to be processed on an individual record basis, rejecting only records that can't be processed, and logging the results.
 
====OAI testing service====
 
====OAI testing service====
 
* Provide a comprehensive remote acceptance test suite that fully tests the functionality of a compatible OAI server.  
 
* Provide a comprehensive remote acceptance test suite that fully tests the functionality of a compatible OAI server.  
Line 21: Line 20:
  
 
====Service Orchestration (ping, ordering, notification)====
 
====Service Orchestration (ping, ordering, notification)====
 +
* Upon completion of a harvest, error logs are passed to the notification service, and registered Service administrators or technical contacts that have signed up for event notification will receive an email or a notice in their RSS feed.
 +
* Technical contacts will have the opportunity to correct or delete the invalid records and schedule an immediate one-time incremental harvest to retrieve them for addition to the MR data store.
 
====Hub Raw Data browser====
 
====Hub Raw Data browser====
 
====Hub Identifier management (record, resource, relationships)====
 
====Hub Identifier management (record, resource, relationships)====

Revision as of 07:00, 12 December 2007

University of Rochester eXtensible Catalog Project

HUB Deliverables

OAI server

  • Must provide a single simple data API designed to support drop-in, plug-in data connectors.
  • Must support any number of data connectors and can use them to aggregate data from multiple sources into a single feed
  • Can provide data from specific data sources in response to request for specific collections or metadata formats.

OAI harvester

  • Must be flexible and forgiving in its handling of common metadata validation errors, allowing otherwise invalid multi-record metadata harvests to be processed on an individual record basis, rejecting only records that can't be processed, and logging the results.

OAI testing service

  • Provide a comprehensive remote acceptance test suite that fully tests the functionality of a compatible OAI server.
  • Provide a set of test data that can be accessed from the remote test suite to ensure that the server is correctly serving a known and correct set of data to compare and isolate data source problems form the server itself.

Services Registry (includes db and admin interface)

Mudball & Gold schema design

Database design

Shredding (QDC, OAIDC, MARCXML)

Reassembly (Mudball)

====

Service Orchestration (ping, ordering, notification)

  • Upon completion of a harvest, error logs are passed to the notification service, and registered Service administrators or technical contacts that have signed up for event notification will receive an email or a notice in their RSS feed.
  • Technical contacts will have the opportunity to correct or delete the invalid records and schedule an immediate one-time incremental harvest to retrieve them for addition to the MR data store.

Hub Raw Data browser

Hub Identifier management (record, resource, relationships)

LC authority to OAI service


User Roles

[

Human Actors

  • System Administrator
    • Overall system administrator. Responsible for system-level software and hardware maintenance
  • HUB Manager
    • One or more persons responsible for the administrative tasks involved in the management of a HUB instance
    • Authorizations: Service Administrator for all registered Services Editor for all Collections and Metadata [not sure about this one]
    • Only role authorized to Delete Services, Users, and Collections
  • Service Administrator
    • One or more persons authorized to maintain one or more Service records. The user who registers a Service becomes the Service Administrator for that Service
    • Authorizations:
      • Service Administrator for all Services owned by that Agent
      • Edit/Delete Service Records
      • Designate other Registered Users as Service Contacts
      • Register Contacts and designate them as: Service Administrators for that Agent or Technical Contacts for that Agent
  • Service Primary Contact
    • One or more persons acting on behalf of a Service, to whom notifications to the Service may be sent.
    • Domain of email address must match the domain registered to that Service
  • Service Technical Contact
    • One or more persons acting on behalf of a service, to whom technical notifications to the Service may be sent.
  • Registered User
    • A Visitor who has registered himself/herself for the purpose of registering an organization or vocabulary. A Registered User may assume an additional role while registering an organization or service. **[




Archive Page