Difference between revisions of "Project:Inventory system"
Jump to navigation
Jump to search
(→Ideas) |
(→Ideas) |
||
| Line 19: | Line 19: | ||
::: Component | ::: Component | ||
; Properties: Each item has properties common to all item types, and ones unique to its category. | ; Properties: Each item has properties common to all item types, and ones unique to its category. | ||
| − | :; | + | :; For example (common): |
| − | + | :: Wiki page | |
| − | + | :: Date acquired | |
| − | + | :: Quantity | |
| − | + | :: Identification description | |
| − | + | :: Category | |
| − | + | :: Location | |
| − | :; | + | :; For example (unique to "Components"): |
| − | + | :: Reorder URL | |
| − | + | :: Reorder Price | |
; Queue: Items can be placed in to one or more queues, and can appear in queues multiple times (providing there is only one unresolved occurrence), to be processed at a later point. | ; Queue: Items can be placed in to one or more queues, and can appear in queues multiple times (providing there is only one unresolved occurrence), to be processed at a later point. | ||
| − | :; | + | :; For example: |
| − | + | :: Reorder | |
| − | + | :: Stock check | |
| − | + | :: Disposal | |
; Queue items: Linked to a regular item (extension of), but with the additional properties "Resolution" and "Resolution date" and attached to a queue. | ; Queue items: Linked to a regular item (extension of), but with the additional properties "Resolution" and "Resolution date" and attached to a queue. | ||
; Relation: Similar objects can be linked together, this can be resolved recursively up to a limit. | ; Relation: Similar objects can be linked together, this can be resolved recursively up to a limit. | ||
; Log: All changes appear in a log with a change description, previous value, new value, user, and time. | ; Log: All changes appear in a log with a change description, previous value, new value, user, and time. | ||
Revision as of 14:45, 8 August 2010
| Inventory system
| |
|---|---|
| Members | roberthl, ms7821 |
| QR code | |
We'd like to have an inventory system for cataloguing the space's equipment and supplies.
For now we're going to see how the Inventory page evolves, and then look in to what enhancements we need to make - if any.
Ideas
Here are some ideas I've had for the project, would appreciate comments. --Robert 13:33, 8 August 2010 (UTC)
The key point of any inventory application would be to provide an efficient workflow that makes the system highly usable, otherwise it will not be used and be little improvement over any existing system.
- List
- The application is centred around one list that contains all equipment, components, etc.
- Item
- The list is composed of items.
- Categories
- All items have one category.
- For example
- Component
- Properties
- Each item has properties common to all item types, and ones unique to its category.
- For example (common)
- Wiki page
- Date acquired
- Quantity
- Identification description
- Category
- Location
- For example (unique to "Components")
- Reorder URL
- Reorder Price
- Queue
- Items can be placed in to one or more queues, and can appear in queues multiple times (providing there is only one unresolved occurrence), to be processed at a later point.
- For example
- Reorder
- Stock check
- Disposal
- Queue items
- Linked to a regular item (extension of), but with the additional properties "Resolution" and "Resolution date" and attached to a queue.
- Relation
- Similar objects can be linked together, this can be resolved recursively up to a limit.
- Log
- All changes appear in a log with a change description, previous value, new value, user, and time.