...
Instead we propose a very simple, but flexible way to track monitor task execution, based on a new annotation type for tasks:
...
The presence of this annotation signifies to the CS that when a task of this type is performed, the outcome should be recorded somewhere, if recording has been otherwise configured activated in the DSpace curation setup. There will be no error (or run-time penalty), if recording has not been activated. The 'outcome' here means the following data elements:
- time stamp of task performance
- id (handle) of object
- EPerson name invoking task (if specified)
- logical task name
- task status code
- task result string (if set)
- task 'type' (explained below)
- task 'value' (also explained below)
'Recorded' here means only that a class implementing the 'Recorder' interface has been configured. What constitutes 'recording' is up to the implementation, but could include:
- logging to a local file
- writing to a database
- posting to a message queue