2024-10-16 ERM SIG meeting

Owned by Martina Schildt
Last updated: Oct 16, 2024
6 min read

 Meeting information

Date: Oct 16, 2024

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

Meeting URL: Join our Cloud HD Video Meeting - password needed: please see link

Housekeeping

 Homework

  • No homework

 Discussion topics

  1. Development progress update

  2. Update and discussion of WOLCon ERM Workflow sessions

  3. New implementers topics (if time)

Minutes

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes



Development progress update

@Owen Stephens

  • EBSCO is working on a new platform approach that is called Eureka

    • one key thing: changes to how authentication works

    • modules need to make changes, applied to ERM modules as well

    • work needed doing within a specific timescale -

    • is what the ERM team worked on last sprint - is done now

  • finished work on being able to attach documents (file, location, URL) to agreement lines

    • URL could be a FOLIO URL, e.g. a pointer to an Inventory record or a list of results

  • Working on a document search to be included in Ramsons (is in code review at the moment)

 

Update and discussion of WOLCon ERM Workflow sessions

@Owen Stephens

  • Owen gives a brief report of the workflow sessions at WOLFcon

  • sessions were held together with Jeremy Huff (PO for Workflow app)

  • groups at WOLFcon worked on ERM workflow examples that have been gathered with ERM SIG and Agreements Local KB subgroup

  • groups were to mock-up a workflow for the requirements listed for the different use cases

  • out of the results Owen and Jeremy produced a structured breakdown

  • Jeremy converted the workflow to an FWZ and imported it into the Workflow app

  • findings: each institution would have a different approach

  • situation is similar to the reporting situation: libraries that have a reporting solution are in a different position than those without

  • there is a risk that we end up in a similar situation with workflows

    • availability within institution as well as skills

  • we need to differentiate between what can be done in Workflow app versus what should be developed for ERM app

  • important: record what is needed in ERM apps

  • To Do: come back to this in a future meeting

  • Owen to present on workflows and extracted requirements for ERM apps

  • Example:

    • Have something similar to ‘Correspondence’ from Open Access app in ERM apps

  • Pcik & Choose use case has been discussde quite often - maybe we need an ERM solution here

  • maybe automation could be a solution here, e.g. by uploading a list of titles to create new agreements lines

    • Zorian in chat: +1 for uploading to create new records!

Questions or feedback

  • Felix Hemme in chat: Shall we still add workflow examples to our document Collecting ERM workflow examples for WolfCon 2024  ?

    • Yes, please add further workflow examples where needed

  • Susanne Gill in chat: Been there. It was fun discussing the workflow with the small-group and getting to know how others do it. (and seeing my writing again :-))

  • Tanja Blixt in chat: Looking forwrad to the recordings, sadly I wasn't a wolfcon but it all sounds really interesting. We're still at Orchid so we have a few updates to go, but we're really looking foward to Workflows or any inbuilt Agreement solution.

 

New implementers topics (if time)

  1. Re-think the order of the filters in Agreements and Licenses (@Molly Driscoll )

 

  • in Quesnelia release there were new filters that were very useful

  • the new ones are at the end of the list

  • how is decided where the filters go?

    • Owen in chat: They aren’t just added in order - I do give some thought to the order when we add new filters 🙂

    • But we don’t usually discuss the detail in this group

    • And we can definitely discuss and re-think!

    • Molly in chat: Thank you! I appreciate the info 😊

  • do we want to re-think the order or do we want to wait dor user preferences?

  • Felix in chat: I think it really comes down to customization of the app's UI. We don't use internal contacts and therefore would be happy to not display the filter for example.

  • Felix in chat: Also a library could benefit from deciding what filters should be expanded by default or what filters should be applied by default when opening the app.

  • Felix in chat: This is broader than ERM

  • Molly in chat: Agreed, Felix! I had a feeling this would be broader, but wanted to start here.

  • Felix in chat: Configuration on the tenant level seems sensible (compared to the user level what can be more complicated I assume).

Owen:

  • filters are getting more sophisticated

Feedback Molly on wishes:

  • date filters and document filters are important for daily work

To Do:

  1. Do an exercise of ranking the filters of each module - could be a regular thing

    1. eHoldings will be excluded (Zorian in chat: eHoldings is a bit more complicated since its showing filters from HLM via API :p)

  2. Check options with development team

Chat

