Skip to end of banner
Go to start of banner

2020-09-22 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Date

Attendees

Paula Sullenger

Jean Pajerek

Kelly Drake

Jackie Magagnosc

Molly Driscoll

Debra Howell

Tracy L Patton

Monica Arnold

Marie Widigson

@Dwayne Swigert

Janice Pfaff

Brooks Travis

Martina Tumulla

Karen Newbery

@Joanna Cerro

Lisa Sjögren (EBSCO)

Peter Murray

@urszula Knepper

Ian Walls

egerman

Tod Olson

Steve Bischof


Goals

Discussion items

TimeItemWhoNotes




Finish ranking definitions

Rankings definitions


R1 - Urgent

Cannot implement without this feature; Cannot complete critical functions without this feature


R2 - HighLibrary operations are severely curtailed; Significantly lowers productivity; Cannot fulfill obligations to patrons or partners


R3 - MediumCan perform normal operations but productivity is noticeably lower; Workaround is insufficient and suitable only for short-term use


R4 - LowHas 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 interestDebra Howell

Round IV and Potential Workarounds

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?

Search filter: "Potential Workaround" is not EMPTY AND labels = round_iv

If the workaround doesn't work, put a comment in the JIRA

If several of us are having the same issues can we work together to get them addressed.  Mike Gorrell of CPT is aware of the issue.  Debra has requested that people stop using the workaround field for comments

Cornell's DRAFT list of issues with no workaround

Note: this is a draft, there may be three issues that really have workarounds.

Big issues:

UXPROD-2092 - Getting issue details... STATUS

UXPROD-1659 - Getting issue details... STATUS

UXPROD-1636 - Getting issue details... STATUS

UXPROD-1056 - Getting issue details... STATUS

UXPROD-1015 - Getting issue details... STATUS  and  UXPROD-907 - Getting issue details... STATUS

UXPROD-875 - Getting issue details... STATUS

UXPROD-845 - Getting issue details... STATUS

UXPROD-728 - Getting issue details... STATUS  

UXPROD-532 - Getting issue details... STATUS

UXPROD-284 - Getting issue details... STATUS  

UXPROD-105 - Getting issue details... STATUS

UXPROD-100 - Getting issue details... STATUS

UXPROD-932 - Getting issue details... STATUS

Showstoppers:

UXPROD-2615 - Getting issue details... STATUS

UXPROD-2551 - Getting issue details... STATUS

UXPROD-2200 - Getting issue details... STATUS  

UXPROD-1800 - Getting issue details... STATUS

UXPROD-1752 - Getting issue details... STATUS

UXPROD-1407 - Getting issue details... STATUS


Goldenrod implementersKelly Drake

MSU, Cornell (testing), Chalmers will upgrade in two weeks, Texas A&M's not stable enough for testing, Cornell will go live with ERM Oct 1

Data import - MSU - not functioning as expected - source records not linking to instance?  Lehigh has a workflow to do this but it's clunky.  Can't match on 035 so can't update OCLC;



Topics for next week
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.




Action items

  •  
  • No labels