5C Record Merge Working Group
Open House
Friday, March 13, 2020
Today’s Agenda
Introduction & Welcome
Update: Review of Recommendations and Work Scope
The merge happens before the migration. 5CRMWG is working on the merge. FIT is working on the migration.
Resources within Scope: Resources in the general collections that aren’t part of a linkage group, suppressed, part of special collections, rented collection, or batch loaded. See Recommendations for full details.
Brief Introduction to Backstage Library Works Dedup Profile
5CRMWG is working with Backstage Library Works on deduping bibliographic records within the scope of the merge. BSLW uses a Dedup Profile.
Our aim is to work within this framework to increase the accuracy and consistency of the merge of our bibliographic records.
Comment & Review: Special Fields To Be or Not To Be Retained Thus Far
Retain | Not Retained |
928 | 049 |
| 029 |
| 907 |
| 910 |
| 998 |
Comment & Review: X9X, 9XX, 99X
We’re Presenting Thus Far: 590, 690, and 793
For information that is specific to a particular resource owned by a specific institution, it’s important to implement a consistent and accurate method for identification, access, and discovery.
The local fields we currently use typically don’t allow a subfield to enter information such as an organization code or source of heading. As such the relationship we’re trying to establish can’t be done according to national standards, best practices and recommended mappings.
So, we are figuring out solutions. The first of which will be shared here.
Solutions
Use of a subfield 5 with the LC Organization Code for those MARC 21 Fields that allow it.
Use of a subfield 2 with local/LC Organization Code for those 6XX MARC 21 Fields that don’t allow a subfield 5.
Comment & Review: Decisions on Dedup Profile
Overall bib record : Keep latest
008 : Date “off by 1 year”
250 : “Full” and “must verify”
260/4 : “Within”
300 : Keep longest
500 : Keep unique
583 : Keep all
Comment & Review: 5XX
The following MARC21 Note Fields take a subfield $5: 500, 501, 506, 526, 533, 538, 540, 541, 561, 563, 584, 585, and 588.
For the following note fields listed above, our guidelines are to use a subfield 5 with the appropriate LC Organization Code if the information entered applies to a specific institution. If the information is general and applies to any institution anywhere, then no subfield 5 is needed. Examples are:
500 _ _ $aIncludes index.
540 _ _ $aIncludes public performance rights$5MU.
Comment & Review: 6XX
For subject fields, our guidelines are to use a subfield 2 with local slash and the appropriate LC Organization Code in lower case if the information entered applies to a specific institution. If the institution has a 655 with information specific to them, then a subfield 5 and subfield 2 should be used. If institutions are mapping the 690 to another 6XX field, there is latitude. Institutions should consider our guidelines and their needs. Examples are:
650_ 7 $aWomen writers.$2local/mns.
655 _ 7 $aFinding aids$5MU$2local/mu.
654 _ _ $aRudman Collection$bOppression and resistance$cHolocaust.$2local/mu
657 _ 7$aTheses$x[Program]$xMasters$2local/mu.
655 _7$aNewspapers$zMexico$5MU$2local/mu.
Comment & Review: 690s in Batch Loads
For subject fields in our batch loads, our guidelines are to make sure that these fields follow the example in the previous slide. For 690 in metadata sets from vendors or OCLC for instance, the 690 fields can be transformed to a 653 field. Our guidelines also recommend that all metadata sets that are batch loaded follow the RDA content standard. Examples are:
653_ _ $aZoologoy.
653 _ _$aChemistry.
Potential Clean-up Projects
Our Work Continues
Stay Tuned to the Five Colleges FOLIO Blog, our Slack Channel (#5crmwg), and email for updates and announcements.
Feedback: https://forms.gle/NK2rHXqZUoiS9GoQ8