Talk:OJS Dashboard

From PKP Wiki
Revision as of 10:53, 8 May 2014 by Alec (Talk | contribs)

Jump to: navigation, search

Bruno's new screenshots

  • About category rows...
    • What categories are we proposing? I currently see...
      • Unassigned
      • My Assigned
      • My Authored
      • Active [this will be confusing, as entries in any of the above 3 can also be considered "active"]
    • Are there others, and how do we handle items potentially appearing in several categories?
    • Will this be confusing for users who have just a single category, e.g. reviewers?
  • The key motivation for the dashboard was to provide an answer to the question "What do I need to do?" at a glance. Does this answer that question?
  • Would the "Archive" still exist as a separate tab, and would it be affected by the changes proposed here?
  • Just to confirm -- does this mean we're making the dashboard fully context (e.g. journal) specific, and that there will be no more global dashboard?
  • What about tasks that don't belong to a particular submission? OTOH we don't have any of these, but it was discussed.

--Alec (talk) 16:10, 7 May 2014 (PDT)

  • Active is anything that's being under editorial process that doesn't fits the above categories.
  • Item should only appear in one category. I don't see need for more categories.
  • Categories should not appear if they have no items, so reviewers will not see them all.
  • I think that's why we need to keep the tasks tab (see at a glance what we have to do).
  • Archive should exist, but I don't see the need to show tasks there.
  • Dashboard should still be global. I still think it's good to have a checkbox to enable it, and as soon it is enabled, users can interact with context filters for the grids (both tasks and submissions).
  • That's another reason I don't think it's good to remove the tasks tab.

--Beghelli (talk) 18:30, 7 May 2014 (PDT)

Agree with above, although we need to experiment with task tab. Further on the icon discussion, we do want the eye to go to the tasks so I'm ready to think about icons for this. For the editor, we may want to just bell their tasks, while indicating that their section editors have tasks outstanding on their submissions but without requiring the same level of attention. The Unassigned needs no additional attention, as every item there needs the same thing every time one appears.

In that sense, I ask you to look again at this screen shot and ask yourself whether a red bell with the number 1 or 2 in it is needed to draw your attention to the presence of a task, compared to the current use of asterisks indicating a task. I am not arguing for the asterisk but only for using no more of an icon than is needed in scanning a list (and thus am not yet entirely an iconoclast). We need to think of this as a list that the eye scans down checking where things are at and what needs to be done. Google uses the bell to bring your to a part of the screen you are not otherwise considering; this is a dashboard and what you are checking is the status of tasks.

--Jwillinsky (talk) 23:41, 7 May 2014 (PDT)

The global vs. context-specific nature of the dashboard bleeds into the global navigation discussion. This specifically caused a lot of the global navigation confusion...

  • It's the only exception to "global nav goes on the very top navbar" (journals pulldown, administration link, user profile link...)
  • It potentially presents the contents of one journal styled in the format of another

I liked the proposal at to make the dashboard context-specific by default, but allow the filtering tools to extend to other contexts at the user's choice.

John, I thought your proposal was a replacement for both submissions and tasks tabs. I don't have a strong opinion either way, but we are trying to avoid presenting the same content in multiple places as a general rule.

Bruno, for reviewers who have a single submission (a common case), this will look like...

  • Submissions
    • Active
      • My Submission Title

--Alec (talk) 10:52, 8 May 2014 (PDT)