ORBIS/Cascades Working Group Home Page (includes group charge, membership and other background information)
Minutes
Non-OCLC record sets
- OSU
- PSU
- Reed
- UW If a non-OCLC vendor supplies 001s, our philosophy up to this point has been to move that number to an 002 field (so all our 001s were only OCLC numbers). We have also always added our own alpha prefix to the 002 for each set (even if the vendor control number began with letters) as a kind of extra insurance, since we were not always sure how unique the vendor's alpha prefix was between sets they sell, let alone uniqueness of prefixes across vendors.
- WU
- UW Non-OCLC Record Sets Policy
Vendor Control Number Stability
Alexander Street Press (American film scripts online, North American women's letter and diaries, Latin American women writers): the 001s for each record remains the same for in all releases of that record for the product. (The same title could appear in different ASP sets and then would have different 001s, a different one for each set.) The 001s are also the same for all customers. There are no plans to alter 001s in foreseeable future. (email to D. Brooking Dec. 15, 2006)
Eighteenth century collections online (ECCO): The 001s are based on the English short title catalog numbers and because of that should be stable and the same for all customers. However, they exactly match the 001s on the microform version of the titles. (D. Brooking: we have kept the microform and electronic records separate in our catalog with the addition of an "e" at the end of the electronic 001s.)
Microlog Canadian microforms: Starting in July 2006, Microlog reports that their 001s will be "assigned by OCLC." Not clear what this means. But they say that the 001s from the pre-2006 records are unique, stable, and the same for all customers. (email to D. Brooking Dec. 18, 2006)
Univ. of Michigan Making of America: The 001s have not proven to be stable, since they are internal system numbers and when the U of Michigan migrated systems, the 001s changed. The stable number is to be found in one of the 035 fields with some kind of prefix containing "moa". Their records are available on an ftp site for download and should be the same for all customers.
Univ. of Michigan Historical mathematics collection: The 001s here look like the stable 035 numbers from Making of America, that is, I assume that these 001s are in fact the stable numbers. Records are available from an ftp site and should be the same for all customers.
U.S. Executive Branch documents (CIS) microforms: Lexis-Nexis reports that the 001s are stable and could be used for merging and overlay. (That must mean that they are also the same for all customers.) (email to D. Brooking, Dec. 18, 2006)
Summit Contribution policy* *This seems to require member libraries to contribute all records they have, with very few exceptions. (I wanted to double check this, since we seemed to be talking about non-contribution as an option [Diana])
P.S. Not included under the exceptions is the case where a member library owns MARC records that it is not licensed to contribute to a union catalog. (Let Alliance know policy should be updated for that?)
Diana's general comments about Standards, Catalog interface environment, Reversibility, Technical capacities, Coordination/communication
General Principles (Draft started by Diana)
1. Use 001 as match/overlay point (INN-Reach software does not offer any other reliable options at this time).
2. Always distinguish non-OCLC 001s from OCLC 001s with an alpha prefix.
3. Need to discover from the vendors of non-OCLC records, if there is a stable and unique control number in the records that would be suitable as a match point and that would be the same for all customers. Such a control number needs to be identified on a case-by-case basis for all non-OCLC record sets.
4. Do as little editing as possible, use the vendor supplied 001s as is whenever appropriate (that is, if it is a stable and unique control number same for all customers and has a unique alpha prefix that will differentiate such numbers from both OCLC 001s and other vendor numbers).
5. Manage and coordinate this effort centrally (Alliance staff only? also a standing subgroup of the Summit Catalog Committee???). Record sets will be reviewed, and appropriate control number strategy identified and documented by the central entity.
6. Adequate communication, publicity, technical and training support needs to be supplied to member libraries to make compliance with the non-OCLC record policy successful.
