MARCEDIT
Outline:
A. General guidelines
B. Field-by-field guidelines
C. Other functionality
4/4/11spg, rev. 12/3/15
D. Character encoding
E. Do a test load
F. Additional resources
G. Set preferences
A. General guidelines
MarcEdit is a free Windows-based MARC editing tool that provides methods for converting MARC to text and doing many
other things. It was created by Terry Reese of Ohio State University. He maintains very useful listserv (MARCEDIT-L)
and website and also produces how-to videos on YouTube. The MarcEdit main screen looks like this:
Some tasks must begin from this screen but most are done within a .mrk file
Immediately after importing a file of records, check for spaces in the file name since they prevent a file from loading. If
spaces are present, convert them to underlines (_).
Create a MarcEdit file
1. Double-click your file of MARC records (.mrc). The MARC Tools screen comes up. With MarcBreaker
selected, click Execute. Check to see if the expected number of records is reported.
2. Click Edit Records:
The .mrk file has already been saved in the same folder as your .mrc file. While editing you can save the file at
any time. If you attempt to exit without saving you will be asked if you want to save your changes.
MarcEdit -- p. 2
General MarcEdit practices













Verify record counts at the beginning and end (more often if a very large file) by clicking Report--Field Count. The
count of 000’s, 001’s, and 245’s should be the same as there can be only one of each field in a record. If not, see the
001 field under Field-by-field guidelines, below.
There may be multiple formats in a file but load the whole thing in accordance with the predominant format. If there is
any question about predominant format, check it by clicking Reports--Material Type Report.
Use validation prior to editing and when done by clicking Report--MARCValidator. See MARCEDIT VALIDATION
guidelines. You cannot toggle back and forth between the validation report and the records. If needed, copy the
validation report to the clipboard or print out.
Check a URL or two to see if they go directly to the resource. If not consult with the E-Resources Librarian.
Determine if records have unique and consistent identifiers to within the file and to facilitate record replacement later
on. See the 001 and 003 fields, below.
The count of changes that pops up after each action, may be higher than expected. It's because it counts the actions
on each field instead of the number of times that field appears.
Use Edit--Find All to find inconsistencies in fields, and after editing to make sure you haven't missed anything. If you
spot a pattern of inconsistencies you can address them in batch. If desired, click “Found Text” to sort by tag and text.
Note that plain old Find only works on the 100 or so records that are onscreen at any one time. Use Find All to find
all records.
When using Edit--Find All, results appear in a Results new window and you can toggle between it and the records.
This is not the case with MarcValidator, unfortunately.
Use Tools--Add/Delete Field to delete a field. Do not use Find--Replace with a blank Replace as that will mess up
your file
Use Tools--Sort By--Sort All Fields if needed to put fields in numerical order
Use Edit--Special Undo if you need to undo your previous action. It can be used only once, but you can use regular
Undo if you have only a few.
If you have a .mrk file you’ve been working on and you open the original .mrc file again, it will overwrite your edited
.mrk file. If you want to view the original .mrc file, rename the edited .mrk file first.
After editing a file of records from a new vendor, load a test record or two to make sure that characters translate
correctly and you've chosen the right Bulk Import Rule. See more about testing records below.
*Records occasionally disappeared fully or in part. To be safe when working on a large file or one with long, complex records such as sound files,
check the field count after every action or two. If there are suddenly fewer records:

If records were lost due to your most recent edit, and you have not yet saved the file, do Edit--Special Undo and check the count
again. If still short, close the file without saving, open it again, and check to see if the number is okay. If so, continue editing.

Otherwise, use WinMerge to compare the file with the original version (which you’ve kept, of course!). See WINMERGE
GUIDELINES. After WinMerging, edit the restored records in your .mrk file as needed.

Or, delete the file as edited so far and start over again from your original file
What fields are worth correcting and adding? Physical resources will be in the catalog forever and it is worth editing
those. E-resource discovery and access will likely be accomplished through other means in the future. For e-resources
concentrate on impediments to batch processing and obsolete fields that may not index well in Voyager:









Non-unique 001’s and/or 003+001 combinations within a record set
Numeric-only 001’s or 035’s which can lead to mistaken overlays in Voyager
Inconsistent URLs or URLs that don't go to the right place. Long URLs that need a |z (or |3)
MARC record structure errors such as incorrect headers, multiple 1XX or 245 fields, multiple |b’s in 245’s, etc.
Missing data that will seriously affect retrieval in the catalog. Make an added entry for the set, usually 830.
Sometimes a different or additional access point is needed, e.g. MyiLibrary is a service rather than a title so it is
entered in a 710.
Change 440's to 490/8XX's because 440's are not in the Voyager series index
Except as noted above, generally, do not edit coded fields (00x, 0XX) or add notes, subject headings, or added
entries
If all or some records have call numbers, turn them into “ELECTRONIC” ones. Don’t add a set call number.
Don’t use “ELECTRONIC …” by itself, i.e. without a call number; better to have no call number.
Follow the specific LOAD guidelines for each record set
When might a complete reload of records be necessary? A complete reload might be called for if:

Record counts are out-of-sync. For instance, a vendor website might say there are a certain number of records in
the complete collection but the catalog has quite a few more or less than that (assuming the loads are up-to-date).
MarcEdit -- p. 3


It’s relative, of course. For a large collections, a small number of records (sometimes a fairly large number,
depending on the set--see the individual guidelines) do not make a difference. For small collection, those few
records are critical. In either case, purchased sets require more scrutiny than subscriptions, and subscriptions
more than free resources.
Records loads are significantly far behind. While you can catch up file-by-file or combine the individual files into
one using MARCjoin, you can also reload the entire collection.
There is concern about the quality of older records vs. new.
If there is a possibility that records may replace correctly, delete the existing records first. One way to identify them is
via an Access query based on operator ID. Copy the results into Excel (saving the file, or not). Copy the bib IDs to a
text file and delete the column header. Use the file of bib IDs to delete records using BibDelete.
B. Field-by-field guidelines
Check record numbers (001 and 003)
001 (record control number) and 003 (MARC code for the organization) must, together, comprise a unique set of
characters in the catalog. Each one alone need not be unique. When records are loaded into the catalog the 003
+ 001 become an 035 field, e.g. “(CaSfKAN)kan1139607”
If 001’s are all-digits, insert distinguishing letters in front, except for OCLC numbers. For instance, insert “spr”
before Springer record numbers. It is not desirable to have number-only record numbers in the catalog as it may
lead to mistaken overlays.
As needed, check earlier files of records or the catalog to see if the pattern of record numbers is consistent from file to file.
In the local catalog the 001 and 003 are combined into an 035 field, e.g. (OCoLC)ocm15654523 or
(CaONFJC)cis16839258. Some vendor files may only have 001 fields, or none at all, and you will have to create unique
ones.
If the record count shows multiple identical 001’s use Tools-Record Deduplication to identify them. Check the
file that is generated by this process and and be glad if it’s empty. Do the same for other fields if needed, e.g.
when you are dealing with a new vendor or the individual LOAD guidelines say to.
OCLC records:
 Record numbers are fine as is
Vendor records:
 Edit 001's as needed to comprise distinctive combinations of text and digits, e.g.:
ASPS00000139/bwld (fine as is)
spr978-3-540-74275-3 (was just the numeric)
 Add/edit 003’s as needed to make them distinctive, e.g.:
VaAlASP
(fine as is)
SPRINGEREB
(was just “Springer”)
 Change 035’s to 935’s unless directed otherwise in pertinent LOAD guidelines
 Change 019’s to 915’s unless directed otherwise in pertinent LOAD guidelines
OCLC and vendor records are usually loaded using using a bulk import rule that adds/replaces on the 0350 index,
such as EB0350 (Ebook Add/Replace 0350)
Records exported from Voyager:

