...
| Code Block |
|---|
(* Query syntax EBNF *)
query = expr , { "AND" , expr } ;
expr = field name | metadata name , oper , value ;
field name = characters , { "_" , characters } ;
metadata name = characters , "." , characters , [ "." , characters ] ;
oper = "=" | "<>" | ">" | "<" | ">=" | "<=" | "BETWEEN" | "LIKE" | "IN" ;
value = literal | variable ;
literal = "'" , characters , { whitespace , characters } , "'" ;
variable = "${" , varname , [ "+" | "-" , number ] , "}" ;
varname = "today" | handle ;
(* end syntax EBNF *)
|
Task Recording
Most routine task executions have no lasting or special significance, but some may merit keeping track of. For example, a scan of the Library of Congress page http://id.loc.gov/vocabulary/preservationEvents.html reveals that many preservation events of significance map to currently offered curation tasks. A facility for tracking important tasks may therefore be desirable. CS does emit ordinary DSpace logging messages, but these are interleaved with all other application logging data, so are not suitable for this sort of historical record.
Instead we propose a very simple, but flexible way to track task execution, based on a new annotation type for tasks:
| Code Block |
|---|
@Record
public class ImportantTask extends AbstractCurationTask
...
|
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 in the DSpace curation setup. There will be no error (or run-time penalty), if recording has not been activated.