Page History

...

For each activated task, a 'class'='taskname' line is added. The taskname is used elsewhere to configure the use of the task, as will be seen below. Note that the curate.cfg configuration file, while in the config directory, is located under 'modules'. The intent is

For many tasks, this activation configuration is all that will be required to use it. But for others, the task needs specific configuration itself. A concrete example is described below, but here note that these configuration property files also reside in {{\[dspace\]/config/modules}}

Writing your own tasks

A task can contain arbitrary code, but the class implementing it must have 2 properties:

...