Meeting Minutes for 07/28/2021

Announcements

• Steamboat Schools are starting a new elementary school called Sleeping Giant
  • Location code will be ssg
• Next month’s cataloging training will be Basic MARC

FOLIO Update

• Cornell went live on July first
• Michigan State is live with Acq and ERM
• Stanford is shooting for implementation in the Summer of 23
• ReShare is going live for PALNI and ConnectNY in a couple of weeks
• Shanghai is developing something like a central admin tool
• Ian at ByWater demonstrated a nice reporting module he is developing on his own
  • It is an interface to query the FOLIO database directly rather than create a copy of the database for statistical purposes.  This is similar to the method Brandon thinks Marmot should use.
  • ByWater is using this for a client with 250,000 records now
  • Larger libraries said they would need a separate database
• There is still no way to delete bib records
  • You can suppress records, but this is probably not honored by record import for matching
• It is not possible to export MARC if you are not on AWS, but maybe TAMU has solved this problem
• They are discussing how they might have asynchronous meetings.  Now that there are people from Asia, Europe and America in more groups it is difficult to hold simultaneous meetings, but it is not clear how an asynchronous meeting is different from a chat group.
• Improvements in bound-with functionality
  • There will be a bound-with table to keep track of which items are attached to which holdings, and a flag in the item record to indicate that it is bound with multiple holdings.
• There was a demo of working INN-Reach software.
  • Only settings have been built yet.
  • You can input local agency codes for each library and the server connection.
  • You can limit locations and statuses that contribute or not.
  • Suppress individual records based on statistical codes.
  • Still hoping it will be ready for Lotus, but not sure.
  • They hope they don’t need a separate circulation module for INN-Reach.
  • A Koha library is live on Prospector now.  It took 6 months to get the certification from III.

Discussion Topics

• Pika suppression codes
  • This was based on a ticket from Mesa County.
  • After a lot of discussions, Ashley joined the meeting and we figured out that this was about Pika’s ability to suppress or make items non-holdable based on status.
  • We realized that there are three problem statuses
    • These are not already either suppressed or non-holdable in Pika:
      • g    damage
      • s    on search
      • l    presumed gone
  • Everyone in the meeting agrees that these three should all be non-holdable
  • Lloyd will run this by everyone on the UCC email
  • Assuming it is agreed to, it will be implemented in Pika

• EDS Export

  • Lloyd is working on setting up Sierra Scheduler to export files to EDS for Aims.  He is hoping that if he can get this working for Aims we could implement it for all the exports that are now coming out of Review File 2.  That would allow us to repurpose the 2M files that RF2 now uses.
  • To do that he needs the EDS logins for all the schools that are now using it.
  • SD51 also uses that export to send records to vendors.
    • Lloyd asks Shelly if her vendors would care if we sent them suppressed items.
    • Also, it would be easier if we could send item records.
    • Shelly has to think about that.
  • Jamie remembers that at one point we were sending the whole consortium’s file to EDS and they separated it out for us.  
  • Lloyd explained that he needs to figure out how to make Scheduler create a list of items then flip it to a bib list.  He thought that was not possible, but recently heard from libraries who are doing that, so it must be possible.
  • Lloyd has EDS login credentials from CMU, Adams, and Aims.  To set this up for the other schools he will need their EDS logins as well. 
• Gap analysis
  • The FOLIO gap analysis is mostly done.  
  • Lloyd reviews the gap analysis document: https://docs.google.com/spreadsheets/d/1jy4bJfmw7MBwIauw_9Qr-YpG0Y1qTE8DKqvKHWeF8RA/edit?usp=sharing
  • The stories are color-coded.
    • Green is working now or by the end of this year
    • Orange is either on the FOLIO roadmap or being developed as a 3rd party app
    • Red means it is not on the FOLIO roadmap
  • Lloyd linked to the relevant FOLIO feature for each story when he could find one.

Ongoing Action Items

Next Duplicates Sub-committee meeting: Aug 11

Next UCC meeting: Aug  25