Meeting Time:    8 am EST / 2 pm CET / 1 pm UK

Call in Number: https://zoom.us/j/995679876 

Meeting URL:  https://zoom.us/j/995679876  -  Password needed - please see link here: https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Meetings+with+Zoom

ERM Group Folio Wiki: https://folio-org.atlassian.net/wiki/display/RM/ERM+Sub+Group 

Google Folder: https://drive.google.com/drive/folders/17X3tr6siZH8iS07kGcjAqUNl01zVrJmB

Terms and definitions: https://docs.google.com/document/d/1vue-mbcULpZivWu69a7nAZEdC-H2yXPQqSblbL_0J6U

Slack Channel: # erm-team

Housekeeping: 

• Convener: Martina T.

• Notetaker: Martina S.

• All: Please edit the attendees list below and indicate when you are there!

• Next ERM meeting: April 28

  • all questions and topics for the ERM implementers meeting can be posted on the ERM Implementers page

• Open discuss posts: -

Agenda items:

1. Development progress - ERM sprint 112 planning

2. Dashboard - see homework

Homework

Please read and respond to the questions about widget sharing and widget management in the linked document.

Minutes

Development progress update

• focus of sprint 112 is fixing issues arising from Iris bugfest

• sprint 112 finishes end of this week

• work on getting dashboard ready to be available on hosted reference environments - planned for end of this week

• functionality planned to be delivered for Juniper release

Dashboard - including homework

• at the moment the dashboard is a personal view of data

• configuration is up to the individual users

• questions: do we need to be able to configure complete dashboards on behalf of other users (pre-configured dashboards) and should this be editable or not

• currently sharing is not possible

• Sara asks in chat: Can one have more than one dashboard?

  • Owen: that is theoretically possible; but no work has been done yet to support adding dashboards;

  • but it would be possible from a design point of view to have multiple dashboards;

  • so far, there is just no button to add dashboards

  • example by Sara: there are pre-configured dashboards for student staff; in addition, they might want to have and set up an own dashboard

• that is one use case; another solution would be to share a dashboard that the other user can edit

Homework question 1

• B + C seem to be the most preferred options

• difference:

  • for option B, a user is starting with an empty screen and would add pre-configured widgets

  • for option C, there is a complete dashboard that is pre-configured for a user; the pre-configured dashboard is editable

• we are aiming to release an ERM focused dashboard for Juniper

• is to be delivered for a range of ERM use cases

• but the goal is to have the dashboard be used across Folio; this might mean that more use cases will need to be included for a future iteration

• Jack: going with B would meet an immediate need

• Sara: the curated dashboard might be good to introduce student workers to Folio; when they are trained after some weeks or months, they could create their own

• Owen: the question is, whether the curated dashboard should be kept up to date on behalf of the student worker; or whether it is created for them but can be edited

• Jack: if there is an ERM dashboard that is shared with several people, it should never be locked

• Kristen: dashboards would not be used so much by students; they rather work on projects

  • a dashboard as a "starter kit" would be nice

  • would not be needed with so high priority; there could be workarounds

• acq teams come up as something to take into account for the dashboard

Homework question 3

• be able to select the app the widgets is for first

• have a name and description display - to know what the widget does/displays

• Scott in chat: An App garage. Something like when you add or take away functions on an App (e.g., MS WORD) tool bar/task bar.

Homework question 4

• yes, the group would like to be able to share widgets

• especially if the widgets are more complicated to set up

• this would definitely something that users would find the time to do

• from time to time new data points will be available that need tracking; new widgets will be needed that can definitely be shared

• would be good to be able to mark those as public or private

Homework question 5

• how would users want to share widgets - seeing your own version of another users's widget or as a copy that the other users can build on

• if only one option of the two is available, the group tends to option B

  • (if looking at the different options described in the homework separately)

• otherwise, if that pre-configured dashboards will be available, it is option A, because with pre-configured dashboards option B is already covered in a way

In general

• as a follow up to this discussion Owen and Gill will work on designs and wireframes

• the option to delete widgets seems to be key

Chat

Von scolglaz@mtholyoke.edu an alle:  02:10 PM
Can one have more than one dashboard?

Von Scott Stangroom an alle:  02:41 PM
If widgets are to aid in work or workflow of different people, then the option to pick is the one most suited to that. Option B.

+1 Sara and Jack

Von Benjamin Ahlborn an alle:  02:46 PM
+1 for a managed Dashboard in contrast to managed Widgets -  makes things much clearer (for me)

Von Scott Stangroom an alle:  02:48 PM
An App garage. Something like when you add or take away functions on an App (e.g., MS WORD) tool bar/task bar.

Attendees list