I am starting to experiment with developing Curation System tasks.
I am working on a task that will identify non-standard items within a
collection (withdrawn, private, access restriction, no bitstreams, multiple
bitstreams).
.../dspace/bin/dspace curate -i 10822.1/707103 -t exception -r -
TOTAL ITEMS (25)
PrivateItem (2)
10822.1/707154
10822.1/707139
WithdrawnItem (2)
10822.1/707155
10822.1/707152
RestrictedAccessItem (2)
10822.1/707155
10822.1/707152
RestrictedAccessBitstream (0)
NoOriginalBitstream (4)
10822.1/707157
10822.1/707156
10822.1/707155
10822.1/707154
MultipleOriginalBitstreams (0)
UnusualBitstreamType (0)
For Curation Tasks that are Queued, is there a standard way to make the
curation task output accessible to a user? I presume that the standard
approach is to e-mail cron output of the queue processes:
.../dspace/bin/dspace curate -q admin_ui -r -
Also, is there a mechanism to generate html rather than text from a
curation task?
Terry
--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
