ocean-tracking-network · yingniu · Feb 17, 2026 · Feb 17, 2026 · Feb 18, 2026 · Feb 19, 2026
diff --git a/_episodes/30_near_real_time_qc_process.md b/_episodes/30_near_real_time_qc_process.md
diff --git a/_episodes/31_near_real_time_qc_how_to_WildlifeComputers.md b/_episodes/31_near_real_time_qc_how_to_WildlifeComputers.md
@@ -0,0 +1,36 @@
+---
+title: "Near Real Time (NRT) Animal Tagging Location Data Quality Control (QC) Process: Wildlife Computers"
+teaching: 120
+exercises: 0
+questions:
+- "How to receive metadata & data access from a researcher to set up satellite data harvesting"
+- "How to use the metadata to create a config file"
+- "How to push that config file somewhere so it can be processed regularly by the RT process"
+- "How to process a dataset that is no longer real-time - delayed-mode"
+---
+
+
+## How to receive metadata & data access from a researcher to set up satellite data harvesting for Wildlife Computers tags
+### Metadata
+The minimum metadata required by the QC process is: 1. species common name; 2. species scientific name; 3. release site (e.g., Sable Island); 4. release country; 5. tag serial number(s) and PTT ID(s). Use whatever method for obtaining these metadata from the researcher works for you.
+
+### Data access
+Ensure you have a Wildlife Computers (WC) Portal account & a security key pair set up (see 30_near_time_qc_process). Ask the researcher to setup sharing for their tag datasets via the WC Portal. The data owner(s) will need the email address the node manager used for their WC Portal user account. If the researcher does not know how to do this, refer them to the information on p. 19 in [document (p 19)](https://static.wildlifecomputers.com/Portal-and-Tag-Agent-User-Guide-2.pdf).
+
+Once data sharing is setup, within R you can verify access to the researcher's data via the WC Portal API using the ArgosQC utility function `wc_get_collab_ids`:
+```
+ArgosQC:::wc_get_collab_ids((a.key = "...", s.key = "...")
+```
+  Where the `a.key` and `s.key` values are your WC access and secret key pair. Executing this function with R returns a data.frame of all data owners' (collaborators) ID's and email addresses who have set up data sharing with the node manager:
+    ![](../fig/wc_owner.ids.png){width=300}
+
+If this function does not return a data.frame (or results in an error) then data sharing has not been setup correctly in the WC Portal and you will need to troubleshoot with the researcher.
+
+## How to use the metadata to create a config file
+All details for constructing `ArgosQC` config files are in this Jupyter notebook: `ArgosQC_WildlifeComputers_Project_Config`
+
+## How to push that config file somewhere so it can be processed regularly by the RT process
+Details on how to do this are in this Jupyter notebook: `ArgosQC_WildlifeComputers_Project_Config`
+
+## How to process a dataset that is no longer real-time - delayed-mode
+I can fill this in assuming the node-manager is going to use the fully automated QC on tags that are no longer active, but explaining how to do an interactive delayed-mode QC workflow is an in-person training session (a hands-on workshop) because it requires a number of decisions to be made based on intermediate outputs from individual ArgosQC functions.
diff --git a/fig/wc_config_akey_skey.png b/fig/wc_config_akey_skey.png
diff --git a/fig/wc_config_model_params.png b/fig/wc_config_model_params.png
diff --git a/fig/wc_config_owner.id.png b/fig/wc_config_owner.id.png
diff --git a/fig/wc_config_tag.list.png b/fig/wc_config_tag.list.png
diff --git a/fig/wc_dataset_uuids.png b/fig/wc_dataset_uuids.png
diff --git a/fig/wc_owner.ids.png b/fig/wc_owner.ids.png
diff --git a/fig/wc_portal_account_settings.png b/fig/wc_portal_account_settings.png
diff --git a/fig/wc_portal_create_account.png b/fig/wc_portal_create_account.png
diff --git a/fig/wc_portal_login.png b/fig/wc_portal_login.png
diff --git a/fig/wc_portal_security_keypair.png b/fig/wc_portal_security_keypair.png
diff --git a/fig/wc_qc_lat_ssmfit.png b/fig/wc_qc_lat_ssmfit.png
diff --git a/fig/wc_qc_map1.png b/fig/wc_qc_map1.png
diff --git a/fig/wc_qc_map12.png b/fig/wc_qc_map12.png
diff --git a/fig/wc_qc_map3.png b/fig/wc_qc_map3.png
diff --git a/fig/wc_qc_map6.png b/fig/wc_qc_map6.png
diff --git a/fig/wc_qc_map_reroute.png b/fig/wc_qc_map_reroute.png
diff --git a/fig/wc_tag.list.png b/fig/wc_tag.list.png