JSON targeted format; MARC should be an option should an institution so choose.
Identified commonalities between the functional requirements of the data loader and the UI import app.
Proposed that there are so many commonalities that the data migration loader and the batch loader should be considered side-by-side. How to prioritize and go forward? The 'guts' would be the same; would need a command line interface for data migration and a FOLIO interface for day-to-day loading.
Issues: we need a way to get the data into FOLIO that is not on a one record at a time basis available asap.
Questions: Where will the data originate for the discovery systems?
15 mins
Loan review
various
Conclude discussion on the gap analysis on loans, including how to facilitate decision-making on which data elements are missing and need to be added. Here is a link to the spreadsheet.
Loan data gaps ("gaps" tab in spreadsheet) have been identified by Cheryl (see action item below). LBS has reviewed and added their input. Some data may not live with the loan (e.g. "Claims returned" status for an item as distinct from the history of the loan transaction). Some things that need to be thought about, may need to be raised to the SIG for design:
Renewal history
Claims returned processing
Damaged item processing
Missing item and pieces processing
Notices/relationship to loan
More discussion for next week.
Historical circulation data – concern that keeping historical loans along with active loans in the same storage could be problematic.
Cheryl
Action Item: Cheryl added a 'gap tab' to the loan spreadsheet and added some possible U Chicago gaps. Some of these might reside elsewhere. Please take a look and provide feedback.
The plan is to present this to the RA SIG. Action Item: Next week we'll talk about when.
Action item
Chris Manly : provide a more detailed description of what LS Tools is used for / what features we need together with the Cornell team.