Difference between revisions of "University of Rochester eXtensible Catalog Project"
From Metadata-Registry
(→Main Decision Points) |
|||
| Line 22: | Line 22: | ||
==== Main Decision Points ==== | ==== Main Decision Points ==== | ||
| − | # | + | #Determine functional requirements |
| + | #Refactor Collection Registry to Service Registry | ||
| + | #ReBuild repository database | ||
#* Determine what database to use | #* Determine what database to use | ||
| − | #* | + | #* Rewrite database interfaces |
| − | # | + | #Rewrite OAI Harvester/Server software |
| + | #Write Round-trip service management | ||
| + | #Write error handling and notification | ||
Revision as of 09:35, 16 October 2007
Contents
University of Rochester eXtensible Catalog Project
Stage I: Enabling XC use of MMS software
See: Re-Implementing the MMS for one scenario
What we have now
Collection Registration Service
- Function: Register and describe Collections, DC metadata editor, OAI harvest manager, metadata cache browser
- Technology: PHP/MySQL
OAI harvester
- Function: harvest OAI data, driven by cron
- Technology: Perl
Safe Transforms Service
- Function: gather harvested data, transform & clean, insert into database
- Technology: Java/Tomcat
Metadata Repository (cache)
- Function: Shred and store Qualified DC XML (other formats stored as text blobs)
- Technology: Oracle 9i, PL/SQL
OAI Server
- Function: Serve OAI
- Technology: Java (custom version of OAIcat from OCLC)
Main Decision Points
- Determine functional requirements
- Refactor Collection Registry to Service Registry
- ReBuild repository database
- Determine what database to use
- Rewrite database interfaces
- Rewrite OAI Harvester/Server software
- Write Round-trip service management
- Write error handling and notification
