Metal

Operations:

1. login
2. add transport container
3. add price list
4. add Metal_type
5. add inventory
6. add user (admin priv)
7. view audit (only admin) -- need to think about paging and/or limits

table design:

Inventory

 Inv_id            number -- PK
 Metal_id          number -- fk to metal_type 
 price_id          number -- fk to price_list
 trans_id          number -- fk to transport_container
 user_id_last_mod  number -- fk to users  
 time_stamp        date   -- last edit date 

Metal_type

 Metal_id          number    -- PK
 Metal             string    -- Metal_name
 

Price_list

 price_id          number   -- PK
 value             number   --maybe based on penny or something...might string it depending 

Transport_container

 trans_id          number  -- PK
 trans_name        string 

Users

 user_id           number -- PK 
 user_name         string -- username
 Lang_id           number -- fk language_translate

User_priv

 uniq_id           number -- PK
 priv_level        number -- 1 admin, 2 user
 user_id           number -- fk users

Language_translate

 Lang_id           number  --  PK
 Field_id          number  -- field in page maybe
 text_string       string  -- text to put in field

Inventory_audit

 Inv_id            number -- PK
 Metal_id          number -- fk to metal_type 
 price_id          number -- fk to price_list
 trans_id          number -- fk to transport_container
 user_id_last_mod  number -- fk to users 
 time_edit         date   -- when entry was updated