Versions Compared

Old Version 4

changes.mady.by.user Tod Olson

Saved on

compared with

New Version Current

changes.mady.by.user Paula Sullenger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

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:

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2092

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1659

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1636

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1056

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1015
 and 
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-907

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-875

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-845

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-728
 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-532

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-284
 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-105

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-100

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-932

Showstoppers:

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2615

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2551

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2200
 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1800

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1752

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1407


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; for all practical purposes we don't have data import; Bywater is looking into their institutions to see how it's working there

QuickMARC working well

OAI/PMH - still not working, not updated since Fameflower, becoming a problem for MSU; Bywater feels they've been updated

Not a lot new in Acq - suppress in MARC, not sure it's being suppressed in EDS

How will Chicago get its records for VuFind?  Not worked out yet

Chalmers - getting records direct from their national catalog

Simmons hoping to test OAI/PMH next month

ERM? 5 Colleges - some are implementing - Chalmers doing OK, but would like the tag features to improve;


Are implemented libraries still ranking features? MSU is trying, Chalmers has not had time, prioritizing bug reports

Chalmers hot topics - lack of title level request;


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.

Someone from CPT to discuss workaround issue?






Action items

  •