2021-04-20 Meeting Notes

Date

Attendees

Paula Sullenger

julie.bickle

Marie Widigson

Peter Murray

Kelly Drake

John Ballestro

Patrick Roth

Anne L. Highsmith

Kristin Martin

Tom Wilson

Patricia Ratkovich

Monica Arnold

@Ana Ugaz

Michael Arthur

jackie.gottlieb@duke.edu (Deactivated)

@Rhonda Fuhrman

Jean Pajerek

Charlotte Whitt

Brian Clark

Brooks Travis

Dwayne Swigert

Martina Tumulla

Michael Patrick

Debra Howell

Ian Walls

Nick Cappadona

Jacquie Samples

Jay Campbell

morganm@gvsu.edu

Darsi Rueda

Jenn Colt

Aaron Neslin

Karen Newbery

Tod Olson

Mark Veksler

Christie Thomas

egerman

Chulin Meng

Shannon Burke

Kyle Banerjee

Anya

patty.wanninger

Robert Scheier



Goals

Discussion items

TimeItemWhoNotes

Kiwi pointing exerciseHolly MistlebauerDeferred to April 27

Iris Release / Data ImportKelly Drake

Reliable / Relied on Data Import Features (Google Doc)

How are related issues arising from bugfest being address? 

  • What about underlying fragility?
  • Non-spec bugs?  These are put in the queue for ranking and more info gathering 
  • Q- I didn't know we ranked bugs - Kelly - only non-spec bug, and it is a murky area. Christie - Should these be verified in UAT prior to bugfest? Brooks - we're working toward this, not there yet Christie - frustrating when things are developed in a way we didn't expect.
  • Charlotte - could we earmark a % of what devs see as a non-spec bug but SMEs see as a regular bug
  • Regressions? Should be scheduled to be fixed in the same release

What bug-free features related to MARC handling can be expected in Iris & Juniper?

  • Anya - there shouldn't be any P1s or P2s found during bugfest? Can there be a list of known issues in release notes? And list of P3s and P4s that might be in Juniper
  • Tom - is it possible to know what can be done without a bug - clearly described
    • Kelly - AMB may be able to answer that next week
    • Michael Arthur - when will we be able to catalog?
    • Jacquie - right now single record import isn't what we need it to be, the workarounds being used are not what FOLIO was supposed to be
  • We try to use it everyday and it's broken, there are so  many parts, its very hard to report and troubleshoot, how can we have a reliable workflow?
  • Jenn - testing is focused on new records, but  most of our work is based on match profiles
  • Christie - a lot of our work is updating records and there isn't much going on here
  • PTF - any performance testing on match profiles?
    • Is there a dependable number on batch loads
    • Can there be testing on match profiles?
  • Are there features that are likely to be resolved by Kiwi?
  • Need clarification of the relationship between Inventory and SRS wrt editing records, updating records, overlaying records, source of truth location, any loss of data or relationships when records are stored in one area or the other
  • Tom - what are the things we are fairly certain we can actually do?  We must be precise in our language, define terms with a specificity that we're not hearing.  Concerned that the questions asked by the community are being dismissed.
  • Jenn - for data import, can only do 1,000 records at a time, then must wait a while
  • Kelly - and that may change tomorrow, stability
  • Michael - please talk about the balance between features and stability.  If we know that things will not be in Iris, we just need to know that
  • oice on timing.  Probably the case for the mid-year implementers.

Can we say without any fudging that as of iris, sits will be able to export MARC bibs and hldgs from FOLIO, edit them singly or in bulk with an external utility, and reload them into FOLIO with appropriate overlays? 

  • Mark - MSU is live, able to import, involves a fair amount of outside-FOLIO work, have been able to make it work.
  • Kelly, can you do bulk overlays? Mark - if you pre-condition the records.  Can do about 100 at a time.  Or can select 20 files with 25 records each.  Can get the job done.
  • Michael - but you're not working in FOLIO, sounds like a lot of workarounds.  When we say we're "live with FOLIO" it won't be until they are actually working in FOLIO
  • Kelly - it depends on what you're able to do and what you're willing to put up with.  Don't think there are many libraries live on FOLIO because they want to be, but because they had no choice
  • Tom - what does it depend on?  where are some examples where it is working?  If a procedure is outside of FOLIO, it's OK for a while, but it implies we can get data in and out.  Some of us haven't had as much success at that as MSU.
  • Kelly - this is something the POs can't answer, they don't know workflows
  • Christie - like where this is going, but maybe the POs can help us understand where the boundaries are, to help us figure out how to best use Data Import when Iris is released
  • Mark - frustrated by the lack of detailed logs when things fail, don't know what is happening
  • Jacquie - want to document when things don' work as expected - is this happening now?  Does someone have a link
  • Kristin - know we have general use cases but need real-world use cases.  How do I overlay 10,000 records?  Is there some other scenario for data import?
  • Jacquie - also don't want to have a bunch of duplicate documents, feels some of this is siloed
  • Tom - would be nice if someone could clarify where this stuff is documented in the wiki or wherever
  • Kelly - it all depends on stability








Future topics

Receiving workflow demos deferred.

What can and can't be done with MARC records right now?  There's some imprecise language in conversations.  Will look into inviting Laura Daniels, AMB, and Khalilah - April 27

Holly will attend on Apr 13, 20 & 27 to address questions related to pointing exercise with a retrospective early May






Next Meeting
April 27 - AMB & Khalilah will talk about what will be released in Iris and Juniper.  Laura Daniels to talk about cataloging at Cornell

Action items

  •