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/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 Dec 1st 2021

Convener: Martina S.

Notetaker: Martina T.

Housekeeping

• All: Please edit the attendees list below and indicate when you are there!
• Next ERM meeting:  Dec 15th
  
• 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
• Support SIG - Request for representatives from other SIGs - meetings Mondays at 10:00 Eastern U.S. time

Agenda items:

1. Development progress -  ERM Sprint 128
2. Open Access properties of Agreements
   1. Please read this linked document about Open Access properties of Agreements and answer the questions

Minutes

• Development progress -  ERM Sprint 128

  • Slower progress due to less resources this sprint

  • Working through the software testing changes – new framework for testing in FOLIO 

  • bugfixing, small story development and small UI improvements

• Open Access properties of Agreements
•  A new application to record requests to publish - Institutions to record and manage publication requests 

• Question about whether library is involved or not – sometimes management of funds or requests for publication in libraries - if payment is to be made managing the process of payment

• Example author at your institution is publishing an article open access and there is a fee APC (article processing charge) - request paid from a fund or institution has an agreement with the publisher

• Examples: Read and publish – access to a set of content and authors from your institution can publish in those journals or subsets of journals – lots of variation

• Examples: 10 article APC included and certain access to journal or discount on APC or price cap 

• Might be more properties to agreements and it might cover other scenarios as well

• Supplementary properties – one option to record, but there are limitations
• Each Open Access publication has the potential of being listed as part of an agreement 
  • Q1: Do you currently have agreements that include "open access publishing" components? If so, what are the key aspects of these that you would want to capture when recording an agreement in Folio?

    • LAS:eR came up in the OA SIG – there is a list of terms from LAS:eR

    • type of agreements: good example of situation whether the type of agreements is a list we can agree on or whether really categorization is useful at institution level

    • Sara (chat): And it is very dynamic--esp right now--so maybe better for it to be more flexible to change as we go

    • Jessica (chat): I agree. Supp. properties would probably work well for this.

    • still see changes how open access works 

    • Agreement type could you see the need in a more general sense or specific to Open Access?

    • Jack (chat): I would also think "type" could be used to represent a perpetual/post-cancellation access agreement or a non-OA membership as opposed to direct subscription

    • We have a license type: consortial, national … - Duke is using to identify which library

    • How people do see agreements categorized and what meaning it is attached to it   
    • Jack: We have agreements for Open Access – paying for being open/donation – recording information in a note - Do you include the list of resources?  link to the eHolding 

    • Agreement and agreement lines are used differently in institutions

    • You may want to apply multiple values to characterized the agreement

    • Developing: a new open access app – functionality is limited at the moment on snapshot – recording request to publish articles  

    • OA for recording the requests to publish and may link to payments and agreements

    • Agreement might say certain number of tokens for APCs as part of your agreement – each time for a publication you use a token (already discussed in OA SIG)

    • Jessica: read and publish agreement – number of authors that publish in resource per year and number of open access publications - for evaluation purposes

    • New Open Access app would be the place to record the publications

    • Who is allowed to publish – discussed in OA

    • From Open Access App Agreements and Invoices could be linked  

    • Complex workflow Open Access: e.g. managing authors questions what options they have, e.g. author already submitted it to the publisher, e.g. the publisher: can we bill you for this submission of your author?

    • High reporting requirements

    • Open Access App name might be misleading - Open access publication requests
  • Q2: Are there other types of agreement which come with their own unique set of properties? If so, what are they? If possible give some examples of the types of property they have.
    • Are there other scenarios / functionality which are helpful?

    • Sara: when things are not at the same level – journal with some open access percentage - issues or title is not open access, but this article – how would you differentiate?

  • Q3: Outside the 'read and publish' scenario listed above, can you think of other examples of situations where agreements might have two or more lists of resources associated with them that had different properties? If so, can you give examples?

    • Jessica: journal custom package – some are subscribed to open some aren’t - one order for everything 

  • If you are interested please have a look at the recordings or minutes from the Open Access SIG https://folio-org.atlassian.net/wiki/display/OA/ and there is a slack channel

Chat

Von Martina Schildt an alle 02:02 PM
2021-12-01 - ERM meeting
Von Felix Hemme (ZBW) an alle 02:16 PM
Challenge and opportunity!
Von Sara Colglazier (MHC/5C) an alle 02:21 PM
And it is very dynamic--esp right now--so maybe better for it to be more flexible to change as we go
Von Jessica Harris an alle 02:21 PM
I agree. Supp. properties would probably work well for this.
Von Jack Mulvaney an alle 02:23 PM
I would also think "type" could be used to represent a perpetual/post-cancellation access agreement or a non-OA membership as opposed to direct subscription
Von Jessica Harris an alle 02:24 PM
That's true or multi-year agreements (though those can change)
Von Jack Mulvaney an alle 02:25 PM
We (UMass not necessarily the rest of the Five Colleges) record some tools like EZProxy or Catalogers Desktop when they're paid out of our acquisitions fund rather than operating funds - there's no content but I need to be able to record things about them beyond a basic acq. note so we have agreements
Von Sara Colglazier (MHC/5C) an alle 02:26 PM
also there is then the problem that it is at the AG level and not AGL level, so ... conseuquences
I would have said the same that Jack is saying a month ago--suddenly all has changing
I remember what I forgot: when we were seeing demos about how institutions were organizing their AGs, we could see such a variety in approach that it already runs counter to all of us being able to Type the same
Von Jessica Harris an alle 02:37 PM
Thank you for the clarification, that helps with how I'm thinking about this.
Von Sara Colglazier (MHC/5C) an alle 02:49 PM
I am not familiar enough with all this, but ... I could imagine article level vs title level
Von Jessica Harris an alle 02:55 PM
MIT Direct to Open I think
Von Emma Raub an alle 02:55 PM
Yes, Direct to Open.
Von Felix Hemme (ZBW) an alle 02:55 PM
@Sara we have a similar usecase with a consortia agreement.
You get one year "as a gift" if you joined in 2020
It's horror to manage this kind of agreements from the content side.

Attendees list