https://support.anitracking.com/api.php?action=feedcontributions&feedformat=atom&user=Admin 2026-04-29T15:33:50Z User contributions MediaWiki 1.30.0 index.php?title=Release_notes/2026-04-28&diff=1297 2026-04-28T10:25:07Z

<p>Admin: Created page with &quot;{{Release note|Device Configuration|new}} {{Release note body start}} * major rework and functionality extension) * options for new 4G tags firmware added * further UX fine-...&quot;</p> <hr /> <div>{{Release note|Device Configuration|new}} <br /> {{Release note body start}}<br /> * major rework and functionality extension)<br /> * options for new 4G tags firmware added <br /> * further UX fine-tuning<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Export data functionality modernised<br /> * Bulk URL selection further improved.<br /> * Geofencing functionality updated<br /> * UI for various areas consolidated and improved<br /> ** easier control using the keyboard implemented<br /> ** date/time input modified<br /> ** warning and notification scheme revised (config storage mode and mortality flags)<br /> {{Release note body end}}<br /> <br /> {{Release note|Various minor fixes|bugfix}}<br /> {{Release note body start}}<br /> * Mainly in the areas refactored in the recent loops<br /> ** person list and person profile<br /> ** user signup, singn-in, invite flow, and reset password features<br /> ** note functionality (attached files fixed)<br /> ** group functionality (logos, adding trackings, adding POIs)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2026-04-28}}<br /> [[Category:2026 Release notes]]</div>

Admin index.php?title=Release_notes/2026-03-21&diff=1296 2026-03-22T05:27:09Z

<p>Admin: </p> <hr /> <div>{{Release note|Bulk selection in URL|new}} <br /> {{Release note body start}}<br /> * A new option for device and tracking grids - bulk selection is now stored in the URL<br /> * URL can be used to share your filtered lists with other users<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for more areas consolidated and improved<br /> ** Groups/Projects (adding persons to Project Roles, more compact)<br /> ** User management and Sign-up process<br /> * Device Configuration (major rework and functionality extension)<br /> ** UX fine-tuning, including autorefresh<br /> ** new parameters for new generation tags<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various minor fixes|bugfix}}<br /> {{Release note body start}}<br /> * mainly related to areas refactored in the previous wave<br /> * in global search, person list<br /> * in POI to group and tracking to group adding<br /> * in note functionality<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2026-03-21}}<br /> [[Category:2026 Release notes]]</div>

Admin index.php?title=Release_notes/2026-03-21&diff=1295 2026-03-22T05:25:58Z

<p>Admin: </p> <hr /> <div>{{Release note|Bulk selection in URL|new}} <br /> {{Release note body start}}<br /> * A new option for device and tracking grids - bulk selection is now stored in the URL<br /> * URL can be used to share your filtered lists with other users<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for more areas consolidated and improved<br /> ** Groups/Projects (adding persons to Project Roles, more compact)<br /> ** User management and Sign-up process<br /> * Device Configuration (major rework and functionality extension)<br /> ** UX fine-tuning, including autorefresh<br /> ** new parameters for new generation tags<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various minor fixes|bugfix}}<br /> {{Release note body start}}<br /> * mainly related to areas refactored in the previous wave<br /> * in global search, person list<br /> * in POI to group and tracking to group adding<br /> * in note functionality<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2026-03-21}}<br /> [[Category:2026 Release notes]]</div>

Admin index.php?title=Release_notes/2026-03-21&diff=1294 2026-03-22T05:21:39Z

<p>Admin: </p> <hr /> <div>{{Release note|Bulk selection in URL|new}} <br /> {{Release note body start}}<br /> * A new option for device and tracking grids - bulk selection is now stored in the URL<br /> * URL can be used to share your filtered lists with other users<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for more areas consolidated and improved<br /> ** Groups/Projects (adding persons to Project Roles, more compact)<br /> ** User management and Sign-up process<br /> * Device Configuration (major rework and functionality extension)<br /> ** UX fine-tuning, including autorefresh<br /> ** new parameters for new generation tags<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various minor fixes|bugfix}}<br /> {{Release note body start}}<br /> * mainly related to areas refactored in the previous wave<br /> * in global search, person list<br /> * in POI to group and tracking to group adding<br /> * in note functionality<br /> {{Release note body end}}<br /> <br /> <br /> bulk, gridy <br /> ukládat výběry do url<br /> <br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2026-03-21}}<br /> [[Category:2026 Release notes]]</div>

Admin index.php?title=Category:2026_Release_notes&diff=1293 2026-03-21T06:18:00Z

<p>Admin: Created page with &quot;Category:Release notes&quot;</p> <hr /> <div>[[Category:Release notes]]</div>

Admin index.php?title=Release_notes/2026-03-21&diff=1292 2026-03-21T06:17:10Z

<p>Admin: Created page with &quot;{{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} {{Release note body start}} * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alte...&quot;</p> <hr /> <div>{{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}}<br /> * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for many form screens consolidated and improved<br /> ** mandatory field guidance<br /> ** discard logic unified<br /> ** keyboard control consolidated<br /> * Functionalities the most reworked:<br /> ** Groups/Projects<br /> ** Load/Save Configuration Preset<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * not working background maps mapy.com reimplemented due to the provider API changes<br /> * track not loading for some scenarios corrected.<br /> * adding attachments/screenshots and creating previews in Notes fixed<br /> * published maps display fixed (legend, logos and controls)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2026-03-21}}<br /> [[Category:2026 Release notes]]</div>

Admin index.php?title=TEA&diff=1291 2026-01-07T11:36:07Z

<p>Admin: Created page with &quot;=={{Fa|fa-tablet}} test == : '''Device profile''' tab (tab control marked green): :* holds all the information about the device (identification, status, type, brand, model, a...&quot;</p> <hr /> <div>=={{Fa|fa-tablet}} test ==<br /> : '''Device profile''' tab (tab control marked green): <br /> :* holds all the information about the device (identification, status, type, brand, model, and user description<br /> :* allows administration of the device (i.e. managing admin list, activating Movebank Datafeed, exporting device data into the file, configuring/programming tag (cogwheel icon))&lt;br&gt;[[File:device_profile_functionality_marked.jpg|450px]]<br /> <br /> '''fasfjsa'''&lt;br&gt;<br /> ''sfasdlf''<br /> <br /> &lt;br&gt;<br /> [[File:flkasd.jpg]]<br /> <br /> [[TEA|text na str8nce kam odkaz vede]]<br /> <br /> &lt;br&gt;[[File:device_profile_graph_marked.jpg|900px]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1290 2025-12-08T22:20:13Z

<p>Admin: </p> <hr /> <div>{{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}}<br /> * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for many form screens consolidated and improved<br /> ** mandatory field guidance<br /> ** discard logic unified<br /> ** keyboard control consolidated<br /> * Functionalities the most reworked:<br /> ** Groups/Projects<br /> ** Load/Save Configuration Preset<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * not working background maps mapy.com reimplemented due to the provider API changes<br /> * track not loading for some scenarios corrected.<br /> * adding attachments/screenshots and creating previews in Notes fixed<br /> * published maps display fixed (legend, logos and controls)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1289 2025-12-08T22:01:03Z

<p>Admin: </p> <hr /> <div>{{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}}<br /> * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * UI for many form screens consolidated and improved<br /> ** mandatory field guidance<br /> ** discard logic unified<br /> ** keyboard control consolidated<br /> * Functionalities the most reworked:<br /> ** Groups/Projects<br /> ** Load/Save Configuration Preset<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * not working background maps mapy.com reimplemented due to the provider API changes<br /> * Track not loading for some scenarios corrected.<br /> * adding attachments/screenshots and creating previews in Notes fixed<br /> * published maps display fixed (legend, logos and controls)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1288 2025-12-08T21:45:24Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> <br /> * UI for many form screens consolidated and improved<br /> ** mandatory field guidance<br /> ** discard logic unified<br /> ** keyboard control consolidated<br /> * Functionalities the most reworked:<br /> ** Groups/Projects<br /> ** Load/Save Configuration Preset<br /> ''Please report any imperfections spotted in these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}}<br /> * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * not working background maps mapy.com reimplemented due to the provider API changes<br /> * Track not loading for some scenarios corrected.<br /> * adding attachments/screenshots and creating previews in Notes fixed<br /> * published maps display fixed (legend, logos and controls)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1287 2025-12-08T21:44:00Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Functionalities the most affected<br /> ** Groups/Projects<br /> ** Load/Save Configuration Preset<br /> ''Please report any imperfections spotted for these areas''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}}<br /> * A new &quot;Find device&quot; tool has been added in the Load Preset modal as an alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various UI improvements|improvement}} <br /> {{Release note body start}}<br /> * UI for many form screens consolidated and improved<br /> ** mandatory field guidance<br /> ** discard logic unified<br /> ** keyboard control consolidated<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * not working background maps mapy.com reimplemented due to the provider API changes<br /> * Track not loading for some scenarios corrected.<br /> * adding attachments/screenshots and creating previews in Notes fixed<br /> * published maps display fixed (legend, logos and controls)<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1286 2025-12-05T13:16:56Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Various application features reviewed and consolidated (most changes in Groups/Projects and Load / Save Configuration Preset)<br /> * Related bug-fixing loop done. <br /> ''Please report any remaining imperfections spotted''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}} <br /> * a new &quot;Find device&quot; tool has been added in the Load Preset modal<br /> * another alternative way of loading existing config values from other devices<br /> [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> <br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> {{Release note body end}}<br /> <br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1285 2025-12-05T13:15:34Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Various application features reviewed and consolidated (most changes in Groups/Projects and Load / Save Configuration Preset)<br /> * Related bug-fixing loop done. <br /> ''Please report any remaining imperfections spotted''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}} <br /> * a new &quot;Find device&quot; tool has been added in the Load Preset modal<br /> * another alternative way of loading existing config values from other devices<br /> * [https://support.anitracking.com/index.php?title=Configuration#Using_saved_preset_.2F_load_existing_preset ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> <br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> {{Release note body end}}<br /> <br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Configuration&diff=1284 2025-12-05T13:13:59Z

<p>Admin: /* Advanced Configuration Management using Presets */</p> <hr /> <div>{{DISPLAYTITLE: CONFIGURATION}}<br /> <br /> ==Overview &amp; Basic Concepts==<br /> &lt;br&gt;<br /> : Users with admin rights (device owners/admins) can access the configuration from the lists and profiles using cogwheel icons. <br /> : Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> <br /> <br /> : User configuration screen is structured into three main areas<br /> :* Data collection settings<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> <br /> : Note many more advanced settings are possibly available to adjust device behavior upon request/need (device maintenance, troubleshooting, firmware upgrades, custom configuration/behavior - such as GPS accuracy, etc) <br /> <br /> <br /> : Any changes made are visualized by blue and red symbols close to the modified setting and in the top right corner of each modified section<br /> :* symbols (&quot;pen&quot;, &quot;clock&quot; and &quot;check&quot;) show the status of each configuration (edited (=blue &quot;pen&quot;) &gt;&gt; pending (=red &quot;clock&quot;) &gt;&gt; confirmed (=green &quot;check&quot;))<br /> : [[File:config_submitted_modified.JPG|400px]]<br /> <br /> <br /> : New modifications (not yet submitted) are highlighted by blue color<br /> :* these modifications can be reverted to saved values simply by closing the config screen or by clicking on the blue &quot;pen&quot; (for a particular parameter or on the section level) <br /> :* in order to submit the modified parameters, click the &quot;Send&quot; button below<br /> : [[File:config_send_discard(send).JPG|400px]]<br /> <br /> <br /> : Submitted values are highlighted by red color<br /> :* &gt;&gt; all the blue &quot;pen&quot; icons change to red &quot;clock&quot; icons indicating the value is waiting for the device to apply it<br /> :* note the configuration changes apply whenever the tag connects to communicate/send data <br /> <br /> <br /> : Until the values ​​are confirmed by the device the pending changes can be modified or canceled <br /> :* by clicking on the particular &quot;clock&quot; icon - for a particular parameter or on the section level<br /> :* by clicking on the &quot;Discard all pending changes&quot; button below - for canceling all<br /> : [[File:config_send_discard(discard).JPG|400px]]<br /> <br /> <br /> : Once the pending parameters are received, accepted, and confirmed successfully by the device the status is changed from red &quot;clock&quot; to green &quot;check&quot;<br /> :* note by default the configuration is sent and delivered to the device via GPRS data<br /> :* as a supplementary delivery channel SMS can be used (&quot;Send by SMS&quot; button)<br /> : [[File:config_send_discard(resendSMS).JPG|400px]]<br /> <br /> <br /> : Using SMS might help to deliver configuration mainly in certain areas with poor GPRS data coverage however please note using SMS has certain limitations<br /> :* SMS delivery is not a guaranteed channel (if not delivered SMS disappears from the network in a couple of hours) - this might cause inconsistency in device configuration temporarily <br /> :* just a small subset of the full configuration scope can be fit into one single SMS (therefore the &quot;Sent by SMS&quot; button is only available till the modifications made fit into one SMS message)<br /> :* also note additional charges might be applied when using SMS excessively<br /> <br /> == Configuration areas / Device features ==<br /> &lt;br&gt;<br /> : The configuration screen shows only <br /> <br /> :* the settings relevant to a particular hardware model, firmware version, etc. are available<br /> :* the options relevant to the context of previous selections are available (unrelated or conflicting options are hidden)<br /> <br /> <br /> === Data collection settings ===<br /> &lt;br&gt;<br /> : Left-side &quot;Data collection&quot; section concentrates all the controls related to data sampling<br /> <br /> : [[File:config_data_collection.jpg|900px.JPG]]<br /> <br /> <br /> ==== Scheduled GPS/sensor sampling ====<br /> &lt;br&gt;<br /> : Defines type and structure of data triggered by the scheduler and the actual schedules<br /> <br /> : Data scheduler offers two distinct modes<br /> :* defined as separate cycles or day and night<br /> :* defined as an interval (ignoring both human clock and day and night transitions)<br /> <br /> <br /> <br /> ===== Different day &amp; night cycles (night saving) =====<br /> &lt;br&gt;<br /> : Day/night and night/day transition is configured by sun angles (either typing in the angle form or comfortably using the slider below day/night graphic)<br /> <br /> : [[File:config_schedule_night_angles.JPG|700px]]<br /> <br /> <br /> : Measurement intervals within each daypart use <br /> <br /> <br /> :* '''&quot;human time&quot;''' (UTC clock) - intervals synchronized around defined UTC time (by default around UTC midnight)<br /> <br /> : [[File:config_schedule_night_human.JPG|700px]]<br /> <br /> <br /> :* '''&quot;solar time&quot;''' (i.e the local solar time for actual GPS position) <br /> <br /> <br /> :: By default, the sampling interval is restarted with each day/night and night/day transition (i.e. the first position is collected with the day/night transition)<br /> <br /> :: [[File:config_schedule_night_solar_start.JPG|700px]]<br /> <br /> <br /> :: Alternatively, the interval can be synchronized '''around solar midnight/noon''' (positions are evenly distributed around solar noon/midnight)<br /> <br /> :: [[File:config_schedule_night_solar_midnight.JPG|700px]]<br /> <br /> <br /> ===== Schedules defined as Interval =====<br /> &lt;br&gt;<br /> : Useful in situations when different day and night interval is not needed or when intensive energy saving needs to be achieved (data sampling within many hours or even days). A floating interval unrelated to the human UTC clock <br /> <br /> : [[File:Config_schedule_interval.JPG|600px]]<br /> <br /> ===== GPS/data measurements vs GPS/data bursts =====<br /> &lt;br&gt;<br /> : The scheduler can trigger both - single GPS/data measurements and/or GPS/data bursts. In default, single measurements are triggered.<br /> <br /> : When the burst launching is activated, an additional configuration section is displayed to specify burst behavior<br /> <br /> : [[File:config_schedule_burst.JPG|700px]]<br /> <br /> <br /> : Note the following about measurements and bursts:<br /> <br /> <br /> : '''GPS/data measurement''' <br /> <br /> :* Is a single planned (or activity-triggered) measurement event saving data from available/active sensors<br /> <br /> :* The full dataset structure contains GPS data (latitude, longitude, altitude, direction, speed, and GNSS quality metrics), solar and battery voltage/percent, 3ax-sensors data (accelerometer, magnetometer, gyroscope), temperature. barometric pressure, and some more value-added calculated measures)<br /> <br /> :* For sake of energy saving some measurements might be scheduled to run without activating the GNSS module and without waiting for GPS fix - i.e. '''interlacing''' GPS records with a sensor only records in data delivered into the database<br /> <br /> ::: By default, GPS is turned on for every measurement:<br /> ::: [[File:config_data_GPS_always.JPG|600px]]<br /> ::: GPS interlacing can be configured here (1 GPS position + 4 non GPS records taken):<br /> ::: [[File:config_data_GPS_each5.JPG|600px]]<br /> ::: GPS can be turned off completely like this<br /> ::: [[File:config_data_GPS_off.JPG|600px]]<br /> ::: Note these settings are ignored when mortality is detected.<br /> <br /> <br /> : '''GPS/data burst'''<br /> <br /> :* a time-limited (by &quot;burst length&quot;) continuous series of measurements at a defined sampling rate/interval (even down to 50Hz = 50 records/second)<br /> <br /> :* while running bursts the device is switched to data and energy-intensive mode - a minimum battery level restriction should be maintained at a safe level<br /> <br /> :* each of the sensor types used has a different &quot;maximum resolution&quot; - therefore in the case of running fast burst, we distinguish between <br /> :** '''&quot;slow&quot; data''' (GPS data, temperature, battery voltage, or barometric pressure) - these are only present in one-second data or slower and<br /> :** '''&quot;fast&quot; data''' (accelerometer, magnetometer, gyroscope) which can be sampled at a much higher frequency (e.g. up to 50hz) and saved in every record (e.g 50x per second)<br /> <br /> :* for sake of energy-saving the busts can be also run without activating GNSS and storing GPS data at all. <br /> :: [[File:config_burst_GNSSoff.JPG|700px]]<br /> <br /> :* for limiting data volume generated by fast bursts '''&quot;acc only&quot; mode''' is available (only accelerometer data are stored - not magnetometer and gyroscope data)<br /> :: [[File:config_burst_acconly.JPG|700px]]<br /> <br /> :* Starting of the GNSS module and acquiring GPS position typically lasts a couple of seconds - the following options allow adjusting the burst start behavior the way needed<br /> : [[File:config_data_burst_wait.JPG|500px]]<br /> : [[File:config_data_burst_wait_off.JPG|500px]]<br /> <br /> <br /> ==== Activity triggered data collection ====<br /> &lt;br&gt;<br /> : Range of triggers that can activate/wake up of the device when a certain activity event is detected by the hardware sensors<br /> : [[File:config_activity_triggers.JPG|800px]]<br /> <br /> <br /> : Currently implemented triggers<br /> <br /> <br /> :* &quot;wake up from accelerometer&quot; - based on sudden movement - e.g. can be used to detect take off / landing<br /> :* &quot;wake up from altimeter&quot; - based on height change in meters<br /> <br /> <br /> : Upon activation, the selected trigger can launch either a single measurement or burst<br /> : In case of using triggers for burst an additional burst configuration screen is opened (similar to bursts triggered by schedule)<br /> <br /> : [[File:config_activity_triggers_burst.JPG|800px]]<br /> <br /> ==== Speed triggered continuous GPS sampling ====<br /> &lt;br&gt;<br /> : A special functionality ensuring continuous GPS sampling till the object moves<br /> <br /> : The speed threshold, GPS sampling rate, and battery threshold are adjustable <br /> <br /> : [[File:config_speed_trigger.JPG|800px]]<br /> <br /> : If used in combination with well-configured activity triggers it can allow full movement coverage of tracked animals!<br /> <br /> ==== Mortality detection ====<br /> &lt;br&gt;<br /> : Dedicated Anitra proprietary algorithm based on accelerometer and gyroscope evaluation. Comparing to the older version the new version is much more sensitive and accurate.<br /> <br /> : When enabled, the mortality status is continuously evaluated and logged (note the device consumes additional energy).<br /> <br /> : As soon as the status changes to &quot;mortality detected&quot; or vice versa (i.e. from &quot;mortality&quot; to &quot;alive&quot;) the device automaticaly runs additional measurement (GPS+data) and stores this additional record into memory.<br /> <br /> : Config parameter &quot;run extra comm session..&quot; proactively launches extra communication and notify of the mortality event immediately.<br /> <br /> : Actual mortality state (in mortality/not in mortality) is stored in each dataset and usable for calibration for particular species or even individual/deployment.<br /> <br /> : Note the default configuration options are adjusted to detect while the tag is deployed as a backpack (best tested for raptors)<br /> <br /> : Calibration parameters are detection interval, number of confirmation cycles before the mortality warning is raised, and detection sensitivity<br /> <br /> :[[File:config_mortality.JPG|800px]]<br /> <br /> ==== Geofencing ====<br /> : ''(for the complete information about geofencing see detailed [[geofencing| geofencing configuration guide ]]'')<br /> &lt;br&gt;<br /> :Modifies standard device behavior based on the geographic location<br /> <br /> : Specifics of Anitra geofencing<br /> :* tailored for very advanced geofencing tasks on top of POI databases with even many thousands of items (e.g. database of past poisoning places, wind turbines, dangerous power pylons, etc)<br /> :* a dynamic geofence synchronization (when moving the tag synchronizes 100 closest geofence instances)<br /> :* geofences defined by circular (or possibly even cylindrical) zones<br /> :** working with circles allows resolving conflicts for overlapping geofences (as the closest, the smallest)<br /> :** altitude definition enables 3D geofencing (when higher it is considered as outside of geofence)<br /> <br /> : Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map<br /> :[[File:GF_map_definition.JPG|900px]]<br /> <br /> : A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence<br /> :* day/night data collection interval<br /> :* activity and speed triggering<br /> :* radio buoy activation<br /> :* communication while entering/leaving the geofence<br /> :[[File:GF_behavior.JPG|900px]]<br /> <br /> : ''(for the complete information about geofencing see detailed[[geofencing| geofencing configuration guide ]])''<br /> <br /> === Communication schedules ===<br /> <br /> : Right-side &quot;Communication plans&quot; section concentrates all the controls related to communications schedules/data delivery<br /> : [[File:config_comm_schedules.jpg|600px.JPG]]<br /> <br /> : Anitra devices offer a very wide range of communication setups to match best any particular field situation. Users can combine the following options in order to achieve desired behavior and data delivery timing<br /> <br /> :* Communication defined by intervals<br /> :* Communication defined by fixed UTC timeslots<br /> :* Communication based on number of records collected<br /> :* One-time communication UTC timeslots<br /> :* Additional options <br /> <br /> ==== Communication defined by intervals ====<br /> : This communication plan allows programming the tag to sent data regularly within defined cycles/intervals. The plans can be set up <br /> <br /> :* synchronized to human clock <br /> :** the interval is repeated within 24 hours and restarted at a defined sync time<br /> :** because of that only intervals matching 24 hours are allowed here (i.e. intervals of 1,2,3,4,6,12 hours)<br /> : [[File:config_comm_interval_synced.JPG|400px]]<br /> <br /> :* or floating (not synchronized to the clock)<br /> :** the interval is repeated independently of human clock hours <br /> :** the cycle is restarted with the applied change of the cycle (or when the device is completely discharged)<br /> :** any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication times from one day to another<br /> : [[File:config_comm_interval_nosync.JPG|400px]]<br /> <br /> : Note this schedule can not be completely turned off as it also acts as an &quot;emergency&quot; schedule (i.e. in case of accidentally turning off all other plans)<br /> : Even when turned off by a user the schedule is still triggered every 648 hours (27 days)<br /> : [[File:config_comm_interval_default.JPG|400px]]<br /> <br /> <br /> ==== Communication defined by fixed UTC timeslots ====<br /> : This functionality offers up to four &quot;fixed&quot; time slots <br /> :* fixed to a particular UTC day hour<br /> :* and run every X days defined per slot<br /> : [[File:config_fixedtime.JPG|400px]]<br /> <br /> <br /> ==== Communication based on number of records collected ====<br /> : Communication is relaunched whenever a defined number of records is collected by the tag<br /> : This setting might be particularly beneficial in case of the use of dynamic, unpredictable, or data-intensive sampling modes (such as data/burst triggered by activity or speed triggers)<br /> : [[File:config_comm_datatrigger.JPG|400px]]<br /> <br /> <br /> ==== One-time communication UTC timeslots ====<br /> : In this case, the tag enforces GPS position taking before running communication<br /> : A typical use case is planning the one-time session at the time of the planned field check (e.i. the tag delivers a fresh GPS position)<br /> : Allows parallel scheduling of up to four one-time communication sessions defined at a particular UTC date/time<br /> : [[File:config_comm_onetime.JPG|400px]]<br /> <br /> <br /> ==== Other communication-triggering events ====<br /> : Note the communication can also be triggered in some other situations<br /> <br /> :* device notifies its state in Power-off / Storage mode<br /> : [[File:config_comm_poweroff.JPG|400px]]<br /> <br /> :* mortality detection functionality can be configured to sent data when mortality is reliably confirmed<br /> : [[File:config_comm_mortality.JPG|400px]]<br /> <br /> :* POI/geofencing can also be configured to trigger communication (when entering POI)<br /> <br /> :* Finally a special SM communication session is trigger when regular data schedules fail cor certain number of days<br /> : [[File:config_comm_emergencySMS.JPG|400px]]<br /> <br /> <br /> : Taking into account above mentioned various communication sources the predictability of the next communication session is limited<br /> : The &quot;Next schedule&quot; prediction only factors schedules planned to UTC clock<br /> : [[File:config_comm_prediction.JPG|400px]]<br /> <br /> <br /> === Other user settings ===<br /> <br /> : Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control, etc)<br /> : [[File:config_other_settings.jpg|700px.JPG]]<br /> <br /> <br /> === Storage mode ===<br /> * allows bringing the device to low energy consumption mode<br /> * the device is powered off most of the time and only wakes up at 00:00 UTC in a specified day interval to send tag status (one dataset - GPS, battery level, etc.)<br /> * the communication interval can be set between 1 and 32 days<br /> * using storage mode is useful for long-distance transport and for storing undeployed devices longer time (e.g. when solar charging or GPS signal is unavailable longterm)<br /> [[File:config_poweroff.JPG|500px]]<br /> <br /> <br /> == Advanced Configuration Management using Presets ==<br /> <br /> === About Configuration Presets ===<br /> <br /> : The functionality allows saving the current device configuration (combination of parameters) into the &quot;Configuration Preset&quot; object.<br /> <br /> : Only the &quot;user&quot; values generally applicable are saved (device unique &quot;admin&quot; values, such as ID, mobile phone number or individual calibration values, are not included).<br /> <br /> : A complete or just a subset of &quot;user&quot; configuration can be saved as a preset. Eg, you can save only communication settings in the first preset, data collection settings in another, and geofence settings in the third separate preset. <br /> <br /> : Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.<br /> <br /> === Preset creation flow ===<br /> <br /> :1) Model a desired configuration as a future template in one of your devices config screen.<br /> :: 1.1. You can start by applying the fresh default configuration. <br /> :: 1.2. Adjust the configuration settings and geofence configuration the way want it saved in the preset<br /> <br /> :2) Use the „Save as preset“ button in the config screen of the source device when ready.<br /> <br /> :3) In the Save preset modal<br /> :: 3.1. Name your new preset. ''Make sure you specify a „good“ preset name (by this, it will be looked up later)''<br /> :: 3.2. Review and adjust the contents,<br /> ::: 3.2.1. manually check/uncheck particular sections or individual parameters (also include/exclude the Geofence definition).<br /> ::: 3.2.2. review the values of particular parameters,<br /> :: 3.3. Save preset when all done. &lt;br&gt;[[File:Presets_Save_as_Preset.jpg|700px]]<br /> <br /> :4) You can discard the modeled changes in source device config screen using „Discard all pending changes“ if needed.<br /> <br /> :5) The Saved Preset is available for other devices/users.<br /> <br /> === Using saved preset / load existing preset ===<br /> <br /> :1) Use the „Load preset“ button in the configuration screen of the target device&lt;br&gt;[[File:Preset_Load_Preset.jpg|900px]]<br /> <br /> :2a) Look up and choose the desired configuration preset<br /> <br /> ::* using &quot;Find preset&quot; - type in the search field (the name you know)&lt;br&gt;''Note that currently, there is no visibility restriction implemented (i.e. any user can search any existing preset, no matter who created it). Because of that, the user needs to know the first characters of the searched preset name to look it up! This way you can share your presets with people outside of your organisation as well''<br /> <br /> ::* choosing from the &quot;My presets&quot; list &lt;br&gt;''Note the &quot;My presets&quot; section is only visible to the user who actually created any presets before. Users can also delete their previously saved presets here.''<br /> <br /> :2b) Alternatively, you can pick another Device <br /> ::* using &quot;Find device&quot; and using its current configuration the same way as for stored presets.<br /> <br /> :3) Select the preset or device and review the displayed configuration contents on the right side of the screen.&lt;br&gt; <br /> <br /> :4) Press &quot;Load values&quot; to pass the config values back to the device config screen &lt;br&gt;''Note the preset application will modify all the parameters defined in the preset on top of your current configuration.''&lt;br&gt;[[File:Presets_Apply_preset.jpg|700px]] <br /> <br /> :5a) Review if the preset applied correctly and expected values are shown (marked blue in the config screen). Submit your new configuration by clicking the „Sent“ button (same as after any manual config edit). Note, you can get rid of applied preset values (e.g when the wrong preset was applied) by simply closing the configuration screen.&lt;br&gt;[[File:Presets_Applied_values.jpg|900px]]<br /> <br /> :5b) Note that the geofence presets need to be confirmed separately<br /> :* The load preset dialogue will create a geofence definition in the geofence section as „disabled“<br /> :* You need to activate the geofence manually in the geofence definition screen<br /> :* A notification message helps you to decide on activating the loaded geofence in the geofencing sub-screen&lt;br&gt;[[File:Presets_Geofence_loaded_warning.jpg|600px]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1283 2025-12-05T13:04:20Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Various application features reviewed and consolidated (most changes in Groups/Projects and Load / Save Configuration Preset)<br /> * Related bug-fixing loop done. <br /> ''Please report any remaining imperfections spotted''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}} <br /> * a new &quot;Find device&quot; tool has been added in the Load Preset modal<br /> * another alternative way of loading existing config values from other devices<br /> * [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> <br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> {{Release note body end}}<br /> <br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Configuration&diff=1282 2025-12-05T12:00:07Z

<p>Admin: /* Advanced Configuration Management using Presets */</p> <hr /> <div>{{DISPLAYTITLE: CONFIGURATION}}<br /> <br /> ==Overview &amp; Basic Concepts==<br /> &lt;br&gt;<br /> : Users with admin rights (device owners/admins) can access the configuration from the lists and profiles using cogwheel icons. <br /> : Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> <br /> <br /> : User configuration screen is structured into three main areas<br /> :* Data collection settings<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> <br /> : Note many more advanced settings are possibly available to adjust device behavior upon request/need (device maintenance, troubleshooting, firmware upgrades, custom configuration/behavior - such as GPS accuracy, etc) <br /> <br /> <br /> : Any changes made are visualized by blue and red symbols close to the modified setting and in the top right corner of each modified section<br /> :* symbols (&quot;pen&quot;, &quot;clock&quot; and &quot;check&quot;) show the status of each configuration (edited (=blue &quot;pen&quot;) &gt;&gt; pending (=red &quot;clock&quot;) &gt;&gt; confirmed (=green &quot;check&quot;))<br /> : [[File:config_submitted_modified.JPG|400px]]<br /> <br /> <br /> : New modifications (not yet submitted) are highlighted by blue color<br /> :* these modifications can be reverted to saved values simply by closing the config screen or by clicking on the blue &quot;pen&quot; (for a particular parameter or on the section level) <br /> :* in order to submit the modified parameters, click the &quot;Send&quot; button below<br /> : [[File:config_send_discard(send).JPG|400px]]<br /> <br /> <br /> : Submitted values are highlighted by red color<br /> :* &gt;&gt; all the blue &quot;pen&quot; icons change to red &quot;clock&quot; icons indicating the value is waiting for the device to apply it<br /> :* note the configuration changes apply whenever the tag connects to communicate/send data <br /> <br /> <br /> : Until the values ​​are confirmed by the device the pending changes can be modified or canceled <br /> :* by clicking on the particular &quot;clock&quot; icon - for a particular parameter or on the section level<br /> :* by clicking on the &quot;Discard all pending changes&quot; button below - for canceling all<br /> : [[File:config_send_discard(discard).JPG|400px]]<br /> <br /> <br /> : Once the pending parameters are received, accepted, and confirmed successfully by the device the status is changed from red &quot;clock&quot; to green &quot;check&quot;<br /> :* note by default the configuration is sent and delivered to the device via GPRS data<br /> :* as a supplementary delivery channel SMS can be used (&quot;Send by SMS&quot; button)<br /> : [[File:config_send_discard(resendSMS).JPG|400px]]<br /> <br /> <br /> : Using SMS might help to deliver configuration mainly in certain areas with poor GPRS data coverage however please note using SMS has certain limitations<br /> :* SMS delivery is not a guaranteed channel (if not delivered SMS disappears from the network in a couple of hours) - this might cause inconsistency in device configuration temporarily <br /> :* just a small subset of the full configuration scope can be fit into one single SMS (therefore the &quot;Sent by SMS&quot; button is only available till the modifications made fit into one SMS message)<br /> :* also note additional charges might be applied when using SMS excessively<br /> <br /> == Configuration areas / Device features ==<br /> &lt;br&gt;<br /> : The configuration screen shows only <br /> <br /> :* the settings relevant to a particular hardware model, firmware version, etc. are available<br /> :* the options relevant to the context of previous selections are available (unrelated or conflicting options are hidden)<br /> <br /> <br /> === Data collection settings ===<br /> &lt;br&gt;<br /> : Left-side &quot;Data collection&quot; section concentrates all the controls related to data sampling<br /> <br /> : [[File:config_data_collection.jpg|900px.JPG]]<br /> <br /> <br /> ==== Scheduled GPS/sensor sampling ====<br /> &lt;br&gt;<br /> : Defines type and structure of data triggered by the scheduler and the actual schedules<br /> <br /> : Data scheduler offers two distinct modes<br /> :* defined as separate cycles or day and night<br /> :* defined as an interval (ignoring both human clock and day and night transitions)<br /> <br /> <br /> <br /> ===== Different day &amp; night cycles (night saving) =====<br /> &lt;br&gt;<br /> : Day/night and night/day transition is configured by sun angles (either typing in the angle form or comfortably using the slider below day/night graphic)<br /> <br /> : [[File:config_schedule_night_angles.JPG|700px]]<br /> <br /> <br /> : Measurement intervals within each daypart use <br /> <br /> <br /> :* '''&quot;human time&quot;''' (UTC clock) - intervals synchronized around defined UTC time (by default around UTC midnight)<br /> <br /> : [[File:config_schedule_night_human.JPG|700px]]<br /> <br /> <br /> :* '''&quot;solar time&quot;''' (i.e the local solar time for actual GPS position) <br /> <br /> <br /> :: By default, the sampling interval is restarted with each day/night and night/day transition (i.e. the first position is collected with the day/night transition)<br /> <br /> :: [[File:config_schedule_night_solar_start.JPG|700px]]<br /> <br /> <br /> :: Alternatively, the interval can be synchronized '''around solar midnight/noon''' (positions are evenly distributed around solar noon/midnight)<br /> <br /> :: [[File:config_schedule_night_solar_midnight.JPG|700px]]<br /> <br /> <br /> ===== Schedules defined as Interval =====<br /> &lt;br&gt;<br /> : Useful in situations when different day and night interval is not needed or when intensive energy saving needs to be achieved (data sampling within many hours or even days). A floating interval unrelated to the human UTC clock <br /> <br /> : [[File:Config_schedule_interval.JPG|600px]]<br /> <br /> ===== GPS/data measurements vs GPS/data bursts =====<br /> &lt;br&gt;<br /> : The scheduler can trigger both - single GPS/data measurements and/or GPS/data bursts. In default, single measurements are triggered.<br /> <br /> : When the burst launching is activated, an additional configuration section is displayed to specify burst behavior<br /> <br /> : [[File:config_schedule_burst.JPG|700px]]<br /> <br /> <br /> : Note the following about measurements and bursts:<br /> <br /> <br /> : '''GPS/data measurement''' <br /> <br /> :* Is a single planned (or activity-triggered) measurement event saving data from available/active sensors<br /> <br /> :* The full dataset structure contains GPS data (latitude, longitude, altitude, direction, speed, and GNSS quality metrics), solar and battery voltage/percent, 3ax-sensors data (accelerometer, magnetometer, gyroscope), temperature. barometric pressure, and some more value-added calculated measures)<br /> <br /> :* For sake of energy saving some measurements might be scheduled to run without activating the GNSS module and without waiting for GPS fix - i.e. '''interlacing''' GPS records with a sensor only records in data delivered into the database<br /> <br /> ::: By default, GPS is turned on for every measurement:<br /> ::: [[File:config_data_GPS_always.JPG|600px]]<br /> ::: GPS interlacing can be configured here (1 GPS position + 4 non GPS records taken):<br /> ::: [[File:config_data_GPS_each5.JPG|600px]]<br /> ::: GPS can be turned off completely like this<br /> ::: [[File:config_data_GPS_off.JPG|600px]]<br /> ::: Note these settings are ignored when mortality is detected.<br /> <br /> <br /> : '''GPS/data burst'''<br /> <br /> :* a time-limited (by &quot;burst length&quot;) continuous series of measurements at a defined sampling rate/interval (even down to 50Hz = 50 records/second)<br /> <br /> :* while running bursts the device is switched to data and energy-intensive mode - a minimum battery level restriction should be maintained at a safe level<br /> <br /> :* each of the sensor types used has a different &quot;maximum resolution&quot; - therefore in the case of running fast burst, we distinguish between <br /> :** '''&quot;slow&quot; data''' (GPS data, temperature, battery voltage, or barometric pressure) - these are only present in one-second data or slower and<br /> :** '''&quot;fast&quot; data''' (accelerometer, magnetometer, gyroscope) which can be sampled at a much higher frequency (e.g. up to 50hz) and saved in every record (e.g 50x per second)<br /> <br /> :* for sake of energy-saving the busts can be also run without activating GNSS and storing GPS data at all. <br /> :: [[File:config_burst_GNSSoff.JPG|700px]]<br /> <br /> :* for limiting data volume generated by fast bursts '''&quot;acc only&quot; mode''' is available (only accelerometer data are stored - not magnetometer and gyroscope data)<br /> :: [[File:config_burst_acconly.JPG|700px]]<br /> <br /> :* Starting of the GNSS module and acquiring GPS position typically lasts a couple of seconds - the following options allow adjusting the burst start behavior the way needed<br /> : [[File:config_data_burst_wait.JPG|500px]]<br /> : [[File:config_data_burst_wait_off.JPG|500px]]<br /> <br /> <br /> ==== Activity triggered data collection ====<br /> &lt;br&gt;<br /> : Range of triggers that can activate/wake up of the device when a certain activity event is detected by the hardware sensors<br /> : [[File:config_activity_triggers.JPG|800px]]<br /> <br /> <br /> : Currently implemented triggers<br /> <br /> <br /> :* &quot;wake up from accelerometer&quot; - based on sudden movement - e.g. can be used to detect take off / landing<br /> :* &quot;wake up from altimeter&quot; - based on height change in meters<br /> <br /> <br /> : Upon activation, the selected trigger can launch either a single measurement or burst<br /> : In case of using triggers for burst an additional burst configuration screen is opened (similar to bursts triggered by schedule)<br /> <br /> : [[File:config_activity_triggers_burst.JPG|800px]]<br /> <br /> ==== Speed triggered continuous GPS sampling ====<br /> &lt;br&gt;<br /> : A special functionality ensuring continuous GPS sampling till the object moves<br /> <br /> : The speed threshold, GPS sampling rate, and battery threshold are adjustable <br /> <br /> : [[File:config_speed_trigger.JPG|800px]]<br /> <br /> : If used in combination with well-configured activity triggers it can allow full movement coverage of tracked animals!<br /> <br /> ==== Mortality detection ====<br /> &lt;br&gt;<br /> : Dedicated Anitra proprietary algorithm based on accelerometer and gyroscope evaluation. Comparing to the older version the new version is much more sensitive and accurate.<br /> <br /> : When enabled, the mortality status is continuously evaluated and logged (note the device consumes additional energy).<br /> <br /> : As soon as the status changes to &quot;mortality detected&quot; or vice versa (i.e. from &quot;mortality&quot; to &quot;alive&quot;) the device automaticaly runs additional measurement (GPS+data) and stores this additional record into memory.<br /> <br /> : Config parameter &quot;run extra comm session..&quot; proactively launches extra communication and notify of the mortality event immediately.<br /> <br /> : Actual mortality state (in mortality/not in mortality) is stored in each dataset and usable for calibration for particular species or even individual/deployment.<br /> <br /> : Note the default configuration options are adjusted to detect while the tag is deployed as a backpack (best tested for raptors)<br /> <br /> : Calibration parameters are detection interval, number of confirmation cycles before the mortality warning is raised, and detection sensitivity<br /> <br /> :[[File:config_mortality.JPG|800px]]<br /> <br /> ==== Geofencing ====<br /> : ''(for the complete information about geofencing see detailed [[geofencing| geofencing configuration guide ]]'')<br /> &lt;br&gt;<br /> :Modifies standard device behavior based on the geographic location<br /> <br /> : Specifics of Anitra geofencing<br /> :* tailored for very advanced geofencing tasks on top of POI databases with even many thousands of items (e.g. database of past poisoning places, wind turbines, dangerous power pylons, etc)<br /> :* a dynamic geofence synchronization (when moving the tag synchronizes 100 closest geofence instances)<br /> :* geofences defined by circular (or possibly even cylindrical) zones<br /> :** working with circles allows resolving conflicts for overlapping geofences (as the closest, the smallest)<br /> :** altitude definition enables 3D geofencing (when higher it is considered as outside of geofence)<br /> <br /> : Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map<br /> :[[File:GF_map_definition.JPG|900px]]<br /> <br /> : A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence<br /> :* day/night data collection interval<br /> :* activity and speed triggering<br /> :* radio buoy activation<br /> :* communication while entering/leaving the geofence<br /> :[[File:GF_behavior.JPG|900px]]<br /> <br /> : ''(for the complete information about geofencing see detailed[[geofencing| geofencing configuration guide ]])''<br /> <br /> === Communication schedules ===<br /> <br /> : Right-side &quot;Communication plans&quot; section concentrates all the controls related to communications schedules/data delivery<br /> : [[File:config_comm_schedules.jpg|600px.JPG]]<br /> <br /> : Anitra devices offer a very wide range of communication setups to match best any particular field situation. Users can combine the following options in order to achieve desired behavior and data delivery timing<br /> <br /> :* Communication defined by intervals<br /> :* Communication defined by fixed UTC timeslots<br /> :* Communication based on number of records collected<br /> :* One-time communication UTC timeslots<br /> :* Additional options <br /> <br /> ==== Communication defined by intervals ====<br /> : This communication plan allows programming the tag to sent data regularly within defined cycles/intervals. The plans can be set up <br /> <br /> :* synchronized to human clock <br /> :** the interval is repeated within 24 hours and restarted at a defined sync time<br /> :** because of that only intervals matching 24 hours are allowed here (i.e. intervals of 1,2,3,4,6,12 hours)<br /> : [[File:config_comm_interval_synced.JPG|400px]]<br /> <br /> :* or floating (not synchronized to the clock)<br /> :** the interval is repeated independently of human clock hours <br /> :** the cycle is restarted with the applied change of the cycle (or when the device is completely discharged)<br /> :** any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication times from one day to another<br /> : [[File:config_comm_interval_nosync.JPG|400px]]<br /> <br /> : Note this schedule can not be completely turned off as it also acts as an &quot;emergency&quot; schedule (i.e. in case of accidentally turning off all other plans)<br /> : Even when turned off by a user the schedule is still triggered every 648 hours (27 days)<br /> : [[File:config_comm_interval_default.JPG|400px]]<br /> <br /> <br /> ==== Communication defined by fixed UTC timeslots ====<br /> : This functionality offers up to four &quot;fixed&quot; time slots <br /> :* fixed to a particular UTC day hour<br /> :* and run every X days defined per slot<br /> : [[File:config_fixedtime.JPG|400px]]<br /> <br /> <br /> ==== Communication based on number of records collected ====<br /> : Communication is relaunched whenever a defined number of records is collected by the tag<br /> : This setting might be particularly beneficial in case of the use of dynamic, unpredictable, or data-intensive sampling modes (such as data/burst triggered by activity or speed triggers)<br /> : [[File:config_comm_datatrigger.JPG|400px]]<br /> <br /> <br /> ==== One-time communication UTC timeslots ====<br /> : In this case, the tag enforces GPS position taking before running communication<br /> : A typical use case is planning the one-time session at the time of the planned field check (e.i. the tag delivers a fresh GPS position)<br /> : Allows parallel scheduling of up to four one-time communication sessions defined at a particular UTC date/time<br /> : [[File:config_comm_onetime.JPG|400px]]<br /> <br /> <br /> ==== Other communication-triggering events ====<br /> : Note the communication can also be triggered in some other situations<br /> <br /> :* device notifies its state in Power-off / Storage mode<br /> : [[File:config_comm_poweroff.JPG|400px]]<br /> <br /> :* mortality detection functionality can be configured to sent data when mortality is reliably confirmed<br /> : [[File:config_comm_mortality.JPG|400px]]<br /> <br /> :* POI/geofencing can also be configured to trigger communication (when entering POI)<br /> <br /> :* Finally a special SM communication session is trigger when regular data schedules fail cor certain number of days<br /> : [[File:config_comm_emergencySMS.JPG|400px]]<br /> <br /> <br /> : Taking into account above mentioned various communication sources the predictability of the next communication session is limited<br /> : The &quot;Next schedule&quot; prediction only factors schedules planned to UTC clock<br /> : [[File:config_comm_prediction.JPG|400px]]<br /> <br /> <br /> === Other user settings ===<br /> <br /> : Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control, etc)<br /> : [[File:config_other_settings.jpg|700px.JPG]]<br /> <br /> <br /> === Storage mode ===<br /> * allows bringing the device to low energy consumption mode<br /> * the device is powered off most of the time and only wakes up at 00:00 UTC in a specified day interval to send tag status (one dataset - GPS, battery level, etc.)<br /> * the communication interval can be set between 1 and 32 days<br /> * using storage mode is useful for long-distance transport and for storing undeployed devices longer time (e.g. when solar charging or GPS signal is unavailable longterm)<br /> [[File:config_poweroff.JPG|500px]]<br /> <br /> <br /> == Advanced Configuration Management using Presets ==<br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''<br /> &lt;br&gt;<br /> : This functionality allows saving the current device configuration (combination of parameters) into the &quot;Configuration Preset&quot; object.<br /> <br /> : Only the &quot;user&quot; values generally applicable are saved (device unique &quot;admin&quot; values, such as ID, mobile phone number or individual calibration values, are not included).<br /> <br /> : A complete or just a subset of &quot;user&quot; configuration can be saved as a preset. Eg, you can save only communication settings in the first preset, data collection settings in another, and geofence settings in the third separate preset. <br /> <br /> : Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.<br /> <br /> === Preset creation ===<br /> <br /> :* use the „Save as preset“ button in the config screen<br /> :* name the preset<br /> :* review and adjust the contents<br /> :* save when all done&lt;br&gt;[[File:Presets_Save_as_Preset.jpg|700px]]<br /> <br /> === Loading existing preset ===<br /> <br /> :* use the „Load preset“ button<br /> :* look up the stored preset<br /> :** either using &quot;Find preset&quot;<br /> :** or choosing from &quot;My presets&quot; <br /> :* alternatively, you can pick another device using &quot;Find device&quot; and use its current configuration the same way as for stored presets<br /> :* pick the preset or device and review the displayed configuration contents<br /> :* load values back to the device config screen<br /> :* review if preset values loaded correctly (marked blue in the config screen)<br /> :* submit modified configuration same as you do for manual config changes and activate geofences created by preset&lt;br&gt;&lt;br&gt;[[File:Presets_Apply_preset.jpg|600px]] <br /> <br /> <br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''</div>

