[
https://issues.apache.org/jira/browse/UIMA-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001660#comment-14001660
]
Lou DeGenaro commented on UIMA-2909:
------------------------------------
The web interface is somewhat minimalist, with design choices made based on
time-to-implement vs. other priorities relative to (perceived) benefits. The
same web pages are meant to satisfy both sys admins and users. A more
elaborate design might address each domain separately.
With respect to the Jobs page and the specific complaints:
1. The State is clear. The difference between "Job is Ending" and "Completing"
does not seem significant.
2. The Reason for a job state is clearly given in the Reason column.
3. With respect to "MonitorActive", this is a critical piece of information
that reflects what the user requested in his/her job submission: that a client
monitor should be started for this job and should said monitor terminate so
should the job.
4. The terminate button is yet another way for a job to be canceled and is
unrelated to the job monitor.
5. The web server cannot teach the user how DUCC works nearly as well as can
the documentation...which is available via one click from any web server page!
It has been my personal experience over the past several years that the web
server serves its wide-ranging audience well, nothwithstanding future
complaints.
I'm going to close this issue as "Not a Problem", but please feel free to
re-open with counter arguments.
> DUCC Web server - follow normal GUI conventions where feasible
> --------------------------------------------------------------
>
> Key: UIMA-2909
> URL: https://issues.apache.org/jira/browse/UIMA-2909
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Marshall Schor
> Assignee: Lou DeGenaro
> Priority: Minor
>
> The web interface probably should be designed for the non-expert user. As
> such, a good message in place of "MonitorActive" is "Running Normally". If
> you want to indicate some extra-ordinary kind of status, you might have the
> hover text indicate that the job was submitted with an option that permits it
> to be cancelled by --insert user action here-- (don't say "interrupt" - as a
> non-expert user won't know what that means in terms of a user action. If it
> means that the "terminate" button on the left works, they you might say that).
> When a job enters the state "ending" (but not fully ended), this field could
> read "Job is Ending". When the job is ended, this field could read Job Ended
> normally, or some indication that it didn't end normally, and why.
> The hover in general should be consistent with the message, and supply more
> details of interest to the non-expert user. For instance, if the message is
> Running Normally, the hover might say "Running Normally. To manually cancel,
> use the terminate button on the left."
> In any case, I would not use the hover to inform the user about some
> auto-cancellation feature that is like a cleanup if the client dies.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
