Web Client: Serials - Predict New Issues Defaults to Previous Pattern
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.0 |
Fix Released
|
High
|
Unassigned | ||
3.1 |
Fix Released
|
High
|
Unassigned |
Bug Description
This has been tested on Evergreen 3.0.3 - Web Client.
When using the Predict New Issues button from either the Manage Issues tab or Manage Predictions tab of a record's Serials interface and multiple patterns exist on for the subscription, (only one active), the Predict New Issues dialog box has to be "tricked" into using the new pattern.
To get the dialog box to display the correct pattern, the "Type" can be changed to something else, (i.e. Supplement), and then changed back, (i.e. Basic).
Additionally, if issues exist and Predict New Issues is used, the system ignores the entered information. This is discussed in this bug: https:/
I have split the bugs because they seem to be separate issues but they combine to create some frustrating workflows.
One way these bugs cause problems is when a subscription changes the way it is published, (i.e. from monthly to seasonal).
Here is how the worfklow SHOULD work:
1. Create/select a new prediction pattern for the new publishing schedule.
2. Activate the new pattern and deactivate the old pattern.
3. Click Predict New Issues.
4. Enter in the new publication date/enumeratio
5. Enter a prediction count and select Save. New issues should be created using the new prediction pattern.
If this workflow is followed then the new issues will ignore the entered information and continue to predict off an old issue with the old prediction pattern. If staff somehow manage to get the new prediction pattern to show, then Predict New Issues will sometimes fail silently and not predict new issues, (in the XUL client, the way around this was to create a new starting issues), and to continue predicting this way can lead to some eraditic results.
Here is a workaround to get it to work:
1. Create/select a new prediction pattern for the new publishing schedule.
2. Activate the new pattern and deactivate the old pattern.
3. Edit Holdings Code of latest expected issue.
4. In the dialog box, change "Type" to Supplement and then back to Basic. This will update the dialog box to the new pattern.
5. Enter in the new issue's publication date/enumeratio
6. The issue should be updated to the new pattern. CLick Predict New Issues.
7. In the dialog box, change "Type" to Supplement and then back to Basic. This will update the dialog box to the new pattern.
8. Ignore fields because they won't be recognized.
9. Enter a prediction count and select Save. New issues should be created using the new prediction pattern.
Predict New Issues should show the chosen/active Prediction Pattern.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: webstaffblocker |
Changed in evergreen: | |
assignee: | nobody → Mike Rylander (mrylander) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
A patch is available at the tip of the user/gmcharlt/ lp1745427_ change_ pred_patterns branch:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ gmcharlt/ lp1745427_ change_ pred_patterns