Table of Contents

1. Brief Announcements (all)
   
2. Cataloging Electronic Resources -- Single Versus Multiple Record Approach
   
3. Authority Control (Van Pulis)
   
4. Cataloging Serial Titles in Aggregators (Davis)
   
5. Pinyin Conversion (El-Sherbini)
   
6. III Millenium Modules (Hamilton, Davis)
   
7. New MARC Fields (Van Pulis, El-Sherbini)
   
8. Analytics Working Group (Scott)
   
9. URL Checker/Displays in the 856 (Helmick, Diedrichs)
   
10. Next meeting

    
    

1. Identifying electronic resources (new location codes, scoping, possible subject headings)
   
2. Online entries for e-journals (JSTOR example) (Scott, Davis, Murphy)
   
3. CD-ROM Processing (El-Sherbini)
   
4. Indexing of data in 028 field (Green)
   
5. Duplicate Serial holdings where only one copy is analyzed (Scott)
   
6. Cat as Monos (El-Sherbini)
   
7. ICODE1 for Non-networked Reference Databases (Davis)
   
8. E-Resources Working Group (Davis, Scott)

   
   

1. Brief Announcements (all)

   
   

2. Cataloging Electronic Resources -- Single Versus Multiple Record Approach

   Summary: OhioLINK DMSC is considering the request from the OhioLINK Users Committee to move to a single record approach for cataloging electronic resources. OSU collection managers have also expressed interest in doing this locally.

   Issues:

   1. As our representative to DMSC, Noelle has requested that we formulate our philosophy on this issue for her use at the 4/17 meeting.
      
   2. The Law Library has submitted a proposal to use the single record for "free" e-journals already owned in print.

   Expected outcome: consider these two requests and determine how to proceed.

   
   

3. Authority Control (Van Pulis)

   Summary: we are close to implementing authority control processing.

   Expected outcome: Hear status of project.

   
   

4. Cataloging Serial Titles in Aggregators (Davis)

   Summary: collection managers have expressed considerable interest in providing access to the serial titles which appear in full text within services (such as aggregators). At present, these titles are not represented in OSCAR and thus, it is not readily apparent that we have all or parrts of these titles in full text. The Program for Cooperative Cataloging's Serial Aggregator Task Force has issued its final report which is available at: http://www.loc.gov/catdir/pcc/reports.html

   Expected outcome: consider what we know about this process. Hear report about what OhioLINK DMSC is thinking about this topic. Decide what further action is warranted.

   
   

5. Pinyin Conversion (El-Sherbini)

   Summary: The Pinyin Conversion Project is an effort to convert romanized Chinese data from the Wade-Giles to Pinyin romanization schemes. Pinyin is a system for writing the Chinese language in the Latin alphabet. It is used throughout the world, including by the United States government and by the news media. Most users of American libraries today are familiar with the pinyin romanization of Chinese names and places, and providing access to the Chinese language with that system will make it easier for them to locate material. The use of pinyin romanization by libraries should also facilitate the exchange of data with libraries internationally. In order to change to pinyin, the Library of Congress (and other libraries such as OSU) will have to convert existing files so that the Library¹s database will reflect the new standard.

   The Research Libraries Group (RLG) will convert all Library of Congress Chinese language bibliographic records that reside in the RLIN database. RLG has supplied LC with lists of book and non-book material appearing on RLIN. LC will then compare these results with lists of Chinese records in its own database, identify records that are not on RLIN, and move them there. OCLC will also convert its database and files. RLG plans to convert Chinese records in its database beginning in spring 2000.

   A current timeline for the project for LC is available at http://www.loc.gov/catdir/pinyin/timeline.html

   Cataloging was asked to check with III about the existence of space in the III record for the "marker" that will identify records which have been converted. Magda and others from Cataloging will meet with Quoqing Li to see what additional information he has available.

   Expected outcome: hear report from Cataloging.

   
   

