Difference between revisions of "Talk:ESciDoc Prototyping"

From MPDLMediaWiki
Jump to navigation Jump to search
 
Line 37: Line 37:
*apart from the bookmarking services, for R5 one article-centered option (ISI Web of Knowledge) on PubMan View Item Version is planned - if there is given an ISI identifier, it should act as a link to look-up this article in ISI -> is not apparent from prototype --[[User:Juliane|Juliane]] 14:29, 14 April 2009 (UTC)
*apart from the bookmarking services, for R5 one article-centered option (ISI Web of Knowledge) on PubMan View Item Version is planned - if there is given an ISI identifier, it should act as a link to look-up this article in ISI -> is not apparent from prototype --[[User:Juliane|Juliane]] 14:29, 14 April 2009 (UTC)


Rupert: Is not described explicitly because it is just a link like file and cite item as. --[[User:Rkiefl|Rupert]] 16:36, 23 April 2009 (UTC)
Rupert: Is not described explicitly because it is just a link like file and cite item as. So the spec should be sufficient. --[[User:Rkiefl|Rupert]] 16:36, 23 April 2009 (UTC)


===Bookmarking===
===Bookmarking===

Latest revision as of 09:50, 24 April 2009

R5 Prototype[edit]

Protoype feedback[edit]

New: Policy&Disclaimer[edit]

  • on all pages, we need one link to the colab page, where Policy and Disclaimer (Leitlinien und Impressum) can be found. CoLab page is in preparation. Please provide a placeholder for the link. Would propose to place it at the very bottom of each page. There will be just one CoLab page as entry page, for both german and english version.--Ulla 15:41, 14 April 2009 (UTC)

Rupert: To include the disclaimer, the main menu will change for R5(BT): Login, Contact us, Policy & Disclaimer, Help; If this is not sufficient from legal point of view, the disclaimer will be shown on both start pages below the left column. But if it really needs to be seen on every page additionally it can be put in a footer which is always below the scrollable area, but this is not desirable from the GUI point of view. --Rupert 16:05, 23 April 2009 (UTC)

Institutional Visibility and Collaboration[edit]

  • both scenarios are postponed to Rx

Rupert: The pages "Audience" and "Collaboration" in the FPT will be marked "Not R5" --Rupert 16:06, 23 April 2009 (UTC)

Copyright Information[edit]

  • in "Files Step 2" of the prototype the two fields for rights statement (optional, free text field) and date copyrighted (optional field with date format) are missing --Juliane 14:47, 14 April 2009 (UTC)

Rupert: Will be updated. --Rupert 16:29, 23 April 2009 (UTC)

  • in "Files Step 2" -> "License Type" -> is there a link to the written form on Creative Commons of the single license which can be chosen at this step of submission? The possibility to read more about the offered license types should be given. --Juliane 14:47, 14 April 2009 (UTC)
  • PubMan Item Version within the array "Files" -> apart from the license type there should also be displayed the rights statement and the date copyrighted -> it's not really apparent from prototype --Juliane 14:47, 14 April 2009 (UTC)

Rupert: As there is nothing special it will be displayed like all other metadata "Label: Value". --Rupert 16:29, 23 April 2009 (UTC)

  • Advanced Search -> there should be the possibility to search for a special license type -> it's not apparent from prototype (or have I overlooked it?) --Juliane 15:00, 14 April 2009 (UTC)

Rupert: As far as I know it's not R5 as it is a string only. --Rupert 16:29, 23 April 2009 (UTC)

  • Advanced Search -> there should be the possibility to search also for embargoed files --Juliane 15:00, 14 April 2009 (UTC)

Rupert: OK --Rupert 16:29, 23 April 2009 (UTC)

Look-Up Services[edit]

  • for R5 two author-centered look-up options (WorldCat and Google Scholar) on PubMan Researcher Portfolio are planned - in the prototype three possibilities are displayed - do they serve as placeholders or do they show the actual number of possibilities? --Juliane 14:29, 14 April 2009 (UTC)

Rupert: Only placeholders, number and type of services are mentioned in spec. --Rupert 16:36, 23 April 2009 (UTC)

  • apart from the bookmarking services, for R5 one article-centered option (ISI Web of Knowledge) on PubMan View Item Version is planned - if there is given an ISI identifier, it should act as a link to look-up this article in ISI -> is not apparent from prototype --Juliane 14:29, 14 April 2009 (UTC)

Rupert: Is not described explicitly because it is just a link like file and cite item as. So the spec should be sufficient. --Rupert 16:36, 23 April 2009 (UTC)

