Upload Knowledge Files from ePublisher
A WebWorks Reverb 2.0 target with Generate Knowledge Base enabled writes Knowledge Files on every build: knowledge-*.zip archives of the published pages. Uploaded to the Assistant, they are its Grounding Knowledge for Reverb 2.0 help. The Reverb Assistant answers from them, and Reverb 2.0 help links each of its citations to the page and section it came from.
Where the build puts them
The build writes the archives to the output folder, beside index.html.
Target setting | Archives |
|---|---|
Generate Knowledge Base | One for the project: |
Generate Knowledge Base Per Parcel as well | One per parcel: |
The <hash> part changes on every build.
Upload the archives after a publish
In AI Assistants, open the Assistant whose Assistant ID the target uses.
On the Configure tab, go to Knowledge Base.
Under Uploaded, select the archives this build replaces and click Delete Selected (the trash icon). With per-parcel archives, select only the parcels you are replacing.
Drag the build's archives onto the dropzone. With per-parcel archives, add only the parcels that changed.
Click Save Changes.
When the Indexing banner clears, the Assistant answers from this build's pages. For the first upload, skip step 3.
Each build names its archives differently, so an upload never replaces an earlier archive. An outdated archive left in the Knowledge Base keeps answering with pages you have changed.
If an archive's row says that some links couldn't be used because they were relative, that is expected: the links between pages in Knowledge Files are relative, and the Reverb Assistant's citations don't use them. See Links and sources in answers.
Near the plan's storage cap, the archives you remove still count until their removal has finished indexing. If the upload is refused, remove the old archives and save first, then upload. See Knowledge Base problems.
Knowledge Files and the Embedded Assistant
Knowledge Files carry no web address, so the Embedded Assistant can't list them under its answers or link to the pages they hold. To have it link visitors to your published help, import the help as a website; see Import a website.