Hi iNaturalist community members,
This is Carrie Seltzer from my new email address—this week I joined the iNaturalist staff! I am thrilled to help this community continue to grow and connect more people to nature while enhancing our collective understanding of biodiversity.
Next week there will be an iNat staff retreat to plan future iNaturalist development. In preparation for that, I would love to hear your thoughts about how the core team can best support you in your efforts to grow participation in your area (be it geographic, taxonomic, or otherwise).
I would appreciate if we keep the focus of this thread on the generation of ideas, without extensively repeating discussion of previous feature requests or changes, and without criticizing other people’s ideas.
Other ways to think about this prompt:
-How can we help you be a better, more effective multiplier of iNat activity?
-What can we do keep new, returning, or occasional users engaged?
Comments by the end of the day on Monday will be most helpful.
Thanks for all that you do to make iNaturalist an awesome, productive, and welcoming community.
Best,
Carrie Seltzer
An email newsletter that summarizes new iNat features, snippets of findings/research, links to the iNat blog posts.
More active curation of taxonomic issues and bad data so that it can be seen as a more reliable resource.
Refine the observation field/annotation concept further to reduce duplicate fields, making the data more useful to everyone, including potential external citizen science efforts/potential partners.
cassi
I am sure more might come to mind, but I will leave it there for now.
--
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+unsubscribe@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 support Charlie’s suggestion re allowing people to upload a single photo once, and use it for multiple observations (eg, a bee, the flower it’s getting nectar from, and a tree in the background). I’m indifferent about the solution (i.e. tags or something else), but the result is very desirable. It is a time-saver that users should find appealing.
Some solution to the group outing issue would also be a big win. Many people go out in groups and it is inefficient to require each member to enter a separate observation for the same thing. Also, consider of it from a data user’s perspective, you get somewhat degraded data that needs some filtering to be useful – eg. if 6 people in a group all report a Bald Eagle, were there really 6 eagles or 1 eagle reported 6 times? Think of a way to have a single entry for the eagle, allowing multiple people to include it in their observation list, and possibly allowing multiple observers to add photos to the single entry.
Several people have mentioned the annotation/field overlap/proliferation problem. Oddly, the unlimited choices in the field menu sometimes overwhelm people - e.g., not everyone wants to figure out which of the dozens of fields that include the word 'count' are correct, and few people want to spend time on something like this (and the search results seem random to me). The anyone-can-do-anything philosophy seems out of place, especially when there are organizations and individuals trying to collect and use data in a standardized format.
I think the most common complaint from new users is the lack of a saved location function. I see why it’s not that relevant for the phone crowd. But I sometimes think that the balance of development effort is tilted away from computer users, which is odd, because that’s where massive digital libraries tend to reside. Think about how your users could add observations faster and help them to do it.
-
I manage two successful projects here, but helping
new users adapt to the site, and directing them to our organization’s preferred
fields, asking them to join projects and share location data is a big use of my
volunteer time that I am increasingly reluctant to supply as iNat grows. I don't mind the role of project admin (posting journal notes, helping with IDs, welcoming people) but I feel that I am providing too much support that wouldn't be required if iNat had better documentation. And part of this may be that there are no advanced tips on how to do things like use fields and annotations (or why they are important). I know this has been raised before, but I believe
that different generations need different support to successfully get going. A friend told me about a bioblitz that she participated in last summer and what struck her was the generational divide between the younger people (phones, many with the iNat app) and the older crowd who tended to use cameras if they were documenting things. Pleas think specifically about ways to connect with those closer to retirement than graduation.
David
I'd like the different features to be better linked among the iNat sub-webpages:
- Facilitate adding observations to projects: when I want to add many sightings to a project, it would be neat to be able to add them directly via the project site by using filters (e.g. for taxa, places, tags etc), similar to the filters used for searching for observations. There should be no necessity to generate a csv file from your iNat observations to then re-upload them into a project.
- I am also missing a button where I can directly add one of my existing observations to one of my (non-life) lists. Also, it would be great to have other options for life lists (i.e. lists that get automatically populated), e.g. by defining a circle around your home without the need to generate a new place or by adding a tag (e.g species seen on the way to work).
- I am trying to be consequent with adding annotations, because I consider phenological input by the community to become very important data sets. But I cannot add those data directly when adding an observation (in contrast to options for tags, projects or fields, which I rarely use). I can only add annotations for already existing observations, so I have always to go back after uploading and might also miss/forget some of my observations. It would be great to have 'add annotations' also implemented in the mobile app versions.
- Another topic is the quite messy situation with the dashboard. I don't want to miss notifications or disagreeing IDs. In addition to the separation of personal messages on the one side and the rest of the notifications on the other side, as it is the status quo, I would prefer to have a better organized personal space with notifications thematically ordered, like (dis-)agreements with own observations, IDs made for others, comments, (responses to) flags... and make this all searchable. Maybe, within notifications, also assign different colors or symbols to confirming IDs vs. disagreements and coarser IDs, respectively.
Ideally, this all would become more like a forum structure, where the google group discussions would also merge into.
And please make it better visible (e.g. by unlinking it) when someone adds an ID plus makes a comment in the 'tell us why' field.
- Also, there is an overwhelming amount of valuable information hidden in the comments under an observation (like ID tips, additional information about that species, other user experiences etc.) Instead of bookmarking the link or to fave the obs, it would be nice to have the option to collect those contributions (like fave a certain comment within an obs) and tag it with keywords (-> creating a sort of iNat bibliography in your personal space).
Way to go, iNat team!
--
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+unsubscribe@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.