A Catalog Is Only as Universal as Its Audience

The Hidden Question Inside Every Catalog

What is the point of organizing the world if nobody can find themselves in the organization?

This question sits beneath every catalog, archive, database, library, and research system. We often treat documentation as a technical problem: collect information, describe it, classify it, and make it retrievable. But classification is never merely technical. The moment we decide what to record, which distinctions matter, and who should be able to use the result, we are designing a possible world for other people to enter.

A vast collection without an imagined user is not yet a knowledge system. It is only an accumulation with better furniture.

This is the tension between the dream of universal documentation and the practical necessity of audience. One ambition seeks to connect everything: books, facts, objects, events, concepts, and the relationships among them. The other asks a deceptively simple question: For whom is this arrangement meaningful? The first gives us scale. The second gives us direction.

The deeper lesson is that knowledge architecture succeeds not when it represents everything, but when it makes the right things visible to the right people at the right moment.

From Collection to World Model

Paul Otlet's vision of documentation was radical because it treated documents not as isolated objects, but as components in a larger intellectual system. A book was not simply a book on a shelf. It was a node in a network of subjects, references, institutions, questions, and discoveries. The purpose of documentation was to create pathways through the world's recorded knowledge.

That idea remains strikingly contemporary. Search engines, digital libraries, linked data systems, and research graphs all pursue some version of the same dream: transform scattered records into a navigable landscape.

But a landscape is not the same thing as a map. A landscape contains more than any one traveler can perceive. A map selects. It emphasizes one route, suppresses another, marks certain boundaries, and leaves countless details unrepresented. The map becomes useful precisely because it is not the world.

Documentation systems face the same constraint. They cannot simply preserve reality. They must decide how reality will be encountered.

Imagine a museum that stores ten million objects but provides only accession numbers. It may be an extraordinary repository, but it is a poor instrument for learning. A visitor interested in migration will not know which objects matter. A schoolchild will not know where to begin. A researcher studying material culture may need a completely different path from a journalist investigating a historical event.

The objects have not changed. The routes through the objects have changed.

This is why the small field labeled “Audience” can be more consequential than a hundred technical specifications. It asks the catalog to disclose the human situation in which an item becomes useful. Is this record for a researcher, a policy maker, a teacher, a student, a member of the public, or an internal administrator? Each answer changes what counts as clarity, relevance, and sufficient detail.

A catalog does not merely describe what exists. It proposes who should notice what exists, and why.

The Audience Is Not a Filter

It is tempting to treat audience as a filter applied at the end of a documentation process. First collect and classify everything, then create views for different users. This sounds neutral, but it hides a major assumption: that the underlying structure can be designed independently of human purposes.

Often it cannot.

Consider a database of city trees. An arborist may need species, disease status, trunk diameter, soil conditions, and maintenance history. A resident may want to know which trees provide shade, which produce fruit, or whether a recently planted tree is likely to survive. A city planner may care about heat reduction, ecological corridors, and distribution across neighborhoods. A child might simply want to find the tallest tree near home.

If the database is designed only around botanical taxonomy, it will serve the arborist better than the resident. If it is designed only around public enjoyment, it may fail the planner. The issue is not that one audience is correct and the others are mistaken. The issue is that different purposes generate different ontologies, meaning different answers to the question, “What kinds of things are important here?”

For the arborist, a tree is a biological organism. For the resident, it is a source of shade. For the planner, it is infrastructure. For the child, it is an object of discovery. All four descriptions can be true at once.

Audience therefore does more than determine presentation. It influences the categories themselves.

This has a powerful implication for organizations. Whenever a team says it is building a single source of truth, it should ask: truth for whom, under what conditions, and for what decision? A financial report, a research archive, and a public dashboard may refer to the same underlying events, yet they should not expose the same structure in the same way.

The fantasy of one universal view often produces systems that are technically comprehensive and practically unusable. They contain every field, every exception, and every legacy convention. No one can tell which parts matter.

A better approach is to distinguish between shared reality and situated access. The system may maintain a rich common record, while offering several meaningful paths through it. The goal is not to create separate truths. It is to create different entrances into a connected body of evidence.

The Three Layers of Useful Documentation

A useful documentation system can be understood as having three layers.

The first is the record layer. This contains the basic claims about an object, event, or idea: what it is, when it existed, where it came from, and how it relates to other records. Accuracy and provenance matter most here.

The second is the interpretation layer. This organizes records according to concepts, themes, categories, and relationships. It answers questions such as: What is this related to? What larger subject does it illuminate? What disagreements surround it? Interpretation turns isolated entries into a field of inquiry.

The third is the encounter layer. This determines how a particular person discovers and uses the material. It includes vocabulary, examples, search paths, levels of explanation, recommended sequences, and visible actions. The encounter layer answers: What can this person do next?

Many systems invest heavily in the first layer and neglect the third. They preserve metadata, enforce naming conventions, and build elaborate relationships, yet leave users facing a blank search box. The system knows a great deal, but it does not know how to begin a conversation.

The great promise of universal documentation depends on all three layers. Without records, there is nothing to trust. Without interpretation, there is no intellectual structure. Without an encounter design, there is no practical access.

Think of a public library. The books are the record layer. The classification scheme and subject relationships form the interpretation layer. The signs, displays, reading lists, reference desk, and arrangement of rooms form the encounter layer. A library that provides only shelves has preserved information but has not fully created access.

Digital systems frequently make this problem worse because their apparent flexibility encourages indiscriminate accumulation. It becomes easy to add another field, another tag, another category, another dashboard. But every new choice increases the cognitive load on the person trying to understand the system.

More metadata does not automatically produce more meaning. Sometimes it produces a thicker fog.

Classification Is an Ethical Act

Every classification system distributes attention. It tells users what is central, what is adjacent, what is exceptional, and what is invisible. That makes catalog design an ethical practice, even when its creators think of themselves as neutral technicians.

Suppose an archive categorizes people only by occupation. It may reveal patterns of labor while concealing family structures, political affiliations, geographic displacement, or disability. Suppose a catalog arranges literature only by national origin. It may reinforce borders that the works themselves challenge. Suppose a research database recognizes only published conclusions and not failed experiments. It will make discovery look cleaner and more inevitable than it really was.

The problem is not that every catalog must contain every possible perspective. That is impossible. The problem is failing to recognize that every structure has consequences.

An audience oriented approach does not solve this problem by pretending to satisfy everyone equally. Instead, it makes the intended use explicit and invites comparison among different views. A historical archive might offer a scholarly view, an educational view, and a community view, while preserving links among them. Each view reveals something the others may miss.

This is where a universal knowledge ambition can become more democratic. Universality should not mean imposing one classification on everyone. It should mean enabling many situated perspectives to connect without being collapsed into one.

The most inclusive system is not the one with a single view for all people. It is the one that lets different views meet without losing their differences.

This principle applies far beyond archives. It matters in company knowledge bases, government data portals, scientific repositories, and personal note systems. A team wiki designed for executives will not serve new employees well. A policy repository designed for lawyers will intimidate citizens. A research archive designed around established disciplines may hide questions that do not fit disciplinary boundaries.

The audience field is therefore a modest form of institutional self awareness. It asks the system builder to name the relationship between information and use. That naming can expose exclusions before they become invisible habits.

A Practical Method: Design the Doorways First

If documentation should begin with audience, how should one proceed in practice?

Start by describing not a demographic category, but a situation. “Researchers” is too broad to guide design. Instead ask: What is this person trying to accomplish? What do they already know? What decision will they make with the information? What would make them trust the result? What would cause them to abandon the search?

A useful audience profile contains at least four elements:

1. The question: What is the person trying to find out?
2. The constraint: What limits their time, vocabulary, authority, or attention?
3. The consequence: What will they do after finding the information?
4. The next doorway: What related path should the system make visible?

For example, “a teacher preparing a lesson on industrialization” is more useful than “educator.” The teacher needs concise context, reliable primary materials, age appropriate language, and a sequence that can become a classroom activity. A catalog built around that situation might surface images, quotations, timelines, and contrasting interpretations before exposing the full technical record.

Then test the system with a simple exercise: ask several people from different situations to complete the same task. Do not measure only whether they eventually find an item. Observe what they assume the categories mean, where they hesitate, and which labels feel obvious to insiders but strange to everyone else.

The most valuable failures often occur before a search returns zero results. A person may find hundreds of results and still fail because the system has not helped them judge relevance. Retrieval is only the beginning. Orientation is the real product.

A second useful practice is to create multiple starting points. Offer a subject pathway, a chronological pathway, a geographic pathway, and a question based pathway when appropriate. These are not redundant interfaces. They are different hypotheses about how understanding begins.

Finally, preserve the links among the pathways. If an item appears in a public story, a scholarly collection, and an administrative record, the user should be able to move among those contexts. This is the operational form of universality: not one flat inventory, but a connected system of perspectives.

Key Takeaways

1. Treat audience as part of the data model, not merely a display setting. Ask whose questions determine which categories and relationships matter.

2. Separate the record, interpretation, and encounter layers. Accuracy alone is not enough. People also need context and a clear next step.

3. Design for situations rather than demographic labels. “A teacher preparing a lesson” gives better guidance than “educator.”

4. Offer several doorways into the same body of knowledge. Different users need different routes, but those routes should remain connected.

5. Measure orientation, not just retrieval. A successful system helps people judge relevance, understand context, and continue exploring.

The Catalog as an Invitation

The dream of documenting the whole world can sound like a dream of total capture: gather every fact, assign every object a place, and make the complete inventory searchable. But the deeper achievement is not possession. It is relationship.

A collection becomes knowledge when someone can enter it with a question and leave with a better one. That transformation depends on structure, but structure alone is insufficient. It depends on recognizing that every user arrives from somewhere, carrying a purpose, a vocabulary, and a limited amount of attention.

The future of documentation will not be decided only by storage capacity, search speed, or the number of records preserved. It will be decided by whether systems can connect scale with human intention.

The most ambitious catalog is not the one that claims to speak to everyone in the same voice. It is the one that offers many intelligible entrances into a shared world, then helps each visitor discover how their path connects to others.

A catalog, at its best, is not a warehouse of answers. It is an invitation to notice what you could not previously see.