Projected Image sha1

[jburel]

sha1 not created for the projected image. "pending" in DB

[jburel]

not top priority pushing

[jburel]

Moving to 5.1.0 for consideration. Pending is still entered in the DB

[jamoore]

for reference, "Pending..." in ome/services/PixelsImpl.java

[mtbcarroll]

Interesting scoping questions here. For instance, ought there be a choice of checksum algorithm? Is it still important to hash the pixel values if we switch to having a Bio-Formats reader for Pixels files and turn these images into more like a normal FS image with a file hash? Are we likely to do that anyway?

[jamoore]

• initially, no choice.
• you could still use the hash if we migrated to an OriginalFile?, so that's fine.
• not *highly* likely that we'll do the pixels reader, but we'll have to better scope 5.2 for that.

[jamoore]

I could imagine a fix for 5.1.2 but it won't be as flexible or clear as we'd like it to be (needing a DB upgrade to make sha1 --> hash nullable). Since we've spent time disabling sha1'ing for 5.1, pushing to 5.2, so we don't undo our work.

[jamoore]

Splitting due to milestone decoupling.

[jburel]

Milestone OMERO-5.2.1 deleted

[jburel]

Milestone OMERO-5.2.2 deleted

[jburel]

Something to consider for 5.3 i.e. DB cleanup