Librarians are among the best-positioned professionals to understand the value of an organized knowledge base — the entire professional discipline is organized around making information findable. Yet the knowledge base that most librarians build for their own professional use is substantially less organized than the collections they curate professionally.
The professional knowledge a librarian accumulates — which sources are most productive for specific research questions, what coverage gaps exist in specific databases, how patrons in this library typically approach research problems, what local cataloging decisions have been made and why — is the institutional expertise that makes a library more effective over time. A searchable KB organized around the four core domains of librarian professional knowledge converts this expertise from individual memory into retrievable institutional intelligence.
Domain 1: Reference and Research Support Knowledge
The reference and research support domain is organized around the research questions and patron needs that the library serves. This is the most retrieval-critical domain: when a patron arrives with a research question, the librarian needs to quickly access the professional knowledge most relevant to that question type.
Organization by research type (primary):
The most important organization dimension for reference knowledge is research type — what kind of research is being conducted, not what subject area it falls in. Genealogical research, legal research, medical literature review, and patent searching are distinct research types with their own source landscapes and strategies, even when they occur in the same subject area.
REFERENCE KNOWLEDGE BY RESEARCH TYPE
RESEARCH TYPE: [e.g., "Genealogical and local history research"]
TYPICAL RESEARCH QUESTIONS:
What patrons typically need: [Common research objectives]
How they typically describe what they need: [Their language]
What they actually need (which may differ): [The reframed understanding]
MOST PRODUCTIVE SOURCES (with currency dates):
For this question type, start with: [Primary source + why + date captured]
Secondary sources: [Supporting resources + dates]
When primary sources fall short: [Backup resources]
WHAT DOESN'T WORK (and why):
Sources that seem relevant but aren't: [The dead ends + specific reason]
Search strategies that waste time: [What to avoid]
COVERAGE GEOGRAPHY AND TIME:
Geographic coverage of key sources: [Where sources cover well and not]
Time period coverage: [Start dates + gaps in coverage]
Format gaps: [What's not digitized, where physical resources are needed]
PATRON POPULATION:
Who typically does this research: [Common patron types]
Their research skill level: [Generally experienced vs. beginning researchers]
What they're usually trying to accomplish: [Final purpose of the research]
REFERRAL KNOWLEDGE:
When to refer elsewhere: [When the library's resources aren't adequate]
Where to refer: [Specific institutions, archives, or specialists]
KB UPDATE DATE: [When this entry was last reviewed for accuracy]
Organization by subject area (secondary):
A secondary organization by subject area captures the collection and resource landscape for the library's major collecting areas. This is the "map of the territory" for each subject area — what the library holds, what key external resources exist, who the subject specialists are.
REFERENCE KNOWLEDGE BY SUBJECT AREA
SUBJECT: [e.g., "Local government and municipal records"]
COLLECTION STRENGTH:
What the library holds in this area: [Collection overview]
Where the collection is strongest: [Time periods, formats, geographic scope]
Known collection gaps: [What's missing]
KEY EXTERNAL RESOURCES:
[Database/archive name + date captured]: [What it offers + coverage + access notes]
SUBJECT COMMUNITY:
Professional organizations covering this area: [Societies, associations]
Subject specialists at partner institutions: [Named contacts where known]
TEACHING AND INSTRUCTION:
Courses typically requesting support in this area: [If applicable]
Research guides or instructional materials already developed: [References]
Domain 2: Collection and Source Intelligence
Collection and source intelligence documents the professional knowledge about the resources the library provides access to — their coverage, their strengths and weaknesses, their search characteristics, and their evolution over time.
This is the most time-sensitive domain. Sources change: databases update their interfaces, coverage dates extend, content is removed or added, quality signals shift. Source intelligence captured without a date becomes misleading as the source evolves.
SOURCE INTELLIGENCE ENTRY
Source name: [Database / Collection / Resource]
Source type: [ ] Subscription database [ ] Open access [ ] Physical collection
[ ] Institutional repository [ ] Other
Date captured: [When this entry was created or last updated]
COVERAGE:
What it contains: [Content description]
Time period: [Coverage start date + present or end date]
Geographic scope: [If applicable]
Format types: [Text, images, data, multimedia, etc.]
SEARCH CHARACTERISTICS:
Search syntax that works: [Specific operators, truncation, phrase search]
Subject vocabulary: [Controlled vocabulary notes, if applicable]
Filters that are useful: [Helpful limits]
QUALITY SIGNALS:
Peer review: [ ] Yes [ ] No [ ] Varies by section
Editorial standards notes: [Anything relevant about quality]
COVERAGE GAPS AND LIMITATIONS:
Known gaps: [What's missing from coverage]
Coverage that has changed: [If coverage has been added or removed over time]
INTERFACE NOTES:
Last interface update: [Date if known]
Quirks or workarounds: [Non-obvious behavior]
HOW I USE THIS SOURCE:
Most productive use cases: [When this source delivers best results]
When to look elsewhere: [Where it falls short]
ARCHIVE URL: [archive.org backup if a web resource]
The coverage gap field is the most practically important and most commonly undocumented aspect of source intelligence. A database that covers 1990 to present but has significant content gaps for the 1990-1997 period is not fully captured by its listed coverage dates; the gap needs to be documented.
Domain 3: Cataloging and Metadata Practice
The cataloging domain captures the professional knowledge accumulated through cataloging practice — the local policy decisions, the edge cases, the non-obvious classification choices, and the standard practice rationale.
CATALOGING PRACTICE KB
LOCAL POLICY DECISIONS:
Decision: [What the local policy is]
Date decided: [When]
Standard it relates to: [RDA rule / MARC field / LCSH practice]
Reasoning: [Why this policy was adopted]
Examples: [Representative records where this applies]
Exceptions: [When not to apply this]
Review date: [When this should be revisited]
EDGE CASES AND NON-OBVIOUS CLASSIFICATIONS:
Material type: [What kind of material]
The edge case: [What made this non-obvious]
How it was handled: [The cataloging decision]
Reasoning: [Why this approach]
Example record: [Reference to a specific catalog record]
STANDARDS REFERENCE:
RDA/MARC notes: [Frequently-referenced rule citations with notes on application]
LCSH notes: [Subject heading choices that are non-obvious + rationale]
Local authority file notes: [Local authority decisions]
Domain 4: Institutional and Professional Knowledge
Institutional and professional knowledge captures the organizational context that makes a librarian effective in a specific institution: the collection development rationale, the patron population knowledge, the vendor and partner relationships, and the professional network.
INSTITUTIONAL KNOWLEDGE
COLLECTION DEVELOPMENT RATIONALE:
Subject area: [Collection area]
Current collecting intensity: [Comprehensive / Research / Teaching / Basic]
Why this intensity: [Rationale — institutional mission, patron need, cost]
History: [When and why priorities shifted, if applicable]
VENDOR AND PARTNER RELATIONSHIPS:
Vendor: [Name]
Products/services: [What we license or purchase]
Relationship notes: [Key contacts, contract renewal dates, relationship history]
Performance notes: [Customer service, reliability, issues]
PATRON POPULATION KNOWLEDGE:
Patron type: [Faculty / Graduate students / Undergraduates / Community]
Research needs: [What they typically research]
Information literacy level: [Generally, what they know and what they need help with]
Common misconceptions: [What they often get wrong that we help correct]
PROFESSIONAL REFERRAL NETWORK:
Institution/Specialist: [Name and role]
Expertise: [What they're particularly strong in]
Contact information: [If appropriate to include]
When to refer: [Question types or resource needs that warrant referral here]
Relationship notes: [History of referral relationship]
KB Maintenance: Currency and Usability
The currency review schedule:
| Domain | Review cadence | Key question |
|---|
| Reference/research knowledge | Quarterly | Are key sources still current? Has new research guide material appeared? |
| Source intelligence | Annually or after major source changes | Has the source changed coverage or interface? |
| Cataloging practice | After standards updates | Do local policies need revision given new standards? |
| Institutional knowledge | Annually | Are collection development priorities current? Are referral contacts still accurate? |
The KB update trigger:
KB updates should happen on-trigger, not only on schedule. The trigger events:
- A patron interaction reveals a new source pattern or dead end
- A database search reveals a new coverage gap or useful search strategy
- A cataloging decision creates a new local policy
- A standards update requires policy review
- A referral reveals a new institutional resource or specialist
Waiting for the scheduled review to update KB entries means most trigger-based discoveries disappear before they're captured.
Key Takeaways
-
Reference knowledge organized by research type is more retrievable than knowledge organized by subject. Genealogical research has a distinct source landscape regardless of geography; organizing by research type makes the knowledge accessible at the moment of need.
-
Source intelligence must include dates. Database coverage changes, interfaces update, quality shifts. Source intelligence without a capture date becomes misleading guidance when the source has evolved.
-
The coverage gap field is the most practically important source documentation field. A database's stated coverage dates don't capture the gaps within those dates; those gaps need to be explicitly documented.
-
Cataloging decisions need a review date. Local policy decisions made against one version of a standard may need revision when the standard updates. A review date on each cataloging decision ensures they're revisited when standards evolve.
-
The professional referral network is KB content, not just professional memory. The subject specialist at a partner institution, the archive with specialized collections, the professional organization with subject expertise — these are referral resources worth capturing with notes on what they're good for.
Conclusion
A searchable knowledge base for librarians organizes four domains for retrieval when professional work requires them: reference and research support knowledge (by research type: most productive sources, coverage gaps, dead ends, referral knowledge — all date-stamped); collection and source intelligence (per source: coverage, search characteristics, quality signals, gaps, and interface notes — with archive.org backup for web sources); cataloging and metadata practice (local policy decisions with reasoning and examples, edge cases, review dates for standards currency); and institutional and professional knowledge (collection development rationale, vendor relationships, patron population patterns, professional referral network). The on-trigger update discipline — capturing source intelligence and reference interaction patterns at the moment of discovery rather than waiting for scheduled reviews — is what builds the KB from a once-created document into a living institutional intelligence system.
Related reading: Clip Articles for Later Reading.