Folgerpedia:Manual of Style/Cataloging: Difference between revisions

(Created page)
 
No edit summary
Line 1: Line 1:
In general, follow the [[Folgerpedia:Manual of Style]] when writing articles about cataloging topics.  
In general, follow the Folgerpedia:Manual of Style when writing articles about cataloging topics.  


==Article titles, headings, and sections==  
==Article titles, headings, and sections==  
* Name articles without particular reference to cataloging. For example: [[Things in books]], not "Cataloging sammelbands." This allows for an article to bring together all information about a topic, of which cataloging policy is one. If an article is too lengthy, cataloging policy can be separated into a subpage.  
* 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.  
* If an article is limited to cataloging policy, summarize the general policy in the lead section if feasible. Example:
: <pre> </pre>
* Formulate article names about [[MARC]] fields in this way:  
* Formulate article names about [[MARC]] fields in this way:  
: <pre>MARC [tag] [name of field from the MARC format]</pre>
: <pre>MARC [tag] [Name of Field from the MARC Format]</pre>
: ''Note'': follow the MARC format's capitalization of field names
* Begin lead section with these or similar words:  
* Begin lead section with these or similar words:  
: <pre> MARC field XXX in the bibliographic format contains <...> </pre>  
: <pre> MARC field XXX in the bibliographic format contains <...> </pre>  
* Copy the remaining part of the lead section from the Field Definition and Scope from the MARC format
* If the field exists in two or more formats, enumerate all format names in the lead section using the short form. The formal and short titles of the format names are:
* If the field exists in two or more formats, enumerate all format names in the lead section using the short form. The formal and short titles of the format names are:
** [[MARC 21 Format for Bibliographic Data]] / bibliographic format  
** [[MARC 21 Format for Bibliographic Data]] / bibliographic format  
** [[MARC 21 Format for Holdings Data]] / holdings format  
** [[MARC 21 Format for Holdings Data]] / holdings format  
** [[MARC 21 Format for Authority Data]] / authority format
** [[MARC 21 Format for Authority Data]] / authority format
**For example:
* 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
::: <pre>MARC field 856 in the bibliographic and holdings format contains information <...> </pre>
* Example:
: <pre>MARC field 856 in the bibliographic and holdings format contains information needed to locate and access an electronic resource in a Hamnet record. 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. </pre>
 
==Style==
* Prefer imperative language when giving instructions. For example, "Make a note" instead of "A note should be made."
* Avoid unnecessary catalogerese. Pretend these articles will be read by a non-specialist interested in cataloging.
* Refer to people by title, not name.
* Spell out abbreviations, especially the Latin abbreviations '''e.g.''' and '''i.e.'''
* Use preformatted text for examples.
 
==Terminology==
* Use '''call number''' instead of '''shelfmark'''.


==Content==
==Content==
* Resist the temptation to put instructions in a 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."
* 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."
 


