(8 months later, I have a reply) intraLibrary is happiest using the IMS Content Package to apply metadata to an object after being dropped off by SWORD. An IMS Content Package consists of a imsmanifest.xml file containing the metadata (LOM) in it zipped together with the object. You could get more complicated, but we haven't explored that yet. I can provide a sample imsmanifest.xml file for use as a template to those who are interested. It's just a matter of variable substitution.
sorry for the delay, but I've only just learned this last month. Boyd On 05/18/2010 12:29 PM, Julie Allinson wrote: > Hi all, > > I'd like to get some views on an issue we are currently thinking through > at York, which I believe others building SWORD clients will also face. > > Here at York we are building a SWORD client which will (initially) > deposit to our local multimedia Digital Library (YODL - Fedora) and/or > to our shared institutional repository (WRRO - EPrints). In the future, > we might want to add additional SWORD targets. > > My questions is essentially what package? > > As far as I can see, we have three options: > > 1) Choose a package which best meets our local needs and configure the > Fedora/EPrints SWORD targets to support this? > 2) Chose a package which is supported 'out of the box' in Fedora/EPrints > and is 'a simple good enough' fit for local needs but don't worry about > other types of repositories? > 3) Do something that works out-of-the box for as many repositories with > SWORD targets as possible? > > Current SWORD implementations across the different repository platforms > vary in the package types they support. With the exception of > IntraLibrary (as it isn't open source), all are extensible so it is > possible to add new file handlers to deal with different packages in > different ways (and thus meet option 1 above). > > In the current demonstrators of Fedora, EPrints and DSpace will all > accept a METS package containing epdcx (SWAP) metadata. In DSpace and > EPrints these are unpacked and imported as objects within the > repository. If this METS package contains any other metadata instead of > or in addition to the epdcx the EPrints import will fail. This is, thus, > the only format that will satisfy option 3. > > From the work I did on SWAP and EPDCX a while ago, this format hasn't > really taken off, but there is still no alternative that can support > cross-disciplinary sharing of metadata. Apart from simple Dublin Core, > that is, which cannot meet all of our requirements. > > Views welcome! > > Julie > -- Boyd Duffee Keele University (01782) 734225 Student Facing Systems If I lose touch with reality, I hope I go all conspiracy-theory, tinfoil-hat delusional. Not "she can change" delusional. - asofterworld ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ sword-app-tech mailing list sword-app-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sword-app-tech
