10min

Development progress update

Owen Stephens

• Trillium release data has been pushed back into 2026. The precise date has not been announced yet. TC is still discussing what this means for the Ramsons support period. This allows the developers to spend more time on working on features to include into Trillium.

• GOKB search integration work is not yet available on folio-snapshots due to some technical issues, but it will be added once these have been solved.

• Main work item to highlight is the ACQ units implementation. It is already functional on folio-snapshot. Owen does a live demo of this new functionality.

Implementers' topics:

Filter for agreements with no Description

Vidhya Ramachandran on behalf of Arkansas Colleges of Health Education

Discussed:

• The requirement is clear, understood and makes sense.

• TODO: Owen will create a Jira story for this requirement.

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.

Discussed:

• Add the ability to copy a widget.

• In the widget edit screen, add a dropdown to select the parent dashboard.

• That allows us to move a widget from one dashboard to another in the event of duplication and potentially even in normal edit operations.

• TODO’s:

  • Owen will investigate if existing widgets can be moved to another parent dashboard (=change the owner property of a widget).

  • Owen will create a Jira story for this requirement.

Implementers' topics:

Ability to delete multiple agreement lines at once

@Martina Schildt for GBV

It is possible to add multiple agreement lines to an agreement at the same time. However, it is not possible to delete multiple agreement lines at the same time.

There are cases where many agreement lines are attached to an agreement and either many lines need to be removed or the entire agreement needs to be deleted. However, agreements cannot be deleted as long as agreement lines are still attached. Therefore, all lines must be removed individually.

It would be practical to have the option of deleting multiple agreement lines at the same time.

Discussed:

• Instead of adding the ability to delete >1 AGRLine at once, we could also remove the constraints that prevent deleting agreements with AGRLines (and licenses, related agreements). Need a separate confirmation step for security reasons.

• Or add the ability to select multiple AGRLines in the Agreement lines search and an “Delete” action from the Action menu. If there are still linked licenses or related agreements, these had to be removed from the agreement before it can be finally deleted. But this solution would allow libraries to select multiple AGRLines from multiple agreements and delete them. This has pros and cons.

  • Would this approach require a separate permission?

• From the discussion and chat, both scenarios are something people want.

• What should we start with? No preferences from the group.

Postponed

45min

Continue

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

• Notes from last meeting: 2025-08-13 ERM SIG meetingPreview