Quick notes inline.. On 5/17/2012 11:43 AM, Richard Jones wrote: > Hi Tim, > > On Thu, May 17, 2012 at 3:30 PM, Tim Donohue <[email protected] > <mailto:[email protected]>> wrote: > > Hi Richard, > > One other thing to consider (though this might be too complex for > your scenario). If you transmitted DSpace AIPs via SWORD than you > could submit authorization permissions in the AIP itself (in METS). > > In other words, the AIP Backup & Restore feature allows DSpace > permissions to be translated into the METSRights Schema, as > described here: > https://wiki.duraspace.org/__display/DSDOC18/DSpace+AIP+__Format > <https://wiki.duraspace.org/display/DSDOC18/DSpace+AIP+Format> > > When an AIP is restored, it actually will be assigned the > authorization settings as detailed in METSRights (this is controlled > by the METSRightsCrosswalk). > > Again, not sure if this is really what you are looking for or not, > but it's something to be aware of. > > > Thanks - I wasn't aware of that, actually. > > The METS support in SWORDv2 has dropped off a bit, because the > complexity of writing the plugin was beyond me in the time-frame of the > project. For this project we are using a profile of BagIt, which we > like very much (I'd love to see it used more in DSpace).
In regards to BagIt -- Richard Rodgers has been working on generating BagIt-based AIPs as part of the "Replication Suite" add-on described here: https://wiki.duraspace.org/display/DSPACE/ReplicationTaskSuite Codebase: https://github.com/DSpace/dspace-replicate However, at this point in time, the BagIt-based AIPs are not as fully-featured as the METS-based AIPs. For example, BagIt AIPs currently don't store Group/EPeople/Policy information, whereas the METS-based AIPs do store that info. But, RichardR & I have talked about achieving feature-parity between the BagIt AIPs and the METS AIPs. Personally, I'd also like to see BagIt used more in DSpace as well. > With lacking support for DSpace AIPs in SWORDv2, that really makes me > think I should sit down and try to re-design the packager plugin process > so that it's easier to get it working again. Some thoughts may follow, > and at least one or two conversations over a drink in Edinburgh in July > (presuming you will all be there)! I'd be all for re-designing the packager plugin process for DSpace in general. It's a bit messy overall, and very difficult to manage. Glad to hear ideas on it on this list or elsewhere (Unfortunately I'll miss out on OR12 because of family conflicts, so I'll miss out on the beer/discussions there. But, I can catch up on the decisions you all make later on.) - Tim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
