Batch processing

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.  We know that for current systems, some batch processing operations are performed by programmers while others can be performed by the user in the system.  Note that in this usage, batch processing refers to operations on existing objects in the system.  For creating a batch of new records from a data file, seethe data import page.  For bulk loading of image records and/or image files, see the bulk load images and metadata page.

Batch processing jobs can fall into the following categories:

• Create a bunch of links -- create a procedure record and associated relations records (e.g., start a loan out transaction based on a saved set or shopping cart).  Patrick: The "create-a-bunch-of-links" variants are easier to understand and process without a lot of custom UI.
• Change a given field for each in a group -- global updates or inserts to a field (or fields) using a saved set or shopping cart (e.g., update specimen identification to X for these specimen numbers).  Patrick notes: One approach may be to do this with an import, listing the objects and only the field(s) to add or replace. Not sure if this will fall out of the import functionality or not. One way to test this is to ask Susan and Glen to create an update that they can run from the command line (curl) or their client code, that does what is needed to one record, without having to first fetch that record.  Chris: batch processing is currently performed across the range of things you mentioned (custom UI, SQL commands, send a spreadsheet to the programmer).
• More complex data change scenarios that might even need some UI -- Change a combination of fields and/or insert a new row in a repeatable group and set it as primary.

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-MUSEUM (when they go live in system)

UCJEPS

Batch processing: For a saved set of objects, user can add or alter geographic coordinates and associated fields (datum, error, coordinate source).

Batch processing: For a saved set of objects, user can change the scientific identification of the specimen. Previous identification should be stored in table corresponding to SMASCH annotation_history table.

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.

Placeholder

MUSEUM could wait six to twelve months

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

Placeholder

MUSEUM would like to have this eventually

These are nice to have but not a near term requirement.

Placeholder