Announcements

Martina Schildt

Follow up to the community priorities dashboard pilot:

• SIGs should review their priorities and make any updates by 9/1.

• PC would like to invite SIGs to come talk about their priorities during one of their regular meetings.

  • 10 minute informal discussion and opportunity for PC members to ask questions.

• In early September, the PC will create its own priority list based on information gathered in these conversations.

• The PC priority list will be published on the community priorities dashboard alongside SIG priorities.

• The community priority dashboard will be published to the community for feedback before WOLFCon.

• After WOLFCON PC will establish a regular cadence for updating and publishing the dashboard.

Charlotte Whitt is our new liaision between the ERM SIG and the Product Council starting immediately.

10min

Development progress update

Owen Stephens

Sprint

• introduction of a GOKB search within agreements

  • there is a new GOKB serach tab in addition to Agreement search and Local KB search

  • it is possible to filter for “type”

  • search options are the ones that ERM SIG agreed on

  • waiting for QA

• implementation of ACQ units

  • backend work is done

  • Agreements AI can use acq units

  • made slight changes where needed, but trying to stay as similar as possible

• Chat

  • Felix Hemme 14:16
    Quick question: With the implementation in Agreements, do we have to know the name of the unit to find it, or will a list display if you click inside the field?

    Gill Osguthorpe 14:22
    By default you will see options before typing. There's an example in the OA app.

• How many acq units do libraries need?

  • Felix Hemme I don't think that we will have more than 10 at ZBW.

    Heiko Schorde >20

• Sara: if a user is not allowed to perform an action because the user is not member of the acq unit > user needs clear and understandable error message

  • Owen: in this case the user should not see the edit action

• acq units will be assigned at Agreements level and will be displayed on AGL level as well

• users can apply every order that they are allowed to view; there is no logc that prevents users from linking to an order from another acq unit

Chat:

Felix Hemme 14:36
Will Orders and Agreements share the same units?

Owen: yes, no additional set up needed; but in future, ERM will not be limited to acq units (not first version)

45min

Implementers' topics:

Adding tags for License Amendments

Irina Trapido (Stanford) - can never attend due to time zone

Our Licensing Librarian would like to track metadata for each document signed (e.g., signatory, fiscal year, type of purchase, etc.). He wants to record this information at both the license and the license amendment levels. Tags would be ideal for this purpose, but they are currently only available at the license level. Would it be possible to make tags available at the amendment level as well, similarly to how they are available at the Order and Order Line levels, the Agreement and Agreement Line levels?

ERM SIG: no objections, no comments

Owen will create a Jira ticket https://folio-org.atlassian.net/browse/UXPROD-5537

Implementers' topics:

Add additional options to the “Is perpetual” field

@Priyanka Thanikachalam (EBSCO)

In Quesnelia there are only two options for field entry for the "Is perpetual" field in FOLIO's Agreements app. MWSU would like to add additional options called "Yes - with fee" and "Yes - with continued subscription to publisher's product" to the “Is perpetual” filter

• similar discussion Agenda Feb 17 2021

  • ticket that has been created based on that discussion: https://folio-org.atlassian.net/browse/UXPROD-5326

Chat

Felix Hemme 14:51
Related to the PCA field: Because we just have yes/no at the moment we are using "yes" in cases where it really is <mixed> in addition with a comment in the agreement description that it has to be checked on a case-by-case basis if an eresource is removed from a package.

Options

• make perpetual access a tenant configurable list

• use suppl. properties

• list of: yes, no, mixed, conditional, none > and keep it system defined

  • single or multi-select?

Sara would rather have a solution that can be quickly developed and used than having a more sophisticated solution

Additional requirement: have it on AGL level

We will come back to this topic. Owen and Gill will work on designs that can be discussed.

Postponed

Implementers' topics:

Filter for agreements with no Description

Vidhya Ramachandran on behalf of Arkansas Colleges of Health Education

Implementers' topics:

Move or copy widgets

@Felix Hemme

Add the ability to move a widget from one dashboard to another.

Use case:

1. As a librarian I want to move an existing widget from my personal to a shared dashboard.

Alternative: Instead of moving a widget add an option to create a new widget and copy the configuration from an existing one.