...
Description
| Excerpt |
|---|
The basic description of the Intake Service goes here. |
There will often be one main entity service, and then a set of relation services. The relation services are generally grouped with the main entity, and should be described there. E.g., for a Person service, a Person-to-Person relationship mapping would also be described. Where to put things will be a judgment call. E.g., for Contact info, the Person-Contact relation and the Organization-Contact relation services probably belong with the Contact service, but should perhaps be mentioned in Person and Organization, respectively.
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
...
- Ex. An example of the case
...
Intake Service facilitates the set of activities that results in the initial intake of items into the organization. These activities typically involve recording the circumstances of the intake (such as information about the donor(s), if any, along with typically very brief descriptive notes about the items received. Often, a receipt is generated for the donor at this stage. |
Intake (or "Object Entry") occurs prior to - and is a separate and distinctive step from - the creation of object records, or the Acquisition of specific collection objects into the organization(s) collections.
Assumptions
- Not all intakes result in the creation of object records.
Key Concepts
- Especially things that become common sense, and so usually missed by new reviewers
...