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

Description:
We were amending a quarterly publication pattern: 03,06,09,12. We made the expected date 31/03/2006, but when viewing the range of dates in the expected screen, got the 31st for each month i.e. 03/31/06, 06/31/06, 09/31/06 and 12/31/06. On changing it to 03/28/06 the expected dates all rolled out at the correct date for the month 03/28, 06/28, etc.

It seems that Aleph is not recognising that an end of month date can be 31st or 30th (or indeed 28th.)

Resolution:
This occurs when no second level chronology defined, that is, no subfield j in 853 and 853X.

On testing, we found the following:

where $j present, but no $y, this produced expected date

20060331
20060630
20060930
20061230

where $j not present with $y this produced the problem results in the above example.

The only way of getting correct dates, without any $j, is entering the dates in $y as follows:

853 L $$av.$$bno.$$u4$$vr$$i(year)$$wq$$ypd0331,0630,0930,1231
853X L $$900001$$a2$$b1$$i2006$$320060331

This is recognized as a bug, but since fixing it might have negative side-effects, it is not planned.

• Article last edited: 10/8/2013