I-Share Voyager Migration

Data Migration Acceptance Testing

Worksheets for New I-Share Participating Libraries

Instructions ................................................................................................................................................................................................................................... 2
Authority Records ....................................................................................................................................................................................................................... 4
Bibliographic Records ................................................................................................................................................................................................................. 7
MFHD or other Holdings Records .......................................................................................................................................................................................... 10
Item Records ............................................................................................................................................................................................................................... 15
Patron (Borrower) Records ....................................................................................................................................................................................................... 21
Charge Transactions .................................................................................................................................................................................................................. 26
Instructions
• Use these worksheets to collect good “test cases” for your library’s data migration to 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 CARLI Office. The time each library will
have for data verification will be very brief. The more you prepare in advance, the better.
• This document suggests some “notable features” of which libraries might want to collect examples. Feel free to collect more than one example
of each “feature.”
• 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.
• If your library does not have a record with one of the suggested features—for instance, if you do not happen to have a bib record with more
than 100 items attached to it, or a National Library of Medicine call number—don’t worry about it. Feel free to skip any entries in the
worksheets that are not applicable to your data.
• Be aware of what record types your library has opted to migrate. For instance, most libraries will not actually convert their authority records;
authority records will be loaded “fresh” from Library of Congress data files into Voyager. For these libraries, it will not be relevant to select
sample authority records from the current local system to be used during the data conversion verification testing. Also, this document
assumes that the only conversions the new I-Share libraries will do are the “standard” Voyager data migrations, and not any of the optional
loads.
• If your library will not convert any MFHDs (and will instead create new MFHDs as part of the conversion), you will not need the worksheet
section on MFHDs at all. Data elements that Voyager stores in the MFHD (such as the call number) are also in the item record section of these
worksheets. You should examine both the Voyager item record and its associated MFHD record during your data review process, to verify
that the MFHD was created properly.
• You can use the “Current System Record No.” column to record the number that you will use to search for the example records during the
review. The different types of records being converted will use different data elements for searching. The most efficient search for
bibliographic records is the Original System Number (the bib record control number from your current local system that is mapped to the 035
$9 in Voyager bib records). For item records, the most efficient search is the item’s barcode number. For patron records, the most efficient
searches are by patron barcode or Institution ID. For the charge transactions, the most efficient search is the patron’s barcode.
• You can use the “Pre-migration 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 “Pre-migration comments” column to record exactly which diacritics
appear in which fields. Then use the “Post-migration comments” column to record any problems or inconsistencies you encounter. Your
library may choose 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 CARLI's timeline and data review FAQ documents (http://www.carli.illinois.edu/products-services/i-share/newmem), so you
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; if your current local system supports item routing, items’ route status will not be converted,
but you should examine item records in Voyager for items in route in your current local system, to make sure their route status did not
confuse the data extract.

Data Migration Acceptance Testing: __________________________________________________________________________ page 2

(institution / date)
• 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 the public catalog(s).
• After data have been extracted from your current local system, do not edit them in your current local system. You need to be able to compare
data-as-extracted with data-as-converted.
• If you do encounter any problems or inconsistencies in the migrated data, report them immediately to the support team at Ex Libris. CARLI
Office staff also receive all email posted to Ex Libris' email distribution list. Be sure your email includes the Voyager record number(s) as well
as a description of the problem. If possible, also include record numbers from your current local system.

Data Migration Acceptance Testing: __________________________________________________________________________ page 3

(institution / date)
Authority Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
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
bibliographic records
3. a subject authority record with a
“see” reference

4. a subject authority record with a

“see also” reference

5. a subject authority record with a

scope note (field 680 in the
MARC standard)
6. a subject authority record with a
topical subdivision

7. a subject authority record with a

geographical subdivision

8. a subject authority record with a

chronological subdivision

9. a subject authority record that

contains diacritics

10. a name authority record for a

heading used by one of your
bibliographic records
11. a name authority record for a
heading not used by one of your
bibliographic records

Data Migration Acceptance Testing: __________________________________________________________________________ page 4

(institution / date)
Authority Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12. a name authority record for a
personal name

13. a name authority record for a

corporate name

14. a name authority record for a

conference name

15. a name authority record with a

“see” reference

16. a name authority record with a

“see also” reference

17. a name authority record with a

scope note

18. a name authority record that

contains diacritics

19.

20.

21.

22.

Data Migration Acceptance Testing: __________________________________________________________________________ page 5

(institution / date)
Authority Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
23.

24.

25.

26.

27.

28.

29.

30.

31.

32.

Data Migration Acceptance Testing: __________________________________________________________________________ page 6

(institution / date)
Bibliographic Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
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 “pre-format-integration”
record (no 006 or 007 fields)

11. a “post-format-integration”
record (a record with an 006 and
007 field)

Data Migration Acceptance Testing: __________________________________________________________________________ page 7

(institution / date)
Bibliographic Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12. a pre-RDA record for an
electronic resource (a record
with a GMD)
13. an RDA record for an electronic
resource (a record with 33X
fields)
14. a record that contains 9XX fields

