Closed luis100 closed 9 years ago
Hi Luis
I wrote KOST-Val for Windows :-( But maybe the SIARD validation works with the v1.5.0_Linux_alpha release (new kostval_en.jar)?! Can you please check that! Thanks
Claire
@Chlara, I tested the v1.5.0_Linux_alpha release but when executing it gives no output at all, even when I call it without any arguments, where it should be printing the syntax.
@luis100 can please give me a screenshot / textcopy of the console and from the kostval.conf.xml in configuration?
@luis100 it gives no output if your command is kostval_en.jar. But if your command begins with java -jar kostval_en.jar it shoud return this (testet on windows):
incomplete KOST-Val command Building KOST-Val command:
Java -jar kostval.jar-path Val-type file-path [-v]
a-------- b--------------- c------- d-------- e---
a = Java command
b = path and file kostval.jar
c = Type of validation:
--format (pure format validation) or
--sip (SIP validation)
d = path and full name of the file or folder being validated
e = verbose option, if the original reports are to be kept
No validation performed.
i notice that i shoud change kostval.jar into kostval_en.jar
@Chlara, the problem was I was running the jar you provided outside the KOST-Val, which gives no error when running. I moved the new linux jar into the folder of the previous release and ran it again, now the error is as follows:
$ java -jar kostval_en2.jar --format ~/old/retrievoTest.siard
KOST-Val
The configuration file from the JhoveApp does not exist on the enclosed place. Please check the configuration.
I guess I am missing Jhove config, but where should it be? Should I install Jhove inside the KOST-Val directory?
Another follow-up, the problem with the JHove config was due to the configuration in kostval.conf.xml, where the path separator was wrong for Linux, I think the forward slash (/) can be used here to make the paths platform independent.
I fixed that on my configuration/kostval.conf.xml
and ran it again, now the validation seems to be running.
I ran the tool against a 22GB zip compressed SIARD file, and the result is:
$ java -jar kostval_en2.jar --format ~/old/retrievoTest_compressed.siard
KOST-Val
Validation: SIARD
/home/lfaria/old/retrievoTest_compressed.siard
Invalid
Looking at the log file I found the following message:
<Error><Modul>A) readability</Modul><Message>The SIARD file is compressed. -> Validation aborted!</Message></Error>
Which I found odd, is the compression a problem on the validity of the SIARD file?
I had to unzipped the SIARD file into a folder of 85GB and tried again:
$ java -jar kostval_en2.jar --format ~/old/retrievoTest_expanded.siard
KOST-Val
<Info><Message>No validation format could be performed (other formats as TIFF, PDF and SIARD or excluded in the configuration).</Message></Info>
So the program is also not expecting an expanded SIARD file, what is then the format it is expecting?
Hi Luis
The SIARD specification say on point 4.1 that it must be an uncompressed ZIP-File with the extension .siard
The link to the specification in German and French: http://www.ech.ch/vechweb/page?p=dossier&documentNumber=eCH-0165
The English specification should been published in January 2015.
Note: At the Moment we are writing an Addendum that will allow deflated ZIP compression and splitting.
OK, I understand. We've tested the SIARD output of our db-preservation-toolkit and besides the compression there are also a couple of issues that we need to solve. Nevertheless, your tool seems to work fine in Linux for checking SIARD files, besides the configuration change described above. Will try to fix the problems as soon as possible and provide you feedback on the db-preservation-toolkit issues, so I'll close this one now. Thanks!
Thanks Luis
I changed the Note from the v1.5.0_Linux_alpha pre-release.
When running on Linux an error occurs due to the file path separator: