DSpacers, I'm working on some tools to automate the update of items with SWORD v2.
Experimenting with curl, I can retrieve a representation of a desired item/container, modify the xml, then send it back using PUT (an update). Have successfully worked on replacing the bitstream/file, and metadata. The odd behavior that I encounter is it will not replace a metadata field, like say "dc.description.abstract" or "dc.date.issued". These fields are *duplicated* instead, and only the original field is initially seen from the web. Once drilling down into the item, both fields can now be seen! Of course my desire is to replace the metadata field, not duplicate it. Later I can edit as admin via the web to delete the original abstract (for example), but that defeats the purpose of automated tools. Some [maybe] pertinent points: a. swordv2-server.cfg changed to use org.dspace.sword2.WorkflowManagerUnrestricted, from WorkflowManagerDefault, to allow update/delete b. bitstream/file update done using edit-media URI, metadata update done using edit URI Anyone know more about this? cheers, Ed ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
