NIMS/Feedback on R4 GUI

Here is feedbacks on new R4 GUI from NIMS. This feedbacks include bugs/feature requests as well as UI-specific issues.

Date: 2009-01-20
Place: Scientific Information Office at NIMS (Sengen, Tsukuba, Japan)
Participants: Core members at our office ( User:Masao, Shingo, and Mikiko )

Feedbacks[edit]

General / Japanese UI / I18n-related issues[edit]

The page content of ErrorPage and Homepage cannot be localized.

I think it is better to use native expression on each language for the language selection. i.e. [ English, Deutsch, 日本語 ] instead of [ 英語, ドイツ語, 日本語 ] (these labels are in Japanese expression, respectively).

JIRA Bug: [1] --Natasa 09:43, 23 January 2009 (UTC)

Default settings in language selection are followed by browser's settings. (i.e. Accept-Language header in HTTP-request)

JIRA Bug (already identified): http://zim01.gwdg.de:8080/browse/PUBMAN-615

And is it also possible to have a user account based preference (like mediawiki)?

No, this is not possible and user preferences are not yet scheduled. That is the reason that the browser language settings is taken over. If the browser language is not supported, default is English language. --Natasa 09:43, 23 January 2009 (UTC)

Rupert: This can be handled by dev. --Rupert 08:14, 23 January 2009 (UTC)

Header[edit]

Separators in breadcrumb are more preferable/intuitive to use ">" (bracket) than "/" (slash).

baseline of search forms

Rupert: This is already known. There is a new concept for breadcrumbs, which was not implemented in R4.0. So the breadcrumb will follow (postponed for bookmarkable searches) --Rupert 08:22, 23 January 2009 (UTC)

The simple query form and the links for advanced search and organizational search are not placed in the same baseline. See also the screenshot.

Rupert: May I ask which browser is in use? Our CSS is aligned to FF3. Other browsers should work but with small divergences in layout consistency. --Rupert 08:22, 23 January 2009 (UTC)

this was also reported by me . there is small descrepancy also with FF3--Natasa 09:03, 23 January 2009 (UTC)

ViewItemFull[edit]

Wording "Visibility" is a little bit ambiguous. ("show/hide" label is enough to understand. Maybe we can omit this header.)

Rupert: Will be put in bug tracking. Wording is done mostly by Service Management. --Rupert 08:23, 23 January 2009 (UTC)

JIRA Bug: [2] --Natasa 09:46, 23 January 2009 (UTC)

Submission[edit]

The links "Easy/Full Submission" and "Import" in "Submission Start" page and the collection name links seem to be just a label. So, there is a concern that novice users are confused with a next action they need to go to.

Usability feedback issue. GUI Team to check on improvement. JIRA ticket: http://zim01.gwdg.de:8080/browse/PUBMAN-707 --Natasa 09:50, 23 January 2009 (UTC)

The "(more)" foldings in the descriptions at SubmissionStart and ChooseCollection pages are not necessarily needed. If a description is not too long, we can browse it at a time without scrolling.
- A "(more)" link appeared, even if the description was short and all of it was displayed.

Rupert: For Easy Submission we decided to keep everything initially in one page. We had that fundamental open close mechanism on dev server and then decided to change it into this "more" mechanism. I would like to wait for more feedback in usability interviews before changing it again. --Rupert 08:38, 23 January 2009 (UTC)

JIRA Issue: http://zim01.gwdg.de:8080/browse/PUBMAN-708 --Natasa 09:58, 23 January 2009 (UTC)

The selection on "Review type" is desirable in the order of "Peer", "None", and "Internal". ("internal review" will be the most infrequent choice, i guess.)

Rupert: This is rather domain specific and will be taken into account by Service Management. --Rupert 08:38, 23 January 2009 (UTC)

No changes are planned for now. "None" is default. Others are by alphabetical order. At present there is no possiblity to define this dinamically. Will be taken into account. JIRA issue: http://zim01.gwdg.de:8080/browse/PUBMAN-709 --Natasa 09:58, 23 January 2009 (UTC)

The label "* mandatory field" at the bottom of the pages are desirable to be located at the top of the page. And the label should be the same style as at the form fields (i.e. in red color).

