Exchanges

Owned by Chris Hoffman
Last updated: Nov 22, 2010Version comment
2 min read

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

UCJEPS engages in specimen exchanges with other herbaria around the world.  For example, they will exchange 20 mosses of one species for a similar number of a different variety from another institution.  They think of these almost like ongoing loans though there is no expectation that the specimen will come back.  These are like an in-kind trade.  Some samples go out, and some samples come in.  A calculation of balance of exchange with particular institutions is desired.

  • Question: How do exchanges effect searching?  For example, if you search for Object Exit transactions, should exchanges (exchange out transactions?) show up? 
  • Question: Do we need an Exchange Out transaction type or subclass of Object Exit?  Do we need an Exchange In type or subclass of Intake or Acquisition?  Could we use the existing Reason code/attribute?
  • Question: Do exchanges happen synchronously or asynchronously?  Probably the latter.
  • Question: Does UC Botanical Garden need this feature as well?  On day one or later?

User stories for definition

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

Exchanges: User can mark an outgoing specimen as an exchange with another institution or organization.

Exchanges: User can mark an incoming specimen as an exchange with another institution or organization.

Exchanges: User can mark an outgoing group of specimens as an exchange with another institution or organization.

Exchanges: User can list exchanges with a particular institution with a count of the balance of the exchange relationship.

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