The metadata sheet must exist in the FluidTopicsControlFile.xlsx file. Name it exactly metadata.
Example:
| document (filePath) | document (originId) | instance (filePath) | topic (originId) | metadataKey | metadataKey2 | |
|---|---|---|---|---|---|---|
| inheritance | yes | no | ||||
| api_ref_guide.ditamap | v1.ditaval | example_value1 | example_valueA | |||
| api_ref_guide.ditamap | example_value2 | |||||
| fluid-topics-configuration-and-administration-guide | ditamap_topic_id | example_valueC |
| Column | Mandatory? | Column value |
|---|---|---|
document (filePath) |
Yes There must be a document (filePath) or document (originId) value in each row. |
The path of the document to target in the archive. When uploading synchronously, use the document (filePath) column to target a document in the archive. |
document (originId) |
Yes There must be a document (filePath) or document (originId) value in each row. |
The identifier of the document to target. When uploading asynchronously, use the document (originId) column to target a document on the portal. |
instance (filePath) |
No | The path of a document variant to target in the archive. |
topic (originId) |
No | The originId of a topic to target. |
metadataKey |
No | metadataKey is a placeholder. It represents any metadata key. Replace it by any value. There can be any number of metadataKey columns. The metadataKey columns must be preceded by an empty column.The empty column can have inheritance in its second line. It makes it possible to define whether the metadata key value gets inherited by adding yes or no above the metadata key values. inheritance can be omitted. If it is omitted, its value is yes. |
All columns can only appear once.
See Use cases and examples for examples.