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: May 5th
  
  • 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 113 planning
2. Dashboard and Widget sharing and copying options proposal
   1. Please read and add your responses to this proposal document
3. Widget configuration - date and date offset UX
   1. Please read and add your responses to this document about the UX for date and date offsets in widget configuration

Minutes

Development Udpdate

• Limited capacity still due to some absences
• a lot of time spent for Iris release - some minor tweaks were neceassary that are done now
• work on dashboard - application now appears on hosted refence environments - but cannot be used currently because the widgets are missing
• after this issue is resolved people can start testing the functionality
• changes to the way organizations work in agreements are not completed - will be as soon as possible - team will focus on those

Dashboard and Widget sharing and copying options proposal

• proposal document
• this proposal is following this group's feedback and input from the last meeting's discussion
• terminology definitions
  • "sharing" - the ERM group agrees to this term
    • "Sharing" will mean making it possible for multiple users to get access to a single thing. Changes to the one thing will affect all users who are using it. Different users may have different levels of access to the thing (i.e. edit vs view-only)
  • "copying" - the ERM group agrees to this term
    • "Copying" will mean making a copy of an existing thing. Once a copy has been made there is no link between the original and the copy
• initial approach in the proposal
  • widgets can be copied
  • dashboards including its widgets can be shared
• question by Eric: if I am sharing someone else created can I add widgets to it
  • Owen's answer: you will be able to share and decide which privileges the person the dashboard is shared with (as in Google docs) - e.g. view only or edit
• widget search modal: description field shows what the widgets does
• the group agrees that the correct priorities are developed for dashboard functionalities
• default for copying widgets options
  • should be controllable but default to public is what most members of the group would expect
  • there is a discussion about lists of widgets getting quite long if the defaukt is "public", e.g. in the 5C example
  • Martina Karlsson in chat: I don't think our list would be that long for us, it wouldn't be a problem, so I still like to have them public as default. Default to private it's so easy to forget to make it public.
  • templates are proposed - Owen will discuss the idea of a template with the ERM team
• Sara asks about widget deletions
  • as widgets will not be shared but copied this is no issue
• would it be more important to be able to add users to a dashboard (A) or should users be able to search for public dashboards (B)
  • the group agrees on being able to add users to a dashboard as being the preferred option (A)
• question by Sara: can users have multiple dashboards - answer by Owen: yes
  • Eric in chat: That answers my initial question. I had in mind that there'd only be one dashboard per account.
• coming back to deletions: the deletion of a shared dashboard will only be possible if it is not used
• for widgets this is different, because they are copied, not shared
• suggestion: maybe deleted dashboards can change ownership and will be moved to a shard place if one user deletes them - as in Google drive
  • worries: this requires someone who takes car of that
  • there have been situations were it did not work - comment by Jack in chat: We've had that exact issue multiple times with Google Drive :)
• Owen asks the group to add additional feedback to this document
• Owen will let people know on the ERM-team slack channel when the dashboard functionality can be tested on the hosted reference environments

Chat

Von Jack Mulvaney an alle:  02:19 PM
I just realized that the term "Duplicate" is used for Agreements and I think also in licenses.

Von Jack Mulvaney an alle:  02:36 PM
That's how I've been imagining this tenant list

Von Martina Karlsson an alle:  02:38 PM
I don't think our list would be that long for us, it wouldn't be a problem, so I still like to have them public as default. Default to private it's so easy to forget to make it public.

Von Eric Hartnett an alle:  02:51 PM
That answers my initial question. I had in mind that there'd only be one dashboard per account.

Von NELA Zoom2 an alle:  02:52 PM
Maybe it becomes public if you delete a shared dashboard but allows you to remove it.

Von Jack Mulvaney an alle:  02:56 PM
We've had that exact issue multiple times with Google Drive :)

Von Gill Osguthorpe an alle:  02:59 PM
I am, thanks for all the feedback so far :)

Attendees list