Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #4109 (closed)

Opened 11 years ago

Closed 7 years ago

Investigate JHOVE for file format recognition

Reported by: crueden-x Owned by: crueden-x
Priority: trivial Milestone: Unscheduled
Component: Bio-Formats Version: 5.0.1
Keywords: n.a. Cc: FCORNELI@…, mtbcarroll, jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


The JHOVE library from Harvard is an extensible framework for format validation. Though the current Bio-Formats validation solution (IFormatReader.isThisType) works quite well, there may be advantages to restructuring it within the JHOVE framework, and the possibility should be explored.

Change History (5)

comment:1 Changed 11 years ago by jmoore

imported from bio-formats:#358

comment:2 Changed 11 years ago by crueden-x

  • Owner changed from curtis to crueden-x
  • Reporter changed from curtis to crueden-x

comment:3 Changed 9 years ago by jmoore

  • Cc mtbcarroll jburel added

Adding Mark in case this (or related projects) may be useful in the fight against multipe-OS file type/name issues we're looking at. Frans, if you would like to be removed from this ticket, please let us know.

comment:4 Changed 9 years ago by mtbcarroll

I think that JHOVE basically just looks at the contents of files, one by one, on the local machine, and doesn't have to worry at all about issues relating to migrating the whole filesystem fragment to a system on a different OS/FS before properly finding the sets of related files, but that is just a first impression and I would be very glad to see it corrected.

I do like how Bio-Formats multi-file-format readers can try to normalize for both "/" and "\" path separators in constructing a File object, and at least all the extensions that need to be recognized are all just ASCII characters. Perhaps there is some JHOVE-like thing (or JHOVE add-on) that can be quite clever about multi-file formats where the reference in the contents of one file to a companion file was originally constructed on a very different system.

comment:5 Changed 7 years ago by crueden-x

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to 5.0.1

It makes more sense to me to write a JHOVE extension that uses Bio-Formats (or better: SCIFIO). But since we don't have an explicit use case for that, I'll argue YAGNI and close this as wontfix. If it becomes clear how JHOVE integration would be useful, we can definitely look into doing this at that time, though.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.64538 sec.)

We're Hiring!