Admin index.php?title=Configuration&diff=1281 2025-12-05T11:57:29Z

<p>Admin: /* Advanced Configuration Management using Presets */</p> <hr /> <div>{{DISPLAYTITLE: CONFIGURATION}}<br /> <br /> ==Overview &amp; Basic Concepts==<br /> &lt;br&gt;<br /> : Users with admin rights (device owners/admins) can access the configuration from the lists and profiles using cogwheel icons. <br /> : Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> <br /> <br /> : User configuration screen is structured into three main areas<br /> :* Data collection settings<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> <br /> : Note many more advanced settings are possibly available to adjust device behavior upon request/need (device maintenance, troubleshooting, firmware upgrades, custom configuration/behavior - such as GPS accuracy, etc) <br /> <br /> <br /> : Any changes made are visualized by blue and red symbols close to the modified setting and in the top right corner of each modified section<br /> :* symbols (&quot;pen&quot;, &quot;clock&quot; and &quot;check&quot;) show the status of each configuration (edited (=blue &quot;pen&quot;) &gt;&gt; pending (=red &quot;clock&quot;) &gt;&gt; confirmed (=green &quot;check&quot;))<br /> : [[File:config_submitted_modified.JPG|400px]]<br /> <br /> <br /> : New modifications (not yet submitted) are highlighted by blue color<br /> :* these modifications can be reverted to saved values simply by closing the config screen or by clicking on the blue &quot;pen&quot; (for a particular parameter or on the section level) <br /> :* in order to submit the modified parameters, click the &quot;Send&quot; button below<br /> : [[File:config_send_discard(send).JPG|400px]]<br /> <br /> <br /> : Submitted values are highlighted by red color<br /> :* &gt;&gt; all the blue &quot;pen&quot; icons change to red &quot;clock&quot; icons indicating the value is waiting for the device to apply it<br /> :* note the configuration changes apply whenever the tag connects to communicate/send data <br /> <br /> <br /> : Until the values ​​are confirmed by the device the pending changes can be modified or canceled <br /> :* by clicking on the particular &quot;clock&quot; icon - for a particular parameter or on the section level<br /> :* by clicking on the &quot;Discard all pending changes&quot; button below - for canceling all<br /> : [[File:config_send_discard(discard).JPG|400px]]<br /> <br /> <br /> : Once the pending parameters are received, accepted, and confirmed successfully by the device the status is changed from red &quot;clock&quot; to green &quot;check&quot;<br /> :* note by default the configuration is sent and delivered to the device via GPRS data<br /> :* as a supplementary delivery channel SMS can be used (&quot;Send by SMS&quot; button)<br /> : [[File:config_send_discard(resendSMS).JPG|400px]]<br /> <br /> <br /> : Using SMS might help to deliver configuration mainly in certain areas with poor GPRS data coverage however please note using SMS has certain limitations<br /> :* SMS delivery is not a guaranteed channel (if not delivered SMS disappears from the network in a couple of hours) - this might cause inconsistency in device configuration temporarily <br /> :* just a small subset of the full configuration scope can be fit into one single SMS (therefore the &quot;Sent by SMS&quot; button is only available till the modifications made fit into one SMS message)<br /> :* also note additional charges might be applied when using SMS excessively<br /> <br /> == Configuration areas / Device features ==<br /> &lt;br&gt;<br /> : The configuration screen shows only <br /> <br /> :* the settings relevant to a particular hardware model, firmware version, etc. are available<br /> :* the options relevant to the context of previous selections are available (unrelated or conflicting options are hidden)<br /> <br /> <br /> === Data collection settings ===<br /> &lt;br&gt;<br /> : Left-side &quot;Data collection&quot; section concentrates all the controls related to data sampling<br /> <br /> : [[File:config_data_collection.jpg|900px.JPG]]<br /> <br /> <br /> ==== Scheduled GPS/sensor sampling ====<br /> &lt;br&gt;<br /> : Defines type and structure of data triggered by the scheduler and the actual schedules<br /> <br /> : Data scheduler offers two distinct modes<br /> :* defined as separate cycles or day and night<br /> :* defined as an interval (ignoring both human clock and day and night transitions)<br /> <br /> <br /> <br /> ===== Different day &amp; night cycles (night saving) =====<br /> &lt;br&gt;<br /> : Day/night and night/day transition is configured by sun angles (either typing in the angle form or comfortably using the slider below day/night graphic)<br /> <br /> : [[File:config_schedule_night_angles.JPG|700px]]<br /> <br /> <br /> : Measurement intervals within each daypart use <br /> <br /> <br /> :* '''&quot;human time&quot;''' (UTC clock) - intervals synchronized around defined UTC time (by default around UTC midnight)<br /> <br /> : [[File:config_schedule_night_human.JPG|700px]]<br /> <br /> <br /> :* '''&quot;solar time&quot;''' (i.e the local solar time for actual GPS position) <br /> <br /> <br /> :: By default, the sampling interval is restarted with each day/night and night/day transition (i.e. the first position is collected with the day/night transition)<br /> <br /> :: [[File:config_schedule_night_solar_start.JPG|700px]]<br /> <br /> <br /> :: Alternatively, the interval can be synchronized '''around solar midnight/noon''' (positions are evenly distributed around solar noon/midnight)<br /> <br /> :: [[File:config_schedule_night_solar_midnight.JPG|700px]]<br /> <br /> <br /> ===== Schedules defined as Interval =====<br /> &lt;br&gt;<br /> : Useful in situations when different day and night interval is not needed or when intensive energy saving needs to be achieved (data sampling within many hours or even days). A floating interval unrelated to the human UTC clock <br /> <br /> : [[File:Config_schedule_interval.JPG|600px]]<br /> <br /> ===== GPS/data measurements vs GPS/data bursts =====<br /> &lt;br&gt;<br /> : The scheduler can trigger both - single GPS/data measurements and/or GPS/data bursts. In default, single measurements are triggered.<br /> <br /> : When the burst launching is activated, an additional configuration section is displayed to specify burst behavior<br /> <br /> : [[File:config_schedule_burst.JPG|700px]]<br /> <br /> <br /> : Note the following about measurements and bursts:<br /> <br /> <br /> : '''GPS/data measurement''' <br /> <br /> :* Is a single planned (or activity-triggered) measurement event saving data from available/active sensors<br /> <br /> :* The full dataset structure contains GPS data (latitude, longitude, altitude, direction, speed, and GNSS quality metrics), solar and battery voltage/percent, 3ax-sensors data (accelerometer, magnetometer, gyroscope), temperature. barometric pressure, and some more value-added calculated measures)<br /> <br /> :* For sake of energy saving some measurements might be scheduled to run without activating the GNSS module and without waiting for GPS fix - i.e. '''interlacing''' GPS records with a sensor only records in data delivered into the database<br /> <br /> ::: By default, GPS is turned on for every measurement:<br /> ::: [[File:config_data_GPS_always.JPG|600px]]<br /> ::: GPS interlacing can be configured here (1 GPS position + 4 non GPS records taken):<br /> ::: [[File:config_data_GPS_each5.JPG|600px]]<br /> ::: GPS can be turned off completely like this<br /> ::: [[File:config_data_GPS_off.JPG|600px]]<br /> ::: Note these settings are ignored when mortality is detected.<br /> <br /> <br /> : '''GPS/data burst'''<br /> <br /> :* a time-limited (by &quot;burst length&quot;) continuous series of measurements at a defined sampling rate/interval (even down to 50Hz = 50 records/second)<br /> <br /> :* while running bursts the device is switched to data and energy-intensive mode - a minimum battery level restriction should be maintained at a safe level<br /> <br /> :* each of the sensor types used has a different &quot;maximum resolution&quot; - therefore in the case of running fast burst, we distinguish between <br /> :** '''&quot;slow&quot; data''' (GPS data, temperature, battery voltage, or barometric pressure) - these are only present in one-second data or slower and<br /> :** '''&quot;fast&quot; data''' (accelerometer, magnetometer, gyroscope) which can be sampled at a much higher frequency (e.g. up to 50hz) and saved in every record (e.g 50x per second)<br /> <br /> :* for sake of energy-saving the busts can be also run without activating GNSS and storing GPS data at all. <br /> :: [[File:config_burst_GNSSoff.JPG|700px]]<br /> <br /> :* for limiting data volume generated by fast bursts '''&quot;acc only&quot; mode''' is available (only accelerometer data are stored - not magnetometer and gyroscope data)<br /> :: [[File:config_burst_acconly.JPG|700px]]<br /> <br /> :* Starting of the GNSS module and acquiring GPS position typically lasts a couple of seconds - the following options allow adjusting the burst start behavior the way needed<br /> : [[File:config_data_burst_wait.JPG|500px]]<br /> : [[File:config_data_burst_wait_off.JPG|500px]]<br /> <br /> <br /> ==== Activity triggered data collection ====<br /> &lt;br&gt;<br /> : Range of triggers that can activate/wake up of the device when a certain activity event is detected by the hardware sensors<br /> : [[File:config_activity_triggers.JPG|800px]]<br /> <br /> <br /> : Currently implemented triggers<br /> <br /> <br /> :* &quot;wake up from accelerometer&quot; - based on sudden movement - e.g. can be used to detect take off / landing<br /> :* &quot;wake up from altimeter&quot; - based on height change in meters<br /> <br /> <br /> : Upon activation, the selected trigger can launch either a single measurement or burst<br /> : In case of using triggers for burst an additional burst configuration screen is opened (similar to bursts triggered by schedule)<br /> <br /> : [[File:config_activity_triggers_burst.JPG|800px]]<br /> <br /> ==== Speed triggered continuous GPS sampling ====<br /> &lt;br&gt;<br /> : A special functionality ensuring continuous GPS sampling till the object moves<br /> <br /> : The speed threshold, GPS sampling rate, and battery threshold are adjustable <br /> <br /> : [[File:config_speed_trigger.JPG|800px]]<br /> <br /> : If used in combination with well-configured activity triggers it can allow full movement coverage of tracked animals!<br /> <br /> ==== Mortality detection ====<br /> &lt;br&gt;<br /> : Dedicated Anitra proprietary algorithm based on accelerometer and gyroscope evaluation. Comparing to the older version the new version is much more sensitive and accurate.<br /> <br /> : When enabled, the mortality status is continuously evaluated and logged (note the device consumes additional energy).<br /> <br /> : As soon as the status changes to &quot;mortality detected&quot; or vice versa (i.e. from &quot;mortality&quot; to &quot;alive&quot;) the device automaticaly runs additional measurement (GPS+data) and stores this additional record into memory.<br /> <br /> : Config parameter &quot;run extra comm session..&quot; proactively launches extra communication and notify of the mortality event immediately.<br /> <br /> : Actual mortality state (in mortality/not in mortality) is stored in each dataset and usable for calibration for particular species or even individual/deployment.<br /> <br /> : Note the default configuration options are adjusted to detect while the tag is deployed as a backpack (best tested for raptors)<br /> <br /> : Calibration parameters are detection interval, number of confirmation cycles before the mortality warning is raised, and detection sensitivity<br /> <br /> :[[File:config_mortality.JPG|800px]]<br /> <br /> ==== Geofencing ====<br /> : ''(for the complete information about geofencing see detailed [[geofencing| geofencing configuration guide ]]'')<br /> &lt;br&gt;<br /> :Modifies standard device behavior based on the geographic location<br /> <br /> : Specifics of Anitra geofencing<br /> :* tailored for very advanced geofencing tasks on top of POI databases with even many thousands of items (e.g. database of past poisoning places, wind turbines, dangerous power pylons, etc)<br /> :* a dynamic geofence synchronization (when moving the tag synchronizes 100 closest geofence instances)<br /> :* geofences defined by circular (or possibly even cylindrical) zones<br /> :** working with circles allows resolving conflicts for overlapping geofences (as the closest, the smallest)<br /> :** altitude definition enables 3D geofencing (when higher it is considered as outside of geofence)<br /> <br /> : Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map<br /> :[[File:GF_map_definition.JPG|900px]]<br /> <br /> : A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence<br /> :* day/night data collection interval<br /> :* activity and speed triggering<br /> :* radio buoy activation<br /> :* communication while entering/leaving the geofence<br /> :[[File:GF_behavior.JPG|900px]]<br /> <br /> : ''(for the complete information about geofencing see detailed[[geofencing| geofencing configuration guide ]])''<br /> <br /> === Communication schedules ===<br /> <br /> : Right-side &quot;Communication plans&quot; section concentrates all the controls related to communications schedules/data delivery<br /> : [[File:config_comm_schedules.jpg|600px.JPG]]<br /> <br /> : Anitra devices offer a very wide range of communication setups to match best any particular field situation. Users can combine the following options in order to achieve desired behavior and data delivery timing<br /> <br /> :* Communication defined by intervals<br /> :* Communication defined by fixed UTC timeslots<br /> :* Communication based on number of records collected<br /> :* One-time communication UTC timeslots<br /> :* Additional options <br /> <br /> ==== Communication defined by intervals ====<br /> : This communication plan allows programming the tag to sent data regularly within defined cycles/intervals. The plans can be set up <br /> <br /> :* synchronized to human clock <br /> :** the interval is repeated within 24 hours and restarted at a defined sync time<br /> :** because of that only intervals matching 24 hours are allowed here (i.e. intervals of 1,2,3,4,6,12 hours)<br /> : [[File:config_comm_interval_synced.JPG|400px]]<br /> <br /> :* or floating (not synchronized to the clock)<br /> :** the interval is repeated independently of human clock hours <br /> :** the cycle is restarted with the applied change of the cycle (or when the device is completely discharged)<br /> :** any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication times from one day to another<br /> : [[File:config_comm_interval_nosync.JPG|400px]]<br /> <br /> : Note this schedule can not be completely turned off as it also acts as an &quot;emergency&quot; schedule (i.e. in case of accidentally turning off all other plans)<br /> : Even when turned off by a user the schedule is still triggered every 648 hours (27 days)<br /> : [[File:config_comm_interval_default.JPG|400px]]<br /> <br /> <br /> ==== Communication defined by fixed UTC timeslots ====<br /> : This functionality offers up to four &quot;fixed&quot; time slots <br /> :* fixed to a particular UTC day hour<br /> :* and run every X days defined per slot<br /> : [[File:config_fixedtime.JPG|400px]]<br /> <br /> <br /> ==== Communication based on number of records collected ====<br /> : Communication is relaunched whenever a defined number of records is collected by the tag<br /> : This setting might be particularly beneficial in case of the use of dynamic, unpredictable, or data-intensive sampling modes (such as data/burst triggered by activity or speed triggers)<br /> : [[File:config_comm_datatrigger.JPG|400px]]<br /> <br /> <br /> ==== One-time communication UTC timeslots ====<br /> : In this case, the tag enforces GPS position taking before running communication<br /> : A typical use case is planning the one-time session at the time of the planned field check (e.i. the tag delivers a fresh GPS position)<br /> : Allows parallel scheduling of up to four one-time communication sessions defined at a particular UTC date/time<br /> : [[File:config_comm_onetime.JPG|400px]]<br /> <br /> <br /> ==== Other communication-triggering events ====<br /> : Note the communication can also be triggered in some other situations<br /> <br /> :* device notifies its state in Power-off / Storage mode<br /> : [[File:config_comm_poweroff.JPG|400px]]<br /> <br /> :* mortality detection functionality can be configured to sent data when mortality is reliably confirmed<br /> : [[File:config_comm_mortality.JPG|400px]]<br /> <br /> :* POI/geofencing can also be configured to trigger communication (when entering POI)<br /> <br /> :* Finally a special SM communication session is trigger when regular data schedules fail cor certain number of days<br /> : [[File:config_comm_emergencySMS.JPG|400px]]<br /> <br /> <br /> : Taking into account above mentioned various communication sources the predictability of the next communication session is limited<br /> : The &quot;Next schedule&quot; prediction only factors schedules planned to UTC clock<br /> : [[File:config_comm_prediction.JPG|400px]]<br /> <br /> <br /> === Other user settings ===<br /> <br /> : Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control, etc)<br /> : [[File:config_other_settings.jpg|700px.JPG]]<br /> <br /> <br /> === Storage mode ===<br /> * allows bringing the device to low energy consumption mode<br /> * the device is powered off most of the time and only wakes up at 00:00 UTC in a specified day interval to send tag status (one dataset - GPS, battery level, etc.)<br /> * the communication interval can be set between 1 and 32 days<br /> * using storage mode is useful for long-distance transport and for storing undeployed devices longer time (e.g. when solar charging or GPS signal is unavailable longterm)<br /> [[File:config_poweroff.JPG|500px]]<br /> <br /> <br /> == Advanced Configuration Management using Presets ==<br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''<br /> &lt;br&gt;<br /> : This functionality allows saving the current device configuration (combination of parameters) into the &quot;Configuration Preset&quot; object.<br /> <br /> : Only the &quot;user&quot; values generally applicable are saved (device unique &quot;admin&quot; values, such as ID, mobile phone number or individual calibration values, are not included).<br /> <br /> : A complete or just a subset of &quot;user&quot; configuration can be saved as a preset. Eg, you can save only communication settings in the first preset, data collection settings in another, and geofence settings in the third separate preset. <br /> <br /> : Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.<br /> <br /> === Preset creation ===<br /> <br /> :* use the „Save as preset“ button in the config screen<br /> :* name the preset<br /> :* review and adjust the contents<br /> :* save when all done&lt;br&gt;[[File:Presets_Save_as_Preset.jpg|700px]]<br /> <br /> === Loading existing preset ===<br /> <br /> :* use the „Load preset“ button<br /> :* look up the stored preset<br /> :** either using &quot;Find preset&quot;<br /> :** or choosing from &quot;My presets&quot; <br /> :* alternatively, you can pick another device using &quot;Find device&quot; and use its current configuration the same way as for stored presets<br /> :* pick the preset or device and review the displayed configuration contents<br /> :* load values back to the device config screen<br /> :* review if preset values loaded correctly (marked blue in the config screen)<br /> :* submit modified configuration &amp; activate geofences created&lt;br&gt;&lt;br&gt;[[File:Presets_Apply_preset.jpg|600px]] same as zou do for manual config changes<br /> <br /> <br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''</div>

Admin index.php?title=Configuration&diff=1280 2025-12-05T11:08:47Z

<p>Admin: /* Advanced Concepts */</p> <hr /> <div>{{DISPLAYTITLE: CONFIGURATION}}<br /> <br /> ==Overview &amp; Basic Concepts==<br /> &lt;br&gt;<br /> : Users with admin rights (device owners/admins) can access the configuration from the lists and profiles using cogwheel icons. <br /> : Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> <br /> <br /> : User configuration screen is structured into three main areas<br /> :* Data collection settings<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> <br /> : Note many more advanced settings are possibly available to adjust device behavior upon request/need (device maintenance, troubleshooting, firmware upgrades, custom configuration/behavior - such as GPS accuracy, etc) <br /> <br /> <br /> : Any changes made are visualized by blue and red symbols close to the modified setting and in the top right corner of each modified section<br /> :* symbols (&quot;pen&quot;, &quot;clock&quot; and &quot;check&quot;) show the status of each configuration (edited (=blue &quot;pen&quot;) &gt;&gt; pending (=red &quot;clock&quot;) &gt;&gt; confirmed (=green &quot;check&quot;))<br /> : [[File:config_submitted_modified.JPG|400px]]<br /> <br /> <br /> : New modifications (not yet submitted) are highlighted by blue color<br /> :* these modifications can be reverted to saved values simply by closing the config screen or by clicking on the blue &quot;pen&quot; (for a particular parameter or on the section level) <br /> :* in order to submit the modified parameters, click the &quot;Send&quot; button below<br /> : [[File:config_send_discard(send).JPG|400px]]<br /> <br /> <br /> : Submitted values are highlighted by red color<br /> :* &gt;&gt; all the blue &quot;pen&quot; icons change to red &quot;clock&quot; icons indicating the value is waiting for the device to apply it<br /> :* note the configuration changes apply whenever the tag connects to communicate/send data <br /> <br /> <br /> : Until the values ​​are confirmed by the device the pending changes can be modified or canceled <br /> :* by clicking on the particular &quot;clock&quot; icon - for a particular parameter or on the section level<br /> :* by clicking on the &quot;Discard all pending changes&quot; button below - for canceling all<br /> : [[File:config_send_discard(discard).JPG|400px]]<br /> <br /> <br /> : Once the pending parameters are received, accepted, and confirmed successfully by the device the status is changed from red &quot;clock&quot; to green &quot;check&quot;<br /> :* note by default the configuration is sent and delivered to the device via GPRS data<br /> :* as a supplementary delivery channel SMS can be used (&quot;Send by SMS&quot; button)<br /> : [[File:config_send_discard(resendSMS).JPG|400px]]<br /> <br /> <br /> : Using SMS might help to deliver configuration mainly in certain areas with poor GPRS data coverage however please note using SMS has certain limitations<br /> :* SMS delivery is not a guaranteed channel (if not delivered SMS disappears from the network in a couple of hours) - this might cause inconsistency in device configuration temporarily <br /> :* just a small subset of the full configuration scope can be fit into one single SMS (therefore the &quot;Sent by SMS&quot; button is only available till the modifications made fit into one SMS message)<br /> :* also note additional charges might be applied when using SMS excessively<br /> <br /> == Configuration areas / Device features ==<br /> &lt;br&gt;<br /> : The configuration screen shows only <br /> <br /> :* the settings relevant to a particular hardware model, firmware version, etc. are available<br /> :* the options relevant to the context of previous selections are available (unrelated or conflicting options are hidden)<br /> <br /> <br /> === Data collection settings ===<br /> &lt;br&gt;<br /> : Left-side &quot;Data collection&quot; section concentrates all the controls related to data sampling<br /> <br /> : [[File:config_data_collection.jpg|900px.JPG]]<br /> <br /> <br /> ==== Scheduled GPS/sensor sampling ====<br /> &lt;br&gt;<br /> : Defines type and structure of data triggered by the scheduler and the actual schedules<br /> <br /> : Data scheduler offers two distinct modes<br /> :* defined as separate cycles or day and night<br /> :* defined as an interval (ignoring both human clock and day and night transitions)<br /> <br /> <br /> <br /> ===== Different day &amp; night cycles (night saving) =====<br /> &lt;br&gt;<br /> : Day/night and night/day transition is configured by sun angles (either typing in the angle form or comfortably using the slider below day/night graphic)<br /> <br /> : [[File:config_schedule_night_angles.JPG|700px]]<br /> <br /> <br /> : Measurement intervals within each daypart use <br /> <br /> <br /> :* '''&quot;human time&quot;''' (UTC clock) - intervals synchronized around defined UTC time (by default around UTC midnight)<br /> <br /> : [[File:config_schedule_night_human.JPG|700px]]<br /> <br /> <br /> :* '''&quot;solar time&quot;''' (i.e the local solar time for actual GPS position) <br /> <br /> <br /> :: By default, the sampling interval is restarted with each day/night and night/day transition (i.e. the first position is collected with the day/night transition)<br /> <br /> :: [[File:config_schedule_night_solar_start.JPG|700px]]<br /> <br /> <br /> :: Alternatively, the interval can be synchronized '''around solar midnight/noon''' (positions are evenly distributed around solar noon/midnight)<br /> <br /> :: [[File:config_schedule_night_solar_midnight.JPG|700px]]<br /> <br /> <br /> ===== Schedules defined as Interval =====<br /> &lt;br&gt;<br /> : Useful in situations when different day and night interval is not needed or when intensive energy saving needs to be achieved (data sampling within many hours or even days). A floating interval unrelated to the human UTC clock <br /> <br /> : [[File:Config_schedule_interval.JPG|600px]]<br /> <br /> ===== GPS/data measurements vs GPS/data bursts =====<br /> &lt;br&gt;<br /> : The scheduler can trigger both - single GPS/data measurements and/or GPS/data bursts. In default, single measurements are triggered.<br /> <br /> : When the burst launching is activated, an additional configuration section is displayed to specify burst behavior<br /> <br /> : [[File:config_schedule_burst.JPG|700px]]<br /> <br /> <br /> : Note the following about measurements and bursts:<br /> <br /> <br /> : '''GPS/data measurement''' <br /> <br /> :* Is a single planned (or activity-triggered) measurement event saving data from available/active sensors<br /> <br /> :* The full dataset structure contains GPS data (latitude, longitude, altitude, direction, speed, and GNSS quality metrics), solar and battery voltage/percent, 3ax-sensors data (accelerometer, magnetometer, gyroscope), temperature. barometric pressure, and some more value-added calculated measures)<br /> <br /> :* For sake of energy saving some measurements might be scheduled to run without activating the GNSS module and without waiting for GPS fix - i.e. '''interlacing''' GPS records with a sensor only records in data delivered into the database<br /> <br /> ::: By default, GPS is turned on for every measurement:<br /> ::: [[File:config_data_GPS_always.JPG|600px]]<br /> ::: GPS interlacing can be configured here (1 GPS position + 4 non GPS records taken):<br /> ::: [[File:config_data_GPS_each5.JPG|600px]]<br /> ::: GPS can be turned off completely like this<br /> ::: [[File:config_data_GPS_off.JPG|600px]]<br /> ::: Note these settings are ignored when mortality is detected.<br /> <br /> <br /> : '''GPS/data burst'''<br /> <br /> :* a time-limited (by &quot;burst length&quot;) continuous series of measurements at a defined sampling rate/interval (even down to 50Hz = 50 records/second)<br /> <br /> :* while running bursts the device is switched to data and energy-intensive mode - a minimum battery level restriction should be maintained at a safe level<br /> <br /> :* each of the sensor types used has a different &quot;maximum resolution&quot; - therefore in the case of running fast burst, we distinguish between <br /> :** '''&quot;slow&quot; data''' (GPS data, temperature, battery voltage, or barometric pressure) - these are only present in one-second data or slower and<br /> :** '''&quot;fast&quot; data''' (accelerometer, magnetometer, gyroscope) which can be sampled at a much higher frequency (e.g. up to 50hz) and saved in every record (e.g 50x per second)<br /> <br /> :* for sake of energy-saving the busts can be also run without activating GNSS and storing GPS data at all. <br /> :: [[File:config_burst_GNSSoff.JPG|700px]]<br /> <br /> :* for limiting data volume generated by fast bursts '''&quot;acc only&quot; mode''' is available (only accelerometer data are stored - not magnetometer and gyroscope data)<br /> :: [[File:config_burst_acconly.JPG|700px]]<br /> <br /> :* Starting of the GNSS module and acquiring GPS position typically lasts a couple of seconds - the following options allow adjusting the burst start behavior the way needed<br /> : [[File:config_data_burst_wait.JPG|500px]]<br /> : [[File:config_data_burst_wait_off.JPG|500px]]<br /> <br /> <br /> ==== Activity triggered data collection ====<br /> &lt;br&gt;<br /> : Range of triggers that can activate/wake up of the device when a certain activity event is detected by the hardware sensors<br /> : [[File:config_activity_triggers.JPG|800px]]<br /> <br /> <br /> : Currently implemented triggers<br /> <br /> <br /> :* &quot;wake up from accelerometer&quot; - based on sudden movement - e.g. can be used to detect take off / landing<br /> :* &quot;wake up from altimeter&quot; - based on height change in meters<br /> <br /> <br /> : Upon activation, the selected trigger can launch either a single measurement or burst<br /> : In case of using triggers for burst an additional burst configuration screen is opened (similar to bursts triggered by schedule)<br /> <br /> : [[File:config_activity_triggers_burst.JPG|800px]]<br /> <br /> ==== Speed triggered continuous GPS sampling ====<br /> &lt;br&gt;<br /> : A special functionality ensuring continuous GPS sampling till the object moves<br /> <br /> : The speed threshold, GPS sampling rate, and battery threshold are adjustable <br /> <br /> : [[File:config_speed_trigger.JPG|800px]]<br /> <br /> : If used in combination with well-configured activity triggers it can allow full movement coverage of tracked animals!<br /> <br /> ==== Mortality detection ====<br /> &lt;br&gt;<br /> : Dedicated Anitra proprietary algorithm based on accelerometer and gyroscope evaluation. Comparing to the older version the new version is much more sensitive and accurate.<br /> <br /> : When enabled, the mortality status is continuously evaluated and logged (note the device consumes additional energy).<br /> <br /> : As soon as the status changes to &quot;mortality detected&quot; or vice versa (i.e. from &quot;mortality&quot; to &quot;alive&quot;) the device automaticaly runs additional measurement (GPS+data) and stores this additional record into memory.<br /> <br /> : Config parameter &quot;run extra comm session..&quot; proactively launches extra communication and notify of the mortality event immediately.<br /> <br /> : Actual mortality state (in mortality/not in mortality) is stored in each dataset and usable for calibration for particular species or even individual/deployment.<br /> <br /> : Note the default configuration options are adjusted to detect while the tag is deployed as a backpack (best tested for raptors)<br /> <br /> : Calibration parameters are detection interval, number of confirmation cycles before the mortality warning is raised, and detection sensitivity<br /> <br /> :[[File:config_mortality.JPG|800px]]<br /> <br /> ==== Geofencing ====<br /> : ''(for the complete information about geofencing see detailed [[geofencing| geofencing configuration guide ]]'')<br /> &lt;br&gt;<br /> :Modifies standard device behavior based on the geographic location<br /> <br /> : Specifics of Anitra geofencing<br /> :* tailored for very advanced geofencing tasks on top of POI databases with even many thousands of items (e.g. database of past poisoning places, wind turbines, dangerous power pylons, etc)<br /> :* a dynamic geofence synchronization (when moving the tag synchronizes 100 closest geofence instances)<br /> :* geofences defined by circular (or possibly even cylindrical) zones<br /> :** working with circles allows resolving conflicts for overlapping geofences (as the closest, the smallest)<br /> :** altitude definition enables 3D geofencing (when higher it is considered as outside of geofence)<br /> <br /> : Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map<br /> :[[File:GF_map_definition.JPG|900px]]<br /> <br /> : A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence<br /> :* day/night data collection interval<br /> :* activity and speed triggering<br /> :* radio buoy activation<br /> :* communication while entering/leaving the geofence<br /> :[[File:GF_behavior.JPG|900px]]<br /> <br /> : ''(for the complete information about geofencing see detailed[[geofencing| geofencing configuration guide ]])''<br /> <br /> === Communication schedules ===<br /> <br /> : Right-side &quot;Communication plans&quot; section concentrates all the controls related to communications schedules/data delivery<br /> : [[File:config_comm_schedules.jpg|600px.JPG]]<br /> <br /> : Anitra devices offer a very wide range of communication setups to match best any particular field situation. Users can combine the following options in order to achieve desired behavior and data delivery timing<br /> <br /> :* Communication defined by intervals<br /> :* Communication defined by fixed UTC timeslots<br /> :* Communication based on number of records collected<br /> :* One-time communication UTC timeslots<br /> :* Additional options <br /> <br /> ==== Communication defined by intervals ====<br /> : This communication plan allows programming the tag to sent data regularly within defined cycles/intervals. The plans can be set up <br /> <br /> :* synchronized to human clock <br /> :** the interval is repeated within 24 hours and restarted at a defined sync time<br /> :** because of that only intervals matching 24 hours are allowed here (i.e. intervals of 1,2,3,4,6,12 hours)<br /> : [[File:config_comm_interval_synced.JPG|400px]]<br /> <br /> :* or floating (not synchronized to the clock)<br /> :** the interval is repeated independently of human clock hours <br /> :** the cycle is restarted with the applied change of the cycle (or when the device is completely discharged)<br /> :** any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication times from one day to another<br /> : [[File:config_comm_interval_nosync.JPG|400px]]<br /> <br /> : Note this schedule can not be completely turned off as it also acts as an &quot;emergency&quot; schedule (i.e. in case of accidentally turning off all other plans)<br /> : Even when turned off by a user the schedule is still triggered every 648 hours (27 days)<br /> : [[File:config_comm_interval_default.JPG|400px]]<br /> <br /> <br /> ==== Communication defined by fixed UTC timeslots ====<br /> : This functionality offers up to four &quot;fixed&quot; time slots <br /> :* fixed to a particular UTC day hour<br /> :* and run every X days defined per slot<br /> : [[File:config_fixedtime.JPG|400px]]<br /> <br /> <br /> ==== Communication based on number of records collected ====<br /> : Communication is relaunched whenever a defined number of records is collected by the tag<br /> : This setting might be particularly beneficial in case of the use of dynamic, unpredictable, or data-intensive sampling modes (such as data/burst triggered by activity or speed triggers)<br /> : [[File:config_comm_datatrigger.JPG|400px]]<br /> <br /> <br /> ==== One-time communication UTC timeslots ====<br /> : In this case, the tag enforces GPS position taking before running communication<br /> : A typical use case is planning the one-time session at the time of the planned field check (e.i. the tag delivers a fresh GPS position)<br /> : Allows parallel scheduling of up to four one-time communication sessions defined at a particular UTC date/time<br /> : [[File:config_comm_onetime.JPG|400px]]<br /> <br /> <br /> ==== Other communication-triggering events ====<br /> : Note the communication can also be triggered in some other situations<br /> <br /> :* device notifies its state in Power-off / Storage mode<br /> : [[File:config_comm_poweroff.JPG|400px]]<br /> <br /> :* mortality detection functionality can be configured to sent data when mortality is reliably confirmed<br /> : [[File:config_comm_mortality.JPG|400px]]<br /> <br /> :* POI/geofencing can also be configured to trigger communication (when entering POI)<br /> <br /> :* Finally a special SM communication session is trigger when regular data schedules fail cor certain number of days<br /> : [[File:config_comm_emergencySMS.JPG|400px]]<br /> <br /> <br /> : Taking into account above mentioned various communication sources the predictability of the next communication session is limited<br /> : The &quot;Next schedule&quot; prediction only factors schedules planned to UTC clock<br /> : [[File:config_comm_prediction.JPG|400px]]<br /> <br /> <br /> === Other user settings ===<br /> <br /> : Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control, etc)<br /> : [[File:config_other_settings.jpg|700px.JPG]]<br /> <br /> <br /> === Storage mode ===<br /> * allows bringing the device to low energy consumption mode<br /> * the device is powered off most of the time and only wakes up at 00:00 UTC in a specified day interval to send tag status (one dataset - GPS, battery level, etc.)<br /> * the communication interval can be set between 1 and 32 days<br /> * using storage mode is useful for long-distance transport and for storing undeployed devices longer time (e.g. when solar charging or GPS signal is unavailable longterm)<br /> [[File:config_poweroff.JPG|500px]]<br /> <br /> <br /> == Advanced Configuration Management using Presets ==<br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''<br /> &lt;br&gt;<br /> : This functionality allows saving the current device configuration (combination of parameters) into the &quot;Configuration Preset&quot; object<br /> : * only the &quot;user&quot; values generally applicable are saved (&quot;admin&quot; values unique to a particular device, such as mobile phone number or individual calibration values, are not included)<br /> : * a complete or just a subset of &quot;user&quot; configuration can be saved as a preset. Eg. you can save only communication settings in the first preset, data collection settings in another, and geofence settings in the third separate preset. <br /> : * Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.<br /> <br /> === Preset creation ===<br /> <br /> :* use the „Save as preset“ button in the config screen<br /> :* name the preset<br /> :* review and adjust the contents<br /> :* save when all done&lt;br&gt;[[File:Presets_Save_as_Preset.jpg|700px]]<br /> <br /> === Loading existing preset ===<br /> <br /> :* use the „Load preset“ button<br /> :* look up the stored preset<br /> :** either using &quot;Find preset&quot;<br /> :** or choosing from &quot;My presets&quot; <br /> :* alternatively, you can pick another device using &quot;Find device&quot; and use its current configuration the same way as for stored presets<br /> :* pick the preset or device and review the displayed configuration contents<br /> :* load values back to the device config screen<br /> :* review if preset values loaded correctly (marked blue in the config screen)<br /> :* submit modified configuration &amp; activate geofences created&lt;br&gt;&lt;br&gt;[[File:Presets_Apply_preset.jpg|600px]] same as zou do for manual config changes<br /> <br /> <br /> ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1279 2025-12-05T09:57:27Z

