Cannot implement without this feature; Cannot complete critical functions without this feature
R2 - High
Library operations are severely curtailed; Significantly lowers productivity; Cannot fulfill obligations to patrons or partners
R3 - Medium
Can perform normal operations but productivity is noticeably lower; Workaround is insufficient and suitable only for short-term use
R4 - Low
Has minimal impact on productivity; feature commonly available in other ILS/LSPs; nice to have; Workaround is viable although long-term solution is still needed (or workaround lacks functionality)
R5 - Not needed
Topics of interest
Debra Howell
Based on UXPROD-1752, optimistic locking, where it was ranked but there was a workaround, which didn't actually work.
Debra found 64 workarounds in JIRA - some are go-live (20) and showstoppers (6) for Cornell that aren't being worked on. She was told to make comments in JIRA
Do other institutions want to do the same search - look for your features that have workarounds that aren't actually workarounds?
Emma Boettcher, PO for item status - trying to work out a plan for if the custom item status feature doesn’t make it into the development plan before implementers go live with FOLIO. Would like to discuss what item statuses should be prioritized for development.