Page History

1. Download the latest Jython installer jar (e.g. jython-installer-2.5.3.jar) from http://www.jython.org/downloads.html
2. Get jython.jar and the Lib directory.
   
   1. either unzip the installer jar:
      unzip -d [dspace]/lib/ jython-installer-2.5.3.jar jython.jar Lib/
unzip -d [dspace]/webapps/xmlui/WEB-INF/lib/ jython-installer-2.5.3.jar jython.jar Lib/
   2. or use it to install Jython: 

      java -jar jython-installer-2.5.3.jar --console

      Note: Installation location doesn't matter, this is not necessary for DSpace. You can safely delete it after you retrieve jython.jar and Lib.
3. Install Jython to DSpace classpaths (step 2a already did this for you):
   The goal is to put jython.jar and the jython Lib/ directory into every DSpace classpath you intend to use, so it must be installed in both[dspace]/lib and the webapp that deploys to Tomcat (if you want to run from the UI) - [dspace]/webapps/xmlui/WEB-INF/lib/. You can use symlinks if you wish. There are no special maven/pom extensions - just copy in the jarsjar and Lib/.
   Note: Older versions of Jython mention the need for jython-engine.jar to implement JSR-223. Don't worry about that, new Jython versions, e.g. 2.5.3 don't require this.
4. Configure the curation framework to be aware of your new task(s):
   
   1. set up the location of scripted tasks in the curation system. This means simply adding a property to [dspace]/config/modules/curate.cfg:
      script.dir=${dspace.dir}/ctscripts

   2. in this directory, create a text file named "task.catalog". This is a Java properties file where lines beginning with '#' are comments. Add a line for each task you write. The syntax is following:

      Code Block
      # logical task name = script engine name|file name|constructor invocation mytask=python|mytask.py|MyTask()

      Notes:

      
      
      • don't put spaces around the pipe character or you'll get an error similar to this one:
        ERROR org.dspace.curate.TaskResolver @ Script engine: 'python ' is not installed
      • The "script engine name" is what ever name (or alias) jython registers in the JVM. You can use both "python" and "jython" as engine name (tested on jython 2.5.3). 
      • The logical task name can't conflict with existing (java) task names, but otherwise any single-word token can be used.
      • The file name is just the script file name in the script.dir directory

      • "constructor invocation" is the language specific way to create an object that implements the task interface - it's ClassName() for Python

   3. If you want pretty names in the UI, configure other curate.cfg properties - see "ui.tasknames" (or groups etc)

5. Write your task.
   In the directory configured above, create your task (with the name configured in "task.catalog").
   The basic requirement of any scripted task is that it implements the ScriptedTask Java interface.
   So for our example, the mytask.py file might look like this:

   Code Block
   language python
   from org.dspace.curate import ScriptedTask class MyTask(ScriptedTask): def init(self, curator, taskName): print "initializing with Jython" def performDso(self, dso): print "perform on dso" return 0 def performId(self, context, id): print "perform on id %s" % (id) return 0

6. Invoke the task.
   You can do this the same way you would invoke any task (from command line, in the admin UI, etc). The advantage of scripting is that you do not need to restart your servlet container to test changes; each task's source code is reloaded when you launch the task, so you can just put the updated script in place.
   Example of invocation from command line:

   Code Block
   [dspace]/bin/dspace curate -t mytask -i 123456789/123 -r -

   Note: "-r -" means that the script's standard output will be directed to the console. You can read more details in the "On the command line" chapter of the Curation System page.

See also