Finding data — Explorer and search

Before almost any analysis, the first question is "where does the data I need live?" Portal offers two patterns: browse and narrow down. Analysts switch between them constantly.

Pattern 1 — Browsing with the Collection Explorer

Click Collections in the left navigation and a tree grouped by organization opens. The tree goes top to bottom: folder → collection → resource.

Resources have visually distinct icons:

• Dataset — Tabular data. View it row by row or wire it into a chart.
• Dashboard — A canvas of widgets.
• Code — A Python or SQL snippet. Called from other stages.
• Pipeline — An execution flow that ties multiple steps together.

Expanding folders is the right move when the question is "what does this team have?" Click a resource and the metadata card opens on the right, showing row count, last updated, and owner at a glance.

Pattern 2 — Narrowing with global search

Type into the search bar at the top (or hit Cmd/Ctrl + K) and resource names, descriptions, and tags are all matched. Results are grouped by resource type.

Two tips that make search more useful:

• Remembering part of the name is enough. The tokenizer handles both Korean and English.
• Use type filters to cut the noise. Limiting to "dashboards only" or "datasets only" keeps results focused when the same keyword shows up across resource types.

When search isn't returning what you expect, check in this order:

1. Permissions — Zero results often means the resource exists but isn't visible to you.
2. Tags and descriptions — The keyword may be in the description rather than the name.
3. AI Assistant — When the two above are blocked, ask in natural language (covered in the last lesson of this Path).

What to take away from this lesson

• Visually distinguish the four resource types in the collection tree
• Apply type filters in Cmd/Ctrl + K search
• When results are empty, check permissions first, then tags

Next lesson

Now you'll create a collection of your own.