FAQs: Creating and Modifying Publication Patterns

Each pattern that is available from the Replace Patterns helper is based upon a particular Frequency Code, such as the one used in the MARC fixed field. The Publication Cycle and Chronology Type values that appear either by default or when a particular pattern is selected from the Replace Patterns helper, are compatible with that frequency. The template serves as a basic starting point for creating an accurate prediction for a particular serial control record. After selecting a pattern, modifications may be made to either the Chronology Type or the Publication Cycle to customize the control for that serial. However, the Publication Cycle and Chronology Type must have values compatible with the frequency. If no appropriate Chronology Type exists, a new one may be defined in the Chronology Type policy in Serial Control Configuration. If the Chronology Type is not appropriate, predictions cannot be created, and the following message will appear.

Chronology does not match chronology pattern

How do I copy a non-standard pattern that is used often in my library?

Click the Patterns tab when modifying or creating a serial control.

Review the publication cycle by clicking the Publication Cycle gadget and clicking OK.

Click the Replace Patterns helper and find the standard pattern closest to the one you need.

Under Chronology Pattern, customize the pattern.

Use the Publication Cycle gadget to customize the cycle.

The chronology pattern you select must correspond appropriately to the publication cycle selected. Additional pattern information may be created using Serial Pattern Policy wizard.

What if there is no predefined publication pattern to fit the frequency I need to predict?

Select a frequency that will predict more issues than you need. Then use the Omit button to omit unneeded issues. This strategy typically requires less manipulation of the control record at the time of prediction because you won’t need to reset the values for enumeration, chronology, date first prediction, and date expected.

How do I create predictions that use chronology instead of enumeration?

Click either the Create Serial Control or the Modify Serial Control wizard, and click the control’s Patterns tab.

If the chronology type and publication cycle are not already defined, click the Replace Patterns helper and set up a pattern, making necessary modifications.

Under Enumeration Pattern, clear any check boxes in the Use column.

On the OPAC Display tab, click Chronology as the Form of Name to Display in the catalog.

Click the Generate Predictions tool.

If the next issue’s chronology is not already defined, type it using the appropriate format and click OK.

Issues with chronology as the only enumeration will appear for confirmation. You may save or redo the prediction, change the pattern, or go back to the serial record.

How do I predict a title with enumeration and no chronology?

Click the Patterns tab, and under Enumeration Pattern, type values in the text boxes as needed.

Under Chronology Pattern, in the Chronology Type box, select Numeration from the list.

Click the OPAC Display tab, and click Enumeration as the Form of Name to Display in the catalog.

How do I predict a title with continuous numbering?

When a serial control pattern uses a continuous numbering scheme on the second level of numeration, the first level of enumeration may not increment as expected.

For example, the library receives a title with a monthly frequency. The enumeration pattern uses a volume and number, and the numbering is continuous. After 12 issues, the volume should increase. Therefore, under Enumeration Pattern on the Patterns tab, there will be two levels of enumeration, V. and NO. The NO. level will be selected as continuous with a limit of 12. The first issue predicted will be V. 22 NO 30, OCT 2003. When creating the predictions, you might expect the volume to increase on the January issue. When creating the predictions, however, it won’t. The volume increases on the May 2004 issue.

Enumeration	Chronology	Date Expected
V. 22 NO. 30	OCT 2003	10/1/2003
V. 22 NO. 31	NOV 2003	11/1/2003
V. 22 NO. 32	DEC 2003	12/1/2003
V. 22 NO. 33	JAN 2004	1/1/2004
V. 22 NO. 34	FEB 2004	2/1/2004
V. 22 NO. 35	MAR 2004	3/1/2004
V. 22 NO. 36	APR 2004	4/1/2004
V. 23 NO. 37	MAY 2004	5/1/2004
V. 23 NO. 38	JUN 2004	6/1/2004
V. 23 NO. 39	JUL 2004	7/1/2004