Reload using bulk import rule BIBR001 which replaces on the BBID (Voyager bib ID) index
For more information see VOYAGER BULK IMPORT RULES AND BIBLIOGRAPHIC DUPLICATE DETECTION
PROFILES
Create an e-book call number in 090 fields (or whatever field you're using for call number)from 050’s:
1. Use Tools--Copy Field Data to copy 050 to 090:
MarcEdit -- p. 4
2. To change 090 $b's to ELECTRONIC BOOK select Edit Subfield Data. Insert values and click Replace Text:
3. Do Find All =090:
 If an 050 lacks |b the 090 will lack ELECTRONIC BOOK. Repeat the above steps but choose "Add
subfield if not present."
 If an 050 has two |a’s the 090 will have the second |a at the end of the ELECTRONIC BOOK call number.
Find All electronic book$a and fix them one-by-one.
4. To change 090 indicators to blank, select Edit Indicators. For the indicators input two asterisks (**) to find all
variations of indicators. For the Replace indicators input two backward slashes (\\). Click Replace:
5. Do Find All =090 one last time to see if there are any remaining problems.
Multiple 050 fields
Check the field count of 001 and 050. More of the latter means more than one 050 in some records.
MarcEdit -- p. 5
If the file is for subscribed content, ignore multiple 050’s. By default the last 050 is put into the MFHD, and for
subscribed content we we don’t really care that much. If the file is for purchased content, decide if having the
best call number makes any difference.
Check the field count of 001 and 050 to see if there are more 050’s. If the file is small you can Find All =050 and
look for records listed more than once. Then delete the unwanted 050 record-by-record or in batch (see below).
If the file is big, it’s hard to identify problematic records by doing Find All. You can give it a try, but it might be
easier to do this:
a)
b)
c)
d)
e)
f)
File--Select Individual Records To Make
Set Display Field to “050”
Click Import File
Enlarge the size of the window and the Display Field column
Look for instances of two call numbers, which will appear in a single row, joined by “|end|”. Alternatively,
you can use the Search box to select records with “|end|” and look for the checked ones.
Check a couple of records to see if you want to routinely keep the first 050 or the second
If you want to keep the first 050 field and delete the second, do this:
Find: (=050.*)\r?\n=050.*/m
Replace: $1
Choose “Use Regular Expressions”
This Find expression is looking for an 050 field followed by any number of characters and captures that field using the parentheses:
(=050.*) until it finds a new line character: \r?\n followed by another 050 field and any number of characters: =050.* Then /m is
used to designate that you are searching multiple fields (or lines)
The Replace expression of $1 is saying to retain the 1st parenthetical expression in the Find syntax, which is the 1st 050 field.
If you want to keep the second 050 field and delete the first, change the parenthetical position, like this:
Find: =050.*\r?\n(=050.*)/m
Replace: $1
Full LC call numbers lacking $b
Although rare in most vendor files, 050 fields may lack $b despite having full LC call numbers. Wes Press
records from EBL are particularly problematic. See LOAD EBL WES PRESS RECORDS guidelines, which may
be helpful in similar situations.
For other vendors you can find problematic 050’s using “$b” followed by “elec,” e.g. 2012$belec. Because you
must fix the records one-by-one, only do it for purchased content and if the number of records is small.
Otherwise, ignore them as call numbers for e-resources are not that critical.
Create a part-specific 090 call number from series |v
1. Use Copy Field Data to copy 830 to a 930 (or some other unique field), retaining the 830:
=830 \4$aThe Dreyfus Affair in the making of modern France ;$vreel 46, item 5.
=930 \4$aThe Dreyfus Affair in the making of modern France ;$vreel 46, item 5.
2. Use Edit Subfield to remove |a:
MarcEdit -- p. 6
Result: =930 \4$aDC354$b.D884 1996$vreel 46, item 5.
3. Replace $v using Find-Replace:
Find:
Replace:
=930 \4$aDC354$b.D884 1996$v
=930 \4$aDC354$b.D884 1996<space>
Result: =930 \\$aDC354$b.D884 1996 reel 54, item 1a.
4. Swap field to 090 and change indicators:
Result: =090 \\$aDC354$b.D884 1996 reel 46, item 5.
5. Remove the period at the end using Find--Replace:
Find:
=090 \\(.*)\.
Replace:
=090 \\$1
Choose Use regular expressions
The (.*) searches for any char, repeated 0 or more times, and saved in a "capture group." The \. says you want
one example of a real character--in this case a period--at the end.
In the replace field, we start with the same prefix =090\\ followed by the contents of the first capture group $1 and
with no additional characters at the end of the string.
Insert $h into 245
As needed, insert $h into 245. This subfield is not valid in RDA but we continue to add it since our OPAC does
not adequately indicate format. When functionality improves, $h can be deleted in batch if desireable. If some
MarcEdit -- p. 7
records have $h and some don’t RDA Helper will not add a second $h to the former. To add, click Tools then
RDA Helper:
For Select choose None, then choose Generate GMD. You will get a confirmation message.
►►MarcEdit will insert a GMD that matches the record’s encoding. Do a Find All for =245 Check to see if any
records are other than “electronic resource.” If so, change them:
Find: $h[videorecording]
Replace: $h[electronic resource]
By the way, the “i” link is to the RDA Toolkit. If you care to view it, you will asked to sign in; see login chart. Other than
that, there are two ways to access RDA Toolkit:

