Page Comparison

Housekeeping

Jana Freytag

• Information on “Agreements Local KB subgroup”: There will be no meeting on 07 Aug 2024

Development progress update

Owen Stephens

Work in progress:

• Allow number fields to take negative and "e" characters as input.

• Ensure date fields are validated when they are optional as well as when mandatory.

• Clearing the agreement line form when "Save and create another" is used.

• Ensure that the S3 secret key is not visible in Settings: Agreements: App settings: File storage.

Upcoming:

• API documentation

Complete

• eISSN and ISSN etc clean up. Have implemented this for all data coming into the Knowledgebase. Will reduce the amount of inconsistent and erroneous data.

Duplicating agreements and licenses

Owen Stephens

When using the duplicate feature, currently a copy is immediately created and saved before displaying in edit mode. The proposed change is to add an interim step, prompting for the Name, Status and Start date before the agreement is created.

Discussion:

• The duplicate option isn't tied into a workflow and has been developed to support multiple use scenarios.

  • An example of a workflow which might be supported: creating a successor agreement.

• Could the name be auto-completed in the new form?

• Could the start date be auto completed based on the end of the agreement being duplicated?

Are there other fields which should be copied across when duplicating an agreement?

• Alternative name will be added.

• Period note was discussed and decision made to not copy it across.

• A new (possibly repeatable) note field might be needed. In a future session, we will assess how the current notes helper app is being used and whether alternative support for notes is needed.

There will be a Wolfcon session to discuss workflow requirements for ERM and look at the proposed FOLIO workflow app to assess whether it will support the needs of users.

• Owen will circulate a document for comment and ideas. This may include some limited info about the workflow tool but Owen is keen to keep the discussion open and unrestricted by the functionality of the proposed tool.