It is a companion tool to Item Import and uses the DSpace simple archive format to specify changes in metadata and bitstream contents.
Item Updated I did an Update and making it trigger itself. If you’re dealing with a event receiver with access to server side code, this is not a problem.
Writing that makes your world pink and sparkly again.
You use collection events to monitor changes to a collection to update the display.
For example, if a custom control uses a collection as its data provider, and you want the control to be updated dynamically and to display the revised data each time the collection changes, the control can monitor the collection events and update accordingly.
All these actions can be combined in a single batch run.
Item Update supports an undo feature for all actions except bitstream deletion. However, unlike Item Import, there is no resume feature for incomplete processing.
The Data Grid class, for example, uses the method to optimize performance in cases where multiple items in a collection are being edited at once.
By disabling the auto update until all changes are made, a control like the Data Grid control can receive an update event as a single batch instead of reacting to multiple events.
But this is the barren end empty world of the remote event receiver and no such this is available.
How I solved it Googleing this helped me not one bit and my first solution was something I would like to hide at the bottom of some server (I don’t want to talk about it, let’s just say it had something to do with counting the seconds since the last update).
This was the method I created: It checks if the property exists at all (it doesn’t if it is an Item Added-event and the property is custom made) and if it differs.