6. III Millenium Modules (Hamilton, Davis)

   Summary: The Libraries has purchased the III Millenium modules including Acquisitions, Serials and Circulation. We have targeted summer 2000 as a possible date for implementation but no specific plans have been made. This issue has been turned over to Marsha Hamilton and Trisha Davis for investigation since the modules to be implemented will have the most impact on their areas. After additional information is determined, that should be shared with the TSC in particular the Health Sciences, Law and Regional Campus Libraries.

   Expected outcome: hear report from Marsha and Trisha

   
   

7. New MARC Fields (El-Sherbini, Van Pulis)

   Summary: Innovative has begun to receive inquiries about how the INNOPAC software will handle a series of new MARC fields in Library of Congress and National Library of Medicine (MeSH) subject authority records: form/genre subject 155), subject subdivision (18X), and heading linking entry (7XX). Tech Bulletin 227 from OCLC includes some minor changes in the MARC fields. H. Thomas will review those and send a message to the committee. We may also need to determine if these create any problems in Felix if they are used. the committee received a report from H. Thomas on this via e-mail. Some changes need to be made before ongoing authority control begins. Most of these will be referred to N. Van Pulis. There are a few issues which will affect the public display. H. Thomas will indicate what these are for the User Committee to consider. With H. Thomas’ resignation, N. Van Pulis and M. El-Sherbini will assume responsibility for this issue.

   Expected Outcome: Refer issue to Users Committee when N. Van Pulis and M. El-Sherbini provide information.

   
   

8. Analytics Working Group (Scott)

   Summary: A working group on analytics was appointed to investigate issues related to analytics including should all cataloging locations be expected to treat a given title in the same fashion. Mary discussed with public services the issue of whether all cataloging locations should be expected to treat a given title in the same fashion. Public Services recommends that if one location wants the title analyzed, then everyone’s copy should be analyzed. There are still lingering issues where a location has individual volumes cataloged as monographs with unique call numbers rather than serial call numbers. The working group (Britton, Van Pulis, and Scott) will develop examples and experiment with displays so that a draft recommendation can be sent to Users.

   Expected Outcome: Hear report for working group

   
   

9. URL Checker/Displays in the 856 (Helmick, Diedrichs)

   Summary: Two questions were raised at the 8/20 meeting. A third question was raised about maintenance of broken URLs.

   1. Are there any plans for using a URL checker for links on the Library’s home page? Carol Diedrichs will forward that question to the IT Committee.

   2. Should we issue an enhancement request to II for display of subfield 3 in the 856 display? Sally will first review release 12 before deciding whether the enhancement is addressed by that release.

   Release 2000 included an optional URL checker. However, III has bundled the URL checker into a product that we do not need; that product is priced at $10,000. S. Rogers has sent a message to III about whether the URL checker can be acquired independently for a lower cost; III is considering the issue.

   Nancy Helmick advised the group that many III users are unhappy with III’s decision to bundle the URL checker with a product that is not in heavy demand. We will continue to advocate for the availability of the option separate from the current product.

   No. 1: Steve Westman is working on a way to do URL checking of titles in OSCAR with an 856 field. Once Steve identifies a process, he will work with technical services to determine how the review and correction of these broken links might be handled.

   No. 2: Carol will check with Sally for a status report.

   Expected outcome: hear status report

   
   

10. Next meeting

    
    

1. Identifying electronic resources (Rogers, Scott)

   Summary: The issue of using a scope to identify electronic journals is now in process. We need to discuss this aspect of the issue so this project can proceed. M. Scott has also raised the question of whether we should consider adding a local subject heading which would allow electronic journals to be located within broad subject areas.

   IT has determined that this approach a separate location code for various servers is not needed. However, TSC did agree to a new location code for electronic full text journals — WWJ.

   Sally will flip the electronic full text journals to WWJ (location code). Any titles which are not full text will be reviewed by her to determine whether they fit the definition. If problems arise, she will refer those to TSC for discussion.

   Expected outcome: the issues have been referred to the Electronic Resources Subgroup

2. Online entries for e-journals (JSTOR example) (Scott, Davis, Murphy)

   Summary: we have a situation where the uniform title for an electronic journal is misleading to the public (or at least difficult to understand). Is there anything that can be done to improve this display?

   Expected outcome: Expected outcome: the issues have been referred to the Electronic Resources Subgroup

   
   

