About Us

The CollectionSpace Services Team is one of three distributed Technical Teams working on the CollectionSpace project. This team comes from the IST-Data Services group at U.C. Berkeley, which is driving services oriented architecture(SOA) analysis, modeling and development. Patrick Schmitz is the technical lead for this work. Much of the email discussion around services design and definition takes place on the SOA-Tech mailing list (when it is not on the broader tech or work lists).

The CollectionSpace Service Layer

An overview of the services currently available in the CollectionSpace Service Layer.

CollectionSpace Services - Technical Documentation

• Service Description Repository
  Formal definitions of the services that make up CollectionSpace's services layer.
  Includes implementation and testing plans, and identifies the current status of work on each service.

  • Recently Updated

    • Common Services REST API documentation
      updated by Aron Roberts
      (view change)
      Mar 27, 2013
    • Common Services REST API documentation
      updated by Rick Jaffe
      (view change)
      Dec 28, 2012
    • Vocabulary Service Contract Description
      updated by Aron Roberts
      (view change)
      Apr 06, 2012
    • Place Service Description and Assumptions
      updated by Rick Jaffe
      (view change)
      Mar 29, 2012
    • Place Service Home
      updated by Chris Hoffman
      (view change)
      Mar 29, 2012
    • More 

Development Planning and Tracking

• Development Status Meeting Notes
• Service Creation - Phases

Attached documents identifying work assignments among the team's members:

Design Meetings

• Topics for Future Design Meetings
• Design Meeting Notes

Risks and Issues

This is a place for project-wide risks and issues.

Technical Risks and Issues

1. We need more detailed user-stories/use-cases to create sprint tasks
2. Nuxeo Integration

Project Management Risks and Issues

1. Sprint task tracking in Jira - will it work?
2. We have only part-time project management support, so overhead needs to be low.

Other Technical Documentation

• Functional Requirements - CollectionSpace
  Formal definitions of the services that make up CollectionSpace's services layer.
  Includes implementation and testing plans, and identifies the current status of work on each service.
• Candidate Services and Related Notes
  A "parking lot" for brief descriptions of proposed ("candidate") services. Some of these services have already been formally defined in the Service Description Repository, while others are under consideration for further definition.
• Services Architecture
  A description of our methodologies for the services architecture.
• Misc. Design and Implementation Notes
  Descriptions and documentation for some of our key design and implementation decisions, discussions, and related issues.
  • How to documents

    Recently Updated

    • Common Services REST API documentation
      updated by Aron Roberts
      (view change)
      Mar 27, 2013
    • Common Services REST API documentation
      updated by Rick Jaffe
      (view change)
      Dec 28, 2012
    • Common Services REST API documentation
      updated by Patrick Schmitz
      (view change)
      Nov 15, 2011
    • Common Services REST API documentation
      updated by Laramie Crocker
      (view change)
      May 19, 2011
    • Common Services REST API documentation
      updated by Joe Slag
      (view change)
      Mar 31, 2011
    • More 
• Development Tools, Environment, and Coding Standards
• Services Build
  A description of the tools and platforms we will be using to implement the service contracts. Also a description of our development methodologies.
• Service Documentation Repositories