From ef7c2b814c05526f8e62c1166a4281380c516683 Mon Sep 17 00:00:00 2001 From: goddesswarship <103530016+goddesswarship@users.noreply.github.com> Date: Fri, 18 Oct 2024 15:52:51 -0700 Subject: [PATCH 1/2] Update data-integrity.md Updated Data Integrity page with new role permissions. --- docs/security/silo-security/data-integrity.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/security/silo-security/data-integrity.md b/docs/security/silo-security/data-integrity.md index b60ddb5..77202fd 100644 --- a/docs/security/silo-security/data-integrity.md +++ b/docs/security/silo-security/data-integrity.md @@ -8,15 +8,15 @@ Check your data for annotations that have been assigned to two or more different Look for duplicated annotations to clean up your data set. From here you can also see which bulk imports contributed to the duplicate annotations or if a single bulk import contained multiple duplicate annotations. -## Check Annotation iaClasses and MediaAsset States by Species (visible to admins only) +## Check Annotation iaClasses and MediaAsset States by Species (visible to staff and orgAdmins only) Look for old iaClasses on annotations and media assets that are stuck in a "pending" state. This can cause poor matching performance as they are ignored. The species list allows you to inspect the iaClass values assigned for each species as well as the detection state of media assets in the database. -## URL Access Security Checks (visible to admins only) +## URL Access Security Checks (visible to staff only) Look for URLs in Wildbook that should or should not be accessible to the public or users with certain roles. -## Wildbook Machine Learning Queue Monitoring (visible to admins only) +## Wildbook Machine Learning Queue Monitoring (visible to staff only) See a current snapshot and 24 hour historical review of the machine learning pipeline. This can help you determine if a specific user's uploads are contributing to a backlog. From c50049675ca959fd932622fd6a76fc9a5def7b8f Mon Sep 17 00:00:00 2001 From: goddesswarship <103530016+goddesswarship@users.noreply.github.com> Date: Mon, 21 Oct 2024 13:16:50 -0700 Subject: [PATCH 2/2] Update data-integrity.md --- docs/security/silo-security/data-integrity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security/silo-security/data-integrity.md b/docs/security/silo-security/data-integrity.md index 77202fd..de261db 100644 --- a/docs/security/silo-security/data-integrity.md +++ b/docs/security/silo-security/data-integrity.md @@ -8,7 +8,7 @@ Check your data for annotations that have been assigned to two or more different Look for duplicated annotations to clean up your data set. From here you can also see which bulk imports contributed to the duplicate annotations or if a single bulk import contained multiple duplicate annotations. -## Check Annotation iaClasses and MediaAsset States by Species (visible to staff and orgAdmins only) +## Check Annotation iaClasses and MediaAsset States by Species (visible to staff, admins, and orgAdmins only) Look for old iaClasses on annotations and media assets that are stuck in a "pending" state. This can cause poor matching performance as they are ignored. The species list allows you to inspect the iaClass values assigned for each species as well as the detection state of media assets in the database.