{description &&
{formatDescription(description)}
}
{visibleProps.map(([name, prop]) => {
const isRequired = requiredProps.includes(name);
const hasDefault = prop.default !== undefined;
const rawDefault = prop.default;
const isComplexDefault = hasDefault && (typeof rawDefault === "object" || typeof rawDefault === "string" && (rawDefault.length > 20 || rawDefault.includes('"')));
const fieldProps = {
key: name,
body: prop.title || name,
type: prop.type,
...prop.title && ({
post: [<>
API property: {name}]
}),
...isRequired && ({
required: true
}),
...!isComplexDefault && hasDefault ? {
default: sanitize(String(rawDefault))
} : {}
};
const isObject = prop.type === "object" && prop.properties;
const isArrayOfObjects = prop.type === "array" && prop.items?.type === "object" && prop.items.properties;
return
{prop.description && {formatDescription(prop.description)}
}
{isComplexDefault &&
Default:
{JSON.stringify(rawDefault, null, 2)}
}
{isArrayOfObjects &&
Object attributes:
{'{\n'}
{Object.entries(prop.items.properties).map(([iname, iprop]) => <>
{` ${iname}`}
{prop.items?.required?.includes(iname) && required}
{`: {\n display name: ${sanitize(iprop.title || '')}\n type: ${iprop.type}\n }\n`}
)}
{'}'}
}
{isObject &&
}
;
})}
See the detailed steps below.
## How to configure new document classification
1. Navigate to **Collections** > **Jobs** > **Add+** > **Classification** to create a new Classification job.
2. Configure the job as follows:
1. In the **Model Deployment Name** field, enter an ID for the new classification model.
2. In the **Training Data Path** field, enter the collection name or cloud storage path where your main content is stored.
3. In the **Training Data Format** field, leave the default `solr` value if the **Training Data Path** is a collection. Otherwise, specify the format of your data in cloud storage.
4. In the **Training collection content field**, enter the name of the field that contains the content to analyze.\
The content field that you choose depends on your use case and the types of queries that your users commonly make.\
For example, you could choose the description field if users tend to make descriptive queries like "4k TV" or "soft waterproof jacket".\
But if users are more likely to search for specific brands or products, such as "LG TV" or "North Face jacket", then the product name field might be more suitable.
5. In the **Training collection class field**, enter the name of the field that contains the category data.