Go to http://access.rdatoolkit.org/. Log in using the account ID and password on our login chart. After logging in
you can set up a personal profile.

You can also set up automatic access within Catalogers Desktop.
Another way to add $h is this:
1. In Edit Subfield:
Field: 245
Subfield: [a,p,n,^c,b]
Field Data: =:/.
Replace with: $h[electronic resource]<space>
Choose Add subfield if not present
Exception: If all the 245’s in your file have no subfields following $a, omit the space after [electronic resource].
This will avoid inserting a blank space before the period at the end of the field.
MarcEdit -- p. 8
How it works. The caret (^) is a special subfield insert tool within MarcEdit meaning "before a subfield." (In
contrast, a caret in a regular expression means "any character except.") To insert at the beginning it’s ^b, at the
end ^e, and in the middle ^c.
Change 440's to 490's and create 830's
1. In Edit--Find input "=440" and click Find All to see if there are 440's, which are obsolete. The most common
fields and coding for series are:
440 \0 (ind2 = # non-filing characters) anpvx
490 1\ (ind1 = series traced differently) avx (no n or p)
830 \0 (ind2 = # non-filing characters) anpvx
See Bib Formats & Standards for others.
2. Use Tools--Copy Field to copy 440 to 830, retaining the 440. The new 830 field is fine as is; don’t bother to
add a period at the end. Notice that the 830 appears immediately following the 440. This is fine but you can also
to click Tools--Sort By--Sort All Fields to put in order. That will re-sort the 050's and 090's, too. If that matters
to you, work with 440's before 090's.
3. Change 440 to 490:
► 490 doesn't use |n and |p, so if you have any you must edit out the subfield codes in the 440 before swapping into a 490. The |n and |p
punctuation will be fine as is. Do Edit--Find All with "=440" to see if you have any.
a) If there are only a few fix them one-by-one by jumping to the record and editing
b) If the exact same 440 appears multiple times, do Find--Replace on the specific 440
c) In more complex situations look for patterns so that you can edit as many as possible with the fewest actions. In this example a main series
called LNCS sublibrary has numerous subsections such as LNCS sublibrary.$nSL 1,$pTheoretical computer science and general issues:
Do Find All "=440." Jump to the first problematic one. Highlight the 440 through $p (this copies it to the clipboard). Go to Find-Replace. The highlighted text has already been pasted into the Find box. Paste it into the Replace box and remove |n and |p and
anything following. Click Replace All:
Find:
=440 \0$aLNCS sublibrary.$nSL 1,$p
Replace: =440 \0$aLNCS sublibrary. SL 1,<space>
Repeat for SL 2, etc. Just change the subsection data each time.
If you remove all the |n's first so you only have to deal with |p. To remove all |n's:
Find:
=440 \0$aLNCS sublibrary.$nSL
Replace: =440 \0$aLNCS sublibrary. SL
MarcEdit -- p. 9
Use Tools--Swap Fields to change 440 into 490. Note the different indicators. Input subfields anpvx in case you
missed any |n's or |p's in a 440:
Don’t bother removing the period at the end
Remove 506's that are basically meaningless clutter to users and/or appear in a minority of records. Add a 506 for
CTW Library Consortium holdings (not Wesleyan alone):
1. Under Tools select Add/Delete Field. Insert values and click Add Field:
2. Add as appropriate, e.g. MyiLibrary PDA/purchase records:
\\$aAccess limited to current students, faculty and staff of the CTW Library Consortium.
We used to add a local 506 \\$aAccess limited to current students, faculty and staff of Wesleyan University but no
longer do that.
Delete non-LC 6XX’s
First do Find All for the various 6XX fields to see if there are non-LC headings. If only a few you can delete them
one-by-one, otherwise follow the batch process below. Records pulled from Voyager may have non-LC 655’s
supplied by SC&A. If so, use the expression that retains 655’s. Certain record sets such as Naxos have non-LC
655’s that we want to retain.
Go to Tools--Add/Delete Field and enter as follows:
Field:
Field data:
6xx
^=6.{5}[^0]
Check Use Regular Expression
Click Delete Field
to do one field at a time enter the specific tag, e.g. 650
to retain existing 655’s use ^=6.[^5].{3}[^0] instead
MarcEdit -- p. 10
This chart of valid indicators and subfields may be useful:
Field
600 Personal name
610 Corporate name
611 Meeting name
630 Uniform title
648 Chronological term
650 Topical term
LC ind 1
0 Forename
1 Surname
3 Family name
0 Inverted name
1 Jurisdiction name
2 Name in direct order
0 Inverted name
1 Jurisdiction name
2 Name in direct order
0-9 nonfiling characters
[blank] Undefined
[blank] No info provided
0 No level specified
LC ind 2
Subfields
0
abcdefghijklmnopqrstuvxyz023468
0
abcdefghklmnoprstuvxyz023468
0
acdefghjklnpqstuvxyz023468
0
0
0
adefghklmnoprstvxyz023468
avxyz02368
abcdevxyz023468
0
aevxyz023468
1 Primary
2 Secondary
651 Geographic name
[blank] Undefined
Add an entry for the set if not already in the records or not in all records
Usually this will be an 830. One exception is MyiLibrary which requires a 710 because there is no title for the set,
only the corporate name. Remember that a series title does not capitalize initial letters unless proper nouns.
Add 852 to put info in the MFHD when adding new records
If the MFHD should have something special such as a note it can be added via an 852 field in the bib record, e.g.:
=852 0\$bomffilm$hAC5$iB44$zTo locate the reel number(s) refer to Underground press collection:
listing of contents, 1963-1985, in OLIN LIBRARY Microforms Area (Reference Book, Ground floor)
The bulk import rule would specify creating a MFHD as well as a bib, and have selected “Copy 852-855, 863-878
Fields From Bib to MFHD”:
MarcEdit -- p. 11
Mapping:
Choose the correct Call Number Hierarchy. In this case, it actually doesn't matter as there are no 050's in the
bibs. We don't have a hierarchy for no call number.
Delete unwanted 856's, retaining only the valid ones
1. First change 856's to 956's. Under Tools select Copy Field Data and choose “Delete Source Field:”
2. To convert valid links back to 856's (in this example, Springer), under Tools select Swap Field Data. Insert
values. In the “Find” box insert something unique in the desired 856’s, usually the beginning part of |u. Here we
MarcEdit -- p. 12
want to find 956's with uhttp://dx.doi.org. You have the option of removing an unwanted |z here or later as a
separate operation. In this example there is an extraneous |z because we already have a useful |3 to display in
the OPAC. Click Process:
Omitting |z leaves a 956 with only the |z, for instance "40$zAn electronic book accessible ," that will disappear
when you delete the 956's later. Alternatively, copy all subfields over and delete |z separately.
Your particular file may already have |3's or |z’s that are fine for OPAC display. If there's just the URL that's fine
unless it's very long, in which case you could create a |z. Check in the catalog or see specific guidelines as to
how those records have been handled in the past. When adding |z be sure to choose New subfield only.
3. To delete the remaining 956's (including any LC ones), select Add/Delete Field. Insert values and click
Delete Field:
Compile into a .mrc file
When all edits are completed, click File--Compile File into MARC. At the end of the file name and before the
extension add “_edited” to avoid confusing your edited file with the original file, e.g.“osophil010113_edited.mrc”.
C. Additional functionality
Select Records for Edit
With your .mrk file open, go to File--Select Individual Records to Edit. This tool allows you to identify records in
order to Generate Report of those records in a comma-delimited file, Export Random records for sampling (not likely
something you’d want to do), or Export Selected records into a .mrk file for further manipulation. At the present time
Delete Selected is grayed out, but there is another way to delete records from a file (see below).
In the following example we have a file of Alexander Street Press “Theater in Video” records within which we want to
identify those records associated with Films for the Humanities:
MarcEdit -- p. 13
In your .mrk file, under File click Select Records for Edit. This image shows the screen already populated in the
steps below it:
Source MARC File. Most likely you want to work on the file you have open. If you want to work on a different file you
can browse for it.
Display Field: Indicate which field or subfield(s) you would like to show in the results. The default is 245$a. Our
example specifies the entire 710 field since this is where Films for the Humanities data appears.
Click the Import File button to see the results for each record.



