DSpace Architectural Review

Notes from Tuesday, 24 Oct 2006 (JSE)

I. Review of Data Model (Rob)

See also: DSpace Data Model

II. Problems with the Data Model

1. Versioning (Rob)

2. Identifiers

*RECOMMENDATION: Each CONTENT COMPONENT should have some sort of PERSISTENT IDENTIFIER associated with it

3. Metadata Flexibility Options

RECOMMENDATION: Always must be able to CROSSWALK to DC

RECOMMENDATION: Put "whether to keep bundles or not" on Half-Baked list

4. Relational Metadata

5. Content Format Support

6. Aggregation

7. JSR-170

8. Terminology

III. Interfaces and Modularity

1. Review of the APIs (Rob)

2. Pain Points: Enumerating the reoccuring types of mods that break things

3. Are we going to decide to stay with servlets and JSPs

4. Much discussion of the current layering ("Application"/"Business Logic"/"Storage")

5. Overview of the AddOnMechanism (RJ)

6. Summary: What should we be able to do without changing code? (Rob)

7. DSpace Manakin Overview (SP)
See: [ DSpace Manakin Wiki|http://wiki.dspace.org/index.php/Manakin]

*What are the alternatives to Manakin?

8. OSGi Overview (RR)

*What are the alternatives to OSGi?

9. What about Maven? (gt)

*What are the alternatives to Maven?

10. What is our recommendation?

11. Break-time discussion of what level of difficulty refactoring should take on, and how it might be managed...

12. (MS) Attempt at summary