Discover how the related items pane’s visible fields are determined by the Search Results Pane view in Relativity Analytics. This specific display configuration defines column choices and order for similar documents, while other elements don’t govern this pane’s layout.

Multiple Choice

Which term controls which fields are visible in the related items pane when you right-click in the viewer to run a Relativity Analytics search for similar documents?

The key idea here is that the fields you see in the related items pane when you run a Relativity Analytics search are controlled by the specific display configuration used for the Analytics results—the Search Results Pane view. This view defines which columns appear, their order, and how the result data is presented in that pane, so selecting the appropriate view determines exactly what metadata you see for the similar documents. Other concepts don’t set that visible layout. Relational Field Friendly Name affects labeling for relational fields, not the pane’s column choices. Views is a broader Relativity concept for saved ways of looking at data but the particular display of analytics results in the related items pane uses its own Search Results Pane view. Workspace is the project container and doesn’t govern the pane’s visible fields.

Relativity Analytics in E-Discovery: The Key to Seeing the Right Fields

If you’ve spent any time mousing around in Relativity, you’ve probably noticed how the platform serves up stacks of data in neat little panes. One of the trickier bits to grasp is how the fields you can see in the related items pane—when you run a Relativity Analytics search for similar documents—get decided. It’s not random. It’s not about the workspace name or some generic label. It’s about a specific display configuration called the Search Results Pane view. Let me break down why that tiny phrase matters and how you can use it to get clearer, more useful results.

The related items pane: a quick refresher

Picture this: you’ve found a document that looks promising, and you want to quickly surface other documents that resemble it. You trigger a Relativity Analytics search, and suddenly a panel shows up with a set of similar items. At first glance, it might feel like a simple list, but there’s more under the hood. The columns, the order, and even the exact pieces of metadata—these are not universal across every search. They’re determined by a display configuration that governs how analytics results are presented in that pane.

The heart of the matter: the Search Results Pane view

So, what exactly is this thing called the Search Results Pane view? In plain terms, it’s a display configuration tailored for the analytics results that appear in the related items pane. It controls:

  • Which columns show up (for example, Title, Bates, Custodian, or a custom field you’ve created)

  • The order of those columns (which field appears leftmost, which moves to the right)

  • How the data is formatted (dates, numbers, text fields, and any computed values)

  • Any filtering or grouping that makes sense specifically for analytics results

If you switch to a different Search Results Pane view, you’re essentially changing the lens through which you’re looking at the same roster of related items. The metadata you see, and how you interact with it, shifts to match the new configuration. That’s why the right view can make a world of difference when you’re trying to understand similarities, clusters, or patterns across a set of documents.

Why not the other terms?

You’ll notice a few other terms float around Relativity, and it’s worth clarifying why they don’t govern the visible fields in the related items pane:

  • Relational Field Friendly Name: This is about labeling for relational fields. It helps users recognize fields more intuitively, especially when dealing with relationship data. But it doesn’t dictate which columns appear in the analytics pane or the exact layout you see there.

  • Views (the broader concept): In Relativity, “Views” are saved ways of looking at data. They’re powerful and versatile, but the analytics-related display in the related items pane uses its own specialized view—namely, the Search Results Pane view. It’s a focused configuration that exists specifically to present analytics results in that pane.

  • Workspace: The project container, the sandbox where you organize datasets and users. It shapes permissions and the big-picture organization, but it doesn’t control the nitty-gritty of which fields render in the analytics results.

That separation of concerns is important. It keeps the UI clean and predictable: the pane you’re examining has its own tailored configuration, while the broader data structure and labeling live in other parts of Relativity.

A practical take: how this shows up in daily use

Imagine you’re exploring a cluster of similar documents and you want to quickly gauge the metadata that seems most telling. If your current Search Results Pane view highlights, say, Source File Type, Date, and a custom tagging field, you’ll instantly get a read on the kinds of documents that cluster together, when they were created, and what themes or topics emerge through tagging. If you switch to a different view, you might start seeing different columns—perhaps a focus on custodian, case label, or a numeric similarity score. That shift isn’t cosmetic; it changes what you notice first, what jumps out as salient, and what you might decide to open for deeper inspection.

The power of a good view: examples to consider

