anuj-adobe
commented
5 months ago Putting up some queries for more clarity...
Q1 - Evaluating columns to be added Current Product.Details.xlsx has these columns - Product Name | BU Tagging | Category Tagging | Industry Tagging | Priority Product Status | Notes
New Columns to be added in Product.Details.xlsx - SDS | TDS | Brochure
From where do we get SDS, Brochure product mapping data?
Do we need these metadata (present in TechnicalDataSheet.xlsx) as well? -
Gated Content | Date Created | Date Modified ? These fields seems to be related to TDS, so while merging should we add a prefix TDS to each of these column name?
Q2 - How do we use Taxonomy.xlsx in creating Product.Details.xlsx?
Q3 - Observation: A Product can have multiple TDS documents, brochures:
https://www.momentive.com/en-us/categories/encapsulants/conformalcoatings/products But a TDS document has 1877 product rows same as present in the product detail document.
Screenshot showing TDS mapping for "Conformal Coating Materials: SILTRUST™ ECC3011 & ECC3051S"
- How are multiple TDS documents associated in current site?
- Does this means that the author will have to add values comma separated in the excel sheet.
The customer has provided a few spreadsheets, which we need to merge into one speadsheet and also consider both authoring and code scenarios for the data.
1) First and foremost, both spreadsheets should be merged into one 2) We don't need to track if products have corresponding pages, we can use the search index for that once we add product name to it. 3) We need to make sure there is a true/false column for SDS, and also one for SDS 4) In the current spreadsheet, there is a field for language. We don't want that. Instead we want one tab per language. For now, just an English tab is sufficient, though we will likely want to add a Japanese tab soon as well. 5) Because products can have zero or more documents, there should be multiple columns (even if empty) for documents. 6) The industry and category fields should just be the last part of the tag. Confirm that we should be able to reconstruct the whole hierarchy of the tag from the last part alone (see the taxonomy worksheet for all the expected values) -- The reason we want to do it this way is in case the hierarchy changes, our data stays more or less relevant regardless.
Data: