Creating competition data from multiple sources
When managing a competition with LynxPad, you can have individual teams enter their own athlete data and seed times into their own copies of LynxPad. Using this method, teams can send you the data from their own LynxPad competition directory. Then, you can import the data (see "Importing Lynx files") into the master competition you create in LynxPad.
Here's how it works
The procedure table shown here assumes you are a meet director, and that coaches participating in your meet are going to enter data for their own athletes.
| Stage | Description | ||
|---|---|---|---|
| 1 | Meet director creates a competition with events, team names, and affiliations in LynxPad and makes the lynx.cmp and lynx.evt files available to coaches. | ||
| 2 | Coaches open their copy of the meet director's lynx.cmp file using LynxPad. At this time, coaches have access to available events. | ||
| 3 | Coaches do the following in LynxPad: a add athletes b select events for each athlete to participate in c enter seed times and seed marks, and d save the competition. | ||
| 4 | Coaches then send the entire competition directory to the meet director. This can be done, for example, by emailing the directory as an attachment using a compression program such as WinZip. At a minimum, coaches must be sure to send the PPL, EVT and LSF files to the meet director. | ||
| 5 | From LynxPad and with the master competition lynx.cmp file open, meet director imports lynx.evt and/or lynx.ppl files received from coaches using the File | Import | Lynx Files... function in LynxPad and navigating to the directory where coaches' files are saved. Lynx.lsf files containing seed times and marks are imported automatically. |
| 6 | After all lynx.evt and/or lynx.ppl files from individual coaches have been imported, meet director assigns ID numbers and begins seeding the events in the master competition. |
|---|
Importing Lynx files
You can import existing Lynx EVT and PPL files into LynxPad. This is particularly helpful when you want multiple teams to enter their own athlete data (see "Creating competition data from multiple sources") on their own copies of LynxPad.
note: LSF, or seeding files, are automatically imported with the EVT file. However, the lynx.cmp file is not imported at this time.
- You first must have a lynx.cmp file open. To do this, either create a new competition (see Creating a new competition) or open an existing competition (see Opening an existing competition).
- Click File from the Menu bar and select Import | Lynx Files.... A Browse Folder dialog appears.
- Navigate to the directory containing the EVT and PPL files you want to import.
- Click to select the EVT and/or PPL file/s you want to import, and then click OK.
- Click OK at the Finished Importing Lynx...Files message. If you imported an EVT file, the events appear in the Events window. If you imported a PPL file, the athletes appear in the Athletes window. If you imported an LSF file, seed marks are available for athletes in corresponding events.
important: Duplicate athletes and events are not imported.
Importing and exporting delimited files
LynxPad can now import and export raw data in the form of semi-colon and comma delimited files, allowing competition data to flow between copies of LynxPad.
For example, if you are directing a competition, you can create a single competition in your version of LynxPad, and then import team and athlete entries made by coaches participating in your competition on their own copies of LynxPad. (See Integrating entries from multiple sources.)
Exporting semi-colon and comma delimited files
With a competition open in LynxPad:
- Click File from the main Menu bar and select Export and then select either Semi-Colon Delimited Entries... or Comma Delimited Entries.... The Save As dialog appears.
- Navigate to where you want the exported file saved and then click Save.
Importing semi-colon and comma delimited files
Individual and relay competition entries in the form of a semi-colon or comma delimited text file can be imported into LynxPad.
Instructions
note: These instructions assume you have a semi-colon or comma delimited text file available somewhere on your computer or network.
- Run LynxPad.
- Open a competition.
- Click File from the Menu bar and select Import. A drop-down menu appears.
- Select either Semi-Colon Delimited Entries... or Comma Delimited Entries... from the drop-down menu. The Open dialog appears.
- Navigate to where the semi-colon or comma delimited file is saved.
- Click to highlight the file, and then click Open. LynxPad begins importing the entries.
Notes about importing
- If an entry has errors in it, it is skipped. When LynxPad completes the import, an Import Results dialog appears, detailing any skipped entries.
- The last directory used for importing becomes the default directory for your next import.
About delimited file entry records
This section describes the characteristics of delimited file entry records. Delimited file entry records There are two types of entry records that can be made in a delimited file format for use by LynxPad:
- A = Individual Entry Record (9 fields separated by semi-colons or commas), and
- L = Relay Entry Record (7 fields separated by semi-colons or commas).
Delimited file entry record rules
Delimited files must adhere to the following rules if they are to be successfully imported into LynxPad:
- If no information is available for a given field, leave it blank, but include the semi-colon or comma.
- Follow each record by a carriage return and line feed (CRLF). Create a CRLF by pressing the Enter key.
- If at any point in a record all remaining fields are blank, you can end it with a carriage return without including the extra semi-colons or commas.
- Create an A record for each individual entry.
About the Individual Entry (A) record
The following table demonstrates the components required in an A, or Individual Entry, record.
| Data | Max Characters | Notes | |
|---|---|---|---|
| A 1 Delineates "Individual Entry Record" | |||
| Last Name | 20 | Required field | |
| First Name 20 Required field | |||
| Athlete Gender | 1 | ▪ M = Male, F = Female | |
| ▪ Required field | |||
| Team Name | 25 | ▪ Use Unattached if | |
| unknown | |||
| ▪ Required field | |||
| Event Number | 5 | Required field | |
| Entry Mark | 11 | ▪ Time: hh:mm:ss | |
| (1:23:44.55, 1:19.14, | |||
| 58.43) | |||
| ▪ Mark: Metric - 12.33; | |||
| English - 12-10.25", | |||
| 12' |
| Event Entry/Relay Entry | Not implemented in | ||
|---|---|---|---|
| LynxPad 3.25 | |||
| Event Measure | 1 | ▪ M for Metric, E for | |
| English | |||
| ▪ Required field | |||
| Event Division | 2 | Not implemented in | |
| LynxPad 3.25 |
Individual Entry (A) record example
A;Doe;John;M;Hurricane High School;1;21.23;M;[CRLF]
Notes
- There is one A record per individual entry.
- Four entries for the same athlete require four A records.
About the Relay Entry (L) record
The following table demonstrates the components required in an L, or Relay Entry, record.
| Data | Max Characters | Notes | |
|---|---|---|---|
| L 1 Delineates "Relay Entry Record" | |||
| Team Name | 25 | ▪ Use Unattached if | |
| unknown | |||
| ▪ Required field | |||
| Designation | 1 | A, B, C, etc. | |
| Relay Gender | 1 | ▪ M = Male, F = | |
| Female, X = Mixed | |||
| ▪ Required field | |||
| Event Number | 5 | Required field | |
| Entry Time | 10 | hh:mm:ss.tt (44.55, | |
| 4:19.14) | |||
| Event Division | 2 | Not implemented in | |
| LynxPad 3.25 |
Relay Entry (L) record example
L;Hurricane High School;A;M;12;4:01.44;[CRLF]