• About Knowledge Libraries
• To control Knowledge Library links using events
• To create and administer Knowledge Library content
• To create paragraph exclusion conditions
• To link Knowledge Library content
• To link Knowledge Library content from the Index
• To modify a Knowledge Library link
• To remove a Knowledge Library link
• To update the Knowledge Library and links
• Knowledge Library Version Update dialog

About Knowledge Libraries

A Knowledge Library is a document containing information that is to be shared with all users. As a Knowledge Library, this information can be made available to users so they can automatically update active documents with the organization’s latest knowledge.

Overview

CaseView Knowledge Libraries allow for the creation of content as well as storage in a central location where it may be linked into various client files. Library content can be anything from a company logo to a full set of financial statements.

For example, a Knowledge Library could be built to contain the various notes the firm regularly uses. Staff can then pick and choose the notes that should be added to the statements and link them in rather than having to type them manually.

The advantages of using CaseView Knowledge Libraries include:

• Content only needs to be built or customized once to make it available firm wide.
• Changes to the content, such as the rewording of a note, can be made in one central location. Documents which link to the content need only to update their links to integrate the changes.
• Content linked from a library is consistent from file to file; free of typos or style/grammatical errors that may appear when staff enter the content manually.
• Staff do not need extensive CaseView knowledge to prepare statements.

The Knowledge Library vs. Templates

Template client files, template documents, and the Knowledge Library share a common purpose, which is to have content stored in a central location to be shared in other files. Knowledge Libraries are simply focused on a smaller scale than template files and documents, storing instead the individual components that are used to create a document such as a variety of Headers or a Balance Sheet.

The main difference in the way these various components function, however, is in future updates. A client file or document based off a template is a standalone copy of that template. Should the template be modified in the future, the existing client file will not see those changes unless it is updated manually as well.

Knowledge Library content is brought into a CaseView document through a link that remains in place. At any point, staff can have CaseView update the links in the document to ensure their content matches what is in the library. CaseView can even compare the updated content in the library to modified content in the document and allow users to blend library changes with specific customization already performed in the document.

Related Topics

• Creating and Administering Knowledge Library Content
  • Creating Paragraph Exclusion Conditions
• Linking Knowledge Library Contents
  • Linking Knowledge Library contents from the Index
  • Updating the Knowledge Library and links
  • Modifying a Knowledge Library link
  • Controlling Knowledge Library links using events
  • Removing a Knowledge Library link