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 SIG Folio Wiki: https://folio-org.atlassian.net/wiki/display/ERMSIG/

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 Oct 19th 2022

Convener: Martina S.

Notetaker: Martina T.

Housekeeping

• All: Please edit the attendees list below and indicate when you are there!
• Next ERM meeting:  02 Nov 2022  | 1 hour earlier for the Europeans due to time change
  
• all questions and topics for the ERM implementers meeting can be posted on this confluence page: https://folio-org.atlassian.net/wiki/x/SABS
• Open discuss posts: right now no new posts regarding erm
• PC meeting Oct 6
• PC meeting Oct 13

Agenda items

1. Development progress - ERM sprint 151
2. PC Questions ERM SIG - homework document

Minutes

• Development progress - ERM sprint 151

  • Feature freeze for Nolana was last week

  • This ERM Sprint - preparing for the release of Nolana and bug fixing (no new feature planned for this ERM sprint)

  • Preparation for Bugfest Nolana – new tests written for testrail and working on setup for the bugfest environment – making sure ERM ready for testing starting Nov. 7th

  • Owen will present on development plans for Orchid to the ERM SIG in a future meeting.  

  • Felix (chat): Owen, has the extension of GOKb metadata made it into Nolana, maybe with exception to package identifiers.
    • yes including package Identifiers

    • Comprehensive set of GOKb metadata updates:  Content type, Availability, GOKb ID and GOKb UUID, Package description URLs, Alternative name, Identifiers including ISIL, ZDB

    • + Filter in the left search & filter pane are available as well

    • Updates from GOKb when it changes in GOKb where appropriate

    • At the moment when a Title is changing in GOKb that will result in a new package in FOLIO → found out last week and looking into this for orchid 

