Typical event entry

A typical entry set up for a gigs list looks something like:

    <A Name="D.19931008">8 October 1993</A>:
    <A Name="B.Dance.English Ceilidh">Ran Tan</A>, caller
    <A Name="C.">Gordon Potts</A>
    <A Name="L.UK.TQ294837">Cecil Sharp House, London</A>

.. or, if you are using tables, something like:

      <TD><A Name="D.19931008">Friday, 8 October 1993</A></TD>
      <TD><A Name="B.Dance.English Ceilidh">Ran Tan</A></TD>
      <TD><A Name="C.">Gordon Potts</A></TD>
      <TD><A Name="L.UK.TQ294837">Cecil Sharp House, London</A></TD>

The Flag fields

The data after the D., E., C. or L. flags in the anchor, like the 'Dance.English Ceilidh' above, won't be visible in the displayed text but could be picked up by a separate indexing script which looks for all "Dance" or all "English Ceilidh" entries.

Indexing scripts will therefore be possible for particular bands, particular callers or types of dance as well as dates.

The following tags are currently recognised:

  • D.: Introducing a date (in the form yyyymmdd), this marks the start of an event.
  • B.: Introducing a band, with the tag giving the style of music. For example <A Name="B.Dance.English Ceilidh">Ran Tan</A> flags a Ceilidh style dance with the Ran Tan band.
  • C.: Introducing a caller, with the with the tag giving the style of dance.
  • E.: Introducing an event and works in the same way as the B. band tag. Note, where the scripts find multiple sources of information for one event, on event and band pages for example, the entry from the Event Organiser is listed first in the diaries. Without some way of distinguishing between these entries the same event could appear twice.
  • L.: Introducing a Map Reference and text which would be used in the index instead of the <H1>...</H1> header data for that event.

The 'Dance-style' type tags currently being used are listed in the 'not a thesaurus' section