Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of release 1.7, DSpace includes support for running curation tasks, which are described below. The main distribution will include several useful tasks, but the system also is designed to allow locally written and deployed tasks that follow the API described below.

Table of Contents
minLevel2
outlinetrue
stylenone

Tasks

The goal of the curation system ('CS') is to provide a simple, extensible, way to manage routine content operations on a repository. These operations are known to CS as 'tasks', and they can operate on any DSpaceObject (i.e. subclasses of DSpaceObject) - which means Communities, Collections, and Items - viz. core data model objects. Tasks may elect to work on only one type of DSpace object - typically an Item - and in this case they may simply ignore other data types (tasks have the ability to 'skip' objects for any reason). The DSpace core distribution will provide a number of useful tasks, but the system is designed to encourage local extension - tasks can be written for any purpose, and placed in any java package. This gives a DSpace site the ability to customize the behavior of their repository without having to alter - and therefore manage - the DSpace source code. What sorts of activities are appropriate for tasks?

...