Page Comparison

Craig and Vince will attend the meeting to discuss and answer any questions that may arise.

All: Please watch the recording in advance:

• Link to the recording: https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/276819cf-e9a6-4071-b72f-3bfb01131bbc%2Fshared_screen_with_speaker_view(CC).mp4
• Link to the chat: https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/276819cf-e9a6-4071-b72f-3bfb01131bbc%2Fchat_file.txt
• Link to the PC meeting minutes: 2023-09-14 Product Council Agenda and Meeting Notes

My unsorted questions (Felix):

1. Applications:
   1. Slide 9: Are there any disadvantages when several BE modules use the same storage? Would there be an advantage, e.g. better performance for read/write accesses?
   2. Slide 10: Merge mod-inventory and mod-inventory-storage into one module? What are the advantages and disadvantages of this?
   3. Slide 11: Independent application development lifecycles. How exactly is this supposed to work? As I understand it, the flower release is also intended to check the interaction between what Vince calls applications. Not only the interaction of BE/FE modules inside one application.
2. Platform:
   1. Slide 16: I understand Core+Functional to be like the iOS operating system and the Extended part are like applications I can install from the App Store. Would that be a reasonable analogy?
   2. Slide 18: Example ERM: The local KB is part of the Agreements modules, but is not used by the US libraries. How should something like this be handled? You can't simply separate the pieces (AFAIK).
   3. Can one switch from one platform to another, e.g. ERM platform first, then ERM+acquisition platform? Or would one start with ERM platform, stay on it and install the acquisition apps afterwards (as extended)?
   4. Who decides which application belongs in Functional or Extended when it is in dispute?