Web Client: Serials - Prediction Pattern Change can Lead to Odd Behavior in "Predict New Issues" Dialog

Bug #1797452 reported by John Amundson
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

I'm filing this bug as an offshoot of bug 1745427, (https://bugs.launchpad.net/evergreen/+bug/1745427/comments/4),

Also see related bug 1745425.

The Predict New Issues dialog in the Serials function can exhibit odd behavior after a Prediction Change...

1. After a prediction change, the Predict New Issues window will reflect the new pattern and will accept new enumeration/chronology captions, BUT if the publication date is adjusted, the prediction fails silently. (the failure produces the attached console error). This means the user will have to either adjust the holdings code of the most recent issue to produce the correct publication date or predict more and then delete until the correct set of issues/dates is present.

2. When Edit issue holdings codes is chosen on an issue using an old pattern, the Predict New Issues screen does not reflect the new pattern, (this can still be changed by moving the type from supplement back to basic). These leads the user into thinking the issue will maintain the old pattern with new values. However, if the type isn't changed and the code edited, the resulting issue is a weird amalgamation of the two patterns.

Here is the current workflow I've been suggesting to our libraries until this is fixed:

1. Delete all expected issues created using the old prediction pattern that will never be received.
To do this, from the Manage Issues tab, checkmark the issue(s) to delete, go to Actions, and
select Delete Items.
2. Click on Predict New Issues from either Manage Issues tab or next to the active prediction
pattern under Manage Predictions. A Predict New Issues dialog box will appear.
3. Adjust the Enumeration Labels as needed
4. Determine if the Publication Date or Chronology Labels need to be adjusted.
a. If they look good, leave them alone and enter the desired Prediction Count. Click Save.
b. If they need to be adjusted, leave them alone for now and enter a Prediction Count of 1.
Click Save. Once the issue has been predicted, highlight it and go to Actions>Edit Issue
Holdings Code. Adjust the Publication Date, Enumeration Labels, and Chronology
Labels as needed. Click Save. Next click Predict New Issues again. Ignore all the values
and simply enter in the desired Prediction Count. Click Save.
5. Your issues should now be predicted using the new pattern.

Tags: serials
Revision history for this message
John Amundson (jamundson) wrote :
tags: removed: webstaffclient
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.