CollectionSpace Release 0.1

Codename: Hello World

Release Date: June 2009

Release 0.1 Information

Functionality Goals

• User: Enter and save object data. Limited to text and non-complex numerical fields.
• User: Create new object from limited version of create new page
• User: View list of objects in repository
• User: Edit existing objects

UI Designs

Create new records (partial)
Object record - basic information

Architecture

Services Consumed

CollectionObject Service (supporting a subset of the Object Identification Information group in the Object Entry Schema)

CollectionSpace Release 0.2

Codename: Mars

Release Date: September 2009

Release 0.2 Information

Functionality Goals

• User: User Can Log in by Providing a Username and Password
• User: Create New Intake Record
• User: Find Edit Landing Page - Object or Intake
• User: Create New Landing Page - Object or Intake
• Auto: Create New Object Records with Auto-filled Identification Number
• Auto: Create New Intake Records with Auto-filled Entry Number

UI Designs

Login page
Create/edit intake record
Create/edit object record
Create new landing page
Create New Object flow
Find/edit landing page

Style guide: standardize appearance/use of buttons

Schema

CollectionObject
Intake

Architecture

• First version of the new DataContext for CRUD operations between client and app
• App integration with services
• Working JavaScript, HTML, and uiSpec for additional functionality
• Application layer plugin format draft

Services Consumed

CollectionObject Service
ID Service
Intake Service
Authentication Service

CollectionSpace Release 0.3

Codename: Venus

Release Date: November 2009

Release 0.3 Information

Functionality Goals

• User: Create New Acquisition Record

• User: Create New Object Record with Choice of Identification Number Patterns
• User: Create New Intake Record with Choice of Entry Number Patterns
• User: Create New Acquisition Record with Choice of Acquisition Number Patterns

• User: Select Item from Entry Method Term List (Intake)
• User: Select Item from Entry Reason Term List (Intake)
• User: Select Item from Responsible Department Term List (Object)
• User: Select Item from Acquisition Method Term List (Acquisition)

• Admin: Configure a Flat Vocabulary for Use With a Field - XML

UI Designs

Find/edit main page
Create/edit object record
Create/edit intake record
Create/edit acquisition record
Choose term from controlled list - uses dropdown wireframe
Choose pattern number for ID - uses select pattern wireframe

Schema

CollectionObject
Intake
Acquisition

Architecture

• Full-stack label customization support
• Support for unbound properties (configuration without touching HTML)
• Complete DataContext support for mapping model paths to URL space
• Working JavaScript, HTML, and uiSpec for additional functionality
• Live configuration to uiSpec generation, including JSONP and preliminary support for configurable form labels
• Creation of "hooks": a way of specifying where new fields should be injected into the UI in cases where the user hasn't hand-edited any HTML
• Rough support for injectable HTML (from plugins)

CollectionSpace Release 0.4

Codename: Mercury

Release date: January 20, 2010

Release 0.4 Information

Functionality Goals

Note about below user stories: Procedural Records in 0.4 refers to Intake and Acquisition, but functionality should apply to all procedures developed in the future (e.g. loans in, loans out, movement, conservation, etc.). Similarly, the Name Authority developed for 0.4 is the only Organizational Record, but the functionality should be the same for the rest e.g. additional vocabularies (location, collecting event), media support records, and collections.

Search via Find/Edit

• User can perform a keyword search, limited by record type
  • Search for CollectionObject Records
  • Search for Intake Records
  • Search for Acquisition Records

• User can view search results
  • View Search Results

Relationships Among Records

• User: View all related records (via right sidebar)
  • View Related Object Records from Procedural Record
  • View Related Procedural Records from Object Record
  • View Related Procedural Records from Procedural Record

• User: Pivot between related records (via right sidebar)
  • Pivot from Object Record to Related Procedural Record
  • Pivot from Procedural Record to Related Object Record
  • Pivot from Procedural Record to Related Procedural Record

• User: Add Existing Name Authority Term to a Record
  • Add Existing Name Authority Term to Object Record
  • Add Existing Name Authority Term to Procedural Record

