Hello,

I am also unfortunately not able to reproduce this problem on 2.2.  If anyone 
can reproduce this, could you please post both your pattern code and also the 
holding code of your starter, along with your exact Evergreen version?

Thanks,
Dan

-- 
*********************************************************************************
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133


>>> On 5/3/2012 at 10:05 AM, Erhan Tuskan <e...@iisg.nl> wrote:
> Which version do you use? I tried both patterns of you in version 2_0_3 and 
> they work without any problem, giving the same predictions.
> 
> At the IISH we have the following pattern for an incrementing annual, using 
> number instead of volume:
> ["2","0","8","1","a","no.","u","1","i","(year)","w","a","x","01"]
> 
> And the calendar changes have indeed no influence.
> 
> Erhan Tuskan
> IISH
> 
> -----Original Message-----
> From: open-ils-general-boun...@list.georgialibraries.org 
> [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
> David Fiander
> Sent: donderdag 3 mei 2012 3:29
> To: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] Prediction pattern for annual serial
> 
> It's probably an odd boundary condition. Because every issue arrives in 
> January, the month never actually "changes".
> 
> - David
> 
> On Thu, May 3, 2012 at 9:15 AM, Kathy Lussier <kluss...@masslnc.org> wrote:
>> Hi all,
>>
>> I have a question about a serials prediction pattern that seems like 
>> it should have been fairly straightforward, but took some time to get 
>> the volumes to increment correctly.
>>
>> The prediction pattern is for an annual serial where the volume should 
>> be incrementing every year. The example I was using was for the 
>> Journal of Hellenic Studies. When I was first setting up the 
>> prediction pattern through the alternate serial control view, I did the 
> following:
>>
>> *I added a first level enumeration for v.
>> *I selected the option to use calendar changes and identified the 
>> start of January as the time when the first-level enumeration should change.
>> * I selected year for the caption
>> * I selected annual as the frequency
>>
>> The resulting prediction pattern was:
>> ["2","0","8","1","a","v.","i","(year)","w","a","x","01"]
>>
>> I then set up my first issuance with a volume number of 10, but when I 
>> generated the predictions, the volumes didn't increment.
>>
>> We ultimately were able to get the volumes to increment correctly by 
>> de-selecting the option to use calendar changes, which resulted in the 
>> following prediction pattern:
>>
>> ["2","0","8","1","a","v.","i","(year)","w","a"]
>>
>> I'm happy we got this pattern working correctly, but I'm still curious 
>> as to why the calendar change option does not work in this situation.
>>
>> Thanks for any insight you can provide!
>>
>> Kathy
>>
>>
>>
>> --
>> Kathy Lussier
>> Project Coordinator
>> Massachusetts Library Network Cooperative
>> (508) 756-0172
>> (508) 755-3721 (fax)
>> kluss...@masslnc.org 
>> Twitter: http://www.twitter.com/kmlussier

Reply via email to