-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design of a brand repository #2
Comments
@PhilippePlagnol can you give a bit more info about what you mean by the brand for a product - perhaps a concrete example ... |
Yes, no prob : in the database, there're currently 3 tables for this brand repository : brand, brand_type and brand_group just go here for the example : http://www.product-open-data.com/group-list/ if you click on "Pepsico", you see that we are speaking of the the corporate group "Pespico" owning a lot of brands (including of course "Pepsi". For the group, we have the logo, the website and a link to wikipedia for more details now, click on the brand called "Izze" All the product you see are the product with the brand_cd = 3629 which is the ID of the brand "Izze" in our repository. So when you add a product in the database, you need to assign a brand and this is done manually because there's no public and worldwide brand repository for the moment,... we are building it ;) |
So strictly "brand" is what you have in Have I understood correctly? |
you can see the description of tables in this document: http://www.product-open-data.com/docs/POD-SPECS-2013.10.08_01.xlsx brands are stored in the brand table, groups are stored in the group table, brand_type only contains 3 records brand_type_cd is a foreign key in the brand table example : pepsi is a manufacturer brand, and the Tesco brands (http://realfood.tesco.com/our-food/our-brands.html) are retailer brands,... Have I answered to your question correctly ? |
In order to store a product into the database, a brand must be assigned.
The current data about brand and groups (id, name, picture, website, like to wikipedia articles,...) has been created manually).
A collaborative platform to manage this repository is critical for the project.
There's an important constraint : the brand identifier must be stable,...
The text was updated successfully, but these errors were encountered: