Folgerpedia:Manual of Style/Cataloging

This article elaborates on the Folgerpedia Manual of Style for articles about cataloging and metadata topics. Anything not covered here defaults there.

Style

Prefer imperative language when giving instructions. For example, "Make a note" instead of "A note should be made."
Avoid unnecessary catalogerese. These articles are being read not only by catalogers, but by non-specialists interested in cataloging.
Refer to staff by role or job title, not name.
Spell out abbreviations, or avoid them entirely. Use "for example" and "that is" instead of the Latin abbreviations e.g. and i.e.
Use preformatted text for examples.

Terminology

Use call number instead of shelfmark.
Hamnet refers to public-facing MARC records. Prefer "Hamnet" if the context encompasses both public and cataloger information.
Voyager refers to the ILS as a whole. Prefer "Voyager" when talking about the settings and capabilities of the software.
Use "At the Folger ..." to distinguish local Voyager customizations.
Examples:

Multiple works bound together subsequent to publication will have multiple bibliographic records in Hamnet, one for each separate title.

Voyager indexes only 852ǂh and 852ǂi for left-anchored call number searches.

At the Folger, Voyager indexes 008 and the 046 dates in Hamnet and the staff modules.

Article titles, headings, and sections

Name articles without particular reference to cataloging. For example: Things in books. This allows an article to bring together all information about a topic, of which cataloging policy is one. If an article becomes too lengthy, cataloging policy can be separated into a subpage.
Take care to follow Folgerpedia:Manual of Style by always providing a lead section followed by a level 2 heading.

Content

Resist the temptation to arrange the instructions in full syndetic structure. Aim for only two or three levels of hierarchy. Even if the lead section is not specific to cataloging, do not create a level for "Cataloging instructions."

Formatting

Use preformatted text for examples or display of exact strings to be used. There are several ways to tag preformatted text.
Format examples so that the box aligns with the text being exemplified.
- If the text is not indented, you may either simply insert an initial blank space (easiest), or the tag for preformatted text: <pre></pre>
- If the text is indented (typically by a bullet), use a colon and the tag for preformatted text: :<pre></pre>
- If an exact string is inserted within regular text, use: <code></code>
- If inserting an example in a double bullet followed by another double bullet, use <code></code>.
Rely on the presence of preformatted text for examples instead of using the label "Examples:" if it simplifies the tagging.

Articles on MARC fields

Use the Template for MARC articles
Formulate the title by copy-and-pasting the heading from the online MARC field; leave off the "(R)" or "(NR)"
If the field exists in two or more formats and is essentially identical, enumerate all format names in the lead section using the short form. The formal and short titles of the format names are:

authority format

bibliographic format

holdings format

Begin lead section with these or similar words:

 MARC field XXX in the bibliographic format contains ...

If a field that exists in different formats has different definitions (as does 046 in authority and bibliographic formats, create separate articles. Disambiguate by putting the format in parentheses after the name of the field.
These articles integrate policy and instructions on content and mark-up; we are using the MARC field as a shortcut for the corresponding AACR2 and RDA elements.
Elements of articles on MARC fields usually include:
- A lead sentence. In general, copy the remaining part of the lead section from the Field Definition and Scope from the MARC format, truncating or editing as desired. Example: MARC field 856 in the bibliographic and holdings format contains information needed to locate and access an electronic resource. The field may be used in a bibliographic record for a resource when that resource or a subset of it is available electronically. In addition, it may be used to locate and access an electronic version of a non-electronic resource described in the bibliographic record or a related electronic resource. This field is repeatable.
- A section on "Commonly-used tags" containing the most commonly used indicators and subfields. Policy and formulation relating only to single subfields may be included in this section.
- A section on "Policy and formulation," for general policies, or those that cover more than one subfield.
- Folger policy statements, style, and interpretations of cataloging instructions, but, in general, not basic cataloging instruction itself; compare to LCC/PC Policy Statements
External links.
- Authority format: to the MARC 21 Format for Authority Data link at loc.gov, to the corresponding authority format link in Cataloger's Desktop, and to the Descriptive Cataloging Manual–Public Sections link in Cataloger's Desktop.
- Bibliographic format: to the MARC 21 Format for Bibliographic Data link at loc.gov, to the corresponding bibliographic format link in Cataloger's Desktop, and to the OCLC MARC guide for the tag.
- Holdings format: to the MARC 21 Format for Holdings Data link at loc.gov.
Generally, use a double dagger (ǂ) for subfield delimiters. If providing preformatted text appropriate for use in a catalog record, format for copy-and-paste according to Connexion or Voyager, depending on where the text is expected to be used.

Advisory statements

Advisory statements come first on a page, preceding the lead section.

Use {{Draft}} when creating a new article from scratch or one combining information from several sources is in process. Use sparingly; remove when the article is substantially usable, even if not complete.
Use {{Draft-section}} when the statement applies only to one or more sections in an article.
Use {{Legacy}} when copying and pasting from Bard pages or other sources and there's uncertainty about whether the instructions are current and authoritative.
Use {{Legacy-section}} when the statement applies only to one or more sections in an article.
Use {{Outdated}} when copying and pasting from Bard pages or other sources and it's known that some of the content is obsolete.
Use {{Outdated-section}} when the statement applies only to one or more sections in an article.
Use {{Incomplete}} for articles that are meant to cover a broad area, but the current content covers only a very narrow area.
Use {{Incomplete-section}} when the statement applies only to one or more sections in an article.

Redirects

When moving (renaming) a page, the system defaults to creating a redirect. Retain the redirect, even if the change was as minor as different capitalization. This will preserve linkage to the moved article that exist in other pages.

External links

Add "External links" as the final section of an article.
Add a link to the MARC field for all MARC-based articles.
Other external links may be added if particularly helpful, such as LC or OCLC.

Talk page

Create a talk page for every article populated by migrated material.
Name the first section "Origin of page" and give links to original pages.
Create a new section for every distinct issue or query; new sections go at the bottom.
Add discussion text within migrated pages to the talk page with a "needs discussion" link on the main page.
Once the issue is resolved, strike through the text.