Results are sorted in the order the records appear in the file. Sort by Display Field if desired.
If a record does not have the field, it will say “Display field not found”
If there are more than one of a field in a record the fields will be concatenated with |end| after each
Notice the check-boxes on the left. While you can select records one-by-one you probably want to use the Search
box to find records with specific data:
In the example we are searching “films for the humanities (firm)” within the data that appears on the screen. Optionally
you can:



Search all Record data, i.e. the full text of the records
Use Regular Expressions.
If you think it will take more than one search to pin down the records you want, Retain Checked Items
To execute the search click the find icon (magnifying glass). You have two options of what to do with the results:

Click Generate Report to get a .txt file of exactly what appears in the displayed results
MarcEdit -- p. 14

Click Export Selected to get a .mrk file of selected records. A new .tmp file appears with just the exported
records--notice the “tmp” file name. Save and rename it so that your original file .mrk remains intact.
Delete Selected Records
To delete selected records you must start at the main MarcEdit screen.
There are two options for deleting. Choose Tools--Select MARC Records. Choose:
 Delete Selected Records, or
 Extract Selected Records (followed by the option to Delete Selected Records):
►►For the first option you are working only with .mrc files. For the second, .mrk files.
The steps are identical to Select Records for Edit described in the previous section except that you have the option to
Delete Selected Records.
MARCSplit and MARCJoin
From the main MarcEdit window, under Tools click MARCSplit to break a very large file into smaller ones or MARCJoin
to join multiple small files into one big one. The first box is where the records are going to, the second box is where
they’re coming from. Adjust Records Per File as needed.
To indicate a certain # of files, click the check box and enter the number of files; under Records Per File indicate how
many records should appear in each file. If a # of records isn't defined, it defaults to 1000. Contrary to expectations, this
option does not create that number of files with your records apportioned among them. Rather, it defines how many files
will be created, each with the number of records you’ve indicated. If you have more records than that they are not
included; if you have fewer records they will fill up each file to the limit, perhaps resulting in fewer files than you indicated.
This seems useful for creating one or more small files records to examine the records and perhaps test them.
D. Character encoding
In MarcEdit you can work with any character set: UTF-8 (Unicode), MARC-8 (non-Unicode), and even Latin-1.
Only the first two support diacritics/special characters. UTF-8 allows all the language scripts supported by
Unicode, while MARC-8 allows the use of Hebrew, Cyrillic, Arabic, Greek, and East Asian scripts. The UTF-8
character set is used in OCLC and some vendor records. To date, most vendor records have been MARC-8.
UTF8 or MARC-8 is indicated in position 9 of the LDR:
For UTF-8 it's a:
1107nam a2200289 a 4500
For MARC-8 it’s blank: 1181oam 22003018a 4500
Position 10 (Indicator Count) is always 2
Position 11 (Subfield Code Count) is always 2
Positions 12-13 (portion of Base Address of Data) are always(?) 00
MarcEdit automatically changes non-Unicode records to Unicode when you compile the file into MARC. The
original mrk file will still show as MARC-8, but if you open the compiled .mrc file in MarcEdit the “a” appears.
When loading a file into Voyager, use a bulk import rule that loads UTF-8.
It can be difficult to tell which symbols/mnemonics in in a MarcEdit file will and will not convert correctly. A test
load is advised for new or problematic files. If they are a major problem through an entire file you can edit all or
some of them in MarcEdit, but it is easier to fix records after they are loaded in Voyager.
MarcEdit -- p. 15
A record will not load if Voyager cannot parse (interpret) a character. The log.imp file will report it as an exception
and the record itself will appear in the corresponding err.imp file for you to follow up. For more information see
“Load” guidelines for the particular set and also POST-LOAD CHECKS.
Now that MarEdit compiles records into UTF-8 the following may no longer be necessary but it is retained here just in case:
Determine if the entire file is UTF-8 by doing Find All for <space>a2200 or MARC-8 by searching <space><space>2200.
If you find a mixture of UTF-8 and MARC-8, change them to be all the same. Normally, you would favor whatever character set appears in the
majority of records, unless you’d lose important Unicode characters:
Scenario 1:
If Find results are exactly what you want to Replace:
Find:
<space><space>2200
Replace: <space> a2200
[This example changes MARC-8 LDRs to UTF-8]
If Find results are a mishmash, edit records one-by-one if there aren’t too many.
Scenario 2 (too many records):
If you have too many records to change, use Select Individual Records to Make or Select MARC Records--Delete Selected
Records to create separate files of UTF-8 and MARC-8 and work with them separately.
E. Do a test load
For new and problematic files, load a few test records to see how they look in Voyager and, if needed, to verify the
character set or identify potential unparsable characters. While you can do this via bulk import, it’s quicker to do it in
the Cataloging module:
1) Copy the record(s) out of MarcEdit, paste into Notepad, and save as .mrk. Open in MarcEdit. Compile into
MARC and save as a .mrc or .dat file.
2) Import but do not save

