Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InsectAI extension of Camtrap DP #389

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

InsectAI extension of Camtrap DP #389

wants to merge 2 commits into from

Conversation

peterdesmet
Copy link
Member

Draft of the suggestions made at the InsectAI writing retreat, by @kbubnicki.

PS: I made this into a PR to allow for comments.

{
"name": "annotationID",
"description": "Unique identifier of the annotation.",
"skos:broadMatch": "http://rs.tdwg.org/dwc/terms/occurrenceID",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a better match is http://rs.tdwg.org/dwc/terms/identificationID. To be explored.

{
"name": "annotationSourceID",
"description": "Identifier of a previous annotation used as input, providing the provenance of annotations made by either machines or humans.",
"skos:broadMatch": "http://rs.tdwg.org/dwc/terms/occurrenceID",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either a match with identificationID or no match.

},
{
"name": "annotationLevel",
"description": "Level at which the annotation was classified. `media` for media-based annotations that are directly associated with a media file (`mediaID`). These are especially useful for machine learning and don't need to be mutually exclusive (e.g. multiple classifications are allowed). `event` for event-based annotations that consider an event (comprising a collection of media files). These are especially useful for ecological research and should be mutually exclusive, so that their `count` can be summed.",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last part of definition might need to be updated, both in annotations (multiple allowed) and in observations (multiple not allowed).

"example": "MegaDetector V5"
},
{
"name": "classifiedByModelID",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tempted to call this classifiedByID or modelID. If so, update foreignKeys too.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think it makes sense to have this field in observations.

@@ -113,7 +113,8 @@
"principalInvestigator",
"rightsHolder",
"publisher",
"contributor"
"contributor",
"funder"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, but keep contributor as last or first (default).

@@ -173,6 +173,15 @@
"unit": "°",
"example": -90
},
{
"name": "cameraSettings",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move after cameraHeading

@@ -173,6 +173,15 @@
"unit": "°",
"example": -90
},
{
"name": "cameraSettings",
"description": "Other custom camera settings used for the deployment. Formatted as a valid JSON object.",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"description": "Other custom camera settings used for the deployment. Formatted as a valid JSON object.",
"description": "Other camera settings used for the deployment. Formatted as a valid JSON object.",

"constraints": {
"required": false
},
"example": "{\"setting1\":200,\"setting2\":true}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An actual example might support the need for this term.

@@ -215,6 +215,28 @@
"unit": "m/s",
"example": 1.75
},
{
"name": "individualLength",
"description": "Length of the observed individual identified by `individualID`. Expressed in centimetres.",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be expressed in meters, like all length-based terms.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This type of data might be better served with a measurement or fact extension.

"required": false,
"minimum": 0
},
"unit": "cm",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"unit": "cm",
"unit": "m",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants