5min

Announcements

@Felix Hemme

eUsage

Stefan will write a summary of the development status of eUsage in the wiki next week and share it in the ERM SIG channel. As a first information:

• Release notes Ramsons

• Plans for Sunflower

• Requirements for improved error handling of CoP and HTTP codes: We would like to work with the community together this year on improved error handling. The proposal is to form a sub-working group to deal with the topic and go through the individual codes. There should not be regular meetings, but only individual meetings to discuss specific topics.

10min

Development progress update

@Owen Stephens

• Sprint 210 started this Monday.

• There would have been feature freeze for Sunflower this Friday, but this had been extended for two more sprints. This is because the Ramsons release has not been completed. New release date for Sunflower is April 28th, 2025. This additional two sprints will help the ERM development team to finish work on Sunflower features that are still in progress.

ERM development: what’s coming with Ramsons?

@Owen Stephens

• Dashboard ERM Ramsons (w/o Bugs): https://folio-org.atlassian.net/jira/dashboards/10483

• The ERM apps as they are are considered stable and reliable. That is one reason why we don’t see changes at the same pace as during the last years. Another reason is the work on the local knowledgebase (KB) and the mechanisms that populates the KB from an external source (GOKB). This work is not fully covered by the FOLIO Jira.

• New functionality in Ramsons:

  • Main or key column in Agreements that can’t no longer be hidden.

  • Documents at the Agreement Line level. Owen will check if the documents sort by name (or something else) or just sort “random”, e.g. by the order they are returned from the database.

ERM development: planned for Sunflower release

@Owen Stephens

• Dashboard ERM Sunflower features: https://folio-org.atlassian.net/jira/dashboards/10485

• Three features for Sunflower have been worked on.

  • Enhance S3 file storage configuration to make keys write only. Some of the configuration will be moved to ENV_VAR that are only visible to the system administrator. This is not the ideal solution but the best that could be done for now. This won’t effect the ERM user experience.

  • ERM basket enhancements to use the “search agreements” plugin.

  • Support selective synchronization into the local KB. A new boolean property synchronise is added on package entity in mod-agreements. This will allow to decide for what packages the package titles will be imported. By default, only package metadata will be imported, but not the complete package titles.

If time allows: Implementers' topic

@Owen Stephens

Other topics

Question from @Sara Colglazier: Does uploading of documents like invoices, contracts etc. into FOLIO is likely to affect performance.

• In the app settings > File storage the user can set S3 or LOB (default). If LOB is selected, the files are stored inside of FOLIO’s database. There will be a difference in performance whether storage is selected. Owen says that S3 might be a better option, because it can be more performent compared to LOB when accessing the documents.

• When working with the ERM apps, an externally stored document is not retrieved when looking or working on the record itself. It is only retrieved the moment the user requests it by clicking on the link.

• Owen, K-Int and GBV will discuss the potential implementation of Elasticsearch into Agreements later this year.