Now that bug #1527342 (decouple checkout history) is done, the plan for this ticket becomes much simpler. I believe now we're only talking about the copy status UI (which lists recent circulations for a copy) and the copy "most recent circulations" interface.
1. The API(s) in question will return the X most recent circs found in action.all_circulation (or similar) -- the goal being to include active and aged circulations.
2. The interface code will be modified to handle action.aged_circulation in addition to action.circulation objects. In short, when an aged_circulation is encountered, the code should avoid referencing the "usr" column (and possibly others).
Now that bug #1527342 (decouple checkout history) is done, the plan for this ticket becomes much simpler. I believe now we're only talking about the copy status UI (which lists recent circulations for a copy) and the copy "most recent circulations" interface.
1. The API(s) in question will return the X most recent circs found in action. all_circulation (or similar) -- the goal being to include active and aged circulations.
2. The interface code will be modified to handle action. aged_circulatio n in addition to action.circulation objects. In short, when an aged_circulation is encountered, the code should avoid referencing the "usr" column (and possibly others).