...
Description
| Excerpt |
|---|
The basic description of the new 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
- 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
- Details of the assumption
Key Concepts
- Especially things that become common sense, and so usually missed by new reviewers
Dependencies
- Note other services that are consumed or that are closely related to this one
Background Documentation
...
Archival and Preservation services provide minimal support for the management and verification of digital resources that will be preserved in a system. This is distinct from conservation and preservation activities on physical objects. |
We think this will eventually be provided by external services, but for now we need to at least model such things as hash-value fingerprinting of digital resources to verify integrity. I (Patrick) plan to talk to MVP folks at UCB about this.
Assumptions
- This will be minimal, and more of a placeholder than anything. It may include some minimal services to support little places that want some safety and cannot afford proper procedures.
Key Concepts
- Digital fingerprint, probably via some secure and reasonable to compute hash mechanism.
- Digital Provenance, to document how digital artifacts and derivatives were produced.
Dependencies
- Media services relate to this.
Background Documentation
- Media Vault Program at U.C. Berkeley
- There must be some other good references on this stuff - I've just forgotten them.