Main Page - Revision history

Admin: /* MAIN CONCEPTS */

2024-05-02T12:26:12Z

‎MAIN CONCEPTS

Admin: /* MAIN CONCEPTS */

2024-05-02T12:25:38Z

‎MAIN CONCEPTS

Admin: /* MAIN CONCEPTS */

2024-05-02T12:24:11Z

‎MAIN CONCEPTS

Admin: /* MAIN CONCEPTS */

2024-05-02T12:12:28Z

‎MAIN CONCEPTS

Admin: /* Device Status and Discard Flow */

2024-04-04T07:02:48Z

‎Device Status and Discard Flow

Admin: /* NOTES: Where to note down info about particular things? */

2024-04-03T21:02:18Z

‎NOTES: Where to note down info about particular things?

Admin: /* MORE GUIDES */

2024-04-03T20:52:25Z

‎MORE GUIDES

Admin: /* NOTES: Where to note down info about particular things? */

2024-04-03T20:50:26Z

‎NOTES: Where to note down info about particular things?

Admin: /* MAIN CONCEPTS */

2024-04-02T14:44:50Z

‎MAIN CONCEPTS

Admin: /* MAIN CONCEPTS */

2024-04-02T14:42:35Z

‎MAIN CONCEPTS

@@ Line 99: / Line 99: @@
 : '''Data Cluster''', Annotation
-:: 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)
+:: 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).
-:: these clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.
+:: These clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.
 = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =

@@ Line 100: / Line 100: @@
 : '''Data Cluster''', Annotation
 :: 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)
-:: these clusters can be used to simplify the visibility of tracks and positions in the maps by masking redundant details showing aggregated information.
+:: these clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.
 = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =

@@ Line 41: / Line 41: @@
 : '''Organisation, Customer, or Ownership'''
 :: Device "Ownership" defines which organization/customer holds ownership of the data.
-:: Purchased Anitra devices are transfered under Customer account during the purchasing process
+:: Purchased Anitra devices are transferred under the Customer account during the purchasing process.
-:: Non-Anitra devices are linked to particural Customer by running integration connector or Importing data manually
+:: Non-Anitra devices are linked to particular Customers by running integration connectors or Importing data manually.
 :: Customer account also holds the credit balance (data fee prepay)
@@ Line 97: / Line 97: @@
 ::*  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.
 ::*  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.
 = PROFILEs: Where can I see and manage the detail info for entities such as Device, Animal, and Tracking? =

@@ Line 38: / Line 38: @@
 :: 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]].
-:: Device "Ownership" defines which organization or individual holds ownership of the data.
@@ Line 67: / Line 73: @@
 :: 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.
-: '''Organisation''', Customer
 : '''Place''', Point of Interest (POI)
 : '''Event''', Observation

@@ Line 333: / Line 333: @@
 : '''Device/SIM Discard Flow''' (for Anitra devices)
-:: 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
+:: 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
-:: users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.
+:: Users are supposed to mark the devices they wish to be terminated - to be used for devices not expected to deliver new data anymore.
-:: marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider
+:: Marking the device triggers a process that '''irreversibly''' terminates the device SIM with our network provider
 :: 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))''
-:: 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)
+:: 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)
-:: the check for marking devices to be terminated is available at the bottom part of the device profile.
+:: The check for marking devices to be terminated is available at the bottom part of the device profile.
 : Device Discard/Archive flow for non-Anitra devices
 :: 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
-:: for those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)
+:: For those, the flag only allows marking those that are not active anymore (for the sake of filtering and correct visibility in the maps)
-:: a recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel
+:: A recommendable practice is to mark the tags that are considered lost or those terminated in the original control panel
-:: note in this case the flag is fully reversible (the user can change it there and back without any restriction)
+:: Note in this case the flag is fully reversible (the user can change it there and back without any restriction)
 : '''Device Status Extended/Long'''
-:: extended/long devices status summarizing all status information related.
+:: Extended/long devices status is summarizing all the status information related.
-:: a combined field of Device status, history summary and Discard status
+:: It is a combined field of Device status, history summary and Discard status.
-:: can be displayed in the Device profile, Device list, and Customer balance overview
+:: It is displayed in the Device profile, Device list, and Customer balance overview
 == Configuration /programming of devices ==

@@ Line 393: / Line 393: @@
 == NOTES: Where to note down info about particular things? ==
