Difference between revisions of "JHOVE (Harvard Object Validation Environment)"
Prwheatley (talk | contribs) |
|||
| (23 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Infobox tool |
| − | |purpose=JHOVE | + | |image=JHOVE.gif |
| − | + | |purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects. | |
| − | |homepage= | + | |homepage=http://jhove.openpreservation.org/ |
|license=GNU Lesser General Public License (LGPL) | |license=GNU Lesser General Public License (LGPL) | ||
| − | |platforms=JHOVE should be usable on any UNIX, Windows, or OS X platform with an appropriate J2SE installation. It should run on any operating system that supports Java 1. | + | |platforms=JHOVE should be usable on any UNIX, Windows, or OS X platform with an appropriate J2SE installation. It should run on any operating system that supports Java 1.5 and has a directory-based file system. |
| + | |formats_in=EPUB, GIF, JP2, JPEG, PDF, PNG, PREMIS (Preservation Metadata Implementation Strategies), TIFF, WARC, XML, AIFF, WAVE, GZIP, ASCII, UTF-8, HTML, MP3 | ||
| + | |function=Encryption Detection, File Format Identification, Metadata Extraction, Validation | ||
}} | }} | ||
| − | + | {{Infobox tool details | |
| − | + | |ohloh_id=JHOVE | |
| − | + | }} | |
| − | + | == Description == | |
| − | + | [http://jhove.openpreservation.org/ JHOVE] allows data curators to verify the file formats of the digital objects in their repositories. The analysis consists of three functions: identification, which determines the object’s format; validation, which checks whether the object conforms to its format’s technical norms; and characterization, which gives a report of the object’s salient properties. | |
| − | |||
| − | |||
| − | = Description = | ||
| − | [http:// | ||
Detailed information can be found in the DCC [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study]. | Detailed information can be found in the DCC [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study]. | ||
| − | ====Provider==== | + | |
| − | + | ==== Provider ==== | |
| − | ====Licensing and cost==== | + | [http://openpreservation.org/ Open Preservation Foundation] |
| + | |||
| + | ==== Licensing and cost ==== | ||
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free. | [http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free. | ||
| − | + | ||
| − | + | ==== Platform and interoperability ==== | |
| − | |||
| − | ====Platform and interoperability==== | ||
JHOVE is implemented using Java 2 Standard Edition 5.0 (JDK 1.5). It was designed incorporating an API, which can be used on its own to create compatible tools and applications. Developers wishing to recompile the JHOVE source code will require Apache Ant. | JHOVE is implemented using Java 2 Standard Edition 5.0 (JDK 1.5). It was designed incorporating an API, which can be used on its own to create compatible tools and applications. Developers wishing to recompile the JHOVE source code will require Apache Ant. | ||
| − | ====Functional notes==== | + | |
| + | ==== Functional notes ==== | ||
JHOVE includes modules for the following 12 format types: AIFF; ASCII encoded text; GIF; HTML; JPEG; JPEG2000; PDF; TIFF; UTF-8 encoded text; WAVE; XML; and arbitrary bytestreams. Three of these formats (AIFF, GIF and JPEG) will not be supported by JHOVE2, while a further two (JPEG2000 and PDF) are not currently supported by JHOVE2 but may be in future. HTML is not directly supported by JHOVE2 but can be processed either as SGML or XML. | JHOVE includes modules for the following 12 format types: AIFF; ASCII encoded text; GIF; HTML; JPEG; JPEG2000; PDF; TIFF; UTF-8 encoded text; WAVE; XML; and arbitrary bytestreams. Three of these formats (AIFF, GIF and JPEG) will not be supported by JHOVE2, while a further two (JPEG2000 and PDF) are not currently supported by JHOVE2 but may be in future. HTML is not directly supported by JHOVE2 but can be processed either as SGML or XML. | ||
A number of limitations have come to light since JHOVE was first released, many of which are addressed with the JHOVE2 project. Currently, identification and validation are linked, with successful identification dependent on the validation process. This means that any trivial error in the validation process can result in an object failing to be identified. In addition, JHOVE cannot analyze objects that are comprised of multiple file formats. | A number of limitations have come to light since JHOVE was first released, many of which are addressed with the JHOVE2 project. Currently, identification and validation are linked, with successful identification dependent on the validation process. This means that any trivial error in the validation process can result in an object failing to be identified. In addition, JHOVE cannot analyze objects that are comprised of multiple file formats. | ||
Developers have also remarked that working with the API is difficult. | Developers have also remarked that working with the API is difficult. | ||
| − | ====Documentation and user support==== | + | |
| + | ==== Documentation and user support ==== | ||
The JHOVE website includes an excellent introduction and [http://hul.harvard.edu/jhove/using.html tutorial]. It also provides detailed specifications for its modules. | The JHOVE website includes an excellent introduction and [http://hul.harvard.edu/jhove/using.html tutorial]. It also provides detailed specifications for its modules. | ||
The [http://sourceforge.net/projects/jhove/ SourceForge] code repository includes a forum, which seems to be used only sporadically. It also hosts a mailing list and the usual facilities for filing bug reports, feature requests and support requests. | The [http://sourceforge.net/projects/jhove/ SourceForge] code repository includes a forum, which seems to be used only sporadically. It also hosts a mailing list and the usual facilities for filing bug reports, feature requests and support requests. | ||
| − | ====Usability==== | + | |
| + | ==== Usability ==== | ||
While installation and configuration can be complex, the Swing-based GUI allows for relatively easy use. JHOVE can also be invoked with a command-line interface. | While installation and configuration can be complex, the Swing-based GUI allows for relatively easy use. JHOVE can also be invoked with a command-line interface. | ||
| − | ====Expertise required==== | + | |
| + | ==== Expertise required ==== | ||
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Familiarity with metadata outputs is also essential. | Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Familiarity with metadata outputs is also essential. | ||
| − | ====Standards compliance==== | + | |
| − | JHOVE was designed to integrate into the Ingest function of an OAIS. The validation process compares objects’ formats against ISO standards. | + | ==== Standards compliance ==== |
| − | ====Influence and take-up==== | + | JHOVE was designed to integrate into the Ingest function of an OAIS. The validation process compares objects’ formats against ISO standards. |
| + | |||
| + | ==== Influence and take-up ==== | ||
The SourceForge website reports approximately 11,400 downloads from the release of JHOVE 1.1 from 2008 to July 2013. Use of JHOVE is widespread in the digital preservation community. | The SourceForge website reports approximately 11,400 downloads from the release of JHOVE 1.1 from 2008 to July 2013. Use of JHOVE is widespread in the digital preservation community. | ||
JHOVE is integrated within the Planets Testbed and Plato. | JHOVE is integrated within the Planets Testbed and Plato. | ||
| + | |||
| + | |||
| + | == User Experiences == | ||
| + | <!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --> | ||
| + | * '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf | ||
| + | * '''Gary McGath:''' https://fileformats.wordpress.com/tag/jhove/ | ||
| + | * '''KOST-CECO:''' Used in [[KOST-Val]] as a validation module for TIFF files. | ||
| + | * '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]] | ||
| + | * '''PDF Association:''' http://www.pdfa.org/2014/12/ensuring-long-term-access-pdf-validation-with-jhove/ | ||
| + | * '''Open Preservation Foundation: JHOVE issues and error messages:''' http://wiki.opf-labs.org/display/Documents/JHOVE+issues+and+error+messages/ | ||
| − | = | + | == Development Activity == |
| − | == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed by the OPF [http://jhove.openpreservation.org/] as it supports some common formats that JHOVE2 does not. | |
| − | + | All development activity is visible on GitHub: http://github.com/openpreserve/jhove/commits | |
| − | + | ||
| − | + | ==== Release Feed ==== | |
| + | Below the last 3 release feeds: | ||
| + | <rss max=3>https://github.com/openpreserve/jhove/releases.atom</rss> | ||
| − | === | + | ==== Activity Feed ==== |
| + | Below the last 5 activity feeds: | ||
| + | <rss max=5>https://github.com/openpreserve/jhove/commits/master.atom</rss> | ||
| − | |||
| − | |||
| − | + | === About Formats === | |
| + | JHOVE do only read the format itself, not the spesification as such | ||
Latest revision as of 14:22, 12 August 2022
Description[edit]
JHOVE allows data curators to verify the file formats of the digital objects in their repositories. The analysis consists of three functions: identification, which determines the object’s format; validation, which checks whether the object conforms to its format’s technical norms; and characterization, which gives a report of the object’s salient properties. Detailed information can be found in the DCC JHOVE Case Study.
Provider[edit]
Licensing and cost[edit]
GNU Lesser General Public License – free.
Platform and interoperability[edit]
JHOVE is implemented using Java 2 Standard Edition 5.0 (JDK 1.5). It was designed incorporating an API, which can be used on its own to create compatible tools and applications. Developers wishing to recompile the JHOVE source code will require Apache Ant.
Functional notes[edit]
JHOVE includes modules for the following 12 format types: AIFF; ASCII encoded text; GIF; HTML; JPEG; JPEG2000; PDF; TIFF; UTF-8 encoded text; WAVE; XML; and arbitrary bytestreams. Three of these formats (AIFF, GIF and JPEG) will not be supported by JHOVE2, while a further two (JPEG2000 and PDF) are not currently supported by JHOVE2 but may be in future. HTML is not directly supported by JHOVE2 but can be processed either as SGML or XML. A number of limitations have come to light since JHOVE was first released, many of which are addressed with the JHOVE2 project. Currently, identification and validation are linked, with successful identification dependent on the validation process. This means that any trivial error in the validation process can result in an object failing to be identified. In addition, JHOVE cannot analyze objects that are comprised of multiple file formats. Developers have also remarked that working with the API is difficult.
Documentation and user support[edit]
The JHOVE website includes an excellent introduction and tutorial. It also provides detailed specifications for its modules. The SourceForge code repository includes a forum, which seems to be used only sporadically. It also hosts a mailing list and the usual facilities for filing bug reports, feature requests and support requests.
Usability[edit]
While installation and configuration can be complex, the Swing-based GUI allows for relatively easy use. JHOVE can also be invoked with a command-line interface.
Expertise required[edit]
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Familiarity with metadata outputs is also essential.
Standards compliance[edit]
JHOVE was designed to integrate into the Ingest function of an OAIS. The validation process compares objects’ formats against ISO standards.
Influence and take-up[edit]
The SourceForge website reports approximately 11,400 downloads from the release of JHOVE 1.1 from 2008 to July 2013. Use of JHOVE is widespread in the digital preservation community. JHOVE is integrated within the Planets Testbed and Plato.
User Experiences[edit]
- Jisc: http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
- Gary McGath: https://fileformats.wordpress.com/tag/jhove/
- KOST-CECO: Used in KOST-Val as a validation module for TIFF files.
- FITS (File Information Tool Set): Used in FITS
- PDF Association: http://www.pdfa.org/2014/12/ensuring-long-term-access-pdf-validation-with-jhove/
- Open Preservation Foundation: JHOVE issues and error messages: http://wiki.opf-labs.org/display/Documents/JHOVE+issues+and+error+messages/
Development Activity[edit]
While much of its development effort has been diverted to JHOVE2, JHOVE is still actively maintained and developed by the OPF [1] as it supports some common formats that JHOVE2 does not.
All development activity is visible on GitHub: http://github.com/openpreserve/jhove/commits
Release Feed[edit]
Below the last 3 release feeds:
- 2024-11-19 11:26:58
- [tag:github.com,2008:Repository/17627031/v1.32.1-RC1 JHOVE v1.32.1-RC1]
- by carlwilson
- 2024-09-23 07:57:05
- [tag:github.com,2008:Repository/17627031/v1.32.0 JHOVE v1.32.0]
- by carlwilson
- 2024-08-22 13:18:38
- [tag:github.com,2008:Repository/17627031/v1.32.0-RC1 JHOVE v1.32.0-RC1]
- by carlwilson
Activity Feed[edit]
Below the last 5 activity feeds: Failed to load RSS feed from https://github.com/openpreserve/jhove/commits/master.atom: There was a problem during the HTTP request: 404 Not Found
About Formats[edit]
JHOVE do only read the format itself, not the spesification as such