This use case no longer has an advocate and is therefore to be disregarded
This use case has likely been completed by the feature described here.
- Transactional
- Need to be able to maintain consistency of the data. Also leads to more complex code to cover this issue.
- Reversibility of a true transaction is a key part of this requirement, again as the option is more complex code.
- A sample use case if changing an authority record and then needing to update the URIs in the related DM records, and needing to do that as a transaction so it is not done until all are completed.
- Record locking requirement can also be put here, for example, editing a MODS record and needing to also update the DC when done.
- This is important within an object, but also across objects, where a set of objects need to be updated.
1 Comment
David Wilcox
This is ready for acceptance testing as of 4.0-Alpha-4. There is an outstanding ticket to address letter e here.