...
Time | Item | Who | Notes |
---|---|---|---|
5 | Welcome | Ingolf |
|
Integrations prerequisites | Ingolf, all | Tod and me brought our issue into the Implementers Group on Tuesday. They said they will make additions to the Spreadsheet (FOLIO Source Data and Integrations Spreadsheet ) until July 31st. The spreadsheet is considered "high level" and we are supposed to do the low-level, viz. technical, analysis. I transmitted all information about integrations and JIRA-Tickets from that spreadsheet to our analysis wiki site: Integrations Prerequisites- Open features and known gaps I had no time to further look at it, at the moment it's just 1:1 what was in the spreadsheet. I hope I can make some first re-arrangements and see where are gaps and what needs to be prioritized (if I can judge that). Otherwise I hope we can do this work tomorrow in the group meeting. Uschi made a comment about RFID integration which we should include. Meeting Notes We have to test these things out. What is under development, what is not → GAP analysis Brandon: Wouldn't prioritizing these integrations fall under another SIG ? In some cases yes, though implementers would not have the technical background to provide good requirements / estimates. Tod: Do we have the pieces on the development channel to allow it to happen ? We have to cut out unpleasant surprises. Prioritizing is not the point. We have to decide what is missing. Jo: We need to integrate data that all libraries need. It's an "information gateway" Ian/Phil: Some tools could open up doors. We need to give architectural guidance. Tod/Phil: We have to consider lead times / trajectories. We have to keep in mind the MVP concept. We should think of these from the FOLIO product perspective, not just our institutions.
(Reporting) How to build up the dataflow from Okapi to the LDP The Reporting / LDP situation is challenged at the moment, not enough resources, much more work needed in designing the schema (a moving target with new releases of FOLIO) Lead time: depends on how many integrations one institution needs to integrate Jason: We need the things working in 6 month lead time / we need test instances and training etc. If that doesn't exist in the Jan 2020 release, we have to change to whole timeline. Classic integration problems: have test instances ... Lead time for Lehigh + Chicago : 6 month, too. Tod: Defining export files. Unit testing would catch changes in the underlying modules. How do we allow for that ? But that does not minimize the sheer amount of work for integrations. |
Action items
- Ingolf Kussget someone from Reporting SIG (probably Sharon AND Nassib) into SysOps SIG meeting. Right now, Reporting/the LDP is a "pipe dream". Phil and Sharon talked about it afterward and she'd be delighted to update us on the LDP situation and challenges.
- Ingolf Kuss , Uschi Klute : Talk to Emma Boettcher about RFID integration
- Christopher Creswell will talk to Michelle Suranofskyabout Patron Lookup functionalities in NCIP ,
. At the moment, there is no way to query whether a user is valid i.e. has current privileges. At the moment, the user status is "active" or "inactive".Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key SIP2-25