SirsiDynix Symphony increases the volume when it can evenly divide the limit on the NO. level of enumeration into the number of the issue. When the predictions are generated, the APR 2004 issue will have an enumeration of V. 22 NO 36. On the Patterns tab of the control record, the limit for the NO. level of enumeration is 12, which can evenly divide into the NO. 36. Therefore, the volume increased on the May 2004 issue. Do not be concerned that SirsiDynix Symphony does this. It is okay to predict a small number of expected issues, then manually increment the volume.

Creating a Control with One Level of Enumeration

To create a serial control record with one level of enumeration, do the following.

Click the Create Serial Control wizard.

Under Library for New Control, select the new control library from the Library list. In the Holding Code box, select the default holding code for this library from the list. Click OK.

In the Select a Pattern Template window, select a publication frequency template for this title, and click OK.

Click the Patterns tab, and select the Use check box for the first level. Verify that no other Use check boxes are selected.

Type a Label or use the gadget to select the appropriate label. For this example, type NO.

Click Create Control.

The Get Expected Issue Info window appears, where you can create predictions for these issues. Type the number of Preview Expected Issues.

Type the number that the serial starts with in the NO. box.

Type the Chronology.

Type the Date Expected and Date First Prediction, or use the gadgets.

Click Generate Predictions.

Even when the year changes, the enumeration continues to increment by one. You can also have continuous numbering for issues that have a volume and number associated with them.

Creating a Control with Two Levels of Enumeration

To create a serial control record with two levels of numeration, do the following.

Click the Create Serial Control wizard.

Under Library for New Control, select the new control library from the Library list. In the Holding Code box, select the default holding code for this library from the list. Click OK.

In the Select a Pattern Template window, select a publication frequency template for this title, and click OK.

On the Patterns tab, select the Use check boxes for the first two levels.

Type a Label for each level, or use the gadget to select the appropriate labels. For this example, use V. and NO.

Select the Continuous check box for the second label.

Type the number of issues to limit this enumeration in the Limit box.

Click Create Control.

The Get Expected Issue Info window appears, where you can create predictions for these issues. Type the number of Preview Expected Issues.

Type the number that the serial starts with in the V. and NO. boxes.

Type the Chronology.

Type the Date Expected and Date First Prediction, or use the gadgets.

Click Generate Predictions.

The enumeration NO. continues to increment by one while the volume changes when the limit is reached (in many cases, the new year issue). If this volume change is inappropriate, generate a smaller number of predictions to preview, then adjust the enumeration.

How do I set up a pattern that comes out twice a month except for May and October, which have three issues?

Click the Replace Patterns helper and select the 3INMONTH pattern template.

Keep the default Chronology Type of DATE.

Click the Publication Cycle gadget. The dates that are used will be the 1st, 15th, and 28th of each month. If the dates specified in the publication are not these dates, click each selected date to unselect it. Click the three dates specified. The third date is the extra date that the issue is published in May and October.

Click Omit.

Click Date. A list of the months and days published appears. Click on the date that the extra issue is published for each month except May and October.

Click OK through the final display of the Publication Cycle gadget.

Click Save Changes and click More Changes.

Click the Generate Predictions for Expected Issues helper. Preview 26 expected issues for the first year by typing the current enumeration, chronology (in DATE format), and dates published and expected.

Save or Redo the prediction, or change the pattern.

If the DATE Chronology Type is inappropriate, a new one may need to be created using the Serial Chronology Type Policy wizard.

For example, the following Date Omit Cycle window displays date omission for an issue published the 2nd and 16th, with extras on the 30th of May and Oct.

How do I set up a pattern that has four issues per month, two issues on the 1st and two issues on the 15th?

Click the Replace Patterns helper, and select the SEMIMONTH pattern template. The default Chronology Type is DATE.

Use the Publication Cycle gadget to confirm that the issue will be published 1st and 15th of every month. Click OK through the final display of the Publication Cycle gadget.

Click Create Control, or click Save Your Changes, then More Changes.

Click the Generate Predictions or Generate Predictions for Expected Issues helper. Preview issues for the first year by typing the current enumeration, chronology (in DATE format), and dates published and expected.