To make this concrete, here are a few scenarios where the right Search Results Pane view makes a meaningful difference:

  • Topic-driven analysis: If your research question centers on a topic tag or a set of keywords, you’ll want a pane that foregrounds fields like Topic Tags, Keywords, and a similarity score. A pane that hides these can leave you wading through less relevant details.

  • Time-based clustering: For investigations where timing matters, a view that emphasizes Date and Year fields, plus perhaps a “Last Modified” stamp, helps you see how documents drift or cluster across a timeline.

  • Custodian-focused reviews: When you’re tracing who touched what, a view that surfaces Custodian, Email Thread ID, and Source File Path can illuminate relationships and data provenance quickly.

  • Vendor or production context: Sometimes you need to understand provenance—Where did this document come from? Which production set does it belong to? A pane that highlights Source Container, Production Set, and Bates Number can be a real help.

Design tips for effective analytics views

If you’re in the business of configuring Relativity Analytics for yourself or a team, a few practical guidelines can save you time and mental energy:

  • Start with a purpose: Before you pick a view, ask what question you’re trying to answer with the analytics results. That purpose should guide which fields you bring to the front.

  • Keep it lean: Too many columns can overwhelm. Start with the essential few that carry the most signal, then add more as you gain clarity.

  • Align with downstream workflows: Consider what you’ll do with the results next. If you’ll export metadata for a report, ensure the export columns align with your Report template.

  • Leverage consistency: If you frequently compare similar searches, use the same Search Results Pane view across those searches. Consistency speeds recognition and reduces cognitive load.

  • Document the rationale: A short note in your project or a shared wiki about why a particular view is chosen can be a huge time saver for teammates who pick up the work later.

A word on configuration discipline

Because the Search Results Pane view is a display-level setting, it’s easy to tweak on the fly—sometimes too easy. If you’re not careful, you might create a jumble of views that look different from project to project. The antidote? Establish a small set of standard views for Analytics results and reserve bespoke views for highly specific investigations. Treat them like color palettes in a design system: consistent, deliberate, and easy to reference.

Common pitfalls and how to avoid them

  • Pitfall: Assuming all analytics results will look the same across projects. Reality: the pane’s view is project-specific. If you switch projects, you’ll want to review the active Search Results Pane view to confirm it still meets your needs.

  • Pitfall: Overloading the pane with fields. If every column is visible, scanning for meaning becomes effortful. Solution: prune to core fields first, then layer in extras as needed.

  • Pitfall: Not syncing with downstream exports. If your view emphasizes fields that aren’t included in your export template, you’ll waste time reformatting later. Solution: align the pane view with your typical export schema.

  • Pitfall: Ignoring the metadata quality while chasing similarity scores. Remember that quality flags and field definitions matter as much as the scores. Ensure the fields you rely on are accurate and consistently populated.

A quick analogy to keep it memorable

Think of the Search Results Pane view like a photographer’s chosen lens for a particular shoot. Different lenses (or, in our case, different views) bring different aspects into sharp relief. A macro lens will highlight close-up details; a wide-angle lens gives you broader context. The analytics pane works the same way: pick the lens that makes the metadata you care about pop, and your sense-making becomes swift and intuitive.

Where to find it in the UI (a quick orientation)

If you’re exploring Relativity, you’ll typically access the Analytics results through the viewer by right-clicking and initiating an Analytics search for similar documents. Once the results appear, you’ll see an option to adjust the display settings for the pane. The Search Results Pane view sits there as a named configuration; clicking it opens a dropdown of available views. From there, you can select the one that aligns with your investigative focus. If you don’t see the exact view you want, that’s a cue to discuss with your Relativity admin about creating or adjusting a view that fits your team’s needs.

The human angle: why this matters

At its core, the whole feature is about clarity. When you can tailor the visible fields to the question at hand, you’re not just saving minutes—you’re reducing the likelihood of misinterpretation. The right view helps you notice patterns sooner, compare documents more efficiently, and communicate findings with confidence. It’s a small configuration, but its impact can feel surprisingly large, especially on complex investigations where every metadata nuance matters.

A parting thought: experiment thoughtfully

If you’re curious, try toggling a couple of different Search Results Pane views on a familiar set of documents. Notice how the emphasis shifts as you switch views. Maybe one view makes a cluster of related items obvious, while another highlights a chronological thread. The beauty here is that you’re not locked in. The analytics pane invites you to experiment with intent, to reveal the story the data is quietly telling.

In the end, the secret behind which fields appear in the related items pane isn’t a mystery at all. It’s the Search Results Pane view—the tiny but mighty gatekeeper that tunes the display to the kind of insight you’re aiming for. Give that configuration a little attention, and the path from raw similarity scores to meaningful, actionable patterns becomes noticeably smoother.