- With what version of python do you work?
Python 2.7
- Django version?
1.9
- Do you have a ssh access to your server. If so I will need a ssh public key for deployment.
Yes
- Server config (for deployment). It number of processor`s cores and memory.
- Is REST interface required?
Required.
- That project. (my task). Will it be absolutely independent project from other part? Or it will using the same database?
It`s part of one big project. Currently it is part 2. Later we will have to merge all parts into one project. Maybe it will necessarily to completely rewrite the first part.
- Can we use postgres db (it will depends on django features and sql table structure)?
No. We will use mysql db.
- Only login page, without registration?
Later. But it is necessary to make if we will remake the first part.
- What does means that string "Location: State:City:District:Street:Building:NO." ? Does it describes a fields in the db? Or is it a format of one db field? If it is a list of db fields: should state and city be represented by own tables and referenced by foreign keys in the user table?
Db table for each reference + representing string.
- Pretty strange to have a "brand name" at user model/table.
Brand is for the STORE!
- Does one store should be belong to the ONE user?
Yes.
- Does vendors (users) will be the only kind of users?
No.
- Can user (vendor) see and use records (size, color, brand, etc) made by other vendors?
No. Vendor can use and see only data of his store.
- Who creates the store?
Vendor. But ONLY after admin (employee, manager) will register him OFFLINE.
- Does store creates after new user(vendor)? Or does store creates before the new user? <<<<<<< Updated upstream
VENDOR. look p. 7.
- Can registered vendor edit his profile?
Yes.
- Commodity model / table structure. Does catalog, size, color and etc should be references to another tables (foreign keys)? Or it is just CHAR values?
Tables.
- I need a logic (pseudo-code) generating and a sample of RFID code.
Waiting...
- What does it mean — "commodity tag". What it should looks like?
User customs tags (structure depends of db). Each commodity can has a multiple tags. The relation structure between commodity table and tag depends of the db choice. POSTGRES IS BETTER. But it is up to you.
- For what purpose are these tags? I need to imagine how they will be used?
For search.
- Only authenticated user can access to commodity views?
Yes.
- Does each user must have his own data with colors, sizes, brands, etc?
YES.