Patterns: Key Facts

note: Vanderbilt is not using the 853/863 holdings fields or the "Automatically update using control info" option on the SCR

Numeration Only
	A numeration-only pattern will duplicate the numeration information
	in the name field -- ignore for purposes of checkin as checkin 
	records alone do not display to the public.  Numeration Only will 
	correctly display in the paired 853/863 fields (if used).

Numeration and Year Only
	Sirsi adds these patterns to an 866 field which does not collapse 
	correctly unless the 866 field is manually updated/created each 
	time an issue is received.   
	
	This pattern can be made to work correctly with an 863 that 
	collapses if a |i(year) is added to the 853 field before any 
	issues are received and the "Automatically update using 
	control info" option is set to Y). 863’s will then be generated 
	for each checkin automatically, but the |i and year will have to 
	be manually added each time an issue is received.

Date Only-- Using "Dummy"  Numbers
	Acorn generally does not accept patterns with only a date and no 
	enumeration. This means that a number must be supplied when 
	creating the pattern in order to generate checkins. Ignore the 
	"fake" numbering for purposes of checkin; set the "Automatically
	update using control info" option to N. Holdings (866 fields) 
	must be	updated/created manually. When claiming, edit the checkin 
	record to remove the artificially-supplied number.

Custom patterns:
	Custom patterns are essentially  free-text fields. Up to 12 custom 
	names may be entered. Input in the order in which the data cycles 
	through the pattern. Separate each name by a comma.  

		For example:  SPR, SUM, FALL, WIN
		
	866 fields will have to be manually created/updated when using the 
	Custom function.  The system cannot read custom data for purposes 
	of creating holdings, when the "Automatically update using control 
	info" option is selected. In some instances the 853/863 fields can 
	be edited to produce the desired holdings display.


Future checkin name:
	For seasons, use  WIN, SPR, SUM, FALL with no periods.	
	For  months, use 3 letter abbreviations with no periods: JAN, FEB, 
	etc. For patterns that use month, day, and year,  use 3 letter 
	abbreviations with no periods for the month, the date followed by a 
	comma, and the year: JUL 1, 1996, etc.
	
	Season assumes that the volume begins with the winter issue 
	and ends with the fall issue. For other patterns, use Custom.

	Bimonthly assumes a pattern of JAN/FEB, MAR/APR, etc. If 
	       the title is published in another pattern, i.e. FEB/MAR, 
	       APR/MAY, etc. use Custom.

Patterns without captions 
	Patterns without captions (labels in Acorn) may show a period 
	preceding the enumeration in the public display. To correct the 
	display, edit the 853 field by supplying a label in parenthesis 
	in the 853 field: |a(no.)

Patterns with Skipped Issues
	If a title regularly skips certain issues, generate the pattern 
	for the frequency type, but remove x’s from the calendar when the 
	journal is not published.  For example, with a monthly journal that 
	is not published during summer months, remove x’s from the calendar 
	for the months that the journal is not published (June, July, and 
	August).  Make sure to remove the x’s before checkin records are 
	created, or individual checkin records will have to be removed with 
	REMOVE CHECKIN.  

	If the publisher skips an issue (irregularly) but numbers the 
	skipped issue into the regular numbering, DO NOT EDIT CALENDAR 
	because this will edit the pattern.  Rather, edit the checkin 
	record.  Use DISPLAY 1 CHECKIN to find the specific record you 
	wish to remove, touch the record with your mouse, and Acorn 
	remembers the record.  Select REMOVE CHECKIN to remove the 
	specific issue which will not be published.