Refinement wording in number generators and sequences

Description

Tasks renaming or changing help text **

Number generator sequences
Renaming “description” to “note” (done)
Renaming “Health check” to “Usage status” (done, but it does not display in the UI, yet)
Renaming “Maximum number” to “Maximum value” 
Renaming “Warning threshold number” to “Warning threshold value”

 

Help texts new sequence modal and 4th pane in Number generator sequences: 

Help text for Warning threshold number: Must be lower than the “Maximum number” to “Maximum value” 

Help text Next value:  This field shows the next value in the sequence based on the current value in the database. It can be set manually as the starting value for a new sequence. Once saved, "Next value" cannot be edited. Delete sentence: Once saved, "Next value" cannot be edited.

 

Warnings and error messages:

Renaming "number" to "value"

  • Warning threshold number must be strictly lower than maximum number. --> Warning threshold value must be strictly lower than maximum value.

  • A warning threshold number cannot be set when there is no maximum number specified. --> A warning threshold value cannot be set when there is no maximum value specified.

  • When set, a warning will be displayed to users of the sequence when its value is reached. Must be lower than the Maximum number. --> When set, a warning will be displayed to users of the sequence when its value is reached. Must be lower than the Maximum value.

  • The maximum number must be smaller than the maximum imposed by the length of the "format" field. --> The maximum value must be smaller than the maximum imposed by the length of the "format" field.

For the following please consider https://folio-org.atlassian.net/browse/SI-42 Display alerts when the next value in a sequence is over the threshold or = max value
Error: The maximum number has been reached for this sequence. Please select an alternative
Warning: The maximum number for this sequence is approaching

 

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Gill Osguthorpe February 5, 2024 at 5:09 PM
Edited

QAed 5/2/24 - these all seem good .

Martina Tumulla February 2, 2024 at 1:26 PM

Hi , thanks for your explanation. Then we leave it as it is and I will delete it in the Jira ticket description. 

Ethan Freestone February 2, 2024 at 11:41 AM

 

UI side changes are easy to make. Changes:
Renaming “Users: Patron barcode” to “Users: User barcode”
Renaming “users_patronBarcode” to “users_userBarcode”

are slightly more complex, since this record will already exist in any system which had Service-Interaction backend module deployed for Poppy (At least, I haven't checked how far back that record goes)
https://github.com/folio-org/mod-service-interaction/blob/release_3.0.x/service/grails-app/services/org/olf/HousekeepingService.groovy#L60-L61

We can decide to change that record code if we really wish to, however previously we have made decisions on this for the openAccess and patronRequest (ILL) generators and not changed code, since it is possible it's in use in current systems. Label change, however, is fine. We can decide then whether to create a migration for this data, as we have done for the examples above, or not if for whatever reason we don't wish to.

I suggest we split that into its own Jira so that the rest of these can be code reviewed, so for now I'll put this issue into CR, we can discuss further on the next call

Done

Details

Assignee

Reporter

Priority

Development Team

K-Int

Release

Quesnelia (R1 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 1, 2024 at 4:56 PM
Updated June 17, 2024 at 3:57 PM
Resolved June 17, 2024 at 3:57 PM
TestRail: Cases
TestRail: Runs