2024-03-11 Meeting notes: Agreements + Inventory interaction
Date
Meeting will be an hour earlier for Europeans due to time changes.
Housekeeping
- Convener and notes: Martina Schildt
- Next meeting:
Discussion items
- Meeting frequency
- AGR and INV interactions
- Tentative:
Technical input on application to aplication linkageGet guidelines or information on standard approach for storing a link
- WOLFcon session ideas
Minutes
Meeting frequency
- less frequent meetings
- keep alternating meetings
AGR and INV interactions
Defined as next steps in last meeting:
- Identify what can be solved
- Identify what the minimal needs are
- Come back to this discussion rather sooner than later
- Discussion with technical input on application to aplication linkage of this type
- Get guidelines or information on standard approach for storing a link
- figuring out where the connecting points are that make sense to have those connection/integration happen
Minimal requirements
- ability to display link in all records | generic link field that simply points to another record
- in Agreements users would like to have this as a first step for AGLs
- ability to add multiple links to one AGL
- a URL (might be list of records or concrete titles) > to get a list of records you currently need to add codes to Inventory records (as pre-work)
- in contrast to the record UUID that would always link to a specific record
- similar to what is already available in supplementary documents in agreements
- using URLs seems more flexible
- adding URLs as well as linking to UUIDs will provide one way linkage
- URLs are searches
- URL would also give flexibility to link to other things
Maximal requirements
- Changing a link on one side should update it in the other app automatically
Level at which linkage needs to take place
- Inventory side: Instance versus Holdings
- Agreements: resource in a KB exposed by Agreements versus AGL level (resource or package of resources)
- example: this AGL covers this Inventory resource
- linkage from both sides needed
Next steps
- Community survey to understand use cases and what will work best for most sites
- continue this discussion on
- discuss what options we will present to Community on
- discuss possible WOLFCon topics
- Martina will propose a new meeting frequency that can be discussed on
Chat
Attendees
Present | Name | Home Organization |
---|---|---|
Amanda Ros | TAMU | |
Brooks Travis | EBSCO | |
x | Charlotte Whitt | Index Data |
Dennis Bridges | EBSCO | |
x | Dung-Lan Chen | Skidmore College |
Gill Osguthorpe | UX/UI Designer - K-Int | |
Heather McMillan Thoele | TAMU | |
Ian Ibbotson | Developer Lead - K-Int | |
Jana Freytag | VZG, Göttingen | |
Khalilah Gambrell | EBSCO | |
Kimberly Pamplin | ||
x | Kristin Martin | Chicago |
x | Laura Daniels | Cornell |
x | Lloyd Chittenden | Marmot Library Network |
Marc Johnson | K-Int | |
x | Martina Schildt | VZG, Göttingen |
Martina Tumulla | hbz, Cologne | |
x | Maura Byrne | Chicago |
Mike Gorrell | Index Data | |
Mike Taylor | Index Data | |
Natascha Owens | Chicago | |
x | Owen Stephens | Product Owner - Owen Stephens Consulting |
Patty Wanninger | EBSCO | |
x | Sara Colglazier | Five Colleges / Mount Holyoke College Library |
Kimie Kester | EBSCO | |
John Coburn | EBSCO | |
Zak Burke | EBSCO | |
Corrie Hutchinson | Index Data | |
Lisa McColl | Lehigh | |
Jean Pajerek | Cornell | |
Mark Veksler | ||
Scott Perry | U. of Chicago | |
Sharon Belaine | Cornell | |
vbar | ||
Natalya Pikulik | Cornell | |
Kara Hart | ||
x | Cathy Tuohy | |
Jamie Jesanis | ||
Tara Barnett | Index Data |