Task #10807 (new)
Opened 11 years ago
Last modified 8 years ago
Final DB modifications — at Version 6
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-5 |
Component: | Model | Version: | n.a. |
Keywords: | fs | Cc: | fs@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | FS Demo 4.3 |
Description (last modified by jamoore)
If we have time to perform further DB changes, the following would simplify much of the OriginalFile? and binary logic put in place for FS:
Mimetype
- register() should check for mimetypes
- originalfile super class so there's no mimetype??
- OriginalFile? extends BaseFile? to remove sha1, mimetype, etc.: Dropping several of the OriginalFile? fields would significantly simplify synchronization between the FS and the DB.
- Move DIRECTORY_MIMETYPE to constants.
- Mimetypes (including "Directory") should be compared to standards: There are various mimetypes relating to directories. Perhaps we could either use of those, or use an "application/vnn.openmicroscopy.dir" style
filesets
- add javaVersion to FilesetVersionInfo?. (And Python?) (see 888)
- Review all the version info set by python/Java/C++
- where to put tags during upload
- check for other definitions of "Reader" (with formatString.replaceAll)
Misc
- PixelsType?.MIN|MAX in database
Change History (6)
comment:1 Changed 11 years ago by mtbcarroll
comment:2 Changed 11 years ago by jamoore
- Description modified (diff)
comment:3 Changed 11 years ago by jamoore
- Keywords fs added
comment:4 Changed 11 years ago by jamoore
- Description modified (diff)
- Priority changed from major to critical
- Sprint changed from FS demo 4.x to FS demo 4.2
- Summary changed from Final OriginalFile modifications to Final DB modifications
comment:5 Changed 11 years ago by jburel
- Sprint changed from FS demo 4.2 to FS Demo 4.3
Moved from sprint FS demo 4.2
comment:6 Changed 11 years ago by jamoore
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Things like repositories and directories and whatnot should perhaps each have separate classes in the hierarchy.