Purchase as separate entity

[peelman]

Currently each item gets a purchase date and PO numbers; with large orders that's a lot of duplicate data (i'm a normalization whore, so please forgive me in advance; I was made this way by several convincing professors).

Plus it would be nice to tie in a vendor (at least the name, but possibly contact information, which depending on how normalized you want to go, could demand another entity), since a PO might not be unique, and by itself doesn't help (unless you have the copy of the email from the user who ordered it and can search for that PO number).

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[snipe]

I'm a normalization whore too, but sometimes de-norming is the better choice for search, etc.

This is low-pri for me, but you're welcome to hack on it. Bear in mind that my plan here is also to have a vendors section that handles vendors like Rackspace, AWS, etc that don't necessarily tie into physical goods, so we may want to call them something other than vendors, or separate the two somehow. There aren't many SaaS/hosting vendors that I can think of that would have physical goods as well as virtual, so we'd need to make sure we kept that in mind.

[peelman]

Agreed, especially in light of that roadmap. I think if done right though, one entity could serve both purposes without conflicts. Just going to have to think on it some first.

I'll see what I can hack into a branch and perhaps between us we can come up with a solution that fits.