[
https://jira.duraspace.org/browse/DS-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18333#action_18333
]
Richard Rodgers commented on DS-750:
------------------------------------
Thanks for the review and comments Tim. As to the requiredmetadata task, it is
working as expected, but this needs a bit of explanation. Tasks decide (at
design time) how to handle themselves when invoked against a container. One
strategy would be to accumulate data and put in all in the result: this is what
the 'profile formats' task does. This is safe when the expectation is that the
result will remain manageably small - say dozens not thousand of lines. In the
latter case, the UI display would be unusable. In the case of
'requiredmetadata' the collection size could be large, so that task has
decided *not* to emit a line for each item examined in the result. Instead, it
uses a 'suspend' strategy - which is just to show the last item examined in the
result, but stop (suspend) whenever the task fails. This strategy means the
curator will see one of two result strings: (1) what you saw, a 'successful'
result on the 'last' item in the collection. [Note that the curator doesn't
need to know what the last item is - the Success status tells that the whole
collection is OK], or (2) a failure status, where the result string shows the
offending item. [Note - there may be more, but the task suspends on the first
bad one]. Does this make sense? It is even possible to tune suspendability
behavior so that in the UI it suspends (where display space is limited), but in
batch it runs to completion [Here the assumption is that you are capturing all
the reporting detail]. Curation is definitely an expert's domain!
> Cleanup display of Curation Admin UI to make more human
> readable/understandable
> -------------------------------------------------------------------------------
>
> Key: DS-750
> URL: https://jira.duraspace.org/browse/DS-750
> Project: DSpace
> Issue Type: Improvement
> Components: XMLUI
> Affects Versions: 1.7.0
> Reporter: Tim Donohue
> Assignee: Richard Rodgers
>
> The results from the Curation Admin UI are a bit confusing at times (and even
> I'm having a bit of trouble understanding/reading them, despite knowing the
> role of the Curation System).
> Here's an example of retrieving results from Curation Admin UI:
> * Login as Admin in XMLUI on http://demo.dspace.org/
> * Visit a Community with contents (e.g.
> http://demo.dspace.org/xmlui/handle/10673/1)
> * Click "Edit Community" and visit the "Curate" tab.
> * Click "Perform" on "Profile Bitstream Formats"
> The results are returned as one long, unbroken string -- e.g.:
> "The task, profileformats was completed with the status: 0. Results: 11 (U)
> Unknown data format 1 (K) Broadcase Wave Format 1 (K) Microsoft Powerpoint 2
> (K) Graphics Interchange Format 1 (K) Microsoft Excel XML 1 (K) Microsoft
> Excel"
> We may want to improve the readibility/understandability of these results by
> doing the following:
> 1. Replace "status: 0" with a understandable string like "Success"
> 2. Explain that "(K)" = Known Format and "(U)" = Unknown. Or leave it out
> altogether, as the unknown data formats are already totaled together.
> 3. Return results in a bulleted list (or each entry on a separate line)
> We also may potentially want a paragraph/description for each of the
> available Curation Tasks. It's not always self-explanatory what a particular
> task may be doing (and therefore, what the results actually mean).
> I've sent these along to Richard Rodgers separately -- but, I wanted to track
> these issues here. Also feel free to add more comments on the Curation Admin
> UI to this same issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: New IBM DB2 features make compatibility easy.
Learn about native support for PL/SQL, new data types, scalar functions,
improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools,
best practices and more - all designed to run applications on both DB2 and
Oracle platforms. http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
