-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a tag field to handle OMERO tags #1289
Comments
Can you explain in more detail what would need to change to support this? I don't have much experience of OMERO tags, but it sounds like what you're suggesting could either be handled entirely in the OMERO extension already (using QuPath's existing metadata support for project entries), or else could risk projects becoming more OMERO-specific (which I'd like to avoid). |
Actually, tags are one key-word annotation.
Maybe... I don't think it is optimal nut having the same value as the key could work, using existing QuPath's metadata |
Ah... makes sense.
Sounds sensible, but I wonder is it possible that people will then want tags with different interpretations? The alternative I'm thinking is to simply have a dictionary entry {
"omeroTags": "tag1, tag2, tag3"
} but I don't know whether it's safe to use a comma (or anything else) as a delimiter. Otherwise, I guess there could be a general Do you think either option is strongly preferable to the other? |
Yes, this is also true.
Actually, I already thought of the solution but our final goal would be to sort the images within the current project according to one or more tags.
I would rather go for this solution as I think it is the best way to make them independant and searchable. |
How would the sorting look? Would there need to be multi-level sorting? QuPath's current sorting logic based upon the 'metadata' dictionary is... not great. I don't think it can really increase in complexity without breaking, so my feeling is we should also think broadly about how projects are displayed, sorted, and incorporate both metadata and tags. |
Well, with the current way of sorting, I wasn't expect more than one-level sorting (i.e. sort by tag1, or tag2). I think both metadata and tag could follow the same sorting logic. The key(s) / tag(s) used to sort the images could be written in the project tab, like in this example. Also, having a default option to sort by image name would be nice :) |
Addresses one of the more minor requests in qupath#1289
Feature request
Issue
Metadata fields are perfectly suitable for OMERO Key-value pairs but there is no way to propertly handle OMERO tags in QuPath.
Description of the solution
As tags are very useful in OMERO to search for images, it could be great to also have a tag field in QuPath.
Tag field attributes
The text was updated successfully, but these errors were encountered: