You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

  1. Transactional
    1. Need to be able to maintain consistency of the data. Also leads to more complex code to cover this issue.
    2. Reversibility of a true transaction is a key part of this requirement, again as the option is more complex code.
    3. 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.
    4. Record locking requirement can also be put here, for example, editing a MODS record and needing to also update the DC when done.
    5. This is important within an object, but also across objects, where a set of objects need to be updated.
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.