Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Archival Control (Leader/08) value “a”
  • Record Type (Leader/06): Can include at, c, e, f, d, p     
    • Type t – Manuscript language material, including all unpublished. i.e. not commercially published, theses 
    • Type f – Manuscript cartographic material
    • Type d – Manuscript notated music
    • Type p - Mixed materials 
  • 040 $e values for manuscript and archival descriptive rules of cataloging

    • See the code list for Description Convention Source Codes
    • For 040 $e codes that have been superseded, if the cataloging of the record has been updated to follow the new code, then the 040 $e should be updated. If not, then the code should stay as-is.
  • General guidelines from OCLC’s Bib Formats:

Material

Guideline

Archival and rare material

Determine the form of material and use the appropriate code. For example, for a rare book, use code a. For a manuscript letter, use code t. For all unpublished theses, use code t. For a collection of mixed materials, use code p. For online resources that are reproductions of manuscripts, use codes a, c, and e (the original format code). Code Ctrl to indicate archival control status of the material.

Recommended Best Practice for Harvard's MARC bibliographic records for manuscripts and archival collections to sync with OCLC's Worldcat:

...

Summary of past and current coding practices for Manuscripts and Archival Collections at Harvard

Questions (hl-cat 11-22-2019)ArchivesBaker Library
Berenson
Countway MedicineDivinityHarvard Theatre CollectionHoughtonLawLoeb MusicSchlesinger
Contact:Kate BowersChristine RiggleAmber LaFountainNell CarlsonSusan PyzynskiSusan PyzynskiMary PersonAnne AdamsLee Sullivan, Paula Aloisio
Which descriptive conventions are used?Current practice is DACS and sometimes dcrmg. About 50% of records have no 040, or no 040 $e. Many have $e dacs or $e local (prior to introduction of DACS in 2005).Majority of archival and manuscript collections are coded appm or dacs. We also use dcrmmss and amremm for manuscript material in our rare book collection.


Current practice is dacs for collections and single item manuscripts. Previously used appm.Currently use appm, but many manuscript records lack $e in 040
Current practice is dacs for collections and single item manuscripts. Previously used appm.
If using the rare book descriptive conventions (like dcrmb), are the record coded "a" in Leader 08 (archival control)Do not use rare book descriptive conventions.Generally no.



No
No
Do you code "a" in Leader 08 for manuscript materials (archival control)?Yes, for current cataloging. Older records pre-date this byte definition.Generally yes. It is the current best practice for materials cataloged according to dacs.


Yes.No, very little use of archival control byte
Yes
Is original cataloging done in Connexion?No, original cataloging is done in Alma.Yes


No, original cataloging is done in AlmaYes, for the past two years
Yes
Are enhancements done in Connexion?No, all work is done in Alma.Generally yes, but it's a new best practice.


Not currently.Yes, for the past two years
Yes

Cataloging reproductions of Manuscripts

...

Theses are not sent in the Data Sync collection for manuscripts regardless of Leader Type coding provided a 502 Dissertation Note is present in the record. The 502 note is used to exclude records from the manuscript collection. 

NET holdings

Location codeData Sync statusComments
COLINDo not sendHoldings for eresources formerly represented by holdings and now primarily represented by portfolios. Per Lauren Syer do not include in Data Sync
INPROCDo not send
BHLDo not send
RDMSend
Restricted AccessDo not sendexclude NET holdings where 506 indicator or note are not for unrestricted access


Provider neutral records - background 

...

If any of this is not clear, or if you need more information from me in order to investigate this, please let me know. Thanks, in advance, for any advice you can provide! 


Jay Weitz, Cc: Morrison,Carrie <morrisoc@oclc.org>; Luo,Ling <luol@oclc.org>; Chirakos,Anthony <chirakoa@oclc.org>; Savage,Michael <savagem@oclc.org>; Bremer,Robert <bremerr@oclc.org>; Ramsey,Laura <ramseyl@oclc.org>

...