2024-04-08 Meeting notes: Agreements + Inventory interaction

Date

08 Apr 2024 

Housekeeping

• Convener and notes: Martina Schildt 

• Next meeting: 17 Apr 2024 

Discussion items

1. Updates

   1. WOLFcon session

   2. PO meeting 

2. AGR and INV interactions

   1. decide on next steps

3. Topics for next meetings

Minutes

WOLFcon updates

• 1 sessions submitted for WOLFcon on app interactions

• Khalilah proposed that we join a PO meeting rather sooner than later instead of having a WOLFcon session

  • Khalilah will propose some good slots

  • preparation can happen then

AGR and INV interactions

• option 1: there is an advantage in solving immediate requirements directly in ERM

  • e.g. being able to add a URL to a decicated field

  • Owen Stephens to write up story

• • when this can be addressed is open

  • Sara votes against option, rather than needing to add URLs to many AGLs link from Inv side

  • Owen: would like to talk with ERM SIG about this

• option 2: more specific: we should have a way of linking to specific titles, instances, holdings, items

  • no huge technical barriers in storing

  • but it would be hard to keep in sync

  • this would be a little less general

  • parallel to what we do with orders already

• option 3: registry: allow definition of some more dynamic process 

  • more than just URL to set of results

  • technically more difficult

  • registry already exists, but would need work

  • registry is existing piece of software aimed to understand applications sharing information with other applications on how things work

  • only registry needs to be kept up to date

  • each app is responsible to keep up to date

  • we do not have software to validate whether links still work

  • Sara in chat: As an ERM only thing (knowing that it is work and an issue of capacity), can it be considered to have Supp documents at the AGL level as well? As a broader solution than just the Inventory thing.

  • Owen in chat: Yes that’s what I’d see as the easiest implementation. And that’s what I think is the easiest thing to do that meets some of the requirements we’ve discussed. I just don’t know when it could be done by

• option 4: 

  • we could do the survey that we thought about in our meeting on March 11th: 2024-03-11 Meeting notes: Agreements + Inventory interaction

    • question: do we have a general question that we would ask?

• it might make sense to do all 3 options

• prioritization
  

  • option 1: store URL in dedicated field in ERM

    • 5 votes

  • option 2: link instance, holding, item from Agreements app (like we do with orders)

    • votes

  • option 3: folow up on registry

    • 2 votes

  • option 4: do a survey to learn about Community requirements (questions tbd)
    

    • 4 votes

  • option 5: store link from Inventory records to Agreements resources

    • 2 votes

• Charlotte in chat: Would it be help ful with UX mock up on what it is we are entering, and how the search options will look like - for each of the options. That could also be part of the input on the survey, for the community to better follow what we have been discussing, and what we try to achieve. 

  • Maura agrees

• Charlotte will sit together with Sara to do some mock-ups

• we will reconvene in next meeting

Next steps

•  Charlotte will create some mock-ups - Sara will give support by demoing whta is needed

• we will reconvene on 17 Apr 2024 

Chat

Attendees

Action items