3. CD-ROM Processing (El-Sherbini)

   Summary: Mary Scott has raised questions about the use of the volume identifier for CD-ROMs. National cataloging policy does govern this issue and our implementation of it.

   After extended discussion, there seem to be three options: 1. use a location code for CD-ROMs for locations which house these in a physically separate place. 2. add a volume identifier for all CD-ROM even where that varies from national standards 3. add a 500 note which indicates that the piece is a CD-ROM. Add the note so that whenever possible this note appears on the first page of the system display.

   The committee decided to put forward options 1 and 3 above for discussion at Users Committee. Option no. 2 violates national standards and thus is less desirable if an acceptable alternative can be found.

   Expected Outcome: Review discussion from Users and determine next steps.

   
   

4. Indexing of data in 028 field (Green)

   Summary: The Music/Dance Library is interested in finding some way to close our card shelflist of record/CD manufacturer numbers and use 028 "music number" data to control our inventories of sound recordings. Currently we need to search our publisher/number card index when we are ordering new CDs or processing gifts to avoid adding duplicates to the collection. The full 028 "publisher/music number" is the functional equivalent of an ISBN for sound recordings, and is a necessary element in sound recording purchase orders. Unfortunately when OSCAR was first set up, a decision was made to retain only |a of 028 (the number value) and not to retain |b (publisher name) when records are imported into OSCAR/FELIX. Therefore when we search the "OTHER NUMBER" index, we cannot browse the numbers with their associated "publisher" (name of record label). Reindexing the "OTHER NUMBER" index is not an option since 028 |b data was not retained. However, 028 |b is essentially identical to 260 |b. This means we have two possible options to explore:

   1) Add an initial search option on PUBLISHER (260 |b), with alternate display option for "music number [028 |a] and title." 2) Add a new alternate display option on the "OTHER NUMBER" index for publisher name. The current alternate display options are D> Display title and author C> Display title and call #

   We suggest adding a third alternate display option for the OTHER NUMBER index:

   B> Display publisher

   If III software limits us to two alternate displays per index, perhaps option C> could be eliminated as an option for OTHER NUMBER index searches and replaced by the "Display publisher" option.

   Browsing 028 publisher numbers with their matching publisher name is necessary for two reasons:

   1) Many publishers use similar numbering systems, e.g., " 028 |a CD 572 " 2) OSCAR does not ignore spacing, and treats punctuation as spaces. Therefore, several variations of searches are usually necessary since the entry of the 028 |a spacing and punctuation.

   I am certain that music librarians around the state would be in favor of developing a better system of publisher/number 028 searching. When we have identified a possible solution to this problem, we are willing to post the refined proposal for comments on the statewide listserve for OhioLINK Music Librarians.

   At the April 9 meeting, the committee favored the approach of the option for searching by publisher. Some of the other options were not feasible with the limitations of III. Alan Green was to revise the proposal and distribute to TSC. Carol Diedrichs will then forward the proposal to Users Committee for consideration.

   Expected Outcome: Carol Diedrichs will check with Users and Alan Green about the status of proposal and discussion with Users Committee

   
   

