10min

Development progress update

Owen Stephens

• Sprint 220 started this Monday.

• 2 main focus areas for this sprint are related to the main features for Trillium:

  • Add the ability to delete content of a package from the local KB

    • There is extensive documentation on GitHub in the mod-agreements repository.

    • markForDelete is a test option that tells what would be deleted if the actual delete is performed.

    • For Trillium it will support the deletion of all resources in a package and will then follow the path and delete the PTI, TI's, TI’s and the work, if possible. Deletion is done via a job, not instantaneously.

    • The package header will remain in the local KB.

  • Integrate GOKB search into the local KB

    • Will support GOKB at the beginning, but is designed to be service agnostic and can accept a config file.

    • Stories are written and development is about to start.

• Concept work has started to add the ability to protect who can edit records in Agreements and Licenses. Acquisition units can then be added to those 2 apps (=needs mod-orders to work). In the future K-Int is going to enhance the functionality even further.

10min

ERM prioritization | Community feedback

Owen Stephens, Zorian Sasyk (regrets), Stefan Dombek

• Is there any feedback on the ERM prioritization process?

• The current ERM prioritization list does represent GBV’s priorities, not the community ones.

• The ERM PO’s are working on creating such a community list.

• Owen has created Jira Dashboard “ERM SIG Topics”. SME’s should vote on the features from this list.

• Stefan points out the eUsage prioritization can start in August at the earliest, because they have to collect requirements first.

We did not have time to discuss any implementers topics (see below) this time. ↘️

40min

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?

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

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.

Postponed

Implementers' topics:

Customized URLs should be shown in the UI

@Sabrina Bayer for TP-ERM (bavarian libraries)

When using the URL customization, the changed URL is only shown in the export file. It would be very useful for our colleagues, if the changed URL is also shown on the AGL and on the  e-Resource record. This would help our cataloguers finding the e-resource on the provider platform quickly.