> 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/acquisition-of-timing-data/bib-chip-correspondence.md).
# Bib - Chip correspondence
When working with transponders, you usually need to fill in a correspondence table, i.e. indicate for a given chip identifier the bib number that it will represent.
The association can be done in several ways:
* by importing a complete correspondence table
* by importing a "chip id" information into a list of participants
* by manual entry on a participant’s registration form
{% hint style="info" %}
Providing a correspondence table is optional in the case where the chip identifiers are also the bib numbers. For example Chip 1208 = Bib 1208.
{% endhint %}
{% hint style="info" %}
The same bib can be associated with several chip identifiers.
{% endhint %}
Viewing/entering the chip ID associated with a bib
Importing chip ID with a list of participants
## The correspondence table
Whichever method you choose, you can consult this table by clicking here, or by changing tabs in the acquisitions window:
In this window you can add/delete/consult associations.
File or clipboard import functions are available.
And you can also save reusable lists, useful for example if you have a set of transponders that is always identical.
## Filters
The filters are mainly intended to eliminate spurious readings, that is to say the detection of transponders which are not yours.
Most often your chips are encoded with a discriminating prefix. For example "9588000164" where 164 represents the useful identifier and 9588 is the prefix found on all transponders. In this case we can indicate to Wiclax that only chips with this prefix are to be processed.
In addition, you can choose to process only part of the code, for example only the last 6 characters from the right. If necessary:
* either the retained part is equal to the bib number, and you do not need a correspondence table
* either it is a random identifier and you will fill your correspondence table without using the prefix
## Short codes
Short codes are like shortcuts for chip IDs.
For example, your batch of transponders is numbered from 1 to 100, but their identifiers are arbitrary.
The principle is as follows: in the example above, if bib 98 receives the encoded chip AH-3453, I can directly assign it the chip identifier 2.
Upon receipt of a detection of the AH-3453 chip, Wiclax will know from the short code associated which bib this chip belongs to.
A list of short codes therefore complements the correspondence table, it does not replace it.
---
# 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/acquisition-of-timing-data/bib-chip-correspondence.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.