Project Notebook

1-Feb-2000

31-May-2000

• Survey of similar systems and potential collaborators.
• List of commercial systems that might be applicable or have useful components.
• Resources on the web -- bookmarks of relevant documents and other projects.
• Lead user study and identification
• Team staffing competency model
• The team membership fully staffed.
• Initial, skeletal architectural specification
• List of areas which will need discovery or improvement.
• Detailed project data sheet.
• Initial, skeletal requirements document.
• detailed project schedule.
• inhabitable space for team established.

• Hold meetings to brainstorm and evaluate:
  • sources of relevant ideas and technologies.
  • potential collaborators.
  • sources of lead users.
• Draft, Revise, and Publish the documents that comprise the deliverables.
• Think about testing issues.

31-May-2000

~31-Aug-2000

• Complete architectural specification.
• Complete software design specifications.
• Specifications for user documentation.
• Training specifications.
• Complete test plans: component tests, integration tests, and sytem tests.

• Investigate and measure whether which if any of the systems or components in the list of commercial systems is applicable.
• Obtain a small server for prototyping explorations.
• Prototype an Oracle-backed web server with some of the ARS-Digita tools and assess the applicability of this implementation technology.
• Visit potential collaborators.
• Visit sources of relevant ideas and technologies:
  • HP Corvallis.
• Visit potential lead users.
• Design the infrastructure aspect of the system.
• Choose lead users and engage them in specifying and designing end-user services.
• Draft, Review, Revise and Publish the documents that comprise the deliverables.

31-Aug-2000

15-Dec-2000

• repository with these functions:
  • allow submission from select few
  • allow access from MIT/HP only
  • Open Archives metadata
  • hooks for searching
  • hooks for access control
• Continuity policy document.

• Identify and prepare to support most widely useful formats.
• Address metadata standards issues.
• Obtain server hardware to be used for Version 0 roll-out.
• Code version 0 of the architecture.
• Prototype the end-user services, coding to the Version 0 infrastructure.

15-Dec-2000

~31 May 2001

• revised software design specifications
• revised specifications for user documentation
• revised training specifications
• revised test plans: component tests, integration tests, and sytem tests.
• business plan for taking the system beyond version 1 roll-out to ongoing service and support as part of MIT infrastructure.

• Obtain hardware to amend version 0 server to version 1 requirements.
• Meet with lead users. Review and revise end-user services. Confirm architecture is adequate to present and planned use.
• Amend architecture, requirements, specification, testing and other documents appropriately to specify version 1.
• Attempt small-scale use of the version 0 infrastructure by lead users.
• Formulate appropriate outreach to new communities based on experience with Version 0.
• Build credibility of the project team and the infrastructure.

~31 May 2001

31 Aug 2001

• New functionality:
  • submission "realms"
  • system available outside MIT/HP
  • rights management framework
  • publishing/printing capabilities
  • metadata to RDF standards
  • metadata "realms" to complement submission
  • searching

• Code and test version 1 amendments to system.
• Confirm that lead user small-scale experiences have been successful and that they are on board for production use.
• Demonstrate production use by lead users to potential new users of the system.
• Code new end-user services for new communities of users.
• Get business plan accepted and funding in place for ongoing operation.