...
- logging to a local file
- writing to a database
- posting to a message queue
The point is to have a 'hook' into the curation runtime where these records can be captured. The release will likely include a simple local file log/journal recorder as a basic starter implementation. A number of default values may be overridden if needed:
| Code Block |
|---|
@Record(statusCodes={1, 2})
@Record(type="PREMIS",
value="Replication")
|
By default, the recording logic will be invoked regardless of the statusCode returned by the task, but in the above case, we limit it to errors and skips. Type and value are very useful when a task's work can be expressed in a controlled vocabulary: it would be easy to generate records, e.g., as RDF statements with the id as subject, and type and value referring to ontologically defined terms.