Save or Redo the prediction, or change the pattern.

This is the basic format. You may continue with one of the following options:

•

If the enumeration is the same on both issues published on the same day, you may generate another batch of prediction records using the same control record and exactly the same first issue prediction information. Make sure that the dates published and expected are the same to ensure that the issues are presented in the appropriate order for display and receipt.

•

If the enumeration is not the same on both issues published on the same day, you may use the Create Serial Control wizard to duplicate the control. The control will be exactly the same as the first option, but you may indicate the difference in the enumeration section of the control. MARC holdings, routing lists, and order information must be maintained in duplicate.

I have a publication with two levels of enumeration, and the second level is continuous. What controls when the volume number in the first level changes?

SirsiDynix Symphony assumes that for the life of the publication, the volume number has always changed every time the continuous number is evenly divisible by the limit. If this is not the case, do the following:

•

Consider choosing a limit that is high enough to prevent SirsiDynix Symphony from incrementing the volume prematurely.

•

Predict all of the issues in the current volume, then increment the volume number manually.

How do I deal with a title that has a predictable combined enumeration?

SirsiDynix Symphony cannot predict combined enumerations. In this instance, do the following:

•

Predict issues as though the issues are not combined.

•

Either remove one of the predicted issues and modify the other to create a combined enumeration, or combine issues at check in.

How do I deal with predictable special issues and supplements?

Make one of the following decisions for each title:

•

If you would like to be able to claim the special issue or supplement, use the Modify Serial Control wizard, and on the Expected tab, click Create Prediction, and type the Predicted Issue Information.

•

If you don’t want to claim the extra issues, use the Check In Issues of a Serial wizard, and click Check In Without Prediction to check in these special issues.

What values are important to enter in a prediction record for special issues and supplements?

The following values are important for special issues and supplements.

•

Enumeration Pattern

•

Chronology Pattern

•

Date to Claim

Select a Date to Claim that will generate a claim after an appropriate interval.

When creating an enumeration and chronology, do one of the following:

•

Type a specific enumeration and chronology. You will need to create a new prediction each time you receive issues.

•

Type a pattern such as v.XX Spec Issue and MM DD YYYY. You will replace the pattern with the proper enumeration and chronology from the issue at receiving. After receiving, your original pattern prediction record will remain; you will need to edit the Date to Claim in your pattern prediction record after each receipt.

Should I try to predict irregular issues?

Do you want a periodic claim reminder?

•

If you don’t need a periodic claim reminder for the title, then check in issues with a prediction as they are received.

•

If you need a periodic claim reminder for the title, use the Modify Serial Control wizard, click the Expected Tab, and click the Create Prediction tool, and type the predicted issue information.

What values are important to enter in a prediction record for irregular issues?

The following values are important for irregular issues.

•

Type an Enumeration Pattern and Chronology Pattern.

•

Select a Date to Claim that will generate a claim after an appropriate interval.

When creating an enumeration and chronology, do one of the following.

•

Type a specific enumeration and chronology. You will need to create a new prediction each time you receive issues.

•

Type an enumeration and chronology such as v.XX no.XXX and MM DD YYYY.

You will replace the pattern with the proper enumeration and chronology from the issue at receiving. After receiving, your original “pattern” prediction record will remain; you will need to edit the Date to Claim in your pattern prediction record after each receipt.

I am unable to generate predictions for issues earlier than 1970. What can I do to reflect historical holdings for pre-1970 issues?

You cannot generate predictions that have a chronology date, date expected, and date first prediction earlier than 1970. SirsiDynix Symphony will display an appropriate error message indicating that you are not able to create issues prior to this date. To represent historical holdings, you can do the following.

•

Update the MARC holdings record with a summary statement in the 866 tag that reflects the range of issues.

•

Do not create predictions. Instead, use the Check In Issues of a Serial wizard to receive special issues. Because you are not following a pattern when you use the special issue work flow, you are able to avoid the pre-1970 date limitation, and you can receive an issue with any date in the Chronology field.