Our default character set in the cataloging module is UTF-8. If a record is other than that you'll see an error
message: The record character encoding does not match the import format: record skipped. In that case the
records are likely MARC-8. You can test that as well by changing your Cataloging module validation to
MARC-8. When done, remember to change back to UTF-8.

An unparsable character will show as �. If needed, examine the record(s) in OCLC to what the valid coding
is. For online resources view the citation and images. Edit your .mrk file as needed and reload. See POSTLOAD CHECKS for more information.
If there is no bulk import rule that meets your needs you can edit an existing rule in System Administration
(remembering to change it back afterward). Or, ask the Head of Cataloging to create a new rule.
F. Additional resources
MarcEdit help
MarcEdit homepage: http://marcedit.reeset.net/
MARCEDIT-L: https://listserv.gmu.edu/cgi-bin/wa?A0=marcedit-l
Tutorials: Search "marcedit" in YouTube. There are also links from the main MarcEdit screen.
Regular Expression Language Elements: http://msdn.microsoft.com/en-us/library/az24scfc(v=vs.110).aspx
G. Set preferences
Click Tools--Preferences and set as follows. Most preferences are fine as is:
MarcEdit -- p. 16
MarcEdit -- p. 17
▲Adjust Font Size as desired
MarcEdit -- p. 18
MarcEdit -- p. 19
MarcEdit -- p. 20