Loan In Service Description and Assumptions

Description

The Loan In Service represents the information around managing and documenting loans made into the organization; that is, the borrowing of objects for which the organization is responsible for a specific period of time and for a specified purpose, normally exhibition/display, but including research, conservation, education or photography/publication.

Assumptions

• Try to be explicit and exhaustive, but not pedantic.
  • ~pschmitz@berkeley.edu: If there is an active discussion or comment, you may want to call it out as a sub-bullet. This example also uses a color macro to call it out, and provides a link to a given user to indicate that this is a particular contributor's position.

Subtopic

• More assumptions around peripheral subject
  • Ex. An example of the case
• Yet another assumption
  • Details of the assumption
    • Nitty-gritty detail 1
    • Nitty-gritty detail 2

Key Concepts

• Especially things that become common sense, and so usually missed by new reviewers

Dependencies

This is bound to an individual CollectionObject, or to some grouping like an Exhibition or perhaps even a Collection. The Loan has some temporal aspects, and may also have some workflow state associated with the planning and execution of a loan. Will definitely need to be able to produce reports like "loans outstanding" (possibly by organization loaned-to, etc.), "loans to and from some organization," etc.

The Loan entity will also associate to Organization, Movement, Insurance, and Person entities, among others.

Background Documentation

• Incoming Loan - Functional Requirements

• If we have notes from community design meetings, link to them here.
• If we have relevant sections in Spectrum or another such document, link to them here (or cite section numbers, etc.)

Key Team Members

• (Name(s) of members) is/are the primary tech team member(s) for this service
• Need to identify the community members acting as Domain Experts.