Flexible CSV format

We have recently extended the number of fields in the database and made the order of the fields flexible. This lets us include information from (for example) Nonconformist and Catholic registers as well as additional information found in more typical parish registers.

Please note that you need to be a spreadsheet user in order to take advantage of this flexibility — the new fields and format are not available currently for WinREG (or WinFreeREG).

The General guidance has been updated for the new fields — please read and note the changes.

Using the flexible CSV record format

Summary of main features

  • Many more fields are now available — information that you had to put in the Notes field previously is likely to have its own field
  • You can use as many (or as few) of the fields as you need
  • You can have the fields in whatever order works best for your register
  • You put the formal names of the fields you use in row 6 of your spreadsheet — do not delete this row before uploading your CSV file
  • Downloads of the three sets of fields as CSV files are available from the relevant Extended fields page — see the Fields in detail menu

The record layout

This description assumes that you are creating your whole file, including the Header rows, in your spreadsheet app. If you are using a text editor at any stage, see Text editors in General guidance.

FreeREG will know that you are going to use the new flexible and extended format if you put the new header as the fifth row of your spreadsheet (replacing the +LDS header): put # in cell 5A and DEF in cell 5B.

This tells the system that the next record (row) is the names of the fields that you have used, in the order in which they appear. These are your column headers. There is really just one rule: you must use the column or field names that the system uses. Variations are currently not allowed. The flexibility comes from being able to include only the fields for which your register has data and also that you can put them in any order.

For example, this is the complete set of fields now available for a burial record — new fields are marked with a :

  • chapman_code
  • place_name
  • church_name
  • register_type
  • register_entry_number
  • burial_date
  • death_date
  • burial_person_forename
  • burial_person_surname
  • burial_person_title
  • person_age
  • burial_person_abode
  • cause_of_death
  • burial_location_information
  • place_of_death
  • memorial_information
  • relationship
  • male_relative_forename
  • relative_surname
  • male_relative_title
  • female_relative_forename
  • female_relative_surname
  • female_relative_title
  • notes
  • notes_from_transcriber
  • film
  • film_number
  • image_file_name

Don’t be put off by the number of fields now available — you will never need to use all of them together, only those fields that are in your register.

See the Fields in detail menu for links to full descriptions of all the flexible baptism, marriage and burial fields.


General guidance
for the flexible CSV format

Type what you see

The first rule of transcribing is to type what you see (TWYS). Even if it looks wrong or seems like an abbreviation. The only exceptions are for various practical reasons:

  • Dates must be entered in a standard way for searching to work (see Dates, below, and the article on Numbers and dates)
  • A few fields (for instance, county) require an abbreviation
  • The name fields must not have anything else other than names — see Names, below, and the guidance for baptisms, marriages or burials
  • Some characters can't be entered in the database — Wm and Wm are both entered as Wm
  • Pairs of letters, written as if joined together, could be entered, but they wouldn't be found: type Phoebe for Phœbe, Aedie for Ædie, and so on

The mandatory fields

The County, Place, Church and Register Type fields must have entries that are recognised by the database. Using a separate field for the Register Type is a change in practice. Contact your Coordinator if you are not sure what to enter here or if your entries are rejected.

The Register Type is a two-letter code that now has its own field, register_type. It indicates the source of your transcription. See the Info Box for a list of the codes; for a description of each Type, see the Register types article.

Illegible or not clear?

If there's something you can't read, or that could be one thing or another, use our Uncertain Character Format (UCF). Even the transcription of uncertainty needs to be done the same way by everybody, so that we can all search the database effectively.

Dates

The next few paragraphs are a summary of our article on Numbers and dates.

The way that we enter most dates is simply dd Mon yyyy: a two-digit day, then a three-letter month, then a four-digit year. For example 01 Aug 1804, 29 Oct 1778, 23 Apr 1642.

If the year is before 1000, and so naturally has three digits, then use a leading zero: enter the year 894 as 0894 (spreadsheet users will need to set the cell format to text, or the zero will disappear).

In England and Wales, for a date from 01 Jan up to 24 Mar in any year before 1752, we use the split-year convention. In 1752, England and Wales adopted the Gregorian calendar and we can be certain of the actual year.

When using the split-year convention, where there is a decade or century change, please make sure you indicate this clearly. For example, 1729/30 or 1699/00.

Scotland adopted January 1st as New Year's Day in 1600: any date recorded in a Scottish register from 1600 onwards will be a new style date. So, we need to insert the old style year for dates from 01 Jan to 24 Mar (incl.) in any year from 1600 to 1751 (incl.). For example: a date recorded as 15th February 1658, should be entered as 15 Feb 1657/8; and 6th January 1700 as 06 Jan 1699/00.

If part or all of the date is missing or illegible, we make use of parts of our Uncertain Character Format (UCF) as follows:

  • If the day is missing, just enter a month and year — Jun 1783
  • If the day is unclear, use _ (underscore) for an unreadable digit, or * (asterisk) for an unreadable day — 1_ Feb 1862, * Jul 1746
  • If the month is missing or illegible, enter dd * yyyy — 09 * 1708
  • If the day and month are missing, just enter the year — 1761
  • If only the year is legible, put * * yyyy — * * 1761
  • If the year is missing or illegible, then enter the most likely year from the position in the register, in the form yyyy? or yyyy/(0)y? as appropriate. Do not use any other UCF (Uncertain Character Format) for the year — 09 Feb 1723/4?, 20 Jun 1786?, * * 1828? (In the last example, the whole date is missing or illegible.)

If using a spreadsheet, be sure to set the cell format for any date fields (columns) to text rather than date: computers are not good with dates before 1900, and certainly do not understand the split-year convention.

Names

Enter only the actual name: any prefix or suffix, such as Revd or Snr or Laird, belongs in one of the new Title fields — these are available for all the main players in an event.

If no name is given, leave the field blank, and put any remarks in the register such as A Woman Unknown in the Notes field.

Please do not use square brackets, [ ], in any of the Forename or Surname fields, unless you need to use the brackets as part of our UCF (Uncertain Character Format).

For example, you may be tempted to enter something like "Willam [sic]" or even "[Willam]", just as you you would in a transcription made for your personal use. For the FreeREG database to be easily searchable by a researcher, you need to put "Willam" in the Forename field and then something like "Forename: Willam [sic]" in the Transcriber notes field.

Notes vs Transcriber notes

The Notes field is for any additional information contained in the register that does not belong in another field.

Transcriber notes is a new field which will be for your comments rather than actual data. For example, "Date unreadable so year entered by assumption from position in the register".

Text editors

Using the flexible format, line 5 of your file will be: #,DEF.
Line 6 could be something like this, depending on which fields you need and what order works for you (the line will scroll horizontally):

register_entry_number,burial_date,death_date,burial_person_forename,burial_person_surname,burial_person_title,person_age,burial_person_abode,relationship,male_relative_forename,relative_surname,male_relative_title,female_relative_forename,female_relative_surname,female_relative_title,notes,notes_from_transcriber,chapman_code,place_name,church_name,register_type,image_file_name

(The first four lines of the Header are unchanged.)

If entering data using a text editor be especially careful to surround a field that includes commas or speech marks with quotation (speech) marks. For example: 23, High St. would be entered as "23, High St." And a surname of Smith that could be Smithe, would be "SMITHE{0,1}".

In addition, literal quotation marks should be doubled, so that Wm. “Billy” George would be entered as "Wm. ""Billy"" George" in the appropriate Forename field.

Modern versions of MS Excel and OpenOffice Calc will deal with these situations for you (as will WinREG).