Assistance with Configuring Multiple Asset Stores in DSpace Based on Communities

[R-Raman Bhardwaj]

Dear All,

  I am currently working on a DSpace instance and am looking to configure multiple asset stores such that items are stored in different asset stores based on their respective communities. After reviewing the documentation and various resources, I have a general idea of how to approach this, but I would greatly appreciate guidance from the community.

Define Multiple Asset Stores: II will define multiple asset stores like so:

[dspace]/config/spring/api/assetstore.xml

  assetstore.dir.0 = /dspace/assetstore1

 assetstore.dir.1 = /dspace/assetstore2  

Please help, how will we call the particular asset store based on the community document?

Regards,

Ravi Bhardwaj

  

 

[DSpace Technical Support]

Hi Ravi,

At this time, DSpace is only able to store *newly* added files in a **single assetstore**.  Take a look at the documentation for assetstore / bitstream store.

Essentially, the way this works is the first storage location is always numbered "0".  Initially all new files are stored in that location.

If, later on, you start to run out of space, you can create a new location numbered "1".  At this point, **all new files** are now stored in store "1".  The older store "0" is **only used** when accessing an older file which was previously saved to that location.

I don't believe there's a way to send different files to different locations based on their Community or Collection.  At least, I'm not aware of a way to do that.

Tim