Where to submit an extracted tick? - briefly
Send the removed tick to a recognized public‑health or veterinary laboratory, for example the state health department’s vector‑borne disease unit or the CDC’s Tick‑Borne Disease Laboratory. These facilities perform species identification and pathogen testing on submitted specimens.
Where to submit an extracted tick? - in detail
When you have isolated a tick for analysis, the appropriate destination depends on its origin and intended use.
First, identify the source of the tick. If it originates from a proprietary software product, the manufacturer’s bug‑tracking system is the primary channel. Locate the official issue tracker—often hosted on platforms such as JIRA, GitHub Issues, or a dedicated portal—and create a new ticket. Include a clear description, the exact timestamp, and any relevant logs. Attach the extracted tick file in the format required by the system (e.g., .pcap, .log, .json).
If the tick is derived from an open‑source project, submit it through the project's contribution workflow. Typical steps are:
- Fork the repository if required.
- Add the tick file to the appropriate directory (e.g.,
testdata/orsamples/). - Open a pull request with a concise title and a brief explanatory comment.
- Reference any related issue numbers.
For community‑driven platforms, such as forums, mailing lists, or Discord channels, post the tick in the designated troubleshooting or bug‑report section. Provide:
- Context of extraction (application version, operating system, configuration).
- Reproduction steps, if known.
- The raw tick data or a link to a secure file‑sharing service.
When dealing with regulatory or compliance concerns, forward the tick to the compliance officer or the designated security team via encrypted email or a secure ticketing system. Ensure the transmission complies with data‑protection policies.
In summary, submit the extracted tick to the official bug‑tracking system of the originating software, to the relevant open‑source contribution channel, or to the appropriate community or compliance venue, always supplying full context and adhering to the accepted file format.