The idea is that you can see who is viewing you journal posts, whether on profile or on project. The feature should only be accessible to the project admins.
Feature request details:
There should be a line graph, and then when you hover a specific date, then the people who saw it in that date should be visible. It can be useful in situations like:
You give a link to one of you journal posts and you want to know whether the person had seen it.
I am pretty sure staff have previously said analytics arenât/wonât be made available for projects or journal posts, but am coming up short with finding that post.
I would be strongly against this level of data being provided to people.
I didnât know if anyone read the journal posts I write for one project, until someone sent me an email complaining about something I had written. So at least I know one person reads it!
Data could be kept anonymous.
Visible only to the author of the journal post.
How many people have seen this?
Wonât happen - but I would also like to know, how many have already looked at this obs, and quietly abandoned an ID attempt? Is it worth me trying, when âso manyâ have despaired already? Especially when clearing the 10 year old backlog. Enquiring minds do want to know.
For the journal, maybe the same could be achieved with a âfavoriteâ icon at the end of the journal entry. We donât really know how they got to the journal entry (forums/external link/inat website/âŚ) so there wouldnât be a link where clicks can be tracked like that. But I often look for a way to favorite/like a journal entry I read. I will add a comment sometimes if I really want to let the author know how much I appreciate it, but if there were a favorite icon underneath Iâd click that much more readily. And the number of favorites (not names) could just be displayed next to it for everyone to see.
I routinely and deliberately right click/new tab in order to not be counted.
I think itâs a bad idea to provide that kind of data to users, it will only lead to people engineering their observations to maximize whatever metric is shown.
The question to ask is if itâs worth it to you. Do you enjoy keeping up with the observation, then do it. If not, no harm done.
People vary. Some will chase vanity metrics. Thatâs the same argument which is regularly rolled out against leaderboards - which I use - to find suitable @mentions each time.
But authors would like to follow trends. I use StatCounter for my blog. I check which pictures are downloaded - then check if and where they appear again. I check which of my links are clicked (any?) I check which site my readers come from, and get a steady trickle from iNat or the Forum (and vice versa since I include relevant iNat links in my blog posts) It is useful information to the author.
I have a link to the City Nature Challenge and am interested to see where the clicks come from. If the iNat journal were outsourced as the Forum is (to Discourse), we could have analytics.
i tend to agree that collecting raw view counts and/or allowing folks to see who has viewed their stuff is a bad idea. i wouldnât mind iNat saying generally how many people look at an average observation or an average journal post, but i donât think most people would be able to do anything useful with those kinds of metrics on specific observations and posts.
âŚ
that said, people who really want to track that kind of data should be able to do that on their own. for example, you could just add a small image file in your observation description or journal post, and if you control the image file, you should be able to count the number of times that image file is served up, which should be roughly equivalent to views of the particular observation or journal post. i think there used to be a free service that would serve up these image files for you and keep track of how many hits, but i forget what this service was called, and i donât know if they are still active.
This is not a feature weâll be implementing. Itâs not data we really keep, and not providing users view stats for their content is a choice iNatâs made for a long time, for the reasons others have brought up here.