> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/use-wiclax/entering-importing-participants/participants-database.md).
# Participants database
Wiclax supports the use of athlete and club files to streamline participant registration. These must be formatted text files. They can be official files provided by your federation (containing all or part of their licensed members) or custom files created by yourself.
To use these files with Wiclax, you simply need to designate their location and describe their content structure. These operations are performed here:
### Designation and Description
First, specify the location of the file to be processed. A data preview will appear. Just like during participant import, you can define the data separator and map the content of each column you wish to use.
You can also define the abbreviations used for male and female genders in the file (defaulting to "M" and "F").
It is possible to make edits directly in the data preview grid, which can then be saved.
### Activation
Searching within the current runner file can be enabled or disabled from the management window, or directly from the participant entry window via the options button.
### Searches
If the license number is included in the file information, you can perform a search directly from the license number field in the registration form. In all cases, a simple search by last name will display a list of potential matches found in the database, showing birth dates to help resolve cases of identical names.
### Club Files
Club files allow you to retrieve a club's full name based on its identifier (club code). Wiclax can utilize a club file as long as it is possible to retrieve a club identifier for a given runner. This identifier may come from a runner file or be embedded within the competitor's license number.
Club files can be designated, activated, and described in the same way as athlete files, with the difference that you can only map the Club and Club Code columns. These operations are performed in the Clubs tab.
### Creating and Updating Runner Files
From the Update tab in the management window, you can:
* Update the current file: This operation completes and updates the information in the current runner file (provided it has been designated and described in the Runners tab) using the participant list from the event. When executed, runners already present in the file are updated with data from the participant list. Runners who do not yet exist are added.
* Create a new file: This operation creates a new runner file initialized with the runners currently in the event. After specifying a name and location for the file, it is created and automatically designated as the active runner file. You can then view the details of the new file in the Runners tab.
### Remote Athlete Databases
Wiclax also has the capability to query a remote database via API.
If you are a sports federation and wish to provide such an API, please do not hesitate to contact us. A specification detailing the call conditions for Wiclax and the expected response format is available upon request.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.wiclax.com/en/use-wiclax/entering-importing-participants/participants-database.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
