2022-10-05 Meeting notes: PC and SIG communication | Future topics

Date

05 Oct 2022

Housekeeping

• Convener and notes: Martina Schildt

Discussion items

1. • Select topics for next meetings
   • AI Slack channel: open vs closed
   • PC questions
   • "How we can be better to coordinate, and prioritize work on features, which the libraries have been asking for for a long time."

Minutes

Future topics

• Topic proposal by Owen Stephens for October:
  • UX patterns for common cross-app tasks (e.g. would it be useful to have a UX for a 'quick add' task that could be used in different contexts when you need to create something in another app). I think it would be good to have UX specialists (Kimie, Gill) present for this, and possibly also some Stripes devs (e.g. John C/Zak)
  • 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
• UX/UI and implementers topics
  • should be Wednesdays

AI Slack channel: open vs closed

• Discuss and decide

PC questions for SIGs

1. 1. Can you share the purpose of your SIG: functional area/cross cutting/affinity group, etc?

      1. About us

         The App Interaction SIG reviews workflows and data flows between FOLIO apps to clarify relationships and agree on future development steps. Its role is to determine gaps in cross app functionality and develop mechanisms and solutions to support required functions. For this outcome to be achieved it defines app interactions for all types of resources as well as all kinds of use cases for the various needs of institutions. As part of defining workflows between FOLIO apps, different scenarios for varying external partners and sources are taken into consideration.

   2. What areas does your SIG have responsibility for?
   3. What do you feel like your SIGs purpose is currently? Has it changed over time?
   4. Do you have product owners who regularly work with the SIG? Do you feel that your requirements are being successfully developed into FOLIO?
   5. How do you feel about the resources allocated in the development areas that are focused on?
   6. What are some of the challenges facing your SIG/subgroup? Are there ways in which you feel the SIG has been unable to accomplish it's mission?
   7. If you work on areas of development, do you feel like there are areas of development not resourced at all or significantly under-resourced?
   8. What has been successful with the SIG? What things contributed to that success?
   9. What could the Product Council do to help the SIG?
   10. Do you feel like the Roadmap accurately represents the work of your SIG (both desired and already accounted for)?
   11. How can we improve our communications with the SIG? Does the current monthly reporting work? Would have a dedicated PC meeting for your SIG be helpful?
   12. Is the SIG comfortable communicating with the PC and have a sense of when a PC conversation would be helpful?
   13. What functions should the PC be accomplishing and how would the SIGs like to have those need met?

"How we can be better to coordinate, and prioritize work on features, which the libraries have been asking for for a long time."

• Proposal by Charlotte: "How we can be better to coordinate, and prioritize work on features, which the libraries have been asking for for a long time." But maybe this is a topic we can talk about, and bring back some ideas to the PC and the Release planning team? We have the ROAD jira key project, but I'm not sure these tickets are really used as a planning tool, when we do planning for the next (flower) release, and for the following (flower) releases.

Next steps

Chat

Attendees

Action items