| Documentation |
| Marcia asks for feedback. She wants to sign off the draft content in the installation section as soon as possible. We have to do work here and do some testing. This needs to be done by the group, at least for the single server installation procedure. Feedback from Jo Drexl: "I modified the documentation a few weeks ago and uploaded it to git. This needs to be reviewed and merged; the PR is open: https://github.com/folio-org/docs/pull/4/commits/604930f2656601bc69d30ce9cc822be99e5ec15b" ==> Skipped topic for next week |
| Shanghai Libraries |
| Please watch the webinar by the Shanghai Library Team (recorder recorded May 2020) : Supporting Your Institutions as They Move Online - FOLIO Community Update from Shanghai Library auf Vimeo (vimeopro.com) We would like to hear more about the Shanghai Library`s FOLIO implementation plans. Questions (and comments) from Ingolf after he has watched the webinar (mainly to Zhou Gang`s presentation): - Is there a central catalogue, which Folio needs to download from and upload to, or do you plan to use Folio as a cataloguing tool ?
- Do you plan to do data sharing between separate tenants in Folio, as described here, ABI-002 : Folio Architectural Blueprint Strategic Changes ?
- It sounds like you are planning to use multiple knowledge bases (why) ?
- You say that you want to implement 6 modules at first : User Management, Circulation, Inventory; Discovery (VuFind), Platform Management, APIs. When are you planning to use ERM ?
- User Synchronisation via OAuth (why OAuth vs. SAML)
- APIs: OpenAPIs (Which OpenAPIs do you plan to develop ?)
- A Platform Managemt App (= Consortium App ?) for Shanghai Libraries = a consortium of 400 libraries (interesting plan)
- Consortium functions: Can you explain more about what you plan to develop / have ?
- Net borrowing: Does this relate to ILL borrowing functions ? Is this designed to be cross-library (cross-tenant) ?
- developing SIP2-CN module supporting multi-tenancy, independent permission control etc. (great!)
- Folio to accomodate the RDF format for linked data → I (for the hbz) would greatly appreciate that !
Question / comments from Ingolf after having read Projects : - Elasticsearch. Just a general question: What is the use case of having ES in Folio, which will "only" be used by librarians ? (it is clear that we need a search engine for the discovery)
- (info for the group:) Here is a sketch about Technical Environment and Infrastructure from the Shanghai Library Project.
Answers - SHL doesn't have a central catalogue and did not have the plan to use Folio multi-tenancy functions, because they have not yet been developed in 2020.
- SHL branches (tenants?) will have own users and items, which should not be shared
- Consortial functions are essential for SHL. Are there already new consortia functions ready?
- SHL does not intend to do data sharing between tenants.
- Phase 1 wil start with circulation. ERM will be implemented later, in 2022 or 2023.
- The platform management app of SHL will enable and disable modules, and also deploy modules. It will also be used as an App Market.
- Cornell is live with ERM. Cornell was self-hosting at first and is now hosting with AWS and EBSCO as partner. They are using the EBSCO Knowledge base.
- Self-hosting is not recommended for single libraries (unless very large ones); it should be done by a consortium.
- In Germany, Leipzig and GBV are self-hosting.
- TAMU is self-hosting. It takes a team of about 5-6 people (of IT staff) to self-host.
- Net borrowing is meant as special online borrowing services to library users (B2C)
- Support the development of elastic search since the performance on searching is not as expected for SHL
- We will be interested in how Shanghai Library plans to host such a large library consortium. We are interested in details of their implementation plans. The Group is very
curious,how SHL will scale up FOLIO for its requirements. About the staffing? The database backend etc.? - We are interested in reporting solutions for the Folio implementation.
|