Cataloging
Tip: CONNEXION to Aleph
CONNEXION
Client Quick List
1. Toolbar > Options > Export > Create
Folder on
your PC with name you can remember, or ConvertIn
When it
asks:
2. Do you want to be prompted for a filename each time you
first perform an export
Answer: yes to verify your records will go to the right
file. Note: It only asks for the first record
Apply
Close
3. Create/apply constant data for 035 (UND - "OCLC
035")
>035 0028240707
>035 ocm28240707
Note: OCLC
will not permit 035 9 before export; it must be added in Aleph
4. Export
For Acquisitions:
Apply constant data [Ctrl A]
Copy OCLC number
Paste in each 035 field remove
preceding space
Click Export
For Cataloging:
Edit record:
049
validate (can set browser to be
automatic)
control headings - Shift F11,
check series and names that don't control UND policy
Apply constant data [Ctrl A]
Copy OCLC number
Paste in each 035 field check
spacing
Update holdings
Click Export
5. Two methods:
One record at a time
Go to ALEPH steps and complete
record
Go to Explore (right click Start
button)
Find folder where OCLC is set to
export to
Delete file
Multiple records
Go to Explore (right click Start
button)
Find folder where OCLC is set to
export to
Rename each record
Before starting a new cataloging
session, delete all files in the folder
Note: OCLC CONNEXION Client export defaults to appending
multiple bibs to one file.
If you forget to manage the file
names, it will add two bibs or two files together
You can create a new notepad
document by finding the double boxes at the end of the first record and copying
the next record to a new file name.
Then remove the extra bib(s) from
the first file.
ALEPH
Cataloging module
1. Under Edit node (paper and pencil), select: Import
Records
2. Two boxes
[1st box] Click [
] to
find folder with saved bib records ( [ConvertIn] is default )
[2nd box] Use option:
2709 OCLC Conversion
Click Convert
3. Click Edit
- Edit
035 - MUST EDIT
- Add
9 in first indicator of the 035 without ocm
- >035
9 0028240707
- >035 ocm28240707
- Make
any additional editing changes such as contents notes, additional
subjects, series according local policy, etc.
- [OPTIONAL]
On toolbar, go to Edit - Fix Record. Select Perform fixes as
executed when document is updated (INS) - the first option - and apply
it. This will add the OWN field which is required.
- Click
the check box to validate the record
- Review
the messages listed by Aleph
- Errors/messages
- remember this is a statewide file that is being checked. Once someone
in the state accepts a new heading (
new heading in the
list), right
or wrong the message will not come up again. Subsequent libraries for
the same record or other records with the same heading will not get an
error message, even if the heading is wrong.
- NOTE:
some error/messages will be corrected when tables are revised in a few
months when we re-do indexing
- If
there is a message/error in red, it cannot be saved to the server.
Consult a supervisor/reviewer
- If
record could not be totally controlled in OCLC and/or the above errors
cannot be cleared, the record will need to be checked by a supervisor/reviewer.
Typical messages are:
-
is a new heading in the
list.
-
is a new heading, and is not in the authority database. That means it
doesnt word for word match an authority record.
- New headings must be checked for
correct construction. They may be right, but no book has had that exact
heading in ODIN before. If it is not right or you are not sure, follow
step 5.
- NOTE:
a new heading in the AUT, or XYZ, or SULX, or SUB, or SUL these are
all codes used in Aleph to correspond to the MARC21 tag fields it makes
the heading list from. AUT = Author, XYZ = Subdivision, SUL = LC
subject, SUB = general subjects, SUM = MeSH, etc.
- SUB
and no other subject thesaurus is probably a heading for something other
than LCSH or MeSH these couldnt be controlled in OCLC. They need to
be right according to the rules for that thesaurus. Need to be reviewed.
-
If the record was totally
controlled in OCLC, it is likely that most of errors can be dealt with. Typical
messages that can be resolved to complete the record are:
- Duplicate
ISBN when the record is for another library Field 020 with Text
is
a duplicate in the INDEX file. Open the Web OPAC and set Libraries to
UND. Select Expert Search, enter ISBN=########## If it isn't in UND, the message is
about another library's record. If this is UNDs record STOP you have a duplicate
- Field
035
is a duplicate. Select Expert
Search, enter PNO=10-digit OCLC no. (These will be duplicated in the sys
no. LOCATE lines just check the 035 lines) If it isn't in UND, the
message is about another library's record If this duplicates a record
already in Aleph for UND STOP you have a duplicate.
- LDR/17:
invalid value I this is the Enc level "I" and it is valid -
this is okay to override
- Field
tag 019 not valid this is valid and is okay to override
- 035
not valid or first indicator in tag 035 not valid this is okay
- 050,
092, 086, 090, 099 should be new headings except for continuing serials,
bound-withs, etc.
- 050
indicators if you see: 0 or blank
or 4 okay
- 082
ignore
- 086
not in authority - okay
- 090
not in authority okay
- Field
tag 099 not valid this is okay
- 245
new to the TTL list or - not in authority okay
- 246
new to the TTL list or - not in authority - okay
- SUB
plus another subject thesaurus code for the same entry, e.g. SUB and SUL
for the same tag and text ignore the SUB
- 655
7 in check_doc_tag_text this is a table the Cataloger User Group will
need to discuss but for now it is not useful for cataloging if
constructed right, these are okay
- 650
_6 AND 650 _2 we dont use okay
- 653
we dont use okay
- 76X-78X
fields not in authority okay (however, the referred from record does
need to be correct and this field should match that record)
- 936
okay
4. Save to server
5. Use Edit - Record's Triggers - to identify
problems. Supervisors/reviewers will review and correct if necessary.** See: http://www.und.nodak.edu/dept/library/Departments/abc/triggers.htm
6. Create/Edit first item.* If created by a batch load or
in Acquisitions Orders for monographs, there will be one default item record
that will likely need editing. Once "Loader" processes are running,
there may also be a default HOL record.
7. Go to HOL tab and Create/Edit HOL
- If
there is more than one vol. or copy, the additional items must be created
after the HOL is created/edited.
8. For analytics, add LKR ANA to the individual title. Since the ANA will create both up and down,
you create the ANA LKR on the analytic with the $b being the main entry sysno.
Since you will usually being working on the analytics, you will usually being
creating the "up" link via your ANA to the main entry.
Fields to use:
$a ANA
$b 000123456 (Aleph BIB SYS number)
$l ODN01
$n Series title (correct form)
$m Individual work title
Vol. and year can be included in
the LKR ANA
$a ANA
$b 000885603
$l ODN01
$n Workforce.
$m Workforce management. Vendor
directory
$y 2003
$v 82
$i 11
*Create Items and HOL
See also: http://www.und.nodak.edu/dept/library/Departments/abc/MARC21HoldingsCheatSheet.htm
Single monographs use only for things in 1 volume; all others see below
- Use Find
to search for either the SYS number or the OC number. Use Aleph Own
field UND
- Make
sure the bib that displays in the bottom pane is the right bib
- In
the lower right of the bottom pane, click Items
- At
the top right of the top pane, click New
- Enter
appropriate data: On tab 2 -barcode, sublibrary, collection, copy,
material type, item status, processing. On tab 3 item statistics.
- Click
refresh to look for errors
- Add
- Click
HOL links
- Select
Create new this create a HOL record from the item data you entered. If $a
NdU, Sublibrary, Collection or Call number are wrong or missing, they must
be fixed on the HOL record it will update the items linked to it
- Click
Link this will add the call number from the HOL. Make sure the
HOL 852 has the correct first indicator for your type of call number. This
will also appear in the small box after Call no. type/call no. on the
workform
- If
you need to review the HOL that was created correctly, click Edit
- NOTE: the LDR 06 must be x
- Conversion
generated HOL records often miss
a)
008/22-24
is not a valid language code - used the same as bibs
b)
LDR/17 invalid value u should be usually 2 for
books and 4 for serials, but if you use an 866 only it is 3
Multi-part monographs
- Begin
as for Single monographs.
- First
create the first item, create the HOL, THEN create additional items.
- LDR 06 must be entered as v.
Migrated HOL records need to be edited
- When
you click New to create the subsequent items, make sure the HOL
number is in Hol. Link.
- Refresh to
bring in the call number from the HOL record
- Tab
2 must have the Description filled in with holdings according to NISO and
MARC21 Standards following NISO formatting for punctuation. This will be
copied into Description on tab 4
- Tab
5 usually has only enumeration just the numbers
- For
complex holdings, including things like teachers guide, an 866 is to
added to the HOL
Serials
- LDR 06 must be entered as
y
- Must
use 853/853X and tab 5 or 866/7/8
for textual holdings or both
- Refer
to other serials instructions, Cataloging
Tip: Holdings/Description and email on Prediction Setup for Titles
with Harvard Data
** Supervisors/reviewers will need to:
- Check
subject headings for correct order and structure.
- Determine
correct form of access points: personal names, corporate name, conference
names. Determine if NACO work needs to be done and initiate NACO as
appropriate.
- Verify
series is correct according to these sources in this priority order:
Authority file, Serial main entry in ODIN (OCLC if non in ODIN), CFL
established practice