The pattern wizard may not match what the underlying prediction code can actually do in that case. It's likely (but I haven't tested) that the prediction code doesn't know how to make combination issues of more than two units.
There might be a plausible workaround: you could have a combined issue for 06/07, and an omitted issue for 08. If that works, you would probably still want to edit the "June/July" label by hand to read "June/July/August" for the generated issues, but unless you subscribe to a lot of publications using this or similar patterns, at least there won't be many such issues to edit. Hope this helps. Lebbeous On Mon, Jun 17, 2013 at 3:38 PM, Kate Butler <[email protected]> wrote: > We recently went live with Evergreen (2.4) and I’ve been working on entering > our periodical information into the serials module. > > > > I’ve been running into a problem when I try to enter a pattern where three > months or days are combined. (Such as June/July/August as a single issue.) > The pattern wizard creates the code fine, but when you generate the > predictions it combines the first two dates and gives the third its own > issue. > > > > It’s easy enough to work around this by omitting one of the three, but I > wondered if there was another way to get this to work. > > > > Ex pattern: > > ["0","0","8","1","a","Vol. ","b","No. > ","u","8","v","r","i","(year)","j","(month)","w","m","x","01","y","cm02/03","y","cm04/05","y","cm06/07/08"] > > > > Kate Butler > > Technology Librarian > > Rodgers Memorial Library (Hudson, NH) > > http://www.rodgerslibrary.org/ -- Lebbeous Fogle-Weekley | Software Developer | Equinox Software, Inc. / The Open Source Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
