LC-PCC policy statements for special issue

LC Core for serial relationships.

LC/PCC practice for special issues to other serials: If the special issue has its own title and specific contents, and is not numbered with the main serial, consider treating it as a monograph. Create a separate work for a special issue to a serial if the issue does not update that related serial and carries its own designation system that is distinct and independent from that used by the related serial.

In addition, provide an authorized access point for the related serial unless the special issue has a common title that is identical to the title proper of the related serial. Serial special issues that are not cataloged separately should be noted on the metadata description sets for the base serial, unless they are included in the general numbering for the serial. Provide access points for the special issue whenever the titles are distinctive.

See instructions below and refer to the Metadata Guidance documents on Descriptive Relationships on how to relate the works.

LC/PCC practice: See the Metadata Guidance documentation: Descriptive Relationship elements and Relationship labels.

LC/PCC practice: Optionally, apply the instruction using a note.

LC/PCC practice: Record the element using a structured description. If possible, express the relationship using a relationship label, or a relationship label in combination with an identifier or IRI, as allowed by the metadata management system. Apply this policy statement when recording: 1) an authorized access point in a bibliographic record, 2) an authorized access point for a related entity in an authority record, or 3) a structured value that is not functioning as an access point. If the metadata management system does not permit recording a relationship label for the element, omit it.

LC/PCC practice: Apply the instruction. In most cases, give serial relationships as reciprocal relationships. See further instructions in the Metadata Guidance documentation on how to relate the works.