General Batch Use Case

Actors

System of Record needs to have created a specification for the data they wish to send.
OpenRegistry has defined specification format such that it can read the specification sent by System of Record and translate data.
OpenRegistry System needs to have staging area created for the System of Record.
OpenRegistry needs to map System of Record to staging area.
OpenRegistry authorizes System of Record to write to particular staging area

System of Record authenticates with the OpenRegistry system.
System of Record composes a set of data to send to OpenRegistry
System of Record sends information in format via transport negotiated between System of Record and OpenRegistry System.
OpenRegistry determines if there is appropriate authorization to store data.
Data is stored in staging stables (parsing and loading), and OpenRegistry starts to process data.
Processing follows the general pipeline for processing, including reconciliation, identifier assignment, normalization, standardization, and pushing data to appropriate systems.
Based on the feed specification, notifications of errors, success, results, etc. should be sent out via the appropriate methods.

System of Record receives detailed information on how the process went (via notification scheme).
Any errors are logged and appropriate people notified.
Every data change is audited and logged for debugging purposes.

Everything that can be executed in parallel should be as a significant amount of data may be transmitted at once.
Batch processing should not unfairly hold up real-time processing.