...
Implementation Characteristics
- Effort
- Risk
- Maintenanceis spread across any parts of the system that interacts with items
- Requires breaking compatibility changes in inventory
- Teams are (hopefully) familiar with making breaking compatibility changes and how to manage the impact of them
- Maintenance effort is likely related to how much needs to be inferred from whether an item is related to one or many holdings
Multiple items for a bound-with
...
- Which items can be requested, only the primary / independent, or any?
- Which items are checked out, is it only the primary or all?
Implementation Characteristics
- Effort is concentrated on
- inventory (weakening constraints, synchronising information between items)
- parts of the system that need to identify whether items are bound-with or not
- parts of the system that need to edit / change / update an item
- Other parts of the system may have relied upon constraints in inventory that are being weakened e.g. only a single item with a barcode
- Complexity of identifying and understanding items which are either independent or primary items is spread through out the system
- The complexity introduced for identifying items and updating them does not reduce over time
Multiple items and single unit of circulation for a bound-with (Marc's more radical model)
...
- Is it an item or a unit of circulation that has a status? This might be especially interesting for processes like cataloguing, where all of the copies in a unit of circulation would go to that process, yet not all might actually be catalogued.
- Which parts of the system needs to understand both the bibliographic copy and unit of circulation aspects e.g. circulation, orders / receiving
Implementation Characteristics
- Requires breaking compatibility changes in inventory (and probably circulation)
- Effort is concentrated on
- inventory (introducing the circulation unit record type)
- parts of the system which interact with items and care about unit of circulation attributes
- Significantly more effort required for upgrading existing records to work with the new model
- The complexity is explicit in the model and may reduce the maintenance once the new model has settled in e.g. either interact with an item or a unit of circulation, don't need to infer between the two