Rupert: Yes, it was proposed to go with it in the message line. In fact it is a hint, coming from the system. In this case it was a decision from a PubMan GUI meeting. I would like to address this in the next PubMan GUI Meeting. --Rupert 08:38, 23 January 2009 (UTC)

JIRA Ticket: http://zim01.gwdg.de:8080/browse/PUBMAN-710 --Natasa 09:58, 23 January 2009 (UTC)

Easy Submission[edit]

STEP1: Generally, this is not as good as R3. (impressions from participants)

JIRA Issue: http://zim01.gwdg.de:8080/browse/PUBMAN-711 --Natasa 10:02, 23 January 2009 (UTC)

The action links "Upload file" and "Save" for files and locators seems to be not a action link, just a normal text.

Rupert: Would it be fine to have "Save" as a button? --Rupert 08:57, 23 January 2009 (UTC)

"File property" form is desirable to be displayed in default.
- Due to these two problems, it seems that a depositor will be confused when the depositor upload a file and then click "Next" button. In that case, an error message of "An attached file is missing a content type (e.g. Abstract, Pre-print, etc.)." will be shown at the top of the page. That behavior is confused because (s)he seems not to be able to find such additional forms beforehand.

Rupert: Just like the Validation message? Submission form is already very cluttered, pointing via text in advance would blow it up even more.--Rupert 08:57, 23 January 2009 (UTC)

- - The error message above should be "A content type for an attached is missing..."???

STEP2

The order of creator type selection is preferable as "Author", "Editor", "Contributor", and others. (These three roles will be more frequent ones than others.)

Rupert: Input for Service Management.--Rupert 08:57, 23 January 2009 (UTC)

See issue above: http://zim01.gwdg.de:8080/browse/PUBMAN-709 --Natasa 10:08, 23 January 2009 (UTC)

It is not clear how to use the "Add multiple" feature
- What is the separator among multiple authors? (A comma, semicolon, or others?)
- Is it possible to add affiliations at one time? if ok, how to add it?
(general question) Is this support a middle name?

Rupert: Yes, it would be good to have more information about the parsing behind. As help is sometimes needed right beside those questionable fields. We already thought about placing "Info Buttons" beside those fields. But this is still not tackled. --Rupert 08:57, 23 January 2009 (UTC)

JIRA Issue: http://zim01.gwdg.de:8080/browse/PUBMAN-712 --Natasa 10:08, 23 January 2009 (UTC)

STEP3

It is desirable to add explanation for the date specification. (e.g. YYYY-MM-DD)

Will be added to the Help text ( http://zim01.gwdg.de:8080/browse/PUBMAN-713 ). Otherwise, may be same issue as PUBMAN-712 above. --Natasa 10:08, 23 January 2009 (UTC)

The Auto-suggesting list for Journals needs a closing button. (when a long list are shown, "Save" button cannot be accessible.

Rupert: In general these layer should vanish by clicking outside the box. This is known and needs to be done still. --Rupert 08:57, 23 January 2009 (UTC)

JIRA Issue: http://zim01.gwdg.de:8080/browse/PUBMAN-714 --Natasa 10:08, 23 January 2009 (UTC)

Full Submission[edit]

"Content type" field for file locators is a mandatory field, but it is not marked as "*".

Problem is already identified. See JIRA http://zim01.gwdg.de:8080/browse/PUBMAN-715 --Natasa 10:12, 23 January 2009 (UTC)

Event information field is missing when submitting an article in "Proceedings Paper" or "Talk" genres. (Event forms appeared if "others" genre is selected)

Ticket already exists, considered by JIRA http://zim01.gwdg.de:8080/browse/AS-627 --Natasa 10:12, 23 January 2009 (UTC)

SearchResult[edit]

When I issued Japanese query from advanced search form, the result of "Show Query" link is gambled. For example, the query "轟*" for creator field is shown in "Show Query" feature as follows (copy/paste from a html source):

( escidoc.any-persons="è½&#159;*" )  and  ( escidoc.objecttype="item" )  and  ( escidoc.content-model.objid="escidoc:persistent4" )