Container User Story Summary
- Megan Forbes
Overview
Many collections holders store groups of objects in crates and other containers. Crates and containers have somewhat different attributes from fixed storage locations; namely, they can move, and when they do, all objects they contain should also move. In order to determine the best method for modeling crates and containers in CollectionSpace, we are gathering user stories from implementers who use crates and containers in their collections storage, which we'll then run through different potential methods of crate management (an authority, a procedure, a type of storage location, etc.). Note that not all the user stories will end up becoming features in CollectionSpace.
What is a user story? A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer. User stories should be a few sentences, in simple language, that outline the desired outcome. They don't go into detail. Requirements are added later, once agreed upon by the team.
Crate and Container User Stories
User can create a Container record with associated details (e.g. type of container, dimensions, material)
User can inactivate a Container
User can add Objects to a Container
User can remove some or all Objects from a Container
User can view the current Objects stored in a Container
User can view the Objects formerly stored in a Container
User can record the Storage Location of a Container
User can view a list of all Containers in a Storage Location
User can move Container and its contents to a new Storage Location
User can receive a system alert when moving a Container that all Objects will also move
User can view the Storage Location history of a Container
User can view the Storage Location history of an Object, including historical Containers and Locations
User can create Container hierarchies; that is, Containers that contain other Containers
User can assign a Condition Check procedure to a container