OR11-PRESENTATION - ResearchSpace@Auckland

advertisement
Writing and Deploying
Your Own Curation
Tasks in Dspace
Managing routine content operations on a
digital repository through the new curation
task system in DSpace 1.7.X.

learn how to write a curation task, as well
as deploy and configure it to run.
You Need Stuff

Link Checker

Creative Commons

Translation

Bitstream Metadata

Bitstream Retrieval

Duplicate Metadata

Scan Bitstreams for Viruses
Curation to the Rescue




a simple, extensible way to manage routine
content operations on a repository
operate on any DSpaceObject
run in interactive, non-interactive or
workflow
customize the behavior of your repository
without having to alter - and therefore
manage synchronization with - the DSpace
source code.
Configurable



No tasks are exposed in the public
interfaces.
performing tasks is an administrative
function
only knowledgeable collection editors,
repository administrators, sysadmins, may
run tasks.
Getting Started

a no argument constructor, so it can be
loaded by the PluginManager.


all tasks are 'named' plugins, with the
taskname being the plugin name.
implement the interface
'org.dspace.curate.CurationTask'
You're the Decider

Suspendable – the Curation System will
cease processing when it encounters a FAIL
status
@Suspendable(invoked=Curator.Invoked.INTERACTIVE)
public class MyTask implements CurationTask

Distributive – If present, task manages
container iteration
@Distributive
public class MyTask implements CurationTask
Deploy

deployment details go here
Command Line
Invocation
[dspace]/bin/dspace curate -t vscan -i 123456789/4
The complete list of arguments:
-t taskname: name of task to perform
-T filename: name of file containing list of tasknames
-e epersonID: (email address) will be superuser if unspecified
-i identifier: Id of object to curate. May be (1) a handle (2) a workflow Id or (3) 'all' to
operate on the whole repository
-q queue: name of queue to process - -i and -q are mutually exclusive
-v emit verbose output
-r - emit reporting to standard out
Admin UI Invocation
ui.tasknames = \
profileformats = Profile Bitstream Formats, \
requiredmetadata = Check for Required Metadata
ui.statusmessages = \
-3 = Unknown Task, \
-2 = No Status Set, \
-1 = Error, \
0 = Success, \
1 = Fail, \
2 = Skip, \
other = Invalid Status
Workflow Invocation
&lt;taskset-map&gt;
&lt;mapping collection-handle=&quot;default&quot; taskset=&quot;cautious&quot; /&gt;
&lt;/taskset-map&gt;
&lt;tasksets&gt;
&lt;taskset name=&quot;cautious&quot;&gt;
&lt;flowstep name=&quot;step1&quot;&gt;
&lt;task name=&quot;vscan&quot;&gt;
&lt;workflow&gt;reject&lt;/workflow&gt;
&lt;notify on=&quot;fail&quot;&gt;$flowgroup&lt;/notify&gt;
&lt;notify on=&quot;fail&quot;&gt;$colladmin&lt;/notify&gt;
&lt;notify on=&quot;error&quot;&gt;$siteadmin&lt;/notify&gt;
&lt;/task&gt;
&lt;/flowstep&gt;
&lt;/taskset&gt;
&lt;/tasksets&gt;
Useful References

https://wiki.duraspace.org/display/DSDOC/Curation+System
RoadMap

Explain the steps that now need to be taken

Future plans
Credits



Wendy Bossons – MIT –
wbossons@mit.edu
Kim Shepherd – University of Auckland
– kim.shepherd@gmail.com
Richard Rodgers – MIT
Download
https://studylib.net/doc/5237953/or11-presentation---researchspace%40auckland
studylib.net
CC-MAIN-2024-26
42843
application/http; msgtype=response
sha1:4SVQIUSKAVAO3HP52UJNQDSHU46WL36U
<urn:uuid:fe702a20-fea9-4811-882f-496d8eb1dfa2>
2024-06-13T04:27:06Z
172.67.193.117
text/html
sha1:NW62IQZVCLOGVEH23XX3SSFGWSTX6O6L
<urn:uuid:5541df60-1ee1-4e14-aa08-cb23f2b5779e>
https://studylib.net/doc/5237953/or11-presentation---researchspace%40auckland
response
<urn:uuid:3e1d9e95-316f-4916-9760-d1ca29f24449>
isPartOf: CC-MAIN-2024-26
publisher: Common Crawl
description: Wide crawl of the web for June 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-207
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/