hwesta / bricks-inventory Goto Github PK

It would be nice if the sorting order of the color choice dropdown was sorted as to which colors were more popular. Something like the following SQL could be used to determine which are the most popular colors (at least as far as the partinstance db is concerned):

SELECT color_id, count(color_id)
FROM `inventory_partinstance`
GROUP BY color_id
ORDER BY count(color_id) DESC

Otherwise, we might want to sort by the most popular colors a person already has, though then we need to decide if we want to sort based on overall color counts (there could be thousands of the same part in the same color from a bulk/PaB purchase), or colors per unique part.

As the title says, it would be nice to have the date and time that something was input into the database stored.

When adding inventory, at least one amount/location pair must be filled in. The error messages are very unclear.

Instead of adding one part with the same keywords and locations, it would be nice to be able to add multiple parts with the same locations and keywords.
However, for locations we'll need some way to programmatically add the lowest level containers easily. See issue #2

There needs to be some sort of way to programmatically add locations. The current workflow of doing things manually is rather slow going.
Potential ways to do this:
-Bulk add in a range between two numbers with automatic incrementing a pattern
-Ability to add a the lowest level location straight from the Add Inventory page, potentially as in increment on a previous patter.
Both of these would need some way to specify a pattern, if we decide to allow something other than integer suffixes that increment by +1 each time.

The count of parts should always be a positive, non-zero integer. Presently accepted values are 0 and -9 (for example). PositiveIntegerField accepts 0, but not negative numbers.

There needs to be some way to edit an inventory instance that doesn't use the admin interface (we should never need to go into the admin interface). This could be useful if, for example, some inventory was added incorrectly.
Note, this might also require removing a partinstance entry if it was added by a part that was added with the wrong color to avoid polluting the partinstance database.

Keywords, locations, amounts, part and color should all be editable.