On December 18th (Tuesday), Wikihub will be unavailable from 7-9am.
Skip to end of metadata
Go to start of metadata

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA and UCJEPS have some broad requirements though we need to get more detail on what is needed on day one and what they can do now.

Overview

Batch processing is related to saved sets and allows users to perform actions on a group of objects that have been previously identified. Examples are needed.  We know that for current systems, some batch processing operations are performed by programmers while others can be performed in the system.

Per 10/20 meeting: UCJEPS often batch processes from spreadsheets with 1,000 items and anticipates this will not change.  In this case, they are talking about batch importing a set of objects from a spreadsheet.  A user story will be added to the data import page.

User stories for definition

Please feel to rewrite these or eliminate completely!  Then move to the prioritized headings below.

PAHMA batch processing user stories

Batch processing: For a saved set of objects, user can associate each record with an exhibit.

Batch processing: For a saved set of objects, user can apply a note to all records in the set.

Batch processing: For a saved set of objects, user can initiate a loan out transaction.

Batch processing: For a saved set of objects, user can initiate a research visit transaction.

UCJEPS batch processing user stories

Batch processing: For a saved set of objects, user can change the scientific identification of the specimen.

Batch processing: For a saved set of objects, user can create an identical treatment record (e.g., all specimens returning from loans are frozen).

Batch processing: For a saved set of objects, user can initiate a loan out transaction.

Prioritization of user stories

As definitions and priorities are clarified, the user stories above should be moved into relative order below.

Must have for 1.x-PAHMA or 1.x-UCJEPS (when museum goes live in system)

Placeholder for required functionality.  As a general rule, functionality that you need and use now should go here or where you have existing data.  However, this is up to the museum.  We will have to balance requirements against resources and timelines.

Placeholder

Must have for a subsequent version of CollectionSpace

What could wait?  These will be re-prioritized at a later date.

Placeholder

Not needed

Just in case we included something not needed, you could move it down here!

Placeholder

  • No labels