Triggers

Needed by whom and when

Basic statements about who needs the functionality and by when.

UCJEPS: Some functions needed by the time they move to CollectionSpace as their production system

Overview

Existing systems use triggers and workflow rules of various kinds to take some action when a specified event occurs.

Question: What are the triggered actions in current systems?  Are they relevant in CollectionSpace?

User stories for definition

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

Triggers: UCJEPS - SMaSCH has about 80 triggers in Sybase that will need to be examined. Cascaded deletes, data validation and conversion, fuzzy date processor, and so on.

Triggers: UCJEPS (and Essig and others) - Latitude/longitude standardization: Allow data entry of latitude and longitude in various formats (e.g., degree-minute-second) but convert to specified format (e.g., digital). Question: What are the allowed formats and the standardized format?  Do they vary from collection to collection?

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)

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

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