Difference between revisions of "Main Page"

From Anitra Support
Jump to: navigation, search
Line 255: Line 255:
 
==Tracked Object EndDate==
 
==Tracked Object EndDate==
  
* Device Statuses are meant to help to control active Loggers >> Tracked Objects (Trackings). In order to receive a meaningful warnings, it is highly recommended not only to turn inactive devices to Archive but also to end related active Tracked Objects (Trackings) whenever the tracking in the field is over (i.e. you do not expect to receive any new data).  
+
* Device Statuses are meant to help to control active Loggers >> Tracked Objects (Trackings). In order to receive a meaningful warning, it is highly recommended not only to turn inactive devices to Archive but also to end related active Tracked Objects (Trackings) whenever the tracking in the field is over (i.e. you do not expect to receive any new data).  
  
 
** Ending Tracked Object / Tracking is done by filling in date into field "End of tracking" in the Tracked Object profile
 
** Ending Tracked Object / Tracking is done by filling in date into field "End of tracking" in the Tracked Object profile
Line 261: Line 261:
 
** Note that you can additionally enter more detail related to mortality event ("Estimated date of death", "Mortality Reason", "Mortality Note", "Mortality Photos/Documents/Reports")
 
** Note that you can additionally enter more detail related to mortality event ("Estimated date of death", "Mortality Reason", "Mortality Note", "Mortality Photos/Documents/Reports")
  
'''Mortality warnings'''
+
'''Mortality warnings''' <br>[[File:DTO000.JPG|44x38px]]
:[[File:DTO000.JPG|44x38px]]
 
 
* Notifies on possible mortality in the last position of finished (archive) trackings
 
* Notifies on possible mortality in the last position of finished (archive) trackings
* You can set the end date of tracking so that the mortality sign is displayed in you archive data (see the end date for the first two tracked objects in the example no 1)
+
* You can set the end date of tracking so that the mortality sign is displayed in you archive data (see the end date for the first two tracked objects in the example no 1) <br>[[File:DTO0000.JPG|36x37px]]
 
 
:[[File:DTO0000.JPG|36x37px]]
 
 
* Warns on possible mortality detected in the last position of active trackings
 
* Warns on possible mortality detected in the last position of active trackings
 
* In order to have relevant red warnings shown correct device/TO configuration needs to be kept by project admin
 
* In order to have relevant red warnings shown correct device/TO configuration needs to be kept by project admin
Line 276: Line 273:
  
 
* You can find these last data mortality warnings on various screens of Anitra platform:
 
* You can find these last data mortality warnings on various screens of Anitra platform:
** Device list (''only Red warning for Active trackings'')
+
** Device list (''only Red warning for Active trackings'') <br>[[File:DTO001.JPG|900px]]
:[[File:DTO001.JPG|900px]]
 
  
* Device Profile
+
* Device Profile <br>[[File:DTO002.JPG|900px]]
:[[File:DTO002.JPG|900px]]
 
  
* TO List (''both Red warnings for Active trackings and Black Info for Archive trackings'')
+
* TO List (''both Red warnings for Active trackings and Black Info for Archive trackings'') <br>[[File:DTO003.JPG|900px]]
:[[File:DTO003.JPG|900px]]
 
  
* TO profile
+
* TO profile <br>[[File:DTO004.JPG|900px]]
:[[File:DTO004.JPG|900px]]
 
  
* Map (both Red warnings for Active trackings and Black Info for Archive trackings)
+
* Map (both Red warnings for Active trackings and Black Info for Archive trackings) <br>[[File:DTO005.JPG|900px]]
:[[File:DTO005.JPG|900px]]
 
  
 
* Device Owner/Admins can freely switch devices from one state to another and modify Tracked Objects end dates in order to achieve desired Anitra behavior
 
* Device Owner/Admins can freely switch devices from one state to another and modify Tracked Objects end dates in order to achieve desired Anitra behavior
Line 296: Line 288:
 
'''Appendix:''' Examples of correct and incorrect configurations:
 
'''Appendix:''' Examples of correct and incorrect configurations:
 
