Fixtures and Diary Entries - Configuration Data

The sort order is the sort-order of the sections in the Fixtures Calendar (by club or by date) - then alphabetic.

Sort by is the sort order to apply to fixtures associated with this section.

The cross-reference filter suppresses events that do not match the section but take place at clubs (when sort is by club) they are then included in the download as 'for XYZ fixture see page n'

The order is the sort-order of the document within its section in the Fixtures Calendar - this is relevant when more than one index is in a section. Indexes always appear at the end of a section and the order of items in the index is defined by the section (as fixtures are).

Categorise By elides the relevant field where it matches the row above and draws a line above each grouping. Note that WeekNum elides the date field (because the WeekNum is not expected to appear in the index but is used for sorting by date).

Creating a new one is probably best done by copying fields from an existing one.

The Entries Secretary is used for every fixture they organise, unless the individual fixture specifies one.

The sort order is used to order the drop-down list control and to order items in a view where everything else is equal.

Don't delete codes that have ever been used (even if a long time ago), but you can set them so they will not be available to be used mistakenly by clearing the 'Use Direct' flag.

A flag on each event code shows if it is used in the current calendar - it is set correctly whenever you run the data checks. Note that the event codes seen by users are per fixture, and are a compression of the event codes used for events. For example, a tournament with AC Advanced and Handicap events shows a code meaning 'Mixed', though no individual event is assigned event type 'Mixed'. Event type codes actually used for events but elided (because the fixture has a mixture of events) are flagged as not used - this is because they do not appear anywhere except in the edit dialogue box for the relevant events, so are not an abbreviation the user will see.

Likewise, codes set as 'Abbreviation Only' because they are used only in consolidation (e.g. MS to mean mixed level and handicap AC) will be marked automatically as used (or not used) when the data checks are run (that way, you can see which you might want to delete). Note though that true abbreviations, such as AMD, will never be marked as used since they are not used in the event codes consolidation

The other event codes, which are used when a fixture has a combination of events, are event codes that do not have the 'Use Direct' flag set. These cannot be assigned as an event type. They are flagged as 'Abbreviation Only'. Likewise, other abbreviations (which are not event codes) are flagged 'Abbreviation Only' (e.g. AMD). Note that the 'Abbreviation Only' flag is cleared automatically when the 'Currently Used' flag is set.

The generated 'Fixtures Key and Abbreviations' contains everything flagged as actually used, plus everything flagged as 'Abbreviation Only'. 'Use Direct' and 'Abbreviation Only' are mutually exclusive - nothing can be both. 'Calendar Entries using this code' and the table show this 'in the key' status.

Running the data checks figures out how many events use each code and which are used and which are replaced - it highlights candidates for change.

The table shows the count of fixtures containing one or more events using the code, and of those which are in the future - this helps maintain the list of event codes flagged as 'Use Direct'