Tavina

Knowledge Library overview

๐Ÿ“– This content is synced from the Tavina Handbook.
The canonical version always lives at https://tavina.ai/docs/friendly/files-knowledge/knowledge-library-overview

Knowledge Library overview

The Knowledge Library is Tavina’s home for uploaded and imported document knowledge. Instead of treating every long file as a one-time chat attachment, Tavina can turn document-like content into Sources that can be organized, processed, retrieved, and cited.

Key terms

Term Meaning
Knowledge Library The area where Tavina stores document-like knowledge for later use.
Catalog A group of Sources. Catalogs help organize documents by topic, project, or purpose.
Library Inbox The default Catalog for new uploads and imports when you do not choose another Catalog.
Source A document-like item such as an uploaded file or imported reference.
Chunk A smaller piece of extracted Source content used for retrieval, citation, and long-document workflows.

Why Sources matter

Sources let Tavina track more than a file name. A Source can include processing state, provenance, extracted text or Markdown derivatives, chunks, indexes, and Catalog membership.

That makes it easier for Tavina to answer questions like:

  • “Which document did you use?”
  • “Which pages or sections support this answer?”
  • “Was the whole Source processed?”
  • “Were any chunks missing, skipped, failed, or unavailable?”

Processing states

A Source may be ready immediately, or it may need processing. Tavina should report processing honestly. Common states include pending, extracting, extracted, chunked, indexed, partial, failed, OCR-needed, encrypted/blocked, or unavailable.

A partial or failed Source can still be useful, but only within the parts Tavina can access.

What you see in the PWA

