General Information - Wildlife Violation and License File (WLQ/WLR)
Wildlife Violation and License File (WLQ/WLR)
The purpose of this system is to provide a standardized, secure and efficient method for Nlets users to exchange wildlife violator and license holder information primarily between conservation officers and, secondarily between state, local and federal law enforcement and criminal justice agencies.
This capability allows states with automated wildlife violator systems to respond automatically (without manual intervention) to requests from other states over Nlets. States without automated systems should respond manually.
Wildlife Violator and License Query / Response
An agency may request out-of-state wildlife violator and license holder information by submitting a fixed format query to the state(s) of record. The query may be on name (NAM) and date of birth (DOB) or social security number (SOC). Response(s) will be returned with the violator or license holder information or contact information. The requester will review the response and contact the agency of record if more details are needed.
Multi-State Query Functionality
Nlets supports the Multi-State Query functionality for the WLQ message format. This functionality allows the query to be automatically sent to all states that participate in the message type and returns a single merged response.
In order to send a Wildlife Violation and License Query transaction using the Multi-State Query, the query should be sent in its typical format to the destination NL. Nlets will take this query and send it to ALL states that support the WLQ message key. Nlets then collects all relevant responses to this query, merges them together while suppressing the NO HIT responses, and sends them onto the querying user as a single response. These responses will also contain summary data indicating which states this query was sent to, which states responded with hits, which responded with no hits, and which states did not respond at all.
States receiving legacy text or GJXDM formats will see the summary data and state responses in a flattened text format (wrapped in XML for GJXDM), whereas states receiving responses in NIEM will receive the summary and state responses in a standardized XML structure detailed below.
An important detail to note is that if a response is received after Nlets has forwarded on the merged Multi-State response, the late response will be sent individually to the original user. This would be most likely to occur if a participating state happened to be 'down' at the time of the query but came back up at a later time and responded.
Overview
The purpose of this inquiry is to request wildlife violator or license holder information on a subject. Records may be requested using both a name and date of birth, OR social security numbers. A user may include both of these search elements but should clearly understand that each search element may generate a separate response, depending on the capabilities of the state.
If no information is available, the state will return a "NO RECORD" message.
Query Requirements
- Up to five 2-character destinations are allowed.
- All requests begin with the purpose code and attention fields.
- The wildlife officers must have a method of accessing Nlets through the state law enforcement system.
- The state must perform the necessary programming to accept and process the wildlife inquiry and response format that will facilitate the exchange of this information.
- The state should have a plan for providing automated responses to wildlife inquiries.
- Recognizing that states may be in various levels of development of these files, automated responses are not a requirement. All states are encouraged to implement or be in the process of implementing this capability.
- Trailing spaces should be eliminated in all data fields. This is to satisfy any state requirements regarding the dissemination of criminal history record information.
Wildlife Query Purpose Codes
The NCIC/Nlets purpose codes are located in Section 1.6 of the Introduction Page.
Data Codes/Field Requirements
The requirements for Wildlife Queries (WLQ) are described in the sections that follow.
Wildlife Query Field Requirements (WLQ)
The requirements to send a Wildlife Query (WLQ) are as follows:
XML Tag:
Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
PUR/
1
Must be "C",
"J" or "F"
Purpose code
<n2:ResponseAttentionDescriptionText>
Manual
Name of requesting
individual
<nc:Person>
<nc:PersonName>
<nc:PersonFullName>Full name; format is
last name, comma,
space after comma
is optional) first
name, space, middle
initial or name,
space, suffix (Jr.,
III, etc.) Titles
or degrees should
not be used as
part of the name.
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>
ccyymmdd
Date of Birth.
Complete DOB must
be present. Some
states have
different
requirements.
Check their OLN
HELP file for
details.
<nc:Person>
<nc:PersonSSNIdentification>
<nc:IdentificationID>Wildlife Responses (WLR)
- All WLQ queries should be answered by a WLR from the destination.
- If a query uses a format with more than one index (e.g., NAM/DOB and SOC) the responder should indicate which search element was used to search the file and which one, if any, produced the hit.
- States should attempt to show what action was taken on the search. For example, a record may be available on JOHN DOE; however, no information was found on the SOC. The requester should be told this.
- If the state does not have the ability to search their file by one of the indices, the requester should be so notified.
- In all cases the original inquiry should be the first part of all responses in order to let the requester identify their request.