It might be worth a discussion if the ROONTAG (TAG) could get assigned externally, and in more than one way; in another thread I came up with
-
ROONALBUMTAG(in the sense of a Tag in the Roon UI) and ROONTRACKTAG
That way one had more flexibility for pre-organisation.
Thanks to the general state of classical related metadata it would help a lot if we could pre-fill all fields available in Roon (Instrumentation, Form, Period for example). It might become tricky with composition related fields.
But this also creates tremendous possibilities to confuse an import module; something the Roon team is probably not too keen to let happen.
An alternative route could be some API for this kind of stuff. If there’s really a need, an non-official import module (extension) will appear. Roon might still have to implement sanity checks on an API level, but no UI required. No support for imports via the API. Just a thought …