Identify species that are parts of objects

Needed by whom and when

Basic statements about who needs the functionality and by when.

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

Overview

PAHMA has objects in their collections that are made of materials derived from species.  They need to be able to identify the species in question.  The artifact might be made from multiple natural materials (e.g., a basket is made of reeds, feathers, and bone beads).  This functionality does relate to the scientific taxonomy controlled vocabulary and specimen identification user stories.

User stories for definition

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

Identify species that are parts of objects: PAHMA - For an artifact, user can identify multiple species that are the source for materials used in the artifact's construction.  Depending on how this is modeled, PAHMA needs a note or remarks field describing the association.

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