<p>Admin: </p> <hr /> <div>{{Release note|UI refactoring and modernization|improvement}} <br /> {{Release note body start}}<br /> * Various application features reviewed and consolidated (most changes in Groups/Projects and Load / Save Configuration Preset)<br /> * Related bug-fixing loop done. <br /> ''Please report any remaining imperfections spotted''<br /> {{Release note body end}}<br /> <br /> {{Release note|New &quot;Find device&quot; feature in Load preset screen|new}} <br /> {{Release note body start}} <br /> * a new &quot;Find device&quot; tool has been added in the Load Preset modal<br /> * as another alternative way of loading existing config values from other devices<br /> * [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''You can check the updated section of the user guide for more details'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> ** Animal created by info added for existing animals<br /> ** Create tracking here fixed for some instances <br /> ** Last record geolocation updating when modifying tracking end fixed<br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> ** Fix tracking name display in notes<br /> ** File attaching into note draft note fixed<br /> ** Time format fixed when creating a new bulk note<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> ** Country code display in tracking grid adjusted<br /> ** Redundant grid refreshing when changing unrelated column mappings removed<br /> ** Device and tracking list XLSX export fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Copy filter functionality fixed<br /> * Waypoints all option fixed<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> ** Fix API scroll requests not working with both body and request parameters<br /> ** Fix API column filtering<br /> {{Release note body end}}<br /> <br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Release_notes/2025-11-30&diff=1278 2025-12-05T09:26:15Z

<p>Admin: Created page with &quot;{{Release note|Server programming environment update|improvement}} {{Release note body start}} * A major server franwork update applied * Related bugfixing in progress {{Rele...&quot;</p> <hr /> <div>{{Release note|Server programming environment update|improvement}} <br /> {{Release note body start}}<br /> * A major server franwork update applied<br /> * Related bugfixing in progress<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2025-11-30}}<br /> [[Category:2025 Release notes]]</div>

Admin index.php?title=Category:2025_Release_notes&diff=1277 2025-12-05T09:26:03Z

<p>Admin: Created page with &quot;Category:Release notes&quot;</p> <hr /> <div>[[Category:Release notes]]</div>

Admin index.php?title=Category:2024_Release_notes&diff=1276 2025-12-05T09:24:58Z

<p>Admin: Created page with &quot;Category:Release notes&quot;</p> <hr /> <div>[[Category:Release notes]]</div>

Admin index.php?title=Release_notes/2024-07-31&diff=1275 2025-12-05T09:23:11Z

<p>Admin: </p> <hr /> <div>{{Release note|Server programming environment update|improvement}} <br /> {{Release note body start}}<br /> * A major server framework update applied<br /> * Related bug fixing in progress<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-07-31}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-07-31&diff=1274 2025-12-05T09:22:12Z

<p>Admin: </p> <hr /> <div>{{Release note|Server programming environment update|improvement}} <br /> {{Release note body start}}<br /> * A major server franwork update applied<br /> * Related bugfixing in progress<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-07-31}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-05-31&diff=1273 2025-12-05T09:21:33Z

<p>Admin: </p> <hr /> <div>{{Release note|New way of Mortality information handling|new}}<br /> {{Release note body start}}<br /> * Mortality information now entered similarly as Tracking End and Tracking start<br /> * The look and functionality of the create/edit/delete for the three events unified<br /> * Mixed app features using mortality information adjusted to work the new way <br /> {{Release note body end}}<br /> <br /> {{Release note|Annotations/Clusters shown to users|new}}<br /> {{Release note body start}}<br /> * Tracking profile timeline modified to show clusters of various types (mortality, night, etc).<br /> * New cluster detail form (the centroid calculated)<br /> * Create annotation/cluster from the interval introduced.<br /> * Mortality info entering coupled with Mortality cluster creation<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management<br /> ** Tracking/Animal visibility in projects improved<br /> ** Statistics updated after the new tracking created<br /> * Import functionality further adjusted <br /> ** Control of cancelling improved<br /> ** More validation checks added<br /> * Note/ToDos replies links added<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-05-31}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-04-22&diff=1272 2025-12-05T09:21:00Z

