Comment 5 for bug 1777675

Jeff,

I'm open to different approaches, but, to be honest, this is the kind of feedback I would love to get when MassLNC shares its requirements for upcoming development projects to the general list or even when the LP bug is first submitted. I'm still trying to figure out a good way to do so in a way that encourages this type of discussion before we move on to the next step of contracting with devvelopers.

Aside from that, to give some background on this project, there have been many inventory projects discussed over the years, but none have been implemented because of the large cost of the project to do a full inventory module. We also did not have the resources to pursue a larger project. However, our thought was that these small additions to the database, along with being able to update the fields and view them from existing client interfaces, could go a long way toward adding some support for inventory, rather than pushing off this project again to some future time when we can do something larger.

For our purposes, the most recent inventory data is what our staffs are most interested in storing when they are performing inventory in the system. Is there a use case for storing dates that go further back? What are the advantages you see for adding them to a different table? Would you want to see those older inventory dates/workstations from the client?