Hi Russell,
Thanks for your answer. I also thought of the workflow you just described.
It works but i choose to avoid this solution for a few reason:
-first, like you said, you duplicate effort/data (not so much effort if you use the auto tag app though).
-secondly, we try to teach our users to use tags to classify/look for their images, but we want them to be as universal as possible (official nomenclature for strain/mutant for example and limitate the use of more abstract tags such as "good quality image" that not everyone might name like this). The point is to underscore the power of omero when it comes to translational research. By that i mean how users of a same group can look into each others data and are able to make comparaison. Ex: data that could have the same dye and gene tag but different tissues tags underlining a difference of effect related to the tissue. Moreover we tell them that the name of their project/dataset/images is their free space so people even if they can access the generic tags like gfp, they would get confused when they have to choose a project tag cause the project's name of their colleagues might not make any sense for them. In the end they would have to go through every project to get an idea of what it is, then specifically select the few one they want to compare.
Of course it can be used to look into your own data since you know about your own tags.
I apologize if what i said is not clear enough.
Hi wmoore,
Thx for your answer. I did not know you could do that on omero and i ll be sure to inform the users. It might be more useful cause you could make abstraction of what the tag name of project/dataset means just by running the script once with every dataset selected to get an overview of all available tags by dataset, then run it a second time with only the dataset that you want to compare
The only pros is that if there are too many dataset, selecting them all would make the analysis of tags troublesome and if you select them 2 by 2 to simplify this task it might be time consuming. Of course this problem arises just when you look into someone else data since you usually know what kind of images/tags you ll find in your own data.
Best,
Alex.