<br>'''''Example no. 1)'''  
 
<br>'''''Example no. 1)'''  
''Correct Device/TO configuration: a device used subsequently for tracking of tree animals (the latest TO still active tracking)''
+
''Correct Device/TO configuration: a device used subsequently for tracking of tree animals (the latest TO still active tracking)'' <br>[[File:DTO006.JPG|900px]]
:[[File:DTO006.JPG|900px]]
 
  
 
'''''Example no. 2)'''
 
'''''Example no. 2)'''
 
''Outdated Device/TO configuration: a device used subsequently for tracking of tree animals''
 
''Outdated Device/TO configuration: a device used subsequently for tracking of tree animals''
 
* ''Last data warning says that the last data arrived more than a year ago, SIM card probably already deactivated?''
 
* ''Last data warning says that the last data arrived more than a year ago, SIM card probably already deactivated?''
''>> no more new data expected to arrive''  
+
''>> no more new data expected to arrive'' <br>''>>> TO should be Ended + Device should be switched to Archive status'' <br>[[File:DTO007.JPG|900px]]
<br>''>>> TO should be Ended + Device should be switched to Archive status''
 
:[[File:DTO007.JPG|900px]]
 
  
 
'''''Example no. 3)'''
 
'''''Example no. 3)'''
Line 311: Line 300:
 
** ''In this case''  
 
** ''In this case''  
 
*** ''The tracked object should be ended with the date when the dead bird was found and the logged recovered''
 
*** ''The tracked object should be ended with the date when the dead bird was found and the logged recovered''
*** ''Device status for AUKI06 should be changed from "Deployed Active" to Backup or Archive (depending on intention to reuse HW)''
+
*** ''Device status for AUKI06 should be changed from "Deployed Active" to Backup or Archive (depending on intention to reuse HW)'' <br>[[File:DTO008.JPG|900px]]
:[[File:DTO008.JPG|900px]]
 

Revision as of 19:09, 7 March 2019


SIGNING IN

Sign in / Sign up

  • Once registered you can log in with your username and password or by using "Sign in with Google" functionality
    Sign-in user-pass.JPG
  • You can also reset your password by "forget password ?" link if needed

Sign up

  • Use "Create new account" link to auto-register yourself as a new platform user
  • Use a valid email address as your future username
  • Upon completion, an email with account confirmation link be sent to your inbox
    Create new user.jpg
  • Note that you can also create a new account by using "SIGN IN WITH GOOGLE" button.
  • This flow will link a newly created account with a chosen google account (you will not need to type user name+pass)
    Create new google user.jpg


User profile

  • Change of user password through user profile page
  • Manage linked Google Account(s)
  • "Sign in with Google" functionality available (once linked to a google account, you do not need to type user name+pass)


AREAS OF FUNCTIONALITY
(also indicated by menu icons on the left side)

  • Map view
  • Device list
    • Device profiles
  • Tracked Object list
    • Tracked Object profiles
  • Photo Gallery
  • Import Data
  • Customers
    Menu.JPG
  • Above functionality available for users acting as Data Owners or Admins
  • A minor subset of the functionality available to those who only receive data through Sharing scheme
  • Each user can act in both modes at the same time
    • As data Owner for some data(=devices) … the full functionality available including admin functionality per owned devices
    • As a passive user of data shared by someone else … only predefined data view is available

MAP

  • A tool to analyze multiple Individuals in a single map
    Map00 paralelanalysis.JPG
  • The functionality displays all the Tracked Individuals available to user (both owned/administered and shared only)
  • By default an overview of the last positions is shown - the color of the point categorizes data by the last data update.
    Map01 lastdatacolors.JPG
  • Filtering functionality below the map limits data in the map and in the right Tracked Object selection list by following criteria:
    • "Search" (full text search across Device/TO codes/names/aliases)
    • Species
    • Last "X" Days (limits all the data showing specified last X days interval)
    • Other: Tracking Status, Country of Tagging, Current Age
      Map02 mapfilterfilled.JPG
  • Map functionality
    896x475
  1. Map zoom
  2. Full screen mode
  3. Overview map
  4. Map layers - a wide range of available maps
    896x475
  5. Show current user position
  6. Map options
  • Last positions
  • Tracks
  • Waypoints
  • Night Points
    Map04b mapFunct Options.JPG
    Map04c mapFunct OptNight.JPG
  • TO details
    • Track point details in the tooltip (note that more track point tooltips can be displayed simultaneously)
    • Additional TO detail in the right TO selection list (including "Share" button for admins)
    • Click through link to particular Tracked Object profile
      Map05 TOdetails.JPG
  • TO Mortality Indicated by black/red symbols in TO right side selection and in the tooltips
    [File:map06_mortalityInMap.JPG|900px]]