Bookmarking[edit]

  • "Bookmarking services below status icon: Needs text for Tooltips" -> proposal for tooltip: "Bookmark this item in Delicious / Citeulike / Connotea" --Juliane 13:27, 14 April 2009 (UTC)

New: Options in Meta Menu[edit]

  1. Feature "Change password"
I am not sure if it will be possible to change the password from the PubMan interface. This needs checking by Natasa. --Nicole 18:44, 24 March 2009 (UTC)
well, it won't be the pubman interface, but the escidocadmin interface. but it could certainly be linked from pubman.--Robert 19:21, 24 March 2009 (UTC)
  1. Change Style
Not clear from the prototype how I can access the options menue. --Nicole 18:44, 24 March 2009 (UTC)

Rupert: Meta Menu/Options/ just by clicking the Options Link--Rupert 07:58, 25 March 2009 (UTC)

Will this then be an interface, which can also be accessed by users, which are not "roland" :-) ? If yes, please check with dev. team how this can be linked with another. --Nicole 11:45, 7 April 2009 (UTC)

Affiliation History (Clarified with Melanie)[edit]

  • shall the affilation history also be visible from the OU tree and if yes how? Not clear from GUI spec. --Nicole 18:58, 24 March 2009 (UTC)

Rupert: The Org. Description is extended: Also by clicking the link Description in Org tree. --Rupert 08:01, 25 March 2009 (UTC)

I see. But I don't think that this is obvious to the user. Maybe there is a more clear possibility to make the user aware of history of affiliations? --Nicole 08:04, 25 March 2009 (UTC)

Proposal: If the affiliation history is used frequently and needs to be accessed in 90% of sessions, it can be more prominent. Another option is to check if in usability tests people have problems to find it. --Rupert 08:46, 25 March 2009 (UTC)

  • According to the use case for view item version the user should also be able to view the affiliation history. How is this realized? Not clear from the prototype. --Nicole 08:04, 25 March 2009 (UTC)

Rupert: View Item Version/click on affiliation name. --Rupert 08:50, 25 March 2009 (UTC)

Changes in Advanced Search (Regrouping, GUI only)[edit]

Rupert: There is a new group here: "Content & Details". This is subject to the discussion. According to the mail the prototype contains a set of changes that can be clarified for now. Nothing else for now. Please refer to the regrouping only so we can close this topic. Everything, not related to the current Version of the prototype is moved below. --Rupert 08:09, 25 March 2009 (UTC)

Administrative Search (Already clarified before R4.1 with Rike)[edit]

  • what does the checkbox "option" stand for? For filled/not filled? I am not sure if it is "nice" to have all possible PubMan MD fields in a pull down list. --Nicole 19:08, 24 March 2009 (UTC)

Rupert: If a dropdown contains "Values defined in Use Case" it should be e.g. for Status (pending, submitted, ...) --Rupert 09:08, 25 March 2009 (UTC)

  • I think the plan was to have a separate search mask for the administrative search and the advanced search... I think this is a point of discussion for the meeting. --Nicole 19:03, 24 March 2009 (UTC)

Rupert: Another form could be one possible solution but this would mean the user knows already the difference between advanced search and administrative search. --Rupert 09:08, 25 March 2009 (UTC)

Nicole: As this feature will only be available for experienced, logged in users, I think the difference between advanced and administrative search should be clear. --Nicole 11:47, 7 April 2009 (UTC)

Authors and Affiliations (Discussed with Markus H. and Markus M.) Not R5!![edit]

  • not clear from GUI spec. how add to multible authors and OUs should work. Do the OUs and creators have to have the same order? What happens if several creators have the same OU? Does the OU have to be repeated? --Nicole 18:51, 24 March 2009 (UTC)

Rupert:

Authors manually

  1. Authors are filled in either by typing in names operating dropdowns (role, type: Person/Org)
  2. A line can be added/removed by clicking the plus symbol

Authors automatically

  1. The lines are populated according to the autodetect we have already (missing fields are typed in manually)

Organizations manually

  1. Organizations are filled in either by typing in name and address
  2. A line can be added/removed by clicking the plus symbol
  3. All Organization names are numbered

Organizations automatically

  1. The lines are populated similar to the autodetect of authors (Cut&Paste, each org separated by line break Address and Org. name are separated by comma)
  2. From the org tree, they can be fetched by "select new" button
  3. All Organization names are numbered

If the list contains at least one author and one affiliation, each author can be affiliated to a person by entering footnotes in the field "Organization" Example:

Peter Müller 1,3,5 Hans Maier 3,5,7

That means Müller and Maier have affiliation 3 and 5.

