Mass processing of files in a specific bit preservation context
The definition of Mass Processing is: Processing of masses of files within a specific bit preservation context.
In practice this means that mass-processing is a service, which can process executable code on files in with given IDs on a recipient pillar allowed via credentials. If there are errors reading the bits in the archive while running the code or if the code cannot be executed or if the code runs, but terminates prematurely it will result in exceptions (that is negative replies or alarms).
An example of Mass Processing is a characterisation analysis of a collection in the bit repository. The analysis to be performed on the individual files is written as a service, the IDs of the files in the collection are found and Mass Processing is invoked with this service on the identified files.
This function does not work on checksum pillars.
The Mass Processing functionality needs further analysis.
Status see BITMAG-89@jira
Example User Stories can be characterisation analyses of large collections of data or possibly migrations.
- Characterisation Analysis of Collection — TBD
- Mass process checksums
- Migration of Data with no longer supported File Type — TBD
Mass Processing Communications will follow the general communication pattern and include IdentifyPillarsForMassProcessing and MassProcessing Primitives, but will probably also include confirmations and some sort of status communication.