Skip to end of metadata
Go to start of metadata

Important Info:

Detailed info on Release Process phases.

Main Drivers

The main drivers for CollectionSpace 1.0 are:

  • Deliver functionality described in the grant proposal to the Andrew Mellon Foundation.
  • Fix bugs and improve performance.
  • Demonstrate to the larger community that CollectionSpace is an operational system.

Release Definition

This release will be a continuation of the previous releases and will include these additional features, enhancements, and schema changes

Repeatable Fields

Some fields and groups of fields will be repeatable. In other words, the user will be able to create additional versions of a particular field as they need them.

User Stories

Wireframes

Schema

There are two groups that will be repeatable in 1.0 Alpha:
Cataloging
> Object name
> Object name currency
> Object name level
> Object name note
> Object name system
> Object name type
> Object name language
Acquisition
> Acquisition funding - denomination
> Acquisition funding - value
> Acquisition funding source
> Acquisition funding source provisos

The development work for the rest of the groups that are indicated as being repeatable will occur during the Alpha phase prior to Beta. Upon review, four additional fields need to be made scalar repeatables, one missed by the Services team and three identified by the functional team. This work was done in the services layer, and submitted to the app layer, late on August 25.

Location and Storage

User Stories

Wireframes

Schema

Vocabularies I
  • 2189 - User selects destination of a newly added term - this could be added to the existing pop up, the wireframes are in the wiki
  • Pagination
Date Enhancement

A user can use the existing date picker, or type directly into that field a date of their choosing.  The field will be validated against ISO standards, *plus* any additional date formats that are configured as 'valid' for a tenant. So a tenant could, for instance, say that US-style dd/MM/yyyy dates, like 08/24/2010 (or 8/24/2010 - leading zeros are optional) are valid, or that those plus the date picker's current MMM dd, yyyy dates, like Aug 24, 2010, are both valid.  Services has configured the two current tenants to support both those formats, in addition to the set of ISO formats that Nuxeo knows about.

Dimensions

Dependencies

Rhino - an open-source implementation of JavaScript written entirely in Java, which uses an MPL license
Jasper - an open-source reporting tool, which uses LGPL license.

JBoss with Nuxeo 5.3.2

Risks to the Schedule

  • The UI development team will decrease by 0.5 people during the last half of August, and will lose additional development time which equals 1 person in September.
  • A developer on the Services team who is currently devoting 100% of his time to the project, may have to decrease his time on the project if we do not get an additional grant that has been applied for.

Timeline:

July 1: Planning and open coding
August 3: Feature freeze
August 26: UI and Services Code freeze
August 30: App Layer Code freeze, begin QA on new 1.0 functionality
End of day Pacific, Sept 3: All 1.0a Blocker Bugs need to be fixed.  Currently, there are 9 blocker bugs.  CSPACE 2641 is a very high priority bug because it prevents us from creating new users and testing roles and permissions.  You can also fix other bugs and check in code, that is great, but the priority is fixing blocker bugs.
Sept 6: Labor Day in the US and Canada - App layer will have an extra day to check in code.
Sept 7 - 10: No checking in code.  We will freeze and QA all new 1.0 functionality in all 4 browsers, and run through all functionality in whatever browser is available to the QA testers. 
Sept 13: 1.0 moves to Alpha.  The only kind of bug that would prevent us moving forward with alpha would be a very serious bug like CollectionSpace causes the blue screen of death or causes your hard drive to reformat - something that would cause our implementers harm.  Otherwise, they know that if they choose to download alpha software, it's buggy and not fully functional.  During this phase implementers will be able to start importing data into the new schemas in 1.0, and we will focus on fixing bugs and improving performance.
Oct 5 - Oct 19*: No checking in code. We will freeze and test everything in every browser.  This way we can know that our 1.0 release is of high quality.
Oct 20 - 22: the team will be at the All Hands meeting in Berkeley, CA.
Oct 25*: 1.0 is released.

* These dates are tentative.  We still have some issues to resolve.

Implementer testing of 1.0 - We will ask implementers to load data into 1.0, go through some typical tasks that they perform as a part of their jobs, perform some tasks that the CollectionSpace team have outlined, and provide us with feedback.  Megan will be the point person for implementers for these activities.

Performance Testing - This has been put off to 1.1

Current Status:

The features for 1.0 alpha:

Feature

Service

Application

UI

Repeatability

Done 

Done

Done

Roles and Permissions

Done

Needs Investigation

0.5 days

Location and Movement procedure

Done

Done

Done

Location and Movement tab

NA

NA

Done

Vocab

Done

Done

Done

Search pagination

Done

Done

Done 

Dates - free text dates 

Done

Done

1.5 days

Dimensions

Done

Done

Done

QA Test Plans

Testing Tasks for 1.0a