Data Migr Accept Ws

ILCSO Voyager Migration
Data Migration Acceptance Testing
Worksheets for ILCSO Libraries
ILCSO Voyager Migration...................................................................................................................................................................................................................1
Data Migration Acceptance Testing...................................................................................................................................................................................................1
Worksheets for ILCSO Libraries.....................................................................................................................................................................................................1
Instructions....................................................................................................................................................................................................................................2
Authority Records........................................................................................................................................................................................................................4
Bibliographic Records..................................................................................................................................................................................................................8
MFHD Records...........................................................................................................................................................................................................................11
Item Records................................................................................................................................................................................................................................17
Vendor (Supplier) Records........................................................................................................................................................................................................23
Patron (Borrower) Records........................................................................................................................................................................................................26
Charge Transactions...................................................................................................................................................................................................................31
Fine Records................................................................................................................................................................................................................................34
Recalls...........................................................................................................................................................................................................................................37
Instructions
• Use these worksheets to collect good “test cases” for your library’s data migration to Endeavor Voyager. These worksheets are for your benefit.
Use them in whatever way makes most sense at your institution. They do not need to be returned to the ILCSO Office. The time each library
will have for data verification will be very brief: five working days for the Bib/MFHD/Item data load, another five working days together for
the Patron and Vendor data loads; two working days altogether for the Circ Transactions, Fine/Fee, and Hold/Recall data loads. Clearly, the
more you prepare in advance, the better. (For more information about the project timeline, please see
http://www.ilcso.uiuc.edu/web/reports/staff/draft_timeline.html.)
• The Voyager Implementation Steering Committee has suggested some “notable features” of which libraries might want to collect examples.
Feel free to collect more than one example of each “feature.”
• If you believe your library has examples of one of the suggested “features” but you are unable to locate them, contact the ILCSO Office. It
might be possible to locate example records through a custom report.
• If your library does not have a record with one of the suggested features—for instance, if you do not happen to have a MFHD with more than
250 items attached to it—don’t worry about it.
• Use the blank rows to note additional records you want to scrutinize, particularly if there are additional “notable features” not suggested in
the table. Feel free to enlarge the table, or to make additional copies of it.
• VISCom suggests that you use the “Premigration comments” column for reminders to yourself about what you will be looking for. For
instance, if the “notable feature” is that the bibliographic record contains diacritics, use the “Premigration comments” column to record
exactly which diacritics appear in which fields. Then use the “Postmigration comments” column to record any problems or inconsistencies
you encounter. Your library may chose to record the date in each row, or just once on each worksheet. Likewise, your library may choose to
record the initials of the tester, or simply to place a ✔in the final column when the example record has been scrutinized within Voyager.
• Refer to http://www.ilcso.uiuc.edu/Web/Reports/staff/draft_timeline.html for a timeline and to
http://www.ilcso.uiuc.edu/web/voyager/conversion/voyager_data_conversions.html for the data conversion specifications, so that you can
know what to expect as you test. (For instance, at the time item records are loaded initially, Voyager will not show which ones are charged.
Charge information will be loaded in a later step; items’ route status will not be converted, but items in route in DRA should be checked in
Voyager, to make sure their route status did not confuse the data extract.)
• When you look at your selected records in Voyager, remember to look at them through one or more of the staff clients, as appropriate, not
through WebVoyáge.
Data Migration Acceptance Testing: ___________________________________________________________________________ page 2
(institution / date)
• With the exception of authority records, whichs will not actually be converted, but will be loaded “fresh” from LCSH data sets into Voyager, all
data types described in these worksheets will be available for viewing in their preVoyager condition in the DRA test system. The DRA test
database will contain a snapshot of your data as they looked when they were extracted. Before reporting a problem with a record, please use
the DRA test system to check the condition of the record before it was extracted. Did the problem predate the extract and conversion? For
information on how to connect to the DRA test system, see http://www.ilcso.uiuc.edu:591/dratest/search.htm.
• If you do encounter any problems or inconsistencies in the migrated data, report them immediately to the ILCSO Office
(oncall@listserv.ilcso.uiuc.edu). Be sure your email includes the DRA DBCN(s) (if applicable) and the Voyager Record Number(s), as well as a
description of the problem.
Authority Records
# Notable Features DRA Premigration comments / Voyager Postmigration comments / date ✔ /
DBCN date Record No. initials
1. a subject authority record for a
heading used by one of your
bibliographic records
2. a subject authority record for a
heading not used by one of your
3. a subject authority record with a
“see” reference
“see also” reference
scope note
topical subdivision
geographic subdivision
8. a subject authority record with
an historic subdivision
9. a subject authority record that
contains diacritics
10. a name authority record for a
heading used by one of your
Authority Records
heading not used by one of your
personal name
corporate name
conference name
15. a name authority record with a
“see” reference
“see also” reference
scope note
18. a name authority record that
contains diacritics
19.
20.
21.
Authority Records
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
Authority Records
33.
Bibliographic Records
1. a “Marcette” or particularly
brief bibliographic record
2. a particularly long bibliographic
record—one that contains many
fields
3. a record that contains a few
particularly long fields
4. a record that contains repeated
fields
5. a record that contains an 856
field
6. a record that contains diacritics
in a heading field
7. a record that contains diacritics
in a note field
8. a record at encoding level 8
9. a record for each type and bib
level combo (am, as, gm, etc.).
Use extra worksheet rows.
10. a “preformatintegration”
record
11. a “postformatintegration”
record
12. a record that contains 9XX fields
13. a record from a Major
Microform set or other special
onetime batch load
14. a record from Marcive or other
regular supplier of records
15. a record that contains CJK data
in an 880 field
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
MFHD Records
1. a particularly brief MFHD
record—one with nothing but
an 004 and an 852 field
2. a particularly long MFHD
record—one that contains many
fields (250+ items, for instance)
3. a “typical” type v MFHD
4. a “typical” type x MFHD
5. a “typical” type y MFHD
6. a record that contains a locally
defined call number
7. a record that contains a call
number with special characters
in it (e.g., colon for translation)
number prefix in 852 $c
MFHD Records
number prefix in 852 $k
10. a record that contains call
number prefixes in 852, both $c
and $k
number suffix
12. a record that contains an LC call
number
13. a record that contains an NLM
call number
14. a record that contains a Dewey
call number
15. a record that contains a SuDoc
call number
16. a record that contains no call
number
17. a record that contains an explicit
“copy 1”
18. a record without an explicit
copy number
19. a record for multiple single
volume copies
MFHD Records
20. a record for one multivolume
copy
21. a record for multiple multi
volume copies
22. a record with a URL in the 866
field only (URL first thing in its
subfield—no prefatory text)
field only (URL not first in its
subfield due to prefatory text)
field only
25. a record with identical URLs in
the 856 and the 866 fields (no
prefatory text in 866)
field that is different from the
URL in the 866 field
27. a record with multiple 856 fields
28. a record with data in the 856
other than “http...” (gopher, ftp,
etc.)
29. a record with a summary
holdings statement
30. a record with multiple levels of
chronology
MFHD Records
31. a record with multiple levels of
enumeration
32. a record with complex holdings,
in which the sequence of
display is very important
33. a record with barcoded items
34. a record with pseudobarcoded
items (38888 . . . )
35. a record with unbarcoded items
(H . . . )
36. a record linked to multiple
37. a record containing a 987 field field should be stripped; a final

OCLC backload will be made
from DRA after extract
38. a record containing a 988 field field should be stripped
39. a record with a copylevel public
note
40. a record with an itemlevel
public note
41. a record with a copylevel staff
note
MFHD Records
42. a record with an itemlevel staff
note
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
MFHD Records
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
MFHD Records
64.
65.
66.
Item Records
1. a barcoded item
2. an unbarcoded item
3. a pseudobarcoded item
(38888 . . . )
4. an item with volume
enumeration
5. an item with an explicit copy
number in the enumeration
field
6. an item with a nonzero price
Item Records
7. an item with a price of $.00
8. a claims lost item
9. a noncirculating item
10. an item with a circ note
11. an item on reserve
12. an item linked directly to a bib
record (no MFHD)
13. an item formerly on reserve
(reserve record deleted but not
expunged)
14. an item in route
15. an item whose “owning”
location is different from its
“permanent” location
16. a record with many
“transactions” tallied
17. a record with zero
“transactions” tallied
Item Records
18. an item linked through a MFHD
to more than one bibliographic
record
19. an item marked damaged
20. an item marked missing
21. an item marked claims returned
22. an item marked withdrawn
23. items with multiple statuses
(damaged+withdrawn, etc.).
Use extra worksheet rows.
24. an item that has been “library
loaned” from one DRA agency
to another
25. an item for each DRA location
DRA material type pair on your
library’s ABBA table
26.
27.
28.
Item Records
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
Item Records
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
Item Records
51.
52.
Vendor (Supplier) Records
1. a record with just one address
for all purposes (ordering,
claiming, etc.)
2. a record with multiple
addresses for various purposes
3. a record with a single customer
account number
4. a record with multiple customer
account numbers
5. a record used for placing orders
6. a record never used for placing
an order
7. a record used in Acquisitions
8. a record used in Serials
9. a record containing EDI
information
10. a record indicating
“prepayment required”
11. a record in which the vendor
name contains nonalpha
numeric characters (&, , etc.)
12. a record in which the vendor
code contains nonalpha
numeric characters (&, , etc.)
13. a record with a name or address
that should include diacritics
14.
15.
16.
17.
18.
19.
20.
21.
22.
Patron (Borrower) Records
1. one record for each DRA
borrower class. Use extra
worksheet rows.
2. a libraryuse ID
3. a record for an institutional
borrower
4. a record with data in both the
“Last [Name]” and “Institution
Name” fields
5. a record with multiple
addresses
6. a record with a note
7. a manually delinquent record
8. a record without an SSN
9. a record with a previous ID
10. an expired record
11. a record with an email address
12. a record for which a duplicate
exists in the DRA patron file
(multiply affiliated?)
13. a “fine exempt” record
14. a record with a twoline address
15. a record with a oneline address
16. a record with an employer
address
17. a record with a secondary
address
18. a record with a guardian
address
19. a record with two or more
addresses
20. a record with a fax number
21. a record with a middle name
22. a record with punctuation in the
name (a hyphen, a period after
an initial, etc.)
23. a record with a title (Miss, Dr.,
etc.)
24. a record with a suffix (Jr., III,
etc.)
25. a record for each statistical
category your library uses
26. an unverified record
27. a record in which the primary
library is different from the
registration library
28. a record for each borrower ID
type used in your library (SSN,
barcode type 1, barcode type2)
29. a record with a PIN
30. a record without a PIN
31. an expired record that will not
have been purged
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
Charge Transactions
34. a charged item
35. a charged/mailed item
36. an overdue item
37. a case where only one of several
items attached to a single
MFHD is charged
38. a case where all items attached
to a single MFHD are charged to
the same patron
39. a case where all items attached
to a single MFHD are charged,
to different patrons
40. a case where many (100+) items
are charged to a single patron
41. an item that has been renewed
42. a recently discharged item (in
the “shelving” status at the time
of the extract)
43. an item charged to a patron
affiliated with another ILCSO
library
Charge Transactions
44. an item charged to an ILLINET
library
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
Charge Transactions
55.
Fine Records
1. a record for an overdue fine
2. a record for some other kind of
fine
3. a record for a partially forgiven
fine
4. a record for a partially paid fine
5. a record for a positive balance
(money owed to borrower)
6. a record for an unpurged fine of
less than $1.00
7. a record for a fine of more than
$100.00
8. an instance of multiple fines for
the same borrower
9. an instance of multiple fines for
the same item (different
borrowers)
10. a record for a fine owed your
library by a patron affiliated
with a different institution
Fine Records
11. a record for a lost book fee owed
your library by an ILLINET
library
12. a record for a fine one of your
patrons owes to another ILCSO
institution
13.
14.
15.
16.
17.
18.
19.
20.
21.
Fine Records
22.
Recalls
1. a recalled item with no request
on it
2. a recalled item with a request on
it
3. a patron for whom an item was
recalled
4. a patron from whom an item
was recalled
5. a patron for whom more than
one item was recalled
6. a patron from whom more than
one item was recalled
7. a recalled item with more than
one request on it
8. a recalled item on hold for pick
up
9. a patron with one recalled item
on hold for pickup
10. a patron with more than one
recalled item on hold for pick
up, all at one pickup location
Recalls
recalled item on hold for pick
up, at various pickup locations
12. a recalled requested item from a
DRA “unclaimed” list
13. an overdue recalled item
14. an item of yours recalled for a
patron affiliated with another
ILCSO institution
15. a patron with an overdue
recalled item
overdue recalled item
17.
18.
19.
20.
21.
Recalls
22.

Data Migr Accept Ws

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Migr Accept Ws

Uploaded by

Copyright:

Available Formats

ILCSO Voyager Migration

37. a record containing a 987 field field should be stripped; a final

You might also like