...
You have to do a little planning before undertaking the conversion.
Review the appropriate documentation (e.g. About + Data + Formats and
BitstreamFormat + Renovation)
and be able to answer the questions below.
...
Download Patch to DSpace 1.5 Source\\
- Shutdown your DSpace archive, i.e. the Java Servlet container / webserver.
- Update your install directory (i.e.
Code Block |
---|
$\{DSPACE_INSTALL\} |
to the 1.6 prototype: Apply patches to the 1.5 source and rebuild or acquire a 1.6 binary distribution. - While in the install directory, run to install new code.
- Check that
Code Block |
---|
$\{DSPACE_HOME\} |
has a subdirectory; if not, copy it over from the distribution hierarchy. You'll probably need to do that.
e.g. Code Block |
---|
cp -rp config/formats $\{DSPACE_HOME\}/config |
- Edit the DSpace Configuration as outlined below:
...
Panel |
---|
- Format Registry Configuration
formatRegistry.Provisional.validate = true formatRegistry.Provisional.schema = ${dspace.dir}/config/formats/formats.xsd formatRegistry.Provisional.document = ${dspace.dir}/config/formats/provisional-formats.xml #
- DROID's signature file - see http://droid.sourceforge.net/
Image Removed formatIdentifier.DROID.signatureFile = ${dspace.dir}/config/formats/DROID_SignatureFile_V13.xml # - PRONOM setup
formatRegistry.PRONOM.contact = http://www.nationalarchives.gov.uk/ Image Removed formatRegistry.PRONOM.dir = ${dspace.dir}/config/formats/PRONOM # - Set of registries (not a stack)
plugin.named.org.dspace.content.format.FormatRegistry = \ org.dspace.content.format.PRONOMFormatRegistry = PRONOM, \ org.dspace.content.format.ProvisionalFormatRegistry = Provisional # - Format identifier stack - NOTE: TextSubtypeHelper must come last.
plugin.sequence.org.dspace.content.format.FormatIdentifier = \ org.dspace.content.format.DROIDIdentifier, \ org.dspace.content.format.TextHeuristicIdentifier, \ org.dspace.content.format.CSSIdentifier, \ org.dspace.content.format.ProvisionalFormatRegistry, \ org.dspace.content.format.TextSubtypeHelper # - CSS SAC parser implementation
formatIdentifier.CSSIdentifier.parser = org.w3c.flute.parser.Parser # - Identifier(s) returned for CSS hits; first one is canonical.
formatIdentifier.CSSIdentifier.identifiers = PRONOM:x-fmt/224 # - Add this if your archive contains tar files.
#formatIdentifier.TextHeuristicIdentifier.formats.tar = PRONOM:x-fmt/265 # - Subtypes of Text formats to be promoted if ID'd by filename extension
formatIdentifier.TextSubtypeHelper.subtypes = \ PRONOM:x-fmt/224, \ PRONOM:x-fmt/91, PRONOM:x-fmt/406, PRONOM:x-fmt/407, PRONOM:x-fmt/408, \ PRONOM:fmt/122, PRONOM:fmt/123, PRONOM:fmt/124, \ PRONOM:fmt/14, PRONOM:fmt/15, PRONOM:fmt/16, PRONOM:fmt/17, \ PRONOM:fmt/18, PRONOM:fmt/19, PRONOM:fmt/20, PRONOM:fmt/95, \ PRONOM:fmt/96, \ PRONOM:fmt/144, PRONOM:fmt/145, PRONOM:fmt/146, PRONOM:fmt/157, \ PRONOM:fmt/146, PRONOM:fmt/147, PRONOM:fmt/158, PRONOM:fmt/148, \ PRONOM:fmt/101, PRONOM:x-fmt/183, PRONOM:x-fmt/160
|
...
Don't worry too much about getting everything perfect the first time, though.
You can always re-identify the formats of specific Bitstreams and
groups of them with the
BitstreamFormat + Workbench
utility, even after the conversion is finished.
...
Now you can examine the Bitstream by visiting it through the DSpace web
server, e.g.
If corrections are necessary, use the BitstreamFormat + Workbench
(
Code Block |
---|
org.dspace.administer.Formats |
...
If a problem or mistake in the BitstreamFormat conversion only becomes
apparent after you finish the conversion process (Phase 3) and thus
cannot go back to it, you can still put it right. The
BitstreamFormat + Workbench tool,
Code Block |
---|
org.dspace.administer.Formats |
...
filename extension that
was not identified correctly before, and retry identifying it, e.g.
with the BitstreamFormat + Workbench utility.
</html>