2018-11-16 - System Operations and Management SIG Agenda & Notes
Date
Attendees
Goals
- Overview Source Data and Integrations Spreadsheet, determine how to proceed with prioritization and integrate into JIRA Tickets.
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5 | Welcome | Ingolf |
|
20+ | Integrations | all | We will review our entries in the FOLIO Source Data and Integrations spreadsheet. TAMU not complete yet. Let's look also at the Five Colleges' Integrations, thanks to Kathleen Berry. Maybe we can sort out what is already in the development pipeline and what still needs to be added. Call from Forum Facilitators SIG |
20+ | Integrations cont. | all | Demo of GOBI: Video by Ann-Marie Breaux (Deactivated) available? Very simple – creates a purchase order.
Prioritization of integrations for each institution: Purpose of identifying integrations – Prioritization for each institution. Priority in development pipeline: P1-P5 How important is it that integrations come within 4-6 months of Folio go-live for each institution? Is it Okay for integration support to be spread out after Folio go-live?
SIP2 protocol: Used with self-checkout. Used by many libraries. Sends a lot of data over the network, insecure?
Identify DUO requirement: Folio does not need to have any knowledge of Duo – handled through Cas/Shibboleth Anya may know about course reserves – support for an App? |
15 | Going forward with integrations | all | To search in Jira: External_sys_int label – list of JIRA tickets that relate. Identify Jira issue for each integration. Use this spreadsheet to get what we need, generate the list. What are the software systems, interfaces, protocols and APIs? Aggregate the institutions. Hkaplanian will compare spreadsheet with what is actually in Jira. |
Action items
- Anne L. Highsmith will fill out remaining TAMU integrations next week.
- Hkaplanian will match spreadsheet with JIRA tickets at the beginning of next year.