Skip to end of metadata
Go to start of metadata

Project Admin multi project Overview Dashboard: Schematic

A card sorting exercise with post-it notes was carried out. It involved all functionality marked from the functional spec, taken from the lists at the back and the sections referring to dashboards. Post-it notes representing themes/actions were grouped by common functionality

  • Each section above has common actions that make sense to be grouped together
  • The "Page widgets" section will change depending on what tool / action you are doing on the site
  • the Main nav, tabs and communication tools are present across all user groups.
  • Blue dots show items that are not available to non-admin Project member

Project admin multi project Dashboard: Wireframe

The yellow stickies on the right represent notes / additional functions on each element

Discussion

Dominic:

  • There is a difference between the Adminstrator and the Project Administrator.
  • The Administrator administrates the ResearchSpace environment and the Project Adminstrator administrates the projects (I may have confused terminology between the project Adminstrator and the project lead. The fundemental thing is that the former does not adminsytaer a project but administers all the projects. The Administrator is concerned about ther whole environment and the Project Administrator is concerned only about what is happening in his or her project.
  • An Administrator will create the initial space for the project. It is not a documented functiona that a Project Administrator can create a project although this may be delegated where an organisation has subscribed and can have a number of projects under their subscription. However, each project administrator may be different from others in the same orgrnaisation.
  • The RS Administrator is concerned with the overall use of the infrastrcuture in terms of storage space etc. The project administrator is concerned only with the capaciaty and space provided for their individual project.
  • An Administrator would create the project, assign an user account for the Project Administrator and the project Administrator would then create the accounts for the rest of the team.
  • Project Administrators, alert the RS Administrator while project team members alert their Project Administrator.
  • The RS Administrator is a consistent role comissioned by RS while Project Administrators are the temporary project leads that come and go with their projects.

Hollie: If the project admins will only be on one project this dashboard in not needed as they would only ever see a single project and not need this overview.

Dominic: It is possible that a user is Project administrator for two projects.

  • I am not sure how this works from a system and dashboard perspective.
  • I would hope that they would have one username and password and could select which project to administer.
  • Vladimir: Sure. Upon login, the user selects which project they will work with (to determine the space and RDF graph he has access to). He can switch to another project later.

HL: I suggest we have a launchpad or similar to the interaction that basecamp uses, I find it very easy to change projects.

  • login
  • splashpage (launchpad) with all projects listed, users selects correct project
  • User enters single project dashboard, can use "launchpad nav" to get back to the splashpage.

Vladimir (e-mail from 26.10.2011): General Feedback

  • they are useful to start figuring out the navigation from the top down
  • if Nuxeo has a different way of doing menus/dashboards, we'd like to stick with that unless it cannot provide the required functioanlity
  • for the current 2 iterations, we can make more use of a UI mockup for displaying data RS-38@jira
  • re 3 Search: please get the 3D COFORM Semantic Search mockups from Dominic and improve on these
  • re 3 Search results: we'll be using Exhibit. Please check out the Exhibit demos (is there a Lightbox amongst them?)

Maria: Please review Nuxeo Dashboard page. There I have put a screen shot from a Personal Dashboard in Nuxeo, where each user will be able to see all projects he is participating in, and to select a project. The user logs in with the  same username and password for all projects.

Austin Nevin: If users would have a single login-password for all projects, would it make sense for users to set up a "profile" - as has been done for this site? This would allow project administrators to automatically add already registered users to projects or alternatively create new profiles for different users - is this type of functionality anticipated in a "user screen" (not yet shown)?

  • Vladimir: Certainly the project admin will be able to select from existing users, either when setting up a project or later
  • Adding new users:
    • maybe it's better to restrict this to a sys admin only (eg a project admin in Jira cannot add users)
    • or on the opposite end of the spectrum, we could even allow self-registration of users to ResearchSpace
  • User profile (photo, info, preferences): I don't think this is in RS3 scope, but it's simple so we may be able to accommodate it.
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 30, 2011

    If users would have a single login-password for all projects, would it make sense for users to set up a "profile" - as has been done for this site? This would allow project administrators to automatically add already registered users to projects or alternatively create new profiles for different users. - is this type of functionality anticipated in a "user screen" (not yet shown)? 

    1. Oct 31, 2011

      I've copied the comment into the main body, because that way it'll be easier to turn into a spec later when the discussion crystallizes into some decisions.
      I've used names instead of initials because I think it's easier to figure out who said what in this way.