ECOLM - An Electronic Corpus of Lute Music
The database
Pieces
For the purpose of this database, a ‘piece’ may be a whole piece, a single movement of a larger work such as a suite, or a single voice of a piece from a partbook. It may be defined as a single unit from a single source. Please note that this is not a ‘work&rsquo in the traditional sense - different versions of Flow my Teares will count as different pieces. To group together such versions of the same piece, we use clusters.
The main Pieces table is set up as follows:
| Piece ID | integer | Auto-increment-generated primary key |
| * Source ID | integer | Joins with Sources table to indicate location |
| Piece Type | string | eg. MS or print. Necessary as one might have manuscript insertions in prints, etc |
| Piece Title | string | As it appears in source. Slashes for line breaks |
| Piece Attribution | string | As and if in the source. NOT directly linked to People |
| Piece Key | string | Upper/lower case for major/minor. sharp=#, flat=b. This is rough judgement of overall key, not deep analysis |
| * PieceStructure ID | integer | Join - for standardising structures (see below) |
| Piece Notation | string | e.g. ‘French’ for French Lute Tablature |
| Piece Namedtuning | string | As and if it appears in manuscript. Currently empty |
| Piece Tuningintervals | string | in semitones from string 1 |
| Piece String1 | string | Absolute tuning of string one if known (or surmised) |
| Piece Comments | text | Any info. Unstructured |
A straightforward look-up table used by this is Piece_Structures. This simply
allocates a unique ID to each structure (e.g. AA'BB'CC' or ABCA'B'C'A''B''C'').
| PieceStructure ID | integer | Auto-increment-generated primary key |
| PieceStructure Def | string | Definition |