Notes to the Central Council Methods Library

The Central Council Methods Library is now maintained using the Composition Library website, and that provides the easiest way to search for and view methods by their blue line or grid. It also provides the ability to check and classify new methods.

In addition, files containing method lists to view, or download for use with spreadsheets or computer programs, are usually generated once a week, and are archived in a Central Council repository on GitHub for direct access through these pages. There are three different formats provided and these are explained further below:


Text Format Files

Text format provides simple lists for browsing or pasting into a spreadsheet or database.

Separate files are provided for each Method Class and Stage, and these can be viewed directly in a browser by clicking on the link. They are presented as simple html files to ensure the browser does not wrap the text. In addition a single zipped file containing all methods (i.e. all Classes and Stages) is provided for download.

The single Class and Stage files are laid out in columns that are both tab separated and space separated to a fixed width. This means that the columns will be aligned when displayed in a browser or text editor, and will also paste or import correctly into the columns of a spreadsheet or database. The fixed column width means that the data in some columns has to be truncated, for example extremely long method names or references. The presence of an ellipsis (...) at the end of the column indicates where the data has been truncated. If full data is needed, use the all methods file.

The all methods file is only tab separated, as use with a spreadsheet or database is assumed. No data is truncated in this file.

The files are UTF-8 encoded to support the full range of Unicode characters used in Method names. UTF-8 is very widely supported by applications, but if you require a simpler encoding, try the MicroSiril format as that is restricted to the ASCII character set.

The data is laid out in columns as follows:

Id
A unique identifier for the method
Method
The method title, omitting the common classes and stage if shown in the heading of the file
First rung
The date [yyyy-mm-dd] the method is first recorded as being rung in a qualifying published performance, whether that be an extent, touch, peal, quarter peal; on its own or in spliced
Refs
References, including:
- Bell News [BN: Vnn/ppp ppp Vnn/ppp ppp]
- Ringing World [RW: yyyy/ppp ppp yyyy/ppp ppp]
- Treble Dodging Minor Methods collection [TDMM: nnnn]
- Plain Minor Methods collection [PMM: nnnn]
FCHs
The tenors together False Course Heads for methods with Plain Bob leadheads
Stage
The number of bells
Symmetry
The symmetry of the method, using the initial letter of the following symmetry types. 'D', 'P' & 'R' will frequently occur together:
A - Asymmetric
D - Double symmetry
P - Palindromic symmetry
R - Rotational symmetry
Little
Contains 'Y' if it is a Little method (the principal hunt bell does not ring in every place)
LLen
Lead Length. The length of a lead of the method and the number of changes represented by the place notation
Leadhead
The Leadhead Code or Leadhead Row if not coded
Notation
The full Place Notation for a lead of the method

MicroSiril Format Files

The MicroSiril format has been used to import methods into computer programs since the 1980s and although it has limitations, it is still the most widely used format today. For example MicroSiril files can be imported by Abel, BelTower, MethodMaster and a number of other applications. Its place notation format is also widely supported, including the online peal prover of BellBoard.

Methods of each combination of stage and class grouping is held in a separated file in ASCII format. The files are named according to the convention below, where n is the Stage:

An - Alliance methods
Bn - Blocks
Dn - Delight methods
Hn - Hybrid methods
In - Differential methods (note: Differential Hunters can be found in their respective hunter class)
On - Principles
Pn - Plain methods
Sn - Surprise methods
Tn - Treble Bob methods
TPn - Treble Place methods
CCCBR_methods.mslibs.zip - A Zip file containing all the other files

Each method is recorded on a separate line using fields as follows, separated by a single space:

Method Name
The method title without the stage and common classes of the file. Any Unicode characters in the name are converted to lower case ASCII format with a leading Capital letter, and all spaces are removed. Leading numbers are prefixed by 'Number'.
Leadhead Code
The Leadhead Code or where there is no leadhead code a 'z' followed by the leadend change is used
Place Notation
The Place Notation for the method in MicroSiril format, omitting the leadend change that can be inferred from the Leadhead Code

XML Format Files

The XML format is the newest and most comprehensive format available, and is ideal for use with any new ringing software being developed. As well as the place notation for each method, it provides method properties, such as False Coursehead Groups, symmetry and hunt bell path, as well as details of the first performance on tower bells and handbells. For full details of the format, you can download the Central Council's XML Method Specification.

Each method tag is given a unique ID corresponding to the method ID used in Composition Library prefixed by 'm'.


Copyright © 2018 Central Council of Church Bell Ringers