FYI we are having discussions with Sun about integrating DSpace with
their Honeycomb CAS system. However, the approach I am advocating is to
build an SRB compatibility layer/driver/translator for the product, and
so insulate DSpace from the specifics of the Honeycomb API. Contact me
if interested.

On Wed, 2007-10-03 at 17:26 -0400, MacKenzie Smith wrote:
> Hi Robert,
> > * Does DSpace have service devices (like SOA or SOAP)?
> >   
> Yes, for submission (see 
> http://wiki.dspace.org/index.php/LightweightNetworkInterface).
> > * Is it correct that DSpace does not have an internal storage
> > management, which would mean (e.g.) to compress documents which are not
> > accessed for a given period, or to move them to an other storage 
> > location (e.g. a tape server) if the last access is much older?
> >   
> You can implement any storage layer underneath DSpace using the storage 
> API. There are implementations now for the local filesystem (the 
> default), SRB and S3 (in prototype, I believe). I think HP has also 
> implemented it with their HSM, but I don't know if there are other HSM 
> systems implemented now.
> > * And is it possible to bundle / relate different versions of the same 
> > document, e.g. preprint and postprint?
> >   
> This is handled now via metadata. For MIT's method of doing this see 
> http://wiki.dspace.org/static_files/f/fa/DSpace_Versioning_Feature_Summary_(July_2004).pdf
> 
> There are plans to change the DSpace data model in a future version so 
> that it can handle versions directly within an item. This is described 
> on the wiki (http://wiki.dspace.org/index.php/ArchReviewSynthesis). A 
> lot of this work has already started, and the plan is to complete these 
> changes in 2008.
> > * Does DSpace keep track of different versions of the same document to 
> > have a history of minor changes (compared to pre- and postprint)?
> >   
> It is a digital archive rather than an authoring system, so no, minor 
> changes to documents are noant normally kept. The idea is to store final 
> versions of documents and keep them forever, and to link different 
> *editions* of documents via metadata (see the last answer) so that users 
> can safely cite a particular version and not worry about it disappearing 
> later.
> 
> MacKenzie
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to