When the "Name of Season" formatting is used, any text put in front of the season is erased from the numbering pattern. This does not seem to affect the "Name of Day" or "Name of Month" formatting options. To test: 1) Go into Serials > Manage Numbering Patterns. 2) Select edit for the "Seasonal" numbering pattern included in the default installation of Koha. 3) Type 'TEST' in front of the numbering formula, so that it reads 'TEST {X} {Y}'. 4) Make sure the X value uses the "Name of Season" formatting. 5) Create a test prediction pattern. 6) Notice that the string "TEST" is erased from the front of the prediction pattern. You will see that anything put in front of the season is erased. If you put a variable like X, Y or Z in front of the pattern, that variable will be erased as well. 7) Change the numbering formula to '{X} TEST {Y}" 8) Create a test prediction pattern. 9) Notice that so long as data is behind the "Name of Season" formatting, it will still display.
Karl, It seems to work (using master): TEST Spring 0 03/05/2016 TEST Summer 0 03/05/2016 TEST Fall 0 04/05/2016 TEST Winter 0 04/05/2016 TEST Spring 1 05/05/2016 TEST Summer 1 05/05/2016 TEST Fall 1 06/05/2016 TEST Winter 1 06/05/2016 On which version of Koha are you testing?
I first noticed it on our institution's install of Koha, which is 3.20. I've tested it just now on ByWater's demo site at intranet.bywatersolutions.com and it also seems to hold true there too. Finally, I've tested it on our test server, which is on master. It also occurs there, though I'm not entirely confident that the test server is set up completely right.
Maybe bug 13877 very recently pushed to master fixed this? It could explain the difference you see in testing.
(In reply to Katrin Fischer from comment #3) > Maybe bug 13877 very recently pushed to master fixed this? It could explain > the difference you see in testing. Good catch Katrin, you must be right.
It seems like this issue is resolved on our machines by the update. I think this was resolved by the bug fix you mentioned. Karl
*** This bug has been marked as a duplicate of bug 13877 ***