2023-11-14 - Consortia SIG Notes

Consortial Reporting Needs

Thoughts on how to update the table?  Ideas?  Anyone taken a look yet? 

• First column : is it the app or is a system?  How does this relate to the reporting app?
  • The Reporting app and Lists app are not the same tool ; two separate reporting tools
• Do we restrict the scope of this table to native FOLIO?  
  • How to represent needs when we don't know everything about upcoming consortial tools like OpenRS?
  • How can libraries who are on FOLIO, in single tenants able to gather this type of information?
  • Example : libraries that don't use ldp/metadb, but want to be able to run 'lists'?
  • Get rid of first column?
  • Action: move app integration columns to the far right, rename the 'tickets' column to FOLIO, include the ticket links, add columns for other apps like Lists, OpenRS, DCB, etc.
• Focus on the reports themselves : is anything missing?  
  • For example : who runs the report?  do reports need to be able to be run by a library and a consortium?
  • Report missing from the list : lost items
  • Replace 'Both' in the 'Who' column with explicit Library, Consortium
    • Assumption is that all these reports should be able to be done at the library level and consortial 
    • Do we need this column? – Yes, for now until we get the new columns at the end that address the various apps
  • Add a new 'Assumptions' to the table 
    • Add an assumption that both a library and consortium have a need for data gathered by these types of reports
    • Noah added some during the meeting
  • Do we need the 'Need' and 'Use' columns?
    • Original use of 'Use' column was to differentiate between when a need is immediate, in data warehouse
    • Agreed we do not – Noah has removed them
• How does the list of 'Resource Sharing' reports look?
  • Add a new one for lost items
    • Status = lost, were lent within the consortium, shared with libraries within the consortium so everyone can look for them
    • Similar to the 'in transit' too long in purpose
    • Noah added a new row to the table
  • Do we need the 'Missing and Lost needs to be included' in the 'Loaned items overdue....'?
    • No – Noah to delete it
  • Do we the '-RA related'?
    • Yes – we want to designate that other SIGs might be interested in these 
    • Margaret to update the comment so it's clearer to the reader
• How does the list of 'Coordinated Collections' reports look?
  • RM is now Acquisitions SIG; likely also involves serials management
  • Updates to comments' wording & spelling
  • Do we need a 'Shelflist' report?  Is it too large, unwieldy?
    • Should it be renamed to indicate it's just for retention commitments?
    • Yes, but then create a new row to note needs for shelf lists by call number, authors, etc. – Noah to perform the update
• Has the Consortia SIG ever had a PO?
  • Not that we know of
  • It's a lot of work