/
2018-11-02 - System Operations and Management SIG Agenda and Notes

2018-11-02 - System Operations and Management SIG Agenda and Notes

Nov 02, 2018

Date

Attendees

Goals

  • Welcome new members JiHe, Robert Douglas
  • Deployment updates from our institutions

Discussion items

TimeItemWhoNotes
5WelcomeIngolf
  • Welcome JiHe
  • Review Action Items
    • Harry's question about known issues on OAI-PMH implementations
    • Update by Harry on FOLIO OAI-PMH Module development
    • hbz Integrations (Ingolf & Martina Tumulla):
      1. LASER - License Administration System for Electronic Resources
        1. Based on a central Knowledge Base (KB)
        2. License administration for e-resources "on a local, regional and national level"
        3. https://www.hbz-nrw.de/projekte/LASeR
        4. required interfaces:
          1. ONIX/PL
          2. KBArt (an exchange format, not an interface)
      2. Discovery integration
        1. hbz uses DigiBib as Discovery, https://www.hbz-nrw.de/produkte/digibib-loesungen/digibib
        2. Needs interfaces:
          1. OAI-PMH
          2. Z39.50
          3. PAIA - Patron Account Information API, used in GBV and developed by GBV, https://gbv.github.io/paia/paia.html
          4. DAIA - Document Availabilty Information API, used and developed in GBV, https://daia.gbv.de/
      3. ILL
        1. Communication between the library system and the ILL server currently via the SLNP protocol - a protocol licenced by OCLC, not an open interface. We have to think about this. Maybe want to replace this by NCIP services.
      4. ELi:SA
        1. ELi:SA is an Acquisition Portal for Literature; Searching and Selecting literature, http://elisa-staging.hbz-nrw.de/
        2. Developed by hbz (et.al.)
        3. we still have to find out which interfaces ELi:SA needs to have on the library system side.
  • do we need a note taker ? (→ Ingolf)

Deployment Updates from institutionswhole group

Introduction of Aliyun / Alibaba Cloud ?

JiHe works for Callas, a Chinese library consortium, and has been in the FOLIO project for about one year now.

They are woking on an Alibaba Cloud Service (also known as Aliyun) for FOLIO.

JiHe had an issue with Hazelcast in an AWS deployment, see the discussion in the Slack chat.

Issues from the other institutions / SAML, sso ?

    • Chris Creswell reports an issue with FOLIO as a SAML Service Provider. A get request results an error where it is supposed to give back the SP metadata.
    • Harry sent Chris an Email with information about SAML SP setup .
    • Mark Stacy did an alternative installation using docker-compose , has documented that here: https://github.com/folio-org/folio-install/tree/kube-rancher/alternative-install/docker-compose/images/stripes (thanks, Mark!)
    • Jason and Anton deployed a Rancher setup
    • Miami University (Craig B.) explore using a Rancher setup
    • Greg is working on replicating the Rancher workflow at Cornell.

Other announcements: A Lousiana Consortium will probably be willing to participate in the SysOps SIG in the near future. There are 4 people in that consortium who work in the FOLIO project.


Outlook to future sessionsIngolf
  • Jakub Skoczen has an update on data loading ready probably for next week, Nov 9.
  • Multitenancy will likely be an issue in one of our future meetings. Brought up by the Consortia SIG. Right now, FOLIO allows for single-tenant or multi-tenant installation:
    • single-tenant = share everything
    • multi-tenant = share nothing

FOLIO Plan for the future is the following:

    • cross-tenant , "share something" = controlled sharing across tenants

See Cate's slides FOLIO single tenant implementation ; YouTube-Video: https://www.youtube.com/watch?v=RTI0CkSccLs

    

Action items

  •