DEVICE LIST

  • List of owned or administered devices (= hardware)
  • Click through to device details (profile)
  • Available device types:
    • "Anitra": used for Anitra native devices, device functionality includes remote control of active devices in the field
    • "Ecotone": virtual devices for Ecotone data, possibly of the data feed on Ecotone web (available on request)
    • "Ornitela": virtual devices for Ecotone data, possibly of data feed on Ornitela web (available on request)
    • "Upload/Basic": devices created through Import functionality, any other tracking data, the one who uploads becomes Device Owner
  • User-managed Device Status: allows to categorize devices into activity groups (archive, installed, backup)
  • System of warning messages
    • Incorrect/Missing Device-TrackedObject configuration: "Device Code" followed by the black/red exclamation mark ( "!" or "!" )
    • Mortality indication: "Device Status" colored in red and followed by red skull symbol
    • Missing data last X days: "Last Device Position" followed by red question mark "?". Mouse-over symbol tells the last data delay.
  • Search and predefined filtering options (Status = Installed, Mortality, Last data before +7 days, incorrect Tracked Object configuration)"Ecotone": virtual devices for Ecotone data, possibly of data feed from Ecotone web (available on request
    Capture.JPG
  • Device information (and configuration) is accessible only to owners/admins (users of shared data do not have the rights see this data]

Capture 2.JPG

DEVICE PROFILE

  • Device identification, meta info, status, overview and admin management
  • Device data visualized on the map and on the timeline
  • Management of device tracked objects
    • Removal of technical/manipulation periods
    • Creation/split of device data into real tracked objects (situation when one logger was subsequently used for more than one animal)
  • Last known geolocation (DateTime + country etc.)
  • System of warnings
    • Incorrect/Missing Device-TrackedObject configuration
    • Mortality indication: red/black warning in "Last device Position" row (red = for installed and currently tracking devices/black = tracking finished)
    • Missing data last X days: red warning in "Last Device Position" row (warning active just for installed and currently tracking devices)
  • Summary for related TO profiles (bellow timeline) including Mortality Indication symbols

Capture 3.JPG

DEVICE CONFIGURATION

  • Customer Owners/Admins can access device configuration
    • from Device List
      Config01.JPG
    • from Device Profile

Config02.JPG

TRACKED OBJECT LIST

  • List of owned TO (tab "my tracked objects")
  • List of TO shared with me (tab "shared with me")
  • Overview of all tracked objects including first and last data
    • Click through to TO detail/profile
    • System of warnings
    • Mortality indication: "Tracking" followed by red skull symbol
    • Missing data last X days: "Last Data " followed by red questionmark "?". Mouse-over symbol tells the last data delay.
  • Search and predefined filtering options (Mortality, Last data before +7 days)

TOL01.JPG

TRACKED OBJECT PROFILE

  • Details of tracked object (= tracking of individual bird)
    • Identification (code, name, ringing, tagging etc.)
    • Info related to particular Individual (species, sex, age, origin)
    • Info related to Start of tracking (including photo and file documentation)
    • Info related to End of tracking (~ mortality/device failure)
  • System of warnings
    • Mortality indication: red/black warnining in "Last known Position" row (red = for installed and currently tracking devices / black = tracking finished)
    • Missing data last X days: red warning in "Last Device Position" row (warning active just for installed and currently tracking devices)
      738x138
  • TO data visualized on the map and on the timeline
    TOP01.JPG
  • "Share" button allows sharing TO to other Anitra users
  • Possibility to attach photos /documents related to
    • tracking start
    • Mortality
  • Same photo can be shared by various Tracked Objects
    TOP02.JPG

PHOTO GALLERY

  • Displays a complete gallery of pictures from all the Tracked Objects (own and shared)
  • Filtering by main metadata criteria
    TO.JPG

IMPORT DATA

  • Allows importing any other tracking data in the predefined structure. Currently, we support:
    • Data in simple structure device-GPSDateTime-latitude-longitude-note (type "Basic")
    • Ecotone CSV format
    • Ornitela CSV format
  • "Upload" automatically analyses imported data and offers the creation of new "Devices"
  • Data for already existing devices are appended to these devices (e.g. allows a user to update data in the system by monthly update files..)
  • The user who uploaded data becomes Device Owner
    Import.JPG

CUSTOMERS AND INTEGRATION

  • There is one more menu item visible for those users who act in the system as "Customer Owners" or "Customer Admins"
    Customers And Integration01.JPG
  • Customer detail can hold the definition of one or more integration connections (currently Ecotone and Ornitela data feeds supported)
    Customers And Integration02.JPG
  • Integration connection toolbox allows
    • Create-edit-remove management of the connection
    • Sending a request for automatic integration run
  • Review of the log of the service
    Customers And Integration03.JPG
    Customers And Integration04.JPG

EXPORT CSV/XLSX

  • At the moment, there are two places to have your data exported:
  1. Customer profile: full data for all ANITRA devices owned by Customer (available for CustomerOwner and CustomerAdmins)
  2. Device profile: all data for a single device (available for all Customer/Device Owner/Admins)
  • /* mass data takeout not available for people with shared acces only */
  • Ref 1) Mass export ANITRA data on "Customer profile"
(Both CSV and formatted Excel sheet available):
Export001.JPG
  • Ref 2) Export data for one particular device
    Export002.JPG
  • Export columns specification:
    Export004.JPG
  • CSV file sample preview:
    Export005.JPG
  • XLSX file sample preview
    Export006.JPG

DEVICE-TRACKED OBJECTS-MORTALITY

  • Anitra platforms data model is based on the following key concepts:

Device

  • Represents physical hardware device to which all the tracking and sensor data are linked
  • Allows storing info related to hardware (Brand, logger model, serial number, GSM no. Etc.)
  • The device in the system can be created
    • By purchasing Anitra logger (the device will be created and assigned to Anitra Customer)
    • By importing tracking file (csv, kml/kmz, gpx)
    • Automatically by Integration (i.e. automated data feed e.g. from Ecotone or Ornitela panels)

Tracked Object (or Tracking)

  • Represents particular animal carrying logger device, a single device can be reused several times (in case of mortality of tracked object)
    • Allows filtering (e.g. display, share) relevant subset of device data
    • Allows attaching metainformation related to:
      • The tracked Individual (species, sex, age, ringing, origin etc)
      • The tracking of that animal (start of tracking, end of tracking, mortality attributes, photos/documents)
    • Tracked Object in the system can be created
      • Automatically: by default, any new device has got a default tracked object configured starting with the first device data
      • Using "split TO" functionality in the device profile
      • Using "create new TO" functionality in the device profile

 

Device Data

  • A basic level of tracking/measurement information
  • Data are accessible through devices and their tracked object(s)

Device Status Management and Tracked Object configuration

  • For maximum benefit of a full array of Anitra functionality (data filtering, mortality warnings, advanced sharing etc.) we highly recommend to maintain "Device Statuses" for your devices and Tracked Objects for your study animals up to date.
  • Available basic "Device Statuses":
    • Backup / Pool:
      • To be used for spare/pool devices which are not currently in the field and are planned to be (re)used in future.
      • New devices which appear in the system are labeled "Backup" status automatically
    • Deployed:
      • To be used for devices which are currently deployed "in the field" and potentially sending data
      • There are 4 sub-statuses available which allow the user to configure Anitra behavior further
1. Deployed Active:
  • Known to be currently delivering data reliably and new data expected to be updated on a regular basis
  • Mortality notification should work reliably
2. Deployed Down:
  • Known to be still delivering data (at least for some time), but based on data received the device very likely not already attached to target animal (shed/down logger, killed animal)
  • Hardware to be either recollected or written-off
  • "New data" notifications could help investigating the case till the logger transmits data
  • After collecting all possible information and closing the case the device should be turned to "Archive" status
3. Deployed Missing:
  • Data delivery suddenly interrupted, last positions do not show animal/logger issue
  • "New data" notifications possibly used to notify on the restoration of data transfer
4. Deployed Problem:
  • Depending on the issue type the data delivery fails or some sensor data might be unreliable
  • Allows suppressing mortality notification as false or confusing warnings may be raised
  • Archive / Discarded:
  • meant for out of use devices (inactivated, suspended, finished) not expected to deliver any new data
  • Turning device into this state allows suppressing warning scheme
  • Allows to store and filter out archive data
  • Note that devices created through import functionality are by default switched to this state

Tracked Object EndDate

  • Device Statuses are meant to help to control active Loggers >> Tracked Objects (Trackings). In order to receive a meaningful warning, it is highly recommended not only to turn inactive devices to Archive but also to end related active Tracked Objects (Trackings) whenever the tracking in the field is over (i.e. you do not expect to receive any new data).
    • Ending Tracked Object / Tracking is done by filling in date into field "End of tracking" in the Tracked Object profile
    • "End Of Tracking" field leaves space for individual interpretation. For instance in case of mortality you can include the period when the tracked individual was alive only or you might as well close the tracking date later when the device was physically found and removed.
    • Note that you can additionally enter more detail related to mortality event ("Estimated date of death", "Mortality Reason", "Mortality Note", "Mortality Photos/Documents/Reports")

Mortality warnings
DTO000.JPG

  • Notifies on possible mortality in the last position of finished (archive) trackings
  • You can set the end date of tracking so that the mortality sign is displayed in you archive data (see the end date for the first two tracked objects in the example no 1)
    DTO0000.JPG
  • Warns on possible mortality detected in the last position of active trackings
  • In order to have relevant red warnings shown correct device/TO configuration needs to be kept by project admin
Note. the detection of mortality is currently based on
  • Anitra: dedicated sensor/accelerometer mortality detection logic
  • Ornitela: identical body position between subsequent measurements
  • Ecotone Activity column with a simple rule (Activity < 10) triggering the alert. More complex logic is being developed for Anitra native devices
  • You can find these last data mortality warnings on various screens of Anitra platform:
    • Device list (only Red warning for Active trackings)
      DTO001.JPG
  • Device Profile
    DTO002.JPG
  • TO List (both Red warnings for Active trackings and Black Info for Archive trackings)
    DTO003.JPG
  • TO profile
    DTO004.JPG
  • Map (both Red warnings for Active trackings and Black Info for Archive trackings)
    DTO005.JPG
  • Device Owner/Admins can freely switch devices from one state to another and modify Tracked Objects end dates in order to achieve desired Anitra behavior

Appendix: Examples of correct and incorrect configurations:
Example no. 1) Correct Device/TO configuration: a device used subsequently for tracking of tree animals (the latest TO still active tracking)
DTO006.JPG

Example no. 2) Outdated Device/TO configuration: a device used subsequently for tracking of tree animals

  • Last data warning says that the last data arrived more than a year ago, SIM card probably already deactivated?

>> no more new data expected to arrive
>>> TO should be Ended + Device should be switched to Archive status
DTO007.JPG

Example no. 3)

  • Outdated Device/TO configuration: Dead bird, logger recovered and physically back in office
    • As the device is still in the "Deployed Active" state and tracked object not closed, it raises false red mortality warnings
    • In this case
      • The tracked object should be ended with the date when the dead bird was found and the logged recovered
      • Device status for AUKI06 should be changed from "Deployed Active" to Backup or Archive (depending on intention to reuse HW)
        DTO008.JPG