2022-11-30 Meeting notes: closed vs. open Slack channel

2022-11-30 Meeting notes: closed vs. open Slack channel

Date

Nov 30, 2022

Meeting time 12:30 until 1 pm ET due to Folio forum

Housekeeping

  • Convener and notes: @Martina Schildt

  • Next meeting: Dec 5, 2022

Discussion items

  1. Slack channel: closed vs. open | discuss pros and cons

    1. meetings?

  2. Form group to talk about expectations related to fast-adding records

  3. Select future topics

Minutes

  • AI SIG started as a small working group, became larger and later became a SIG

  • PC recommended a while ago to open up groups - if there are no reasons to keep them closed

  • similar example: ACQ group and RM SIG - opening up ACQ made sense and they are making good experience

  • group will most probably not get overrun

  • possibility: open channel but keep meetings closed

  • Slack channel should be open

  • few groups have closed meetings | meetings are not communicated

  • there is a private and a public part

  • Charlotte in chat: The App Interaction SIG is recommending cross app functionality, so maybe we are one of the very important groups to be ’Public’ - and open for everyone

  • Kristin: would not call our meetings closed, there is a wiki space, meeting minutes ... - if channel goes public 

  • we can continue to call this a meeting for POs, devs and conveners

  • if we make this open, Martina will communicate the open invitation via Slack in in PC

  • continue practice of asking the group for topics

  • cancel meetings (even with short notice) is fine

Chat

 

Future topics

  • Topic proposal by @Owen Stephens for October:

    • Use of shortcut keys and macros for more effective cross-app working  - it also be good to have UX and Stripes/dev knowledge for this discussion I think. I know @Laura (she/they) uses macros so might have insights into the potential for cross-app working

    • Potential for external 'workflow' solutions for cross-app interactions

      • I think 'workflow' is a dangerous term here - in this context it's more about automation than user workflows, although I think there is overlap

      • I was particularly struck by the solution in production at TAMU (Jeremy Huff and Sebastian Hammer presented, the recording is at https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/50dc6c87-3912-43fa-8287-56ec73b12bbb%2Fshared_screen_with_speaker_view%28CC%29.mp4 starting at 3 hrs, 14 min) - I think getting someone from TAMU to talk about how this is used would be v interesting

      • There was also a presentation on the use of a tool called Airflow at Stanford for "bibliographic workflow" but I've not watched that yet so not 100% sure if it is completely applicable - I think the core use case there was systems migration but it may go beyond that

      • Or Jenn Colt on using Prefect

      • does not need to be workflow across apps

  • UX/UI and implementers topics

    • should be Wednesdays

  • comprehensive look at where data is copied and stored as opposed to live data | how it is represented

Attendees

Present

Name

Home Organization

Present

Name

Home Organization

 

Ann-Marie Breaux

EBSCO

 

Brooks Travis

EBSCO

x

Charlotte Whitt

Index Data

 

Dennis Bridges

EBSCO

 

Dung-Lan Chen

Skidmore College

 

Gill Osguthorpe

UX/UI Designer - K-Int

 

Heather McMillan Thoele

TAMU

 

Ian Ibbotson

Developer Lead - K-Int

x

Jana Freytag

VZG, Göttingen

 

Khalilah Gambrell

EBSCO

 

Kirstin Kemner-Heek  

VZG, Göttingen

x

Kristin Martin

Chicago

x

Laura Daniels

Cornell

 

Lloyd Chittenden

Marmot Library Network

x

Marc Johnson

K-Int

x

Martina Schildt

VZG, Göttingen

 

Martina Tumulla

hbz, Cologne

 

Maura Byrne

Chicago

 

Mike Gorrell

Index Data

x

Owen Stephens

Product Owner -  Owen Stephens Consulting

 

Patty Wanninger

EBSCO

 

Sara Colglazier

Five Colleges / Mount Holyoke College Library

 

Kimie Kester

EBSCO

 

John Coburn

EBSCO

 

Zak Burke

EBSCO

Action items