The copy cataloging assignment LIS512

Introduction

Copy cataloging means copying records made by other catalogs into yours. Later you can then modify them.
The copy-cataloging assignment explores the usefulness of records found in catalogs that are open to Z39.50 searches.

The process

Technically, the process works by conducting searches on the Z39.50 targets that are available in koha. If you come across another target you want to search, I can add it. The search will consult all select Z39.50 targets. The more targets you select, the longer the search will take.
You are supposed to item to be copy-cataloged in hand. If you can’t find enough items in your own private collection, I suggest you contact your local public library.
The two fields you absolutely have to change is 003 and 040$d. They have to be set to the code inofficial (unfortunately) agency code lis512. If there is already a set of 040$d, you can add a new one by clicking on the first icon on the left, to say you have made additional changes to the record. If 040$c is blank also record lis512 there.
Set your own control number in field 001. This code should start with you library code. This is the same as your login to koha. It sholud be followed by an underscore (_) to increase readability. This if your login is "libertarian", your control number should start with libertarian_. What you put after that is up to you. Avoid a blank in the code.
Set your own control number in field 001. This code should start with you library code. This is the same as your login to koha. It sholud be followed by an underscore (_) to increase readability. This if your login is "libertarian", your control numbre should start with libertarian_. What you put after that is up to you. Avoid a blank in the code.
After you save the record about the manifestation, you are passed to the items screen. There you should place the item in your library. If you are like me, you will put a bar code that reminds you where you have the item in your personal collection.
Copy-catalog five item. Try to use the same source of records throughout.

The documentation

The documentation should be short, about two pages.
When you write the documentation, don’t describe the record. I can lookup the record myself, and look at it. So I don’t need you tell me anything about it.
You can organize the report per item, or per MARC field.
The aim is to assess the record. Consider the following
When you make observations about a record, it is assumed that you did not change it. If you make changes to the record, record this explicitely in your documentation.

Written by Thomas Krichel, last updated 2010‒11‒24.

Valid XHTML 1.0!