Prepare Input Template
This section talks about preparing the SKU input template for Content and Catalog.
Overview
Rubick OS Flow is a customizable editor for your cataloging and content operations. You can customize the workflows and SKU editor view, configure allowed values, and input files. Let us understand more about creating an input template while creating catalog and content orders.
Input Template for Catalog Orders
The input sheet for catalog order will be below the tab comprising 4 sheets: Export Summary, Instructions, Types, and Values.
This sheet captures the instructions to fill the two main sheets of the input template: types and values.
The sheet introduces the columns and rows in the types and values sheet and acts as a first-step guide to filling in data in the sheet.
Here are a few Key instructions for filling the sheet:
Don't change the order of sheets in the downloaded file.
Don't modify the names of the sheets in the excel.
Use datatypes from the allowed list only. Whenever unsure, use datatype as a string if it is a text/number or imageURLarray if it is an image link.
Always download the sample template from os.rubick.ai while creating an order. This ensures that you are accessing the latest template with all updates.
The Types sheet is the blueprint of your format. This sheet captures all the headers, the datatype, the mandatory flag, and hint text for each header.
Types Sheet has four major components:
Field Name: This is the header of the template. E.g. Product Name, Images, Description, Brand. The sequence of the field name generally matches the upload template for your website or marketplace.
Field Hint Text: This is the help text to explain the field name. You can also use it to provide example values, the format of the value to be filled, or guidelines to be followed by enriching the field. E.g. If the field name is Title, hint text can be Don't exceed 50 characters.
Mandatory or Not: This flag makes a field name mandatory to fill or not. When uploaded as mandatory, the field is highlighted in orange in the SKU editor to differentiate it from non-mandatory fields.
Field Type: This identifies the value type to be entered for the field name. This is to ensure that the wrong values aren't entered while cataloging.
You can also define allowed values for each field name in the same sheet. Allowed values are restricted values allowed for that particular attribute for your website or a marketplace. These values appear as dropdowns. The field type for dropdowns is to be set as select and can be filled as values after the field type for the field name wherever applicable.
This sheet captures the input values to be prefed to Rubick OS. This can be left completely blank if all the data has to be enriched on OS. Typically, the base data of the SKUs like product images, product link, legal and taxation information like HSN, GST, manufacturer information are prefilled before loading the data on to the Rubick OS Flow.
The headers in value sheet must match exactly as in the types sheet. Please note that even an error in case of the headers will not allow the upload of the sheet.
This sheet is a simple index with sheet links to instructions, types and values.
You can download the sample file from here or the button to download a sample template while creating the order.
Input Template for Content Orders
The input sheet for content order has only a sheet with the following headers:
a. Title - The title of the article to be written. You can list as many titles in the multiple rows to create one order for 1000s articles to be written.
b. Total Word Count - Define the word count per article. This acts as a threshold during the submission, and any content more than or less than the word count will not be allowed for submission. You can also control the threshold by introducing allowed % variance in word count (e.g. + or - 10% of word count)
c. Primary Keywords - List the keywords that must be included in the article. Rubick OS automatically validates the presence of keywords in the article and the quality of writing to ensure that the article is not a keyword dump and also analyzes if the required density is met.
d. Secondary Keywords - List the secondary keywords that must be included in the article. Rubick OS automatically validates the presence of keywords in the article and the quality of writing to ensure that the article is not a keyword dump and also analyzes if the required density is met.
e. Other Keywords - List if any other keywords are to be included beyond primary and secondary keywords.
f. Primary Keyword Density - Define the primary keyword density expected as a percentage of the total word count in the article.
g. Secondary Keywords Density - Define the secondary keyword density expected as a percentage of the total word count in the article.
h. Comments - Leave any additional instructions or comments for the writer.
All the values given here create a strong check system not to allow the system to pass any data that doesn't meet the threshold requirements.
You can download the sample file from here or the button to download a sample template while creating the order.
Last updated
Was this helpful?