COPTR - User contributions [en-gb]

Peepdf

2018-09-24T15:39:43Z

Yfriese:

{{Infobox_tool
|purpose=peepdf is a Python tool to explore PDF files in order to find out if the file can be harmful or not.
|image=
|homepage=http://eternal-todo.com/tools/peepdf-pdf-analysis-tool
|license=GNU GPL v3
|platforms=
}}


[[Category:Metadata Extraction]]
[[Category:Document]]

= Description =
From the peepdf homepage:

peepdf is a Python tool to explore PDF files in order to find out if the file can be harmful or not. The aim of this tool is to provide all the necessary components that a security researcher could need in a PDF analysis without using 3 or 4 tools to make all the tasks. With peepdf it is possible to see all the objects in the document showing the suspicious elements, supports all the most used filters and encodings, it can parse different versions of a file, object streams and encrypted files. With the installation of Spidermonkey and Libemu it provides Javascript and shellcode analysis wrappers too. Apart of this it is able to create new PDF files and to modify existent ones.

= User Experiences =
After downloading the tool [http://eternal-todo.com/tools/peepdf-pdf-analysis-tool Download Page] you can just open the command line from any folder on your machine with PDF files in it and type e. g.:

''folderWithPeepdfInIt\peepdf.py -l nameOfPdfToanalyse.pdf''

You can also create an output file (e. g. output.txt),it will appear in the folder of the PDF you are examining.

''folderWithPeepdfInIt\peepdf.py -l nameOfPdfToanalyse.pdf > output.txt''

An output might look like this:

[[File:Screenshot_peepdf_findings.jpg]]

= Development Activity =

{{Infobox_tool_details
|ohloh_id=peepdf
}}

File:Screenshot peepdf findings.jpg

2018-09-24T15:38:18Z

Yfriese: Yfriese uploaded a new version of "File:Screenshot peepdf findings.jpg"

File:Screenshot peepdf findings.jpg

2018-09-24T15:36:53Z

Yfriese:

File:PeePDFOutput.jpg

2018-09-24T15:26:59Z

Yfriese:

Peepdf

2018-09-24T15:26:34Z

Yfriese:

{{Infobox_tool
|purpose=peepdf is a Python tool to explore PDF files in order to find out if the file can be harmful or not.
|image=
|homepage=http://eternal-todo.com/tools/peepdf-pdf-analysis-tool
|license=GNU GPL v3
|platforms=
}}


[[Category:Metadata Extraction]]
[[Category:Document]]

= Description =
From the peepdf homepage:

peepdf is a Python tool to explore PDF files in order to find out if the file can be harmful or not. The aim of this tool is to provide all the necessary components that a security researcher could need in a PDF analysis without using 3 or 4 tools to make all the tasks. With peepdf it is possible to see all the objects in the document showing the suspicious elements, supports all the most used filters and encodings, it can parse different versions of a file, object streams and encrypted files. With the installation of Spidermonkey and Libemu it provides Javascript and shellcode analysis wrappers too. Apart of this it is able to create new PDF files and to modify existent ones.

= User Experiences =
After downloading the tool [http://eternal-todo.com/tools/peepdf-pdf-analysis-tool Download Page] you can just open the command line from any folder on your machine with PDF files in it and type e. g.:

''folderWithPeepdfInIt\peepdf.py -l nameOfPdfToanalyse.pdf''

You can also create an output file (e. g. output.txt),it will appear in the folder of the PDF you are examining.

''folderWithPeepdfInIt\peepdf.py -l nameOfPdfToanalyse.pdf > output.txt''

An output might look like this:

= Development Activity =

{{Infobox_tool_details
|ohloh_id=peepdf
}}

Peepdf

2018-09-24T14:55:32Z

Yfriese: /* Description */

Cloc

2018-09-24T14:21:28Z

Yfriese:

{{Infobox_tool
|purpose= Cloc (Count Lines of Code) serves not only to count the lines of Code,but also guesses the programming language, thus can be used to identify files. It is a command line tool which is easy to use.
|image={{PAGENAMEE}}.png
|homepage=[https://github.com/AlDanial/cloc CLOC in GitHub]
|license= GNU General Public License v2.0
|platforms=
}}






== Description ==

Start the command line from the folder which contains the CLOC exe file.

Type:

''cloc-1.78.exe D:/Folder/fileToAnalyse''

The findings are shown in the black window. Alternatively, you can have an output file

''cloc-1.78.exe D:/Folder/fileToAnalayse > outputfile.txt''

You can also analyse all files in certain folder, the syntax is like this:

''cloc-1.78.exe D:/AnalyseWholeFolder > outputForAllFilesInFolder.txt''

[[File:Cloc_FindingExxample.jpg]]

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
The tool is now released at GitHub. [https://github.com/AlDanial/cloc/releases CLOC Page on GitHub]
There are new releases roughly twice a year.

File:Cloc FindingExxample.jpg

2018-09-24T14:18:35Z

Yfriese: Shows an example for a Cloc finding file

Shows an example for a Cloc finding file

Cloc

2018-09-24T14:11:25Z

Yfriese:

{{Infobox_tool
|purpose= Cloc (Count Lines of Code) serves not only to count the lines of Code,but also guesses the programming language, thus can be used to identify files. It is a command line tool which is easy to use.
|image={{PAGENAMEE}}.png
|homepage=[https://github.com/AlDanial/cloc CLOC in GitHub]
|license= GNU General Public License v2.0
|platforms=
}}






== Description ==

Start the command line from the folder which contains the CLOC exe file.

Type:

''cloc-1.78.exe D:/Folder/fileToAnalyse''

The findings are shown in the black window. Alternatively, you can have an output file

''cloc-1.78.exe D:/Folder/fileToAnalayse > outputfile.txt''

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
The tool is now released at GitHub. [https://github.com/AlDanial/cloc/releases CLOC Page on GitHub]
There are new releases roughly twice a year.

Cloc

2018-09-24T14:08:29Z

Yfriese:

{{Infobox_tool
|purpose= Cloc (Count Lines of Code) serves not only to count the lines of Code,but also guesses the programming language, thus can be used to identify files. It is a command line tool which is easy to use.
|image={{PAGENAMEE}}.png
|homepage=[https://github.com/AlDanial/cloc CLOC in GitHub]
|license= GNU General Public License v2.0
|platforms=
}}






== Description ==

Start the command line from the folder which contains the CLOC exe file.

Type:

''cloc-1.78.exe D:/Folder/fileToAnalyse''

The findings are shown in the black window. Alternatively, you can have an output file

''cloc-1.78.exe D:/Folder/fileToAnalayse > outputfile.txt''

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Cloc

2018-09-24T14:01:26Z

Yfriese:

{{Infobox_tool
|purpose= Cloc Count Lines of Code
|image={{PAGENAMEE}}.png
|homepage=[https://github.com/AlDanial/cloc CLOC in GitHub]
|license= GNU General Public License v2.0
|platforms=
}}






== Description ==


== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Cloc

2018-09-24T13:56:01Z

Yfriese: Created page with " {{Infobox_tool |purpose=A brief description |image={{PAGENAMEE}}.png |homepage=url |license= |platform..."

{{Infobox_tool
|purpose=A brief description
|image={{PAGENAMEE}}.png
|homepage=url
|license=
|platforms=
}}






== Description ==


== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Bad Peggy

2017-09-28T07:33:41Z

Yfriese:

{{Infobox_tool
|purpose=Scans for damaged images and photos.
|image=BadPeggy.png
|homepage=https://www.coderslagoon.com/index.php?lang=EN
|license=GPLv3
|platforms=Windows, Linux, OSX
}}



[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Image]]


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Image]]

== Description ==

Bad Peggy scans images ({{Format|JPEG}}, {{Format|PNG}}, {{Format|BMP}}, {{Format|GIF}}) for damages and other blemishes, and shows the results and files instantly. It enables you to find such broken files quickly, inspect and then either delete or move them to a different location.

Requires Java 6 or higher.

Lizensed under the GPLv3.

Quoted from the documentation:
"Bad Beggy uses the Java Image IO (JIIO) library to examine image files. Its decoder emits warnings and errors while an image gets loaded. Thus the results do depend on it being up-to-date and also its changes in functionality. Bad Peggy checks though on startup if in general, well-known errors in images do get detected, i.e. if JIIO is still functioning in detecting damaged images as expected. What "damaged" truly means depends and can be
*small difference from the official format, e.g. extra data appended after the actual image.
*non-critical issues like unknown values, which do not affect displaying the image at all.
*minor damage which only disturb smaller parts of the image.
*major damage, which causes the display to be corrupted after a particular position.
*completely truncated or i.e. incomplete images.
*errors at the beginning of the files, so that decoding can't even commence.
*files with are not images at all, but accidentally carry the file extension.
*image files which don't get recognized b the JIIO, but can be processed by other image viewers, e.g. if additional information is stored before the *image data starts (which smarter or more aggressive decoders then skip).
*an image which looks damaged because it got loaded as such, and saved again in another application - and thus is structurally fine.
*an image which is logically damaged but does not cause complains by the JIIO, although the flaws are clearly visible - this is one of the most problematic cases, since such files won't be detected by Bad Peggy - detection for such problems is difficult, you can compare this with a text editor loading and displaying a file with the word "text pr{cessor" in the, where the 'a' to '{' change was caused by a faulty transmission but the text *still makes sense to the editor itself.
In general it is not recommended to just discard every image reported as damaged but to check out if repairing or re-saving the file in other applications into a generally valid image format is possible."

== User Experiences ==

* '''KOST-CECO:''' Used in [[KOST-Val]] for the JPEG validation module. [[KOST-Val]] evaluates the error message "Not a JPEG file" further.
* '''Error detection of JPEG files with JHOVE and Bad Peggy:''' http://openpreservation.org/blog/2016/11/29/jpegvalidation/ (December 2016)

* To validate other file formats than JPEG, make sure the file extension (e. g. gif, png, bmp) appears on the List "options" -> "file extension". If it does not appear there, maybe you should re-download directly from '''Coderslagoon''' https://www.coderslagoon.com/#/product/badpeggy

== Development Activity ==


New in Version 2.0:
* Support for PNG, BMP and GIF images.
* Simplified status bar.
* Visual error differentiation changed to grayscale.
* Error differentiation now in done in gray tones.
* Message box button text is now translated.
* Minor bug fixes and cosmetic changes.

Bad Peggy Sources: https://www.coderslagoon.com/files/badpeggy20_src.tar.xz

{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Talk:Bad Peggy

2017-09-22T10:14:43Z

Yfriese: Created page with "The first sentence '' Bad Peggy scans images (JPEG, PNG, BMP, GIF) for damages and other blemishes, '' does not appear to be true. The documentations sais it's only JPEGs and..."

The first sentence
''
Bad Peggy scans images (JPEG, PNG, BMP, GIF) for damages and other blemishes,
''
does not appear to be true. The documentations sais it's only JPEGs and trying for GIF has also not worked. Should we correct the article?

TrID File Identifier

2017-04-10T07:16:31Z

Yfriese:

{{Infobox_tool
|purpose=TrID is a utility designed to identify file types from their binary signatures.
|image=
|homepage=http://mark0.net/soft-trid-e.html
|license=
|platforms=
}}


[[Category:File Format Identification]]

= Description =
TrID is a utility designed to identify file types from their binary signatures. While there are similar utilities with hard coded rules, TriID has no such rules. Instead, it is extensible and can be trained to recognize new formats in a fast and automatic way.

It was first released in 2003. Currently, its library contains of 8408 entries.

= User Experiences =
It's a command line tool, which can be scripted pretty easily, e. g.:

<code>
echo off 
echo Please paste folder with files to identify: 
echo ************************** 
set /p inputfolder= folder : 
for /r "%inputfolder%\" %%X in (*.*) do ( 
echo new File >> gfindings.txt 
echo TRId Findings >> govDocs.txt 
trid "%%X" >> govDocs.txt 
) 
Pause 
</code>

TrID works best for binary files, plain text files are just identified as "test/ASCII".

Findings are output in %, a file format, so typical TrID findings can be:

* 50.0% (.BMP) Windows Bitmap (v3) (2004/2)
* 100.0% (.FM) FrameMaker document (11000/1)
* 53.8% (.WRI) Windows Write Document (7000/1)

It is also possible that several file formats are output, e. g. 50% JPEG, 50% something else.

= Development Activity =

{{Infobox_tool_details
|ohloh_id=TrID File Identifier
}}

PRONOM Signature Development Utility

2017-04-04T08:07:44Z

Yfriese:

{{Infobox_tool
|purpose=Output DROID compatible file format signature files using PRONOM syntax
|image=
|homepage=https://github.com/exponential-decay/signature-development-utility
|license=Open source (see URL above)
|platforms=PHP + JQuery + Javascript + text/html
}}


[[Category:File Format Identification]]



== Description ==

Utility to enable the creation of DROID compatible signature files using PRONOM regular expression syntax. The tool outputs in an XML format compatible with DROID 4 upwards (including DROID 5 and 6). Three sequences can be combined to create a single file format signature. Signature files can be concatenated manually if more complex collections are required for testing.

Signature File 88 contains of 1427 different PUIDs.

= Development Activity =

All development activity is visible on GitHub: https://github.com/exponential-decay/signature-development-utility/commits

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/exponential-decay/signature-development-utility/commits/master.atom</rss>


{{Infobox_tool_details
|ohloh_id=
}}

TrID File Identifier

2017-04-03T13:55:41Z

Yfriese:

{{Infobox_tool
|purpose=TrID is a utility designed to identify file types from their binary signatures.
|image=
|homepage=http://mark0.net/soft-trid-e.html
|license=
|platforms=
}}


[[Category:File Format Identification]]

= Description =
TrID is a utility designed to identify file types from their binary signatures. While there are similar utilities with hard coded rules, TriID has no such rules. Instead, it is extensible and can be trained to recognize new formats in a fast and automatic way.

= User Experiences =
It's a command line tool, which can be scripted pretty easily, e. g.:

<code>
echo off 
echo Please paste folder with files to identify: 
echo ************************** 
set /p inputfolder= folder : 
for /r "%inputfolder%\" %%X in (*.*) do ( 
echo new File >> gfindings.txt 
echo TRId Findings >> govDocs.txt 
trid "%%X" >> govDocs.txt 
) 
Pause 
</code>

TrID works best for binary files, plain text files are just identified as "test/ASCII".

Findings are output in %, a file format, so typical TrID findings can be:

* 50.0% (.BMP) Windows Bitmap (v3) (2004/2)
* 100.0% (.FM) FrameMaker document (11000/1)
* 53.8% (.WRI) Windows Write Document (7000/1)

It is also possible that several file formats are output, e. g. 50% JPEG, 50% something else.

= Development Activity =

{{Infobox_tool_details
|ohloh_id=TrID File Identifier
}}

Siegfried

2017-03-21T12:08:03Z

Yfriese:

{{Infobox_tool
|purpose=A PRONOM based, command line, file format identification tool using Aho Corasick matching and no buffer limits.
|image=
|homepage=http://www.itforarchivists.com/siegfried
|license=Apache License 2.0
|platforms=
}}


[[Category:File Format Identification]]



== Description ==

Siegried is a file format identification tool that, like DROID and Fido, is based on PRONOM. However, it uses a different pattern matching algorithm that offers different strengths and weaknesses to those other PRONOM based tools. A detailed description of the tool and why it was created can be found in [http://www.openplanetsfoundation.org/blogs/2014-09-27-siegfried-pronom-based-file-format-identification-tool this blog post].
Besides, there is a more detailed description in terms of functionality on the [https://github.com/richardlehane/siegfried Github Page of Siegfried].

Siegfried was first publicly released the 28th february 2014 in version 0.1.

== User Experiences ==

* '''ZBW:'''
** The command line tool is very easy to handle. The default output is yaml. This can be changed to csv or json.
***Usual command: sf file.ext (will output in yaml)
***Change output to csv: sf -csv file.ext
***Change output to json: sf -json file.ext
**It is also possible to save the output in an external file:
***sf file.ext >output.yml
***sf -csv file.ext >output.csv
***sf -json file.ext >output.json

== Development Activity ==

All development activity is visible on GitHub: http://github.com/richardlehane/siegfried/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/richardlehane/siegfried/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/richardlehane/siegfried/commits/master.atom</rss>


{{Infobox_tool_details
|ohloh_id=
}}

DROID (Digital Record Object Identification)

2017-03-15T10:57:39Z

Yfriese:

{{Infobox_tool
|purpose=DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats.
|image=
|homepage=http://digital-preservation.github.io/droid/
|license=BSD License
|platforms=Java 6 Standard Edition
}}


[[Category:File Format Identification]]
[[Category:Metadata Extraction]]

= Description =
DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats. DROID is designed to meet the fundamental requirement of any digital repository to be able to identify the precise format of all stored digital objects, and to link that identification to a central registry of technical information about that format and its dependencies.

DROID uses the PRONOM [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] to perform format identification. Like PRONOM, it was [http://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/digital-continuity/file-profiling-tool-droid/ developed by the National Archives of the UK]. Written in Java, XML.

== PRONOM ==
The format information held in PRONOM is what powers [[DROID (Digital Record Object Identification)]]. Both are maintained by the [http://www.nationalarchives.gov.uk/ UK's National Archives].

DROID downloads the latest [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] from PRONOM, and those are used to drive the identification process. See the [http://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml PRONOM release notes].

A number of other tools and registries have been based around the PRONOM data. These include:

* [[Nanite]] and [[Fido]] identification tools
* [[Siegfried]] identification tool

Although the information and website are made freely available under the Open Government License, the underlying software engine that powers PRONOM is proprietary.

=== The PRONOM Web API ===
The website is oriented towards manual browsing, but note that each PRONOM registry entry as a permalink, like this:

http://apps.nationalarchives.gov.uk/pronom/fmt/579

and furthermore, by appending '.xml' to the URL for any entry, the data can be recovered as XML:

http://apps.nationalarchives.gov.uk/pronom/fmt/579.xml

= User Experiences =
* [http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf Digital Asset Assessment Tool - Assessment of file format testing tools].
* Comparing how [[Apache Tika]] and DROID perform HTML identification: [http://britishlibrary.typepad.co.uk/webarchive/2014/07/how-much-of-the-uk-html-is-valid.html How much of the UK's HTML is valid?]
* [http://openplanetsfoundation.org/blogs/2014-06-03-analysis-engine-droid-csv-export An Analysis Engine for the DROID CSV Export]
* '''KOST-CECO:''' Used in [[KOST-Val]] for the file format identification. For performance and granularity reasons an own SignatureFile is used instead of the official PRONOM registry.
* '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]]

= Development Activity =

<rss max=5>https://github.com/digital-preservation/droid/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=droid
}}

ImageMagick

2017-01-03T14:06:06Z

Yfriese:

{{Infobox_tool
|purpose=ImageMagick® is a software suite to create, edit, compose, or convert bitmap images.
|image=ImageMagick.jpg
|homepage=http://www.imagemagick.org
|license=Apache License v2.0
|platforms=should run under any operating system
}}


[[Category:Rendering]]
[[Category:File Format Migration]]
[[Category:Image]]

= Description =
ImageMagick® is a software suite to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 100) including DPX, EXR, GIF, JPEG, JPEG-2000, PDF, PNG, Postscript, SVG, and TIFF.
Can be used as a migration tool for bitmap images.

=== Functionality ===
The functionality of ImageMagick is typically utilized from the command line or you can use the features from programs written in your favorite language. C

An example for a command is:

magick convert original.JPG migration.png

This converts a certain jpeg to a png file. For this command to work the console has to be opened in the folder the jpeg ("original.JPG") is saved in.

Another example:

magick -verbose identify examine.jpg >test.txt

This gives as many information as possible about "examine.jpg" and saves it in a Textfile ("test.txt"). It is also possible to do this with whole folders by building a script.

=== License ===
ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under the Apache 2.0 license, approved by the OSI and recommended for use by the OSSCC.

=== Download ===
The current release is available from http://www.imagemagick.org/download.

= User Experiences =
Used in Planets as a migration tool for Tiff format files.

A German speaking guide to develop batch-programs for ImageMagick can be found in the nestor wiki from https://wiki.dnb.de/pages/viewpage.action?pageId=123046041.

= Development Activity =

{{Infobox_tool_details
|ohloh_id=ImageMagick
}}

ImageMagick

2016-12-12T10:04:00Z

Yfriese:

{{Infobox_tool
|purpose=ImageMagick® is a software suite to create, edit, compose, or convert bitmap images.
|image=ImageMagick.jpg
|homepage=http://www.imagemagick.org
|license=Apache License v2.0
|platforms=should run under any operating system
}}


[[Category:Rendering]]
[[Category:File Format Migration]]
[[Category:Image]]

= Description =
ImageMagick® is a software suite to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 100) including DPX, EXR, GIF, JPEG, JPEG-2000, PDF, PNG, Postscript, SVG, and TIFF.
Can be used as a migration tool for bitmap images.

=== Functionality ===
The functionality of ImageMagick is typically utilized from the command line or you can use the features from programs written in your favorite language. C

An example for a command is:

magick convert original.JPG migration.png

This converts a certain jpeg to a png file. For this command to work the console has to be opened in the folder the jpeg ("original.JPG") is saved in.

Another example:

magick -verbose identify examine.jpg >test.txt

This gives as many information as possible about "examine.jpg" and saves it in a Textfile ("test.txt"). It is also possible to do this with whole folders by building a script.

=== License ===
ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under the Apache 2.0 license, approved by the OSI and recommended for use by the OSSCC.

=== Download ===
The current release is available from http://www.imagemagick.org/download.

= User Experiences =
Used in Planets as a migration tool for Tiff format files.

= Development Activity =

{{Infobox_tool_details
|ohloh_id=ImageMagick
}}

FITS (File Information Tool Set)

2016-06-20T09:25:34Z

Yfriese:

{{Infobox_tool
|purpose=FITS allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository.
|image=
|homepage=http://fitstool.org
|license=[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License]
|platforms=Windows or Unix
}}


[[Category:File Format Identification]]
[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Encryption Detection]]

= Description =
[http://fitstool.org FITS] allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository. It does this by encorporating a range of mostly third-party open source tools, normalising and consolidating their output.

=== Provider ===
Harvard Library

=== Platform and interoperability ===
FITS is written in Java and is compatible with Java 1.6 or higher.
It uses six external tools:
* [[JHOVE (Harvard Object Validation Environment)| JHOVE]]
* [[ExifTool]]
* [[Metadata Extraction Tool]]
* [[DROID_(Digital_Record_Object_Identification)|DROID]]
* [http://web.archive.org/web/20061106114156/http://schmidt.devlib.org/ffident/index.html FFIdent]
* [http://unixhelp.ed.ac.uk/CGI/man-cgi?file File Utility]

A few Harvard Library-created tools; and many open source libraries.
Instructions for command line use are given for Windows and Unix.

=== Functional notes ===
FITS acts as a wrapper, invoking and managing the output from several other open source tools. Output from these tools are converted into a common format, compared to one another and consolidated into a single XML output file. Technical metadata is only output (and a part of the consolidation process) for tools that were able to identify the file. All other output is discarded.

=== Documentation and user support ===
Documentation exists in the form of a user manual and more technical developer manual.
The project actively uses the fits-users google group has 30 members, and is active as of January 2012.
The FITS web site links to a [https://github.com/harvard-lts/fits github site] that includes the source code and an issues tracker.

=== Usability ===
FITS uses a command line interface; it is designed to be integrated into other software workflows, and so is aimed at those with application design experience.

=== Expertise required ===
Installation and configuration require deep systems administration and application design knowledge, as well as familiarity with file format and metadata standards.

=== Standards compliance ===
FITS outputs in XML format. A detailed description of the FITS-XML can be found [http://projects.iq.harvard.edu/fits/fits-xml here] and an analysis of the output data [http://projects.iq.harvard.edu/fits/understanding-output here].

=== Influence and take-up ===
The FITS website shows over 2000 downloads of the software.
The tool was designed for and is in use at the Harvard Library [http://hul.harvard.edu/ois/systems/drs/ Digital Repository Service].

= User Experiences =

* '''DNB (German National Library):'''
** FITS v0.6.1 with modified [[JHOVE (Harvard Object Validation Environment)| Jhove 1.11]], Gentoo Linux, Java-Environment, Tomcat-Application Server
** Since the end of 2012, DNB uses the FITS library as a part of its risk management within the automated ingest process. At present more than 1500 files are daily examined by FITS.
*** The purpose of the risk management and its implementation with metadata tools like FITS or JHOVE is to facilitate automatic technical quality checking (bitstream integrity and validation) of each digital publications. Furthermore, the analysis is aimed at recognising technical restrictions such as DRM at an early stage, which hinder or even prevent the task of long-term preservation and use of the digital objects.
*** The extracted technical metadata (the FITS output) are used further for future long-term preservation measures such as format migration and are stored and managed in the metadata management of the long-term archive of the DNB. The capture of these metadata is essential in order to execute targeted migration measures of files in endangered formats.
*** FITS also offers significant benefit in the form of easily configurable standardisation of the different tool outputs into the FITS format using XSLT. The DNB has used this function to adapt the FITS output to its own requirements, e.g. incorporating other metadata elements not included in the FITS distribution into the standardisation.
*** A further adjustment, which the DNB has made, is the integration of a DNB tool to analyse files in ePub format.

* '''ZBW (German National Library of Economics):'''
[https://wiki.dnb.de/display/NESTOR/ZBW+user+experience+with+FITS Link to the user experience of the ZBW]

= Development Activity =

FITS 0.2.0 was first released as open source in July 2009. As of April 2014 the latest release was version 0.8, released in January 2014. The tool was created to be used in Harvard's Digital Repository Service, and development is active and ongoing.

All development activity is visible on GitHub: http://github.com/harvard-lts/fits/commits

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/harvard-lts/fits/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=fits
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:56:42Z

Yfriese: /* Development Activity */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''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/

== 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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:56:04Z

Yfriese: /* Development Activity */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''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/

== 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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:53:01Z

Yfriese: /* User Experiences */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''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/

== Development Activity ==

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed (apparently as a [http://fileformats.wordpress.com/tag/jhove/ solo project]) 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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:48:59Z

Yfriese: /* User Experiences */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''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/

== Development Activity ==

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed (apparently as a [http://fileformats.wordpress.com/tag/jhove/ solo project]) 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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:40:06Z

Yfriese: /* Development Activity */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''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]]

== Development Activity ==

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed (apparently as a [http://fileformats.wordpress.com/tag/jhove/ solo project]) 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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:39:28Z

Yfriese: /* Activity Feed */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''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]]

== Development Activity ==
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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

JHOVE (Harvard Object Validation Environment)

2015-07-09T09:38:32Z

Yfriese: /* Activity Feed */

{{Infobox_tool
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|image=JHOVE.gif
|homepage=http://jhove.openpreservation.org/
|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.4 and has a directory-based file system.
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

== Description ==
[http://hul.harvard.edu/jhove/ 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 [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
JSTOR and the Harvard University Library

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== 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.

==== 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.
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 ====
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.

==== 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.

==== Expertise required ====
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.

==== 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.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''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]]

== Development Activity ==
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>

{{Infobox_tool_details
|ohloh_id=JHOVE
}}

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed (apparently as a [http://fileformats.wordpress.com/tag/jhove/ solo project]) as it supports some common formats that JHOVE2 does not.

FITS (File Information Tool Set)

2015-07-02T13:52:24Z

Yfriese: /* Standards compliance */

{{Infobox_tool
|purpose=FITS allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository.
|image=
|homepage=http://fitstool.org
|license=GNU Lesser General Public License
|platforms=Windows or Unix
}}


[[Category:File Format Identification]]
[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Encryption Detection]]

= Description =
[http://fitstool.org FITS] allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository. It does this by encorporating a range of mostly third-party open source tools, normalising and consolidating their output.

=== Provider ===
Harvard Library

=== Licensing and cost ===
[http://www.gnu.org/licenses/gpl.html GNU Lesser GPL] – free.

=== Platform and interoperability ===
FITS is written in Java and is compatible with Java 1.6 or higher.
It uses six external tools:
* [[JHOVE (Harvard Object Validation Environment)| JHOVE]]
* [[ExifTool]]
* [[Metadata Extraction Tool]]
* [[DROID_(Digital_Record_Object_Identification)|DROID]]
* [http://web.archive.org/web/20061106114156/http://schmidt.devlib.org/ffident/index.html FFIdent]
* [http://unixhelp.ed.ac.uk/CGI/man-cgi?file File Utility]

A few Harvard Library-created tools; and many open source libraries.
Instructions for command line use are given for Windows and Unix.

=== Functional notes ===
FITS acts as a wrapper, invoking and managing the output from several other open source tools. Output from these tools are converted into a common format, compared to one another and consolidated into a single XML output file. Technical metadata is only output (and a part of the consolidation process) for tools that were able to identify the file. All other output is discarded.

=== Documentation and user support ===
Documentation exists in the form of a user manual and more technical developer manual.
The project actively uses the fits-users google group has 30 members, and is active as of January 2012.
The FITS web site links to a [https://github.com/harvard-lts/fits github site] that includes the source code and an issues tracker.

=== Usability ===
FITS uses a command line interface; it is designed to be integrated into other software workflows, and so is aimed at those with application design experience.

=== Expertise required ===
Installation and configuration require deep systems administration and application design knowledge, as well as familiarity with file format and metadata standards.

=== Standards compliance ===
FITS outputs in XML format. A detailed description of the FITS-XML can be found [http://projects.iq.harvard.edu/fits/fits-xml here] and an analysis of the output data [http://projects.iq.harvard.edu/fits/understanding-output here].

=== Influence and take-up ===
The FITS website shows over 2000 downloads of the software.
The tool was designed for and is in use at the Harvard Library [http://hul.harvard.edu/ois/systems/drs/ Digital Repository Service].

= User Experiences =

= Development Activity =

FITS 0.2.0 was first released as open source in July 2009. As of April 2014 the latest release was version 0.8, released in January 2014. The tool was created to be used in Harvard's Digital Repository Service, and development is active and ongoing.

All development activity is visible on GitHub: http://github.com/harvard-lts/fits/commits

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/harvard-lts/fits/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=fits
}}

FITS (File Information Tool Set)

2015-07-02T13:51:52Z

Yfriese: /* Standards compliance */

{{Infobox_tool
|purpose=FITS allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository.
|image=
|homepage=http://fitstool.org
|license=GNU Lesser General Public License
|platforms=Windows or Unix
}}


[[Category:File Format Identification]]
[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Encryption Detection]]

= Description =
[http://fitstool.org FITS] allows data curators to identify, validate, and extract technical metadata for the objects in their digital repository. It does this by encorporating a range of mostly third-party open source tools, normalising and consolidating their output.

=== Provider ===
Harvard Library

=== Licensing and cost ===
[http://www.gnu.org/licenses/gpl.html GNU Lesser GPL] – free.

=== Platform and interoperability ===
FITS is written in Java and is compatible with Java 1.6 or higher.
It uses six external tools:
* [[JHOVE (Harvard Object Validation Environment)| JHOVE]]
* [[ExifTool]]
* [[Metadata Extraction Tool]]
* [[DROID_(Digital_Record_Object_Identification)|DROID]]
* [http://web.archive.org/web/20061106114156/http://schmidt.devlib.org/ffident/index.html FFIdent]
* [http://unixhelp.ed.ac.uk/CGI/man-cgi?file File Utility]

A few Harvard Library-created tools; and many open source libraries.
Instructions for command line use are given for Windows and Unix.

=== Functional notes ===
FITS acts as a wrapper, invoking and managing the output from several other open source tools. Output from these tools are converted into a common format, compared to one another and consolidated into a single XML output file. Technical metadata is only output (and a part of the consolidation process) for tools that were able to identify the file. All other output is discarded.

=== Documentation and user support ===
Documentation exists in the form of a user manual and more technical developer manual.
The project actively uses the fits-users google group has 30 members, and is active as of January 2012.
The FITS web site links to a [https://github.com/harvard-lts/fits github site] that includes the source code and an issues tracker.

=== Usability ===
FITS uses a command line interface; it is designed to be integrated into other software workflows, and so is aimed at those with application design experience.

=== Expertise required ===
Installation and configuration require deep systems administration and application design knowledge, as well as familiarity with file format and metadata standards.

=== Standards compliance ===
FITS outputs in XML format. A detailed description of the FITS-XML can be found [http://projects.iq.harvard.edu/fits/fits-xml here] and an analysis of the output data here[http://projects.iq.harvard.edu/fits/understanding-output here].

=== Influence and take-up ===
The FITS website shows over 2000 downloads of the software.
The tool was designed for and is in use at the Harvard Library [http://hul.harvard.edu/ois/systems/drs/ Digital Repository Service].

= User Experiences =

= Development Activity =

FITS 0.2.0 was first released as open source in July 2009. As of April 2014 the latest release was version 0.8, released in January 2014. The tool was created to be used in Harvard's Digital Repository Service, and development is active and ongoing.

All development activity is visible on GitHub: http://github.com/harvard-lts/fits/commits

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/harvard-lts/fits/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=fits
}}

JHOVE2

2015-06-05T13:47:44Z

Yfriese:

{{Infobox_tool
|purpose=JHOVE2 allows data curators to characterise the digital objects in their repositories.
|image=
|homepage=http://jhove2.org/
|license=JHOVE2 is made freely available under the termsof the BSD open source license for all project-developed code; some third-party libraries may be covered by other open source licences.
|platforms=
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]

= Description =
[https://bitbucket.org/jhove2/main/wiki/Home JHOVE2] is a follow-on to the Harvard/JSTOR [[JHOVE (Harvard Object Validation Environment)| JHOVE]] project, with the similar purpose of allowing data curators to characterise the digital objects in their repositories.  Characterisation is comprised of four elements: first, identifying the object’s format; second, validating that the object conforms to its format’s technical norms; third, extracting technical metadata from the object; and fourth, assessing whether the object should be accepted into a repository, based on policies set by the curator.  
The software was designed to be able to integrate with other applications to enable easy incorporation into a repository’s Ingest workflow.
====Provider====
California Digital Library, Portico, and Stanford University, with funding from the National Digital Information Infrastructure and Preservation Program (NDIIPP). Version 2.1 also credits the Bibliothèque nationale de France and Netarkivet.
====Licensing and cost====
Open Source [http://www.linfo.org/bsdlicense.html BSD license] – free.
====Development activity====
JHOVE2 version 2.1 was released in March 2013.
Funding for the JHOVE2 project ended in 2011. The project partners committed to providing self-funded maintenance (but not further development effort) for three years. Their goal was to create an open-source community to guide and foster JHOVE2 technical development, and the involvement of Bibliothèque nationale de France and Netarkivet from version 2.1 signifies some success in this regard.
====Platform and interoperability====
JHOVE2 is written in Java Standard Edition 6, and requires a Java 6 runtime environment.  If the user is hoping to use the SGML validation module, an OpenSP SGML parser is required.
Developers wishing to rebuild JHOVE2 from the provided source will need a full Java SE 6 development kit and the Apache Maven project tool.
====Functional notes====
The JHOVE2 project came about as a response to perceived shortcomings in the [[JHOVE (Harvard Object Validation Environment)| JHOVE]] software. JHOVE2 separates identification from validation, allowing the software to identify objects even if they are not valid.  This also provides the opportunity to use the [http://www.dcc.ac.uk/resources/external/pronom PRONOM] registry in signature-based identification via integration with [[DROID_(Digital_Record_Object_Identification)|DROID]], creating the ability to identify many more format-types than those for which it has validation modules. Other improvements include the ability to characterize hierarchical digital objects such as directories, zip files and bit streams nested within files, and a design that allows easier integration with other applications.
JHOVE2 has validation modules for the following format types: ICC color profile; SGML; Shapefile; TIFF (including TIFF/EP, TIFF-FX, TIFF/IT, Exif, GeoTIFF, DNG and RFC 1314); UTF-8 encoded text; WAVE (including Broadcast Wave); XML; ZIP; GZIP; ARC; WARC; and arbitrary bytestreams, filesets and directories. Modules for JPEG 2000 (JP2 and JPX profiles) and PDF (including PDF/X and PDF/A) were planned but have not been implemented yet.  
For comparison, ICC, SGML, Shapefile, ZIP, GZIP, ARC and WARC are newly supported in JHOVE2; however, JHOVE supports AIFF, GIF, JPEG, JPEG2000 and PDF while JHOVE2 does not.  HTML is also not supported in JHOVE2, as it is in JHOVE, but since HTML can be expressed in terms of SGML or XML the functionality remains the same. 
====Documentation and user support====
JHOVE2’s website includes an informative FAQ introduction, as well as standard documentation such as a [https://bytebucket.org/jhove2/main/wiki/documents/JHOVE2-Users-Guide_20110222.pdf user guide] and [https://bytebucket.org/jhove2/main/wiki/documents/JHOVE2Programmer2-0-0.pdf programmer guide].  
Primary user support is through the jhove2-techtalk-l listserv, which remains active as of June 2013.  In addition, the website includes an issue tracker displaying reported bugs and feature enhancement requests. 
====Usability====
JHOVE2 does not include a GUI, which will be challenging for many users.
The default output (e. g. in xml, txt or json) is very talkative and can contain up to 3500 lines for one TIFF file.
====Expertise required====
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Creation of the assessment policies requires detailed knowledge of digital preservation standards and technologies.  
====Standards compliance====
JHOVE2 uses the PRONOM registry for file identification.  The software includes a stylesheet that can transform JHOVE2 outputs into the METS metadata standard.
====Influence and take-up====
As of July 2013, the website reports approximately 1000 downloads of version 2 and 200 of version 2.1.

= User Experiences =
Please note that JHOVE2 cannot cope with any empty spaces in the command line. Therefor, JHOVE2 has to be stored in a folder which can be typed in without any empty space.

As the output is extremely wordy and contains so much information that it is difficult to tell if a certain TIFF file is valid or not, it might be helpfull to configure the output options. This is possible in the sgml-file. It might proove to be difficult for the average non-SGML-expert to handle the file.

= Development Activity =
=== Activity Feed ===
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
<rss max=7>http://bitbucket.org/jhove2/main/rss</rss>

{{Infobox_tool_details
|ohloh_id=JHOVE2
}}

KOST-Val

2015-04-23T13:15:56Z

Yfriese: /* User Experiences */

{{Infobox_tool
|purpose=KOST-Val is an open source validator for different file formats (TIFF, SIARD, PDF/A, JP2, JPEG) and Submission Information Package (SIP).
|image=KOST-Val.JPG
|formats_in={{Format|TIFF}}, {{Format|SIARD}}, {{Format|PDF}}/A, {{Format|JP2}}, {{Format|JPEG}} and SIP
|homepage=http://kost-ceco.ch/cms/index.php?kost_val_de
|license=GPL V3
|platforms= should run under Java 1.6 on Windows
}}


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Image]]
[[Category:Document]]
[[Category:Preservation System]]


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Image]]
[[Category:Document]]
[[Category:Preservation System]]

= Description =

The KOST-Val application is used to validate {{Format|TIFF}}, {{Format|SIARD}}, {{Format|PDF}}/A, {{Format|JP2}}, {{Format|JPEG}} files and Submission Information Package (SIP).

KOST-Val supersedes the format validation tools [[SIARD-VAL]], [[TIFF-Val]] and SIP-Val by KOST-CECO.

=== Funtional Principle ===
KOST-Val uses unmodified components of other manufacturers by embedding them directly into the source code. Users of KOST-Val are requested to adhere to these components ‘terms of licence.

KOST-Val complies with the following requirements.

* '''TIFF validation:''' KOST-Val reads a TIFF file and uses [[JHOVE (Harvard Object Validation Environment)| JHOVE]] to validate the structure, the content, and key properties such as compression, colour space, and multipage. These properties can be configured.
* '''SIARD validation:''' KOST-Val reads a SIARD (eCH-0165 v1 ) file and validates the structure and the content.
* '''PDF/A validation:''' KOST-Val reads a PDF or PDF/A file (ISO 19005-1 and 19005-2) and uses [[3-Heights(TM) PDF Validator|3-Heights™ PDF/A Validator]] by PDF-Tools or [[PDFTron PDF-A Manager|PDF/A Manager]] by PDFTron to validate the structure and the content of the PDF file. KOST-Val organises the different error messages into main categories such as fonts, graphics, and metadata. KOST-Val supplies only a limited version from 3-Heights™ PDF/A Validator by PDF-Tools.
* '''JP2 validation:''' KOST-Val reads a JP2 file (ISO 15444) and uses [[Jpylyzer]] to validate the structure and the content.
* '''JPEG validation:''' KOST-Val reads a JPEG file (ISO 10918-1) and uses [[Bad Peggy]] to validate the structure and the content.
* '''SIP validation:''' KOST-Val reads an SIP (eCH-0160 v1 as well as Swiss Federal Archives SFA v1 and v4 ) and validates the mandatory requirements of the SIP specification. The validated requirements are organised into groups such as folder structure, schema validation, and checksum validation. At the outset, a file format validation is performed.

The results (including information on inconsistencies and errors) are output for every step and written into a validation log.
The validation steps are executed sequentially. Whenever possible the validation shall continue after an error has been detected in order to reduce the number of correction cycles.

[[File:KOST-Val_FuntionalPrincipleFormatValidation.JPG|800px]]

=== Third-party applications ===
* The TIFF validation module uses [[JHOVE (Harvard Object Validation Environment)| JHOVE]] and evaluates its output further.
* For the PDF/A validation module [[PDFTron PDF-A Manager|PDF-A Manager]] or [[3-Heights(TM) PDF Validator|3-Heights™ PDF/A Validator]] are used.
* The JP2 validation module uses [[Jpylyzer]] and translates the failed tests into appropriate error messages (DE/FR/EN).
* The JPEG validation module uses [[Bad Peggy]] and evaluates the error message "Not a JPEG file" further.
* For the file format identification [[DROID_(Digital_Record_Object_Identification)|DROID]] is used. For performance and granularity reasons an own SignatureFile is used instead of the official PRONOM registry.

===Read Me===
The KOST-Val application is used to validate TIFF, SIARD, PDF/A, JP2, JPEG files and Submission Information Package (SIP).

KOST-Val, Copyright (C) 2012-2015 Claire Roethlisberger (KOST-CECO), Christian Eugster, Olivier Debenath, Peter Schneider (Staatsarchiv Aargau), Markus Hahn (coderslagoon), Daniel Ludin (BEDAG AG)

This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; see GPL-3.0_COPYING.txt for details.

You can download KOST-Val under https://github.com/KOST-CECO/KOST-Val/releases. For installation instructions please check the manual (DE/FR/EN).

=== SIARD format ===
SIARD stands for Software Independent Archiving of Relational Databases. Originally the Swiss Federal Archives (SFA) have developed the SIARD format as a sustainable solution for the archiving of relations databases.

In early 2013 SIARD format has been adopted as an eCH Standard (eCH-0165: SIARD format specification http://www.ech.ch/vechweb/page?p=dossier&documentNumber=eCH-0165).

eCH is the Swiss organization for standardization in the field of e-government. eCH Standards define guidelines for recurring applications and their results, as for example format definitions or procedural standards. The aim of those standards is to unify and thus facilitate the electronic collaboration between authorities as well as between authorities and organizations, educational and research institutions, firms and private organizations.

===Future===
See http://github.com/KOST-CECO/KOST-Val/issues

===Feedback & Issues===
Feedback about KOST-Val is very welcome at http://github.com/KOST-CECO/KOST-Val/issues or kost-val[at]kost-ceco.ch

.

== User Experiences ==
* '''ZBW:'''
** KOST-Val v1.6.0
** The tool is very easy to install and to handle.
** The output in xml-Format (open in a browser to have a table) is easy to understand
** Running the JPEG-Module against almost 2,400 JPEGs has only lasted 7 minutes
** The tool recognises fake-JPEGs (jpeg-extension, but no jpeg inside) and issues with jpegs and can differentiate easily between these two cases.

= Development Activity =

All development activity is visible on GitHub: http://github.com/KOST-CECO/KOST-Val/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/KOST-CECO/KOST-Val/releases.atom</rss>

=== Activity Feed===
Below the last 5 commits:
<rss max=5>https://github.com/KOST-CECO/KOST-Val/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=KOST-Val
}}

Siegfried

2015-04-23T12:05:06Z

Yfriese: /* User Experiences */

{{Infobox_tool
|purpose=A PRONOM based, command line, file format identification tool using Aho Corasick matching and no buffer limits.
|image=
|homepage=http://www.itforarchivists.com/siegfried
|license=Apache License 2.0
|platforms=
}}


[[Category:File Format Identification]]



== Description ==

Siegried is a file format identification tool that, like DROID and Fido, is based on PRONOM. However, it uses a different pattern matching algorithm that offers different strengths and weaknesses to those other PRONOM based tools. A detailed description of the tool and why it was created can be found in [http://www.openplanetsfoundation.org/blogs/2014-09-27-siegfried-pronom-based-file-format-identification-tool this blog post].
Besides, there is a more detailed description in terms of functionality on the Github Page of Siegfried [https://github.com/richardlehane/siegfried].

== User Experiences ==
* '''ZBW:'''
** The command line tool is very easy to handle. The default output is yaml. This can be changed to csv or json.
***Usual command: sf file.ext (will output in yaml)
***Change output to csv: sf -csv file.ext
***Change output to json: sf -json file.ext
**It is also possible to save the output in an external file:
***sf file.ext >output.yml
***sf -csv file.ext >output.csv
***sf -json file.ext >output.json

== Development Activity ==



{{Infobox_tool_details
|ohloh_id=
}}

<rss max=7>https://github.com/richardlehane/siegfried/commits/master.atom</rss>

Siegfried

2015-04-23T09:51:37Z

Yfriese:

{{Infobox_tool
|purpose=A PRONOM based, command line, file format identification tool using Aho Corasick matching and no buffer limits.
|image=
|homepage=http://www.itforarchivists.com/siegfried
|license=Apache License 2.0
|platforms=
}}


[[Category:File Format Identification]]



== Description ==

Siegried is a file format identification tool that, like DROID and Fido, is based on PRONOM. However, it uses a different pattern matching algorithm that offers different strengths and weaknesses to those other PRONOM based tools. A detailed description of the tool and why it was created can be found in [http://www.openplanetsfoundation.org/blogs/2014-09-27-siegfried-pronom-based-file-format-identification-tool this blog post].
Besides, there is a more detailed description in terms of functionality on the Github Page of Siegfried [https://github.com/richardlehane/siegfried].

== User Experiences ==
The command line tool is very easy to handle. The default output is yaml. This can be changed to csv or json.
Usual command: sf file.ext (will output in yaml)
Change output to csv: sf -csv file.ext
Chante output to json: sf -json file.ext

It is also possible to save the output in an external file:
sf file.ext >output.yml
sf -csv file.ext >output.csv
sf -json file.ext >output.json


== Development Activity ==



{{Infobox_tool_details
|ohloh_id=
}}

<rss max=7>https://github.com/richardlehane/siegfried/commits/master.atom</rss>

Siegfried

2015-04-23T09:28:36Z

Yfriese:

{{Infobox_tool
|purpose=A PRONOM based, command line, file format identification tool using Aho Corasick matching and no buffer limits.
|image=
|homepage=http://www.itforarchivists.com/siegfried
|license=Apache License 2.0
|platforms=
}}


[[Category:File Format Identification]]



== Description ==

Siegried is a file format identification tool that, like DROID and Fido, is based on PRONOM. However, it uses a different pattern matching algorithm that offers different strengths and weaknesses to those other PRONOM based tools. A detailed description of the tool and why it was created can be found in [http://www.openplanetsfoundation.org/blogs/2014-09-27-siegfried-pronom-based-file-format-identification-tool this blog post].
Besides, there is a more detailed description in terms of functionality on the Github Page of Siegfried [https://github.com/richardlehane/siegfried].

== User Experiences ==
The command line tool is very easy to handle. The default output is yaml. This can be changed to csv or json.
Usual command: sf file.ext (will output in yaml)
Change output to csv: sf -csv file.ext
Chante output to json: sf -json file.ext


== Development Activity ==



{{Infobox_tool_details
|ohloh_id=
}}

<rss max=7>https://github.com/richardlehane/siegfried/commits/master.atom</rss>

Rosetta

2015-01-15T09:27:44Z

Yfriese: edited the Description section with openly available information from studies and presentations

{{Infobox_tool
|purpose=Designed in collaboration with the National Library of New Zealand and reviewed by an international peer group of recognized leaders and innovators, Ex Libris Rosetta enables institutions to preserve and provide access to the collections in their care, now and in the future.
|image=
|homepage=http://www.exlibrisgroup.com/category/RosettaOverview
|license=
|platforms=
}}


[[Category:Preservation System]]

= Description =
Designed in collaboration with the National Library of New Zealand and reviewed by an international peer group of recognized leaders and innovators, Ex Libris Rosetta enables institutions to preserve and provide access to the collections in their care, now and in the future.

Rosetta is a complete preservation solution. Its focus is to archive and preserve the digitized and born digital materials stored at academic and memory institutions like libraries and archives, research organizations and government institutions.
It aims to ensure data integrity and access over time for the archived digital data.

Rosetta supports the acquisition, validation, ingest, storage, preservation and dissemination of digitale objects that are in various formats and originate from many sources.

Rosetta uses standards like Premis and Mets. The METS profile of Ex Libris is published and open. Tehe data model of Rosetta is as following:

* intellectual entity (coherent set of content, the whole unit like e. g. a digitized book)
* representation (the set of files, including all the metadata)
* file
* bit-stream

Tools integrated in Rosetta
* BIRT (open source, eclipse-based Business Intelligence and Reporting Tools reporting system)
* thanks to a SDK, Rosetta users can easily build their own tools, submission applications and plug-ins
* Pronom connection

Rosetta is an OAIS-compliant solution.

= User Experiences =

= Development Activity =

= User Experiences =

= Development Activity =

Talk:Rosetta

2015-01-14T08:48:02Z

Yfriese: Created page with "Dear Folks, I think the logo/Picturen under "Development Activity" is not about the Rosetta from Ex Libris. That Rosetta has more than 515 lines of code (I am sure :-) ) and i..."

Dear Folks,
I think the logo/Picturen under "Development Activity" is not about the Rosetta from Ex Libris. That Rosetta has more than 515 lines of code (I am sure :-) ) and is not written in Ruby.
The real Logo should be like this [http://www.multidata.cz/obrazky/loga-ex-libris/Rosetta.jpg].
I try to add some Information about user experience.
Best, Yvonne

7-Zip

2013-12-18T08:29:39Z

Yfriese:

{{Infobox_tool
|purpose=7-Zip is a file archiver with a high compression ratio
|image=
|homepage=http://www.7-zip.org/
|license=
|platforms=
}}


[[Category:Rendering]]
[[Category:Container]]

= Description =
7-Zip is a file archiver with a high compression ratio

= User Experiences =
7zip can also be used to open an ISO Image File[http://en.wikipedia.org/wiki/ISO_image].

= Development Activity =

{{Infobox_tool_details
|ohloh_id=7-Zip
}}