Thank you for your suggestions.
- Make the yaml file optional, with the default behavior mapping all attributes as if they were string values (I suspect this will be the case 100% of the time for our use cases).
Thanks, I have captured the idea of a default configuration allowing to convert tables into Key-Value pairs (MapAnnotations) in the omero-metadata library - see https://github.com/ome/omero-metadata/issues/33 . Note that “bulk annotations” mentioned in that context are OMERO.tables.
Please note that the Key-Value pairs (MapAnnotations), which are searchable, at the moment will only support strings (numerical values can be entered, but they will be stored as strings). This might be the reason why using OMERO.tables might be sensible - see OMERO.parade https://pypi.org/project/omero-parade/ - a data mining tool which we are developing. OMERO.parade can filter images and create graphs according to (preferably numerical) values stored in OMERO.tables.
- Add a script to do the mapping on the web, possibly as an option in the current populate metadata script. Since the yaml file is optional, this will be made a bit easier. If you really, really need the yaml file, then it could be included as an attachment.
We have captured your suggestion - see https://github.com/ome/scripts/issues/151 and will have a look at implementations. In the meantime, please note that the community already came up with scripts (server-side scripts, just like the Populate metadata script you are exploring.) These are to be found in https://github.com/evenhuis/omero-user-scripts, more precisely https://code.research.uts.edu.au/MIF/OMERO-instructions/wikis/organising_data/csv/Managing-Key-values-with-csv-files#4-add-key-values-pair-from-the-csv , and https://github.com/saeri-ims/omero-docker-compose/tree/master/custom_scripts/for_tags_adminONLY .
You might find it worthwhile to study, adjust and overtake those scripts for your use case.
All the best
Seb and Petr