Skip to end of metadata
Go to start of metadata

CollectionSpace APIs

Your own scripts and programs can create, update, read, list and delete data in a CollectionSpace system, as well as integrate other systems with CollectionSpace, via its Services layer's REST API.

Team Structure and Organization

The original technical/development team was composed of architects and developers from the partner organizations, structured around three main functional areas:

  • UI Team - The Fluid group at the University of Toronto drove the development of tools and widgets that support the user interface.
  • Application Team - CARET at Cambridge University concentrated on the application level, where the UI tools are bound to the services to assemble the end-user application experience.
  • Services Team - The IST-Data Services group from UC Berkeley drove the SOA analysis, modeling and development.

MMI also contributed development resources that applied across the three areas described above.

What are we up to? Where are we going?

CollectionSpace Architecture: UI + Application + Services

The CollectionSpace project is structured around three main functional components: the User Interface component, the Application component, and the Services component.

Component Integration Points and Interfaces

CollectionSpace Development Tools, Environment and Practices

Archived Builds and Releases

  • See the /home/build/releases directory on the host machine.

Meetings, Collaboration and Outreach

The technical team talked at least weekly on a status teleconference hosted by the Services team at UC Berkeley. Larger team meetings are documented in the Project Coordination section. A good deal of our discussions took place on a tech-team mailing list, This list is archived here. In addition, an older archive of our earlier list is available at nabble.

Some other meetings with potential collaborators:

Existing CMS Software: Survey + Functional Analysis