RPInventory

I'm going to rework the entire approach to conditions. Anytime users can change the condition, they will also be able to enter a description of the new condition. This would most obviously occur on loan/checkout returns and repairs.

This will require additions to the database. I will be making a 'condition' table to store the fixed-text conditions (Poor, Fair, Good, Excellent, etc. -- eventually we can give users the ability to edit these or add new ones). There will also be a 'condition_record' table, which will store an inventory id, a primary key to a 'condition', and the (optional) textual description entered by the user for each condition change.

This will enable the creation of an 'item history' page showing the changes in condition of an item over time.

Since there is still no functionality for actually changing the condition of an item when repairing it, I made a simple interface to update the condition while "repairing" the item.

Yeah, I found the beginnings of my implementation of this in uncommitted changes to git. You can tell how often I used my laptop this summer...

I never got anywhere because I was first modifying the database to allow conditions to be custom-defined instead of hardcoded everywhere.

This is another of my priorities.