• PC Questions ERM SIG - homework document

  • PC has asked those questions to the SIGs to check on activity of groups and subgroups and is interesting in improving communications

  • 2. What areas does your SIG have responsibility for?

    • Sara: Integrations with different apps – eHoldings, Organisations, Orders should be reflected here as well

    • Owen: SIGs is responsible to listen to requirements across ERM and look how this can be processed, but the available actions are not always directly going into development.

    • Jack (chat): So we have more direct responsibility over the apps that you and the code team have responsibility for developing, and indirect responsibility over a larger amount of FOLIO due to the integrations

    • Owen: SIG responsible of area of ERM, If someone starts working on a new app around ERM in the future, it should not have its own new SIG, but it would be discussed here as well – integrating themselves into the community, environment, into the other apps in this space.  

  • 3. What do you feel like your SIGs purpose is currently? Has it changed over time?

    • Jack: changed from SubSIG of RM to ERM SIG

    • Owen: significant change, change in emphasis, started from scratch (discussing how to build it meeting the needs of ERM), now seeing the discussion on how to improve what we have and not how should we approach generally, Have more implementers – new issues, bugfixes and improvements 

    • Sara: change to SIG – recognized by the library community that ERM is very important part of libraries

    • Owen (chat): And that had to be fought for - so thank you for all that added their voices to that in this community

  • 5. How do you feel about the resources allocated in the development areas that we are focused on?

    • Jack: very well supported, successful SIG – more than in other areas  

    • Sara (chat): Thank goodness for Owen! And the Martinas!!

    • Julie (chat): +1 to Jack - very well supported in the ERM SIG by our PO and dev team! Yes - +1 to Sara about the consistent, diligent leadership of our conveners too

    • Sara: conveners are important, most productive group, good conversations, Owen asks great questions and how we have homework

    • Martina S.: very good and communicative group – team effort conveners, PO, group is defining the requirements, developers and Gill as UX designer

  • 6. What are some of the challenges facing your SIG/subgroup? Are there ways in which you feel the SIG has been unable to accomplish its mission?
    • Owen: areas integrations - we are not always able to deliver the level of integration that the SIG would like to see / Example team or unit based structure – there is not a general structure and we need a FOLIO wide solution / Challenge to move forward: integrations and FOLIO wide solutions

    • Jack (chat): I suppose the fully external integrations are also a challenge - not a contentious one, but since we don't have direct control over the structure of GOKB or the EBSCO KB it means we do not always see what we might want

    • Sara: Lacking stress testing capacity of the different apps around performance and usability in terms of capacity not accessibility / volume of e.g. AGL or POL could not being anticipated / hitting the threshold of AGL the Agreement was unusable 

    • Owen (chat): I think this is a really good point Sara. We need better approach to having good set of test data that can help with realistic development and testing

    • Owen: to have more realistic test data in the environments, snapshot and bugfest environment, volume that is realistic

    • Felix (chat): Can we have sample data added to folio-snapshot, like other apps have?

    • Zorian (chat): I would be interested in helping out with that, if needed!

    • Kristin: Chicago offered data for Bugfest, but not ERM – institution could provide data, so that we are in a more realistic situations

    • Owen (chat): And just to clarify on the Agreement Lines situation - we are now in the situation where the Agreement edit is the last remaining screen where the large number of ALs causes problems. This is something that needs work still - I think it would be good to make this is a topic for an upcoming SIG
  • 7. If you work on areas of development, do you feel like there are areas of development not resourced at all or significantly under-resourced?

    • Felix: had more delevopment resources in the past and lost some – implementation page – there are a lot of things in backlog maybe due to lacking of development resources, but maybe there are other reasons as well

  • 8. What has been successful with the SIG? What things contributed to that success?

    • Sara: great conveners, highly motivated participants, Felix for writing up bugs, early implementer page, outstanding PO

    • Julie (chat): The development updates at the beginning of each meeting are very helpful!  And the preview of what is coming in each release.

    • Owen: highly motived participants, active participants willing and able to speak up, Participants bringing issues and solutions
    • Owen: Funding of GBV making it happen – this is essential - and developers from other institutions who contribute 

    • Sara (chat): Homework! YES! Thank you to GBV!!

    • Kristin (chat): Just want to second the in-advance homework and opportunity to provide feedback and understand direction of meetings.

  • 9. What could the Product Council do to help the SIG?

    • Jack: not necessarily the PC that can help / when we encounter issues with e.g. integrations / over the years brought topics to the App interaction group – encouraging more comprehensive conversations across apps e.g. search / discussions before bigger things are added or are coded 

  • 10. Do you feel like the Roadmap accurately represents the work of your SIG (both desired and already accounted for)?

    • Owen: we don’t have a forward enough plan that we following a roadmap – currently discussing what we need to look at in orchid / Strength: very reactive, able to make decisions in reaction of what people telling us at the time / Roadmap is high level and vague

    • Martina S:  There are the roadmap group and prioritization group – discussions and work in progress for new processes

  • 11. How can we improve our communications with the SIG? Does the current monthly reporting work? Would having a dedicated PC meeting for your SIG be helpful?

    • Martina S.: Conveners are reporting on what the SIG is doing and discussing once a month

    • Jack (chat): I think what's happening now works fine

    • Sara: we are covered - relying on people involved – SIG conveners

    • Owen (chat): We currently have 4 members of the PC, including a co-chair attending the SIG meeting pretty much every meeting

  • Please add to the document if you have additions or comments homework document

Chat

