Skip to end of banner
Go to start of banner

2024-07-24 ERM SIG meeting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

\uD83D\uDDD3 Meeting information

Date:

Meeting Time:  8am ET | 1pm UK | 2pm CET

Meeting URL: https://openlibraryfoundation.zoom.us/j/88673361033 - password needed: please see link

🏘️ Housekeeping

\uD83E\uDD45 Homework

\uD83D\uDDE3 Discussion topics

  1. Development progress update

  2. Continue implementers topic: When duplicating an agreement/ or a license: additional fields should be duplicated

    1. Please review the document at https://docs.google.com/document/d/1QR-7Fd3nubZLy5LXhUW8nEoIk-6zgpf7PVBVIIqSGfE/edit?usp=sharing and answer the questions

📔 Minutes

Time

Item

Presenter

Notes

Housekeeping

Jana Freytag

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


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.

✍️ Chat

Felix Hemme 14:09
Just wondering: When you refactor the number validation, do you also modify the values that are allowed for certain fields, e.g. "Number of concurrent users allowed" to no longer allow negative values?
Okay, then this seems like a Stripes issue

"issue"

Felix Hemme 14:25
We work the same as Sara here. Please keep duplicating the name with prepending Copy of. We then remove this string easily.

(thumbs up) (Lars-Håkan Herbertsson )

Felix Hemme 14:26
We just add the year at the end of the name, e.g. Agreement 2022, Agreement 2023 etc.

Sara Colglazier 14:29
I would be fine with that: no COpy of, but I cannot save until I change the name however slightly etc

Felix Hemme 14:53
We don't use the notes helper app.

Lars-Håkan Herbertsson, Chalmers uni 14:56
Not even sure what it is (notes helper app)

Felix Hemme 14:57
@Lars-Håkan Herbertsson, Chalmers uni Here the documentation about the helper app: https://docs.folio.org/docs/settings/settings_notes/settings_notes/

Supported apps per this list:

  • Agreements

  • eHoldings

  • eUsage

  • Licenses

  • Organizations

  • Users

 Action items

  •  

⤴ Decisions

  • No labels