15. records for a bound-with (two

or more bibs linked to one
holding or item record)
16. a record from a Major
Microform set or other special
one-time batch load
17. a record from Marcive or other
regular supplier of records

18. a record that contains CJK data

in an 880 field

19. a record to which a large

number of item records are
attached (perhaps 100+ items)

20. a record to which no item

holdings records are attached

21. a record with a 10-digit ISBN

Data Migration Acceptance Testing: __________________________________________________________________________ page 8

(institution / date)
Bibliographic Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
22. a record with a 13-digit ISBN

23. a record with an 8-digit OCLC

control number

24. a record with an OCLC control

number of less than 8-digits

25. a record with a 9-digit OCLC

control number

26. a record without an OCLC

control number

27. a record with data other than

the OCLC number in 035 $a

28. a record with data in 035 $z

29.

30.

31.

32.

Data Migration Acceptance Testing: __________________________________________________________________________ page 9

(institution / date)
Bibliographic Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
33.

34.

35.

36.

37.

38.

39.

40.

41.

42.

Data Migration Acceptance Testing: __________________________________________________________________________ page 10

(institution / date)
MFHD or other Holding Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
1. a particularly brief holding
record (e.g., a MFHD with just
an 004 and an 852 field)
2. a particularly long holding
record—one that contains many
fields (250+ items, for instance)
3. a “typical” type x MFHD

4. a “typical” type v 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)
8. a record that contains an [Prefixes in Voyager are not
indexed call number prefix indexed]

9. a record that contains an

unindexed call number prefix

10. a record that contains both an

indexed and an unindexed call
number prefix
11. a record that contains a call
number suffix

Data Migration Acceptance Testing: __________________________________________________________________________ page 11

(institution / date)
MFHD or other Holding Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12. a record that contains an LC call
number

13. a record that contains a Dewey

call number

14. a record that contains an NLM

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

20. a record for one multi-volume

copy

21. a record for multiple multi-

volume copies

22. a holdings record with a URL in

a field other than 856 (MFHD
866?)

Data Migration Acceptance Testing: __________________________________________________________________________ page 12

(institution / date)
MFHD or other Holding Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
23. a MFHD record with a URL in
the 856 field only

24. a record with multiple 856 fields

25. a record with a summary

holdings statement (866 field)

26. a record with multiple levels of

chronology

27. a record with multiple levels of

enumeration

28. a record with complex holdings,

in which the sequence of
display is very important
29. a record with barcoded items

30. a record with pseudo-barcoded

items (system-supplied
barcodes of some sort )
31. a record with unbarcoded items

32. a record linked to multiple

bibliographic records (a bound-
with)
33. a record with a copy-level
public note

Data Migration Acceptance Testing: __________________________________________________________________________ page 13

(institution / date)
MFHD or other Holding Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
34. a record with an item-level
public note

35. a record with a copy-level staff

note

36. a record with an item-level staff

note

37.

38.

39.

40.

41.

42.

Data Migration Acceptance Testing: __________________________________________________________________________ page 14

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
1. a barcoded item

2. an unbarcoded item

3. a pseudo-barcoded item
(with a system-supplied or
“dummy” barcode )
4. an item with volume Also verify MFHD record
enumeration

5. an item with an explicit copy Also verify MFHD record

number in an enumeration field

6. an item with a non-zero

replacement price recorded

7. an item with a replacement

price of $0.00 recorded

8. a non-circulating item

9. an item with a circ note

10. an item linked directly to a bib Also verify MFHD record

record (no intervening holdings
record)
11. an item formerly on reserve
(“inactive” reserve or record
flagged for later deletion)

Data Migration Acceptance Testing: __________________________________________________________________________ page 15

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12. an item whose “owning” Also verify MFHD record
location is different from its
“permanent” location
13. an item whose “permanent” Also verify MFHD record
location is different from its
“temporary” location
14. a record with many historical
circulation transactions tallied

15. a record with zero historical

circulation transactions tallied

16. an item linked through a Also verify MFHD record

holding record to more than one
bibliographic record
17. an item linked directly to more Also verify MFHD record
than one bibliographic record

18. an item marked damaged

19. an item marked missing

20. an item marked claimed lost

21. an item marked claimed

returned

22. an item marked withdrawn

Data Migration Acceptance Testing: __________________________________________________________________________ page 16

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
23. an item marked en route or in [en route or in transit status is not
transit converted]

24. items with multiple statuses

(damaged+withdrawn, etc.).
Use extra worksheet rows.
25. an item for each location-item
type pair on your library’s
ABBA table
26. a record that contains a locally Also verify MFHD record
defined call number

27. a record that contains a call Also verify MFHD record

number with special characters
in it (e.g., colon for translation)
28. a record that contains a call Also verify MFHD record
number prefix (add additional
examples for all prefixes used)

29. a record that contains a call Also verify MFHD record

number suffix (add additional
examples for all suffixes used)
30. a record that contains an LC call Also verify MFHD record
number

31. a record that contains an NLM Also verify MFHD record

call number

32. a record that contains a Dewey Also verify MFHD record

call number

Data Migration Acceptance Testing: __________________________________________________________________________ page 17

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
33. a record that contains a SuDoc Also verify MFHD record
call number

