--
You received this message because you are subscribed to the Google Groups "iNaturalist" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inaturalist...@googlegroups.com.
To post to this group, send email to inatu...@googlegroups.com.
Visit this group at https://groups.google.com/group/inaturalist.
For more options, visit https://groups.google.com/d/optout.
I totally get the obs number thing... I pin butterflies/moths, and I will write down the obs number on a little slip to “follow” the moth around until it is finally labelled up completely. Also, soft-bodied specimens in vials get the obs number written on them until the label for inside the vial is printed. The labels are small, and include the obs number too, so iNat can be consulted for much more detail about the specimen than is represented in the label. iNat is effectively my fieldbook now... In chrome, I can double click on the obs number part of the url, and it just selects the number, then ctrl-c to copy and ctrl-v to paste, so it is not too difficult. I imagine in the app it would be very different!
Also, when we tie observations into a set, we use a field called “Similar observation set” and often just make it the obs number of the first observation in the set. This is terrific for lifecycle following (raising on) as well as for repeat visits to the same tree for seasonal variations etc... and I think this would help with the connecting of obs in mycological studies:
https://inaturalist.nz/observation_fields/9207
and a great example of it in action (I have clicked the field and selected “view observations with this field and value”)
and one of my examples (note: I had to tweak the filters to get all three to show, as some are marked “captive”):
This “Similar observation set” is not just restricted to using obs numbers, although you are guaranteed a unique key if you do use it! You can use more descriptive ties, such as “Undescribed salticid from Southland” to tie up observations of a similar looking undescribed species that keeps popping up... then if it ever gets described, we have an easy way to go back and review them all!
I like the shared observation idea... I think it needs careful consideration, as it could introduce problems that are unexpected. What happens if the observation owner deletes the observation? As far as skewed distributions etc... that already happens just by virtue of unusual things get observed, everyday mundane do not... but yes... we have certain birds nesting in high traffic areas that get photographed dozens of times a day, especially when there is a school trip that visits that location.
Another possibility, and it would take coordination and deliberate action... is for the first observer to make theirs the main observation, and the others to add a field “Count=0” so that it can be factored into distributions (I do this when I notice I am doubling up on someone elses observation). Each get’s the taxa counted towards lifelists etc, without skewing data. They could even include the field “Similar observation set” with the first obs number as the link. It is unlikely that this would catch on and become a standard practise though...
cheers
Mark Tutty
kiwif...@gmail.com
You received this message because you are subscribed to a topic in the Google Groups "iNaturalist" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/inaturalist/Z0CsgQzjxis/unsubscribe.
To unsubscribe from this group and all its topics, send an email to inaturalist...@googlegroups.com.
To post to this group, send email to inatu...@googlegroups.com.
Visit this group at https://groups.google.com/group/inaturalist.
For more options, visit https://groups.google.com/d/optout.
--
I’m with Christian, Tony... there are times when having the obs# is very handy, and accession numbers or whatever are either not available, or problematic. I see accession numbers as being a great way to tie multiple observations into describing the same organism (ie to make it explicit that they do so), but there are times when you want to link the other way, ie at the organism itself, to tie back to a specific observation. Obs# is then the best way to do so, as it is unique to the observation.
As an example, I raise on moth larvae, and the collecting event is described in an observation, let’s say obs#1001. I might make several observations subsequent, showing different instars and the dates those occurred, as well as date of pupation and eventual emergence. In fact, the original collecting event may even be of an egg that I witnessed being laid... so the “sequence” might encompass all life stages. When it comes time to pin the adult out into the reference collection, it might receive an accession number (not in my case though), but invariably the most useful reference I can make is back to the collecting event, so I use the obs# of the collecting event AS MY ACCESSION NUMBER!
Accession numbers are just a way to tie back to journal and record entries to find out about an item in the collection. If we use iNaturalist as our collecting field book, and record all notes in the observations that we make, then it makes sense to tie back to those entries. Why create an additional UNIQUE KEY, when obs# already gives us that. I’ll admit, that losing such things as year components to numbering systems does lose a little of the “immediate info” obtainable from such numbers, but if you don’t need that, then it’s not a big deal.
cheers
Mark Tutty
kiwif...@gmail.com
From: tony rebelo
Sent: Sunday, 23 December 2018 10:02 AM
To: iNaturalist
Subject: Re: [inaturalist] Recap from a big biodiversity event: Top5Most-Wanted Features
1. iNat observation field search URLs: Yes it is clunky, but trivial to learn.
--
You received this message because you are subscribed to the Google Groups "iNaturalist" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inaturalist...@googlegroups.com.