Development progress update

@Owen Stephens

• The team did the Ramsons release preparation and released ERM modules.

• Bugfest Ramsons has started this week. If you have spare time, then please consider to take on some test cases in Testrail.

  • Eureka Bugfest environment is covered by a team contracted by EBSCO. Mayor changes to app permissions have to be tested, including the ERM apps.

  • The community shall focus on the non-Eureka environment. As far as ERM apps are concerned, the community can test the non-ECS environment as used to in previous Bugfest test runs.

• Main new feature for Ramsons besides the enhanced data harvesting: When adding an agreement line to an agreement, the user can now add documents that supplement the agreement line metadata, similar to documents in agreements. It can have any of a physical location, a url, or a file uploaded. Agreement line search has been updated as well so that a user can search be those documents. To only search for documents in a specific agreement the user has to filter for the agreement first and then apply the document filter in a second step.

ERM workflow requirements

@Owen Stephens

• Slidedeck

• The question comes up of whether an app is part of the “official” FOLIO (folio-complete/Flower release) or not. We can verify that the Lists app is part of folio-complete and has been approved by TC.

• Could the Dashboard app interact with the Lists app? Owen shares that there is already a Jira feature for this integration: https://folio-org.atlassian.net/browse/UXPROD-4808

• Sara points out that reporting on our data is a crutial point and must-have for a library management system.

• It is currently unclear who is responsible with programming the workflows that can be executed within the Workflow app: Libraries, system providers or someone else?

• Owen will share the rest of his slides via Slack and we’ll continue there and maybe also in the next SIG meeting.