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 below

https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Meetings+with+Zoom

ERM Sub SIG 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

Agenda July 21st 2021

Convener: Martina T.

Notetaker: Martina S.

Housekeeping

• All: Please edit the attendees list below and indicate when you are there!
• Next ERM meeting: July 28th
  
• all questions and topics for the ERM implementers meeting can be posted on this confluence page: https://folio-org.atlassian.net/wiki/display/RM/ERM+implementers 
• Open discuss posts: right now no new posts regarding erm

Agenda items

1. Development progress - ERM sprint 119
2. FOLIO Roadmap ideas (Roadmap development team)
   1. Roadmap questions

Minutes

Development updates

• we are in sprint 119
• in Kiwi release the goal was to slow down and consolidate
• in ERM there were smaller changes picked up - that would improve the system 
• Owen thanks people for picking up testcases in bug fest 
• Owen shows the testrail 
• there are only few test cases that have failed
  • e.g. "add platform URL customization" - Owen will add information in the release notes for the edge case situations that led to this test case being failed
• there are some incremental fixes:
  • for Licenses or Agreements with documents/files attached - everyone is able to download the attached documents
    • a separate permission has been added that allows to download the files
    • this prevents users without the permission to be able to download documents that they should not have access to - e.g. the license contract that could be attached as core document tot the license
    • the permission is just for the download - users could still follow the URL or see the physical location
    • file upload is still managed via the "edit license permission"
  • Amendment: on the amendment user can see whether it is applied to an agreements - what the status is of the amendment for the linked agreement
    • Virginia: on the amendment record it would be usefull to be able to see the other amendments of the license as well
    • this would help clarify if the user is on the right amendment
    • this request is noted and will be added to the development
  • created and last updated date: user can see that on the license and the amendment
    • these dates are coming soon to agreements as well
  • some keyboard shortcuts are supported by the ERM apps
  • Agreements - on the Agreement lines - in the e-resources list: there is the e-resource icon displaying now

Folio Roadmap

• The Roadmap development group is tasked with modelling a Release planning/Roadmap.
• Members
  • Jesse Koennecke, Chair - Cornell
  • Kristin Martin - Chicago
  • Karen Newbery - Duke
  • Björn Muschall - Leipzig
  • Tod Olson - Chicago
  • Martina Schildt - VZG/GBV
  • Brooks Travis - Missouri State
  • Sharon Wiles-Young - Lehigh
  • Tom Wilson - Alabama
• To achieve that, the group gathered initiatives, ideas and open features and grouped those via themes.
• List of revised themes: Roadmap Themes
• The goal is to visualize the themes and related epics/features on a roadmap/timeline.

Questions:

Q1: Is an annual cycle appropriate and useful? 

• Sara Colglazier (MHC/5C) in chat: More, more like 3 years at least
• Sarah Dennis in chat: more than a year
• Jack Mulvaney in chat: I think what Kristin is saying makes sense. When I'm looking at documents like this for other systems I assume the things further out are not set in stone anyways so I wouldn't focus on much more than the first year

Q2: What should be included in the Roadmap?

• Related to this question it might be helpful to look at the Kiwi pointing exercise priorities - Pointing results for Kiwi release

Additional answers:

• More control by individual users to control what they see on the screen (UI)
• Persistent URL generator
• Container records in Inventory
• Serials management in ACQ
• ERM SIG would like to see functionality, that is no longer developed - would like to see the status of development
• Codex is mentioned

Q3: How should the Roadmap be presented to help your group?

Q4: Do you have any plans or projected Epics/features that should or could be included?

• What features or Epics are your highest priorities?
• For which features are you currently working on specs?

Q5: What questions do you have?

• How do you see the relationship between the roadmap and independent development teams?
• What level does the roadmap aim at
• Do you see the roadmap as setting a direction, or summarising the existing plans?
• what happens to those items that get deprioritized, and how do we indicate that?
• who ultimately is the audience for the roadmap
• will we need multiple views for multiple audiences?

Chat

Von Jack Mulvaney an alle:  02:28 PM
I am also very excited for the UI changes in Iris

Von Sara Colglazier (MHC/5C) an alle:  02:36 PM
More, more like 3 years at least
Von Sarah Dennis an alle:  02:36 PM
more than a year
Von Jack Mulvaney an alle:  02:38 PM
I think what Kristin is saying makes sense. When I'm looking at documents like this for other systems I assume the things further out are not set in stone anyways so I wouldn't focus on much more than the first year
Von Owen Stephens an alle:  02:39 PM
How do you see the relationship between the roadmap and independent development teams?
Von Owen Stephens an alle:  02:48 PM
I think my concern is what level the roadmap is aimed at
Von Sara Colglazier (MHC/5C) an alle:  02:49 PM
More control by individual users to control what they see on the screen (UI)
Von Owen Stephens an alle:  02:51 PM
Perhaps related - do you see the roadmap as setting a direction, or summarising the existing plans?
Von Owen Stephens an alle:  02:58 PM
Thanks. Whatever the decisions I think that needs to be clear as the roadmap is developed and communicated

Attendees list