===Articles on MARC fields===
==Articles on MARC fields==
* 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.   
* 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:
* Elements of articles on MARC fields usually include:
Line 30: Line 38:
==[[Advisory statements]]==
==[[Advisory statements]]==
*Advisory statements come first on a page, preceding the lead section.
*Advisory statements come first on a page, preceding the lead section.
* While a new article from scratch or one combining information from several sources is in process, add '''<nowiki>{{Draft}}</nowiki>'''. Remove it when the article substantially stands alone; that is, do not keep a draft advisory statement just because you want to add more stuff later
* Use '''<nowiki>{{Draft}}</nowiki>''' while a new article from scratch or one combining information from several sources is in process. Remove it when the article is substantially usable, even if not complete.
* When copying and pasting from Bard pages or other sources and there's uncertainty about whether the instructions are current and authoritative, add '''<nowiki>{{Legacy}}</nowiki>'''.   
* Use  '''<nowiki>{{Legacy}}</nowiki>''' when copying and pasting from Bard pages or other sources and there's uncertainty about whether the instructions are current and authoritative.   
* When copying and pasting from Bard pages or other sources and it's known that some of the content is obsolete, add '''<nowiki>{{Outdated}}</nowiki>'''.
* Use '''<nowiki>{{Outdated}}</nowiki>''' when copying and pasting from Bard pages or other sources and it's known that some of the content is obsolete.


==Migration==
==Migration==
* If none of the content of an existing Bard page is relevant (for example, pages made specifically for projects that have ended), do not migrate.     
* Add newly-migrated articles to [[List of cataloging pages migrated from Bard]]
* Cataloging information is spread among several sources. Search these
** [http://bard.folger.edu/cgi-bin/view.pl/Main/CentralLibrary/CatMain Bard]
** [http://shcolcatalogingproject.pbworks.com/w/page/39690608/ShCol%20Cataloging%20Project%20Front%20Page pbworks]
** [file://\\nerissa\CentralLibrary\Cataloging\Cataloging%20website.html Old cataloging website]. Most of the pertinent information had been migrated to Bard, but there may be small oases of hidden information.
* Refrain from doing any editing except for what is necessary to create and format the article. Add Advisory statements as appropriate
* Once a page has been migrated, add a statement to the effect and a link to the Folgerpedia article.
** If only a portion of a Bard or pbworks page is migrated, strike through the text.
: <pre>Migrated to http://folgerpedia.folger.edu/MARC_040_Cataloging_Source</pre>
* If none of the content of an existing Bard page is relevant (for example, pages made specifically for projects that have ended), do not migrate.     


==External links==
==External links==
* Add "External links" as the final section of an article.  
* Add "External links" as the final section of an article.  
* Add a link to the [www.loc.gov/marc/| MARC field] for all MARC-based articles  
* Add a link to the [www.loc.gov/marc/| MARC field] for all MARC-based articles.
* Other external links may be added if particularly helpful, such as LC or OCLC  
* Other external links may be added if particularly helpful, such as LC or OCLC.
 
==Categories==
* Add these categories to all articles on cataloging:
[[Category:Description]]
[[Category:Staff policies and procedures]]
* Add categories for material types only when an article is specific to one or two material types. Otherwise, the ''Description'' category will suffice.
* Categories are a controlled vocabulary in Folgerpedia; other categories may be proposed, but not used before approval. 


==Discussion page==
==Discussion page==
*
* Create a discussion 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 discussion page with a "needs discussion" link on the main page.
* Once the issue is resolved, strike through the text.

Revision as of 19:17, 11 April 2014

In general, follow the Folgerpedia:Manual of Style when writing articles about cataloging topics.

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.
  • Formulate article names about MARC fields in this way:
MARC [tag] [Name of Field from the MARC Format]
Note: follow the MARC format's capitalization of field names
  • Begin lead section with these or similar words:
 MARC field XXX in the bibliographic format contains <...> 
MARC field 856 in the bibliographic and holdings format contains information needed to locate and access an electronic resource in a Hamnet record. 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. 

Style

  • Prefer imperative language when giving instructions. For example, "Make a note" instead of "A note should be made."
  • Avoid unnecessary catalogerese. Pretend these articles will be read by a non-specialist interested in cataloging.
  • Refer to people by title, not name.
  • Spell out abbreviations, especially the Latin abbreviations e.g. and i.e.
  • Use preformatted text for examples.

Terminology

  • Use call number instead of shelfmark.

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."

Articles on MARC fields

  • 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 section on "Policy and formulation," or as two separate sections if content is extensive
    • a section on "Common tagging" containing the most commonly used indicators and subfields
    • Folger policy statements, style, and interpretations of cataloging instructions, not cataloging training itself

Advisory statements

  • Advisory statements come first on a page, preceding the lead section.
  • Use {{Draft}} while a new article from scratch or one combining information from several sources is in process. Remove it when the article is substantially usable, even if not complete.
  • 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 {{Outdated}} when copying and pasting from Bard pages or other sources and it's known that some of the content is obsolete.

Migration

  • Add newly-migrated articles to List of cataloging pages migrated from Bard
  • Cataloging information is spread among several sources. Search these
    • Bard
    • pbworks
    • [file://\\nerissa\CentralLibrary\Cataloging\Cataloging%20website.html Old cataloging website]. Most of the pertinent information had been migrated to Bard, but there may be small oases of hidden information.
  • Refrain from doing any editing except for what is necessary to create and format the article. Add Advisory statements as appropriate
  • Once a page has been migrated, add a statement to the effect and a link to the Folgerpedia article.
    • If only a portion of a Bard or pbworks page is migrated, strike through the text.
Migrated to http://folgerpedia.folger.edu/MARC_040_Cataloging_Source
  • If none of the content of an existing Bard page is relevant (for example, pages made specifically for projects that have ended), do not migrate.

External links

  • Add "External links" as the final section of an article.
  • Add a link to the [www.loc.gov/marc/| MARC field] for all MARC-based articles.
  • Other external links may be added if particularly helpful, such as LC or OCLC.

Categories

  • Add these categories to all articles on cataloging:
  • Add categories for material types only when an article is specific to one or two material types. Otherwise, the Description category will suffice.
  • Categories are a controlled vocabulary in Folgerpedia; other categories may be proposed, but not used before approval.

Discussion page

  • Create a discussion 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 discussion page with a "needs discussion" link on the main page.
  • Once the issue is resolved, strike through the text.