|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
The behavior you report is not a bug - but operation as designed. See here for more context:
https://wiki.duraspace.org/display/DSPACE/Curation+Task+Cookbook
(especially the 3rd section, about 'suspendable' tasks)
The admin UI (or any simple web page) is not well-suited to display an arbitrarily long list of status codes (or result strings), so no attempt was made to do so. There are facilities, however, to capture all the details you might need using the 'reporting stream' feature of the curation system.
See https://wiki.duraspace.org/display/DSDOC3x/Curation+System#CurationSystem-ReportingStream
for more details.
Hope this helps,
Richard