Skip to end of banner
Go to start of banner

2024-03-20 Meeting notes: Agreements + Inventory interaction + WOLFcon

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 8 Next »

Date

 


Meeting will be an hour earlier for Europeans due to time changes.

Housekeeping

Discussion items

  1. AGR and INV interactions
  2. WOLFcon session ideas
  3. Meeting frequency

Minutes

AGR and INV interactions 

Questions to be answered

What kinds of functionality do users want out of cross-app links, e.g.
  1. App A provides a link to the “details” pane of a record owned by App B
  2. App A provides a link to the “edit” pane for a record owned App B
  3. App A provides a link to the “find-records” pane in App B
  4. App A displays a modal with the details for a record that is owned by App B
  5. App A displays links to records in Apps B, C, D (i.e. ui-dashboard becomes universal to any record type).
  6. App A provides a link to create a record in App B

From last meeting

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

WOLFcon sessions

Meeting frequency

  • less frequent meetings 
  • keep alternating meetings
  • Martina will propose a new meeting frequency that can be discussed on

Next steps

  •  

Chat


Attendees

Present

Name

Home Organization

     xAmanda RosTAMU

Brooks Travis

EBSCO

    x

Charlotte Whitt

Index Data


Dennis Bridges

EBSCO

    xDung-Lan ChenSkidmore College

Gill Osguthorpe

UX/UI Designer - K-Int

    x

Heather McMillan Thoele

TAMU


Ian Ibbotson

Developer Lead - K-Int


Jana Freytag

VZG, Göttingen

     

Khalilah Gambrell

EBSCO

     xKimberly Pamplin
     x

Kristin Martin

Chicago

     x

Laura Daniels

Cornell

     x

Lloyd Chittenden

Marmot Library Network


Marc JohnsonK-Int
     x

Martina Schildt

VZG, Göttingen


Martina Tumulla

hbz, Cologne

     

Maura Byrne

Chicago


Mike Gorrell

Index Data


Mike TaylorIndex Data

Natascha OwensChicago
    x

Owen Stephens

Product Owner -  Owen Stephens Consulting


Patty Wanninger

EBSCO

    xSara ColglazierFive Colleges / Mount Holyoke College Library

Kimie KesterEBSCO

John CoburnEBSCO
     xZak BurkeEBSCO

Corrie HutchinsonIndex Data

Lisa McCollLehigh

Jean PajerekCornell

Mark Veksler

Scott PerryU. of Chicago

Sharon BelaineCornell

vbar

Natalya PikulikCornell

Kara Hart
    Cathy Tuohy
     xJamie Jesanis

Tara BarnettIndex Data

Action items

  •  
  • No labels