| field |
comment |
| whole table |
This is the management table for satellite tags. Typically joins will be made using both the tagnumber and pttnumber fields. Important fields used as query filters are tagmodel, tagmodel_num, tagstatus, invoicedate and owner. There is only one record for each tagnumber but there are multiples times where pttnumber is duplicated across different tag numbers. All date fields should be converted from type text to date or timestamp. |
| argosdirect |
Is the PTT currently enrolled in the Argos Direct program? Tags in Argos Direct generate emails with each new detection for a selected group of email addresses. |
| argos_region |
The primary ocean region in which the PTT is expected to transmit. Not important for transmission success according to Argos. Generally either Pacific, Atlantic or Indian. |
| arrival_timedrift |
The amount of drift in seconds upon arrival from the factory. |
| chaffing |
Exists and belongs in programming and/or deploy table. Candidate for deprecation. |
| comments |
Any comments about the tag including past locations. |
| dart |
Exists and belongs in programming and/or deploy table. Candidate for deprecation. |
| daystorelease |
Probably only for Lotek PSAT tags which come preprogrammed from the factory. |
| deploykey |
This should be called eventid. The eventid assigned to the tag if it was deployed. |
| format |
The Argos transmitter formatting. Specific to tag model and requested with new PTTs from CLS America. |
| hexadecimal |
The hexadecimal number ID for an Argos PTT. |
| igfa_invoice_date |
The date of the IGFA invoice. |
| igfa_invoice_num |
Not sure about this one. Either IGFA purchase order number, or Block lab invoice number submitted to IGFA for payment. |
| instrumentreportfiles |
Generic comment on how the instrument report file was received for a new tag, e.g., "hardcopy in tag shipment" or "Tag Agent". |
| invoicedate |
What date is on the shipping invoice. |
| invoicenumber |
The number on the shipping invoice. |
| mbari_share_date |
MBARI owned tags. When did we give them the tag number? |
| ordernum |
Customer specific like a purchase order number. |
| paint |
Paint type applied by the manufacturer. |
| physicallocation |
Duplicated by tagstatus and comments. Should be merged into them and deprecated. |
| programmingreportfile |
Exists and belongs in the programming table. Candidate for deprecation. |
| programnumber |
The Argos program number associated with the PTT number. |
| project |
Duplicated by tagstatus and comments. Should be merged into them and deprecated. |
| pttnumber |
The Argos ID/PTT number for the tag. |
| pttstatus |
The current status of the PTT number. Is it active, recycled to another tag or been returned to Argos? There can also be user-on-copy info or WC Portal when appropriate. |
| quotenumber |
Sometimes the order quote number is available. It is stored in this field. |
| refurbished |
Was the tag returned to the manufacturer for refurbishment? Generally this would mean testing of sensors and installation of a new battery. |
| repetitionperiod |
The repetition period for the Argos PTT. Not sure of the units. |
| rewardamount |
What is the reward amount printed on the tag? |
| rma_number |
RMA number associated with tag return to manufacturer. |
| rma_request |
The requested action associated with rma_number. |
| sequentialnumber |
Unknown. Candidate for deprecation. |
| species |
Exists and belongs in deploy table. Candidate for deprecation. |
| startdate |
Not sure about this one. Possible duplicate of satdeployments startdate field. Candidate for deprecation. |
| taglabel |
Generic reference to label style and content. Generally either Pacific, Atlantic, Wildlife etc. |
| tagmodel |
Manufacturer model name of the tag, e.g., PAT-MK10, miniPAT or SPOT5. Should match tagmodel field in tbltopptags. There is a major caveat with this field. Older Wildlife tags (PAT 1 to PAT 5) can change model name with a tagware upgrade! Therefore it is possible a tag might have first been deployed as a PAT 2, recovered and upgraded and deployed again but this time as a PAT 4. This field will only try and track the most recent model name. For this reason it should not be expected to always match modelname in satdeployments or tagmodel in tblfgsatdeployments. This also means that there is not a single perfect source for model name. Table satdeployments is the most logical but it is likely missing records from some older tags, meaning in some situations tblfgsatdeployments will be best. Currently tblsharkdeployment does not include a model name field. |
| tagmodel_num |
Probably specific to Wildlife Computers. More specific tag model information, e.g., newer Mk9s can be number 286C or 286F. |
| tagnumber |
The manufacturer serial number. |
| tagowner |
Who owns the tag? |
| tagsoft |
The tag firmware/software version number. This value could change with an upgrade on older tags (PAT 1 to PAT 5), making it difficult to get tagmodel correct. |
| tagstatus |
The current location and/or status of the tag. |
| toppid |
Basically duplicated by deploykey. Candidate for deprecation. |
| trade_date |
If the tag was traded between owners on what date did the trade take place? |
| trade_owner |
If the tag was traded between owners who is the new owner? |
| trade_tag |
If the tag was traded between owners what tag was it traded for? |
| uplinkid |
An ID used in an LUT system to locate a detached tag. Also found in the programming table. Maybe more appropriate in the programming table. |