The State University Libraries of Florida: Guidelines and Procedures for the Shared Bibliographic Catalog were revised by the Bibliographic Control and Discovery Subcommittee of the Cataloging, Authorities, and Metadata Committee (CAM) of the Council of State Universities (CSUL) and approved by CAM in October 2018. Please provide any comments or suggestions to: Dave Van Kleeck firstname.lastname@example.org Chair of the Bibliographic Control and Discovery Subcommittee.
- Version 1.05 of the Shared Bib Cataloging Guidelines as approved by CAM on October 11, 2018
- Unofficial Online Shared Bib Guidelines
- version 1.01: Corrected title page ("Catalog" not "Cataloging")
- version 1.02: Edited responsibility statement to note approval by CAM on July 9, 2015
- version 1.03: Corrected typo on page 27 ("(see section 126.96.36.199)" not "(see section 188.8.131.52)")
Sections to be completed
- 184.108.40.206 Display issues when varying series practice and multiple series statements with different indicators. Related content in 3.4.8 Local Series.
- 220.127.116.11 Proprietary Fields in Enhanced Records
- 18.104.22.168 "Each institution must report to a centralized location [TBD] data on products for which batch loading is used ..."
- 22.214.171.124 Add recommendation to move OCLC numbers on vendor records to a protected 599 field with "(OCoLC)" as the identifier.
- Add to 3.4.8 Local Series -- How to record 490 fields corresponding to the local series access points. Use $5 and $9?
Final Report (August 27, 2014)
Valid STA Values
This page describes the valid status values for both holdings and bibliographic records.
Keep XX Codes
FLVC has implemented $5 KEEPXX for protecting local or proprietary fields from being wiped out during WorldCat overlays of Aleph bib records. This replaces the use of $9 + MARC Organization Code for this purpose. It turned out that $9 was already used in Aleph to mark long fields that have been broken up.
When $5 KEEPXX is used with a valid 2-letter code replacing the XXs, almost any field will be protected. If you’re adding a $$5KEEPxx to a field, make it the first $$5 so that the field is protected. If there are multiple KEEP $$5’s, it doesn’t matter which is first. If there’s a mix of multiple KEEP $$5’s and MARC Org Code $$5’s, order doesn’t matter as long as one of the KEEP $$5s is first.
Below are the codes to be used for each university:
Attached are drafts for three sections I (Kim Montgomery) was working on for the Guidelines:
- The Subfield 5 in Aleph – includes differentiation between the $5 KEEPXX, $5 + MARC Organization Code, what to do with Non-SUL $5s in OCLC records and in archival digitization vendor records, and an appendix with codes and actions. New 3.4.1 The Subfield 5 in Aleph (docx)
- Proprietary Fields in Shared Records – includes an appendix of known proprietary field purchases as of December 2012, based on a survey done at that time. 126.96.36.199 Proprietary Fields in Shared Records (docx)
To explain this further, please see the PowerPoint written by Kim Montgomery from UCF. Please read the comments below the slides to flesh out the slide text.
Data loading information can be found here: Data Loading
GenLoad Manual Update
The following MS Word document is supplemental. Due to the maintenance of the Data Loading section of this wiki and this section, we've put this document here. In the future, they should be combined.
Experimental Links - Batchloading
To submit a batch load event: Google Form
To review batch loaded events: Google Spreadsheet
To correct an entry (video link to Youtube): YouTube
Multiple Series Fields Cleanup
Shared Bib Records with Multiple Series Fields: Issues and Suggested Solution
- Set of 1,123 Bib Records to Have OCLC Numbers Replaced (.xlsx)
- Set of Bib Records Identified for Overlay (.xlsx)
Authority Review Set:
- This set contains any OCLC records that contain 490 0# fields OR don’t contain any 490 field. Their Aleph records will be excluded from overlay. The following two files are the same in content. The first is a zipped CSV file and the second is already converted to Excel format. They contain multiple rows from the same Aleph Bib, but with different series data from Aleph.
- * A = Aleph Bib Number
- * B = OCLC Number
- * C = Aleph 490
- * D = Aleph 830
- * E = OCLC 490
- * F = OCLC 830
- Caution, there is a known bug in the code so that when there is no Aleph 830, the OCLC 490 can end up in column D, as seems to be the case in the first 5 rows of data (excluding the headers).
Reporting Duplicate Records
In Dec. 2013, FLVC began centralized duplicate clean up for the SUL’s. As a result duplicate reporting to the Aleph Duplicate Spreadsheet was discontinued on March 1, 2014.
For monographs, duplicates will now be reported to FLVC staff member Melissa Stinson at email@example.com. Please include the Aleph Bibliographic system numbers and any other relevant information about the records.
For continuing resources, report duplicate records to SERCLIENT-L for continuing resources to discuss whether to overlay the record and so the other libraries can edit their OCLC holdings. The subject line of the e-mail should state the nature of the change (e.g. SB overlay) followed by abbreviations for the SULs affected by the change. The body of the e-mail should contain at the minimum the bib number and OCLC control number of the Aleph record to be overlaid and the OCLC number of the new record selected in OCLC.
Tools for reporting duplicate records:
Instructions for 856 41 Cleanup Project
FLVC sites with information about how the Mango ICONs are currently displayed in the wiki:
- How does an eBook or eJournal icon get Created in MANGO? (FLVC)
- How is the format icon that displays on the brief record in Mango chosen when the record has listed multiple formats? (FLVC)
- How is the Online Material Type Created for records in Mango? (FLVC)
- Shared Bib Cataloging and Display in Mango
Cataloging statistics via the ARL field in the holdings record
- Instructions for the entering data into the ARL field
- Instructions for running the ARL field report in Aleph Services
- Instructions for the editing the ARL Report data
- Instructions for maintaining the Total Delete List spreadsheet
- Example of the ARL Report DATA spreadsheet
- Example of the Total Delete List spreadsheet
Issues with the ARL Report
Problem: The report only retrieves the first of multiple fields or subfields.
- Solution: Add the new field or subfield before the old one. See Appendix 3 of "Instructions for the entering data into the ARL field" for more details.
Problem: When titles are withdrawn and the bib and holdings records are deleted, the data in the ARL field is lost.
- Solution: Maintain an archive of ARL field data for 'total deletes' before deleting the bib and holdings records.
Problem: Human error.
- Solution: Review the report data for errors. Provide ongoing training as needed.
SULs may share their local policies and procedures, training aids, instruction sheets, and guidelines examples here. Recommendation: upload documents to the wiki instead of Google Docs for permanence and protection from editing.
SB Cataloging guidelines examples
Cataloging, Authorities, and Metadata Committee
- Daniel Scheide firstname.lastname@example.org
- Chris Boyd (past co-chair) email@example.com
- Rita M. Cauce (2017 co-chair) firstname.lastname@example.org
- Amy K. Weiss email@example.com
- Jeanne M. Piascik (past co-chair) firstname.lastname@example.org
- David Van Kleeck email@example.com
- Jennifer L. Murray (2018 chair) Jennifer.firstname.lastname@example.org
- Brian Falato (2017 co-chair) email@example.com
- Shari Johnson firstname.lastname@example.org
Meetings occur on Adobe Connect. Links will be shared each time.
Bibliographic Control and Discovery Subcommittee
see CSUL for more information (http://csul.net/content/bibliographic-control-and-discovery-subcommittee)
- Malka Schyndel email@example.com
- Chris Boyd firstname.lastname@example.org
- Elaine Dong email@example.com
- Mark Lopez firstname.lastname@example.org
- Kim Montgomery Kimberly.Montgomery@ucf.edu
- Dave Van Kleeck (2018 Chair) email@example.com
- Susan Massey firstname.lastname@example.org / Tammy Druash email@example.com
- Brian Falato firstname.lastname@example.org
- Donna R. Fluharty email@example.com
BCDS Meeting Link Location
Meetings occur on Zoom since April 2018. Links will be shared each time.
in 2019, BCDS meetings are held quarterly, all at 2pm ET
- January 11, 2017 Agenda | Minutes
- April 3, 2017 Agenda | Minutes
- July 7, 2017 Agenda | Minutes
- October 2, 2017 Agenda | Minutes
- November 29, 2016 Agenda | Minutes
- October, 12, 2016 Agenda | Minutes
- September, 14, 2016 Agenda | Minutes
- August, 10, 2016 Agenda | Minutes
- July, 13, 2016 Agenda | | Minutes
- June, 8, 2016 (Meeting Canceled)
- May 11, 2016 Agenda | Minutes
- April 13, 2016 Agenda | Minutes
- March 9, 2016 Agenda | Minutes
- February 10, 2016 Minutes
- January 13, 2016 Minutes
- December 09, 2015
- October 14, 2015
- September 9, 2015
- August 12, 2015
- July 8, 2015
- June 10, 2015
- May 12, 2015
- April 8, 2015
- March 11, 2015
- February 11, 2015
- January 14, 2015
- November 11, 2014
- October 8, 2014
- September 10, 2014
- August 13, 2014
- July 9, 2014
- June 11, 2014
- May 14, 2014
- April 9, 2014
- March 12, 2014
- February 12, 2014
- January 8, 2014
- December 11, 2013
- November 13, 2013
- October 9, 2013
- September 11, 2013
- August 14, 2013
- July 10, 2013
- June 12, 2013
- May 22, 2013
- April 10, 2013
- March 27, 2013
Working Documents and Supplementary BCDS Materials
3.3.3. Rules for the Creation and Maintenance of Access Points
- Shared Bib Cataloging Guidelines Section 188.8.131.52 Subject Headings - Addition of FAST Headings (docx)
- Shared Bib Cataloging Guidelines Section 3.3.3 - Series Headings Draft Revision (docx)
- Shared Bib Cataloging Guidelines Section 5.0 - Aleph Authority File Maintenance (docx)
- Supplementary Documents - rewrite of 4.2.4 to include a new section on links for free resources (docx)
- Supplementary Documents - New 3 4 1 The Subfield 5 in Aleph.docx
- Supplementary Documents - 3 4 8 Local Series.docx
- Supplementary Documents - 3 6 13 Proprietary Fields in Shared Records
- Supplemental Documents - 856 Cleanup followup & Proposal
- Supplemental Documents - 856 Cleanup Document - FIU
- Supplemental Documents - Draft Guidelines revision for Agenda Item 8b (Series Headings)
Topics referred to the Bibliographic Control and Discovery Subcommittee
- 01/14/15: From the Cataloging, Authorities, and Metadata (CAM) Committee
- Best practices and instructions for batchloading as a separate document or appendix of the Shared Bib Guideline
- 02/12/14: From the Cataloging, Authorities, and Metadata (CAM) Committee
- Removing 856 fields for non-SUL links that require authorization
- 11/13/13: From the Cataloging, Authorities, and Metadata (CAM) Committee
- Determine specifics for removing OCLC numbers from non-OCLC so that the Report of duplicate records with same OCLC number is more useable
- Address the possibility of global changes to remove the status of DO NOT OFFLOAD on bibs with protected Tables of Contents and Summaries
- Identifying proprietary records with 520/505/970 fields
- Provide more specifics on implementing the proposal on cleaning up 856 fields for display of Mango icons
- Fixing incorrectly coded 856 41 fields
- 4/11/12: From the Shared Bib Task Force
- Report on 856 coding and icon display
- December 12, 2012
- November 14, 2012
- October 24, 2012
- October 10, 2012
- September 12, 2012
- August 22, 2012
- August 8, 2012
- July 11, 2012
- June 13, 2012
- May 23, 2012
- April 25, 2012
- March 14, 2012
- February 8, 2012
- January 11, 2012
Topics referred to the Metadata Subcommittee
- 9/26/12: Statement to CSUL on the Need for RDA Implementation Assistance
- 4/25/12: From the Shared Bib Data Loading Group. On the issue of locking records in Shared Bib, for guidelines on the use of a proxy prefix in the 856 field, and for guidelines on when to overlay an existing bib in Aleph.
- 3/19/12: From Shared Bib Implementation Team. For bib tag use post merge, add to bib tag chart and possibly add 9XX & Aleph specific fields
- 3/19/12: From Shared Bib Implementation Team. For proprietary records, need to review advisory group and establish guidelines
- 3/19/12: From Shared Bib Implementation Team. Use of STA values other than Suppressed or Deleted
- 2/20/12: the post-migration discussion of what to do with STA values should be referred to the metadata subcommittee because this has to do with establishing uniform practices across the SULs
- 2/20/12: Discussion of whether or not there should be a uniform standard for the creation of “little” bibs that are created at the branches to circulate equipment and such
- 2/20/12: Process for deleting records added in error submitted to TSPC for approval
- 2/09/12: The Technical Services Planning Committee (TSPC) asked Metadata to take responsibility for "assuring approved revisions are included in the SUL Guidelines and Procedures for the Shared Bibliographic Catalog. The master copy of the guidelines will reside on the CSUL/TSPC Web site." TSPC minutes from the 2/09/12 meeting.
Outstanding issues from the Metadata Subcommittee's 2012 Q4 report to CSUL
- Completion of the State University Libraries of Florida: Guidelines and Procedures for the Shared Bibliographic Catalog
- Work with FLVC to resolve vendor batch load issues and incorporate decisions into future guidelines
- Train university cataloging staff on the application of the Shared Bib Cataloging Guidelines once they are completed
- The creation of project plans for FLVC to complete global clean-up of data issues resulting from the Shared Bib merge
- Inform CSUL and FLVC about university library cataloging issues that arise due to rule changes such as RDA
- Maintenance of a shared university library cataloging page on the Shared Bib Wiki
- Provide feedback to CSUL on the impact of the Shared Bib merge
Click on the header above for historical and archival information
Ideas for what is covered under "cataloging"
This list of issues and topics was provided to the Metadata Subcommittee by the Shared Bib Implementation Team. The Bibliographic Control and Discovery Subcommittee has retained issues or topics that are still relevant.
- Guidelines/procedures for cataloging issues not already covered.
- Value of keeping electronic vs. print records separate.
- What is needed in the "union" view of the record.
- Proprietary fields/records.
- Suggesting bib. record cleanup.
- Use of LKR and ANA tags.
- Indexing changes (if any).