Revision as of 11:45, 8 November 2005

Re-Implementing the MMS for GEM

Phase I

Current implementation has very tight ties to an Oracle database. For new, generalized MMS, the functions need to be more abstract, in order to work with any database. The internal user management systems were handed off to an external service in the original implementation. In the re-implementation, roles and rights for users need to be abstracted to work either wholly within the MMS or linked to an external user authentication system.

1. New implementation of the main Repository database
   • Currently based on Oracle 9i. We need to decide whether to go with Oracle's new release (10g called 'Express Edition') which is open-source, or switch to MySQL. Regardless of which is chosen for the first re-implementation, the code will be developed to make that decision a local one, with the MMS working with any database.
2. New implementation of the internal management database
3. Abstracting user and service management and adding to internal management database (using registry model)
4. Setup of simple services structure (similar to Recommender)
5. Implement new harvester

Phase II

1. Re-implementing the MMS OAI server (exising server needs to have data backend made more abstract to deal with any data schema or source)
2. Adjust the metadata editor to accommodate any metadata schema and work with the simple services structure
3. Implement services registry on top of existing components (user management and repository)
4. Implement error handling and notifications
5. Setup safe transformation service, generalized to any repository

Phase III

1. Implement harvest diagnostics and helpdesk functionality
2. Implement distributed GEM community services (includes OAI server capable of working on many platforms, plugin data connections, etc.)
3. Implement comprehensive evaluation and test suite, validity checkers

Phase IV

1. Implement metadata augmentation, improvement and rating services
2. Non-OAI data services
3. Secure OAI services