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 26th

  • 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 update - ERM sprint 114

2. Dashboard progress update

   1. Feedback on date search UI

   2. Feedback on sharing of dashboards and widgets

   3. Expectations for Dashboard in the Juniper release

Minutes

Development progress update - ERM sprint 114

• a lot of work related to the dashboard

• more resource on the team; there is a new member

• work on automated testing; target is end of September for that work being done

• progress with changes to the way organizations are managed 

• 3 weeks away from feature freeze; there is a chance that the dashboard will be part of Juniper

• few bugfixes going on

• sorting agreements by start and end date in agreements result screen; sort on those will be part of the Juniper release

Dashboard progress update

Feedback on date search UI

• when creating a widget:

• changes to filtering by date are made

• feedback on these changes and the new layout is very welcome

• maybe this will be avilable for Juniper, maybe for Kiwi

Feedback on sharing of dashboards and widgets

• the following will be developed as consequence of our discussions

• first approach

  • firstly, there will be a single dashboard design by one person

  • with access for other people from your team

  • it may be in addition to dashboards they can view, that they created for themselves

  • so dashboards can be shared; they cannot be changed by the other members; just by the one person who created it

• second approach

  • it will be possible to copy a widget and using it as a starting point to create an own widget

  • there will be a list of available widgets

• there are still open questions such as:

  • how do users share a dashboard

  • can there be multiple owners on one dashboard

  • what if someone deletes a dashboard

Expectations for Dashboard in the Juniper release

• expectations and use cases are collected on a spreadsheet

• the spreadsheet has a column that displays whether use cases can be solved with the next release 

• available will be 

  • filters for approaching end dates or cancellation deadlines

  • filters for agreements with a specific status 

  • filters on renewal priority

  • possibly partial support: filter on whether an agreement has an agreement line or not; will work for internal KB and eholdings users

  • possibly partial support: filter on agreements without organizations or with specific organization roles; there are some limitations, so not all use cases might be solved; searching on organizations and organization roles will be possible

  • filters on tags (to pin agreements); it will be possible to display concrete single agreements

  • filters on jobs of the internal KB

  • partial support: filters on possible job errors 

  • filters for license end dates or some other information related tot he license

  • filters for recently changed licenses under user's responsibility - most likely

  • licenses with organizations or organization roles - same as fr agreements

• not available in the next release will be 

  • filters on unassigned license amendments

  • filters on ended amendments or licenses

  • filters on dropped resources (for internal KB users)

  • filters on title changes; e.g. when titles left a package

  • filters on licenses with primary terms; is still under investigation but most likely not part of the next release

  • filters for list of tasks from a tasks list

  • filters for sticky notes

  • eusage: filters on new usage statistics

  • filters on platform availability

  • RSS feed

• question: What is the character limit on the names for the individual widgets?

  • it is 255 characters 

  • ERM team discussed a description field for what a widgets is doing or a self-summarization of the widgets for display in the title of the widget

• Question from Owen: do people know already whether they will definitely use Juniper?

• in chat:

  • Fom Felix Hemme (ZBW): We're likely to upgrade but we need to upgrade to Iris before.
    From Jack Mulvaney 
    Five Colleges will eventually upgrade to every version, we're slated for Iris in end of June.

• Cornell: expect to use each version

• same applies for Duke

Additional questions from Owen:

• search by agreement name: user can use filter "contains"; in widgets the ERM team has implemented the filters but not the match; match would be the more complicated piece of work

• Jack raised before in Slack: this could be a problem because 5C starts each agreement name with an abbreviation for the individual college

• Owen will havecheck on possible solutions

• link to full search results: behind each results display is a search; initially it was planned to have  a link to the full search results; in the widget the number of rows displayed is limited when setting up the widget

• do people feel this is important to have

• Jack in chat: I think as long as I can copy & paste the License Name from the list that's good for the first round

• workaround would: set number of results displayed to 100, which is the highes value to choose

• Owen will post the above question and two more remaining in Slack to hear more feedback

Chat

Von Jack Mulvaney an alle:  02:22 PM
What is the character limit on the names for the individual widgets?

Von Felix Hemme (ZBW) an alle:  02:29 PM
It's 255 characters. Just tested it on Folio-snapshot
Von Jack Mulvaney an alle:  02:29 PM
Perfect - I don't think we'd hit that
Von Sara Colglazier (MHC/5C) an alle:  02:29 PM
Yes, the what purpose  is importnatn, too

not just for sharing but also for down the road

And I really like the idea of a widget self-summarizing what it is doing!
Von Felix Hemme (ZBW) an alle:  02:31 PM
Yes/no is good for the beginning!
Von Jack Mulvaney an alle:  02:32 PM
Agreed - I have a bunch of notes on my desktop right now for specific agreements that I have to go and clean something up before adding AGLs.

Von Felix Hemme (ZBW) an alle:  02:35 PM
No problem -- we changed our workflow for creating and linking orgs to agreements so nothing urgent.

Von Felix Hemme (ZBW) an alle:  02:48 PM
We're likely to upgrade but we need to upgrade to Iris before.
Von Jack Mulvaney an alle:  02:48 PM
Five Colleges will eventually upgrade to every version, we're slated for Iris in end of June.

I don't remember off the top of my head what version will be used for our ILS migration

Von Abigail Wickes an alle:  02:49 PM
I expect Duke will upgrade for each version as well, but I'm not sure about skipping. I'm sure it will depend on functionality like you say Owen

Von Jack Mulvaney an alle:  02:59 PM
I think as long as I can copy & paste the License Name from the list that's good for the first round

Attendees list