<p>Admin: </p> <hr /> <div>{{Release note|New IMPORT functionality (final version)|new}} <br /> {{Release note body start}} <br /> * Workflow reviewed and finalized<br /> * Return info and warning messages finalized<br /> * Cancel button behavior adjusted<br /> * Data validation logic extended (insert, update, skip options elaborated)<br /> * More error situations handled<br /> * Missing progress bars for remaining import stages added<br /> [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''Please check the updated section of the user guide'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> ** Animal created by info added for existing animals<br /> ** Create tracking here fixed for some instances <br /> ** Last record geolocation updating when modifying tracking end fixed<br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> ** Fix tracking name display in notes<br /> ** File attaching into note draft note fixed<br /> ** Time format fixed when creating a new bulk note<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> ** Country code display in tracking grid adjusted<br /> ** Redundant grid refreshing when changing unrelated column mappings removed<br /> ** Device and tracking list XLSX export fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Copy filter functionality fixed<br /> * Waypoints all option fixed<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> ** Fix API scroll requests not working with both body and request parameters<br /> ** Fix API column filtering<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-04-22}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-04-22&diff=1271 2025-12-05T09:20:13Z

<p>Admin: </p> <hr /> <div>{{Release note|New IMPORT functionality (final version)|new}} <br /> {{Release note body start}} <br /> * Workflow reviewed and finalized<br /> * Return info and warning messages finalized<br /> * Cancel button behavior adjusted<br /> * Data validation logic extended (insert, update, skip options elaborated)<br /> * More error situations handled<br /> * Missing progress bars for remaining import stages added<br /> [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''Please check the updated section of the user guide'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> ** Animal created by info added for existing animals<br /> ** Create tracking here fixed for some instances <br /> ** Last record geolocation updating when modifying tracking end fixed<br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> ** Fix tracking name display in notes<br /> ** File attaching into note draft note fixed<br /> ** Time format fixed when creating a new bulk note<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> ** Country code display in tracking grid adjusted<br /> ** Redundant grid refreshing when changing unrelated column mappings removed<br /> ** Device and tracking list XLSX export fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Copy filter functionality fixed<br /> * Waypoints all option fixed<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> ** Fix API scroll requests not working with both body and request parameters<br /> ** Fix API column filtering<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-04-22}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Release_notes/2024-03-31&diff=1270 2025-12-05T09:19:42Z

<p>Admin: </p> <hr /> <div>{{Release note|Import flow further extended|improvement}} <br /> {{Release note body start}} <br /> * more finetuning of the graphic wizard<br /> * improved parallel run of multiple files<br /> * more file variants tested<br /> {{Release note body end}}<br /> <br /> {{Release note|Device discard flow and SIM management changed|new}} <br /> {{Release note body start}}<br /> * Device discard state made more visible in profiles<br /> * Change device saving checks, modify required fields in device form<br /> * Refresh device detail header upon saving modifications<br /> * Fix the zooming issue in the Comm history and SIM profile<br /> * Fix SIM detail zooming incorrectly<br /> * Add refreshing of SIM state in profile<br /> * [https://support.anitracking.com/index.php?title=Main_Page#Device_Status_and_Discard_Flow ''See the updated documentation section'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Notes can be dragged as a reply<br /> ** Add drag-and-drop notes to replies<br /> ** Dragging notes with replies not disabled<br /> ** Additional consistency checks for user rights in note dragging added<br /> * Tracking / Animal visibility and handling improvements<br /> ** Created by Person for existing Animals shown<br /> ** Disable create tracking functionality where 'here' can be applied<br /> ** Change wording in select animal<br /> ** Context menu for tracking creation/modification adjusted<br /> {{Release note body end}}<br /> <br /> {{Release note|System optimization and performance|improvement}}<br /> {{Release note body start}}<br /> * 3rd party API reactivated (Google altitude geolocation)<br /> * Prevent duplicate preference calls in profiles<br /> * system monitoring improved (row counts per queue added)<br /> * other data processing optimizations<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Public (iframes) maps - animation and logos fixed <br /> * Person names in search fixed<br /> * Fixed track visibility - first position missing<br /> {{Release note body end}}<br /> <br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-03-31}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-03-17&diff=1269 2025-12-05T09:19:25Z

<p>Admin: </p> <hr /> <div>{{Release note|New IMPORT FLOW (new user interface and background processes)|new}} <br /> {{Release note body start}} <br /> * new workflow implemented as a graphic wizard<br /> ** parallel run of multiple files in a single run (each file flow processed independently)<br /> * file acquiring phase embedded in the flow<br /> * file structure checking phase reimplemented and extended (prevents further processing for wrong type and error structured files)<br /> * automated import type matching implemented<br /> ** The file column list must match one of the existing import format<br /> ** More accepted file variants added (Ornitela and Ecotone CSV file versions)<br /> * data validation phase reimplemented<br /> ** insert new data only or data merge (insert new + update existing) options<br /> * import into database reimplemented, the user stays notified on the status of progress till the end of the import run<br /> {{Release note body end}}<br /> <br /> {{Release note|Live updates concept implemented|new}}<br /> {{Release note body start}}<br /> * Configuration status is now automatically updated for Anitra tags <br /> * i.e. config icons refreshed across the app whenever the status changes (e.g. when the device applies config changes)<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * API extended to provide data with a customized column list<br /> ** Available data and metadata columns can be queried over API<br /> ** Data can be fetched using a customized column list similar to metadata <br /> * Tracking / Animal visibility and handling improvements<br /> ** Tracking end filtering condition added<br /> ** The existing animal list improved to provide more details<br /> ** Fix layout in the profile data grid, tracking list visibility<br /> ** Age vs tracking start conflicts visibility improved in profile, grid, map tooltip<br /> ** Movebank sourced objects (Tracking and Animal) are now fully controlled in profiles <br /> ** Mortality section visibility and behavior (collapsed for not dead animals) <br /> ** New Tracking controls in project tracking list (remove Tracking from project)<br /> ** Tracking End and Mortality geolocation related topics handled <br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * wrong track from the last point (in particular data situations)<br /> * fix iframe styling, animation controls<br /> * Fix quick filter breaking visually in Chrome<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-03-17}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-01-29&diff=1268 2025-12-05T09:17:22Z

<p>Admin: </p> <hr /> <div>{{Release note|New last data post-process mortality detector|new}} <br /> {{Release note body start}} <br /> * activated for Anitra trackings<br /> * last 3 hours and or minimum last 3 positions analyzed<br /> * pitch and roll oscillation evaluated, when both below 3 deg, evaluated as mortality<br /> * re-run mortality with modified tracking interval<br /> * add mortality tracking calculation to data received chain of events<br /> ''Note the algorithm is now in the verification phase'' <br /> {{Release note body end}}<br /> <br /> {{Release note|More mortality related improvements|improvement}} <br /> {{Release note body start}} <br /> * Mortality (any) filter modified<br /> ** result of new mortality detection added<br /> ** Invalid body orientation included<br /> * Mortality warnings in profiles <br /> ** onboard and post-process warnings reviewed and made consistent<br /> ** Invalid body orientation warning added<br /> * [https://support.anitracking.com/index.php?title=Main_Page#MORTALITY_WARNINGS ''Mortality detection and warnings user guide added'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Area hierarchy enriched|improvement}}<br /> {{Release note body start}}<br /> * Added admin L1 for SK and IT<br /> * Added admin L2 for FR, ES, CZ, and SK <br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Filter profile map to X days back as user preference <br /> ** Fast profile data loading for large profiles<br /> ** managed by a new user preference<br /> * More profile graph options (post-release adjustments and fixes)<br /> ** Fix column visibility modal comparison<br /> ** Fix an issue in clearing graph styles<br /> ** Fix column mapping empty headings<br /> * [https://support.anitracking.com/index.php?title=Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F ''Graphs user guide updated'']<br /> * Tracking end adjustments<br /> ** Fix tracking event saving<br /> ** Fix tracking event not opening in some cases<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2024-01-29}}<br /> [[Category:2024 Release notes]]</div>

Admin index.php?title=Release_notes/2024-07-31&diff=1267 2024-08-04T23:46:43Z

<p>Admin: Created page with &quot;{{Release note|Server programming environment update|improvement}} {{Release note body start}} * A major server franwork update applied * Related bugfixing in progress {{Rele...&quot;</p> <hr /> <div>{{Release note|Server programming environment update|improvement}} <br /> {{Release note body start}}<br /> * A major server franwork update applied<br /> * Related bugfixing in progress<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-07-31}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Release_notes/2024-05-31&diff=1266 2024-06-01T16:24:54Z

<p>Admin: </p> <hr /> <div>{{Release note|New way of Mortality information handling|new}}<br /> {{Release note body start}}<br /> * Mortality information now entered similarly as Tracking End and Tracking start<br /> * The look and functionality of the create/edit/delete for the three events unified<br /> * Mixed app features using mortality information adjusted to work the new way <br /> {{Release note body end}}<br /> <br /> {{Release note|Annotations/Clusters shown to users|new}}<br /> {{Release note body start}}<br /> * Tracking profile timeline modified to show clusters of various types (mortality, night, etc).<br /> * New cluster detail form (the centroid calculated)<br /> * Create annotation/cluster from the interval introduced.<br /> * Mortality info entering coupled with Mortality cluster creation<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management<br /> ** Tracking/Animal visibility in projects improved<br /> ** Statistics updated after the new tracking created<br /> * Import functionality further adjusted <br /> ** Control of cancelling improved<br /> ** More validation checks added<br /> * Note/ToDos replies links added<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-05-31}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Release_notes/2024-05-31&diff=1265 2024-06-01T16:14:05Z

<p>Admin: </p> <hr /> <div>{{Release note|New way of Mortality information handling|new}}<br /> {{Release note body start}}<br /> * Mortality information now entered similarly as Tracking End and Tracking start<br /> * The look and functionality of the create/edit/delete for the three events unified<br /> * Mixed app features using mortality information adjusted to work the new way <br /> {{Release note body end}}<br /> <br /> {{Release note|Annotations/Clusters shown to users|new}}<br /> {{Release note body start}}<br /> * Tracking profile timeline modified to show clusters of various types (mortality, night, etc).<br /> * New cluster detail form (the centroid calculated)<br /> * Create annotation/cluster from interval introduced.<br /> * Mortality info entering coupled with Mortality cluster creation<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management<br /> ** Tracking/Animal visibility in projects improved<br /> ** Statistics updated after the new tracking created<br /> * Import functionality further adjusted <br /> ** Control of cancelling improved<br /> ** More validation checks added<br /> * Note/ToDos replies links added<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-05-31}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Release_notes/2024-05-31&diff=1264 2024-06-01T14:03:40Z

<p>Admin: Created page with &quot;{{Release note|New way of Mortality information handling|new}} {{Release note body start}} * Mortality information now entered similarly as Tracking End and Tracking start * T...&quot;</p> <hr /> <div>{{Release note|New way of Mortality information handling|new}}<br /> {{Release note body start}}<br /> * Mortality information now entered similarly as Tracking End and Tracking start<br /> * The look and functionality of the create/edit/delete for the three events unified<br /> * Mixed app features using mortality information adjusted to work the new way <br /> {{Release note body end}}<br /> <br /> {{Release note|Annotations/Clusters shown to users|new}}<br /> {{Release note body start}}<br /> * Tracking profile timeline modified to show clusters of various types (mortality, night, etc).<br /> * New cluster detail form (the centroid calculated)<br /> * Create annotation/cluster from interval introduced.<br /> * Mortality info entering coupled with Mortality cluster creation<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal visibility in projects improved<br /> ** Statistics updated after the new tracking created<br /> * Import functionality further adjusted <br /> ** Control of cancelling improved<br /> ** More validation checks added<br /> * Note/ToDos replies links added<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-05-31}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Release_notes/2024-04-22&diff=1263 2024-06-01T13:17:14Z

<p>Admin: </p> <hr /> <div>{{Release note|New IMPORT functionality (final version)|new}} <br /> {{Release note body start}} <br /> * Workflow reviewed and finalized<br /> * Return info and warning messages finalized<br /> * Cancel button behavior adjusted<br /> * Data validation logic extended (insert, update, skip options elaborated)<br /> * More error situations handled<br /> * Missing progress bars for remaining import stages added<br /> [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''Please check the updated section of the user guide'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> ** Animal created by info added for existing animals<br /> ** Create tracking here fixed for some instances <br /> ** Last record geolocation updating when modifying tracking end fixed<br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> ** Fix tracking name display in notes<br /> ** File attaching into note draft note fixed<br /> ** Time format fixed when creating a new bulk note<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> ** Country code display in tracking grid adjusted<br /> ** Redundant grid refreshing when changing unrelated column mappings removed<br /> ** Device and tracking list XLSX export fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Copy filter functionality fixed<br /> * Waypoints all option fixed<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> ** Fix API scroll requests not working with both body and request parameters<br /> ** Fix API column filtering<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-04-22}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=Main_Page&diff=1262 2024-05-02T12:26:12Z

<p>Admin: /* MAIN CONCEPTS */</p> <hr /> <div>{{DISPLAYTITLE: Anitra Platform User Guide}}<br /> <br /> '''ABOUT'''<br /> &lt;br&gt;<br /> : Anitra platform is a flexible environment that allows storing, analyzing, and visualizing telemetry data. On top of actual telemetry data, a lot of additional metainformation and field information can be stored to document and visualize data in a very rich context. Anitra is primarily tailored to manage even very complex telemetry projects but similarly, a single user data can be comfortably maintained. <br /> <br /> : The tool allows hosting data generated by transmitters of any brand however some of the more advanced features are tailored to complement the unique onboard functionality of ANITRA GPS-GSM transmitters only. Part of the core functionality serves as a device backend for Anitra tags (a functionality for Data Owners/Admins). An elaborated sharing scheme allows granting a full range of access rights from &quot;admin&quot; to &quot;view only&quot;. Data in form of the maps can be made public in a very controlled and safe way. Most of the platform functionality is free of any charge and available to anyone having some defined access rights to particular data sets. Some data-intensive areas such as data/photo storage might be possibly restricted or charged per amount of data.<br /> <br /> <br /> = [[SIGNING_IN | SIGNING IN - How do I get into the app?]] =<br /> <br /> : Home screen of the ANITRA platform is at https://app.anitra.cz/<br /> <br /> : New users can register in the system either using &quot;Create new account link&quot; or using the &quot;SIGN IN WITH GOOGLE&quot; button ''(you will not need to type user name+pass anymore)''&lt;br&gt;[[File:sign-in_ user,pass_createNew.JPG|400px]]<br /> <br /> : Note new user can also be created by other existing users sending an invitation to the new person from access granting wizards (e.g. sharing tracking, adding admins, or assigning project access) - typing a new email address launches the invite process &lt;br&gt;[[File:user_invite_dialogue.jpg|400px]]<br /> <br /> : Once you have your account created and active you can log in either typing user name and password or using Google sign-in feature<br /> <br /> : You can review and modify your details and preferences in your user profile later.&lt;br&gt;[[File:user_profile_google_auth.JPG|900px]]<br /> <br /> : ''[[SIGNING_IN| More about User creation and user managment here]].''<br /> <br /> <br /> = MAIN CONCEPTS =<br /> &lt;br&gt;<br /> : Anitra data model is based on the following key concepts:<br /> <br /> : '''Device'''<br /> :: Device (or Tag) entity represents the physical telemetry hardware that collects particular telemetry data. Any tracking and sensor data are linked to one of the devices.<br /> <br /> :: Devices are created automatically in the system while importing a new telemetry dataset (via Import or Integration flow) or created by us in the case of Anitra devices (created as part of the device purchase process).<br /> <br /> :: Device Status attribute reflects the current usage of the devices (statuses are '''pool-new''', '''pool-used''', '''deployed-active''', '''deployed-delayed''', and '''deployed-missing'''). <br /> :: Besides, a &quot;Discard&quot; flag is available to mark the tags that are considered out of service. <br /> :: [[Main_Page#Device_Status_and_Discard_Flow |More on device statuses and discard flow here]].<br /> <br /> :: Attributes related to the hardware (brand, model, serial no., GSM no., etc.) or summary metrics can be seen and managed in the [[Main_Page#Device_profile|Device profile]].<br /> <br /> <br /> : '''Organisation, Customer, or Ownership'''<br /> :: Device &quot;Ownership&quot; defines which organization/customer holds ownership of the data.<br /> :: Purchased Anitra devices are transferred under the Customer account during the purchasing process.<br /> :: Non-Anitra devices are linked to particular Customers by running integration connectors or Importing data manually.<br /> <br /> :: Customer account also holds the credit balance (data fee prepay)<br /> <br /> <br /> : '''Animal'''<br /> :: Animal (or Individual) entity represents a particular animal/individual <br /> <br /> :: The main attributes for an Animal are its Species, Sex, and Dates when Born and Died (~ which also defines the current age e.g.).<br /> <br /> :: Additional complex meta-information can be linked-to Animal such as origin info, relationships to other animals, ringing, tagging or trapping details, and mortality attributes<br /> <br /> :: Photos (or documents) can be attached either directly to the Animal entity or indirectly to some related entities or Events such as Tagging or Mortality.<br /> <br /> <br /> : '''Tracking'''<br /> :: Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on [[TRACKING_ANIMAL|creation and modification of the tracking range]].<br /> <br /> :: The date(time) interval defines when the device was physically attached to the Animal<br /> <br /> :: ''Note when looking at the timeline of a particular Animal, multiple telemetry devices might have been used to track it subsequently (e.g. first tag failed and removed or was shed by the animal). Similarly, when analyzing Device usage history a single device might have been possibly reused several times for Tracking various animals (e.g. one animal died, the tag was recovered and reused elsewhere).''<br /> <br /> :: Besides the time aspect, some additional details such as place of tagging, place of release, tagging persons, various notes, photos, etc can be attached to Tracking Start/End. <br /> <br /> :: Tracking inherits permissions from its parent Device entity so users with device owner/admin access can create and modify the deployments as well.<br /> <br /> <br /> : '''Group''', Project, Study<br /> : '''Person''', User, Role<br /> :: Data owners can make their data available to other users or even make their data public in a simplified and secured way using an elaborated sharing scheme. Each user can act in both modes (i.e. admin for owned or administered devices and viewer for data shared with him by others). Most of the platform functionality is free of charge and available to anyone. Only large data volumes might be possibly restricted or charged. <br /> <br /> <br /> : '''Place''', Point of Interest (POI)<br /> : '''Event''', Observation<br /> <br /> <br /> : '''Device Data''', Records, Positions, Outliers<br /> :: Measurement data collected by telemetry devices. <br /> :: A combination of the device ID and UTC timestamp (date time in milliseconds) uniquely identifies each record.<br /> :: Records are linked to devices but can also be fetched for child Trackings, or Animals.<br /> <br /> :: '''Record''': a dataset related to particular UTC timestamp carrying measurements performed by particular device sensors (such as GNSS module, IMU, barometer)<br /> :: '''Position''': a record with a successful GPS fix (obtained Latitude and Longitude). Positions can be shown on maps.<br /> :: '''Outlier''': a record without GPS fix (no valid Latitude/Longitude) due to unsuccessful, skipped, or wrong GPS fixing. Note Outliers are not shown in maps but can still be displayed in table, timeline, and graph view.<br /> <br /> :: You can visualize, analyse, or download data using the Anitra platform functionality.<br /> ::: Within the platform you can see the data in [[Main_Page#MAIN_TRACKING_MAP:_Where_do_I_see_more_animals_in_one_map.3F|the main overview tracking map]] or in [[Main_Page#Device_profile|the (device or tracking) profile]] data tables, maps, timelines, and graphs<br /> ::: To analyze data outside of Anitra you can use the [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Export]] functionality or [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]].<br /> <br /> :: Note the list of columns/metrics covered by the Anitra data model can be understood from various places:<br /> ::* [[DATA_COLUMNS| a table of the most important metrics]] with explanations and comments - primarily to explain those used by Anitra tags<br /> ::* a detailed [https://anitracking.com/api/ Anitra API specification] provides a list of all the columns available over the API with a brief description<br /> ::* [[Main_Page#COLUMN_EDITOR:_How_can_I_adjust_columns_I_see.3F|column editor]] functionality lists the available columns per platform functionality.<br /> ::* the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality reference guide provides the samples/examples of files, columns, or formats to be used while importing data.<br /> ::* for additional explanations about some columns you can also refer to [https://www.movebank.org/cms/movebank-content/movebank-attribute-dictionary| Movebank attribute dictionary]. As the data from Movebank can be easily integrated in Anitra the data model and column names are ovelapping much.<br /> <br /> : '''Data Cluster''', Annotation<br /> :: An object created (automatically or manually) on top of the telemetry data that annotates a series of Records into semantic groups (such as Mortality or Night clusters).<br /> :: These clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.<br /> <br /> = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =<br /> Most entities in Anitra carry a certain list of attributes and offer a range of functions and operations related to it. The place that accommodates all this is a detail or profile page of it. <br /> <br /> Depending on the importance and complexity of a particular entity, the detail page might be rather simple (e.g. Person/User profile) or more structured and information-rich (e.g. Tracking/Animal profile). Most important entity pages are described here:<br /> <br /> =={{Fa|fa-tablet}} Device profile ==<br /> <br /> : '''Device profile''' tab (tab control marked green): <br /> :* holds all the information about the device (identification, status, type, brand, model, and user description<br /> :* allows administration of the device (i.e. managing admin list, activating Movebank Datafeed, exporting device data into the file, configuring/programming tag (cogwheel icon))<br /> :* shows device activity (i.e. bits needed for monitoring: Statistics, System of warnings (mortality, missing data), the last position in the overview map, first/last geolocation, communication log (wifi icon))<br /> :* lists Trackings/Animals created on top of device data (bottom right) - more rows in situation when single tag was redeployed multiple times &lt;br&gt;[[File:device_profile_functionality_marked.jpg|900px]]<br /> <br /> : '''Data''' tab (marked green):<br /> :* data collected by the tag visualized in the table, on the map, in the timeline, and the graph<br /> :* [[MORE_GUIDES#Tracking_range_management|functionality for creation of Trackings (aka Deployments) and modification of the DateTime ranges]].&lt;br&gt;[[File:01_create_new_tracking_here - kontext.jpg|900px]]<br /> <br /> : '''Graph''' tabs (marked green):<br /> :* data collected by the tag can be analysed in the graph<br /> :* wide range and flexible selection of columns for display<br /> :* [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|More about graphs here]]&lt;br&gt;[[File:device_profile_graph_marked.jpg|900px]]<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal profile ==<br /> <br /> * Details of tracked object (= tracking of the individual animal)<br /> ** Identification (code, name, ringing, tagging, etc.)<br /> ** Info related to particular Individual (species, sex, age, origin)<br /> ** Info related to Start of tracking (including photo and file documentation)<br /> ** Info related to End of tracking (~ mortality/device failure)<br /> * System of warnings<br /> ** Mortality indication: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt;/black warning in &quot;Last known Position&quot; row (&lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; = for deployed and currently tracking devices / black = tracking finished)<br /> ** Missing data last X days: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; warning in &quot;Last Device Position&quot; row (warning active just for deployed and currently tracking devices)<br /> :[[File:TOP00.JPG|738x138]]<br /> <br /> * Tracked animal data visualized on the map and on the timeline &lt;br&gt;[[File:TOP01.JPG|900px]]<br /> <br /> * &quot;Share&quot; button allows sharing Tracking to other Anitra users<br /> * Possibility to attach photos /documents related to<br /> ** Tracking start<br /> ** Mortality<br /> * Same photo can be shared by various Trackings &lt;br&gt;[[File:TOP02.JPG|900px]]<br /> <br /> =={{Fa|fa-user}} Organisation/Customer profile==<br /> <br /> A section visible in the side menu (only) for users with Admin/Owner relations to Organisations listed in the system. <br /> * users not having any role in any organization do not see this menu item at all<br /> * in case the user is active in more organizations the list of these is displayed first&lt;br&gt;[[File:customer_list.JPG|900px]]<br /> <br /> Organization details such as contacts and access roles can be edited on the organization profile.<br /> * main customer admin (owner) is assigned<br /> * owner can make other people admins granting them &quot;customer admin&quot; role.<br /> * customer owner(admins) have full access to devices belonging to a particular customer/organization account (can export data, manage trackings and animals, etc.)<br /> <br /> <br /> [[DATA_FLOWS|Various inbound and outbound data flows]] from manual data export to fully automated can be managed for organization account<br /> * (IN) Inbound data flows (connectors for Movebank, Ornitela, and Ecotone available)<br /> * (IN) Manual data import (see the Import functionality)<br /> * (OUT) API data access<br /> * (OUT) Manual data export<br /> * (OUT) Anitra to Movebank datafeed<br /> <br /> Note, only the legal owners of original data are allowed to configure inbound data flows! <br /> * Any data uploaded manually or synchronized automatically to Anitra are linked to a particular legal entity (Organisation / Customer) represented by its &quot;owner&quot; i.e. person in charge.<br /> * The ownership of and the responsibility for all the data remain with this legal entity. This organization's owner and admins assigned by the owner retain full control over the data related to this entity.<br /> * Anitra works as private and secure storage and a visualization tool of these data only.<br /> <br /> Data Management section of Customer profile is also a place to define and review customer [[PUBLISHED_MAPS|published maps]] i.e. a creation wizard for maps construction.<br /> <br /> ''Note the term &quot;customer&quot; refers to any &quot;organization&quot; having some kind of (active or past) commercial agreement with Anitra company''<br /> <br /> '''Customer balance''' - i.e. usage/charging summary vs. payment history is available in the Customer profile&lt;br&gt;[[File:spending_payments_tab.jpg|900px]]<br /> <br /> : A list of the devices owned by the customer is updated and visible right before or soon after shipping devices<br /> : Fix data fee calculation is also available instantly<br /> : Overage data charges are updated according to reality after the month is over and the detailed billing summary is available from the mobile network<br /> : Payments (from invoices paid) are visible after the data fee payment is received by us<br /> <br /> = LISTS, GRIDS=<br /> <br /> =={{Fa|fa-tablet}} Device list==<br /> : List of owned or administered devices (= hardware) - accessible only to owners/admins (users with shared data do not have the rights to see this area)<br /> : Click through to device details (profile), sort by the column, browsed by pages, first column freezing, quick system, and user filters<br /> : [[Main_Page#FILTERS_.26_SEARCHES:_How_do_I_find_what_I_am_looking_for_.3F|Search and Filter functionality]]: allows filtering your devices by criteria<br /> : Manageable through Filter manager next to the Search box, marked with icon [[File:C2.JPG|30px]] <br /> :* Predefined quick filters, which cannot be modified (Missing data in the last 7+ days, Anitra devices only, Powered off devices, Wrong tracking configuration, Deployed devices, Mortality indication)<br /> :* You can turn on multiple Quick filters at once in the Quick filter panel<br /> : Context menu - as anywhere in Anitra the right-click mouse context menu offers the most relevant actions for the current context, functionality, or the whole page or a user<br /> : A wide range of columns available. Column selection and more column-related actions using Column manager from the context menu or directly e.g. by drag-drop columns:<br /> :* Column selection, adding, removing columns (a default list can be restored using &quot;reset visibility&quot;)<br /> :* Column renames (default names can be restored using &quot;reset display names&quot;)<br /> :* Column order (a default order can be restored using &quot;reset order&quot;)<br /> : Multi-select for bulk operations (open all in tabs, graph, apply config preset, etc)<br /> : System of warning messages such as Mortality indication: &quot;Device Status&quot; colored in red and followed by {{red|red skull}} symbol or Missing data last X days: &quot;Last Device Position&quot; followed by red question mark {{red|&quot;?&quot;}}.<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal list ==<br /> <br /> * List of owned Trackings (tab &quot;my trackings&quot;)<br /> * List of Trackings shared with me (tab &quot;shared with me&quot;)<br /> * Overview of all Trackings including first and last data<br /> ** Click through to Tracking detail/profile<br /> ** System of warnings<br /> ** Mortality indication: &quot;Tracking&quot; followed by &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; &lt;span style=&quot;color:red&quot;&gt;skull&lt;/span&gt; symbol<br /> ** Missing data last X days: &quot;Last Data &quot; followed by red question mark &lt;span style=&quot;color:red&quot;&gt;&quot;?&quot;&lt;/span&gt;. Mouse-over symbol tells the last data delay.<br /> <br /> = MAPS =<br /> <br /> : Common map properties and controls<br /> : 1) '''Map zoom''' <br /> :: ''Note besides the zoom buttons you can zoom the map''<br /> ::* ''using the mouse scroll wheel'' <br /> ::* ''or by double-clicking the left mouse button (to zoom in) and the right button (to zoom out)''<br /> <br /> : 2) '''Full-screen''' mode<br /> <br /> : 3) Shows the user/device's '''current position''' on the map as a blue dot <br /> <br /> : 4) '''GPS search''' tool - various GPS formats accepted (e.g. decimal degrees such as &quot;52.7761 27.811889&quot;)<br /> <br /> : 5) '''Background maps''' <br /> :* a wide range of background maps of various types<br /> :* transparent overlays (country and admin borders)<br /> <br /> : 6) '''Transparent map overlays''' <br /> :* country borders <br /> :* admin leve1 1 borders<br /> <br /> : 7) '''Map options''' <br /> :* '''Tracks''' - note the option &quot;'''Clustered'''&quot; simplifies the track by removing movements within clusters<br /> :* '''Waypoints''' - note the option &quot;'''All'''&quot; suppresses the default performance optimisation behavior (= option &quot;'''Filtered'''&quot;) - i.e. enforces showing of all the waypoints<br /> :* '''Annotations''' (aka '''Clusters''') - currently these two Annotatin/Cluster types availabe to be used<br /> :** '''Last positions''' - show/hide the last position of the tracking<br /> :** '''Sleep clusters''' - show/hide the sleep clusters (data from periods defined by solar night/day i.e. by sun angle)&lt;br&gt;[[File:map04_mapFunctionality.JPG|900px]]<br /> <br /> : 8) '''Copy coordinates to clipboard''' <br /> :: using left click context menu<br /> <br /> : 9) '''Measure distance''' <br /> :: using left click context menu&lt;br&gt;[[File:map04_mapFunctionality_2.JPG|600px]]<br /> <br /> <br /> =={{Fa|fa-map-o}} MAIN TRACKING MAP: Where do I see more animals in one map? ==<br /> <br /> : A tool to analyze multiple Trackings / Individuals in a single map.<br /> : The functionality displays all the Tracked Individuals available to a user (both owned/administered and shared only) <br /> : The start view shows an overview of the last positions - the color of the point classifies the last positions by the last update. &lt;br&gt;[[File:map01_lastdatacolors.JPG|900px]]<br /> <br /> : '''Filtering functionality below the map''' limits the data in the map (and in the right Tracking list panel]<br /> :: The three quick filter conditions (&quot;Search&quot;, &quot;Tracking filters&quot;, &quot;Species&quot;) directly filter matching/not matching Trackings/Animals<br /> ::* &quot;Search&quot;: a full-text search across Device/Tracking/Animal codes/names/aliases<br /> ::* &quot;Tracking filters&quot;: existing Tracking filters created by the user can be reused here in the map. This allows applying very complex filter conditions in the map<br /> ::* &quot;Species&quot;: an obvious and simple quick filter conditions<br /> :: Note that the &quot;Days filter&quot; works differently - it uses a time filter over telemetry data first and based on that it leaves or removes Trackings/Animals from the page<br /> ::* it excludes all the trackings with data outside of the time interval<br /> ::* for overlapping Trackings/Animals it limits data/tracks in the map according to the interval defined - i.e. only relevant parts of the tracks are loaded&lt;br&gt;[[File:map02_mapfilterfilled.JPG|900px]]<br /> :: Also note the map filter is stored in the URL (browser address bar). You can open another browser tab with a map page and configure a different filter (eg. another species). Both tabs then work independently.<br /> <br /> : '''Choosing Trackings / Animals to be loaded''' in the map.<br /> :* using tooltips of single last points <br /> :* or for multiple items using the rectangle tool selection in the map (using CTRL + click/drag with left mouse button)<br /> :* selecting/unselcting particular items in the right Tracking pannel (single Trackings or all grouped by species)&lt;br&gt;[[File:map03_TOselection.JPG|900px]]<br /> <br /> : '''Waypoints and Last positions (tooltips)'''<br /> :* More tooltips can be displayed simultaneously<br /> :* Click through the link to a particular Tracked Object profile&lt;br&gt;[[File:map05_TOdetails.JPG|900px]]<br /> :* Warnings and statuses are shown in tooltips e.g. mortality being indicated by black/red symbols &lt;br&gt;[[File:map06_mortalityInMap.JPG|900px]]<br /> <br /> == [[PUBLISHED_MAPS|PUBLISHED MAPS: How do I show an overview of our study results to the public?]]==<br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> : A tool tailored to configure simplified and secured live telemetry maps from your full data sets.<br /> <br /> : Configured maps are available in form of a link or in form of short HTML code which can be simply added to your web presentation or published on Facebook.<br /> <br /> : Map output can be created:<br /> :* on top of single organization data <br /> :* on top of &quot;project&quot; (i.e. accross more complex data ownership structure)<br /> <br /> : Map editor with a live preview is used to configure the map&lt;br&gt;[[File:publish_map_configuration_groups.JPG|900px]]<br /> <br /> : Two map modes can be configured:<br /> :* map showing the simplified '''Tracks''' <br /> :* map showing the '''Last positions''' only<br /> <br /> : For the mode of &quot;Tracks&quot; '''Animation''' can be anabled<br /> <br /> : The map configuration includes:<br /> :* animal selection<br /> :* language localisations (alternative language variants)<br /> :* map mode (tracks vs. last position), grouping options, ordering, data filtering (e.g. track simplified to one position a day)<br /> :* security features (security delay, zoom restriction, position &quot;rounding&quot;)<br /> :* presentation and visualization presets (a default map selection, icon/track styles, choice of icons, logos with links, foto gallery, animation enabling)<br /> <br /> : Samples showing some of the map features<br /> :* map with tracks and gallery and animation anabled:https://app.anitra.cz/share/map/5d2e379ed6f9c &lt;br&gt;[[File:publish_map_animationEnabled.jpg|900px]]<br /> :* map of last positions with categories: https://app.anitra.cz/share/map/5f1a97bb13ba5<br /> <br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> = GRAPHS: How to visualize important data relations in graphs? =<br /> <br /> : Graph functionality available<br /> :* as a tab in Device and Tracking profiles (see #0)<br /> :* for a group of Devices (only admin functionality now).<br /> <br /> : Time is indicated by the horizontal axis (see #1)<br /> : By default period of the last 7 data days is loaded.<br /> : The interval shown can be managed either by the interval slider (see #2) or using the date input below the chart area (see #3).&lt;br&gt;[[File:graph_time.jpg|600px]]<br /> <br /> : You can hover over the chart to preview the actual values (see #4).<br /> : The values of metrics are plotted at the vertical axis of the graph (see #5).<br /> : The scale for a particular metric is shown on the left and right from the graph area (see #6).<br /> : To quickly show/hide a particular metric click the label color above the graph (only used till the next page reload)(see #7).&lt;br&gt;[[File:graph_orientation.jpg|600px]]<br /> <br /> : You can customize your metric list (visibility) and order using the &quot;Choose metrics&quot; button below the chart (see #8).<br /> : Visibility (see #9) and order (see #10) is controlled by drag'n'drop action.&lt;br&gt;[[File:graph_choseMetrics.jpg|600px]]<br /> <br /> : Visibility and order can also be managed in &quot;Edit graph columns&quot; from the context menu (see #11). <br /> : Additionally, this functionality offers even more properties to be controlled such as custom rename (see #12) or colors, graph type, and default value range (see #13). <br /> : It also allows resetting the changes to system defaults (reset options in the top right corner)(see #14)&lt;br&gt;[[File:graph_editColumns.jpg|600px]]<br /> <br /> ={{Fa|fa-photo}}PHOTO GALLERY: Where do I browse all the photos? =<br /> <br /> * Displays a complete gallery of pictures from all the Trackings (own and shared)<br /> * Filtering by main attributes &lt;br&gt;[[File:TO.JPG|900px]]<br /> <br /> = {{Fa|fa-cog}} MANAGING and CONFIGURING of Anitra Tags =<br /> <br /> == Device Status and Discard Flow ==<br /> <br /> : '''Device Status''' attribute is automatically assigned based on device usage history (including its past and current deployments)<br /> :: ''E.g. the tags are automatically moved from Pool to Deployed statuses by creating Tracking (+Animal) object. [[TRACKING_ANIMAL| Check the detailed guide here.]]''<br /> <br /> :: ''pool-new'' : devices never deployed previously<br /> :: ''pool-used'': devices returned to the device pool after deployment<br /> :: ''deployed-active'': deployed on animals, known to have delivered fresh data within the last 3 days<br /> :: ''deployed-delayed'': deployed on animals, known to have delivered fresh data within the last 4-7 days<br /> :: ''deployed-missing'': last data older than 7 days<br /> <br /> :: ''Note Devices status applies to all the devices types including data imported from Movebank of from Import flow.''<br /> <br /> : '''Device/SIM Discard Flow''' (for Anitra devices) <br /> :: Device/SIM closing(discard/termination) workflow is available for Anitra device owners so the SIM can be closed and the device removed from (data fees) billing<br /> :: Users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.<br /> :: Marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider <br /> :: SIM is ultimately terminated by the end of the month following after marking the device to be discarded ''(e.g for a device marked to be discarded on the 13th of February the SIM will be active (and data fees charged till the end of the March))''<br /> :: Note you can still stop the discard process till the SIM is irreversibly terminated by the network operator by contacting us directly till the end of the following month (i.e. for the example above we can manually withdraw the SIM closing request till the 31st of March)<br /> :: The check for marking devices to be terminated is available at the bottom part of the device profile.<br /> <br /> : Device Discard/Archive flow for non-Anitra devices<br /> :: For non-Anitra devices (= devices originating from import or integration - i.e. Movebank, Ornitela, Ecotone, Manual Import) there is also a Discard/Archive mark present in the Device profile <br /> :: For those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)<br /> :: A recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel <br /> :: Note in this case the flag is fully reversible (the user can change it there and back without any restriction)<br /> <br /> : '''Device Status Extended/Long''' <br /> :: Extended/long devices status is summarizing all the status information related.<br /> :: It is a combined field of Device status, history summary and Discard status.<br /> :: It is displayed in the Device profile, Device list, and Customer balance overview<br /> <br /> == Configuration /programming of devices == <br /> <br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> &lt;br&gt;<br /> : Users with admin rights can access the configuration from the lists and profiles using cogwheel icons. Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> &lt;br&gt;<br /> : Configuration contains three main areas<br /> :* Data collection settings<br /> :** GPS/sensor sampling time schedules<br /> :** Data collection triggered by events<br /> :** Configuration of bursting behavior<br /> :** Mortality detection adjustment<br /> :** Geofencing<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> <br /> = OTHER PRODUCTIVITY TOOLS =<br /> == FILTERS &amp; SEARCHES: How do I find what I am looking for ? ==<br /> <br /> Various features helping user find and filter down what is needed are available in Anitra:<br /> <br /> # '''Global full text search'''&lt;br&gt;- full text seach accross all the objects of various types which user has access rights to.&lt;br&gt;- a list of relevant item s sorted by relevancy is returned&lt;br&gt;[[File:global_full_text_search.JPG|500px]]<br /> # '''Grid search'''&lt;br&gt;- seaches in important fields in displayed grid only&lt;br&gt;[[File:grid_search.JPG|500px]] <br /> # '''System and Custom &quot;Quick&quot; filters'''&lt;br&gt;- allows quickly filter data using predefined &quot;system&quot; or &quot;user defined&quot; filters&lt;br&gt;- filters are available as icons on top of the device or tracking grid header line&lt;br&gt;- custom filters can be created in &quot;Filter manager&quot;&lt;br&gt;[[File:quick_filters.JPG|900px]] <br /> # '''Published map filters'''<br /> <br /> * Filter manager <br /> ** Customized quick filters that filter devices according to specified criteria (e.g. Device list, Name fields, Device notes..), you can set multiple criteria at once &lt;br&gt;:[[File:B.JPG|900px]] <br /> ** You can save your customized filter with the green &quot;check&quot; icon &lt;br&gt;:[[File:Ml.JPG|900px]] <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:Mil.JPG|900px]] <br /> <br /> * Filter functionality: allows filtering your trackings by criteria <br /> ** Predefined quick filters, which cannot be modified (Mortality Warning, Last data warning only, Anitra devices only)<br /> ** Customized quick filters, which filter Trackings by set criteria (e.g. Tracked Objects, Name fields, Note fields..), you can set multiple criteria at once <br /> ** You can save your customized filter with the green &quot;check&quot; icon <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:ksdjf.JPG|900px]] <br /> ** You can turn on multiple Quick filters at once in the Quick filter panel<br /> <br /> == NOTES: Where to note down info about particular things? ==<br /> : A handy feature helping users to get organized and stay organized with their data.&lt;br&gt;:[[File:note_thread_narrow.JPG|600px]]<br /> <br /> : Available for multiple entities (Devices, Trackings, Animals, and Customers/Organizations)<br /> <br /> : Note threads can be accessed <br /> :* from entity profiles - in the green shown opening of the Tracking note, the blue mark on the right shows the place to access the device note &lt;br&gt;[[File:note_from_profile.JPG|900px]]<br /> :* entity lists or using the context menu - either click on the note icon in the Notes column or use the context menu over the desired row&lt;br&gt;[[File:note_from_listContext.JPG|900px]]<br /> :* from user Task List &lt;br&gt;[[File:task_userTaskList.jpg|700px]]<br /> : Here a new note can be created, existing notes can be edited, or a reply to previous notes can be posted.<br /> : The thread window is flowing over the entity. It can be open parallel to whatever you do in your profile. You can switch tabs, type forms, take screenshots while browsing, or even create/edit notes. <br /> <br /> : Create the note simply by typing in the form<br /> : Edit existing notes by double-clicking them or using &quot;more&quot; or &quot;Edit&quot; icons in the right top corner. This switches note into &quot;'''edit'''&quot; mode&lt;br&gt;<br /> :[[File:note_editMode.JPG|500px]]<br /> : Save the new or edited note by clicking the &quot;Publish/Done&quot; button or simply hitting ENTER.<br /> : While creating or editing you can cancel by the &quot;Cancel&quot; button or using ESC on your keyboard<br /> : The note text does not allow formatting but you can structure the note to more rows. Use SHIFT+ENTER for the new line (as ENTER is reserved for the &quot;Save&quot; operation)<br /> : An existing note can be deleted using the &quot;more&quot; button &gt;&gt; &quot;Delete thread&quot;. Note while deleting the parent note all the replies will also be deleted.<br /> : &quot;Clone note&quot; function - particularly useful e.g. for fast duplicating of notes with complex definitions (i.e. notes linked to many items). <br /> :: ''While cloning notes attachments are removed (not cloned with the note).''&lt;br&gt;:[[File:note_deleteClone_thread.JPG|500px]]<br /> : Use &quot;Promote to parent note&quot; when you need to convert a note reply to a top-level parent note. <br /> :: ''While promoting reply to note it inherits the relations from its original parent note''<br /> : Use &quot;drag'n'drop: action to move one note into the reply area of the other note to move and transform the note into the reply. <br /> :: ''Converting note into reply is only possible for notes created by the user himself and only to notes that have no complex relationship''<br /> <br /> : By default the note thread is<br /> :* sorted starting with newest notes up. You can invert the sort order to have the oldest notes on top of the page. This setting is remembered in your user preferences.<br /> :* positioned on the top right side of the page. You can modify the position by dragging the floating window to any side, This setting is remembered in your user preferences.<br /> :* sized to one-third of the screen width. You can switch the window size between one-third and one-half by the &quot;shrinking/stretching&quot; button. This setting is also remembered in your user preferences.&lt;br&gt;:[[File:note_sortSizePosition.JPG|600px]]<br /> <br /> : Notes can be saved as<br /> :* shared - will be visible to all the users with access to the entity. a way to share knowledge, tasks, and the status of particular items<br /> :* private - will be visible only to the author of the note. a way to note down things or ToDos only for the author&lt;br&gt;:[[File:note_sharedPrivate.JPG|600px]]<br /> <br /> : The functionality contains a complex toolkit covering&lt;br&gt;:[[File:note_functionality_options.JPG|900px]]<br /> :* relations - a single note (thread) can be linked to multiple items of the same type (e.g. a single/shared note linked to 5 devices)<br /> :* attachments<br /> :** To each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)<br /> :** Picture attachments are then previewed in the thread, photos can be opened in full size and browsed as a gallery<br /> :* screenshots<br /> :** For adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body. <br /> :** This will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.<br /> :* links/URL<br /> :* tags - you can label your notes by using user &quot;tags&quot;, later you can search, filter, or group by these tags<br /> <br /> == TASKS (TODOS): Where to note down reminders and ToDos ? ==<br /> <br /> : Extension of the Notes functionality<br /> : By assigning a note to someone (to ''another user'', to ''user himself'' or to ''anyone'') the note is transformed into the Task (ToDo)<br /> <br /> : Use the button below the note editor or simply type @+name to assign the note as a task to someone&lt;br&gt;[[File:task_assignment.jpg|600px]]<br /> :* assigning a task to another person (''@other.person'') will list the task in the other person's Task list (as created by you).<br /> :* assigning a task to yourself (''@your.name'') will list the task in your Task list (as created by yourself).<br /> :* assigning a task to anyone (''@anyone'') will create a shared task displayed to all the people with access to the linked entity (e.g. particular device, tracking, or customer)<br /> <br /> : A simple workflow for tasks exists - the task can be in one of the three states<br /> :* new/open (= to be completed, highlighted by yellow background)<br /> :* completed /done (= marked as completed, highlighted by a green background)<br /> :* canceled / rejected (highlighted by a reddish background)&lt;br&gt;[[File:task_statusColors.jpg|600px]]<br /> <br /> : Users can move the tasks between the states using icons and controls in the right corner&lt;br&gt;:[[File:task_statusChange.jpg|600px]]<br /> <br /> : User Task board screen shows all the ToDos assigned to the user or defined by the user to others<br /> : Entity note thread can be accessed from the Task list by clicking the particular task<br /> : Task status can be changed from here or some comments added<br /> : You can also jump to the profile screen of the linked entity by clicking its name&lt;br&gt;:[[File:task_userTaskList.jpg|600px]]<br /> <br /> == COLUMN EDITOR: How can I adjust columns I see? ==<br /> <br /> : All the data visualization and download features are designed to allow users to pick and modify the columns to be used. <br /> : Use &quot;Edit columns&quot; options from the context menu of the functionality you wish to modify.<br /> : Beyond choosing the columns, the Edit functionality allows customizing names, order, color, graph type, and ranges, and reset changes to the default.<br /> : Edit columns option is available for <br /> :* metadata (device/tracking) lists<br /> :* metadata list exports<br /> :* profile data table columns<br /> :* profile graph columns<br /> :* data export columns<br /> : See the [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|Graphs section]] for some screens of column editing<br /> <br /> : Both metadata and data can be accessed via [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]] and same here the columns to be included can also be managed at the level of API query<br /> : [https://anitracking.com/api/| The detailed API specification] provides basic info about columns available.<br /> <br /> == USER PREFERENCES: How can I customize my user experience ? ==<br /> <br /> : Various features in the application are designed to remember user modifications<br /> : You can see and manage all your user preferences in the User preferences screen<br /> : The preferences listed are organized into categories <br /> : It is accessible from the user avatar in left menu or anywhere from right click context menu&lt;br&gt;[[File:user_preferences.jpg|600px]]<br /> <br /> = [[DATA_FLOWS | DATA FLOWS: How do I get the data IN/OUT?]] =<br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> : Anitra offers a range of data manipulation options on how to get data and metadata IN or OUT of the platform.<br /> <br /> : This functionality area involves features of data import, export, automated data connectors or API access<br /> <br /> : The options range from purely manual (e.g. [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|manual data exports]] or [[DATA_FLOWS#.28IN.29_Manual_data_import|data imports]]) to fully automated (e.g. [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|inbound data flows for Ornitela, Ecotone, or Movebank]]).<br /> <br /> : Some flows make sense for the particular user but most of the data management tools are meant to be configured at the level of customer/organization (hence available in customer profile)<br /> <br /> : '''Outbound data flows:'''<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Data Export]]&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_METADATA_Export|Metadata Export]]&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|API (both data and metadata)]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_to_Movebank_data_feed|Anitra to Movebank data feed]]<br /> <br /> : '''Inbound data flows:'''<br /> :* [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|Data integration of external data sources (i.e. connectors for Movebank, Ornitela, and Ecotone available)]]&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> :* [[DATA_FLOWS#.28IN.29_Manual_data_import|Data Import]]&lt;br&gt;[[File:manual_customer_import.JPG|900px]]<br /> <br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> = WARNINGS, NOTIFICATIONS=<br /> <br /> ==MORTALITY WARNINGS== <br /> [[File:DTO0000.JPG|36x37px]] Red skull<br /> * Indicates mortality detected by onboard mortality detector (Anitra tags only)<br /> * More about mortality detector in firmware configuration<br /> * The flag is stored at the level of database records (visible in data history anytime the device detected mortality)<br /> <br /> [[File:DTO000.JPG|44x38px]] Black skull<br /> : Notifies on possible mortality in the last records of trackings as estimated by server post-process analysis<br /> : Recalculated <br /> :* with new received data<br /> :* with modification of the tracking range (i.e. when closing active Tracking or when updating Tracking End Date)<br /> : The flag is recalculated and visible for the last data only (not visible in data history).<br /> : Algorithm factors in roll and pitch oscillations for the latest three records and/or the last 3 hours<br /> <br /> Red bird belly up<br /> : Unnatural body position in the very last record (roll and pitch)<br /> : whenever the absolute value of the angle for Roll or Pitch exceeds 90 degrees<br /> <br /> <br /> =={{Fa|fa-map-o}} RELEASE NOTES==<br /> <br /> : Latest release note overview is shown to the user any time a new release is deployed since the last user's Anitra access.<br /> : After being displayed the screen is no longer shown till another release<br /> : The release note screen aggregates data from the past 60 days are shown.<br /> : Release note screen can be manually invoked by pressing the Anitra icon (left top corner of the application)&lt;br&gt;[[File:ReleaseNotes_drill.jpg|900px]]<br /> <br /> =[[MORE_GUIDES| MORE GUIDES]]=<br /> <br /> : [[RK_WINTERCOUNT_TIPS| LIFE EUROKITE Red kite Wintering count (Anitra tips)]]<br /> <br /> : [[EUROKITE_PROJECT_DATASHARING| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]</div>

Admin index.php?title=Main_Page&diff=1261 2024-05-02T12:25:38Z

<p>Admin: /* MAIN CONCEPTS */</p> <hr /> <div>{{DISPLAYTITLE: Anitra Platform User Guide}}<br /> <br /> '''ABOUT'''<br /> &lt;br&gt;<br /> : Anitra platform is a flexible environment that allows storing, analyzing, and visualizing telemetry data. On top of actual telemetry data, a lot of additional metainformation and field information can be stored to document and visualize data in a very rich context. Anitra is primarily tailored to manage even very complex telemetry projects but similarly, a single user data can be comfortably maintained. <br /> <br /> : The tool allows hosting data generated by transmitters of any brand however some of the more advanced features are tailored to complement the unique onboard functionality of ANITRA GPS-GSM transmitters only. Part of the core functionality serves as a device backend for Anitra tags (a functionality for Data Owners/Admins). An elaborated sharing scheme allows granting a full range of access rights from &quot;admin&quot; to &quot;view only&quot;. Data in form of the maps can be made public in a very controlled and safe way. Most of the platform functionality is free of any charge and available to anyone having some defined access rights to particular data sets. Some data-intensive areas such as data/photo storage might be possibly restricted or charged per amount of data.<br /> <br /> <br /> = [[SIGNING_IN | SIGNING IN - How do I get into the app?]] =<br /> <br /> : Home screen of the ANITRA platform is at https://app.anitra.cz/<br /> <br /> : New users can register in the system either using &quot;Create new account link&quot; or using the &quot;SIGN IN WITH GOOGLE&quot; button ''(you will not need to type user name+pass anymore)''&lt;br&gt;[[File:sign-in_ user,pass_createNew.JPG|400px]]<br /> <br /> : Note new user can also be created by other existing users sending an invitation to the new person from access granting wizards (e.g. sharing tracking, adding admins, or assigning project access) - typing a new email address launches the invite process &lt;br&gt;[[File:user_invite_dialogue.jpg|400px]]<br /> <br /> : Once you have your account created and active you can log in either typing user name and password or using Google sign-in feature<br /> <br /> : You can review and modify your details and preferences in your user profile later.&lt;br&gt;[[File:user_profile_google_auth.JPG|900px]]<br /> <br /> : ''[[SIGNING_IN| More about User creation and user managment here]].''<br /> <br /> <br /> = MAIN CONCEPTS =<br /> &lt;br&gt;<br /> : Anitra data model is based on the following key concepts:<br /> <br /> : '''Device'''<br /> :: Device (or Tag) entity represents the physical telemetry hardware that collects particular telemetry data. Any tracking and sensor data are linked to one of the devices.<br /> <br /> :: Devices are created automatically in the system while importing a new telemetry dataset (via Import or Integration flow) or created by us in the case of Anitra devices (created as part of the device purchase process).<br /> <br /> :: Device Status attribute reflects the current usage of the devices (statuses are '''pool-new''', '''pool-used''', '''deployed-active''', '''deployed-delayed''', and '''deployed-missing'''). <br /> :: Besides, a &quot;Discard&quot; flag is available to mark the tags that are considered out of service. <br /> :: [[Main_Page#Device_Status_and_Discard_Flow |More on device statuses and discard flow here]].<br /> <br /> :: Attributes related to the hardware (brand, model, serial no., GSM no., etc.) or summary metrics can be seen and managed in the [[Main_Page#Device_profile|Device profile]].<br /> <br /> <br /> : '''Organisation, Customer, or Ownership'''<br /> :: Device &quot;Ownership&quot; defines which organization/customer holds ownership of the data.<br /> :: Purchased Anitra devices are transferred under the Customer account during the purchasing process.<br /> :: Non-Anitra devices are linked to particular Customers by running integration connectors or Importing data manually.<br /> <br /> :: Customer account also holds the credit balance (data fee prepay)<br /> <br /> <br /> : '''Animal'''<br /> :: Animal (or Individual) entity represents a particular animal/individual <br /> <br /> :: The main attributes for an Animal are its Species, Sex, and Dates when Born and Died (~ which also defines the current age e.g.).<br /> <br /> :: Additional complex meta-information can be linked-to Animal such as origin info, relationships to other animals, ringing, tagging or trapping details, and mortality attributes<br /> <br /> :: Photos (or documents) can be attached either directly to the Animal entity or indirectly to some related entities or Events such as Tagging or Mortality.<br /> <br /> <br /> : '''Tracking'''<br /> :: Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on [[TRACKING_ANIMAL|creation and modification of the tracking range]].<br /> <br /> :: The date(time) interval defines when the device was physically attached to the Animal<br /> <br /> :: ''Note when looking at the timeline of a particular Animal, multiple telemetry devices might have been used to track it subsequently (e.g. first tag failed and removed or was shed by the animal). Similarly, when analyzing Device usage history a single device might have been possibly reused several times for Tracking various animals (e.g. one animal died, the tag was recovered and reused elsewhere).''<br /> <br /> :: Besides the time aspect, some additional details such as place of tagging, place of release, tagging persons, various notes, photos, etc can be attached to Tracking Start/End. <br /> <br /> :: Tracking inherits permissions from its parent Device entity so users with device owner/admin access can create and modify the deployments as well.<br /> <br /> <br /> : '''Group''', Project, Study<br /> : '''Person''', User, Role<br /> :: Data owners can make their data available to other users or even make their data public in a simplified and secured way using an elaborated sharing scheme. Each user can act in both modes (i.e. admin for owned or administered devices and viewer for data shared with him by others). Most of the platform functionality is free of charge and available to anyone. Only large data volumes might be possibly restricted or charged. <br /> <br /> <br /> : '''Place''', Point of Interest (POI)<br /> : '''Event''', Observation<br /> <br /> <br /> : '''Device Data''', Records, Positions, Outliers<br /> :: Measurement data collected by telemetry devices. <br /> :: A combination of the device ID and UTC timestamp (date time in milliseconds) uniquely identifies each record.<br /> :: Records are linked to devices but can also be fetched for child Trackings, or Animals.<br /> <br /> :: '''Record''': a dataset related to particular UTC timestamp carrying measurements performed by particular device sensors (such as GNSS module, IMU, barometer)<br /> :: '''Position''': a record with a successful GPS fix (obtained Latitude and Longitude). Positions can be shown on maps.<br /> :: '''Outlier''': a record without GPS fix (no valid Latitude/Longitude) due to unsuccessful, skipped, or wrong GPS fixing. Note Outliers are not shown in maps but can still be displayed in table, timeline, and graph view.<br /> <br /> :: You can visualize, analyse, or download data using the Anitra platform functionality.<br /> ::: Within the platform you can see the data in [[Main_Page#MAIN_TRACKING_MAP:_Where_do_I_see_more_animals_in_one_map.3F|the main overview tracking map]] or in [[Main_Page#Device_profile|the (device or tracking) profile]] data tables, maps, timelines, and graphs<br /> ::: To analyze data outside of Anitra you can use the [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Export]] functionality or [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]].<br /> <br /> :: Note the list of columns/metrics covered by the Anitra data model can be understood from various places:<br /> ::* [[DATA_COLUMNS| a table of the most important metrics]] with explanations and comments - primarily to explain those used by Anitra tags<br /> ::* a detailed [https://anitracking.com/api/ Anitra API specification] provides a list of all the columns available over the API with a brief description<br /> ::* [[Main_Page#COLUMN_EDITOR:_How_can_I_adjust_columns_I_see.3F|column editor]] functionality lists the available columns per platform functionality.<br /> ::* the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality reference guide provides the samples/examples of files, columns, or formats to be used while importing data.<br /> ::* for additional explanations about some columns you can also refer to [https://www.movebank.org/cms/movebank-content/movebank-attribute-dictionary| Movebank attribute dictionary]. As the data from Movebank can be easily integrated in Anitra the data model and column names are ovelapping much.<br /> <br /> : '''Data Cluster''', Annotation<br /> :: an object created (automatically or manually) on top of the telemetry data that annotates a series of Records into semantic groups (such as Mortality or Night clusters)<br /> :: these clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.<br /> <br /> = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =<br /> Most entities in Anitra carry a certain list of attributes and offer a range of functions and operations related to it. The place that accommodates all this is a detail or profile page of it. <br /> <br /> Depending on the importance and complexity of a particular entity, the detail page might be rather simple (e.g. Person/User profile) or more structured and information-rich (e.g. Tracking/Animal profile). Most important entity pages are described here:<br /> <br /> =={{Fa|fa-tablet}} Device profile ==<br /> <br /> : '''Device profile''' tab (tab control marked green): <br /> :* holds all the information about the device (identification, status, type, brand, model, and user description<br /> :* allows administration of the device (i.e. managing admin list, activating Movebank Datafeed, exporting device data into the file, configuring/programming tag (cogwheel icon))<br /> :* shows device activity (i.e. bits needed for monitoring: Statistics, System of warnings (mortality, missing data), the last position in the overview map, first/last geolocation, communication log (wifi icon))<br /> :* lists Trackings/Animals created on top of device data (bottom right) - more rows in situation when single tag was redeployed multiple times &lt;br&gt;[[File:device_profile_functionality_marked.jpg|900px]]<br /> <br /> : '''Data''' tab (marked green):<br /> :* data collected by the tag visualized in the table, on the map, in the timeline, and the graph<br /> :* [[MORE_GUIDES#Tracking_range_management|functionality for creation of Trackings (aka Deployments) and modification of the DateTime ranges]].&lt;br&gt;[[File:01_create_new_tracking_here - kontext.jpg|900px]]<br /> <br /> : '''Graph''' tabs (marked green):<br /> :* data collected by the tag can be analysed in the graph<br /> :* wide range and flexible selection of columns for display<br /> :* [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|More about graphs here]]&lt;br&gt;[[File:device_profile_graph_marked.jpg|900px]]<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal profile ==<br /> <br /> * Details of tracked object (= tracking of the individual animal)<br /> ** Identification (code, name, ringing, tagging, etc.)<br /> ** Info related to particular Individual (species, sex, age, origin)<br /> ** Info related to Start of tracking (including photo and file documentation)<br /> ** Info related to End of tracking (~ mortality/device failure)<br /> * System of warnings<br /> ** Mortality indication: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt;/black warning in &quot;Last known Position&quot; row (&lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; = for deployed and currently tracking devices / black = tracking finished)<br /> ** Missing data last X days: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; warning in &quot;Last Device Position&quot; row (warning active just for deployed and currently tracking devices)<br /> :[[File:TOP00.JPG|738x138]]<br /> <br /> * Tracked animal data visualized on the map and on the timeline &lt;br&gt;[[File:TOP01.JPG|900px]]<br /> <br /> * &quot;Share&quot; button allows sharing Tracking to other Anitra users<br /> * Possibility to attach photos /documents related to<br /> ** Tracking start<br /> ** Mortality<br /> * Same photo can be shared by various Trackings &lt;br&gt;[[File:TOP02.JPG|900px]]<br /> <br /> =={{Fa|fa-user}} Organisation/Customer profile==<br /> <br /> A section visible in the side menu (only) for users with Admin/Owner relations to Organisations listed in the system. <br /> * users not having any role in any organization do not see this menu item at all<br /> * in case the user is active in more organizations the list of these is displayed first&lt;br&gt;[[File:customer_list.JPG|900px]]<br /> <br /> Organization details such as contacts and access roles can be edited on the organization profile.<br /> * main customer admin (owner) is assigned<br /> * owner can make other people admins granting them &quot;customer admin&quot; role.<br /> * customer owner(admins) have full access to devices belonging to a particular customer/organization account (can export data, manage trackings and animals, etc.)<br /> <br /> <br /> [[DATA_FLOWS|Various inbound and outbound data flows]] from manual data export to fully automated can be managed for organization account<br /> * (IN) Inbound data flows (connectors for Movebank, Ornitela, and Ecotone available)<br /> * (IN) Manual data import (see the Import functionality)<br /> * (OUT) API data access<br /> * (OUT) Manual data export<br /> * (OUT) Anitra to Movebank datafeed<br /> <br /> Note, only the legal owners of original data are allowed to configure inbound data flows! <br /> * Any data uploaded manually or synchronized automatically to Anitra are linked to a particular legal entity (Organisation / Customer) represented by its &quot;owner&quot; i.e. person in charge.<br /> * The ownership of and the responsibility for all the data remain with this legal entity. This organization's owner and admins assigned by the owner retain full control over the data related to this entity.<br /> * Anitra works as private and secure storage and a visualization tool of these data only.<br /> <br /> Data Management section of Customer profile is also a place to define and review customer [[PUBLISHED_MAPS|published maps]] i.e. a creation wizard for maps construction.<br /> <br /> ''Note the term &quot;customer&quot; refers to any &quot;organization&quot; having some kind of (active or past) commercial agreement with Anitra company''<br /> <br /> '''Customer balance''' - i.e. usage/charging summary vs. payment history is available in the Customer profile&lt;br&gt;[[File:spending_payments_tab.jpg|900px]]<br /> <br /> : A list of the devices owned by the customer is updated and visible right before or soon after shipping devices<br /> : Fix data fee calculation is also available instantly<br /> : Overage data charges are updated according to reality after the month is over and the detailed billing summary is available from the mobile network<br /> : Payments (from invoices paid) are visible after the data fee payment is received by us<br /> <br /> = LISTS, GRIDS=<br /> <br /> =={{Fa|fa-tablet}} Device list==<br /> : List of owned or administered devices (= hardware) - accessible only to owners/admins (users with shared data do not have the rights to see this area)<br /> : Click through to device details (profile), sort by the column, browsed by pages, first column freezing, quick system, and user filters<br /> : [[Main_Page#FILTERS_.26_SEARCHES:_How_do_I_find_what_I_am_looking_for_.3F|Search and Filter functionality]]: allows filtering your devices by criteria<br /> : Manageable through Filter manager next to the Search box, marked with icon [[File:C2.JPG|30px]] <br /> :* Predefined quick filters, which cannot be modified (Missing data in the last 7+ days, Anitra devices only, Powered off devices, Wrong tracking configuration, Deployed devices, Mortality indication)<br /> :* You can turn on multiple Quick filters at once in the Quick filter panel<br /> : Context menu - as anywhere in Anitra the right-click mouse context menu offers the most relevant actions for the current context, functionality, or the whole page or a user<br /> : A wide range of columns available. Column selection and more column-related actions using Column manager from the context menu or directly e.g. by drag-drop columns:<br /> :* Column selection, adding, removing columns (a default list can be restored using &quot;reset visibility&quot;)<br /> :* Column renames (default names can be restored using &quot;reset display names&quot;)<br /> :* Column order (a default order can be restored using &quot;reset order&quot;)<br /> : Multi-select for bulk operations (open all in tabs, graph, apply config preset, etc)<br /> : System of warning messages such as Mortality indication: &quot;Device Status&quot; colored in red and followed by {{red|red skull}} symbol or Missing data last X days: &quot;Last Device Position&quot; followed by red question mark {{red|&quot;?&quot;}}.<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal list ==<br /> <br /> * List of owned Trackings (tab &quot;my trackings&quot;)<br /> * List of Trackings shared with me (tab &quot;shared with me&quot;)<br /> * Overview of all Trackings including first and last data<br /> ** Click through to Tracking detail/profile<br /> ** System of warnings<br /> ** Mortality indication: &quot;Tracking&quot; followed by &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; &lt;span style=&quot;color:red&quot;&gt;skull&lt;/span&gt; symbol<br /> ** Missing data last X days: &quot;Last Data &quot; followed by red question mark &lt;span style=&quot;color:red&quot;&gt;&quot;?&quot;&lt;/span&gt;. Mouse-over symbol tells the last data delay.<br /> <br /> = MAPS =<br /> <br /> : Common map properties and controls<br /> : 1) '''Map zoom''' <br /> :: ''Note besides the zoom buttons you can zoom the map''<br /> ::* ''using the mouse scroll wheel'' <br /> ::* ''or by double-clicking the left mouse button (to zoom in) and the right button (to zoom out)''<br /> <br /> : 2) '''Full-screen''' mode<br /> <br /> : 3) Shows the user/device's '''current position''' on the map as a blue dot <br /> <br /> : 4) '''GPS search''' tool - various GPS formats accepted (e.g. decimal degrees such as &quot;52.7761 27.811889&quot;)<br /> <br /> : 5) '''Background maps''' <br /> :* a wide range of background maps of various types<br /> :* transparent overlays (country and admin borders)<br /> <br /> : 6) '''Transparent map overlays''' <br /> :* country borders <br /> :* admin leve1 1 borders<br /> <br /> : 7) '''Map options''' <br /> :* '''Tracks''' - note the option &quot;'''Clustered'''&quot; simplifies the track by removing movements within clusters<br /> :* '''Waypoints''' - note the option &quot;'''All'''&quot; suppresses the default performance optimisation behavior (= option &quot;'''Filtered'''&quot;) - i.e. enforces showing of all the waypoints<br /> :* '''Annotations''' (aka '''Clusters''') - currently these two Annotatin/Cluster types availabe to be used<br /> :** '''Last positions''' - show/hide the last position of the tracking<br /> :** '''Sleep clusters''' - show/hide the sleep clusters (data from periods defined by solar night/day i.e. by sun angle)&lt;br&gt;[[File:map04_mapFunctionality.JPG|900px]]<br /> <br /> : 8) '''Copy coordinates to clipboard''' <br /> :: using left click context menu<br /> <br /> : 9) '''Measure distance''' <br /> :: using left click context menu&lt;br&gt;[[File:map04_mapFunctionality_2.JPG|600px]]<br /> <br /> <br /> =={{Fa|fa-map-o}} MAIN TRACKING MAP: Where do I see more animals in one map? ==<br /> <br /> : A tool to analyze multiple Trackings / Individuals in a single map.<br /> : The functionality displays all the Tracked Individuals available to a user (both owned/administered and shared only) <br /> : The start view shows an overview of the last positions - the color of the point classifies the last positions by the last update. &lt;br&gt;[[File:map01_lastdatacolors.JPG|900px]]<br /> <br /> : '''Filtering functionality below the map''' limits the data in the map (and in the right Tracking list panel]<br /> :: The three quick filter conditions (&quot;Search&quot;, &quot;Tracking filters&quot;, &quot;Species&quot;) directly filter matching/not matching Trackings/Animals<br /> ::* &quot;Search&quot;: a full-text search across Device/Tracking/Animal codes/names/aliases<br /> ::* &quot;Tracking filters&quot;: existing Tracking filters created by the user can be reused here in the map. This allows applying very complex filter conditions in the map<br /> ::* &quot;Species&quot;: an obvious and simple quick filter conditions<br /> :: Note that the &quot;Days filter&quot; works differently - it uses a time filter over telemetry data first and based on that it leaves or removes Trackings/Animals from the page<br /> ::* it excludes all the trackings with data outside of the time interval<br /> ::* for overlapping Trackings/Animals it limits data/tracks in the map according to the interval defined - i.e. only relevant parts of the tracks are loaded&lt;br&gt;[[File:map02_mapfilterfilled.JPG|900px]]<br /> :: Also note the map filter is stored in the URL (browser address bar). You can open another browser tab with a map page and configure a different filter (eg. another species). Both tabs then work independently.<br /> <br /> : '''Choosing Trackings / Animals to be loaded''' in the map.<br /> :* using tooltips of single last points <br /> :* or for multiple items using the rectangle tool selection in the map (using CTRL + click/drag with left mouse button)<br /> :* selecting/unselcting particular items in the right Tracking pannel (single Trackings or all grouped by species)&lt;br&gt;[[File:map03_TOselection.JPG|900px]]<br /> <br /> : '''Waypoints and Last positions (tooltips)'''<br /> :* More tooltips can be displayed simultaneously<br /> :* Click through the link to a particular Tracked Object profile&lt;br&gt;[[File:map05_TOdetails.JPG|900px]]<br /> :* Warnings and statuses are shown in tooltips e.g. mortality being indicated by black/red symbols &lt;br&gt;[[File:map06_mortalityInMap.JPG|900px]]<br /> <br /> == [[PUBLISHED_MAPS|PUBLISHED MAPS: How do I show an overview of our study results to the public?]]==<br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> : A tool tailored to configure simplified and secured live telemetry maps from your full data sets.<br /> <br /> : Configured maps are available in form of a link or in form of short HTML code which can be simply added to your web presentation or published on Facebook.<br /> <br /> : Map output can be created:<br /> :* on top of single organization data <br /> :* on top of &quot;project&quot; (i.e. accross more complex data ownership structure)<br /> <br /> : Map editor with a live preview is used to configure the map&lt;br&gt;[[File:publish_map_configuration_groups.JPG|900px]]<br /> <br /> : Two map modes can be configured:<br /> :* map showing the simplified '''Tracks''' <br /> :* map showing the '''Last positions''' only<br /> <br /> : For the mode of &quot;Tracks&quot; '''Animation''' can be anabled<br /> <br /> : The map configuration includes:<br /> :* animal selection<br /> :* language localisations (alternative language variants)<br /> :* map mode (tracks vs. last position), grouping options, ordering, data filtering (e.g. track simplified to one position a day)<br /> :* security features (security delay, zoom restriction, position &quot;rounding&quot;)<br /> :* presentation and visualization presets (a default map selection, icon/track styles, choice of icons, logos with links, foto gallery, animation enabling)<br /> <br /> : Samples showing some of the map features<br /> :* map with tracks and gallery and animation anabled:https://app.anitra.cz/share/map/5d2e379ed6f9c &lt;br&gt;[[File:publish_map_animationEnabled.jpg|900px]]<br /> :* map of last positions with categories: https://app.anitra.cz/share/map/5f1a97bb13ba5<br /> <br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> = GRAPHS: How to visualize important data relations in graphs? =<br /> <br /> : Graph functionality available<br /> :* as a tab in Device and Tracking profiles (see #0)<br /> :* for a group of Devices (only admin functionality now).<br /> <br /> : Time is indicated by the horizontal axis (see #1)<br /> : By default period of the last 7 data days is loaded.<br /> : The interval shown can be managed either by the interval slider (see #2) or using the date input below the chart area (see #3).&lt;br&gt;[[File:graph_time.jpg|600px]]<br /> <br /> : You can hover over the chart to preview the actual values (see #4).<br /> : The values of metrics are plotted at the vertical axis of the graph (see #5).<br /> : The scale for a particular metric is shown on the left and right from the graph area (see #6).<br /> : To quickly show/hide a particular metric click the label color above the graph (only used till the next page reload)(see #7).&lt;br&gt;[[File:graph_orientation.jpg|600px]]<br /> <br /> : You can customize your metric list (visibility) and order using the &quot;Choose metrics&quot; button below the chart (see #8).<br /> : Visibility (see #9) and order (see #10) is controlled by drag'n'drop action.&lt;br&gt;[[File:graph_choseMetrics.jpg|600px]]<br /> <br /> : Visibility and order can also be managed in &quot;Edit graph columns&quot; from the context menu (see #11). <br /> : Additionally, this functionality offers even more properties to be controlled such as custom rename (see #12) or colors, graph type, and default value range (see #13). <br /> : It also allows resetting the changes to system defaults (reset options in the top right corner)(see #14)&lt;br&gt;[[File:graph_editColumns.jpg|600px]]<br /> <br /> ={{Fa|fa-photo}}PHOTO GALLERY: Where do I browse all the photos? =<br /> <br /> * Displays a complete gallery of pictures from all the Trackings (own and shared)<br /> * Filtering by main attributes &lt;br&gt;[[File:TO.JPG|900px]]<br /> <br /> = {{Fa|fa-cog}} MANAGING and CONFIGURING of Anitra Tags =<br /> <br /> == Device Status and Discard Flow ==<br /> <br /> : '''Device Status''' attribute is automatically assigned based on device usage history (including its past and current deployments)<br /> :: ''E.g. the tags are automatically moved from Pool to Deployed statuses by creating Tracking (+Animal) object. [[TRACKING_ANIMAL| Check the detailed guide here.]]''<br /> <br /> :: ''pool-new'' : devices never deployed previously<br /> :: ''pool-used'': devices returned to the device pool after deployment<br /> :: ''deployed-active'': deployed on animals, known to have delivered fresh data within the last 3 days<br /> :: ''deployed-delayed'': deployed on animals, known to have delivered fresh data within the last 4-7 days<br /> :: ''deployed-missing'': last data older than 7 days<br /> <br /> :: ''Note Devices status applies to all the devices types including data imported from Movebank of from Import flow.''<br /> <br /> : '''Device/SIM Discard Flow''' (for Anitra devices) <br /> :: Device/SIM closing(discard/termination) workflow is available for Anitra device owners so the SIM can be closed and the device removed from (data fees) billing<br /> :: Users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.<br /> :: Marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider <br /> :: SIM is ultimately terminated by the end of the month following after marking the device to be discarded ''(e.g for a device marked to be discarded on the 13th of February the SIM will be active (and data fees charged till the end of the March))''<br /> :: Note you can still stop the discard process till the SIM is irreversibly terminated by the network operator by contacting us directly till the end of the following month (i.e. for the example above we can manually withdraw the SIM closing request till the 31st of March)<br /> :: The check for marking devices to be terminated is available at the bottom part of the device profile.<br /> <br /> : Device Discard/Archive flow for non-Anitra devices<br /> :: For non-Anitra devices (= devices originating from import or integration - i.e. Movebank, Ornitela, Ecotone, Manual Import) there is also a Discard/Archive mark present in the Device profile <br /> :: For those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)<br /> :: A recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel <br /> :: Note in this case the flag is fully reversible (the user can change it there and back without any restriction)<br /> <br /> : '''Device Status Extended/Long''' <br /> :: Extended/long devices status is summarizing all the status information related.<br /> :: It is a combined field of Device status, history summary and Discard status.<br /> :: It is displayed in the Device profile, Device list, and Customer balance overview<br /> <br /> == Configuration /programming of devices == <br /> <br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> &lt;br&gt;<br /> : Users with admin rights can access the configuration from the lists and profiles using cogwheel icons. Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> &lt;br&gt;<br /> : Configuration contains three main areas<br /> :* Data collection settings<br /> :** GPS/sensor sampling time schedules<br /> :** Data collection triggered by events<br /> :** Configuration of bursting behavior<br /> :** Mortality detection adjustment<br /> :** Geofencing<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> <br /> = OTHER PRODUCTIVITY TOOLS =<br /> == FILTERS &amp; SEARCHES: How do I find what I am looking for ? ==<br /> <br /> Various features helping user find and filter down what is needed are available in Anitra:<br /> <br /> # '''Global full text search'''&lt;br&gt;- full text seach accross all the objects of various types which user has access rights to.&lt;br&gt;- a list of relevant item s sorted by relevancy is returned&lt;br&gt;[[File:global_full_text_search.JPG|500px]]<br /> # '''Grid search'''&lt;br&gt;- seaches in important fields in displayed grid only&lt;br&gt;[[File:grid_search.JPG|500px]] <br /> # '''System and Custom &quot;Quick&quot; filters'''&lt;br&gt;- allows quickly filter data using predefined &quot;system&quot; or &quot;user defined&quot; filters&lt;br&gt;- filters are available as icons on top of the device or tracking grid header line&lt;br&gt;- custom filters can be created in &quot;Filter manager&quot;&lt;br&gt;[[File:quick_filters.JPG|900px]] <br /> # '''Published map filters'''<br /> <br /> * Filter manager <br /> ** Customized quick filters that filter devices according to specified criteria (e.g. Device list, Name fields, Device notes..), you can set multiple criteria at once &lt;br&gt;:[[File:B.JPG|900px]] <br /> ** You can save your customized filter with the green &quot;check&quot; icon &lt;br&gt;:[[File:Ml.JPG|900px]] <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:Mil.JPG|900px]] <br /> <br /> * Filter functionality: allows filtering your trackings by criteria <br /> ** Predefined quick filters, which cannot be modified (Mortality Warning, Last data warning only, Anitra devices only)<br /> ** Customized quick filters, which filter Trackings by set criteria (e.g. Tracked Objects, Name fields, Note fields..), you can set multiple criteria at once <br /> ** You can save your customized filter with the green &quot;check&quot; icon <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:ksdjf.JPG|900px]] <br /> ** You can turn on multiple Quick filters at once in the Quick filter panel<br /> <br /> == NOTES: Where to note down info about particular things? ==<br /> : A handy feature helping users to get organized and stay organized with their data.&lt;br&gt;:[[File:note_thread_narrow.JPG|600px]]<br /> <br /> : Available for multiple entities (Devices, Trackings, Animals, and Customers/Organizations)<br /> <br /> : Note threads can be accessed <br /> :* from entity profiles - in the green shown opening of the Tracking note, the blue mark on the right shows the place to access the device note &lt;br&gt;[[File:note_from_profile.JPG|900px]]<br /> :* entity lists or using the context menu - either click on the note icon in the Notes column or use the context menu over the desired row&lt;br&gt;[[File:note_from_listContext.JPG|900px]]<br /> :* from user Task List &lt;br&gt;[[File:task_userTaskList.jpg|700px]]<br /> : Here a new note can be created, existing notes can be edited, or a reply to previous notes can be posted.<br /> : The thread window is flowing over the entity. It can be open parallel to whatever you do in your profile. You can switch tabs, type forms, take screenshots while browsing, or even create/edit notes. <br /> <br /> : Create the note simply by typing in the form<br /> : Edit existing notes by double-clicking them or using &quot;more&quot; or &quot;Edit&quot; icons in the right top corner. This switches note into &quot;'''edit'''&quot; mode&lt;br&gt;<br /> :[[File:note_editMode.JPG|500px]]<br /> : Save the new or edited note by clicking the &quot;Publish/Done&quot; button or simply hitting ENTER.<br /> : While creating or editing you can cancel by the &quot;Cancel&quot; button or using ESC on your keyboard<br /> : The note text does not allow formatting but you can structure the note to more rows. Use SHIFT+ENTER for the new line (as ENTER is reserved for the &quot;Save&quot; operation)<br /> : An existing note can be deleted using the &quot;more&quot; button &gt;&gt; &quot;Delete thread&quot;. Note while deleting the parent note all the replies will also be deleted.<br /> : &quot;Clone note&quot; function - particularly useful e.g. for fast duplicating of notes with complex definitions (i.e. notes linked to many items). <br /> :: ''While cloning notes attachments are removed (not cloned with the note).''&lt;br&gt;:[[File:note_deleteClone_thread.JPG|500px]]<br /> : Use &quot;Promote to parent note&quot; when you need to convert a note reply to a top-level parent note. <br /> :: ''While promoting reply to note it inherits the relations from its original parent note''<br /> : Use &quot;drag'n'drop: action to move one note into the reply area of the other note to move and transform the note into the reply. <br /> :: ''Converting note into reply is only possible for notes created by the user himself and only to notes that have no complex relationship''<br /> <br /> : By default the note thread is<br /> :* sorted starting with newest notes up. You can invert the sort order to have the oldest notes on top of the page. This setting is remembered in your user preferences.<br /> :* positioned on the top right side of the page. You can modify the position by dragging the floating window to any side, This setting is remembered in your user preferences.<br /> :* sized to one-third of the screen width. You can switch the window size between one-third and one-half by the &quot;shrinking/stretching&quot; button. This setting is also remembered in your user preferences.&lt;br&gt;:[[File:note_sortSizePosition.JPG|600px]]<br /> <br /> : Notes can be saved as<br /> :* shared - will be visible to all the users with access to the entity. a way to share knowledge, tasks, and the status of particular items<br /> :* private - will be visible only to the author of the note. a way to note down things or ToDos only for the author&lt;br&gt;:[[File:note_sharedPrivate.JPG|600px]]<br /> <br /> : The functionality contains a complex toolkit covering&lt;br&gt;:[[File:note_functionality_options.JPG|900px]]<br /> :* relations - a single note (thread) can be linked to multiple items of the same type (e.g. a single/shared note linked to 5 devices)<br /> :* attachments<br /> :** To each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)<br /> :** Picture attachments are then previewed in the thread, photos can be opened in full size and browsed as a gallery<br /> :* screenshots<br /> :** For adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body. <br /> :** This will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.<br /> :* links/URL<br /> :* tags - you can label your notes by using user &quot;tags&quot;, later you can search, filter, or group by these tags<br /> <br /> == TASKS (TODOS): Where to note down reminders and ToDos ? ==<br /> <br /> : Extension of the Notes functionality<br /> : By assigning a note to someone (to ''another user'', to ''user himself'' or to ''anyone'') the note is transformed into the Task (ToDo)<br /> <br /> : Use the button below the note editor or simply type @+name to assign the note as a task to someone&lt;br&gt;[[File:task_assignment.jpg|600px]]<br /> :* assigning a task to another person (''@other.person'') will list the task in the other person's Task list (as created by you).<br /> :* assigning a task to yourself (''@your.name'') will list the task in your Task list (as created by yourself).<br /> :* assigning a task to anyone (''@anyone'') will create a shared task displayed to all the people with access to the linked entity (e.g. particular device, tracking, or customer)<br /> <br /> : A simple workflow for tasks exists - the task can be in one of the three states<br /> :* new/open (= to be completed, highlighted by yellow background)<br /> :* completed /done (= marked as completed, highlighted by a green background)<br /> :* canceled / rejected (highlighted by a reddish background)&lt;br&gt;[[File:task_statusColors.jpg|600px]]<br /> <br /> : Users can move the tasks between the states using icons and controls in the right corner&lt;br&gt;:[[File:task_statusChange.jpg|600px]]<br /> <br /> : User Task board screen shows all the ToDos assigned to the user or defined by the user to others<br /> : Entity note thread can be accessed from the Task list by clicking the particular task<br /> : Task status can be changed from here or some comments added<br /> : You can also jump to the profile screen of the linked entity by clicking its name&lt;br&gt;:[[File:task_userTaskList.jpg|600px]]<br /> <br /> == COLUMN EDITOR: How can I adjust columns I see? ==<br /> <br /> : All the data visualization and download features are designed to allow users to pick and modify the columns to be used. <br /> : Use &quot;Edit columns&quot; options from the context menu of the functionality you wish to modify.<br /> : Beyond choosing the columns, the Edit functionality allows customizing names, order, color, graph type, and ranges, and reset changes to the default.<br /> : Edit columns option is available for <br /> :* metadata (device/tracking) lists<br /> :* metadata list exports<br /> :* profile data table columns<br /> :* profile graph columns<br /> :* data export columns<br /> : See the [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|Graphs section]] for some screens of column editing<br /> <br /> : Both metadata and data can be accessed via [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]] and same here the columns to be included can also be managed at the level of API query<br /> : [https://anitracking.com/api/| The detailed API specification] provides basic info about columns available.<br /> <br /> == USER PREFERENCES: How can I customize my user experience ? ==<br /> <br /> : Various features in the application are designed to remember user modifications<br /> : You can see and manage all your user preferences in the User preferences screen<br /> : The preferences listed are organized into categories <br /> : It is accessible from the user avatar in left menu or anywhere from right click context menu&lt;br&gt;[[File:user_preferences.jpg|600px]]<br /> <br /> = [[DATA_FLOWS | DATA FLOWS: How do I get the data IN/OUT?]] =<br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> : Anitra offers a range of data manipulation options on how to get data and metadata IN or OUT of the platform.<br /> <br /> : This functionality area involves features of data import, export, automated data connectors or API access<br /> <br /> : The options range from purely manual (e.g. [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|manual data exports]] or [[DATA_FLOWS#.28IN.29_Manual_data_import|data imports]]) to fully automated (e.g. [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|inbound data flows for Ornitela, Ecotone, or Movebank]]).<br /> <br /> : Some flows make sense for the particular user but most of the data management tools are meant to be configured at the level of customer/organization (hence available in customer profile)<br /> <br /> : '''Outbound data flows:'''<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Data Export]]&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_METADATA_Export|Metadata Export]]&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|API (both data and metadata)]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_to_Movebank_data_feed|Anitra to Movebank data feed]]<br /> <br /> : '''Inbound data flows:'''<br /> :* [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|Data integration of external data sources (i.e. connectors for Movebank, Ornitela, and Ecotone available)]]&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> :* [[DATA_FLOWS#.28IN.29_Manual_data_import|Data Import]]&lt;br&gt;[[File:manual_customer_import.JPG|900px]]<br /> <br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> = WARNINGS, NOTIFICATIONS=<br /> <br /> ==MORTALITY WARNINGS== <br /> [[File:DTO0000.JPG|36x37px]] Red skull<br /> * Indicates mortality detected by onboard mortality detector (Anitra tags only)<br /> * More about mortality detector in firmware configuration<br /> * The flag is stored at the level of database records (visible in data history anytime the device detected mortality)<br /> <br /> [[File:DTO000.JPG|44x38px]] Black skull<br /> : Notifies on possible mortality in the last records of trackings as estimated by server post-process analysis<br /> : Recalculated <br /> :* with new received data<br /> :* with modification of the tracking range (i.e. when closing active Tracking or when updating Tracking End Date)<br /> : The flag is recalculated and visible for the last data only (not visible in data history).<br /> : Algorithm factors in roll and pitch oscillations for the latest three records and/or the last 3 hours<br /> <br /> Red bird belly up<br /> : Unnatural body position in the very last record (roll and pitch)<br /> : whenever the absolute value of the angle for Roll or Pitch exceeds 90 degrees<br /> <br /> <br /> =={{Fa|fa-map-o}} RELEASE NOTES==<br /> <br /> : Latest release note overview is shown to the user any time a new release is deployed since the last user's Anitra access.<br /> : After being displayed the screen is no longer shown till another release<br /> : The release note screen aggregates data from the past 60 days are shown.<br /> : Release note screen can be manually invoked by pressing the Anitra icon (left top corner of the application)&lt;br&gt;[[File:ReleaseNotes_drill.jpg|900px]]<br /> <br /> =[[MORE_GUIDES| MORE GUIDES]]=<br /> <br /> : [[RK_WINTERCOUNT_TIPS| LIFE EUROKITE Red kite Wintering count (Anitra tips)]]<br /> <br /> : [[EUROKITE_PROJECT_DATASHARING| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]</div>

Admin index.php?title=Main_Page&diff=1260 2024-05-02T12:24:11Z

<p>Admin: /* MAIN CONCEPTS */</p> <hr /> <div>{{DISPLAYTITLE: Anitra Platform User Guide}}<br /> <br /> '''ABOUT'''<br /> &lt;br&gt;<br /> : Anitra platform is a flexible environment that allows storing, analyzing, and visualizing telemetry data. On top of actual telemetry data, a lot of additional metainformation and field information can be stored to document and visualize data in a very rich context. Anitra is primarily tailored to manage even very complex telemetry projects but similarly, a single user data can be comfortably maintained. <br /> <br /> : The tool allows hosting data generated by transmitters of any brand however some of the more advanced features are tailored to complement the unique onboard functionality of ANITRA GPS-GSM transmitters only. Part of the core functionality serves as a device backend for Anitra tags (a functionality for Data Owners/Admins). An elaborated sharing scheme allows granting a full range of access rights from &quot;admin&quot; to &quot;view only&quot;. Data in form of the maps can be made public in a very controlled and safe way. Most of the platform functionality is free of any charge and available to anyone having some defined access rights to particular data sets. Some data-intensive areas such as data/photo storage might be possibly restricted or charged per amount of data.<br /> <br /> <br /> = [[SIGNING_IN | SIGNING IN - How do I get into the app?]] =<br /> <br /> : Home screen of the ANITRA platform is at https://app.anitra.cz/<br /> <br /> : New users can register in the system either using &quot;Create new account link&quot; or using the &quot;SIGN IN WITH GOOGLE&quot; button ''(you will not need to type user name+pass anymore)''&lt;br&gt;[[File:sign-in_ user,pass_createNew.JPG|400px]]<br /> <br /> : Note new user can also be created by other existing users sending an invitation to the new person from access granting wizards (e.g. sharing tracking, adding admins, or assigning project access) - typing a new email address launches the invite process &lt;br&gt;[[File:user_invite_dialogue.jpg|400px]]<br /> <br /> : Once you have your account created and active you can log in either typing user name and password or using Google sign-in feature<br /> <br /> : You can review and modify your details and preferences in your user profile later.&lt;br&gt;[[File:user_profile_google_auth.JPG|900px]]<br /> <br /> : ''[[SIGNING_IN| More about User creation and user managment here]].''<br /> <br /> <br /> = MAIN CONCEPTS =<br /> &lt;br&gt;<br /> : Anitra data model is based on the following key concepts:<br /> <br /> : '''Device'''<br /> :: Device (or Tag) entity represents the physical telemetry hardware that collects particular telemetry data. Any tracking and sensor data are linked to one of the devices.<br /> <br /> :: Devices are created automatically in the system while importing a new telemetry dataset (via Import or Integration flow) or created by us in the case of Anitra devices (created as part of the device purchase process).<br /> <br /> :: Device Status attribute reflects the current usage of the devices (statuses are '''pool-new''', '''pool-used''', '''deployed-active''', '''deployed-delayed''', and '''deployed-missing'''). <br /> :: Besides, a &quot;Discard&quot; flag is available to mark the tags that are considered out of service. <br /> :: [[Main_Page#Device_Status_and_Discard_Flow |More on device statuses and discard flow here]].<br /> <br /> :: Attributes related to the hardware (brand, model, serial no., GSM no., etc.) or summary metrics can be seen and managed in the [[Main_Page#Device_profile|Device profile]].<br /> <br /> <br /> : '''Organisation, Customer, or Ownership'''<br /> :: Device &quot;Ownership&quot; defines which organization/customer holds ownership of the data.<br /> :: Purchased Anitra devices are transferred under the Customer account during the purchasing process.<br /> :: Non-Anitra devices are linked to particular Customers by running integration connectors or Importing data manually.<br /> <br /> :: Customer account also holds the credit balance (data fee prepay)<br /> <br /> <br /> : '''Animal'''<br /> :: Animal (or Individual) entity represents a particular animal/individual <br /> <br /> :: The main attributes for an Animal are its Species, Sex, and Dates when Born and Died (~ which also defines the current age e.g.).<br /> <br /> :: Additional complex meta-information can be linked-to Animal such as origin info, relationships to other animals, ringing, tagging or trapping details, and mortality attributes<br /> <br /> :: Photos (or documents) can be attached either directly to the Animal entity or indirectly to some related entities or Events such as Tagging or Mortality.<br /> <br /> <br /> : '''Tracking'''<br /> :: Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on [[TRACKING_ANIMAL|creation and modification of the tracking range]].<br /> <br /> :: The date(time) interval defines when the device was physically attached to the Animal<br /> <br /> :: ''Note when looking at the timeline of a particular Animal, multiple telemetry devices might have been used to track it subsequently (e.g. first tag failed and removed or was shed by the animal). Similarly, when analyzing Device usage history a single device might have been possibly reused several times for Tracking various animals (e.g. one animal died, the tag was recovered and reused elsewhere).''<br /> <br /> :: Besides the time aspect, some additional details such as place of tagging, place of release, tagging persons, various notes, photos, etc can be attached to Tracking Start/End. <br /> <br /> :: Tracking inherits permissions from its parent Device entity so users with device owner/admin access can create and modify the deployments as well.<br /> <br /> <br /> : '''Group''', Project, Study<br /> : '''Person''', User, Role<br /> :: Data owners can make their data available to other users or even make their data public in a simplified and secured way using an elaborated sharing scheme. Each user can act in both modes (i.e. admin for owned or administered devices and viewer for data shared with him by others). Most of the platform functionality is free of charge and available to anyone. Only large data volumes might be possibly restricted or charged. <br /> <br /> <br /> : '''Place''', Point of Interest (POI)<br /> : '''Event''', Observation<br /> <br /> <br /> : '''Device Data''', Records, Positions, Outliers<br /> :: Measurement data collected by telemetry devices. <br /> :: A combination of the device ID and UTC timestamp (date time in milliseconds) uniquely identifies each record.<br /> :: Records are linked to devices but can also be fetched for child Trackings, or Animals.<br /> <br /> :: '''Record''': a dataset related to particular UTC timestamp carrying measurements performed by particular device sensors (such as GNSS module, IMU, barometer)<br /> :: '''Position''': a record with a successful GPS fix (obtained Latitude and Longitude). Positions can be shown on maps.<br /> :: '''Outlier''': a record without GPS fix (no valid Latitude/Longitude) due to unsuccessful, skipped, or wrong GPS fixing. Note Outliers are not shown in maps but can still be displayed in table, timeline, and graph view.<br /> <br /> :: You can visualize, analyse, or download data using the Anitra platform functionality.<br /> ::: Within the platform you can see the data in [[Main_Page#MAIN_TRACKING_MAP:_Where_do_I_see_more_animals_in_one_map.3F|the main overview tracking map]] or in [[Main_Page#Device_profile|the (device or tracking) profile]] data tables, maps, timelines, and graphs<br /> ::: To analyze data outside of Anitra you can use the [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Export]] functionality or [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]].<br /> <br /> :: Note the list of columns/metrics covered by the Anitra data model can be understood from various places:<br /> ::* [[DATA_COLUMNS| a table of the most important metrics]] with explanations and comments - primarily to explain those used by Anitra tags<br /> ::* a detailed [https://anitracking.com/api/ Anitra API specification] provides a list of all the columns available over the API with a brief description<br /> ::* [[Main_Page#COLUMN_EDITOR:_How_can_I_adjust_columns_I_see.3F|column editor]] functionality lists the available columns per platform functionality.<br /> ::* the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality reference guide provides the samples/examples of files, columns, or formats to be used while importing data.<br /> ::* for additional explanations about some columns you can also refer to [https://www.movebank.org/cms/movebank-content/movebank-attribute-dictionary| Movebank attribute dictionary]. As the data from Movebank can be easily integrated in Anitra the data model and column names are ovelapping much.<br /> <br /> : '''Data Cluster''', Annotation<br /> :: an object created (automatically or manually) on top of the telemetry data that annotates a series of Records into semantic groups (such as Mortality or Night clusters)<br /> :: these clusters can be used to simplify the visibility of tracks and positions in the maps by masking redundant details showing aggregated information.<br /> <br /> = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =<br /> Most entities in Anitra carry a certain list of attributes and offer a range of functions and operations related to it. The place that accommodates all this is a detail or profile page of it. <br /> <br /> Depending on the importance and complexity of a particular entity, the detail page might be rather simple (e.g. Person/User profile) or more structured and information-rich (e.g. Tracking/Animal profile). Most important entity pages are described here:<br /> <br /> =={{Fa|fa-tablet}} Device profile ==<br /> <br /> : '''Device profile''' tab (tab control marked green): <br /> :* holds all the information about the device (identification, status, type, brand, model, and user description<br /> :* allows administration of the device (i.e. managing admin list, activating Movebank Datafeed, exporting device data into the file, configuring/programming tag (cogwheel icon))<br /> :* shows device activity (i.e. bits needed for monitoring: Statistics, System of warnings (mortality, missing data), the last position in the overview map, first/last geolocation, communication log (wifi icon))<br /> :* lists Trackings/Animals created on top of device data (bottom right) - more rows in situation when single tag was redeployed multiple times &lt;br&gt;[[File:device_profile_functionality_marked.jpg|900px]]<br /> <br /> : '''Data''' tab (marked green):<br /> :* data collected by the tag visualized in the table, on the map, in the timeline, and the graph<br /> :* [[MORE_GUIDES#Tracking_range_management|functionality for creation of Trackings (aka Deployments) and modification of the DateTime ranges]].&lt;br&gt;[[File:01_create_new_tracking_here - kontext.jpg|900px]]<br /> <br /> : '''Graph''' tabs (marked green):<br /> :* data collected by the tag can be analysed in the graph<br /> :* wide range and flexible selection of columns for display<br /> :* [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|More about graphs here]]&lt;br&gt;[[File:device_profile_graph_marked.jpg|900px]]<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal profile ==<br /> <br /> * Details of tracked object (= tracking of the individual animal)<br /> ** Identification (code, name, ringing, tagging, etc.)<br /> ** Info related to particular Individual (species, sex, age, origin)<br /> ** Info related to Start of tracking (including photo and file documentation)<br /> ** Info related to End of tracking (~ mortality/device failure)<br /> * System of warnings<br /> ** Mortality indication: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt;/black warning in &quot;Last known Position&quot; row (&lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; = for deployed and currently tracking devices / black = tracking finished)<br /> ** Missing data last X days: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; warning in &quot;Last Device Position&quot; row (warning active just for deployed and currently tracking devices)<br /> :[[File:TOP00.JPG|738x138]]<br /> <br /> * Tracked animal data visualized on the map and on the timeline &lt;br&gt;[[File:TOP01.JPG|900px]]<br /> <br /> * &quot;Share&quot; button allows sharing Tracking to other Anitra users<br /> * Possibility to attach photos /documents related to<br /> ** Tracking start<br /> ** Mortality<br /> * Same photo can be shared by various Trackings &lt;br&gt;[[File:TOP02.JPG|900px]]<br /> <br /> =={{Fa|fa-user}} Organisation/Customer profile==<br /> <br /> A section visible in the side menu (only) for users with Admin/Owner relations to Organisations listed in the system. <br /> * users not having any role in any organization do not see this menu item at all<br /> * in case the user is active in more organizations the list of these is displayed first&lt;br&gt;[[File:customer_list.JPG|900px]]<br /> <br /> Organization details such as contacts and access roles can be edited on the organization profile.<br /> * main customer admin (owner) is assigned<br /> * owner can make other people admins granting them &quot;customer admin&quot; role.<br /> * customer owner(admins) have full access to devices belonging to a particular customer/organization account (can export data, manage trackings and animals, etc.)<br /> <br /> <br /> [[DATA_FLOWS|Various inbound and outbound data flows]] from manual data export to fully automated can be managed for organization account<br /> * (IN) Inbound data flows (connectors for Movebank, Ornitela, and Ecotone available)<br /> * (IN) Manual data import (see the Import functionality)<br /> * (OUT) API data access<br /> * (OUT) Manual data export<br /> * (OUT) Anitra to Movebank datafeed<br /> <br /> Note, only the legal owners of original data are allowed to configure inbound data flows! <br /> * Any data uploaded manually or synchronized automatically to Anitra are linked to a particular legal entity (Organisation / Customer) represented by its &quot;owner&quot; i.e. person in charge.<br /> * The ownership of and the responsibility for all the data remain with this legal entity. This organization's owner and admins assigned by the owner retain full control over the data related to this entity.<br /> * Anitra works as private and secure storage and a visualization tool of these data only.<br /> <br /> Data Management section of Customer profile is also a place to define and review customer [[PUBLISHED_MAPS|published maps]] i.e. a creation wizard for maps construction.<br /> <br /> ''Note the term &quot;customer&quot; refers to any &quot;organization&quot; having some kind of (active or past) commercial agreement with Anitra company''<br /> <br /> '''Customer balance''' - i.e. usage/charging summary vs. payment history is available in the Customer profile&lt;br&gt;[[File:spending_payments_tab.jpg|900px]]<br /> <br /> : A list of the devices owned by the customer is updated and visible right before or soon after shipping devices<br /> : Fix data fee calculation is also available instantly<br /> : Overage data charges are updated according to reality after the month is over and the detailed billing summary is available from the mobile network<br /> : Payments (from invoices paid) are visible after the data fee payment is received by us<br /> <br /> = LISTS, GRIDS=<br /> <br /> =={{Fa|fa-tablet}} Device list==<br /> : List of owned or administered devices (= hardware) - accessible only to owners/admins (users with shared data do not have the rights to see this area)<br /> : Click through to device details (profile), sort by the column, browsed by pages, first column freezing, quick system, and user filters<br /> : [[Main_Page#FILTERS_.26_SEARCHES:_How_do_I_find_what_I_am_looking_for_.3F|Search and Filter functionality]]: allows filtering your devices by criteria<br /> : Manageable through Filter manager next to the Search box, marked with icon [[File:C2.JPG|30px]] <br /> :* Predefined quick filters, which cannot be modified (Missing data in the last 7+ days, Anitra devices only, Powered off devices, Wrong tracking configuration, Deployed devices, Mortality indication)<br /> :* You can turn on multiple Quick filters at once in the Quick filter panel<br /> : Context menu - as anywhere in Anitra the right-click mouse context menu offers the most relevant actions for the current context, functionality, or the whole page or a user<br /> : A wide range of columns available. Column selection and more column-related actions using Column manager from the context menu or directly e.g. by drag-drop columns:<br /> :* Column selection, adding, removing columns (a default list can be restored using &quot;reset visibility&quot;)<br /> :* Column renames (default names can be restored using &quot;reset display names&quot;)<br /> :* Column order (a default order can be restored using &quot;reset order&quot;)<br /> : Multi-select for bulk operations (open all in tabs, graph, apply config preset, etc)<br /> : System of warning messages such as Mortality indication: &quot;Device Status&quot; colored in red and followed by {{red|red skull}} symbol or Missing data last X days: &quot;Last Device Position&quot; followed by red question mark {{red|&quot;?&quot;}}.<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal list ==<br /> <br /> * List of owned Trackings (tab &quot;my trackings&quot;)<br /> * List of Trackings shared with me (tab &quot;shared with me&quot;)<br /> * Overview of all Trackings including first and last data<br /> ** Click through to Tracking detail/profile<br /> ** System of warnings<br /> ** Mortality indication: &quot;Tracking&quot; followed by &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; &lt;span style=&quot;color:red&quot;&gt;skull&lt;/span&gt; symbol<br /> ** Missing data last X days: &quot;Last Data &quot; followed by red question mark &lt;span style=&quot;color:red&quot;&gt;&quot;?&quot;&lt;/span&gt;. Mouse-over symbol tells the last data delay.<br /> <br /> = MAPS =<br /> <br /> : Common map properties and controls<br /> : 1) '''Map zoom''' <br /> :: ''Note besides the zoom buttons you can zoom the map''<br /> ::* ''using the mouse scroll wheel'' <br /> ::* ''or by double-clicking the left mouse button (to zoom in) and the right button (to zoom out)''<br /> <br /> : 2) '''Full-screen''' mode<br /> <br /> : 3) Shows the user/device's '''current position''' on the map as a blue dot <br /> <br /> : 4) '''GPS search''' tool - various GPS formats accepted (e.g. decimal degrees such as &quot;52.7761 27.811889&quot;)<br /> <br /> : 5) '''Background maps''' <br /> :* a wide range of background maps of various types<br /> :* transparent overlays (country and admin borders)<br /> <br /> : 6) '''Transparent map overlays''' <br /> :* country borders <br /> :* admin leve1 1 borders<br /> <br /> : 7) '''Map options''' <br /> :* '''Tracks''' - note the option &quot;'''Clustered'''&quot; simplifies the track by removing movements within clusters<br /> :* '''Waypoints''' - note the option &quot;'''All'''&quot; suppresses the default performance optimisation behavior (= option &quot;'''Filtered'''&quot;) - i.e. enforces showing of all the waypoints<br /> :* '''Annotations''' (aka '''Clusters''') - currently these two Annotatin/Cluster types availabe to be used<br /> :** '''Last positions''' - show/hide the last position of the tracking<br /> :** '''Sleep clusters''' - show/hide the sleep clusters (data from periods defined by solar night/day i.e. by sun angle)&lt;br&gt;[[File:map04_mapFunctionality.JPG|900px]]<br /> <br /> : 8) '''Copy coordinates to clipboard''' <br /> :: using left click context menu<br /> <br /> : 9) '''Measure distance''' <br /> :: using left click context menu&lt;br&gt;[[File:map04_mapFunctionality_2.JPG|600px]]<br /> <br /> <br /> =={{Fa|fa-map-o}} MAIN TRACKING MAP: Where do I see more animals in one map? ==<br /> <br /> : A tool to analyze multiple Trackings / Individuals in a single map.<br /> : The functionality displays all the Tracked Individuals available to a user (both owned/administered and shared only) <br /> : The start view shows an overview of the last positions - the color of the point classifies the last positions by the last update. &lt;br&gt;[[File:map01_lastdatacolors.JPG|900px]]<br /> <br /> : '''Filtering functionality below the map''' limits the data in the map (and in the right Tracking list panel]<br /> :: The three quick filter conditions (&quot;Search&quot;, &quot;Tracking filters&quot;, &quot;Species&quot;) directly filter matching/not matching Trackings/Animals<br /> ::* &quot;Search&quot;: a full-text search across Device/Tracking/Animal codes/names/aliases<br /> ::* &quot;Tracking filters&quot;: existing Tracking filters created by the user can be reused here in the map. This allows applying very complex filter conditions in the map<br /> ::* &quot;Species&quot;: an obvious and simple quick filter conditions<br /> :: Note that the &quot;Days filter&quot; works differently - it uses a time filter over telemetry data first and based on that it leaves or removes Trackings/Animals from the page<br /> ::* it excludes all the trackings with data outside of the time interval<br /> ::* for overlapping Trackings/Animals it limits data/tracks in the map according to the interval defined - i.e. only relevant parts of the tracks are loaded&lt;br&gt;[[File:map02_mapfilterfilled.JPG|900px]]<br /> :: Also note the map filter is stored in the URL (browser address bar). You can open another browser tab with a map page and configure a different filter (eg. another species). Both tabs then work independently.<br /> <br /> : '''Choosing Trackings / Animals to be loaded''' in the map.<br /> :* using tooltips of single last points <br /> :* or for multiple items using the rectangle tool selection in the map (using CTRL + click/drag with left mouse button)<br /> :* selecting/unselcting particular items in the right Tracking pannel (single Trackings or all grouped by species)&lt;br&gt;[[File:map03_TOselection.JPG|900px]]<br /> <br /> : '''Waypoints and Last positions (tooltips)'''<br /> :* More tooltips can be displayed simultaneously<br /> :* Click through the link to a particular Tracked Object profile&lt;br&gt;[[File:map05_TOdetails.JPG|900px]]<br /> :* Warnings and statuses are shown in tooltips e.g. mortality being indicated by black/red symbols &lt;br&gt;[[File:map06_mortalityInMap.JPG|900px]]<br /> <br /> == [[PUBLISHED_MAPS|PUBLISHED MAPS: How do I show an overview of our study results to the public?]]==<br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> : A tool tailored to configure simplified and secured live telemetry maps from your full data sets.<br /> <br /> : Configured maps are available in form of a link or in form of short HTML code which can be simply added to your web presentation or published on Facebook.<br /> <br /> : Map output can be created:<br /> :* on top of single organization data <br /> :* on top of &quot;project&quot; (i.e. accross more complex data ownership structure)<br /> <br /> : Map editor with a live preview is used to configure the map&lt;br&gt;[[File:publish_map_configuration_groups.JPG|900px]]<br /> <br /> : Two map modes can be configured:<br /> :* map showing the simplified '''Tracks''' <br /> :* map showing the '''Last positions''' only<br /> <br /> : For the mode of &quot;Tracks&quot; '''Animation''' can be anabled<br /> <br /> : The map configuration includes:<br /> :* animal selection<br /> :* language localisations (alternative language variants)<br /> :* map mode (tracks vs. last position), grouping options, ordering, data filtering (e.g. track simplified to one position a day)<br /> :* security features (security delay, zoom restriction, position &quot;rounding&quot;)<br /> :* presentation and visualization presets (a default map selection, icon/track styles, choice of icons, logos with links, foto gallery, animation enabling)<br /> <br /> : Samples showing some of the map features<br /> :* map with tracks and gallery and animation anabled:https://app.anitra.cz/share/map/5d2e379ed6f9c &lt;br&gt;[[File:publish_map_animationEnabled.jpg|900px]]<br /> :* map of last positions with categories: https://app.anitra.cz/share/map/5f1a97bb13ba5<br /> <br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> = GRAPHS: How to visualize important data relations in graphs? =<br /> <br /> : Graph functionality available<br /> :* as a tab in Device and Tracking profiles (see #0)<br /> :* for a group of Devices (only admin functionality now).<br /> <br /> : Time is indicated by the horizontal axis (see #1)<br /> : By default period of the last 7 data days is loaded.<br /> : The interval shown can be managed either by the interval slider (see #2) or using the date input below the chart area (see #3).&lt;br&gt;[[File:graph_time.jpg|600px]]<br /> <br /> : You can hover over the chart to preview the actual values (see #4).<br /> : The values of metrics are plotted at the vertical axis of the graph (see #5).<br /> : The scale for a particular metric is shown on the left and right from the graph area (see #6).<br /> : To quickly show/hide a particular metric click the label color above the graph (only used till the next page reload)(see #7).&lt;br&gt;[[File:graph_orientation.jpg|600px]]<br /> <br /> : You can customize your metric list (visibility) and order using the &quot;Choose metrics&quot; button below the chart (see #8).<br /> : Visibility (see #9) and order (see #10) is controlled by drag'n'drop action.&lt;br&gt;[[File:graph_choseMetrics.jpg|600px]]<br /> <br /> : Visibility and order can also be managed in &quot;Edit graph columns&quot; from the context menu (see #11). <br /> : Additionally, this functionality offers even more properties to be controlled such as custom rename (see #12) or colors, graph type, and default value range (see #13). <br /> : It also allows resetting the changes to system defaults (reset options in the top right corner)(see #14)&lt;br&gt;[[File:graph_editColumns.jpg|600px]]<br /> <br /> ={{Fa|fa-photo}}PHOTO GALLERY: Where do I browse all the photos? =<br /> <br /> * Displays a complete gallery of pictures from all the Trackings (own and shared)<br /> * Filtering by main attributes &lt;br&gt;[[File:TO.JPG|900px]]<br /> <br /> = {{Fa|fa-cog}} MANAGING and CONFIGURING of Anitra Tags =<br /> <br /> == Device Status and Discard Flow ==<br /> <br /> : '''Device Status''' attribute is automatically assigned based on device usage history (including its past and current deployments)<br /> :: ''E.g. the tags are automatically moved from Pool to Deployed statuses by creating Tracking (+Animal) object. [[TRACKING_ANIMAL| Check the detailed guide here.]]''<br /> <br /> :: ''pool-new'' : devices never deployed previously<br /> :: ''pool-used'': devices returned to the device pool after deployment<br /> :: ''deployed-active'': deployed on animals, known to have delivered fresh data within the last 3 days<br /> :: ''deployed-delayed'': deployed on animals, known to have delivered fresh data within the last 4-7 days<br /> :: ''deployed-missing'': last data older than 7 days<br /> <br /> :: ''Note Devices status applies to all the devices types including data imported from Movebank of from Import flow.''<br /> <br /> : '''Device/SIM Discard Flow''' (for Anitra devices) <br /> :: Device/SIM closing(discard/termination) workflow is available for Anitra device owners so the SIM can be closed and the device removed from (data fees) billing<br /> :: Users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.<br /> :: Marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider <br /> :: SIM is ultimately terminated by the end of the month following after marking the device to be discarded ''(e.g for a device marked to be discarded on the 13th of February the SIM will be active (and data fees charged till the end of the March))''<br /> :: Note you can still stop the discard process till the SIM is irreversibly terminated by the network operator by contacting us directly till the end of the following month (i.e. for the example above we can manually withdraw the SIM closing request till the 31st of March)<br /> :: The check for marking devices to be terminated is available at the bottom part of the device profile.<br /> <br /> : Device Discard/Archive flow for non-Anitra devices<br /> :: For non-Anitra devices (= devices originating from import or integration - i.e. Movebank, Ornitela, Ecotone, Manual Import) there is also a Discard/Archive mark present in the Device profile <br /> :: For those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)<br /> :: A recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel <br /> :: Note in this case the flag is fully reversible (the user can change it there and back without any restriction)<br /> <br /> : '''Device Status Extended/Long''' <br /> :: Extended/long devices status is summarizing all the status information related.<br /> :: It is a combined field of Device status, history summary and Discard status.<br /> :: It is displayed in the Device profile, Device list, and Customer balance overview<br /> <br /> == Configuration /programming of devices == <br /> <br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> &lt;br&gt;<br /> : Users with admin rights can access the configuration from the lists and profiles using cogwheel icons. Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> &lt;br&gt;<br /> : Configuration contains three main areas<br /> :* Data collection settings<br /> :** GPS/sensor sampling time schedules<br /> :** Data collection triggered by events<br /> :** Configuration of bursting behavior<br /> :** Mortality detection adjustment<br /> :** Geofencing<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> <br /> = OTHER PRODUCTIVITY TOOLS =<br /> == FILTERS &amp; SEARCHES: How do I find what I am looking for ? ==<br /> <br /> Various features helping user find and filter down what is needed are available in Anitra:<br /> <br /> # '''Global full text search'''&lt;br&gt;- full text seach accross all the objects of various types which user has access rights to.&lt;br&gt;- a list of relevant item s sorted by relevancy is returned&lt;br&gt;[[File:global_full_text_search.JPG|500px]]<br /> # '''Grid search'''&lt;br&gt;- seaches in important fields in displayed grid only&lt;br&gt;[[File:grid_search.JPG|500px]] <br /> # '''System and Custom &quot;Quick&quot; filters'''&lt;br&gt;- allows quickly filter data using predefined &quot;system&quot; or &quot;user defined&quot; filters&lt;br&gt;- filters are available as icons on top of the device or tracking grid header line&lt;br&gt;- custom filters can be created in &quot;Filter manager&quot;&lt;br&gt;[[File:quick_filters.JPG|900px]] <br /> # '''Published map filters'''<br /> <br /> * Filter manager <br /> ** Customized quick filters that filter devices according to specified criteria (e.g. Device list, Name fields, Device notes..), you can set multiple criteria at once &lt;br&gt;:[[File:B.JPG|900px]] <br /> ** You can save your customized filter with the green &quot;check&quot; icon &lt;br&gt;:[[File:Ml.JPG|900px]] <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:Mil.JPG|900px]] <br /> <br /> * Filter functionality: allows filtering your trackings by criteria <br /> ** Predefined quick filters, which cannot be modified (Mortality Warning, Last data warning only, Anitra devices only)<br /> ** Customized quick filters, which filter Trackings by set criteria (e.g. Tracked Objects, Name fields, Note fields..), you can set multiple criteria at once <br /> ** You can save your customized filter with the green &quot;check&quot; icon <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:ksdjf.JPG|900px]] <br /> ** You can turn on multiple Quick filters at once in the Quick filter panel<br /> <br /> == NOTES: Where to note down info about particular things? ==<br /> : A handy feature helping users to get organized and stay organized with their data.&lt;br&gt;:[[File:note_thread_narrow.JPG|600px]]<br /> <br /> : Available for multiple entities (Devices, Trackings, Animals, and Customers/Organizations)<br /> <br /> : Note threads can be accessed <br /> :* from entity profiles - in the green shown opening of the Tracking note, the blue mark on the right shows the place to access the device note &lt;br&gt;[[File:note_from_profile.JPG|900px]]<br /> :* entity lists or using the context menu - either click on the note icon in the Notes column or use the context menu over the desired row&lt;br&gt;[[File:note_from_listContext.JPG|900px]]<br /> :* from user Task List &lt;br&gt;[[File:task_userTaskList.jpg|700px]]<br /> : Here a new note can be created, existing notes can be edited, or a reply to previous notes can be posted.<br /> : The thread window is flowing over the entity. It can be open parallel to whatever you do in your profile. You can switch tabs, type forms, take screenshots while browsing, or even create/edit notes. <br /> <br /> : Create the note simply by typing in the form<br /> : Edit existing notes by double-clicking them or using &quot;more&quot; or &quot;Edit&quot; icons in the right top corner. This switches note into &quot;'''edit'''&quot; mode&lt;br&gt;<br /> :[[File:note_editMode.JPG|500px]]<br /> : Save the new or edited note by clicking the &quot;Publish/Done&quot; button or simply hitting ENTER.<br /> : While creating or editing you can cancel by the &quot;Cancel&quot; button or using ESC on your keyboard<br /> : The note text does not allow formatting but you can structure the note to more rows. Use SHIFT+ENTER for the new line (as ENTER is reserved for the &quot;Save&quot; operation)<br /> : An existing note can be deleted using the &quot;more&quot; button &gt;&gt; &quot;Delete thread&quot;. Note while deleting the parent note all the replies will also be deleted.<br /> : &quot;Clone note&quot; function - particularly useful e.g. for fast duplicating of notes with complex definitions (i.e. notes linked to many items). <br /> :: ''While cloning notes attachments are removed (not cloned with the note).''&lt;br&gt;:[[File:note_deleteClone_thread.JPG|500px]]<br /> : Use &quot;Promote to parent note&quot; when you need to convert a note reply to a top-level parent note. <br /> :: ''While promoting reply to note it inherits the relations from its original parent note''<br /> : Use &quot;drag'n'drop: action to move one note into the reply area of the other note to move and transform the note into the reply. <br /> :: ''Converting note into reply is only possible for notes created by the user himself and only to notes that have no complex relationship''<br /> <br /> : By default the note thread is<br /> :* sorted starting with newest notes up. You can invert the sort order to have the oldest notes on top of the page. This setting is remembered in your user preferences.<br /> :* positioned on the top right side of the page. You can modify the position by dragging the floating window to any side, This setting is remembered in your user preferences.<br /> :* sized to one-third of the screen width. You can switch the window size between one-third and one-half by the &quot;shrinking/stretching&quot; button. This setting is also remembered in your user preferences.&lt;br&gt;:[[File:note_sortSizePosition.JPG|600px]]<br /> <br /> : Notes can be saved as<br /> :* shared - will be visible to all the users with access to the entity. a way to share knowledge, tasks, and the status of particular items<br /> :* private - will be visible only to the author of the note. a way to note down things or ToDos only for the author&lt;br&gt;:[[File:note_sharedPrivate.JPG|600px]]<br /> <br /> : The functionality contains a complex toolkit covering&lt;br&gt;:[[File:note_functionality_options.JPG|900px]]<br /> :* relations - a single note (thread) can be linked to multiple items of the same type (e.g. a single/shared note linked to 5 devices)<br /> :* attachments<br /> :** To each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)<br /> :** Picture attachments are then previewed in the thread, photos can be opened in full size and browsed as a gallery<br /> :* screenshots<br /> :** For adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body. <br /> :** This will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.<br /> :* links/URL<br /> :* tags - you can label your notes by using user &quot;tags&quot;, later you can search, filter, or group by these tags<br /> <br /> == TASKS (TODOS): Where to note down reminders and ToDos ? ==<br /> <br /> : Extension of the Notes functionality<br /> : By assigning a note to someone (to ''another user'', to ''user himself'' or to ''anyone'') the note is transformed into the Task (ToDo)<br /> <br /> : Use the button below the note editor or simply type @+name to assign the note as a task to someone&lt;br&gt;[[File:task_assignment.jpg|600px]]<br /> :* assigning a task to another person (''@other.person'') will list the task in the other person's Task list (as created by you).<br /> :* assigning a task to yourself (''@your.name'') will list the task in your Task list (as created by yourself).<br /> :* assigning a task to anyone (''@anyone'') will create a shared task displayed to all the people with access to the linked entity (e.g. particular device, tracking, or customer)<br /> <br /> : A simple workflow for tasks exists - the task can be in one of the three states<br /> :* new/open (= to be completed, highlighted by yellow background)<br /> :* completed /done (= marked as completed, highlighted by a green background)<br /> :* canceled / rejected (highlighted by a reddish background)&lt;br&gt;[[File:task_statusColors.jpg|600px]]<br /> <br /> : Users can move the tasks between the states using icons and controls in the right corner&lt;br&gt;:[[File:task_statusChange.jpg|600px]]<br /> <br /> : User Task board screen shows all the ToDos assigned to the user or defined by the user to others<br /> : Entity note thread can be accessed from the Task list by clicking the particular task<br /> : Task status can be changed from here or some comments added<br /> : You can also jump to the profile screen of the linked entity by clicking its name&lt;br&gt;:[[File:task_userTaskList.jpg|600px]]<br /> <br /> == COLUMN EDITOR: How can I adjust columns I see? ==<br /> <br /> : All the data visualization and download features are designed to allow users to pick and modify the columns to be used. <br /> : Use &quot;Edit columns&quot; options from the context menu of the functionality you wish to modify.<br /> : Beyond choosing the columns, the Edit functionality allows customizing names, order, color, graph type, and ranges, and reset changes to the default.<br /> : Edit columns option is available for <br /> :* metadata (device/tracking) lists<br /> :* metadata list exports<br /> :* profile data table columns<br /> :* profile graph columns<br /> :* data export columns<br /> : See the [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|Graphs section]] for some screens of column editing<br /> <br /> : Both metadata and data can be accessed via [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]] and same here the columns to be included can also be managed at the level of API query<br /> : [https://anitracking.com/api/| The detailed API specification] provides basic info about columns available.<br /> <br /> == USER PREFERENCES: How can I customize my user experience ? ==<br /> <br /> : Various features in the application are designed to remember user modifications<br /> : You can see and manage all your user preferences in the User preferences screen<br /> : The preferences listed are organized into categories <br /> : It is accessible from the user avatar in left menu or anywhere from right click context menu&lt;br&gt;[[File:user_preferences.jpg|600px]]<br /> <br /> = [[DATA_FLOWS | DATA FLOWS: How do I get the data IN/OUT?]] =<br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> : Anitra offers a range of data manipulation options on how to get data and metadata IN or OUT of the platform.<br /> <br /> : This functionality area involves features of data import, export, automated data connectors or API access<br /> <br /> : The options range from purely manual (e.g. [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|manual data exports]] or [[DATA_FLOWS#.28IN.29_Manual_data_import|data imports]]) to fully automated (e.g. [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|inbound data flows for Ornitela, Ecotone, or Movebank]]).<br /> <br /> : Some flows make sense for the particular user but most of the data management tools are meant to be configured at the level of customer/organization (hence available in customer profile)<br /> <br /> : '''Outbound data flows:'''<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Data Export]]&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_METADATA_Export|Metadata Export]]&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|API (both data and metadata)]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_to_Movebank_data_feed|Anitra to Movebank data feed]]<br /> <br /> : '''Inbound data flows:'''<br /> :* [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|Data integration of external data sources (i.e. connectors for Movebank, Ornitela, and Ecotone available)]]&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> :* [[DATA_FLOWS#.28IN.29_Manual_data_import|Data Import]]&lt;br&gt;[[File:manual_customer_import.JPG|900px]]<br /> <br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> = WARNINGS, NOTIFICATIONS=<br /> <br /> ==MORTALITY WARNINGS== <br /> [[File:DTO0000.JPG|36x37px]] Red skull<br /> * Indicates mortality detected by onboard mortality detector (Anitra tags only)<br /> * More about mortality detector in firmware configuration<br /> * The flag is stored at the level of database records (visible in data history anytime the device detected mortality)<br /> <br /> [[File:DTO000.JPG|44x38px]] Black skull<br /> : Notifies on possible mortality in the last records of trackings as estimated by server post-process analysis<br /> : Recalculated <br /> :* with new received data<br /> :* with modification of the tracking range (i.e. when closing active Tracking or when updating Tracking End Date)<br /> : The flag is recalculated and visible for the last data only (not visible in data history).<br /> : Algorithm factors in roll and pitch oscillations for the latest three records and/or the last 3 hours<br /> <br /> Red bird belly up<br /> : Unnatural body position in the very last record (roll and pitch)<br /> : whenever the absolute value of the angle for Roll or Pitch exceeds 90 degrees<br /> <br /> <br /> =={{Fa|fa-map-o}} RELEASE NOTES==<br /> <br /> : Latest release note overview is shown to the user any time a new release is deployed since the last user's Anitra access.<br /> : After being displayed the screen is no longer shown till another release<br /> : The release note screen aggregates data from the past 60 days are shown.<br /> : Release note screen can be manually invoked by pressing the Anitra icon (left top corner of the application)&lt;br&gt;[[File:ReleaseNotes_drill.jpg|900px]]<br /> <br /> =[[MORE_GUIDES| MORE GUIDES]]=<br /> <br /> : [[RK_WINTERCOUNT_TIPS| LIFE EUROKITE Red kite Wintering count (Anitra tips)]]<br /> <br /> : [[EUROKITE_PROJECT_DATASHARING| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]</div>

Admin index.php?title=Main_Page&diff=1259 2024-05-02T12:12:28Z

<p>Admin: /* MAIN CONCEPTS */</p> <hr /> <div>{{DISPLAYTITLE: Anitra Platform User Guide}}<br /> <br /> '''ABOUT'''<br /> &lt;br&gt;<br /> : Anitra platform is a flexible environment that allows storing, analyzing, and visualizing telemetry data. On top of actual telemetry data, a lot of additional metainformation and field information can be stored to document and visualize data in a very rich context. Anitra is primarily tailored to manage even very complex telemetry projects but similarly, a single user data can be comfortably maintained. <br /> <br /> : The tool allows hosting data generated by transmitters of any brand however some of the more advanced features are tailored to complement the unique onboard functionality of ANITRA GPS-GSM transmitters only. Part of the core functionality serves as a device backend for Anitra tags (a functionality for Data Owners/Admins). An elaborated sharing scheme allows granting a full range of access rights from &quot;admin&quot; to &quot;view only&quot;. Data in form of the maps can be made public in a very controlled and safe way. Most of the platform functionality is free of any charge and available to anyone having some defined access rights to particular data sets. Some data-intensive areas such as data/photo storage might be possibly restricted or charged per amount of data.<br /> <br /> <br /> = [[SIGNING_IN | SIGNING IN - How do I get into the app?]] =<br /> <br /> : Home screen of the ANITRA platform is at https://app.anitra.cz/<br /> <br /> : New users can register in the system either using &quot;Create new account link&quot; or using the &quot;SIGN IN WITH GOOGLE&quot; button ''(you will not need to type user name+pass anymore)''&lt;br&gt;[[File:sign-in_ user,pass_createNew.JPG|400px]]<br /> <br /> : Note new user can also be created by other existing users sending an invitation to the new person from access granting wizards (e.g. sharing tracking, adding admins, or assigning project access) - typing a new email address launches the invite process &lt;br&gt;[[File:user_invite_dialogue.jpg|400px]]<br /> <br /> : Once you have your account created and active you can log in either typing user name and password or using Google sign-in feature<br /> <br /> : You can review and modify your details and preferences in your user profile later.&lt;br&gt;[[File:user_profile_google_auth.JPG|900px]]<br /> <br /> : ''[[SIGNING_IN| More about User creation and user managment here]].''<br /> <br /> <br /> = MAIN CONCEPTS =<br /> &lt;br&gt;<br /> : Anitra data model is based on the following key concepts:<br /> <br /> : '''Device'''<br /> :: Device (or Tag) entity represents the physical telemetry hardware that collects particular telemetry data. Any tracking and sensor data are linked to one of the devices.<br /> <br /> :: Devices are created automatically in the system while importing a new telemetry dataset (via Import or Integration flow) or created by us in the case of Anitra devices (created as part of the device purchase process).<br /> <br /> :: Device Status attribute reflects the current usage of the devices (statuses are '''pool-new''', '''pool-used''', '''deployed-active''', '''deployed-delayed''', and '''deployed-missing'''). <br /> :: Besides, a &quot;Discard&quot; flag is available to mark the tags that are considered out of service. <br /> :: [[Main_Page#Device_Status_and_Discard_Flow |More on device statuses and discard flow here]].<br /> <br /> :: Attributes related to the hardware (brand, model, serial no., GSM no., etc.) or summary metrics can be seen and managed in the [[Main_Page#Device_profile|Device profile]].<br /> <br /> <br /> : '''Organisation, Customer, or Ownership'''<br /> :: Device &quot;Ownership&quot; defines which organization/customer holds ownership of the data.<br /> :: Purchased Anitra devices are transfered under Customer account during the purchasing process<br /> :: Non-Anitra devices are linked to particural Customer by running integration connector or Importing data manually<br /> <br /> :: Customer account also holds the credit balance (data fee prepay)<br /> <br /> <br /> : '''Animal'''<br /> :: Animal (or Individual) entity represents a particular animal/individual <br /> <br /> :: The main attributes for an Animal are its Species, Sex, and Dates when Born and Died (~ which also defines the current age e.g.).<br /> <br /> :: Additional complex meta-information can be linked-to Animal such as origin info, relationships to other animals, ringing, tagging or trapping details, and mortality attributes<br /> <br /> :: Photos (or documents) can be attached either directly to the Animal entity or indirectly to some related entities or Events such as Tagging or Mortality.<br /> <br /> <br /> : '''Tracking'''<br /> :: Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on [[TRACKING_ANIMAL|creation and modification of the tracking range]].<br /> <br /> :: The date(time) interval defines when the device was physically attached to the Animal<br /> <br /> :: ''Note when looking at the timeline of a particular Animal, multiple telemetry devices might have been used to track it subsequently (e.g. first tag failed and removed or was shed by the animal). Similarly, when analyzing Device usage history a single device might have been possibly reused several times for Tracking various animals (e.g. one animal died, the tag was recovered and reused elsewhere).''<br /> <br /> :: Besides the time aspect, some additional details such as place of tagging, place of release, tagging persons, various notes, photos, etc can be attached to Tracking Start/End. <br /> <br /> :: Tracking inherits permissions from its parent Device entity so users with device owner/admin access can create and modify the deployments as well.<br /> <br /> <br /> : '''Group''', Project, Study<br /> : '''Person''', User, Role<br /> :: Data owners can make their data available to other users or even make their data public in a simplified and secured way using an elaborated sharing scheme. Each user can act in both modes (i.e. admin for owned or administered devices and viewer for data shared with him by others). Most of the platform functionality is free of charge and available to anyone. Only large data volumes might be possibly restricted or charged. <br /> <br /> <br /> : '''Place''', Point of Interest (POI)<br /> : '''Event''', Observation<br /> <br /> <br /> : '''Device Data''', Records, Positions, Outliers<br /> :: Measurement data collected by telemetry devices. <br /> :: A combination of the device ID and UTC timestamp (date time in milliseconds) uniquely identifies each record.<br /> :: Records are linked to devices but can also be fetched for child Trackings, or Animals.<br /> <br /> :: '''Record''': a dataset related to particular UTC timestamp carrying measurements performed by particular device sensors (such as GNSS module, IMU, barometer)<br /> :: '''Position''': a record with a successful GPS fix (obtained Latitude and Longitude). Positions can be shown on maps.<br /> :: '''Outlier''': a record without GPS fix (no valid Latitude/Longitude) due to unsuccessful, skipped, or wrong GPS fixing. Note Outliers are not shown in maps but can still be displayed in table, timeline, and graph view.<br /> <br /> :: You can visualize, analyse, or download data using the Anitra platform functionality.<br /> ::: Within the platform you can see the data in [[Main_Page#MAIN_TRACKING_MAP:_Where_do_I_see_more_animals_in_one_map.3F|the main overview tracking map]] or in [[Main_Page#Device_profile|the (device or tracking) profile]] data tables, maps, timelines, and graphs<br /> ::: To analyze data outside of Anitra you can use the [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Export]] functionality or [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]].<br /> <br /> :: Note the list of columns/metrics covered by the Anitra data model can be understood from various places:<br /> ::* [[DATA_COLUMNS| a table of the most important metrics]] with explanations and comments - primarily to explain those used by Anitra tags<br /> ::* a detailed [https://anitracking.com/api/ Anitra API specification] provides a list of all the columns available over the API with a brief description<br /> ::* [[Main_Page#COLUMN_EDITOR:_How_can_I_adjust_columns_I_see.3F|column editor]] functionality lists the available columns per platform functionality.<br /> ::* the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality reference guide provides the samples/examples of files, columns, or formats to be used while importing data.<br /> ::* for additional explanations about some columns you can also refer to [https://www.movebank.org/cms/movebank-content/movebank-attribute-dictionary| Movebank attribute dictionary]. As the data from Movebank can be easily integrated in Anitra the data model and column names are ovelapping much.<br /> <br /> = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =<br /> Most entities in Anitra carry a certain list of attributes and offer a range of functions and operations related to it. The place that accommodates all this is a detail or profile page of it. <br /> <br /> Depending on the importance and complexity of a particular entity, the detail page might be rather simple (e.g. Person/User profile) or more structured and information-rich (e.g. Tracking/Animal profile). Most important entity pages are described here:<br /> <br /> =={{Fa|fa-tablet}} Device profile ==<br /> <br /> : '''Device profile''' tab (tab control marked green): <br /> :* holds all the information about the device (identification, status, type, brand, model, and user description<br /> :* allows administration of the device (i.e. managing admin list, activating Movebank Datafeed, exporting device data into the file, configuring/programming tag (cogwheel icon))<br /> :* shows device activity (i.e. bits needed for monitoring: Statistics, System of warnings (mortality, missing data), the last position in the overview map, first/last geolocation, communication log (wifi icon))<br /> :* lists Trackings/Animals created on top of device data (bottom right) - more rows in situation when single tag was redeployed multiple times &lt;br&gt;[[File:device_profile_functionality_marked.jpg|900px]]<br /> <br /> : '''Data''' tab (marked green):<br /> :* data collected by the tag visualized in the table, on the map, in the timeline, and the graph<br /> :* [[MORE_GUIDES#Tracking_range_management|functionality for creation of Trackings (aka Deployments) and modification of the DateTime ranges]].&lt;br&gt;[[File:01_create_new_tracking_here - kontext.jpg|900px]]<br /> <br /> : '''Graph''' tabs (marked green):<br /> :* data collected by the tag can be analysed in the graph<br /> :* wide range and flexible selection of columns for display<br /> :* [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|More about graphs here]]&lt;br&gt;[[File:device_profile_graph_marked.jpg|900px]]<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal profile ==<br /> <br /> * Details of tracked object (= tracking of the individual animal)<br /> ** Identification (code, name, ringing, tagging, etc.)<br /> ** Info related to particular Individual (species, sex, age, origin)<br /> ** Info related to Start of tracking (including photo and file documentation)<br /> ** Info related to End of tracking (~ mortality/device failure)<br /> * System of warnings<br /> ** Mortality indication: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt;/black warning in &quot;Last known Position&quot; row (&lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; = for deployed and currently tracking devices / black = tracking finished)<br /> ** Missing data last X days: &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; warning in &quot;Last Device Position&quot; row (warning active just for deployed and currently tracking devices)<br /> :[[File:TOP00.JPG|738x138]]<br /> <br /> * Tracked animal data visualized on the map and on the timeline &lt;br&gt;[[File:TOP01.JPG|900px]]<br /> <br /> * &quot;Share&quot; button allows sharing Tracking to other Anitra users<br /> * Possibility to attach photos /documents related to<br /> ** Tracking start<br /> ** Mortality<br /> * Same photo can be shared by various Trackings &lt;br&gt;[[File:TOP02.JPG|900px]]<br /> <br /> =={{Fa|fa-user}} Organisation/Customer profile==<br /> <br /> A section visible in the side menu (only) for users with Admin/Owner relations to Organisations listed in the system. <br /> * users not having any role in any organization do not see this menu item at all<br /> * in case the user is active in more organizations the list of these is displayed first&lt;br&gt;[[File:customer_list.JPG|900px]]<br /> <br /> Organization details such as contacts and access roles can be edited on the organization profile.<br /> * main customer admin (owner) is assigned<br /> * owner can make other people admins granting them &quot;customer admin&quot; role.<br /> * customer owner(admins) have full access to devices belonging to a particular customer/organization account (can export data, manage trackings and animals, etc.)<br /> <br /> <br /> [[DATA_FLOWS|Various inbound and outbound data flows]] from manual data export to fully automated can be managed for organization account<br /> * (IN) Inbound data flows (connectors for Movebank, Ornitela, and Ecotone available)<br /> * (IN) Manual data import (see the Import functionality)<br /> * (OUT) API data access<br /> * (OUT) Manual data export<br /> * (OUT) Anitra to Movebank datafeed<br /> <br /> Note, only the legal owners of original data are allowed to configure inbound data flows! <br /> * Any data uploaded manually or synchronized automatically to Anitra are linked to a particular legal entity (Organisation / Customer) represented by its &quot;owner&quot; i.e. person in charge.<br /> * The ownership of and the responsibility for all the data remain with this legal entity. This organization's owner and admins assigned by the owner retain full control over the data related to this entity.<br /> * Anitra works as private and secure storage and a visualization tool of these data only.<br /> <br /> Data Management section of Customer profile is also a place to define and review customer [[PUBLISHED_MAPS|published maps]] i.e. a creation wizard for maps construction.<br /> <br /> ''Note the term &quot;customer&quot; refers to any &quot;organization&quot; having some kind of (active or past) commercial agreement with Anitra company''<br /> <br /> '''Customer balance''' - i.e. usage/charging summary vs. payment history is available in the Customer profile&lt;br&gt;[[File:spending_payments_tab.jpg|900px]]<br /> <br /> : A list of the devices owned by the customer is updated and visible right before or soon after shipping devices<br /> : Fix data fee calculation is also available instantly<br /> : Overage data charges are updated according to reality after the month is over and the detailed billing summary is available from the mobile network<br /> : Payments (from invoices paid) are visible after the data fee payment is received by us<br /> <br /> = LISTS, GRIDS=<br /> <br /> =={{Fa|fa-tablet}} Device list==<br /> : List of owned or administered devices (= hardware) - accessible only to owners/admins (users with shared data do not have the rights to see this area)<br /> : Click through to device details (profile), sort by the column, browsed by pages, first column freezing, quick system, and user filters<br /> : [[Main_Page#FILTERS_.26_SEARCHES:_How_do_I_find_what_I_am_looking_for_.3F|Search and Filter functionality]]: allows filtering your devices by criteria<br /> : Manageable through Filter manager next to the Search box, marked with icon [[File:C2.JPG|30px]] <br /> :* Predefined quick filters, which cannot be modified (Missing data in the last 7+ days, Anitra devices only, Powered off devices, Wrong tracking configuration, Deployed devices, Mortality indication)<br /> :* You can turn on multiple Quick filters at once in the Quick filter panel<br /> : Context menu - as anywhere in Anitra the right-click mouse context menu offers the most relevant actions for the current context, functionality, or the whole page or a user<br /> : A wide range of columns available. Column selection and more column-related actions using Column manager from the context menu or directly e.g. by drag-drop columns:<br /> :* Column selection, adding, removing columns (a default list can be restored using &quot;reset visibility&quot;)<br /> :* Column renames (default names can be restored using &quot;reset display names&quot;)<br /> :* Column order (a default order can be restored using &quot;reset order&quot;)<br /> : Multi-select for bulk operations (open all in tabs, graph, apply config preset, etc)<br /> : System of warning messages such as Mortality indication: &quot;Device Status&quot; colored in red and followed by {{red|red skull}} symbol or Missing data last X days: &quot;Last Device Position&quot; followed by red question mark {{red|&quot;?&quot;}}.<br /> <br /> =={{Fa|fa-paw}} Tracking &amp; Animal list ==<br /> <br /> * List of owned Trackings (tab &quot;my trackings&quot;)<br /> * List of Trackings shared with me (tab &quot;shared with me&quot;)<br /> * Overview of all Trackings including first and last data<br /> ** Click through to Tracking detail/profile<br /> ** System of warnings<br /> ** Mortality indication: &quot;Tracking&quot; followed by &lt;span style=&quot;color:red&quot;&gt;red&lt;/span&gt; &lt;span style=&quot;color:red&quot;&gt;skull&lt;/span&gt; symbol<br /> ** Missing data last X days: &quot;Last Data &quot; followed by red question mark &lt;span style=&quot;color:red&quot;&gt;&quot;?&quot;&lt;/span&gt;. Mouse-over symbol tells the last data delay.<br /> <br /> = MAPS =<br /> <br /> : Common map properties and controls<br /> : 1) '''Map zoom''' <br /> :: ''Note besides the zoom buttons you can zoom the map''<br /> ::* ''using the mouse scroll wheel'' <br /> ::* ''or by double-clicking the left mouse button (to zoom in) and the right button (to zoom out)''<br /> <br /> : 2) '''Full-screen''' mode<br /> <br /> : 3) Shows the user/device's '''current position''' on the map as a blue dot <br /> <br /> : 4) '''GPS search''' tool - various GPS formats accepted (e.g. decimal degrees such as &quot;52.7761 27.811889&quot;)<br /> <br /> : 5) '''Background maps''' <br /> :* a wide range of background maps of various types<br /> :* transparent overlays (country and admin borders)<br /> <br /> : 6) '''Transparent map overlays''' <br /> :* country borders <br /> :* admin leve1 1 borders<br /> <br /> : 7) '''Map options''' <br /> :* '''Tracks''' - note the option &quot;'''Clustered'''&quot; simplifies the track by removing movements within clusters<br /> :* '''Waypoints''' - note the option &quot;'''All'''&quot; suppresses the default performance optimisation behavior (= option &quot;'''Filtered'''&quot;) - i.e. enforces showing of all the waypoints<br /> :* '''Annotations''' (aka '''Clusters''') - currently these two Annotatin/Cluster types availabe to be used<br /> :** '''Last positions''' - show/hide the last position of the tracking<br /> :** '''Sleep clusters''' - show/hide the sleep clusters (data from periods defined by solar night/day i.e. by sun angle)&lt;br&gt;[[File:map04_mapFunctionality.JPG|900px]]<br /> <br /> : 8) '''Copy coordinates to clipboard''' <br /> :: using left click context menu<br /> <br /> : 9) '''Measure distance''' <br /> :: using left click context menu&lt;br&gt;[[File:map04_mapFunctionality_2.JPG|600px]]<br /> <br /> <br /> =={{Fa|fa-map-o}} MAIN TRACKING MAP: Where do I see more animals in one map? ==<br /> <br /> : A tool to analyze multiple Trackings / Individuals in a single map.<br /> : The functionality displays all the Tracked Individuals available to a user (both owned/administered and shared only) <br /> : The start view shows an overview of the last positions - the color of the point classifies the last positions by the last update. &lt;br&gt;[[File:map01_lastdatacolors.JPG|900px]]<br /> <br /> : '''Filtering functionality below the map''' limits the data in the map (and in the right Tracking list panel]<br /> :: The three quick filter conditions (&quot;Search&quot;, &quot;Tracking filters&quot;, &quot;Species&quot;) directly filter matching/not matching Trackings/Animals<br /> ::* &quot;Search&quot;: a full-text search across Device/Tracking/Animal codes/names/aliases<br /> ::* &quot;Tracking filters&quot;: existing Tracking filters created by the user can be reused here in the map. This allows applying very complex filter conditions in the map<br /> ::* &quot;Species&quot;: an obvious and simple quick filter conditions<br /> :: Note that the &quot;Days filter&quot; works differently - it uses a time filter over telemetry data first and based on that it leaves or removes Trackings/Animals from the page<br /> ::* it excludes all the trackings with data outside of the time interval<br /> ::* for overlapping Trackings/Animals it limits data/tracks in the map according to the interval defined - i.e. only relevant parts of the tracks are loaded&lt;br&gt;[[File:map02_mapfilterfilled.JPG|900px]]<br /> :: Also note the map filter is stored in the URL (browser address bar). You can open another browser tab with a map page and configure a different filter (eg. another species). Both tabs then work independently.<br /> <br /> : '''Choosing Trackings / Animals to be loaded''' in the map.<br /> :* using tooltips of single last points <br /> :* or for multiple items using the rectangle tool selection in the map (using CTRL + click/drag with left mouse button)<br /> :* selecting/unselcting particular items in the right Tracking pannel (single Trackings or all grouped by species)&lt;br&gt;[[File:map03_TOselection.JPG|900px]]<br /> <br /> : '''Waypoints and Last positions (tooltips)'''<br /> :* More tooltips can be displayed simultaneously<br /> :* Click through the link to a particular Tracked Object profile&lt;br&gt;[[File:map05_TOdetails.JPG|900px]]<br /> :* Warnings and statuses are shown in tooltips e.g. mortality being indicated by black/red symbols &lt;br&gt;[[File:map06_mortalityInMap.JPG|900px]]<br /> <br /> == [[PUBLISHED_MAPS|PUBLISHED MAPS: How do I show an overview of our study results to the public?]]==<br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> : A tool tailored to configure simplified and secured live telemetry maps from your full data sets.<br /> <br /> : Configured maps are available in form of a link or in form of short HTML code which can be simply added to your web presentation or published on Facebook.<br /> <br /> : Map output can be created:<br /> :* on top of single organization data <br /> :* on top of &quot;project&quot; (i.e. accross more complex data ownership structure)<br /> <br /> : Map editor with a live preview is used to configure the map&lt;br&gt;[[File:publish_map_configuration_groups.JPG|900px]]<br /> <br /> : Two map modes can be configured:<br /> :* map showing the simplified '''Tracks''' <br /> :* map showing the '''Last positions''' only<br /> <br /> : For the mode of &quot;Tracks&quot; '''Animation''' can be anabled<br /> <br /> : The map configuration includes:<br /> :* animal selection<br /> :* language localisations (alternative language variants)<br /> :* map mode (tracks vs. last position), grouping options, ordering, data filtering (e.g. track simplified to one position a day)<br /> :* security features (security delay, zoom restriction, position &quot;rounding&quot;)<br /> :* presentation and visualization presets (a default map selection, icon/track styles, choice of icons, logos with links, foto gallery, animation enabling)<br /> <br /> : Samples showing some of the map features<br /> :* map with tracks and gallery and animation anabled:https://app.anitra.cz/share/map/5d2e379ed6f9c &lt;br&gt;[[File:publish_map_animationEnabled.jpg|900px]]<br /> :* map of last positions with categories: https://app.anitra.cz/share/map/5f1a97bb13ba5<br /> <br /> ''[[PUBLISHED_MAPS|A detailed guide to to Published maps functionality is available here]].''<br /> <br /> = GRAPHS: How to visualize important data relations in graphs? =<br /> <br /> : Graph functionality available<br /> :* as a tab in Device and Tracking profiles (see #0)<br /> :* for a group of Devices (only admin functionality now).<br /> <br /> : Time is indicated by the horizontal axis (see #1)<br /> : By default period of the last 7 data days is loaded.<br /> : The interval shown can be managed either by the interval slider (see #2) or using the date input below the chart area (see #3).&lt;br&gt;[[File:graph_time.jpg|600px]]<br /> <br /> : You can hover over the chart to preview the actual values (see #4).<br /> : The values of metrics are plotted at the vertical axis of the graph (see #5).<br /> : The scale for a particular metric is shown on the left and right from the graph area (see #6).<br /> : To quickly show/hide a particular metric click the label color above the graph (only used till the next page reload)(see #7).&lt;br&gt;[[File:graph_orientation.jpg|600px]]<br /> <br /> : You can customize your metric list (visibility) and order using the &quot;Choose metrics&quot; button below the chart (see #8).<br /> : Visibility (see #9) and order (see #10) is controlled by drag'n'drop action.&lt;br&gt;[[File:graph_choseMetrics.jpg|600px]]<br /> <br /> : Visibility and order can also be managed in &quot;Edit graph columns&quot; from the context menu (see #11). <br /> : Additionally, this functionality offers even more properties to be controlled such as custom rename (see #12) or colors, graph type, and default value range (see #13). <br /> : It also allows resetting the changes to system defaults (reset options in the top right corner)(see #14)&lt;br&gt;[[File:graph_editColumns.jpg|600px]]<br /> <br /> ={{Fa|fa-photo}}PHOTO GALLERY: Where do I browse all the photos? =<br /> <br /> * Displays a complete gallery of pictures from all the Trackings (own and shared)<br /> * Filtering by main attributes &lt;br&gt;[[File:TO.JPG|900px]]<br /> <br /> = {{Fa|fa-cog}} MANAGING and CONFIGURING of Anitra Tags =<br /> <br /> == Device Status and Discard Flow ==<br /> <br /> : '''Device Status''' attribute is automatically assigned based on device usage history (including its past and current deployments)<br /> :: ''E.g. the tags are automatically moved from Pool to Deployed statuses by creating Tracking (+Animal) object. [[TRACKING_ANIMAL| Check the detailed guide here.]]''<br /> <br /> :: ''pool-new'' : devices never deployed previously<br /> :: ''pool-used'': devices returned to the device pool after deployment<br /> :: ''deployed-active'': deployed on animals, known to have delivered fresh data within the last 3 days<br /> :: ''deployed-delayed'': deployed on animals, known to have delivered fresh data within the last 4-7 days<br /> :: ''deployed-missing'': last data older than 7 days<br /> <br /> :: ''Note Devices status applies to all the devices types including data imported from Movebank of from Import flow.''<br /> <br /> : '''Device/SIM Discard Flow''' (for Anitra devices) <br /> :: Device/SIM closing(discard/termination) workflow is available for Anitra device owners so the SIM can be closed and the device removed from (data fees) billing<br /> :: Users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.<br /> :: Marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider <br /> :: SIM is ultimately terminated by the end of the month following after marking the device to be discarded ''(e.g for a device marked to be discarded on the 13th of February the SIM will be active (and data fees charged till the end of the March))''<br /> :: Note you can still stop the discard process till the SIM is irreversibly terminated by the network operator by contacting us directly till the end of the following month (i.e. for the example above we can manually withdraw the SIM closing request till the 31st of March)<br /> :: The check for marking devices to be terminated is available at the bottom part of the device profile.<br /> <br /> : Device Discard/Archive flow for non-Anitra devices<br /> :: For non-Anitra devices (= devices originating from import or integration - i.e. Movebank, Ornitela, Ecotone, Manual Import) there is also a Discard/Archive mark present in the Device profile <br /> :: For those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)<br /> :: A recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel <br /> :: Note in this case the flag is fully reversible (the user can change it there and back without any restriction)<br /> <br /> : '''Device Status Extended/Long''' <br /> :: Extended/long devices status is summarizing all the status information related.<br /> :: It is a combined field of Device status, history summary and Discard status.<br /> :: It is displayed in the Device profile, Device list, and Customer balance overview<br /> <br /> == Configuration /programming of devices == <br /> <br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> &lt;br&gt;<br /> : Users with admin rights can access the configuration from the lists and profiles using cogwheel icons. Note the configuration functionality is available for Anitra devices only.<br /> :[[File:config_lists_profiles.JPG|900px]]<br /> &lt;br&gt;<br /> : Configuration contains three main areas<br /> :* Data collection settings<br /> :** GPS/sensor sampling time schedules<br /> :** Data collection triggered by events<br /> :** Configuration of bursting behavior<br /> :** Mortality detection adjustment<br /> :** Geofencing<br /> :* Communication schedules<br /> :* Other settings<br /> :[[File:config_sections.JPG|900px]]<br /> : ''For complete detail of all the configuration options see the configuration guide [[configuration| to the latest firmware version ]] or to [[configuration_fw2| older versions respectively]].''<br /> <br /> = OTHER PRODUCTIVITY TOOLS =<br /> == FILTERS &amp; SEARCHES: How do I find what I am looking for ? ==<br /> <br /> Various features helping user find and filter down what is needed are available in Anitra:<br /> <br /> # '''Global full text search'''&lt;br&gt;- full text seach accross all the objects of various types which user has access rights to.&lt;br&gt;- a list of relevant item s sorted by relevancy is returned&lt;br&gt;[[File:global_full_text_search.JPG|500px]]<br /> # '''Grid search'''&lt;br&gt;- seaches in important fields in displayed grid only&lt;br&gt;[[File:grid_search.JPG|500px]] <br /> # '''System and Custom &quot;Quick&quot; filters'''&lt;br&gt;- allows quickly filter data using predefined &quot;system&quot; or &quot;user defined&quot; filters&lt;br&gt;- filters are available as icons on top of the device or tracking grid header line&lt;br&gt;- custom filters can be created in &quot;Filter manager&quot;&lt;br&gt;[[File:quick_filters.JPG|900px]] <br /> # '''Published map filters'''<br /> <br /> * Filter manager <br /> ** Customized quick filters that filter devices according to specified criteria (e.g. Device list, Name fields, Device notes..), you can set multiple criteria at once &lt;br&gt;:[[File:B.JPG|900px]] <br /> ** You can save your customized filter with the green &quot;check&quot; icon &lt;br&gt;:[[File:Ml.JPG|900px]] <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:Mil.JPG|900px]] <br /> <br /> * Filter functionality: allows filtering your trackings by criteria <br /> ** Predefined quick filters, which cannot be modified (Mortality Warning, Last data warning only, Anitra devices only)<br /> ** Customized quick filters, which filter Trackings by set criteria (e.g. Tracked Objects, Name fields, Note fields..), you can set multiple criteria at once <br /> ** You can save your customized filter with the green &quot;check&quot; icon <br /> ** &quot;Eye&quot; icon enables to pin the particular Quick filter into the Quick filter panel next to the Search box &lt;br&gt;:[[File:ksdjf.JPG|900px]] <br /> ** You can turn on multiple Quick filters at once in the Quick filter panel<br /> <br /> == NOTES: Where to note down info about particular things? ==<br /> : A handy feature helping users to get organized and stay organized with their data.&lt;br&gt;:[[File:note_thread_narrow.JPG|600px]]<br /> <br /> : Available for multiple entities (Devices, Trackings, Animals, and Customers/Organizations)<br /> <br /> : Note threads can be accessed <br /> :* from entity profiles - in the green shown opening of the Tracking note, the blue mark on the right shows the place to access the device note &lt;br&gt;[[File:note_from_profile.JPG|900px]]<br /> :* entity lists or using the context menu - either click on the note icon in the Notes column or use the context menu over the desired row&lt;br&gt;[[File:note_from_listContext.JPG|900px]]<br /> :* from user Task List &lt;br&gt;[[File:task_userTaskList.jpg|700px]]<br /> : Here a new note can be created, existing notes can be edited, or a reply to previous notes can be posted.<br /> : The thread window is flowing over the entity. It can be open parallel to whatever you do in your profile. You can switch tabs, type forms, take screenshots while browsing, or even create/edit notes. <br /> <br /> : Create the note simply by typing in the form<br /> : Edit existing notes by double-clicking them or using &quot;more&quot; or &quot;Edit&quot; icons in the right top corner. This switches note into &quot;'''edit'''&quot; mode&lt;br&gt;<br /> :[[File:note_editMode.JPG|500px]]<br /> : Save the new or edited note by clicking the &quot;Publish/Done&quot; button or simply hitting ENTER.<br /> : While creating or editing you can cancel by the &quot;Cancel&quot; button or using ESC on your keyboard<br /> : The note text does not allow formatting but you can structure the note to more rows. Use SHIFT+ENTER for the new line (as ENTER is reserved for the &quot;Save&quot; operation)<br /> : An existing note can be deleted using the &quot;more&quot; button &gt;&gt; &quot;Delete thread&quot;. Note while deleting the parent note all the replies will also be deleted.<br /> : &quot;Clone note&quot; function - particularly useful e.g. for fast duplicating of notes with complex definitions (i.e. notes linked to many items). <br /> :: ''While cloning notes attachments are removed (not cloned with the note).''&lt;br&gt;:[[File:note_deleteClone_thread.JPG|500px]]<br /> : Use &quot;Promote to parent note&quot; when you need to convert a note reply to a top-level parent note. <br /> :: ''While promoting reply to note it inherits the relations from its original parent note''<br /> : Use &quot;drag'n'drop: action to move one note into the reply area of the other note to move and transform the note into the reply. <br /> :: ''Converting note into reply is only possible for notes created by the user himself and only to notes that have no complex relationship''<br /> <br /> : By default the note thread is<br /> :* sorted starting with newest notes up. You can invert the sort order to have the oldest notes on top of the page. This setting is remembered in your user preferences.<br /> :* positioned on the top right side of the page. You can modify the position by dragging the floating window to any side, This setting is remembered in your user preferences.<br /> :* sized to one-third of the screen width. You can switch the window size between one-third and one-half by the &quot;shrinking/stretching&quot; button. This setting is also remembered in your user preferences.&lt;br&gt;:[[File:note_sortSizePosition.JPG|600px]]<br /> <br /> : Notes can be saved as<br /> :* shared - will be visible to all the users with access to the entity. a way to share knowledge, tasks, and the status of particular items<br /> :* private - will be visible only to the author of the note. a way to note down things or ToDos only for the author&lt;br&gt;:[[File:note_sharedPrivate.JPG|600px]]<br /> <br /> : The functionality contains a complex toolkit covering&lt;br&gt;:[[File:note_functionality_options.JPG|900px]]<br /> :* relations - a single note (thread) can be linked to multiple items of the same type (e.g. a single/shared note linked to 5 devices)<br /> :* attachments<br /> :** To each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)<br /> :** Picture attachments are then previewed in the thread, photos can be opened in full size and browsed as a gallery<br /> :* screenshots<br /> :** For adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body. <br /> :** This will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.<br /> :* links/URL<br /> :* tags - you can label your notes by using user &quot;tags&quot;, later you can search, filter, or group by these tags<br /> <br /> == TASKS (TODOS): Where to note down reminders and ToDos ? ==<br /> <br /> : Extension of the Notes functionality<br /> : By assigning a note to someone (to ''another user'', to ''user himself'' or to ''anyone'') the note is transformed into the Task (ToDo)<br /> <br /> : Use the button below the note editor or simply type @+name to assign the note as a task to someone&lt;br&gt;[[File:task_assignment.jpg|600px]]<br /> :* assigning a task to another person (''@other.person'') will list the task in the other person's Task list (as created by you).<br /> :* assigning a task to yourself (''@your.name'') will list the task in your Task list (as created by yourself).<br /> :* assigning a task to anyone (''@anyone'') will create a shared task displayed to all the people with access to the linked entity (e.g. particular device, tracking, or customer)<br /> <br /> : A simple workflow for tasks exists - the task can be in one of the three states<br /> :* new/open (= to be completed, highlighted by yellow background)<br /> :* completed /done (= marked as completed, highlighted by a green background)<br /> :* canceled / rejected (highlighted by a reddish background)&lt;br&gt;[[File:task_statusColors.jpg|600px]]<br /> <br /> : Users can move the tasks between the states using icons and controls in the right corner&lt;br&gt;:[[File:task_statusChange.jpg|600px]]<br /> <br /> : User Task board screen shows all the ToDos assigned to the user or defined by the user to others<br /> : Entity note thread can be accessed from the Task list by clicking the particular task<br /> : Task status can be changed from here or some comments added<br /> : You can also jump to the profile screen of the linked entity by clicking its name&lt;br&gt;:[[File:task_userTaskList.jpg|600px]]<br /> <br /> == COLUMN EDITOR: How can I adjust columns I see? ==<br /> <br /> : All the data visualization and download features are designed to allow users to pick and modify the columns to be used. <br /> : Use &quot;Edit columns&quot; options from the context menu of the functionality you wish to modify.<br /> : Beyond choosing the columns, the Edit functionality allows customizing names, order, color, graph type, and ranges, and reset changes to the default.<br /> : Edit columns option is available for <br /> :* metadata (device/tracking) lists<br /> :* metadata list exports<br /> :* profile data table columns<br /> :* profile graph columns<br /> :* data export columns<br /> : See the [[Main_Page#GRAPHS:_How_to_visualize_important_data_relations_in_graphs.3F|Graphs section]] for some screens of column editing<br /> <br /> : Both metadata and data can be accessed via [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|Anitra API]] and same here the columns to be included can also be managed at the level of API query<br /> : [https://anitracking.com/api/| The detailed API specification] provides basic info about columns available.<br /> <br /> == USER PREFERENCES: How can I customize my user experience ? ==<br /> <br /> : Various features in the application are designed to remember user modifications<br /> : You can see and manage all your user preferences in the User preferences screen<br /> : The preferences listed are organized into categories <br /> : It is accessible from the user avatar in left menu or anywhere from right click context menu&lt;br&gt;[[File:user_preferences.jpg|600px]]<br /> <br /> = [[DATA_FLOWS | DATA FLOWS: How do I get the data IN/OUT?]] =<br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> : Anitra offers a range of data manipulation options on how to get data and metadata IN or OUT of the platform.<br /> <br /> : This functionality area involves features of data import, export, automated data connectors or API access<br /> <br /> : The options range from purely manual (e.g. [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|manual data exports]] or [[DATA_FLOWS#.28IN.29_Manual_data_import|data imports]]) to fully automated (e.g. [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|inbound data flows for Ornitela, Ecotone, or Movebank]]).<br /> <br /> : Some flows make sense for the particular user but most of the data management tools are meant to be configured at the level of customer/organization (hence available in customer profile)<br /> <br /> : '''Outbound data flows:'''<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_DATA_Export|Data Export]]&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Manual_METADATA_Export|Metadata Export]]&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_API_data_.26_metadata_access|API (both data and metadata)]]<br /> :* [[DATA_FLOWS#.28OUT.29_Anitra_to_Movebank_data_feed|Anitra to Movebank data feed]]<br /> <br /> : '''Inbound data flows:'''<br /> :* [[DATA_FLOWS#.28IN.29_Inbound_DATA_flows|Data integration of external data sources (i.e. connectors for Movebank, Ornitela, and Ecotone available)]]&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> :* [[DATA_FLOWS#.28IN.29_Manual_data_import|Data Import]]&lt;br&gt;[[File:manual_customer_import.JPG|900px]]<br /> <br /> ''[[DATA_FLOWS|A detailed guide to to all the data flows here]].''<br /> <br /> = WARNINGS, NOTIFICATIONS=<br /> <br /> ==MORTALITY WARNINGS== <br /> [[File:DTO0000.JPG|36x37px]] Red skull<br /> * Indicates mortality detected by onboard mortality detector (Anitra tags only)<br /> * More about mortality detector in firmware configuration<br /> * The flag is stored at the level of database records (visible in data history anytime the device detected mortality)<br /> <br /> [[File:DTO000.JPG|44x38px]] Black skull<br /> : Notifies on possible mortality in the last records of trackings as estimated by server post-process analysis<br /> : Recalculated <br /> :* with new received data<br /> :* with modification of the tracking range (i.e. when closing active Tracking or when updating Tracking End Date)<br /> : The flag is recalculated and visible for the last data only (not visible in data history).<br /> : Algorithm factors in roll and pitch oscillations for the latest three records and/or the last 3 hours<br /> <br /> Red bird belly up<br /> : Unnatural body position in the very last record (roll and pitch)<br /> : whenever the absolute value of the angle for Roll or Pitch exceeds 90 degrees<br /> <br /> <br /> =={{Fa|fa-map-o}} RELEASE NOTES==<br /> <br /> : Latest release note overview is shown to the user any time a new release is deployed since the last user's Anitra access.<br /> : After being displayed the screen is no longer shown till another release<br /> : The release note screen aggregates data from the past 60 days are shown.<br /> : Release note screen can be manually invoked by pressing the Anitra icon (left top corner of the application)&lt;br&gt;[[File:ReleaseNotes_drill.jpg|900px]]<br /> <br /> =[[MORE_GUIDES| MORE GUIDES]]=<br /> <br /> : [[RK_WINTERCOUNT_TIPS| LIFE EUROKITE Red kite Wintering count (Anitra tips)]]<br /> <br /> : [[EUROKITE_PROJECT_DATASHARING| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]</div>

Admin index.php?title=Release_notes/2024-04-22&diff=1258 2024-04-24T11:25:01Z

<p>Admin: </p> <hr /> <div>{{Release note|New IMPORT functionality (final version)|new}} <br /> {{Release note body start}} <br /> * Workflow reviewed and finalized<br /> * Return info and warning messages finalized<br /> * Cancel button behavior adjusted<br /> * Data validation logic extended (insert, update, skip options elaborated)<br /> * More error situations handled<br /> * Missing progress bars for remaining import stages added<br /> [https://support.anitracking.com/index.php?title=DATA_FLOWS#.28IN.29_Manual_data_import ''Plase check the updated section of the user guide'']<br /> {{Release note body end}}<br /> <br /> {{Release note|Various improvements|improvement}} <br /> {{Release note body start}}<br /> * Tracking/Animal management improved<br /> ** Tracking/Animal entities identification in projects modified<br /> ** Animal created by info added for existing animals<br /> ** Create tracking here fixed for some instances <br /> ** Last record geolocation updating when modifying tracking end fixed<br /> * Note/ToDos more functionality added<br /> ** Transform/move a note into the reply<br /> ** Fix tracking name display in notes<br /> ** File attaching into note draft note fixed<br /> ** Time format fixed when creating a new bulk note<br /> {{Release note body end}}<br /> <br /> {{Release note|Various fixes|bugfix}}<br /> {{Release note body start}}<br /> * Tracking and device grid<br /> ** Broken grid header in some situations fixed<br /> ** Country code display in tracking grid adjusted<br /> ** Redundant grid refreshing when changing unrelated column mappings removed<br /> ** Device and tracking list XLSX export fixed<br /> * Device and SIM discard flow post-release adjustments<br /> * Copy filter functionality fixed<br /> * Waypoints all option fixed<br /> * Percentage values in XLS exports fixed<br /> * API issues fixed<br /> ** Fix API declaration typos<br /> ** Fix API scroll requests not working with both body and request parameters<br /> ** Fix API column filtering<br /> {{Release note body end}}<br /> <br /> {{DEFAULTSORT:1-24}}<br /> {{DISPLAYTITLE:2023-04-22}}<br /> [[Category:2023 Release notes]]</div>

Admin index.php?title=DATA_FLOWS&diff=1257 2024-04-24T11:23:00Z

<p>Admin: /* {{Fa|fa-upload}} (IN) Manual data import */</p> <hr /> <div>{{DISPLAYTITLE: DATA MANAGEMENT}}<br /> <br /> = (IN) Inbound DATA flows= <br /> :A possibility of plugging to external telemetry data sources and having them fed into Anitra<br /> :: ''Note the devices imported from the data source are imported to your profile and listed in the device list. A unified metadata structure can be then created on top of the imported data (Device - :Tracking - Animal). Ultimately data from various sources can be browsed and visualized side by side in a unified metadata-rich structure'' <br /> <br /> :Connectors for the following data sources currently exist:<br /> :* Movebank<br /> :* Ecotone<br /> :* Ornitela<br /> <br /> : Inbound connections are managed in the &quot;Integrations In&quot; section of [[Main_Page#Organisation.2FCustomer_profile |Customer profile]]. &lt;br&gt;[[File:Customer_Profile_Inbound.jpg|900px]]<br /> <br /> : The overview of existing connections allows adding, editing/removal and running/scheduling the connection<br /> <br /> : Use the &quot;+create new&quot; button to launch the connector creation wizard and enter the information required for running the feed&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> <br /> : Note each of the connectors works differently and hence also the information needed for running the data flow and scheduling the run slightly differs.<br /> <br /> == Ecotone ==<br /> : Details needed: Ecotone panel name (=URL of CSV files storage), user name, and password<br /> : User can manage this connector fully i.e. create, edit, run (once or schedule regular run), and delete&lt;br&gt;[[File:Ecotone2Anitra_setup_wizard.JPG|400px]]<br /> <br /> == Ornitela ==<br /> : Details needed: Ornitela user name and password <br /> : Ornitela integration is realised using &quot;Ornitela SFTP&quot; functionality. <br /> :* i.e. in this case user creates, edits the data connector, and requests activation (or requests deactivation) of the data flow<br /> :* by requesting activation user also requests to have the SFTP configuration in his Ornitela pannel configured by us. &lt;br&gt;[[File:Ornitela2Anitra_setup_wizard.JPG|400px]]<br /> : Note other related aspects using SFTP:<br /> :* only new data are integrated once the data flow is activated. <br /> :* for importing older data (records created before the feed activation) use the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality (any duplicate records are merged or skipped so you can import the same period repeatedly). <br /> :* only the devices marked for SFTP export in the Ornitela panel will be automatically updated into Anitra<br /> :* make sure you also update the connector definition anytime you are changing your Ornitela user password <br /> :* also bear in mind that modifying the list of devices marked for SFTP (unchecking and checking again) will result in the data flow interruption and thus to some possible gaps in the data.<br /> <br /> == Movebank to Anitra ==<br /> : Configuring this connector a Movebank data (+ Movebank metadata) are connected <br /> : Movebank API is employed for accessing the records<br /> : In this case user is supposed to enter a movebank username and password in combination with Movebank Study ID and request the data flow activation &lt;br&gt;[[File:Movebank2Anitra_setup_wizard.JPG|400px]]<br /> <br /> = {{Fa|fa-upload}} (IN) Manual data import= <br /> <br /> : Data Import dialog can be accessed in the Data management section of your Customer/Organization profile.<br /> : Imported data are merged under the Customer/Organisation account (new devices added or data appended to existing devices).<br /> <br /> : Import flow starts by browsing a file (or multiple files).&lt;br&gt;[[File:customer_import_01_file_selection.jpg|900px]]<br /> <br /> : An import wizard in a separate browser tab is open and automated file preprocessing (checking file type, header/columns, and actual data in the file) is run. <br /> : Messages about the progress of file checking are displayed. <br /> : In case any errors preventing the file from being imported occur the actual import (last step of the flow) is not triggered. <br /> : In case the file passes the checks successfully (no blocking errors detected) user will confirm the import by submitting it into the database import queue in the last step of the wizard. &lt;br&gt;[[File:customer_import_02_import_wizard.jpg|900px]]<br /> <br /> : '''1) Aquiring file'''<br /> :: File is downloaded into working space of the import procedure. This step also confirms the import service is actually ready to process your file.<br /> <br /> : '''2) File format and structure checking'''<br /> :: CSV files only are accepted currently. <br /> :: The CSV is supposed to be well structured i.e.:<br /> ::* Columns to be delimitted by a valid column separators (TAB, comma or semi-colon)<br /> ::* UTF-8 data encoding to be used etc<br /> :: First row must contain column list<br /> :: column names must be unique and not empty<br /> :: Wrong files will display errors and would not be imported. <br /> <br /> : '''3) Detect import file format'''<br /> :: Import dialog now accepts data in several formats/structures <br /> :: The format is automatically detected from the first file row (column header).<br /> :: To pass this step successfully the column list must match one of the accepted formats i.e the mandatory columns (such as device identification, datetime, or latitude and longitude) per format to be supplied and matching<br /> :: Missing columns (or column names not matching) related to optional data result in having these columns skipped and not imported. <br /> <br /> :: The following formats/structures/templates are now accepted:<br /> :: '''Basic''' - Anitra general import structure designed for importing custom (any) data <br /> ::: Data mapped directly to Anitra database column names<br /> ::: Check our guidelines and sample files while preparing your import files<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EW3wvkVaaFlMjlp9yFMEgT4BFu_8rAWtlCh2nOUuVrfmkQ?e=XenvK8| guideline file] - explains mandatory columns, lists correct column names and data types to be used, and gives some example values<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EQhkt8fmgPVDjUak8IhbxPkBceKv7jXoiF2dhp6gcJ0lMg?e=GeAxvj| template CSV file] - This is how your files should be structured. Note the file contains a header row and several sample/test rows. <br /> <br /> :: '''Movebank''' data (to be imported via Basic format currently)<br /> <br /> :: For importing data in the original CSV file structure and format generated by some other tag producers (fixed custom mapping of original files to Anitra database) these import formats are also implemented.<br /> :: '''Ecotone''' <br /> ::: Devices created using Ecotone import format are automatically labeled as device type &quot;Ecotone&quot; in Anitra (same as if these were created via Ecotone integration - see automatic integration section)<br /> :: '''Ornitela''' <br /> ::: Ornitela import currently accepts multiple versions of the Ornitela CSV file (versions 1 and 2, GPS, GPS+SENSORS, etc). Note the &quot;SENSORS&quot; rows are skipped and not imported.<br /> ::: Devices created using Ornitela import format are automatically labeled as device type &quot;Ornitela&quot; in Anitra (same as if these were created via Ornitela integration - see automatic integration section)<br /> <br /> :: Flows using native file formats can be useful when uploading older data files not available anymore to automated integration flow e.g. older records after having activated Ornitela SFTP data flow (which only generates new records).<br /> <br /> : '''4) Validate data'''<br /> :: Once the import file is successfully matched a data-checking phase follows (i.e. rows are checked) <br /> <br /> :: Data validation step checks the values against datatypes expected in target columns (e.g. wrong date time format, string data too long, text data in numeric columns, or similar datatype conflicts, etc)<br /> :: The rows/cells with problem data are detected and problems are shown.<br /> :: ''Note the past option of skipping the error rows processing only non-error data not currently implemented. I.e any data error in the file prevents the whole file from being imported.''&lt;br&gt;[[File:customer_import_03b_import_wizard_data_err.jpg|900px]]<br /> <br /> :: The second major task of the validation phase is to check the previous existence of the rows in the database. <br /> :: Rows matching existing records are prepared to be possibly '''updated'''.<br /> :: Rows not matching existing records are prepared to be '''inserted'''.<br /> :: Additionally, special purpose rows are removed from the file (e.g. not processed sensor rows in Ornitela files)<br /> <br /> :: Note the import procedure performs append and merge data operations (Also note no data delete occurs).<br /> ::: For any new device (device_code) detected in the file a new Device will be created in Anitra and all the imported rows linked to it.<br /> ::: For devices matching existing Anitra devices the data from the file will be merged (rows inserted or updated using data timestamp). Note a possible data loss by overwriting existing data (the same combination of device and date time already exists in the database).<br /> <br /> :: In case no data errors are detected user can decide if new rows should be inserted and/or existing data should be updated.<br /> :: Hitting the Import button submits the task to the server queue for processing.&lt;br&gt;[[File:customer_import_03c_import_wizard_data_ok.jpg|700px]]<br /> <br /> : After the import is done a summary is provided.<br /> <br /> : Note you can import simultaneously more files in one import session. Each of the files runs independently through its 5-step import flow.<br /> : As the import of large files can last many minutes or even hours (depending on server overload), you can close the browser tab (or even your computer) any time during the import. In case you need to return to the import screen use the &quot;Running imports&quot; list in the customer profile to reopen the session again&lt;br&gt;[[File:customer_import_04_running_imports.jpg|900px]]<br /> <br /> : [[IMPORT_OLD| Manual import functionality - old version (before 2024)]]<br /> <br /> = (OUT) Anitra API data &amp; metadata access =<br /> :* allows grabbing Anitra DATA and METADATA from external tools such as from GIS systems API interface <br /> :* curent version of API offers access to the following items:<br /> :** Device List (=Device metadata)<br /> :** Device Data<br /> :** Tracking List (=Tracking and Animal metadata)<br /> :** Tracking Data<br /> :* for detailed documentation and examples of API implementation refer to [https://anitracking.com/api/ Anitra Public API documentation]<br /> :* note the API is currently linked to user access rights. Therefore your API credentials can be managed down in your user profile &quot;API keys&quot; section. You can generate new keys or revoke existing here.&lt;br&gt;[[File:api_credentials.JPG|800px]]<br /> <br /> <br /> = (OUT) Anitra to Movebank data feed =<br /> * Anitra to Movevebank data feed can be set up in the &quot;integration out&quot; section of the customer profile using the &quot;+create new&quot; button&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * a Movebank data owner username needs to be specified and credentials verified before saving. <br /> * the account provided will be used to host all the data synchronized into Movebank &lt;br&gt;[[File:movebank_customer_profile_integrationOUT_setup.JPG|600px]]<br /> * activate the connector by the button in Service status column&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * by default the synchronization is inactive for the new devices<br /> * you can switch ON/OFF data synchronization for particular tags using the &quot;Export to Movebank&quot; checkbox in the device profile.<br /> &lt;br&gt;[[File:movebank_check_deviceprofile.JPG|900px]]<br /> * review the status of the check and the last time of synchronization of each of your devices at the device list&lt;br&gt;[[File:movebank_device_list_columns.JPG|900px]]<br /> <br /> = (OUT) Manual DATA Export=<br /> : Allows manually exporting data from Anitra to CSV, XLSX, KMZ, and GPX formats for offline use.<br /> <br /> : Data export is available<br /> :* for Device entity<br /> :** the &quot;Export&quot; button in the Device profile <br /> :** context menu in Device grid&lt;br&gt;[[File:export_device_grid.JPG|900px]]<br /> :* for Tracking/Animal entities<br /> :** the &quot;Export&quot; button in Tracking/Animal profile <br /> :** context menu in Tracking grid.&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> <br /> : Note the content and the structure of the exported file can managed in the export dialogue<br /> :: * Format selector allows to swithc between the four available file formats (CSV, XLSX, KMZ, and GPX)<br /> :: * Time filter optioanly allows filtering the exported data range by time interval (empty dates = full dataset from the first till the last record)<br /> :: * Export settings section offers more export options for selected file format (e.g. default text qualifiers or field separators can be overriden here)<br /> :: * The column editor feature allows modifying output columns in terms of columns list, column order, and naming of exported columns (a user preference)&lt;br&gt;[[File:export_edit_columns.JPG|900px]]<br /> <br /> : Note the data export functionality is typicaly only available for device admins users (Customer/Device Owner/Admins). Users with shared access (&quot;view only&quot;) are not supposed to download and store the shared records outside of the system. In case of need a &quot;share with data export&quot; can be used.&lt;br&gt;[[File: share_with_export.JPG|900px]]<br /> <br /> = (OUT) Manual METADATA Export =<br /> * allows manually exporting Device, Tracking and Animal metadata from Anitra to CSV and XLSX formats<br /> * this export feature can be launched in Device and Tracking list using items from the context dialogue&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> * you can modify the columns that will be exported (column list, order, names) using &quot;column editor&quot;<br /> * use the item &quot;edit columns&quot; from context dialogue over the Device or Tracking grid header line and switch to &quot;export grid&quot; configuration&lt;br&gt;[[File: export_meta_edit_columns.JPG|900px]]</div>

Admin index.php?title=DATA_FLOWS&diff=1256 2024-04-24T11:19:57Z

<p>Admin: /* {{Fa|fa-upload}} (IN) Manual data import */</p> <hr /> <div>{{DISPLAYTITLE: DATA MANAGEMENT}}<br /> <br /> = (IN) Inbound DATA flows= <br /> :A possibility of plugging to external telemetry data sources and having them fed into Anitra<br /> :: ''Note the devices imported from the data source are imported to your profile and listed in the device list. A unified metadata structure can be then created on top of the imported data (Device - :Tracking - Animal). Ultimately data from various sources can be browsed and visualized side by side in a unified metadata-rich structure'' <br /> <br /> :Connectors for the following data sources currently exist:<br /> :* Movebank<br /> :* Ecotone<br /> :* Ornitela<br /> <br /> : Inbound connections are managed in the &quot;Integrations In&quot; section of [[Main_Page#Organisation.2FCustomer_profile |Customer profile]]. &lt;br&gt;[[File:Customer_Profile_Inbound.jpg|900px]]<br /> <br /> : The overview of existing connections allows adding, editing/removal and running/scheduling the connection<br /> <br /> : Use the &quot;+create new&quot; button to launch the connector creation wizard and enter the information required for running the feed&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> <br /> : Note each of the connectors works differently and hence also the information needed for running the data flow and scheduling the run slightly differs.<br /> <br /> == Ecotone ==<br /> : Details needed: Ecotone panel name (=URL of CSV files storage), user name, and password<br /> : User can manage this connector fully i.e. create, edit, run (once or schedule regular run), and delete&lt;br&gt;[[File:Ecotone2Anitra_setup_wizard.JPG|400px]]<br /> <br /> == Ornitela ==<br /> : Details needed: Ornitela user name and password <br /> : Ornitela integration is realised using &quot;Ornitela SFTP&quot; functionality. <br /> :* i.e. in this case user creates, edits the data connector, and requests activation (or requests deactivation) of the data flow<br /> :* by requesting activation user also requests to have the SFTP configuration in his Ornitela pannel configured by us. &lt;br&gt;[[File:Ornitela2Anitra_setup_wizard.JPG|400px]]<br /> : Note other related aspects using SFTP:<br /> :* only new data are integrated once the data flow is activated. <br /> :* for importing older data (records created before the feed activation) use the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality (any duplicate records are merged or skipped so you can import the same period repeatedly). <br /> :* only the devices marked for SFTP export in the Ornitela panel will be automatically updated into Anitra<br /> :* make sure you also update the connector definition anytime you are changing your Ornitela user password <br /> :* also bear in mind that modifying the list of devices marked for SFTP (unchecking and checking again) will result in the data flow interruption and thus to some possible gaps in the data.<br /> <br /> == Movebank to Anitra ==<br /> : Configuring this connector a Movebank data (+ Movebank metadata) are connected <br /> : Movebank API is employed for accessing the records<br /> : In this case user is supposed to enter a movebank username and password in combination with Movebank Study ID and request the data flow activation &lt;br&gt;[[File:Movebank2Anitra_setup_wizard.JPG|400px]]<br /> <br /> = {{Fa|fa-upload}} (IN) Manual data import= <br /> <br /> : Data Import dialog can be accessed in the Data management section of your Customer/Organization profile.<br /> : Imported data are merged under the Customer/Organisation account (new devices added or data appended to existing devices).<br /> <br /> : Import flow starts by browsing a file (or multiple files).&lt;br&gt;[[File:customer_import_01_file_selection.jpg|900px]]<br /> <br /> : An import wizard in a separate browser tab is open and automated file preprocessing (checking file type, header/columns, and actual data in the file) is run. <br /> : Messages about the progress of file checking are displayed. <br /> : In case any errors preventing the file from being imported occur the actual import (last step of the flow) is not triggered. <br /> : In case the file passes the checks successfully (no blocking errors detected) user will confirm the import by submitting it into the database import queue in the last step of the wizard. &lt;br&gt;[[File:customer_import_02_import_wizard.jpg|900px]]<br /> <br /> : '''1) Aquiring file'''<br /> :: File is downloaded into working space of the import procedure. This step also confirms the import service is actually ready to process your file.<br /> <br /> : '''2) File format and structure checking'''<br /> ::* CSV files only are accepted currently. <br /> ::* The CSV is supposed to be well structured i.e.:<br /> ::** Columns to be delimitted by a valid column separators (TAB, comma or semi-colon)<br /> ::** UTF-8 data encoding to be used etc<br /> ::* First row must contain column list<br /> ::* column names must be unique and not empty<br /> :: Wrong files will display errors and would not be imported. <br /> <br /> : '''3) Detect import file format'''<br /> :: Import dialog now accepts data in several formats/structures <br /> :: The format is automatically detected from the first file row (column header).<br /> :: To pass this step successfully the column list must match one of the accepted formats i.e the mandatory columns (such as device identification, datetime, or latitude and longitude) per format to be supplied and matching<br /> :: Missing columns (or column names not matching) related to optional data result in having these columns skipped and not imported. <br /> <br /> :: The following formats/structures/templates are now accepted:<br /> :: '''Basic''' - Anitra general import structure designed for importing custom (any) data <br /> ::: Data mapped directly to Anitra database column names<br /> ::: Check our guidelines and sample files while preparing your import files<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EW3wvkVaaFlMjlp9yFMEgT4BFu_8rAWtlCh2nOUuVrfmkQ?e=XenvK8| guideline file] - explains mandatory columns, lists correct column names and data types to be used, and gives some example values<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EQhkt8fmgPVDjUak8IhbxPkBceKv7jXoiF2dhp6gcJ0lMg?e=GeAxvj| template CSV file] - This is how your files should be structured. Note the file contains a header row and several sample/test rows. <br /> <br /> :: '''Movebank''' data (to be imported via Basic format currently)<br /> <br /> :: For importing data in the original CSV file structure and format generated by some other tag producers (fixed custom mapping of original files to Anitra database) these import formats are also implemented.<br /> :: '''Ecotone''' <br /> ::: Devices created using Ecotone import format are automatically labeled as device type &quot;Ecotone&quot; in Anitra (same as if these were created via Ecotone integration - see automatic integration section)<br /> :: '''Ornitela''' <br /> ::: Ornitela import currently accepts multiple versions of the Ornitela CSV file (versions 1 and 2, GPS, GPS+SENSORS, etc). Note the &quot;SENSORS&quot; rows are skipped and not imported.<br /> ::: Devices created using Ornitela import format are automatically labeled as device type &quot;Ornitela&quot; in Anitra (same as if these were created via Ornitela integration - see automatic integration section)<br /> <br /> :: Flows using native file formats can be useful when uploading older data files not available anymore to automated integration flow e.g. older records after having activated Ornitela SFTP data flow (which only generates new records).<br /> <br /> : '''4) Validate data'''<br /> :: Once the import file is successfully matched a data-checking phase follows (i.e. rows are checked) <br /> <br /> :: Data validation step checks the values against datatypes expected in target columns (e.g. wrong date time format, string data too long, text data in numeric columns, or similar datatype conflicts, etc)<br /> :: The rows/cells with problem data are detected and problems are shown.<br /> :: ''Note the past option of skipping the error rows processing only non-error data not currently implemented. I.e any data error in the file prevents the whole file from being imported.''&lt;br&gt;[[File:customer_import_03b_import_wizard_data_err.jpg|900px]]<br /> <br /> :: The second major task of the validation phase is to check the previous existence of the rows in the database. <br /> :: Rows matching existing records are prepared to be possibly '''updated'''.<br /> :: Rows not matching existing records are prepared to be '''inserted'''.<br /> :: Additionally, special purpose rows are removed from the file (e.g. not processed sensor rows in Ornitela files)<br /> <br /> :: Note the import procedure performs append and merge data operations (Also note no data delete occurs).<br /> ::* For any new device (device_code) detected in the file a new Device will be created in Anitra and all the imported rows linked to it.<br /> ::* For devices matching existing Anitra devices the data from the file will be merged (rows inserted or updated using data timestamp). Note a possible data loss by overwriting existing data (the same combination of device and date time already exists in the database).<br /> <br /> :: In case no data errors are detected user can decide if new rows should be inserted and/or existing data should be updated.<br /> :: Hitting the Import button submits the task to the server queue for processing.&lt;br&gt;[[File:customer_import_03c_import_wizard_data_ok.jpg|700px]]<br /> <br /> : After the import is done a summary is provided.<br /> <br /> : Note you can import simultaneously more files in one import session. Each of the files runs independently through its 5-step import flow.<br /> : As the import of large files can last many minutes or even hours (depending on server overload), you can close the browser tab (or even your computer) during the last import step. In case you need to return to the import screen use the &quot;Running imports&quot; list in the customer profile to reopen the session again&lt;br&gt;[[File:customer_import_04_running_imports.jpg|900px]]<br /> <br /> : [[IMPORT_OLD| Manual import functionality - old version (before 2024)]]<br /> <br /> = (OUT) Anitra API data &amp; metadata access =<br /> :* allows grabbing Anitra DATA and METADATA from external tools such as from GIS systems API interface <br /> :* curent version of API offers access to the following items:<br /> :** Device List (=Device metadata)<br /> :** Device Data<br /> :** Tracking List (=Tracking and Animal metadata)<br /> :** Tracking Data<br /> :* for detailed documentation and examples of API implementation refer to [https://anitracking.com/api/ Anitra Public API documentation]<br /> :* note the API is currently linked to user access rights. Therefore your API credentials can be managed down in your user profile &quot;API keys&quot; section. You can generate new keys or revoke existing here.&lt;br&gt;[[File:api_credentials.JPG|800px]]<br /> <br /> <br /> = (OUT) Anitra to Movebank data feed =<br /> * Anitra to Movevebank data feed can be set up in the &quot;integration out&quot; section of the customer profile using the &quot;+create new&quot; button&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * a Movebank data owner username needs to be specified and credentials verified before saving. <br /> * the account provided will be used to host all the data synchronized into Movebank &lt;br&gt;[[File:movebank_customer_profile_integrationOUT_setup.JPG|600px]]<br /> * activate the connector by the button in Service status column&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * by default the synchronization is inactive for the new devices<br /> * you can switch ON/OFF data synchronization for particular tags using the &quot;Export to Movebank&quot; checkbox in the device profile.<br /> &lt;br&gt;[[File:movebank_check_deviceprofile.JPG|900px]]<br /> * review the status of the check and the last time of synchronization of each of your devices at the device list&lt;br&gt;[[File:movebank_device_list_columns.JPG|900px]]<br /> <br /> = (OUT) Manual DATA Export=<br /> : Allows manually exporting data from Anitra to CSV, XLSX, KMZ, and GPX formats for offline use.<br /> <br /> : Data export is available<br /> :* for Device entity<br /> :** the &quot;Export&quot; button in the Device profile <br /> :** context menu in Device grid&lt;br&gt;[[File:export_device_grid.JPG|900px]]<br /> :* for Tracking/Animal entities<br /> :** the &quot;Export&quot; button in Tracking/Animal profile <br /> :** context menu in Tracking grid.&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> <br /> : Note the content and the structure of the exported file can managed in the export dialogue<br /> :: * Format selector allows to swithc between the four available file formats (CSV, XLSX, KMZ, and GPX)<br /> :: * Time filter optioanly allows filtering the exported data range by time interval (empty dates = full dataset from the first till the last record)<br /> :: * Export settings section offers more export options for selected file format (e.g. default text qualifiers or field separators can be overriden here)<br /> :: * The column editor feature allows modifying output columns in terms of columns list, column order, and naming of exported columns (a user preference)&lt;br&gt;[[File:export_edit_columns.JPG|900px]]<br /> <br /> : Note the data export functionality is typicaly only available for device admins users (Customer/Device Owner/Admins). Users with shared access (&quot;view only&quot;) are not supposed to download and store the shared records outside of the system. In case of need a &quot;share with data export&quot; can be used.&lt;br&gt;[[File: share_with_export.JPG|900px]]<br /> <br /> = (OUT) Manual METADATA Export =<br /> * allows manually exporting Device, Tracking and Animal metadata from Anitra to CSV and XLSX formats<br /> * this export feature can be launched in Device and Tracking list using items from the context dialogue&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> * you can modify the columns that will be exported (column list, order, names) using &quot;column editor&quot;<br /> * use the item &quot;edit columns&quot; from context dialogue over the Device or Tracking grid header line and switch to &quot;export grid&quot; configuration&lt;br&gt;[[File: export_meta_edit_columns.JPG|900px]]</div>

Admin index.php?title=File:Customer_import_04_running_imports.jpg&diff=1255 2024-04-24T11:15:40Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=File:Customer_import_03c_import_wizard_data_ok.jpg&diff=1254 2024-04-24T10:57:26Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=DATA_FLOWS&diff=1253 2024-04-24T10:34:23Z

<p>Admin: /* {{Fa|fa-upload}} (IN) Manual data import */</p> <hr /> <div>{{DISPLAYTITLE: DATA MANAGEMENT}}<br /> <br /> = (IN) Inbound DATA flows= <br /> :A possibility of plugging to external telemetry data sources and having them fed into Anitra<br /> :: ''Note the devices imported from the data source are imported to your profile and listed in the device list. A unified metadata structure can be then created on top of the imported data (Device - :Tracking - Animal). Ultimately data from various sources can be browsed and visualized side by side in a unified metadata-rich structure'' <br /> <br /> :Connectors for the following data sources currently exist:<br /> :* Movebank<br /> :* Ecotone<br /> :* Ornitela<br /> <br /> : Inbound connections are managed in the &quot;Integrations In&quot; section of [[Main_Page#Organisation.2FCustomer_profile |Customer profile]]. &lt;br&gt;[[File:Customer_Profile_Inbound.jpg|900px]]<br /> <br /> : The overview of existing connections allows adding, editing/removal and running/scheduling the connection<br /> <br /> : Use the &quot;+create new&quot; button to launch the connector creation wizard and enter the information required for running the feed&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> <br /> : Note each of the connectors works differently and hence also the information needed for running the data flow and scheduling the run slightly differs.<br /> <br /> == Ecotone ==<br /> : Details needed: Ecotone panel name (=URL of CSV files storage), user name, and password<br /> : User can manage this connector fully i.e. create, edit, run (once or schedule regular run), and delete&lt;br&gt;[[File:Ecotone2Anitra_setup_wizard.JPG|400px]]<br /> <br /> == Ornitela ==<br /> : Details needed: Ornitela user name and password <br /> : Ornitela integration is realised using &quot;Ornitela SFTP&quot; functionality. <br /> :* i.e. in this case user creates, edits the data connector, and requests activation (or requests deactivation) of the data flow<br /> :* by requesting activation user also requests to have the SFTP configuration in his Ornitela pannel configured by us. &lt;br&gt;[[File:Ornitela2Anitra_setup_wizard.JPG|400px]]<br /> : Note other related aspects using SFTP:<br /> :* only new data are integrated once the data flow is activated. <br /> :* for importing older data (records created before the feed activation) use the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality (any duplicate records are merged or skipped so you can import the same period repeatedly). <br /> :* only the devices marked for SFTP export in the Ornitela panel will be automatically updated into Anitra<br /> :* make sure you also update the connector definition anytime you are changing your Ornitela user password <br /> :* also bear in mind that modifying the list of devices marked for SFTP (unchecking and checking again) will result in the data flow interruption and thus to some possible gaps in the data.<br /> <br /> == Movebank to Anitra ==<br /> : Configuring this connector a Movebank data (+ Movebank metadata) are connected <br /> : Movebank API is employed for accessing the records<br /> : In this case user is supposed to enter a movebank username and password in combination with Movebank Study ID and request the data flow activation &lt;br&gt;[[File:Movebank2Anitra_setup_wizard.JPG|400px]]<br /> <br /> = {{Fa|fa-upload}} (IN) Manual data import= <br /> <br /> : Data Import dialog can be accessed in the Data management section of your Customer/Organization profile.<br /> : Imported data are merged under the Customer/Organisation account (new devices added or data appended to existing devices).<br /> <br /> : Import flow starts by browsing a file (or multiple files).&lt;br&gt;[[File:customer_import_01_file_selection.jpg|900px]]<br /> <br /> : An import wizard in a separate browser tab is open and automated file preprocessing (checking file type, header/columns, and actual data in the file) is run. <br /> : Messages about the progress of file checking are displayed. <br /> : In case any errors preventing the file from being imported occur the actual import (last step of the flow) is not triggered. <br /> : In case the file passes the checks successfully (no blocking errors detected) user will confirm the import by submitting it into the database import queue in the last step of the wizard. &lt;br&gt;[[File:customer_import_02_import_wizard.jpg|900px]]<br /> <br /> : '''1) Aquiring file'''<br /> :: File is downloaded into working space of the import procedure. This step also confirms the import service is actually ready to process your file.<br /> <br /> : '''2) File format and structure checking'''<br /> ::* CSV files only are accepted currently. <br /> ::* The CSV is supposed to be well structured i.e.:<br /> ::** Columns to be delimitted by a valid column separators (TAB, comma or semi-colon)<br /> ::** UTF-8 data encoding to be used etc<br /> ::* First row must contain column list<br /> ::* column names must be unique and not empty<br /> :: Wrong files will display errors and would not be imported. <br /> <br /> : '''3) Detect import file format'''<br /> :: Import dialog now accepts data in several formats/structures <br /> :: The format is automatically detected from the first file row (column header).<br /> :: To pass this step successfully the column list must match one of the accepted formats i.e the mandatory columns (such as device identification, datetime, or latitude and longitude) per format to be supplied and matching<br /> :: Missing columns (or column names not matching) related to optional data result in having these columns skipped and not imported. <br /> <br /> :: The following formats/structures/templates are now accepted:<br /> :: '''Basic''' - Anitra general import structure designed for importing custom (any) data <br /> ::: Data mapped directly to Anitra database column names<br /> ::: Check our guidelines and sample files while preparing your import files<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EW3wvkVaaFlMjlp9yFMEgT4BFu_8rAWtlCh2nOUuVrfmkQ?e=XenvK8| guideline file] - explains mandatory columns, lists correct column names and data types to be used, and gives some example values<br /> :::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EQhkt8fmgPVDjUak8IhbxPkBceKv7jXoiF2dhp6gcJ0lMg?e=GeAxvj| template CSV file] - This is how your files should be structured. Note the file contains a header row and several sample/test rows. <br /> <br /> :: '''Movebank''' data (to be imported via Basic format currently)<br /> <br /> :: For importing data in the original CSV file structure and format generated by some other tag producers (fixed custom mapping of original files to Anitra database) these import formats are also implemented.<br /> :: '''Ecotone''' <br /> ::: Devices created using Ecotone import format are automatically labeled as device type &quot;Ecotone&quot; in Anitra (same as if these were created via Ecotone integration - see automatic integration section)<br /> :: '''Ornitela''' <br /> ::: Ornitela import currently accepts multiple versions of the Ornitela CSV file (versions 1 and 2, GPS, GPS+SENSORS, etc). Note the &quot;SENSORS&quot; rows are skipped and not imported.<br /> ::: Devices created using Ornitela import format are automatically labeled as device type &quot;Ornitela&quot; in Anitra (same as if these were created via Ornitela integration - see automatic integration section)<br /> <br /> :: Flows using native file formats can be useful when uploading older data files not available anymore to automated integration flow e.g. older records after having activated Ornitela SFTP data flow (which only generates new records).<br /> <br /> : '''4) Validate data'''<br /> :: Once the import file is succesfuly matched a data checking phase follows (i.e. rows are checked) <br /> <br /> :: Data validation step checks the values against datatypes expected in target columns (e.g. wrong date time format, string data too long, text data in numeric columns or similar datatype conflicts etc)<br /> :: The rows/cells with problem data are detected and problems shown.<br /> :: ''Note the past option of skipping the error rows processing only non error data not currently implemented. I.e any data error in the file prevents the whole file from being imported.''&lt;br&gt;[[File:customer_import_03b_import_wizard_data_err.jpg|900px]]<br /> <br /> :: The second major task of the validation phase is to check previous existence of the rows in the database. <br /> :: Rows mathing existing records are prepared to be possibly '''updated'''.<br /> :: Rows not matching existing records are prepared to be '''inserted'''.<br /> :: Additionally, a special purpose rows are removed from the file (e.g. not processsed sensor rows in Ornitela files)<br /> <br /> : Note the import procedure performs append and merge data operations (Also note no data delete occures)<br /> :* For any new device (device_code) detected in the file a new Device will be created in Anitra and all the imported rows linked to it<br /> :* For devices matching existing Anitra devices the data from the file will be merged (rows inserted or updated using data timestamp). Note a possible data loss by overwritiong existing data (same combination of device and date time already exists in the database) <br /> <br /> : [[IMPORT_OLD| Manual import functionality - old vereison (before 2024)]]<br /> <br /> = (OUT) Anitra API data &amp; metadata access =<br /> :* allows grabbing Anitra DATA and METADATA from external tools such as from GIS systems API interface <br /> :* curent version of API offers access to the following items:<br /> :** Device List (=Device metadata)<br /> :** Device Data<br /> :** Tracking List (=Tracking and Animal metadata)<br /> :** Tracking Data<br /> :* for detailed documentation and examples of API implementation refer to [https://anitracking.com/api/ Anitra Public API documentation]<br /> :* note the API is currently linked to user access rights. Therefore your API credentials can be managed down in your user profile &quot;API keys&quot; section. You can generate new keys or revoke existing here.&lt;br&gt;[[File:api_credentials.JPG|800px]]<br /> <br /> <br /> = (OUT) Anitra to Movebank data feed =<br /> * Anitra to Movevebank data feed can be set up in the &quot;integration out&quot; section of the customer profile using the &quot;+create new&quot; button&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * a Movebank data owner username needs to be specified and credentials verified before saving. <br /> * the account provided will be used to host all the data synchronized into Movebank &lt;br&gt;[[File:movebank_customer_profile_integrationOUT_setup.JPG|600px]]<br /> * activate the connector by the button in Service status column&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * by default the synchronization is inactive for the new devices<br /> * you can switch ON/OFF data synchronization for particular tags using the &quot;Export to Movebank&quot; checkbox in the device profile.<br /> &lt;br&gt;[[File:movebank_check_deviceprofile.JPG|900px]]<br /> * review the status of the check and the last time of synchronization of each of your devices at the device list&lt;br&gt;[[File:movebank_device_list_columns.JPG|900px]]<br /> <br /> = (OUT) Manual DATA Export=<br /> : Allows manually exporting data from Anitra to CSV, XLSX, KMZ, and GPX formats for offline use.<br /> <br /> : Data export is available<br /> :* for Device entity<br /> :** the &quot;Export&quot; button in the Device profile <br /> :** context menu in Device grid&lt;br&gt;[[File:export_device_grid.JPG|900px]]<br /> :* for Tracking/Animal entities<br /> :** the &quot;Export&quot; button in Tracking/Animal profile <br /> :** context menu in Tracking grid.&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> <br /> : Note the content and the structure of the exported file can managed in the export dialogue<br /> :: * Format selector allows to swithc between the four available file formats (CSV, XLSX, KMZ, and GPX)<br /> :: * Time filter optioanly allows filtering the exported data range by time interval (empty dates = full dataset from the first till the last record)<br /> :: * Export settings section offers more export options for selected file format (e.g. default text qualifiers or field separators can be overriden here)<br /> :: * The column editor feature allows modifying output columns in terms of columns list, column order, and naming of exported columns (a user preference)&lt;br&gt;[[File:export_edit_columns.JPG|900px]]<br /> <br /> : Note the data export functionality is typicaly only available for device admins users (Customer/Device Owner/Admins). Users with shared access (&quot;view only&quot;) are not supposed to download and store the shared records outside of the system. In case of need a &quot;share with data export&quot; can be used.&lt;br&gt;[[File: share_with_export.JPG|900px]]<br /> <br /> = (OUT) Manual METADATA Export =<br /> * allows manually exporting Device, Tracking and Animal metadata from Anitra to CSV and XLSX formats<br /> * this export feature can be launched in Device and Tracking list using items from the context dialogue&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> * you can modify the columns that will be exported (column list, order, names) using &quot;column editor&quot;<br /> * use the item &quot;edit columns&quot; from context dialogue over the Device or Tracking grid header line and switch to &quot;export grid&quot; configuration&lt;br&gt;[[File: export_meta_edit_columns.JPG|900px]]</div>

Admin index.php?title=File:Customer_import_03b_import_wizard_data_err.jpg&diff=1252 2024-04-24T10:27:40Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=File:Customer_import_03_import_wizard_data_err.jpg&diff=1251 2024-04-24T10:24:13Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=File:Customer_import_02_import_wizard.jpg&diff=1250 2024-04-24T08:17:04Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=File:Customer_import_01_file_selection.jpg&diff=1249 2024-04-24T07:56:33Z

<p>Admin: </p> <hr /> <div></div>

Admin index.php?title=DATA_FLOWS&diff=1248 2024-04-24T07:55:07Z

<p>Admin: /* {{Fa|fa-upload}} (IN) Manual data import */</p> <hr /> <div>{{DISPLAYTITLE: DATA MANAGEMENT}}<br /> <br /> = (IN) Inbound DATA flows= <br /> :A possibility of plugging to external telemetry data sources and having them fed into Anitra<br /> :: ''Note the devices imported from the data source are imported to your profile and listed in the device list. A unified metadata structure can be then created on top of the imported data (Device - :Tracking - Animal). Ultimately data from various sources can be browsed and visualized side by side in a unified metadata-rich structure'' <br /> <br /> :Connectors for the following data sources currently exist:<br /> :* Movebank<br /> :* Ecotone<br /> :* Ornitela<br /> <br /> : Inbound connections are managed in the &quot;Integrations In&quot; section of [[Main_Page#Organisation.2FCustomer_profile |Customer profile]]. &lt;br&gt;[[File:Customer_Profile_Inbound.jpg|900px]]<br /> <br /> : The overview of existing connections allows adding, editing/removal and running/scheduling the connection<br /> <br /> : Use the &quot;+create new&quot; button to launch the connector creation wizard and enter the information required for running the feed&lt;br&gt;[[File:Inbound_connection_overview.jpg|600px]]<br /> <br /> : Note each of the connectors works differently and hence also the information needed for running the data flow and scheduling the run slightly differs.<br /> <br /> == Ecotone ==<br /> : Details needed: Ecotone panel name (=URL of CSV files storage), user name, and password<br /> : User can manage this connector fully i.e. create, edit, run (once or schedule regular run), and delete&lt;br&gt;[[File:Ecotone2Anitra_setup_wizard.JPG|400px]]<br /> <br /> == Ornitela ==<br /> : Details needed: Ornitela user name and password <br /> : Ornitela integration is realised using &quot;Ornitela SFTP&quot; functionality. <br /> :* i.e. in this case user creates, edits the data connector, and requests activation (or requests deactivation) of the data flow<br /> :* by requesting activation user also requests to have the SFTP configuration in his Ornitela pannel configured by us. &lt;br&gt;[[File:Ornitela2Anitra_setup_wizard.JPG|400px]]<br /> : Note other related aspects using SFTP:<br /> :* only new data are integrated once the data flow is activated. <br /> :* for importing older data (records created before the feed activation) use the [[DATA_FLOWS#.28IN.29_Manual_data_import|Manual Data Import]] functionality (any duplicate records are merged or skipped so you can import the same period repeatedly). <br /> :* only the devices marked for SFTP export in the Ornitela panel will be automatically updated into Anitra<br /> :* make sure you also update the connector definition anytime you are changing your Ornitela user password <br /> :* also bear in mind that modifying the list of devices marked for SFTP (unchecking and checking again) will result in the data flow interruption and thus to some possible gaps in the data.<br /> <br /> == Movebank to Anitra ==<br /> : Configuring this connector a Movebank data (+ Movebank metadata) are connected <br /> : Movebank API is employed for accessing the records<br /> : In this case user is supposed to enter a movebank username and password in combination with Movebank Study ID and request the data flow activation &lt;br&gt;[[File:Movebank2Anitra_setup_wizard.JPG|400px]]<br /> <br /> = {{Fa|fa-upload}} (IN) Manual data import= <br /> <br /> : [[IMPORT_OLD| Manual import functionality - old vereison (before 2024)]]<br /> <br /> : Data Import dialog can be accessed in Data management section of your Customer/Organization profile<br /> : Imported data are merged under Customer/Organisation account (new devices added or data appended to existing devices)&lt;br&gt;[[File:customer_import_01_file_selection.jpg|900px]]<br /> <br /> : Import dialog now accepts data in the following structures/teplates:<br /> <br /> : 1) data mapped directly to Anitra database column names - labeled as a '''Basic format''' in the Import dialog<br /> <br /> :: Designed for importing custom data <br /> :: Check our guideline and sample files while preparing your import files<br /> ::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EW3wvkVaaFlMjlp9yFMEgT4BFu_8rAWtlCh2nOUuVrfmkQ?e=XenvK8| guideline file] - explains mandatory columns, lists correct column names and data types to be used, and gives some example values<br /> ::* [https://memos-my.sharepoint.com/:x:/g/personal/dusan_rak_anitra_cz/EQhkt8fmgPVDjUak8IhbxPkBceKv7jXoiF2dhp6gcJ0lMg?e=GeAxvj| template CSV file] - this is how your files should be structured. Note the file contains a header row and several sample/test rows. <br /> <br /> :: For successful import make sure you use correct datatypes, column and data delimitters and the file encoding. <br /> <br /> : 2) for importing data in the original file structure and format generated by other tag producers (fixed custom mapping of original files to Anitra database). <br /> <br /> ::* '''Ecotone CSV format''' <br /> ::* '''Ornitela CSV format''' <br /> ::: Ornitela import currently accepts muptiple versions of the Ornitela CSV file (versions 1 and 2, GPS, GPS+SENSORS etc). Note the &quot;SENSORS&quot; rows are skipped and not imported.<br /> <br /> :: Flows using native file formats can be useful when uploading older data files not available anymore to automated integration flow e.g. older records after having activated Ornitela SFTP data flow (which only generates new records).<br /> <br /> <br /> : Note this general behavior traits of the import flow<br /> <br /> :* import procedure performs append and merge data operations i.e.<br /> :** for any new device (device_code) detected in the file a new Device will be created in Anitra and all the imported rows linked to it<br /> :** for devices matching existing Anitra devices the data from the file will be merged (rows inserted or updated using data timestamp, no delete occures here)<br /> <br /> :* first step of the import flow evaluates the file structure and the data contained<br /> :** completely wrong files will display errors and will not be imported. following type of problems will prevent file from being imported<br /> :*** wrong column separators, <br /> :*** unmatching names of key columns (such as device identification, dateime, or latitude and longitude or containi)<br /> :*** duplicate column names in the list<br /> :*** wrong coding used&lt;br&gt;[[File:import_column_errors.jpg|1200px]]<br /> :** some less severe problems will only result in having some columns from the file skipped and not imported. e.g.missing column name or wrong name (not exactly matching teh template columns)&lt;br&gt;[[File:import_column_warnings.jpg|1200px]]<br /> <br /> :* similarly as for the file structure the rows are also checked. The rows with problem data are detected, problems shown and rows skipped while importing. You can possibly notice these <br /> :** errors:<br /> :*** data in the cell not matching the expected target format (e.g. wrong date time format, string data too long, text data in numeric columns or similar datatype conflicts etc)<br /> :*** all these rows will be skipped during the import&lt;br&gt;[[File:import_data_errors.jpg|1200px]]<br /> :** warnings:<br /> :*** possible data loss by overwritiong existing data (same combination of device and date time already exists in the database) <br /> :*** these row will be used to update existing data base records&lt;br&gt;[[File:import_data_warnings.jpg|1200px]]<br /> <br /> = (OUT) Anitra API data &amp; metadata access =<br /> :* allows grabbing Anitra DATA and METADATA from external tools such as from GIS systems API interface <br /> :* curent version of API offers access to the following items:<br /> :** Device List (=Device metadata)<br /> :** Device Data<br /> :** Tracking List (=Tracking and Animal metadata)<br /> :** Tracking Data<br /> :* for detailed documentation and examples of API implementation refer to [https://anitracking.com/api/ Anitra Public API documentation]<br /> :* note the API is currently linked to user access rights. Therefore your API credentials can be managed down in your user profile &quot;API keys&quot; section. You can generate new keys or revoke existing here.&lt;br&gt;[[File:api_credentials.JPG|800px]]<br /> <br /> <br /> = (OUT) Anitra to Movebank data feed =<br /> * Anitra to Movevebank data feed can be set up in the &quot;integration out&quot; section of the customer profile using the &quot;+create new&quot; button&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * a Movebank data owner username needs to be specified and credentials verified before saving. <br /> * the account provided will be used to host all the data synchronized into Movebank &lt;br&gt;[[File:movebank_customer_profile_integrationOUT_setup.JPG|600px]]<br /> * activate the connector by the button in Service status column&lt;br&gt;[[File:movebank_customer_profile_integrationOUT.JPG|800px]]<br /> * by default the synchronization is inactive for the new devices<br /> * you can switch ON/OFF data synchronization for particular tags using the &quot;Export to Movebank&quot; checkbox in the device profile.<br /> &lt;br&gt;[[File:movebank_check_deviceprofile.JPG|900px]]<br /> * review the status of the check and the last time of synchronization of each of your devices at the device list&lt;br&gt;[[File:movebank_device_list_columns.JPG|900px]]<br /> <br /> = (OUT) Manual DATA Export=<br /> : Allows manually exporting data from Anitra to CSV, XLSX, KMZ, and GPX formats for offline use.<br /> <br /> : Data export is available<br /> :* for Device entity<br /> :** the &quot;Export&quot; button in the Device profile <br /> :** context menu in Device grid&lt;br&gt;[[File:export_device_grid.JPG|900px]]<br /> :* for Tracking/Animal entities<br /> :** the &quot;Export&quot; button in Tracking/Animal profile <br /> :** context menu in Tracking grid.&lt;br&gt;[[File:export_tracking_profile.JPG|900px]]<br /> <br /> : Note the content and the structure of the exported file can managed in the export dialogue<br /> :: * Format selector allows to swithc between the four available file formats (CSV, XLSX, KMZ, and GPX)<br /> :: * Time filter optioanly allows filtering the exported data range by time interval (empty dates = full dataset from the first till the last record)<br /> :: * Export settings section offers more export options for selected file format (e.g. default text qualifiers or field separators can be overriden here)<br /> :: * The column editor feature allows modifying output columns in terms of columns list, column order, and naming of exported columns (a user preference)&lt;br&gt;[[File:export_edit_columns.JPG|900px]]<br /> <br /> : Note the data export functionality is typicaly only available for device admins users (Customer/Device Owner/Admins). Users with shared access (&quot;view only&quot;) are not supposed to download and store the shared records outside of the system. In case of need a &quot;share with data export&quot; can be used.&lt;br&gt;[[File: share_with_export.JPG|900px]]<br /> <br /> = (OUT) Manual METADATA Export =<br /> * allows manually exporting Device, Tracking and Animal metadata from Anitra to CSV and XLSX formats<br /> * this export feature can be launched in Device and Tracking list using items from the context dialogue&lt;br&gt;[[File: export_meta_tracking_grid.JPG|900px]]<br /> * you can modify the columns that will be exported (column list, order, names) using &quot;column editor&quot;<br /> * use the item &quot;edit columns&quot; from context dialogue over the Device or Tracking grid header line and switch to &quot;export grid&quot; configuration&lt;br&gt;[[File: export_meta_edit_columns.JPG|900px]]</div>

Admin