14:01:17 Von Martina Schildt an Alle:
2024-10-16 ERM SIG meeting
14:30:20 Von Felix Hemme an Alle:
Shall we still add workflow examples to our document Collecting ERM workflow examples for WolfCon 2024 ?
14:30:42 Von Susanne Gill (BVB) an Alle:
Been there. It was fun discussing the workflow with the small-group and getting to know how others do it. (and seeing my writing again :-))
14:31:15 Von Tanja Blixt (Linköping University) an Alle:
Looking forwrad to the recordings, sadly I wasn't a wolfcon but it all sounds really interesting. We're still at Orchid so we have a few updates to go, but we're really looking foward to Workflows or any inbuilt Agreement solution.
14:33:22 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
ProQuest or ebsco
14:33:30 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
millions of titles
14:36:56 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
+1 for uploading to create new records!
14:46:18 Von Owen Stephens an Alle:
They aren’t just added in order - I do give some thought to the order when we add new filters 🙂
14:46:48 Von Molly Driscoll an Alle:
Reacted to "They aren’t just add..." with 👍
14:46:50 Von Owen Stephens an Alle:
But we don’t usually discuss the detail in this group
14:46:56 Von Molly Driscoll an Alle:
Reacted to "But we don’t usually..." with 👍
14:47:05 Von Owen Stephens an Alle:
And we can definitely discuss and re-think!
14:47:27 Von Molly Driscoll an Alle:
Thank you! I appreciate the info 😊
14:47:43 Von Felix Hemme an Alle:
I think it really comes down to customization of the app's UI. We don't use internal contacts and therefore would be happy to not display the filter for example.
14:48:26 Von Heiko Schorde an Alle:
Reacted to "I think it really co..." with 👍
14:48:27 Von Felix Hemme an Alle:
Also a library could benefit from deciding what filters should be expanded by default or what filters should be applied by default when opening the app.
14:48:39 Von Tanja Blixt (Linköping University) an Alle:
Reacted to "Also a library could..." with 👍
14:48:46 Von Jessica Harris an Alle:
Reacted to "Also a library could..." with 👍
14:48:52 Von Molly Driscoll an Alle:
Reacted to "I think it really co..." with 👍
14:48:55 Von Felix Hemme an Alle:
This is broader than ERM.
14:48:59 Von Molly Driscoll an Alle:
Reacted to "Also a library could..." with 👍
14:49:00 Von Owen Stephens an Alle:
Reacted to "Also a library could..." with 👍
14:49:03 Von Owen Stephens an Alle:
Reacted to "I think it really co..." with 👍
14:49:12 Von Susanne Gill (BVB) an Alle:
Reacted to "Also a library could..." with 👍
14:49:15 Von Susanne Gill (BVB) an Alle:
Reacted to "I think it really co..." with 👍
14:49:22 Von Molly Driscoll an Alle:
Agreed, Felix! I had a feeling this would be broader, but wanted to start here.
14:49:28 Von Felix Hemme an Alle:
Reacted to "Agreed, Felix! I had..." with 💯
14:50:00 Von Felix Hemme an Alle:
Has this topic been discussed in the AI SIG as well? I would bet on it ;-)
14:55:03 Von Molly Driscoll an Alle:
Absolutely! There's the rub 😁
14:55:37 Von Felix Hemme an Alle:
Agreements and Licenses are already ahead of other apps with the 'exclution' of accordions w/o any data in the display of records. :-)
14:55:46 Von Martina Schildt an Alle:
Reacted to "Agreements and Licen..." with 💯
14:55:48 Von Molly Driscoll an Alle:
Reacted to "Agreements and Licen..." with 💯
14:56:32 Von Philip Adams an Alle:
Customisation might be the way forward. We do use Internal Contacts, for example.
14:56:55 Von Molly Driscoll an Alle:
Thanks so much for the discussion! I can share this info with my interested colleague :)
14:57:02 Von Martina Schildt an Alle:
Reacted to "Thanks so much for t..." with 👍
14:57:44 Von Felix Hemme an Alle:
Configuration on the tenant level seems sensible (compared to the user level what can be more complicated I assume).
14:58:53 Von Felix Hemme an Alle:
Yes, but this is not persistent, right?
15:00:33 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
Reacted to "Agreements and Licen..." with 💯
15:01:40 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
eHoldings is a bit more complicated since its showing filters from HLM via API :p
15:02:10 Von Zorian Sasyk | EBSCO FOLIO Implementation an Alle:
not that im against it per se
15:02:16 Von Owen Stephens an Alle:
Reacted to "not that im against ..." with 👍

 Action items

@Owen Stephens extract ERM requirements from ERM workflow examples and present options to ERM SIG
@Owen Stephens Create a survey to rank filters across ERM apps and discuss in a future meeting

 Decisions