• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
For ABC50 ADM record #1829259, item records are displaying out of enumeration order (i.e.):

v.3:no.2(2005:Fall)
v.4:no.1(2006:Spring)
v.3:no.3(2005:Winter)
v.4:no.2(2006:Summer)
v.5:no.1(2007:Spring)
v.5:no.2(2007:Summer)
v.5:no.3(2007:Fall)
v.5:no.4(2007:Winter)
v.4:no.3(2006:Fall)
v.6:no.1(2008:Spring)
v.6:no.2(2008:Summer)
v.6:no.3(2008:Fall)
v.6:no.4(2008:Winter)

Resolution:
Column 3 in the abc50 tab_z30_sort specifies the sort which is going to be used for Issue items.
We see the following values in this column:

00, 01, and 02.

Looking at the "sort identifiers for ISS.. 'issue' items" (near the top of the tab_z30_sort header), we see that Issue sort's 00, 01, and 02 all have z30_chronological_i as their highest-level element, followed by z30_enumeration_a and z30_enumeration_b. (z30_description and z30_chronological_j are not used for these three Issue Sort Identifiers.)


Below are z30 fields for each of these issues. The top line is the z30_description (what you show in your problem description). And, in the line below that,

the first number is the z30_chronological_i;
the second, the z30_enumeration_a;
the third, the z30_enumeration_b; and
the fourth, the z30_chronological_j (the season).

For instance, for z30_description "v.3:no.2(2005:Fall)" we see:

v.3:no.2(2005:Fall)
2006 3 2 23

The second line represents the following values:

04 chronological_i .........2006
04 enumeration_a ...........3
04 enumeration_b ...........2
04 chronological_j .........23


v.4:no.1(2006:Spring)
2006 4 1 21

v.3:no.3(2005:Winter)
2007 3 3 24

v.4:no.2(2006:Fall)
2007 4 2 23

v.5:no.1(2007:Spring)
2007 5 1 21

v.5:no.2(2007:Summer)
2007 5 2 22

v.5:no.3(2007:Autumn)
2007 5 3 23

v.5:no.4(2007:Winter)
2007 5 4 24

v.4:no.3(2006:Winter)
2008 4 3 24

v.6:no.1(2008:Spring)
2008 6 1 21

v.6:no.2(2008:Summer)
2008 6 2 22

v.6:no.3(2008:Autumn)
2008 6 3 23

v.6:no.4(2008:Winter)
2008 6 4 24

Thus, the reason that v.3, no.3 appears after v.4, no.1, is that the z30_chronological_i is "2007"; the reason that v.4, no.3 appears after v.5, no.4 is that the z30_chronological_i is "2008"; etc.

To correct this, you simply need to change the z30_chronological_i to the correct year (as seen in the z30_description).

It *seems* that this problem is no longer happening -- since we see that all four 2008 issues have been received and are all in order. Thus, it seems the pattern is currently working correctly.


(SKB 5533, which describes how to handle the case where "Winter" -- which is usually the last issue of the year -- is instead the first issue of the year, is *not* relevant in this case, but could be in certain others....)

• Article last edited: 10/8/2013