- Article Type: General
- Product: Voyager
- Product Version: 8.2.2
Bug Report for 16384-6593
Release(s) replicated in: 7.0.3, 7.1
Server Platform(s) affected: Solaris/all
Expected Results: The second level of enumeration in a publication pattern should collapse properly.
Actual Results: If the second level of enumeration in a pub pattern is Quarterly with combined months (Jan-Mar., etc.), the combined months don’t collapse into the 86x subfields b and j.
Also, combined months in a quarterly pattern are collapsing as “seasons”. It could be that having three months combined just can’t be handled by Voyager and so they’ve chosen seasons as the best fit. (e.g. Jan-Mar = Spring)".
Workflow Implications: Confusing for operators.
In Acquisitions>Serials>New Publication Pattern, create a publication pattern that includes a second level chronology of Quarterly with combined months.
Create a serials check-in component and, on the Predictive Pattern tab in Subscription Maintenance, attach your new pub pattern to this component.
In Serials Check-In, check in several issues.
In Serials History, highlight the issues you’ve checked in and hit Collapse.
In Serials History, click on the Holdings button, select the appropriate MFHD, and click MARC to view the holdings for this serial.
You’ll note that when the 85x/86x pair was created, the 86x was created without a subfield j of the corresponding months. For example:
853: ‡8 229 ‡a v. ‡b no. ‡u 4 ‡v r ‡c issue ‡u 1 ‡v c ‡i (year) ‡j (season) ‡w q ‡x 21
863: ‡8 229.40 ‡a 1 ‡b 1-4 ‡c 1-4 ‡i 2009
Fixed in Voyager 8.2.2.
- Article last edited: 3/18/2015