Previously, the classification method for industry email list classifying and organizing content and deciding where to put it (= "design of taxonomy") was explained as " ketchup problem ", but the object to be classified (contents of contents) itself is What kind of ingredients (not just tomatoes and salt) are included? This time, how should the "ingredients" be constructed, using the industry email list website of a manufacturer that handles "product information" as an example? Or what kind of "information" is involved? I would like to take a concrete look at.
What is "product information"? Products for general industry email list consumers can be lined up on display shelves and can be picked up, so I think it's easy to imagine specific industry email list information about the product. In the case of " ketchup ", the manufacturer, contents, date of manufacture, expiration date, price, etc. can be imagined as "information on a product called ketchup". However, "ketchup" actually contains a lot more information, and the related information is also diverse. For example, variations in capacity and container, ingredients of allergens, or packaging (6 pieces or 6 dozen on 1 pallet).
The required information varies depending on the industry email list user's position and the situation. By the way, product information includes information about the "product itself" and its "incidental information". Here, the former is called " entity information " and the latter is called " meta information ". Due to space limitations in the catalog prepared by the manufacturer, the industry email list entity information and meta information are well-balanced with information of a certain depth, but when the state is expanded to the Web, the user Most of the time it doesn't match your information needs. How should these be organized and defined in the information design of a website?