AIP Prototype (from MIT): Adds ability to import and export
Community/Collection/Item AIPs and restore DSpace from assetstore contents
--------------------------------------------------------------------------------------------------------------------------------------
Key: DS-465
URL: http://jira.dspace.org/jira/browse/DS-465
Project: DSpace 1.x
Issue Type: New Feature
Components: DSpace API
Affects Versions: 1.n
Reporter: Tim Donohue
Assignee: Tim Donohue
Fix For: 1.n
Attachments: AIP-dspace-api.patch, AIP-dspace-sword.patch,
AIP-dspace.patch
This is a place to discuss the AIP (Archival Information Package) Prototype
built by the MIT PLEDGE project team in 2006-07. The Documentation for this
prototype is available on the Wiki at:
http://wiki.dspace.org/index.php/AipPrototype
I've spent some time updating this prototype so that it now works with the
latest 1.6.0 code on Trunk.
The latest version of the prototype is available in the DSpace SVN Sandbox at:
http://scm.dspace.org/svn/repo/sandbox/aip-1_6-prototype/
This AIP prototype implements several new features:
------------------------------------------------------------------------
(1) Allows DSpace to export/import Community/Collection/Item AIPs
* Community/Collection AIP is a zipped up METS file containing
Community/Collection metadata
* Item AIP is a zipped up METS file (metadata) and content files
(bitstreams + license file)
(2) Allows DSpace to store Community/Collection/Item AIPs (METS files) within
its existing Assetstore. These AIPs can be regenerated via cron to ensure they
are in sync with Database contents.
(3) Provides basic functionality to restore a Community/Collection or Item from
an exported AIP. However, "restoring" a Community/Collection is not very easy
as it Community/Collection AIPs only contain metadata and Handle references to
Items (not the Items themselves).
(4) Provides ability to rebuild DSpace hierarchy (Community/Collection/Item)
from just the Assetstore (in case of a corruption of your database). However,
restoring from assetstore doesn't restore epeople, groups, permissions, etc.
This AIP prototype modifies DSpace in the following ways:
-------------------------------------------------------------------------------
(A) Creates a new IngestionWrapper object which handles any sort of generic
"ingestion object" (whether it creates a Community/Collection or Item).
WorkspaceItem is now a subclass of IngestionWrapper specific to Items. The
various Packager classes now ingest IngestionWrapper objects (rather than just
WorkspaceItems), which allows them to also ingest Communities or Collections
from various packaging formats.
(B) Creates a few new database tables (internalaip and internalaip2bitstream)
which essentially serve as lookup tables for Internal AIPs stored as bitstreams
in the Assetstore (to differentiate them from normal bitstreams)
(C) Creates a RebuildBitstreamTable class which can restore your Bitstream
table from the assetstore contents. Also creates an AIPManager which can crawl
the newly restored Bitstream table to find internal AIPs and restore the
Community, Collection, Item hierarchy based on those internal AIPs.
More details about the AIP prototype can be found here:
http://wiki.dspace.org/index.php/AipPrototype
I've attached patch files which will give folks a better sense of the size of
the changes proposed by this prototype (most changes are to dspace-api, as
you'll see from the size of that patch). These patch files should work with
any 1.6.0 (current Trunk) version of DSpace.
If anyone is interested in helping me review, improve or "tease apart" the
various features provided by this patch let me know. Feedback on the prototype
is also very welcome, if you notice parts of this implementation which could
use improvement, etc. Also, feel free to vote/comment on whether you feel this
could be a good addition to a future version of DSpace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel