Thanks for raising this @graffte - I see how that can be quite tedious. I’m curious what you think about the UI for adding assets to a log that opens a modal for searching and selection a few assets in bulk (this is called the “Entity browser” widget). It’s not exactly the same as V1, but do you think this would be an improvement over the “Add another item” UI?
As you described assets can be added to a log for different reasons (asset, location, equipment, parent…) @BOTLFarm raised a similar question in another thread early in the v2 lifecycle. I’m afraid we’ve let this slip through the cracks while working on the foundation of v2, but now is a great time to circle back to this (very!) important UI consideration.
I’d like to highlight the end of @mstenta response here: Adding assets to a log, 2.x - #3 by mstenta
If we made Entity Browser the default, we would want to review all the fields that would be affected by that (probably in both farmOS core and known contrib modules) to see if that would adversely affect any of them.
I tend to be in favor of making Entity Browser widget the default. I think it makes sense for most asset reference fields (asset, location, equipment) but I see how a simpler widget (text search + add another) can be sufficient for simpler asset references (parent, mother, group).
In the end I don’t think there is a right or wrong answer though, it likely comes down to the use-case and user preference. With that in mind I’m curious if we could make this choice configurable by users. Ideally such a configuration could be on a per-field basis - I don’t think the same widget is the best choice for all of these asset reference fields