I’m getting the corrupt file popup in Firefox 132.0.2 on Windows 11
Edit:: Got it working on Edge and it’s awesome! (With 65,546 observations in my “to annotate” queue.)
It’s now possible to specify, for a Taxon ID action, whether you want it to be added as Disagreeing or not. If you do not select this box, it will behave as it does now (if you add any ID from a different taxon, it’s a disagreement; if it’s a lower or higher level taxon consistent with the current community ID it is supportive).
If you enable the box, it will now add the ID as a disagreement if it’s a higher level taxon consistent with the current community ID.
Thank your for this great tool. 
It has made annotations so much easier for me. It’s great for easily distinguishable things like life stages of Lepidoptera. I have been cranking away on those in my home state with it, making much better progress than without it.
I wish it was a little bit faster while processing (also seems to stop/slow down when tab is in the background). But I guess it’s a limitation of the API?
2 Likes
Yes, the API has a rate limit so if you use the bulk action tool there are built-in cool-off timers. If those weren’t there it would attempt and fail a bunch of actions.
The fact that the operations stop when the tab is in the background is I believe a browser issue, not an API issue. I don’t know if it’s possible for me to change that setting. Suffice it to say that the extension is making its requests as fast as I know how to make that happen. Glad you’re getting good use out of it!
4 Likes
What constitutes a “valid taxon for all Add Taxon ID actions”?
‘Cumulopuntia boliviana boliviana’ fails.
Works fine for me. Are you using the latest version of the extension?
Just downloaded and installed the current version but it still fails to accept the name.
The name appears to be correct since when I select it from the drop-down the correct taxon page opens. If however, I use an abbreviation like “Cum bol bol” it isn’t expanded to the full name.
UPDATE: I have it working now but only by reading the code in function ‘showTaxonSuggestions’ did I realise to click the image rather than the name.
You should be able to click anywhere except the name–the name is a hyperlink to the species page to make it easier for you to double check that you have the right species.
Hi Megachile! Are you still taking requests for added features? I would LOVE it if you had the option to remove an observation from a project as well as add. It would be so useful for projects I curate…
3 Likes
I just came here to see if anyone had mentioned that! Removing things from projects can get really tedious. But I don’t know if it can be added, since you can’t do it from the identify page (…which is why it’s so tedious).
1 Like
I definitely am–I was just thinking recently if this might be feature-complete and at a point when I should think about shipping it to the extension stores but I want to make sure it’s as close to actually done as possible before I do that. Will get on this soon! In theory anything you can do through the browser is possible through the extension because it all uses the same API; I bet I can make this happen. Let me know if you have any other requests or ideas!
2 Likes
Just trying this for the first time and I am getting this error as well, Windows 10 and Firefox.
I’ve been using this extension heavily for months now and have been loving it.
One feature I’d appreciate - an option to keep the “Reviewed” box unchecked as part of a bulk action.
For example, if I want to bulk-identify a bunch of “Unknown” observations as “Fungi Including Lichens,” I personally like to keep the “Reviewed” box unchecked.
I know there are ways to make it happen through the browser, but it takes a bunch of extra steps. It’d be nice if it were an option in the extension!
Ah - here’s another suggestion!
It’d be nice to have a “Disable All Configurations” option/checkbox, to clear out all active configurations. Often I have a lot of active configurations, but want to disable them all and instead make some others active.
Here’s a bug that you might not have run into yet: for a while, I was using a mouse with a wobbly button that would send two clicks in quick succession, and your extension would respond by executing its action twice separately in ways that ought not be possible in iNaturalist’s design: for instance, adding an observation field twice to the same record when they ought to overwrite each other, or adding the same observation twice to the same project. I know the duplication was real because you could then hand-remove each of the duplicates independently. I later found that I could reproduce this behavior with a normal mouse if I clicked fast enough although normal double-click speed doesn’t do it.
Oh man, yeah. I don’t really have a suggestion for megachile, just sympathising with comradejon. What bugs me is having the default behavior for adding an observation field be to follow the observation. I now get gazillions of notifications of identifications for observations I didn’t identify, just added unrelated info to. I did suggest to the iNat team that they should add settings for more fine-grained control of reviewing and following behavior, and they said it was in the works, but it’s been a few years.
I suppose that control options for reviewing and following behavior could be added to all of the Metadata Tool’s configurations.
I actually have an important request: a standard keyboard shortcut to enable and disable bulk mode (you have one to show/hide the bulk action buttons, which is not of as much significance).
2 Likes
Very much agree with that.
I oft switch it on and off the check specific observations when something is not immediately clearly visible in the small image. Having a shortcut to do so woudl be super helpful
2 Likes
This should be easy to implement and I will get on it soon but I want to make sure you’re taking full advantage of the action set feature. If you find yourself wanting to switch back and forth between small subsets of your configs, don’t do it manually; make a config set for each of them and you can switch back and forth at will on the Identify page.
1 Like
Just added three new actions:
Mark as reviewed/unreviewed
Follow/unfollow
Withdraw ID
You can use them in any combination you see fit with other actions, but remember that the extension is just sending API calls in the order you tell it to. So eg if you include a taxon ID and a “mark as unreviewed” action, the resulting state depends on the order of those actions. When you do the taxon ID, iNat will mark the observation as reviewed automatically, so you need to put the “unreviewed” action after or it will be overwritten. Or for OF actions, make sure the “Unfollow” action goes after the OF input, not before.
Now that I say that: how annoying does that sound? Would it make more sense to create a global setting where the extension automatically appends an “unfollow” command after ANY OF action, or a “mark unreviewed” after ANY taxon ID action? etc? I think that would be more work but definitely doable if it seems like a priority.
1 Like