Announcing the Universal Metadata Tool Beta (by @megachile)

This tool is DELIGHTFUL! I’m working with a big dataset of Observation Fields for pollinators on flowers, and it’s a slog. So many different projects source from different Observation Fields, so I need to tag the same plant multiple times. Fortunately, I already have 5,500 observations tagged, so I know what the most popular plants are. I turned those into buttons!
Here’s how I used your tool:

This is saving me SO much type and irritation, though we’ll see how soon people start muting me for spamming their observations…
Thank you for your work!

So glad to see your face here and to know my work has helped you! Please let me know if there are things I could do to make it even easier.

Actually! The one issue I’ve encountered is that, when I’m, say, adding a “Mark as Reviewed” action to ~40 buttons, the one hiccup I have is that “Add Action” is right next to and same colored as “Update Configuration”. It’s a small thing, but would you consider changing the color to help me stop clicking the wrong dang button?

No worries if not, it’s definitely a quality of life request, not an urgent need

Done! Added a little extra dead space between the buttons and colored everything more appropriately. Good suggestion, thank you.

Wow. :exploding_head:
I’ve been dreaming of a tool like this for a long time. It blew me away that:

  • It exists,
  • It’s even better than what I imagined (more customizable and well thought-out),
  • It was quite easy to install (maybe a short installation tutorial could help some users, but I might have missed it in the 200+ comments above) and easy to set-up!

Anyway, thank you so much for creating and sharing this – it’s exactly what I needed! :heart_eyes:

A new slight bug, with the Alt-S shortcut. It does cycle through my different buttons sets, but some are always lacking. For instance here, I am positioned on the “Musa sauvage” set, and Alt-S only displays alternatively “Ensete” and “Autres actions”…

Maybe an encoding issue for the titles of the sets? I have some French accents here. But Default Set is not appearing either.

[Edit] Actually no: if I’m set to ‘Musa cultivés’ then the other sets displayed are “Zingibérales” and ‘Default Set’. So in fact, it skips every other set and skips one when you click on it.

Should be fixed now. Basically the switcher was getting called twice on every shortcut so it was guaranteed to skip a set.

Is it possible to add the ability to add tags with this tool? I use tags a good bit to sort my own observations and this would definitely be helpful.

I read about this tool when it came out. But I just now got around to trying it out. What a life/time saver. This thing is amazing. Thanks so much for creating it.

Aside from what appears at the top of the topic, is there a “users guide” or “faq” somewhere? I’ve been using it, but I can’t seem to get the hang of how the bulk operations work. I also have questions about other things, will it only add fields with fixed values? For something like “count”, one would need to be able to enter a value (though I suppose it’s possible to create buttons for a set of frequently added values).

Yes, you should be able to add buttons that add specific text strings but you do have to specify them in advance. I suppose in theory it would be possible to make the tool give you an on-the-spot input box to type things into, Opus might be able to handle that easily now. I’ll put it on my list for next time I work on improvements. But no promises :D

Thanks for this tool, it’s so great not having to click as much! I can’t seem to make the “observation field” work - as I type in the name of the field, the fields appear, but it won’t actually select the field, and then I’m unable to type anything in Field ID. What am I doing wrong? Thanks again!

cool tool.

I noticed addAnnotation just uses /annotations and tries to send given field values. As there will be cases where an annotation can exist - rightly or wrongly annotated - using response in someway and then using post /votes/vote/annotation/{id} would help here better for existing annotations voting automatically.

maybe even additional option of something like “mention annotator in comment on disagreements” - which sends preformatted comment from annotations options like “lifestage adult not nymph @einsum. also you can correct too - owner (without tag) “ with such collisions, only if suggested annotation collides with suggested annotation

so instead of only silent voting which we have no idea if ur feature request gets solved, we take the only available proactive action of correction tag for now.

Hmm I like this idea, it’s creative and addresses a real issue. But I am a bit hesitant to automate the power to tag users in bulk. I suppose it’s already technically possible to do this with the comment feature but making it even easier idk. . . I’ll think about it

@Megachile it looks like you’ve moved to a standalone repo and the download link no longer works. Can you update the original post to point to https://github.com/Megachile/inathelperJS/archive/refs/heads/main.zip please?

I just need you to know that I use this tool pretty much daily and I appreciate you so much.

Today I changed my life by making an “Alive - Organism - Adult - Mark as Reviewed” Annotation button and the number of clicks it will save me is astronomical. I can’t believe I didn’t think of this sooner.

Currently, I’m doing spring phenology and rocking this:

Just tried to install it on Firefox and got the following error:

It’s not letting me select the manifest.json file but rather only letting me pick a .zip file

I couldn’t get it to work on Firefox, so now use Edge when I want to use this tool. That has essentially made Edge the app that runs the tool as I don’t use Edge otherwise. Works for me.