+: A handy feature helping users to get organized and stay organized with their data.<br>:[[File:note_thread_narrow.JPG|600px]]
 : Available for multiple entities (Devices, Trackings, Animals, and Customers/Organizations)
 : Note threads can be accessed
-:* from entity profiles - in green shown opening of the Tracking note, the blue mark on the rigt show the place to access device note <br>[[File:note_from_profile.JPG|900px]]
+:* 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 <br>[[File:note_from_profile.JPG|900px]]
-:* entity lists or using the context menu - either click on the note icon in Notes column or use context menu over the desired row<br>[[File:note_from_listContext.JPG|900px]]
+:* 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<br>[[File:note_from_listContext.JPG|900px]]
 :* from user Task List <br>[[File:task_userTaskList.jpg|700px]]
 : Here a new note can be created, existing notes can be edited, or a reply to previous notes can be posted.
-: The thread window is flowing over the entity. It can be open paralel to whatever you do in profile. You can switch tabs, type form, take screenshots while browisng or even be creating/editing notes.
+: 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.
 : Create the note simply by typing in the form
-: Edit existing notes by double-clicking them or using "more" or "Edit" icons in the right top corner. this switches note into "'''edit'''" mode<br>
+: Edit existing notes by double-clicking them or using "more" or "Edit" icons in the right top corner. This switches note into "'''edit'''" mode<br>
 :[[File:note_editMode.JPG|500px]]
 : Save the new or edited note by clicking the "Publish/Done" button or simply hitting ENTER.
@@ Line 414: / Line 413: @@
 : "Clone note" function - particularly useful e.g. for fast duplicating of notes with complex definitions (i.e. notes linked to many items).
 :: ''While cloning notes attachments are removed (not cloned with the note).''<br>:[[File:note_deleteClone_thread.JPG|500px]]
-: Use "Promote to parent note" when you need to convert a note reply reply to top level parent note.
+: Use "Promote to parent note" when you need to convert a note reply to a top-level parent note.
-:: ''While promoting reply to note it inherits the relations from its orginal parent note''
+:: ''While promoting reply to note it inherits the relations from its original parent note''
-: Use "drag'n'drop: action to move one note into reply area of the other note to move and transform note into reply.
+: Use "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.
 :: ''Converting note into reply is only possible for notes created by the user himself and only to notes that have no complex relationship''
@@ Line 431: / Line 430: @@
 :* 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)
 :* attachments
-:** to each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)
+:** To each note or reply, one or more attachments (e.g. pictures) can be attached (by browse function or using drag 'n' drop)
-:** picture attachments are then previewed in the thread, photos can be opened in ful size and browsed as a gallery
+:** Picture attachments are then previewed in the thread, photos can be opened in full size and browsed as a gallery
 :* screenshots
-:** for adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body.
+:** For adding a screenshot from the clipboard just press CTRL+V (paste) while in the note body.
-:** this will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.
+:** This will append the screenshot similarly as it was a regular attached picture file. Note you can modify the screenshot file name as well.
 :* links/URL
 :* tags - you can label your notes by using user "tags", later you can search, filter, or group by these tags

← Older revision		Revision as of 20:52, 3 April 2024
Line 540:		Line 540:

	: [[EUROKITE_PROJECT_DATASHARING\| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]		: [[EUROKITE_PROJECT_DATASHARING\| LIFE EUROKITE Project datasharing (a guide for Eurokite data controllers)]]
−
−	~~: [[MORE_GUIDES#Device_Statuses\| Device Status Management, Tracking specification, Mortality warnings]]~~

@@ Line 34: / Line 34: @@
 :: Device Status attribute reflects the current usage of the devices (statuses are '''pool-new''', '''pool-used''', '''deployed-active''', '''deployed-delayed''', and '''deployed-missing''').
 :: Besides, a "Discard" flag is available to mark the tags that are considered out of service.
-:: [[MORE_GUIDES#Device_Statuses|More on device statuses and discard floow here]].
+:: [[Main_Page#Device_Status_and_Discard_Flow |More on device statuses and discard flow here]].
 :: 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]].

@@ Line 52: / Line 52: @@
 : '''Tracking'''
-:: Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on [[MORE_GUIDES#Tracking_range_management|creation and modification of the tracking range]].
+:: 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]].
 :: The date(time) interval defines when the device was physically attached to the Animal