Skip to end of banner
Go to start of banner

Spitfire Poppy CSPs / Upgrade Issues

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 8 Next »

ECS - complete

Ticket

Description

Status

1

https://issues.folio.org/browse/UIIN-2728

Prevents ECS users from viewing other tenants' locations in the Effective location (item) facet.

APPROVED

2

https://issues.folio.org/browse/UIPFI-138

Prevents ECS users from viewing other tenants' locations in the Effective location (item) facet (Find instance plugin)

APPROVED

3

https://issues.folio.org/browse/UIPFI-140

Users are not able to identify the searched effective location in the corresponding facet

APPROVED

CSP #2 - March 1st

Ticket

Description

Status

1

UIMARCAUTH-363 - Getting issue details... STATUS

Facet counters do not update when searching and navigating through results in the MARC authority app, which prevents users from accurately interpreting search results

APPROVED

2

MSEARCH-686 - Getting issue details... STATUS

Work required for Folijet’s bugfix related to consortial holdings accordion in ECS. Retrieving additional fields for holdings/items.

REQUESTED APPROVAL

Likely CSP #3

Ticket

Description

Status

1

MSEARCH-689 - Getting issue details... STATUS - placeholder story while waiting for confirmation

In the preexisting algorithm, the logic checked the call number against the algorithms for all types - I believe based on the marc4j library. Meaning, call numbers were interpreted based on the "valid" parameters built into the algorithm. Dewey numbers with alpha characters were already not sorting based on Dewey rules - they were being interpreted as LC call numbers. This validation became more apparent when call numbers were split by types - the existing validation rules were being applied, but instead of checking against ALL types, the logic checks against the assigned type. Meaning, call numbers with Dewey types that "failed" this validation are not getting the shelving order assigned, and therefore are not showing up in results.

  • Requesting feedback on 2/29/24: Assumption is that we will need to remove validation.

  • Blocking upgrades

AWAITING FEEDBACK

Upgrade issues

Ticket

Description

Fix

1

MSEARCH-670 - Getting issue details... STATUS

Call numbers showing up in other browse by type options. - is this related to the type inheritance issue?

Script

2

MODELINKS-223 - Getting issue details... STATUS

Running into an issue with authorities migration in Poppy upgrades

Existing script

3

  • No labels