Web Client: Serials - Pattern Wizard does not work when using specific dates for regularity

[John Amundson]

Evergreen 3.0.8.

The final step to the serial Pattern Wizard in both the xul and web clients is to add any regularity information your subscription may have.

In most of my testing, the web client wizard works as intended. However, there does seem to be one area not working. When including specific dates to publish or omit, the web client wizard does not create a working code.

For example, here is a comparison of two codes. The first one was created in the xul client and the second one was created in the web client. In both cases, I have chosen a completely irregular schedule where the only published issues are January 15, April 4, and August 12.

Xul client code:
["0","0","8","1","a","v.","b","no.","u","var","v","r","i","(year)","j","(month)","k","(day)","w","x","x","01","y","pd0115,0304,0812"]

Web client code:
["3","0","8",0,"a","v.","b","no.","u","var","v","r","i","(year)","j","(month)","k","(day)","w","x","x","01","y","pd,,"]

Notice how the information filled in after "pd" includes date criteria in the xul client code but is blank in the web client code.

I've attached a screenshot of what the differences look like when using one wizard over the other.

The top left image is what the Regularity screen looks like during the initial creation of the pattern in the xul client. The top right image is what the same pattern looks like when choosing to "edit" it in the web client.

The bottom left image is what the Regularity screen looks like during the initial creation of the pattern in the web client, and the bottom right is what same pattern looks like when choosing to "edit" it in the web client.

Some things to note: After the correct pattern is created in the xul client, it can still be used to predict issues in the web client. Even though the "Visualization" of the xul code's regularity information appears incorrect in the web client, the code itself continues to work.

It should not be necessary to use the xul client to create a working pattern with specific date regularity.

[Chrisy Schroth (cschroth)]

I can confirm this in Evergreen 3-4-5. I no longer have access to XUL, so there are many patterns I can no longer create.

In addition to the blank "pd,," information, I can also add that in the Specific Regularity Information, if you try something like Omit Week of specific month, while XUL created a functioning pattern, the web client creates your week and month backwards, creating an invalid pattern. I'll attach an image of a magazine that publishes every 3 weeks. The first column was created in the web client, the functioning pattern in the second column in XUL before we migrated. The difference is pretty clear.

[Beth Willis (willis-a)]

Confirming that this is still an issue in 3.10.3

I created a pattern using only specific publication dates but, instead of selecting the “Completely Irregular” as the pattern type, I chose “Use number of issues per year”

The resulting code was as follows:
["2","0","8",0,"a","(year)","b","(month)","c","(day)","w",4,"y","pd","y","pd","y","pd","y","pd"]

I was able to predict only the first issue.

It is not possible to edit the prediction pattern.

I created another prediction pattern, selecting the same options except that I chose the "Completely Irregular" pattern type.

The resulting code was as follows::
["2","0","8",0,"a","(year)","b","(month)","c","(day)","w","x","y","pd","y","pd","y","pd","y","pd"]

Again, I was able to predict only the first issue. Attempting to predict additional issues failed.

In this case, when I chose to edit the prediction pattern, I was able to do so but found that the selected publication dates no longer displayed.