...
An ODM document's FileType must be either Snapshot or Transactional. A Snapshot document shows how to re-create the current state of the source database with respect to the included data, but does not show how it got to be in that state over time. A Transactional document shows, for each included entity, both the latest state of the source database, and (optionally) some prior states of that entity in the source database. The TransactionType attribute need not be present in a Snapshot document. When processing a Transactional document, the rules for ordering a set of transactions for a single data point are those described in the Element Ordering Section.
| Anchor | ||||
|---|---|---|---|---|
|
Granularity
An ODM document's Granularity is intended to give the sender a shorthand way to describe the breadth of the information in the document, for certain common types of documents.
Here are the intended meanings of these categories:
...
- The current file must be Transactional.
- If the current file is one of a collection, all other files in the collection must be both Archival and Transactional.
- The set of transactions must be both complete and non-redundant within the file or collection of files. In particular each file must contain:
- no transactions that have an audit date of prior to the AsOfDateTime of its PriorFile (if any),
- all transactions up to its AsOfDateTime. (For Granularity=All, this means all transactions in the study. See Granularity for the meaning of "all" for other Granularity settings),
- all AuditRecord and Signature information available in the source database, and
- no Upsert transactions.
...