Hi Kai,
first of all, you should reconsider your intention to do automatic
conversion to PDF/A. What is the ratio of successfull conversions on your
sample? When I tried it with our ETDs, even though the conversion reported
no errors, less than 5% of the resulting PDFs were valid PDF/A. I tried 2
different tools, one was Adobe prefligt and the other one I don't remember.
What is it you're trying to achieve? I'd recommend mandating new files to
be PDF/A compliant, but automatic conversion is likely to do more harm than
good - and especially *in place* conversion is a terrible preservation
practice.
Still, if you want to do that, you'll have to detect which assetstore files
are actually PDFs (using e.g. the "file" tool) and do the conversion on
them. Then you'll have to regenerate the MD5 checksums and write them to
the database - the "checksum" column in the "bitstream" table where the
filename matches the value in the "internal_id" column. A simple shell
script will do, but make sure to have a full backup of both your assetstore
and your database. Finally, use "[dspace]/bin/dspace checker" to check the
checksums.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