Question Nicole:

  • Copy and paste for OUs sound good, but how will these names be connected to the OU tree. Should be checked with dev. team. Further more we should check how adding multiple authors and OUs is related to CoNE. --Nicole 11:50, 7 April 2009 (UTC)

Other features will be extended, when spec is clear:[edit]

institutional visibility access rights (colaborator, audience)

Search String display[edit]

  • should also contain button to hide query. Is also missing in current implementation. --Nicole 18:49, 24 March 2009 (UTC)

Import[edit]

  • the prototype for import is different from the current implementation. In the current implementation import and fetch full text/MD are on separate pages, in the prototype it is only one page. Does that mean, that the current implementation should be changed? --Nicole 18:53, 24 March 2009 (UTC)
  • due to implementation effort, the first step is different from prototype, submission startpage will be extended with multiple import text (clarified with Michael) and will be aligned later with prototype if possible. --Rupert 08:51, 20 April 2009 (UTC)

Feedback, not related to the current prototype. For now only above issues are included and can be discussed![edit]

  • Search also not clear. See under advanced search. --Nicole 19:14, 24 March 2009 (UTC)
  • We wanted to have seperate search indexes for files and locators. If this is possible for R5 the prototype needs to be changed. --Nicole 18:54, 24 March 2009 (UTC)

Rupert: Could not find locators it in func spec as separate search option. --Rupert 14:15, 26 March 2009 (UTC)

  • The agreed change for the search for OU is not presented in the prototype. Pls. check JIRA. In R5 we will have to options to search for OUs. We have one free text field and we have a field, which we can fill with OU ID, selected from the tree. --Nicole 18:56, 24 March 2009 (UTC)

Rupert: Also, this needs to be in the func spec UC_PM_SR_03 Do advanced search. --Rupert 14:15, 26 March 2009 (UTC)

  • I think it is not clear from the prototype how the search for successor or predessor OUs shall be realized. I think the user should also be able to understand the structure and not just include or not the affiliation history. --Nicole 19:11, 24 March 2009 (UTC)

Rupert: It would be very good to have the structure explained in the GUI. But as we are more and more taking reusable components we are not free to create a specific org search here. At least a section of the manual should explain it. --Rupert 14:15, 26 March 2009 (UTC)

  • no, you added search for locators... we currently don't have a search index for locators. --Nicole 18:49, 24 March 2009 (UTC)


Handover meeting outcome, 29.10.2008[edit]

Candidates

Agreement: The following will be implemented 'if possible' by the following order of priority:

  1. Table List
  2. Dependent sorting Options between bibl. and table view
  3. Tooltips 1. Step (Depends on resources of SvM). 1. Step means: At least in header area and important elements (Form Buttons, Icons, Menus ...) a tooltip is applied. For the following release tooltips should be available completely to ensure accessibility, see GUI_Accessibility
  4. Org filter
  5. Last released Items

In (Part of the FPT and to be developed for R4)

Browse and Display - Message line syntax: Nr. of Items (Filter Options) - Sorting options in menu of Table View

My Tasks - needs to be revised, renaming needed (check with SvM)

Search - Search string as output text hidden layer under revise search -> Show/Hide (replacing the message)

Submission - No tabs but Skip Links to sources. Skip link navigates to source and opens the group - Item is shown with all sources Order (Matrix will be aligned):

Group: Basic

  • Genre
  • Title

Group: Files

Group: Locator

Group: Creator

Group: Content

  • Free Keywords (hint for separating character
  • Abstract

Group: Details

Date inputs are all shown in Full Submission. In easy submission only one date input will be shown with the option to choose a type (done on client side)

Out (Not to be developed for R4)

Start Page - News box (right side)

Browse and Display - sorting options/ more - sorting by files

Breadcrumb - new logic will not be part of R4 (postponed for bookmarkable searches

View Item Version - Revisions/Release History/... Replace dynamic short views. Jump to Item (Revisions, Releases, ...). To be aligned to current functionality - Withdrawn Item: Should be aligned to R3.8, not like func spec (postponed)

Easy Submission - Import files do not have properties - upload button is useless ("next" triggers upload)

Advanced Serch - Admin search is subject to a later release

Decisions taken

  • Fields displayed (in short-, medium view) derive from the genre matrix. The FPT is only an exemplary visualization.
  • Empty fields (in short-, medium view) are shown without value the term "no entry" will not be shown any more
  • FPT should show total number of pages besides
  • Filters not in search result (not in options menu and actions menu)
  • Wording: View Item version replace "Visibility" -> "Show/Hide"
  • Show/Hide always with corresponding labels (e.g. Show creators)
  • Wording options menu: Viewing Options, Sorting Options
  • Wording: Table List -> Table View
  • Add Select Option: None on this page/on all pages
  • Collection is also chosen by clicking on label (expand click target)
  • Submission shows a message about collection (link to collection description)
  • Add remove needs to be attached to date field in Easy Submission
  • Import: Upload file and fetch external are actions in the action menu
  • Advanced Search: Show/Hide for groups
  • Wording: more/less within groups
  • Advanced Search: Include files also needs "none" (default)
  • Advanced Search: Options for term are: Title, Keywords, any filed, any field plus files,

Next steps As we would like to get a more clear picture of the effort, Markus M. will start working with preparations of JSPFs exclusively for the next two weeks with dev (Presentation/Tobias). At the end of week 44 and next week 45 a status will be given.

R3 Prototype[edit]

Feedback of internal GUI Preview for R3 by UIE

Depositor Workspace

  • Action Menu/Help is now in H1 Title (done)
  • Flags should have a space to the top (done)

Submission

  • Only menus should be fixed. The header should not move (done)
  • Submission form should not overlap with action menu (done)
  • Clickable area of radio buttons should cover labels as well (Label for ...) (done)
  • Next/Back buttons for wizard lower (done)
  • Please provide button varieties + alignment of text (vertically centered) (done)
  • @Denise: Colours for input fields (yellow, yellow light) should be redefined (done and implemented)
  • @Denise/Rupert: please unify icons (done)
  • Asterisk should stand left of mandatory fields (done); please add TITLE tag: Mandatroy (Tooltip) (done)
  • Move language box higher (done)
  • margin of labels: margin to above should be bigger than margin between label and field (done)
  • Inline add button should be aligned to bottom of form (done)
  • Add form icon + text font smaller (same font as Labels) (done)
  • Evaluate blueprint css framework (not R3)
  • "Path" label has bigger font-size than other labels (done)

List Display

  • Paginator disabled should be visible (done)
  • Redesign filetypes icons (done and implemented)
  • "Showing" pull down list should be extended to display 3 digit-number (done)

Advanced Search

  • Align checkboxes
  • Show/Hide as links only (Displaygroup)


Organizations

  • Show/Hide (clearify with dev - no windows)

Export

  • Remove
    above display (done)
  • Align radio buttons (done)
  • Font size for export menu labels is different then for Deposit menu labels (no, because the ones are radio-button-labels and the other are links)

Preview 25.04.2008:

  • Help Icon smaller (done)
  • Hover Effekte in Blau
  • Klammer für Locators überarbeiten (done)
  • Inline Anchors must be available (Page jumps) -> Prio
  • Label "Dateiadresse" für Locator änern (Done)
  • Validation Message (Formatierung fehlt ganz) -> Prio (done)
  • Nach Fileupload und Save erscheint die Gruppe File leer (fixed)
  • Hover für Button Curser fehlt noch (done)
  • EAS Step 3 Radio Button für BibTech zu hoch (done)
  • Mandatory fields with text: (* are mandatory) (done)
  • Radiobuttons für Visibility to narrow (done)
  • Box für uploaded File + Locator (EAS) (done)
  • Add Buttons zu hoch in der Schrifthöhe (done)
  • Show/Hide für öffnen/ (done)
  • Sort Ascending/Descending Button (Buchstabe A verwirrend) (done)
  • Export Mailform Send Back smaller (done)
  • Header Link Advanced Search soll genauso groß sein wie Label vom benachbarter checkbox (?)
  • Menü für Item actions (Revisions ... soll als Metadatenfeld erscheinen) (done)



Feedback from Nijmegen taken by Ulla:

  • workspace (internal areay) vs. "open" area of repository unclear (e.g. scenario searching for pending items)
  • advanced search: oeffnen der einzelnen boxen umstaendlich bzw nicht sichtbar...Nutzer merkt nicht, dass er eigentlich noch boxen oeffnen kann, um nach mehr details suchen zu koennen.
  • Hilfetexte edit mask
  • Pre-selection of all items by default(scenario export)
Proposal: Select items (all, items on this page, none ) pull-down list can be taken to the Export menu completely (R4).--Natasa 09:48, 22 April 2008 (CEST)
  • Systemmessages validation => DCterms are mentioned, are different to GUI labels
  • Icons for selecting different display types not understandable
  • In addition, no icons in item list, just in view item version
  • proposal for short display: short display should be default, can be "enlarged" by clikcing on title
  • Change label "submit" to "submit and release"
  • Workspace: provide "all" in filter for status of items
  • org unit search not clear..what to expect?
  • export: download button not clear, user expects to download the arcticle (connotation "download")