This is a project begun over the summer of 2010 by Robert Wallis, and aims to be a fast, user-friendly interface to the data provided on methods.cccbr.org.uk, and dove.cccbr.org.uk.


iPhone/iPad users can install Blueline as a web app by navigating to the homepage in Mobile Safari, tapping the action button, then tapping 'Add to Home Screen'. There's no native iOS app, and no current plans to make one as I don't have an Apple computer to make it on.

An Android app is available.

Android users with Chrome >32 can also install Blueline as a web app by navigating to the homepage in Chrome, tapping the menu button, then tapping 'Add to Home Screen'.

There is a Chrome Web App.

Data and Copyright

The database tables can be downloaded below, and an explanation of where it's come from and how it works follows.


Only the current version of the data for each entity is retained, and I keep no record of when data was created or modfied (that information may be available at source). The data is stored in 8 tables and (with the exception of those generated from Dove data) can be downloaded as ,-delimited and "-enclosed CSV files for your own use (bearing in mind the health warnings and copyright information on this page): associations, collections, methods, methods_collections, performances.

The towers, towers_associations and towers_oldpks tables aren't provided as the maintainers of Dove have decided to authorise and log downloads of the Dove data, and I don't want to ruin that. A download code can be requested from them here. I expand some abbreviations and create a link-table to associations, but make no significant changes to the data before using it on this site.


Method details are derived from the Central Council of Church Bellringers data maintained on methods.cccbr.org.uk.

The XML schema (part 6) has been mapped into the database table in an obvious way.

Data has not been modified, but the following additional fields have been added:

Table FieldValue
methods.notationExpandedContains the place notation of the method converted to a normalised format using 0-9 and uppercase letters for places, 'x' for changes with no places made, '.' to seperate consecutive changes with places made, and expanding any abbreviations made due to palindromic symmetry. The code carrying out this expansion is here.
methods.urlContains the method's name with URL-unsafe/reserved characters removed, and converted to the ASCII character set.
methods.nameMetaphoneContains the metaphone key of the method's name. This is used for implementing spell-check in search. Example.
methods.magicContains an integer that can be used to sort methods in an order approximating how popular/common they are. This is calculated using a number of variables, such as whether the method is in a standard collection, what classification it is, how commonly peals of the method are rung, etc
methods.callsContains the details of common calls (Bobs and Singles) for the method. These are automatically generated unless overidden by me based on common practice (e.g. Stedman Triples has Bobs of '5:6:-3' and Singles, '567:6:-3').
methods.ruleOffsDetails where lines should be drawn to divide the method into sections when displaying, in the format '[divisionLength]:[start]' with both divisionLength and start integers.
This is assumed to be '[leadLength]:0' unless overidden by me based on common practice (e.g. Stedman divided into sixes by '6:-3').

The manual overrides mentioned above are best viewed on GitHub, and I would welcome any comments on other methods where tweaks are required.


The method data discussed above also contains the numeric indices of methods in the "Treble Dodging Minor Methods" and "Plain Minor Methods" collections as 'tdmmRef' and 'pmmRef'. These are added (unmodified) to my database to create the 'tdmm' and 'pmm' collections.

Any further collection data have been added by me and are based on my knowledge of common practice.


The method data discussed above contains the date and location of the first towerbell and handbell peals of methods if they are known. The XML schema (part 7) has been mapped into the database table in an obvious way.

A relation back to the method is added and then I also attempt to add a relation to the tower where the performance took place. This is done by searching the towers table for a matching location, or using a manual list where there are known differences in spelling or similar between the Dove data file and the naming used in the methods data. If multiple (or no) matches are found then no relation is added, so these relations are certainly incomplete. They may also be incorrect if a previously ambiguous location in the method data no longer results in multiple matches due to towers being removed from the current version of Dove.


Tower information is taken from the the current version of the Dove data file, maintained by the Central Council of Church Bellringers. The fields in the data file are mapped as follows:

CSV FieldTable Field

Data is modified as follows: Spaces in Dove IDs are replaced with underscores (_) to improve readability in URLs. Various abbreviations are expanded.


The Dove data file noted above contains an affiliations field with a list of abbreviations of associations to which the tower is affiliated. I used Google to find the full name and websites of them. A more complete list is avaliable on ringing.info.

Fields and relationships are as in the below diagram:

Source code

The source code for this website is made available for interested people.