Special Fields

• User: Add Dimensions to an Object Record
• User: Add a Calendar Date to a Procedural Record

System Messages

• User: Save Warning

Schema

CollectionObject
Intake
Acquisition
Name Authority

UI Designs

Find/edit main page - uses find and edit landing page and search wireframes
Search results - uses search results
Create new main page - uses create new landing page
Sysadmin main page - uses admin wireframes
User profile management - uses admin wireframes
Name authority data entry - uses name authority wireframes
Vocabulary add (within record) - uses predictive text wireframe
Right sidebar - uses sidebar wireframe
Dimensions - uses dimension wireframe
Calendar date - uses [to be posted]
Location and movement record page - uses location and movement control wireframes
Object tab on procedural records - uses object tab wireframes
Login and "forgot password" sequence - uses login wireframes

Architecture

CollectionSpace Release 0.5

Codename: Jupiter

Open coding: January 22 - February 19
Feature freeze: February 22 - February 26
Code freeze / QA: March 1 - March 4
Release date: March 4, 2010

Test URL: http://jupiter.collectionspace.org:8180/cspace-ui/html/

Object Tab

• View Object Information from Procedural Record - Object Tab
• Search for Object Record from Procedural Record - Object Tab
• Create New Object Record from Procedural Record - Object Tab
• Edit Object Information from Procedural Record - Object Tab

Relationships Among Records

• User: Add relationships between existing records
  • Add Relationship Between Existing Object and Procedural Records
  • Add Relationship between Existing Procedural Records
  • Add Relationship Between Existing Procedural and Object Records

• User: View all related records (via right sidebar)
  • View Related Object Records from Name Authority Term Record
  • View Related Procedural Records from Name Authority Term Record

• User: Pivot between related records (via right sidebar)
  • Pivot from Object Record to Related Name Authority Term Record
  • Pivot from Procedural Record to Related Name Authority Term Record
  • Pivot from Name Authority Term Record to Related Object Record
  • Pivot from Name Authority Term Record to Related Procedural Record
  • Pivot from Name Authority Term Record to Related Name Authority Term Record

Related Records

• User: Create new records from existing records via Right Sidebar
  • Add New Procedural Record from Object Record - Right Sidebar
  • Add New Object Record from Procedural Record - Right Sidebar
  • Add New Procedural Record from Procedural Record - Right Sidebar

• User: View related records (via right sidebar)
  • View Integrated Authority Records from Object Record
  • View Integrated Authority Records from Procedural Record
  • View Integrated Authority Records from Name Authority Term Record

Vocabulary

• Admin can create a new Person namespace
• Add New Name Authority Term to Object Record
• Add New Name Authority Term to Procedural Record
• Add New Name Authority Term via Create New
• Search for Name Authority Term via Find Edit
• View and Edit Name Authority Term Information

Admin

• Access Administrator Main Page
• Admin Can Create a New User
• Admin Can Update a User
• Admin Can Deactivate a User
• Admin Can Delete a User
• Admin Can Search for User(s)
• User Can Reset Password

Customization

Tools and basic documentation sufficient to customize a schema and make the associated changes appear in the user interface: "A user contacts Museum IT to ask for a label to be changed (or some other property of a field such as the way it is indexed for a search), or a field to be added and the IT department can do this quickly by a reasonably junior member of the IT staff using a text editor to edit a few simple files."

Schema
Name Authority
User Profile
Acquisition

UI Designs

• Find/edit main page - uses find and edit landing page and search wireframes.
• Create new main page - uses create new landing page
• Sysadmin main page - uses admin wireframes
• User profile management - uses admin wireframes
• Name authority data entry - uses name authority wireframes
• Vocabulary add (within record) - uses predictive text wireframe
• Calendar date - uses [to be posted]
• Location and movement record page - uses location and movement control wireframes
• Object tab on procedural records - uses object tab wireframes
• Login and "forgot password" sequence - uses login wireframes

CollectionSpace Release 0.7

Codename: Saturn