Open Knowledge Library from the toolbar. It is hidden by default on new accounts; enable it under Settings โ†’ Appearance โ†’ Toolbar (see Appearance settings for the full toolbar controls). Read-aloud in the Library follows your voice selection in Identity settings; everything else the Library exposes is in its own panel rather than in Settings. The panel is organized around your Catalogs and Sources:

  • Catalog list โ€” choose the Library Inbox, a personal Catalog, or an available System Catalog.
  • Source list โ€” see the documents, URLs, Markdown, text, PDFs, EPUBs, and other source records in the selected Catalog.
  • Status details โ€” check whether a Source is pending, extracted, partial, failed, OCR-needed, stale, or blocked.
  • Preview โ€” open a Source’s preview to read its content as a rendered document: headings, lists, tables, callouts, images (stored uploads or web addresses), footnotes, and code blocks all display (tavina/tavina#2391, tavina/tavina#2459), the same formatting Notepad notes use. The preview is read-only.
  • Summaries โ€” a Source with a generated summary shows it right on its card, with an out of date badge when the summary predates the Source’s latest change and a refresh control to request a new one (tavina/tavina#2399).
  • Read aloud โ€” listen to a Source, or a selected passage, with play, pause, and skip controls; long Sources are read in comfortable segments rather than one giant run, and the control stays out of the way when voice isn’t set up on your account (tavina/tavina#2403).
  • Curation queues โ€” Needs review, Recently added, and Stale views per Catalog surface what deserves attention, with one-click jumps to the exact field to fix (tavina/tavina#2402).
  • Duplicates โ€” a Find duplicates check groups likely copies with the evidence for each match; a merge always asks for confirmation first, keeps one canonical Source with the combined metadata, repoints existing citations and links, and is captured to version history so it can be undone (tavina/tavina#2400).
  • Facets and links โ€” filter a Catalog by its declared metadata fields, and follow each Source’s See also links and provenance card (see below).
  • Actions โ€” when available, rename or delete personal Catalogs, add Sources, refresh Sources, clone System Catalog material into your own Catalog, or remove Sources you no longer want. Deletes and removals ask for your confirmation, are captured to version history first, and can be restored; a purged original can be restored byte-for-byte and purged derivatives regenerated (tavina/tavina#1951, tavina/tavina#1952, tavina/tavina#1953).

If you are not sure what changed after an upload, open Knowledge Library and look at the selected Catalog’s Source list before asking detailed questions.

Upload and use flow

A practical first upload looks like this:

  1. Open Knowledge Library from the toolbar.
  2. Choose the Catalog where the file belongs, or use the Library Inbox when you are not sure yet.
  3. Use the add/upload Source control. Depending on the Source type, Tavina may ask for a file, URL, pasted text, or Source title.
  4. Wait for the Source status to finish processing. Some files may be partial, failed, OCR-needed, encrypted/blocked, or unsupported.
  5. Ask Tavina a question that names the Source or Catalog.
  6. Ask for citations when the answer depends on a document.

Good first questions after an upload:

  • “Summarize the PDF I just uploaded.”
  • “What are the three most important sections in this Source?”
  • “What does this manual say about warranty claims?”
  • “Which pages or sections did you use?”
  • “Search only my Home Repairs Catalog for this answer.”

Searching and intelligent queries

Broad questions work best when the answer could be anywhere in your library. Targeted questions work best when you know the Catalog or Source.

Use a broad query when you want discovery:

  • “Do I have anything about roof repairs?”
  • “Find Sources that mention account cancellation.”

Use a targeted query when accuracy matters:

  • “In the 2024 benefits PDF, what is the deductible?”
  • “Search only the Travel Catalog for passport renewal instructions.”

If Tavina’s answer feels too broad, ask it to narrow the scope. If it seems too narrow, ask what Catalogs or Sources it searched.

When a Catalog’s Sources carry an authority tier or evidence grade, searching weighs them: stronger material ranks higher in the results, and each result shows its tier and evidence grade so you can weigh the evidence at a glance. Sources without any authority information keep their normal ranking โ€” nothing is hidden or reordered for them (tavina/tavina#2401).

How Tavina answers from the Library

For a specific question, Tavina may retrieve relevant chunks from a Source or Catalog. For a broad summary or review, Tavina may need a whole-Source traversal that tracks coverage.

The answer should distinguish between these modes. Targeted retrieval is not the same as reading every page.

Structured metadata and faceted filtering

A Catalog can declare typed metadata fields for its Sources (tavina/tavina#2392) โ€” for example an evidence grade, a source tier, a reviewer, or a last-reviewed date, each with its type and, where useful, a fixed set of allowed values. You choose the fields per Catalog, so a plant reference Catalog and a product-manual Catalog can track different facts.

  • Filtering โ€” the declared fields become a filter bar above the Source list. Pick values to narrow the list โ€” for example every safety-flagged Source, or everything not reviewed in the last twelve months โ€” and clear the filters when done.
  • Fail-closed validation โ€” once a field is declared, a Source cannot be saved with an invalid value for it: a rejected save explains what is wrong instead of quietly keeping bad data. Undeclared extra metadata stays untouched.
  • Review status on the card โ€” filled review fields show on the Source card itself, such as the evidence grade and who reviewed it last, so trust signals are visible before you open a Source.
  • Your agent can read and set these fields for you, and can filter a Catalog by them when you ask โ€” “show only safety-flagged entries”.

Cross-source links and citations

Sources can reference each other with typed links (tavina/tavina#2394) โ€” see also, supersedes, part of, and contradicts. Both ends show the link with its proper label, and removing a link is one click. Read-only and system material cannot be the source of a link, so curated content stays as published, though it can be pointed at.

Each Source also carries an always-visible provenance card โ€” where it came from (an imported web address or added in Tavina), when it was retrieved, and how trustworthy you rate it โ€” plus a one-click citation export in BibTeX, RIS, or plain text for reference managers and papers. See Long documents, citations, and coverage for how citations should be used in answers.

Sharing Catalogs with friends

Catalogs are private by default. You can share a personal Catalog you own with a verified friend, per Catalog (tavina/tavina#2045).

  • Share a Catalog โ€” open the Catalog, choose Share, and pick a verified friend. You choose the permission: View only (browse, search, ask questions, read Sources) or Edit (add, update, and remove Sources, and trigger refreshes).
  • Accept or deny โ€” your friend gets an invitation they must accept before they see anything. Invitations surface in the notification bell’s Share invitations section and under Settings โ†’ Account โ†’ Shared Tools. Denying simply discards the invitation.
  • One master copy โ€” the Catalog stays yours. Friends always see your current Sources and any changes you make, automatically. They never get a forked or stale copy.
  • Owner-only management โ€” renaming, changing the description or icon, retrieval defaults, deleting the Catalog, and managing its shares stay owner-only.
  • Revoke or leave โ€” you can revoke a share at any moment and access stops immediately. Recipients can leave a shared Catalog on their own.
  • Assistant access โ€” each recipient controls whether their Tavina agent may use a shared Catalog. You cannot force agent access on a recipient.
  • System Catalogs (published by Tavina) follow their own subscribe flow and cannot be shared this way.

Deleting a Catalog you have shared revokes every share as part of deletion recovery, so no recipient keeps access to removed material.

Related pages

Scroll to Top