MARC / MARC-Lite Library Meeting(in place of the TSUG Subcommittee Meeting)

Thursday, August 13, 2015 9:30am – Conference Call --CORRECTED

Purpose of this meeting was to follow-up on questions that PC catalogers had from the May 18 RAILS RDA workshop presented by Lynn Fields/Director of Technical Services at Southern Illinois University Edwardsville.

Q: Confusion on the assigning of the 33x tagsA: There are macros in Connexion (have to have a bib record up, then go to Tools> Macros> Manage> expand the OCLC entry on the left side of the pop-up. Left click on Add33x then on the <Run> button, then on <Ok> to execute the macro. Book is the default, can use the pulldown on the 336/Content Type, to select a different material.

Q: Processing an RDA record through MarcReport and the publisher is not identified but the “publisher not present” statement is included, MR does not like UPPER case P-Publisher, but when you change it to lower case p – publisher the error is not present.A: Replace upper case P with lower p for the word “publisher”.

Q: Tag 648, when the date is out of range this tag produces in MarcReport an error message in purple.A: Leave the tag in and the indictors “as-is”. We do not know what the future holds for this tag and coding, but are prepared when it comes along.

Q: LCCN’s with the prefix bl produce an error in MarcReport. Message is ‘not correct format’.A: Remove the entire line/tag.

Q: New books are coming up as manuscripts in the Sierra format/icons, why? b: Change the Material Type from “t” to “a” and keep going. Speculated a mass error – or an individual persons errors in WorldCat.

Q: Dixie/YKBB working on Adventures of Tintin series, when working with the Standard Number for the bibs, 2 OCLC bib records are come

220 W. 23rd AvenueCoal Valley, IL 61240

(309) 799-3155http://support.prairiecat.info

up in the database. Can a list of these bibs be generated and then cleaned up?A: Duplicate bibliographic records based on the 001, 010 and 020 tags are produced from each batchload file submitted to TMQ. We (PC staff & the MARC library volunteers) are working on list of duplicate bib records based on the LCCN. When those records are resolved then we will tackle the duplicates based on the 001/OCLC number).

Q: Dixie/YK has experienced that she is unable (the software is not allowing) to merge 2 bibs when they BOTH contain the same OCLC number in the 001 tags. Workaround is to delete the OCLC number from the source bib, then when she merges the source bib is removed and no error messages returned from the server.A: John will review the Permissions on Dixie and the other MARC cataloger’s logins to see that they have the same MARC related permissions as the Sysadmin staff have.

Gail suggested that members, when in a MARC record (View or Edit) to use the <Verify> button, off on the upper right area. The <Verify> (Headings Verification) enables you to ensure consistent, authoritative headings in the database. By using headings verification, you can: Verify all indexed fields on a record, including subjects,

OCLC/LCCNs, authors, etc Verify headings while editing or creating a record. Verify and update an individual field. View verification code definitions.See the Verification Codes Explained at the end of these minutes for an explanation of the codes used in <Verify>.

Q: If you import a record from OCLC and it only has a 490 (Series Statement) and you have searched the Library of Congress Authority file for the proper heading in the 830, can you create an 830 even though it is “unauthorized”?A: Suggestion from Sandy to change the 1st indicator on the 490 to be 1, then copy the text of the line and insert an 890 tag, second indicator 0 and paste in the text. Remove any/all leading articles and you *must* end the line with a period (.).

Q: How is MARCIVE processing any unauthorized headings when staff has to add an 8XX for a 4XX?A: John is checking with the vendor.

Q: Do catalogers have to be spelling out the ISBN qualifier in $q on record that they import from OCLC, or will MARCIVE take care of that? Also, is MARCIVE removing the $c (cost) when it is records that they process?

A: John was unsure and is checking with the vendor.

Q: What is the lastest version of the PrairieCat validation table?A: Sandy will send the latest version to the mailing list for all to have.

Q: Tag 264, what do we do when the tag is repeated but the first occurrence does not have a date?A: Sandy will send out instructions on how to handle. There needs to be a $c present in the record.

Q: It has been noticed that there are Quick Click (QC) records in the database with many libraries attached. Can a list of these be generated so they can be cleaned up?A: Yes, it is possible to create a list of QC bibs. When the bibs are imported a 699 tag of $a QUICK CLICK is added to each.

Q: Is it since the last upgrade that QC bibs have a Sierra Material Type of -/blank?A: No, the default has been that QC bibs have a -/blank Material Type, because the final format of the material is not known.REPLY: This is not good. Patrons click on the Book facet in Encore and then the on-order book recors are not included in the Book facet. Request that QC bibs be loaded with a Book Material Type.A: John to look into either with B&T or the loading table being used to process the records. Would need to be able to accommodate loading of AV and having an appropriate AV bib level Material Type being assigned.

The MAGIC LLSAP is doing their monthly MARCIVE processing tomorrow/Friday. This was a good “nudge” for John, who apologized for the late notice. PraireiCat will be “froze” on Friday while those bibs added in July (except Quick Click bibs) and those bibs that were overlayed in July are copied off, the items stripped out of and then sent to the vendor.

Meeting ended 10:20 a.m.

In attendance:

Berkley, Laura – PEBBBill, Leah – CCBBBrown, Mary Louise - RAILSChapman, Elaine – RLBBCornelio, Aimee – CCBBDeBord, Dixie – YKBBFine, Dana – PRGGHickey, Trudy – SYLYLandis, Melissa – KKBBLien, Gail - RAILSSciaky, Jenifer – MKBBSlanicky, John – RAILSTedder, Sandy – RAILSTepen, Beth – UTSGWharrie, Pat – CCBBZanelli, Ed - RAILS

Verification Codes Explained 8/13/2015 from WebHelp

When you verify the headings on a record, Sierra displays codes to the left of the MARC tag for headings that are indexed in the database. To view a description of the verification codes, choose Tools | Explain Verification Codes while editing/viewing a record. The codes below provide information about the headings as they are indexed in the database.

Code Explanation

<blank> The heading is found only in the record currently being edited (and it is already in the index). This is the only record in the system with this heading.

* The heading is found only in the record currently being edited (and it is already in the index), that is, this record is the only one in the database that has this heading. This heading might be valid, or it might contain a spelling error that should be corrected. Verify the heading to ensure consistency.

+ The heading is not in the index. However, a longer version of this field is found in an indexed field in another record, for example, a birth or death date may have been established. This code can appear for new headings instead of the code N. You should verify this field to update the heading to include the additional information.

1, 4, 5 The numbers 1, 4, and 5 indicate in which MARC Authority field the heading is to be found:1—1XX field (valid form of heading)4—4XX field (SEE FROM tracing)5—5XX field (SEE ALSO FROM tracing)Numbers may appear alone, or together with code B.You should verify the heading to ensure it is tagged with the correct MARC Authority field.

B The heading is found in an indexed field in another bibliographic record. This code may be combined with a numeric code, or with code N. If the B code appears alone, you do not need to take any further action. If the B appears with a numeric value, you should verify the heading to ensure it is tagged with the correct MARC Authority field.

N The heading is not in the index. This code appears for new headings. If this code appears for a heading that you know is not new, it may indicate that the transaction file is not fully processed or that there is an indexing error in the system (contact Innovative to resolve the error).This code might be combined with code B.

X Field has not been verified. This occurs if an indexed field is added or modified after the record has been verified.