Von Felix Hemme (ZBW) an alle 02:05 PM
Owen, has the extension of GOKb metadata made it into Nolana, maybe with exception to package identifiers.
Wonderful news, thank you for making this happen!
Von Jack Mulvaney an alle 02:12 PM
Same here actually
Von Owen Stephens an alle 02:15 PM
Felix - just FYI we also have included the updating of URLs for a title on a platform (the PTI url). But we only do this if the source is marked as ‘trusted source for title data’ (because multiple sources can update the same PTI )
Von Sara Colglazier (MHC/5C) an alle 02:17 PM
& THANK YOU very much to you, Owen!
Stress on: integration(s)
Von Jack Mulvaney an alle 02:19 PM
So we have more direct responsibility over the apps that you and the code team have responsibility for developing, and indirect responsibility over a larger amount of FOLIO due to the integrations
Von Zorian Sasyk (he/him) an alle 02:21 PM
Functionally in libraries, ERM includes the entire of lifecycle of eresources, including their acquisition, speaking to Sara's point
Von Jack Mulvaney an alle 02:22 PM
We've come upon a microcosm of the profession :)
Von Zorian Sasyk (he/him) an alle 02:22 PM
@jack small but mighty!
HERE HERE SARA
Von Owen Stephens an alle 02:27 PM
And that had to be fought for - so thank you for all that added their voices to that in this community
Von Sara Colglazier (MHC/5C) an alle 02:28 PM
Thank goodness for Owen! And the Martinas!!
Von Julie Brannon (she/her) an alle 02:29 PM
+1 to Jack - very well supported in the ERM SIG by our PO and dev team!
Yes - +1 to Sara about the consistent, diligent leadership of our conveners too
Von Owen Stephens an alle 02:30 PM
Completely agree with this - the SIG Convener role is not talked about as much as the PO role but it's really important
Von Jack Mulvaney an alle 02:33 PM
I suppose the fully external integrations are also a challenge - not a contentious one, but since we don't have direct control over the structure of GOKB or the EBSCO KB it means we do not always see what we might want
Von Owen Stephens an alle 02:35 PM
Yes absolutely Jack
Von Zorian Sasyk (he/him) an alle 02:38 PM
There is a limit to number of Agreements?
Oh gotcha agreement lines
Von Owen Stephens an alle 02:39 PM
I think this is a really good point Sara. We need better approach to having good set of test data that can help with realistic development and testing
Von Felix Hemme (ZBW) an alle 02:39 PM
Can we have sample data added to folio-snapshot, like other apps have?
Von Zorian Sasyk (he/him) an alle 02:40 PM
I would be interested in helping out with that, if needed!
Von Sara Colglazier (MHC/5C) an alle 02:40 PM
stress/capacity test re: volume of things and calls
Von Sara Colglazier (MHC/5C) an alle 02:43 PM
stress/capacity test re: 
Martina, may I add performance to stress/capacity test
Von Owen Stephens an alle 02:44 PM
And just to clarify on the Agreement Lines situation - we are now in the situation where the Agreement edit is the last remaining screen where the large number of ALs causes problems. This is something that needs work still - I think it would be good to make this is a topic for an upcoming SIG
Von Felix Hemme (ZBW) an alle 02:47 PM
Outstanding PO!
Von Owen Stephens an alle 02:47 PM
🙂
Von Julie Brannon (she/her) an alle 02:47 PM
The development updates at the beginning of each meeting are very helpful!  And the preview of what is coming in each release.
Von Sara Colglazier (MHC/5C) an alle 02:50 PM
Homework!
YES! Thank you to GBV!!
Von Kristin Martin an alle 02:50 PM
Just want to second the in-advance homework and opportunity to provide feedback and understand direction of meetings.
Von Jack Mulvaney an alle 02:50 PM
+1
Von Sara Colglazier (MHC/5C) an alle 02:50 PM
+1 to Kristin's more detailed homework statement
Von Owen Stephens an alle 02:51 PM
And the homework was something that SIG participants actually initiated - so again down to high quality participation and community voices
Von Jack Mulvaney an alle 02:57 PM
I think what's happening now works fine
I've never felt like we weren't getting important info or that issues we raised weren't being shared
Von Owen Stephens an alle 02:59 PM
We currently have 4 members of the PC, including a co-chair attending the SIG meeting pretty much every meeting
Von Carol Sterenberg an alle 03:00 PM
Thank you!
Von Sara Colglazier (MHC/5C) an alle 03:00 PM
Thankyou!
Von Owen Stephens an alle 03:00 PM
It's such a pleasure & privilege working with this group !
Von Zorian Sasyk (he/him) an alle 03:00 PM
Thank you everyone!

Attendees list