Page History

...

As with other command-line tools, these invocations could be placed in a cron table and run on a fixed schedule, or run on demand by an administrator.

In the admin UI

In the XMLUI, there are several ways to execute configured Curation Tasks:

1. From the Administrative "Curation Tasks" page. This option appears in the side-menu when logged in as a DSpace Administrator. This page allows one to run Site-wide Curation Tasks
   • In order to run a task from this interface, you must enter in the handle for the DSpace object. To run a task site-wide, you can use the handle: handle-prefix/0
2. There is also a 'Curate' tab appearing within the 'Edit Community/Collection/Item' page. This page allows you to run a Curation Task on that particular Community, Collection or Item. For Communities & Collections, this task also will execute on all its child objects, unless the Task itself states otherwise (e.g. running a task on a Collection will also run it across all Items within that collection).

In the XMLUI, there is a 'Curate' tab (appearing within the 'Edit  Community/Collection/Item') thatEach of the above pages exposes a drop-down list of configured tasks, with a button to 'perform' the task, or queue it for later operation (see section below). Not all activated tasks need appear in the Curate tab - you filter them by means of a configuration property. This property also permits you to assign to the task a more user-friendly name than the PluginManager _taskname_. The property resides in {{\[dspace\]/config/modules/curate.cfg}}:

...