5. Duplicate Serial holdings where only one copy is analyzed (Scott)

   Summary: There are a number of duplicate serial holdings in the system where only one copy is analyzed. The title that came up is:

   
   B12429132    BIBLIOGRAPHIC Information
   LANG: eng    LOCATION: multi    BIB LVL: s         BCODE3: z
   SKIP: 0      CAT DATE: 03-16-94 MAT TYPE: s        COUNTRY: nyu
   CALL #       QP601 .C47
   TITLE        Methods in enzymology
   IMPRINT      New York, Academic Press
   DESCRIPT'N   v. ill. 24 cm
   
   MARC         LABELING:VOL(+PT IF NEEDED)---ANYL[VC890713]$$ &vc840501
   
                         Summary of Attached Records
   CHECKIN 0001 > LOC: hea; COPY=c.3; ID=v246-; CHECK-IN=Card: Status is
   current,
   CHECKIN 0002 > LOC: hea; COPY=c.11; ID=LibHas
   CHECKIN 0003 > LOC: hea; COPY=c.11; ID=LibHas
   CHECKIN 0004 > LOC: sel; COPY=C.1; CHECK-IN=Card: Status is current, 49
   boxes,
   CHECKIN 0005 > LOC: agi; COPY=C.2; CHECK-IN=Card: Status is current, 49
   boxes,
   CHECKIN 0006 > LOC: bpl; COPY=C.4; CHECK-IN=Card: Status is current, 49
   boxes,
   CHECKIN 0007 > LOC: vet; COPY=C.6; CHECK-IN=Card: Status is current, 49
   boxes,
   
   

   Only the Copy in BPL is being analyzed, but there are 5 currently received copies in the system. The question came up because it is confusing to patrons in VET and SEL when they find the BPL copy and request it, not realizing that the VET or the SEL copy is on the shelf and all they have to do it pick it.

   Apparently the current policy is to do analytics only for the location that makes the original request. I personally think the policy should be to provide linking for all copies no matter where they are located if a title is identified as important enough to be analyzed. We have enough problem with patrons requesting OhioLINK copies of unanalyzed serials we own without continuing the same problem on campus. A small working group composed of Mary Scott, Noelle Van Pulis, Barbara Van Brimmer, and Connie Britton has been appointed.

   Expected outcome: hear report from working group

   
   

6. Cat as Monos (El-Sherbini)

   Proposal for the cat-as-mono series records.

   Problem: The CAT-AS-MONO (CAM) series records often are brief bibs. Usually, only order and check-in records are attached. The CAM brief bib records contain very little information and it is necessary to go to the order or check-in records to clearly identify the series and the treatment. The CAM bib is a shared record, used by acquisitions and cataloging for the same, related or different purposes during processing or problem-solving. Also, to identify which titles are treated as CAM, it is necessary to do a boolean to collect records based on a note in the attached order record, which uses significant system resources.

   Expected Outcome: review recommendation and determine next steps.

   Recommendation:

   Part 1: add "CAT-AS-MONO" as the call number in the series bib, in field 099. This is searchable in Search mode or Update mode. The result is an alphabetic list of titles. Further, in Search mode the search can be Limited by location, which could be useful to collection managers or others who would need to scan a list of titles which have this treatment for a particular location. A boolean is not necessary to collect all or some titles. (However, a boolean would be needed if sorting or other work was needed on the resulting file.)

   Possibly discontinue use of "CAT-AS-MONO" note in the order record. Main Library and HEA use different notes (CAT-AS-MONO and CAM).

   Retain other characteristics of the series bib: e.g. CAT DATE is blank, usually no item record attached.

   Part 2: when a full bib is available from OCLC, overlay the short series bib. This fuller record provides additional identifying information, perhaps including series/serial title changes.

   Advantages:

   The treatment of the series is immediately visible in the 099 as call number. The series with this treatment can be easily collected by any OSCAR staff user in search or update mode (including ability to limit by location in Search mode). A boolean is simplified because only one element is required (not bib plus order records) and the call number is standardized.

   The fuller bib provides additional identifying information, and can carry title changes, etc.

   The update of the records can be done only as the records are otherwise worked on or can be a special student project to be done as time permits (low priority).

   Disadvantage: Time to update bibs with 099 call number, import full bib if available

   
   

