<?xml version="1.0" encoding="utf-8"?>
<html>
Pluggable Storage
Considerable thought, discussion, design, prototyping, etc has focused on what a DSpace+2.0 asset store should look like. In particular, whether and how such an asset store should model archival information packages (AIPs) in a more substantial manner than in the current architecture. This model is conceived as a DSpace asset store API/interface. Of course one big advantage of such an interface is the ease of writing implementations for different storage systems (file-based, grid, etc) and plugging them into DSpace. However, it should be noted that this benefit redounds to just having an interface, not having an AIP-aware one in particular.
...
- Download the interface and refactored storage manager, and cleanup:
- BitStore interface
- refactored bitstream storage manager
- .java
- BitstreamStorageManager.java
- Cleanup.javarefactored Cleanup
- Add all files to the DSpace source tree at
. The storage manager and cleanup will replace the existing source files.Code Block org/dspace/storage/bitstore
...
- Download the implementation or implementations you want to use, and place into above directory:
- Install bitstore dependencies:
- DSBitStore has none
- SRBBitStore requires jargon.jar and a broker instance. The former is part of the standard DSpace distribution, so no further requirements
- S3BitStore requires the jets3t java library (and its dependencies) available at
Code Block http://jets3t.s3.amazonaws.com/index.html
- Place all required jars in
Code Block dspace/lib
- Configure bitstores for use in DSpace:
- each 'assetstore' number in
can be assigned to an instance of a bitstore as follows:Code Block dspace.cfg
- each 'assetstore' number in
...