One of the core strengths of libraries is shared standards and sharing library data. Since we migrated to Evergreen in May I’ve been doing migration cleanup, implementing acquisitions and trying to figure out serials. Setting up serial prediction patterns is ugly in any ILS because prediction patterns are ugly.
There’s a great opportunity for the open source ILS world (both the Koha and Evergreen) communities to develop a standard so that libraries using these systems can save time and money by sharing serial prediction patterns. As more academic libraries are considering migrating to Evergreen, this would also help remove a barrier to selecting Evergreen. While it’s painful and annoying for me to manually set up all of our serial prediction patterns, I work in a small library, so it’s still possible. There’s only about 150. For a large university library it would not be possible set up a prediction pattern for each title.
Examples of serial prediction patterns
Can you guess what these prediction patterns describe?
- Published Monday , Saturday, except for Christmas Day. Issues are identified by date. (daily newspaper in most cities)
- Published weekly on Thursday, except for a double issue in the last two weeks of December. Issues are numbered continuously and four volumes are published annually, starting in Jan, Apr, Jul, Oct (The Economist)
- Published twice monthly, except monthly in Jan, Jul, Aug, Dec. Issue numbers restart in each volume, which starts in Jan (Library Journal)
None of these are terribly complicated and yet they are still pretty messy. Thanks to David Fiander for letting me pinch these examples from his slides.
What’s a serial prediction pattern? Who cares?
Scholarly journals/magazines/periodicals/newspapers are published on different schedules. For example, some are published weekly, monthly, bimonthly, quarterly or yearly. There are also cataloguing codes for semiregularly, 3 times a year, biennial, triennial, and completely irregular.
In academic libraries it’s important to know if the library has a specific issue of a title, as users are most often looking for a specific article in a specific issue of a title. Generally, in public libraries this level of detail is not necessary. However, if libraries shared these prediction patterns perhaps more public libraries might use them.
Prediction patterns are also used to figure out which issues of a title should have arrived but haven’t. Libraries can then claim the missing issues with the vendor or directly with the publisher. (As an aside, I think journal claiming is a silly process that involves a lot of correspondence that doesn’t often end up in the issue being replaced. Some libraries are giving up on claiming for each issue.) Still, it’s important for both the user and the library to know which issues are missing in a run.
If serial prediction patterns interests you I highly recommend watching David’s webinar from 2009 on this topic.
What’s information is included in a serial prediction pattern?
There’s a bunch of information in a MFHD record, namely:
- Hierarchy of enumeration, for example volume, issue, number, part (can have up to 6 levels in the hierarchy)
- Does the numbering restart? If so, when?
- How often does the title come? weekly? monthly? 4 times a year?
- Are there exceptions to this pattern? If so, what are they?
Pattern (both publication and enumeration)
- When is the journal published?
- What publications will be omitted?
- What issues will be combined?
I’m not really sure what the next steps are. I think the open source ILS communities are best positioned to tackle this and figure out a standard way of sharing prediction patterns. We might want to talk to serials and cataloguing experts, like perhaps the folks at CONSER or NASIG. Perhaps it would be useful to talk to folks at OCLC or NISO. We might want to look outside the libraryland–what other industries are sharing information about odd, picky, sometimes irregular patterns? How are they doing things and what can we learn?
I’ll be presenting on this topic at the Evergreen conference next week and want to explore some next steps with people. I’ll be copresenting with Grace Dunbar and Mike Rylander from Equinox Software on Resource Sharing in Evergreen on Friday, April 27th from 3-4pm