7. ICODE1 for Non-networked Reference Databases (Davis)

   Summary: P. Pearson has developed a list of reference/citation databases which are available to patrons but are not accessible on the network. These databases will be made available in a boolean file to the public. What needs to be done to make this information useful?

   The list from P. Pearson needs to be reviewed and cleaned-up. We need to notify collection managers about how future purchases or gifts in these categories need to be submitted to technical services so that they will be processed and appear in this boolean file. We also need a definition about what type of material is to be included in the file. The decision was also made to add an item record for these products (which are physical pieces usually) and code them with ICODE1 = 6 (non-networked databases). What this boolean is for and how it should be defined has been referred by the Steering Committee to the Users Committee. Once that is determined, technical services can proceed to catalog and clean up these records and establish a process for new titles to be coded for inclusion in the boolean. T. Davis will investigate the questions above and draft a document for review by the committee (after Users Committee has defined). Users has completed its survey and P. Pearson is developing some sample records for further review.

   C. Diedrichs received the following message from Penny Pearson on 7/20/99:

   "If we use the ICODE1 value 6 to identify titles to be handled in this way I assume one of the next steps is for Tech Services to issue a policy memo. Some of the issues I've identified which should be included are:

   1. Update item records for non-networked electronic resources to ICODE1 value 6 so they can be identified via an OSCAR boolean.

   2. A policy that at least one item record needs to be created for non-networked electronic resources and who is responsible for creating that item record. Most of these non-networked electronic resources are CD-ROMs and an item record is created automatically. But BUS has several Internet resources that are available only from BUS, so we are defining them as non-networked since they can't be accessed from any other location. For those titles no item records were created and now one item record for each title is needed in order to collect these titles in the boolean I'll be doing on ICODE1 = 6. Teri Hagerman asked me about several titles for which Chuck Popovich requested that item records be created; she wanted to know why an item record was needed and why a summary statement wasn't an acceptable alternative. I explained this project to her. Other than those few BUS titles I don't know of any other existing titles that fit this mold, but the fact that an item record must be created should probably be included in any policy statement.

   I can write up a description of this non-networked electronic resources project if you want to include such a description in a policy statement. Let me know if there's anything else I can do to assist or any other information you need from me."

   
   It is still not clear to us what the definition of "non-networked" is. The Electronic Resources Working Group will define the term as they are aware of it and propose that to the Users Committee. SER will also develop a procedure for applying the appropriate codes to make this project work.

   Penny Pearson provided an update on this topic via e-mail subsequent to the meeting (10/15/99). That text is follows:

   "This project is now in my hands and is temporary delayed because we haven't determined yet how to provide this information on the OSUL web site.

   1. items to be coded with ICODE1=6: The public services librarians agreed that this ICODE1 value would be used for non-networked materials such as periodical indexes/abstracting services and full-text reference resources, but not things such as CDs that come with a book. However since the item records will be updated by location staff there's no way to prevent them from using ICODE1=6 for items such as CDs that come with books. I think if we find that a location is using the ICODE1=6 value in a way we hadn't intended we'll have to remind them.

   2. How to provide a list for non-networked databases for the public: I proposed to the public service librarians that I run a boolean to collect bib records that have item records with ICODE1=6 and this list be linked to from the By Subject and By Title lists of databases on our web site. The public services librarians didn't like this approach because the patron doesn't care whether a database is networked or non-networked and wouldn't think to look at a separate list -- and I have to agree with them.

   The public services librarians would prefer to have these titles listed in the By Subject and By Title html pages. Gay doesn't want to do this because of the maintenance of those pages. We postponed the whole project until Stephen Westman started. One option is for him to create a database that creates the html pages for our web site on-the-fly. This is an idea Karen had but never had the time to do. Stephen could include the non-networked databases in this database he creates. I discussed this project briefly with Stephen so he's aware of it. He said it would be possible to write a script that compares the results of my boolean with his database so new additions and deletions could be identified easily. I think this project is a lower priority Let me know if you need more information/details."

   Outcome: This will be moved to the pending list until its priority is changed.

   
   8. E-Resources Working Group (Davis, Scott)

   Summary: A working group on e-resources was appointed to investigate a series of issues related to the cataloging and public display of electronic resources. The working group presented two proposals at the 6/3 meeting: Cataloging Web Sites on OSCAR and Providing OSCAR Records for Titles Contained in a Aggregated Database (such as Periodicals Abstracts). There was considerable discussion of both of these issues. Although the proposals were approved with revisions at the meeting for further discussion with public services, subsequent discussion occurred after the meeting. As a result, Carol Diedrichs referred both of these proposals back to the working group for further discussion.

   Expected Outcome: hear report from working group

   
   
   

   

   
   

   Document last revised: 6/21/06
   Return to TSC Menu of Agendas and Minutes
   
   BACK TO TOP