This is a system for exporting recently-updated (or created) DOMS entries as XML files that can be imported to LARM. The source code is maintained at https://github.com/statsbiblioteket/larm-doms-exporter .
A sample xml export file, together with relevant clarification of the various elements it contains, is kept in the codebase. See the file src/main/resources/CHAOS_envelope_template_test.xml .
The basic logic is based on that used in the Broadcast Transcoder Application. It uses a database-backed object-store as a persistent queue/log. Each entry in the persistence layer is a tuple:
(doms-pid, doms-timestamp, last-exported-timestamp, status).
status has values
(PENDING, REJECTED, FAILED, COMPLETE). (For objects in status COMPLETE, the two timestamps should be equal.)
The logic has producer and consumer phases.
Fetch from the object-store an ordered list of all PENDING exports and put them in a queue, oldest doms-timestamp first.
For each entry in the queue: if the object is not a radio program: mark as REJECTED and move to next object else if the object has no shard analysis delete the object from the database else if the object is REJECTED or FAILED in the bta database mark as rejected and move to next object else if the object is PENDING or missing(*) in the bta database leave as PENDING in LDE database and move to next object else (ie object is COMPLETE in bta database) if there is a significant change in DOMS object between doms-timestamp and last-exported-timestamp export object update last-exported-timestamp to doms-timestamp mark as COMPLETE
\* Note that objects in the bta database are only consulted if there is a shard analysis. Therefore we do not usually expect to find objects missing in the bta database.