Where Wildlife Computers Tag Users Find Data, Tools, and Support

Updated

If you already have a Wildlife Computers tag deployed or in hand, the resources you need are grouped under four areas of the site: the online data portal (My Tags, My Data, Tag Agent), tools and documentation (IGOR, Document Repository, Downloads), technical support (FAQs, Repairs and Returns, Contact Us), and project forms (Project Information Form). The portal is where tag data lands; the tools section is where you decode, archive, or retrieve it; support handles hardware problems and questions; forms cover project-level submissions. Below is what each entry does and when to use it.

Online data portal: My Tags, My Data, Tag Agent

The site describes an online data portal that "captures, decodes and stores your data online and supports automatic data retrieval by government-mandated data systems." Three entries sit in this area:

  • My Tags — the tag-level view. Use it to see the tags registered to your account and their status.
  • My Data — the data-level view. Use it to access the decoded, stored records associated with your tags.
  • Tag Agent — the software component that handles capture and decoding of tag data into the portal.

Practical sequence: register or locate your tag under My Tags, confirm data is flowing, then pull records from My Data. If data is not appearing, Tag Agent is the first thing to check, since it is the piece that captures and decodes before storage.

Tools and documentation: IGOR, Document Repository, Downloads

  • IGOR — listed under Tools. This is the analysis/processing tool referenced alongside the data products (Archiving, Transmitting, Locations, Environmental, Behavior, Activity, Time Series). Use it when you need to work with tag data beyond what the portal displays.
  • Document Repository — the place for documentation. Use it for manuals, specifications, and reference material tied to your tag model.
  • Downloads — software and file downloads. Use it to get the applications and utilities you run locally.

A workable order when starting with a new tag: check the Document Repository for the model's documentation, get the needed software from Downloads, then use IGOR for processing.

Technical support: FAQs, Repairs and Returns, Contact Us

  • FAQs — first stop for common questions before opening a support thread.
  • Repairs and Returns — for hardware that is damaged, malfunctioning, or needs servicing. Use this when the issue is physical rather than data-related.
  • Contact Us — the general route when FAQs do not cover the problem.

Rule of thumb: data or portal issues → check Tag Agent and the portal entries first; hardware issues → Repairs and Returns; anything unresolved → Contact Us.

Project forms and account access

  • Project Information Form — for submitting project-level details. Use it when setting up or registering a project rather than troubleshooting an existing tag.
  • Portal — the login entry point for the online data portal. Access to My Tags and My Data runs through here.

Note that the site does not state whether portal access or any of these tools carry a cost or require specific account permissions; treat login and access terms as something to confirm through the portal or Contact Us rather than assuming they are open.

Quick routing table

What you need Where to go
See your registered tags My Tags
Retrieve decoded tag data My Data
Fix data not appearing Tag Agent
Process/analyze tag data IGOR
Manuals and reference docs Document Repository
Software and files Downloads
Common questions FAQs
Damaged or malfunctioning hardware Repairs and Returns
Unresolved issues Contact Us
Register project details Project Information Form
Log in to the portal Portal

Common sticking points

  • Data missing from My Data — check Tag Agent first; it is the capture-and-decode step that feeds the portal.
  • Wrong tool for the job — IGOR is for processing; the portal is for storage and retrieval. Do not expect one to replace the other.
  • Hardware vs. data confusion — a tag that is not transmitting may be a deployment or hardware matter (Repairs and Returns) rather than a portal matter.
  • Skipping documentation — model-specific behavior lives in the Document Repository; check there before assuming a fault.