Page History

...

As of release 1.7, DSpace includes support for running curation tasks, which are described below. The main distribution will include in this section. DSpace 1.7 and subsequent distributions will bundle (include) several useful tasks, but the system also is designed to allow new tasks to be added between releases, both general purpose tasks the come from the community, and locally written and deployed tasks that follow the API described below.

...

For CS to run a task, the code for the task must of course be included with other deployed code (to {{\[dspace\]/lib}}, WAR, etc) but it must also be declared and given a name.
 This is done via a configuration property in {{\[dspace\]/config/modules/curate.cfg}} as follows:

plugin.named.org.dspace.curate.CurationTask = \
org.dspace.curate.ProfileFormats = format-profileprofileformats, \
org.dspace.curate.RequiredMetadata = req-metadatarequiredmetadata, \
org.dspace.curate.ClamScan = vscan

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.

For many tasks, this configuration is all that will be required to use it. But for others,

Writing your own tasks

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

...