Hi David, Out-of-the-box, DSpace only currently has two available Bitstream storage plugins -- a Filesystem one, and an Amazon S3 one. They are described here: https://wiki.duraspace.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore
So, if your external assetstore still "looks like" a filesystem folder to DSpace (e.g. a externally mounted drive looks like a filesystem folder), then DSpace should have no problems with it. However, if your external assetstore requires a special API or authentication/authorization scheme, then you'd likely need to build a custom BitStoreService plugin to handle it (which would require custom Java programming). It is possible to build your own custom BitStoreService plugin by extending our BitStoreService Java interface: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/storage/bitstore/BitStoreService.java You could model a custom plugin based on one of the existing ones: - Here's the filesystem storage plugin: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/storage/bitstore/DSBitStoreService.java - Here's the Amazon S3 storage plugin: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/storage/bitstore/S3BitStoreService.java If you build a custom plugin, you'd then need to "wire it up" via this Spring config: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/spring/api/bitstore.xml (This config is described in the documentation that I linked to above). Hopefully that gives you a few ideas of how you could support this in DSpace. Tim On Mon, Apr 1, 2019 at 1:46 PM <[email protected]> wrote: > I'm running DSpace 6.3 on my server which contains some sensitive records > that we would like to keep behind a firewall on a separate server than > where they are currently. Would it be possible to have DSpace point to, > and access, the assetstore while it's on a separate machine? I know you > can do it on Amazon Web Services (AWS) but i wasn't sure if this was > restrained to just AWS. We can't use AWS for the same reason we want to > move these records behind another firewall-- they're sensitive. > > I appreciate any help you can offer, > David K. > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
