Mapping TCP texts to MARC records

NOTE: The following comments were true until 2020, when ProQuest shifted EEBO from its ‘legacy’ Chadwyck-Healey platform to its main online platform, and simultaneously released a completely refreshed set of MARC records. We are working with the new records as of this date (August 2020), attempting to overlay our TCP metadata (built on the old EEBO records) onto the new (2020) records, and hoping eventually to emerge with the information necessary to add TCP information to the new records on the same basis as that outlined below. Please stand by!

Most libraries that have EEBO will also have purchased EEBO MARC records from ProQuest. We can provide a map that should allow you to add a link within a given EEBO MARC record to the associated TCP text, where one exists, using the TCP ID number. To generate a link to the Michigan-hosted version of the EEBO TCP files, given a TCP ID number of the form ‘A04486’  (the EEBO-TCP ID numbers all begin with ‘A’ or ‘B’ followed by five numbers), the corresponding link should take the form:

This map associates our internal “TCPid” numbers with STC numbers, ESTC numbers, catalog attributes (Redgrave, Wing, or Thomason Tracts), citation ‘accession’ numbers as supplied in the 001 field of ProQuest MARC records, image-set ID numbers assigned by ProQuest (appearing in the 856 field of ProQuest MARC records), date of publication (normally from DATE1 of MARC), and the number of page images in the EEBO image set.

Although we have made best efforts to map these relationships accurately, the TCP makes no guarantees regarding that accuracy. Because ProQuest continues to catalog, revise its cataloging, to scan, and to re-scan, none of these relationships is absolutely stable. We hope to update this map file periodically.

Download a compressed version of the XML file

Note: In order to read this file, you will need to unzip it and then open it with a text editor.

Unfortunately, the TCP does not have the resources to create new catalog records for each text we produce (though you are welcome to do so, and if you are willing to share them we would be very glad to know about it). We have also not yet produced a comparable map of ID numbers for the Evans and ECCO projects, in part because it is somewhat more difficult to guess which records our users have at their disposal.