34. a record that contains no call Also verify MFHD record

number

35. a record that contains an explicit Also verify MFHD record

“copy 1”

36. a record that contains an explicit Also verify MFHD record

copy number other than “copy
1”
37. a record without any explicit Also verify MFHD record
copy number

38. record(s) for multiple single- Also verify MFHD record

volume copies

39. a record for one multi-volume Also verify MFHD record

copy

40. record(s) for multiple multi- Also verify MFHD record

volume copies

41. a record linked to multiple Also verify MFHD record

bibliographic records

42. a record with a title/copy-level Also verify MFHD record

public note

43. a record with an item-level

public note

Data Migration Acceptance Testing: __________________________________________________________________________ page 18

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
44. a record with a title/copy-level Also verify MFHD record
staff note

45. a record with an item-level staff

note

46. record(s) with complex Also verify MFHD record

holdings, in which the sequence
of display is very important
47. an “on-the-fly” item record Also verify bib and MFHD record

48.

49.

50.

51.

52.

53.

54.

Data Migration Acceptance Testing: __________________________________________________________________________ page 19

(institution / date)
Item Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
55.

56.

57.

58.

59.

60.

61.

62.

63.

64.

Data Migration Acceptance Testing: __________________________________________________________________________ page 20

(institution / date)
Patron (Borrower) Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
1. one record for each “patron
type” or “borrower class.” Use
extra worksheet rows.
2. a library-use ID (e.g. a patron
record for “lost” or “mending”
or “new bookshelf”)
3. a record for an institutional
borrower (e.g., another library)

4. a record with data in both the

personal and institution name
fields, if these are separate
5. a record with a middle name

6. a record with punctuation in

the name (a hyphen, a period
after an initial, etc.)
7. a record with a title (Miss, Dr.,
etc.)

8. a record with a suffix (Jr., III,

etc.)

9. a record with a note

10. a record with multiple notes

11. a record marked “problem

patron” or with blocked
privileges

Data Migration Acceptance Testing: __________________________________________________________________________ page 21

(institution / date)
Patron (Borrower) Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12. a record with data in the SSN [SSN data will not be converted
field to Voyager]

13. a record without an Institution [these records should be rejected

ID by the conversion]

14. a record with a previous or

superseded barcode number

15. a record with more than one

current/active ID

16. a record for which a duplicate

exists (multiple statuses or
affiliations?)
17. a record with a multi-line
address

18. a record with a one-line address

19. a record with two or more

addresses of the same record
type (e.g., temporary)
20. a record with two or more
addresses of different record
types (e.g., permanent and
temporary)

21. a record with an email address

Data Migration Acceptance Testing: __________________________________________________________________________ page 22

(institution / date)
Patron (Borrower) Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
22. a record with a telephone
number

23. a record with a fax number

24. a record with a cell/mobile

phone number

25. a record for each statistical

category your library uses

26. an “unverified” or “inactive”

(but not expired) record

27. a record in which the primary

library/affiliation is different
from the current affiliation
28. a record for each ID type used
locally (barcode with and
without check digit, prefixes,
29. etc.)
an expired record that will not
be purged before migration
(because of charges or fines)
30. an expired record that will be [purged records should not
purged before migration appear in Voyager]

31. a record with the historical

charges counter set to a number
other than zero
32. a record with the claims
returned count set to a number
other than zero

Data Migration Acceptance Testing: __________________________________________________________________________ page 23

(institution / date)
Patron (Borrower) Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
33. a record with the self-shelved
counter set to a number other
than zero
34. a record with the lost items
count set to a number other
than zero
35. a record(s) with any of the
other counts (fields 44-51 in the
Patron SIF) set to a number
other than zero

36.

37.

38.

39.

40.

41.

42.

Data Migration Acceptance Testing: __________________________________________________________________________ page 24

(institution / date)
Patron (Borrower) Records
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
43.

44.

45.

46.

47.

48.

49.

50.

51.

52.

Data Migration Acceptance Testing: __________________________________________________________________________ page 25

(institution / date)
Charge Transactions
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
1. a charged item

2. an overdue item [Status of “Overdue” is usually

not applied during loads, but you
should verify the due date.]
3. a case where only one of several
items attached to a single copy
or title is charged
4. a case where all items attached
to a single copy or title are
charged to one patron
5. all items attached to a single
copy or title are charged, but to
different patrons
6. a case where many (100+) items
are charged to a single patron

7. an item that has been renewed Status of “Renewed” is usually

not applied during loads, but you
should verify the due date.]
8. a recently discharged item (in
the “shelving” status at the time
of the extract)
9. an item charged to a patron
affiliated with another I-Share
library
10.

11.

Data Migration Acceptance Testing: __________________________________________________________________________ page 26

(institution / date)
Charge Transactions
# Notable Features Current Pre-migration Voyager Post-migration comments / date /
System comments / date Record No. initials
Record
No.
12.

13.

14.

15.

16.

17.

18.

19.

20.

Data Migration Acceptance Testing: __________________________________________________________________________ page 27

(institution / date)