...
Each match is represented using three mandatory values and four five optional values. A round-number, a "home" team/opponent number, and an "away" team/opponent number make up a match's mandatory values; a time, a day, a green/rink allocation ID(s), and a section-number, and a yes/no flag to associate the competition format to the match’s location make up a match's optional values.
...
| Code Block | ||
|---|---|---|
| ||
|=================================| | Round | Home | Away | |=============+=========+=========| | 1 | 1 | 2 | |-------------+---------+---------| | 1 | 3 | -1 | |-------------+---------+---------| | 2 | 1 | 3 | |-------------+---------+---------| | 2 | -1 | 2 | |-------------+---------+---------| | 3 | 1 | -1 | |-------------+---------+---------| | 3 | 2 | 3 | +|-------------+---------+---------+| |
The template above is a typical representation of a round-robin competition with only 3 teams, where teams play each other only once. The template above includes only the mandatory values for each match: a round-number, and two opponent numbers.
...
In contrast, the template below is more complex, and includes optional values for each match, including a day, time, green/rink allocation ID(s), and sectionsection, and yes/no flag to associate the competition format to the match’s location (represented by a ‘1' or '0’ respectively).
Sample fixtures
| Code Block | ||
|---|---|---|
| ||
|=================================================================================================| | Round===============| | Round | Home | Away | Day | Time | Green/Rink | Section | Associate Format | |=============+=========+=========+============+==========+================+=============+=======================| | 1 | 1 | 2 | 2021-04-01 | 09:15 | 4642 | | |------ 1 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 1 | 3 | -1 | | 17:30 | 76/234 | 76 1 | 1 | |-------------+---------+---------+------------+----------+----------------+-------------|+-----------------------| | 2 | 1 | 3 | 2021-05-21 | 13:20 | | | | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 2 | -1 | 2 | 2021-05-22 | | 5367 | 1 | 0 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 3 | 1 | -1 | | | | | | |-------------+---------+---------+------------+----------+----------------+-------------|+-----------------------| | 3 | 2 | 3 | 2021-11-03 | | 76/9/345 | 345 | 1 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 1 | 4 | 5 | 2021-04-01 | 09:15 | 4642 | 2 | 1 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 1 | 6 | -1 | | 17:30 | 76 | 2 | 0 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 2 | 4 | 6 | 2021-05-21 | 13:20 | | 2 | | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 2 | -1 | 5 | 2021-05-22 | | 5367 | 2 | | | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 3 | 4 | -1 | | | | 2 | 0 | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------| | 3 | 5 | 6 | 2021-11-03 | | 345 | 2 | | |-------------+---------+---------+------------+----------+----------------+-------------+-----------------------+| |
Note that in the template above, optional values are just that: optional. A match may have a day, but no time; or a time, but no day.
...
| Code Block | ||
|---|---|---|
| ||
Round,Home,Away,Day,Time,Green/Rink,Section,Associate Format 1,1,2,2021-04-01,09:15,4642,,1 1,3,-1,,17:30,76/234,1,1 2,1,3,2021-05-21,13:20,,, 2,-1,2,2021-05-22,,5367,1,0 3,1,-1,,,,, 3,2,3,2021-11-03,,76/9/345,,1 1,1,2,2021-04-01,09:15,4642,2,1 1,3,-1,,17:30,76,2,0 2,1,3,2021-05-21,13:20,,2, 2,-1,2,2021-05-22,,5367,2, 3,1,-1,,,,2,0 3,2,3,2021-11-03,,345,2,2, |
A match may require the allocation of more than one green/rink. This can be achieved by identifying multiple green/rink allocation IDs for the match, each separated by a forward slash / - e.g. 76/9/345 . In the template above, both match #3 and #7 identify multiple greens/rinks; match #3 has two greens/rinks allocated (IDs 76 and 234), and match #7 has three greens/rinks allocated (IDs 76, 9, and 345).
When opting to associate the competition format with an allocated green/rink, an association will only be created between the first allocated green/rink and the format. However, if the competition is a multi-format competition, and a match has multiple green/rinks allocated, associations will be created sequentially between each format and green/rink allocation. Example: the first format of a multi-format competition will be associated with the first green/rink allocation, the second format of a multi-format competition will be associated with the second green/rink allocation, and so on.
A match may require one or both of its opponents to be determined by the outcome of other matches - such as a round-2 match in a knock-out competition having both opponents determined by the winners of two distinct round-1 matches.
This can be achieved in a template by using an opponent source identifier in place of a team/opponent number for the "home" value, "away" value, or both.
...
| Note |
|---|
Before attempting to import your own fixture template CSV file, take note of the following: |
Ensure your CSV file has a .csv extension; the BowlsLink application may be unable to recognise the file as a fixture template otherwise.
Ensure your CSV file's first row represents "column headers" (like 'Round', 'Home', etc), and not a match; the BowlsLink template importer is configured to ignore the first row. As such, feel free to use whatever "column headers" make sense to you.
Ensure every row of your CSV file has values for all three mandatory columns: round-number, "home" team/opponent number, and "away" team/opponent number.
Round numbers don't have to be contiguous, nor do they have to start at 1; a fixture template with rounds 5, 21, and 40 is perfectly valid.
Round numbers do, however, need to be greater than zero (0).
Like round numbers, team/opponent numbers don't have to be contiguous, nor do they have to start at 1. We recommend, however, that you use team/opponent numbers that are greater than zero (0), as the BowlsLink application reserves numbers less than one (1) for specialised cases (like byes, which are represented using -1).
Team/opponent numbers must be no greater than 9000.
Days must conform to the format YYYY-MM-DD.
Times must use 24-hour time and conform to the format HH:MM.
Green/rink allocation IDs must identify greens/rinks allocated to the competition to which the match(s) belong. The Greens & Rinks Report can be used to generate a list of green/rink allocation IDs per competition.
Section numbers don't have to be contiguous, nor do they have to start at 1; a fixture template with sections 7, 2, and 11 is perfectly valid.
Section numbers do, however, need to be greater than zero (0).
For any match that doesn't define a section number, section 1 will be used as default.
For templates that define more than single section, the same team/opponent number must not appear in more than one section. Example: if one section uses team/opponent numbers 1-3, no other section may use these numbers. The exception to this rule is team/opponent numbers below 1, such as -1 (byes).
A fixture template that defines more than a single section cannot have its matches extrapolated using the Apply the template to how many sections? feature.
The yes/no flag for associating the competition format with a green/rink allocation must be represented by a one (1) or a zero (0) respectively.
For any match that doesn’t explicitly specify a flag for associating the competition format with a green/rink allocation, '0' (no) will be assumed by default.