Update of holdings also sets the updated date in attached items | Khalilah Gambrell | 20 Jun 2024 Update - Team is reviewing an issue that Julian has created https://folio-org.atlassian.net/browse/MODINVSTOR-1220 Notes from discussion: Khalilah reviewed feedback and change was made in Poppy to increase consistency but there are some institutions that are having workflow problems as a result. Julian created story to reflect this new feedback MODINVSTOR-1220 Team will review and estimate time needed. Does this story meet expectations? The item date can change when the holdings is updated, but should be reflected that the System made this change and not a user. +1s When should an item get updated? Item records should only get new version number/date update when certain holdings changes are made that the item inherits. Sarah reports that adding link to the holdings record triggers an item update. This should be considered a bug. When you change a system maintained field, e.g. a check-in, it is confusing that the metadata now reflects a user has made a change to the record. Item updated date becomes irrelevant if it is changed every time a holdings is touched.
Are there any patterns in FOLIO where the system makes a change and it is clearly reflected?
Can address the system user issue (short term), but the last updated date issue is much broader. How is this defined and is it different across institutions? Longer term (Sunflower) it would be good to look at this more, what do users want to track/not track? How does it relate to the change tracker? Action: Christie suggests this SIG collect use cases around changes, e.g. implied vs direct. Please see chat transcript below for more on this. Change Tracker Can view changes from app, e.g. in quickMARC and includes user (can be anonymized), what changes made, date, what app triggered the change. Summary: alot more discussion needed around all of this
|
PC updates | Charlotte Whitt | 2024-06-20 Product Council Meeting Notes Announcements: Reminder to folks about voting for the CC, TC and PC. No PC meeting on 6/27/2024 and 7/4/2024. The PC meeting on 7/18/2024 is to be Asian Passific Friendly meeting. Time to be decided later. WOLFcon updates: the Sched program will be sent out next week. A few notifications is to be send out 6/21/2024. Pretty much all sessions were approved. A few conflicts to be resolved. Separate registrations for both workshop (9/23/2024) and the conference. Both are now open, and registrations are trickling in. This year there is a fee for attending virtually 50.00 USD to pay for equipment. SIG report - the link is here. The new PC WG on Better Sample Data in FOLIO Snapshot will have their first meeting on 6/25/2024.
SIG Discussion: Conversation with SIG on PC action items from Things that could be better about FOLIO survey. Four topics which require the PC’s focus: Search - improvements to inventory search, both basic and advanced, and cross app search Courses - no PO for four years, no funding, some requirements work underway by Implementer’s SIG: 2024-01-30 FOLIO Implementers Meeting Notes and review to happen in August at Cornell Labeled Jira tickets for Courses
Data import - less about new functionality and more about performance, stability, reliability Reporting - options for reporting are distributed and inconsistently available to different FOLIO libraries - how can we come up with a general reporting strategy to ensure all libraries have options available?
|