Task #7069 (new)
Opened 12 years ago
Last modified 8 years ago
Annotation and namespace
Reported by: | jburel | Owned by: | jburel |
---|---|---|---|
Priority: | blocker | Milestone: | Metadata |
Component: | General | Version: | 4.4.8 |
Keywords: | n.a. | Cc: | omero-team@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Annotation can have a namespace set.
In the Attachments tab, the smartfolders related to given ns are harcoded e.g. movies, attachments.
Most of the attachments will end in other.
Requirement:
- need to be able to retrieve list of available ns for a given type of annotations.
Scanning the annotation table with all available ns is not an option b/c it can be very large.
The namespace table should be populated each time a new annoation with ns is added. Not possible to indicate the type of annotation the namespace is for.
Change History (5)
comment:1 Changed 12 years ago by jburel
- Cc omero-team@… added; hic@… removed
- Milestone changed from OMERO-Beta4.4 to Future
comment:2 Changed 11 years ago by spli
- Milestone changed from Future to OMERO-5
- Priority changed from major to blocker
- Version set to 4.4.8
comment:3 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Metadata
comment:4 Changed 8 years ago by mtbcarroll
One shouldn't have to scan the annotation table: both the discriminator and ns columns are indexed with B-Trees. Does HQL like, say, SELECT DISTINCT ns FROM CommentAnnotation take far too long in large databases? If so it might be worth checking what SQL Hibernate is actually generating.
If necessary one might try actually partitioning the annotation table (it's at least as easy on Oracle as it is on PostgreSQL) or creating a multicolumn index on (discriminator, ns); I am not sure what effect either might have.
comment:5 Changed 8 years ago by mtbcarroll
These days our triggers do provide,
The namespace table should be populated each time a new annotation with ns is added.
Bumping this after talking to JM. The analysis tools which are currently being developed will result in lots of attachments being created to hold the results. Setting an appropriate namespace will allow these annotations to be found/listed/categorised in the clients, but for efficiency annotations.ns should be changed from a string to a foreign key referencing the namespace table.
This is a breaking change, so a decision for OMERO5 needs to be made soon.