Comment 5 for bug 1745425

I just experienced the same as Irene (comment #4) on our 3.9.4 system. I was attempting to change the pattern for a publication that changed from bimonthly to quarterly using seasons (some quarterly titles use months for their enumerations). Even though the pattern it was predicting was created with, and displaying YEAR Season, it predicted YEAR Month issues instead.

I had created the pattern with a template, so I assumed I'd accidentally chosen the wrong template, using one that makes Quarterly with months instead of Quarterly with seasons, so I went in and edited the pattern to use seasons, saved it, and predicted the issues again. After 3 tries I deleted the whole pattern and started over, but got the same results.

My only option was to predict the first one, edit issue holding codes to display the proper YEAR Season, and then predict the future issues from there.

I can add a further complication with this, that Evergreen doesn't allow you to choose when you want to start your issues. The title in question was bimonthly, and had already had an Oct. 2023 issue several months ago. The new issue, first as a quarterly, is Fall 2023. I began by deleting the pending Dec. 2023 issue that will never be published and deactivating the bimonthly pattern. Created the new pattern and predicted the issues. When predicting, I changed the Predict New Issues: Initial Values to October 21, 2023, which caused it to display an 2023 Autumn enumeration to predict. Despite the fact that Evergreen only recognizes Winter as being in December, never January (some quarterly titles begin their year with Winter, not end it) Evergreen predicted a Jan. 2024 issue over and over. If Evergreen had been following the previous pattern (which is not active), it would have predicted a December or February issue.