Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Circulation Rules Editor - Normalization of non alpha-numeric characters from Location Codes in editor

Description

Support the ability for spaces and non alpha-numeric characters in Institution, Campus, Library, Location Codes to be replaced with a dash when the Codes are written into the Circulation Rules. Note that similar code is currently in place in the editor for normalizing policy names.

Settings>Tenant>Locations:Code - This field is free text and can contain spaces and non alpha-numeric characters

Scenario 1: spaces
Given:
FOLIO>Settings>Tenant>Locations:Code=PER PKEM2
and
FOLIO>Settings>Tenant>Locations:Folio name=East Asian Collection Microforms Microfiche

Then:

  • Circulation Rules Menu for Locations should read:
    PER-PKEM2 (East Asian Collection Microforms Microfiche)

  • Encoded Circulation Rule should read:
    s PER-PKEM2

Scenario 2: non alpha-numeric
Given:
FOLIO>Settings>Tenant>Locations:Code=PER>PKEM2
and
FOLIO>Settings>Tenant>Locations:Folio name=East Asian Collection Microforms Microfiche

Then:

  • Circulation Rules Menu for Locations should read:
    PER-PKEM2 (East Asian Collection Microforms Microfiche)

  • Encoded Circulation Rule should read:
    s PER-PKEM2

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Sergiy SergiyenkoAugust 19, 2019 at 8:02 AM

, please could you check this story on https://folio-snapshot.aws.indexdata.com/? Thank you.

Emma BoettcherAugust 16, 2019 at 8:32 PM

Added (low-priority, draft) stories for that validation to a separate feature, .

Emma BoettcherAugust 15, 2019 at 2:48 PM

Yes, I think validating elements of the location hierarchy should be a separate story from this one. I am talking with the PO's who control other attributes of circulation rules to discuss validation/format requirements and how universal those should be.

Viktor SorokaAugust 15, 2019 at 11:43 AM

, I have already raised a similar question and have a response from . Anyways, it would require the preliminary work both on the backend and UI in order to add that validation and should not be considered as a part of this story in my opinion. are you okay with it?

Dmytro PopovAugust 13, 2019 at 10:07 AM
Edited


As the code field accepts any text without validation, in theory, the operator can enter something like this:

So, we may have more than one non-alphanumerics in the midddle and/or at the start or end of the code. According to the existing implementaiton, the normilized version displayed in the rule editor would be:

  1. Is this as expected?

  2. Do you think it's a good idea to implement some kind of the code format validation in the creation of institures, campuses, libraries, locations, etc. ? For this approach we would need to think of the valid format first.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Concorde

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 20, 2019 at 11:48 PM
Updated September 19, 2019 at 10:34 AM
Resolved August 19, 2019 at 2:34 PM
TestRail: Cases
TestRail: Runs