Open coding: 3/8 - 4/9
Mid-term integration: 3/29
Feature freeze: 4/12
Bug parade: 4/19
QA + Release: 4/26-4/30

Procedures

• User can create/edit a loans in record
• User can create/edit a loans out record

Admin

Roles and Permissions/Authentication - Interface

• Admin can create a new role
  • Admin can create a new role allowing no access / read / write / delete at the record level
  • Admin can create a new role allowing read / write / delete at the field level
  • Admin can create a new role allowing read / write / delete at the vocabulary level
  • Admin can create a new role allowing "authorization" at the vocabulary term level
• Admin can assign one or more roles to a user
• Admin can remove one or more roles from a user

Special Fields

Structured Dates

• User can add structured dates via the Spectrum date units of information

Repeatable Fields

• User can add one or more instances of a field
• User can add one or more instances of a group of fields
• User can delete one or more instances of a field
• User can delete one or more instances of a group of fields
• User can group together fields or groups of fields (e.g. dimensions)

Primary Fields

• User can designate one value of a repeated field as the "primary" value

Currency

• User can add currency value and denomination to a record

Vocabularies

• User can create a new place authority term record

• User can add a term to a hierarchical vocabulary
• User can add a provisional term to a vocabulary
• User can authorize the addition of a new term to a vocabulary

Mid-term Integration

Procedures

• User can create a new location and movement control record

Media Handling

• User can create a new media record
• User can upload media to a media record (image, audio, video)

Admin

Roles and Permissions/Authentication - Runtime

• Admin can create a new role
  • Admin can create a new role allowing no access / read / write / delete at the record level
  • Admin can create a new role allowing read / write / delete at the field level
  • Admin can create a new role allowing read / write / delete at the vocabulary level
  • Admin can create a new role allowing "authorization" at the vocabulary term level
• Admin can assign one or more roles to a user
• Admin can remove one or more roles from a user

Search

• Search results will be persistent on search results page when user leaves page and returns

Advanced Search

• User may perform an advanced search, limited by record type
• User may view results of advanced search in a list or hierarchy
• User may sort columns in search results list

Vocabulary

• User can create a new storage location authority term record

Special Fields

Parts, Sets, Ranges

• User can add child records
• User can assign a parent record
• User can create sibling records
• User can view records in a hierarchy

Customization

Full-stack label-customization support: "An integrator can provide a file containing a list of customized text for the UI labels (e.g. "Descriptive Notes" instead of "Brief Description," or language translations), and the system will automatically use those labels instead of the defaults."

Creation of "hooks" (a way of specifying where new fields should be injected into the UI in cases where the user hasn't hand-edited any HTML): "A tenacious, reasonably technically aware user in a small museum without much dedicated IT staff can quickly add a field just by adding a line or two to a single file, to be tidied up later by an editor, but can get on with their job in the meantime."

Support for unbound properties (configuration without touching HTML)

Documentation

Help
[User Documentation]
Setup and Install Documentation

Schema

Acquisition Schema
Cataloging Schema
[Date Schema]
Intake Schema
Loans In Schema
Loans Out Schema
[Location and Movement Control Schema]
[Media Handling Schema]
[Place Authority Schema]
[Storage Location Schema]

UI Designs

Wireframes - Loan
Wireframes - Location and Movement Control
Wireframes - Administration - Roles and Permissions for Roles and Permissions
Wireframes - Search
Wireframes - Search Results
Wireframes - Date information for Fuzzy Dates

CollectionSpace Releases 0.8 and 0.9

Codenames: Neptune and Pluto

Release Goal: May 2010

Functionality Goals

Procedures
Object Exit

Functions
Batch Processing
Import and Export
Reporting
Audit Trail
Collections Exposure
Create from Existing
Template
Dashboard
Group

Vocabulary
Collecting Event Authority
Exhibition Authority
+ Any other vocabulary needs to support initial deployments

Documentation
Help
User Documentation
Setup and Install Documentation
Propagation

CollectionSpace Release 1.0

Release Goal: June 2010

ALL OF THE ABOVE