How to Map an Unfamiliar Research Field in One Week

Mapping an unfamiliar field in one week is a scoping task, not an exhaustive review. The goal is a defensible map: a documented search, a shortlist of anchor studies, a clear picture of the main evidence streams, and a written statement of what the map can and cannot support. You finish the week with an artifact your team can read in ten minutes and a log that lets someone else retrace your steps.

The sequence below assumes you are a clinician or researcher preparing a focused evidence brief, a research update, or a team discussion. It uses a single worked example throughout and ends with checkpoints, a reusable checklist, and stop rules.

Most wasted weeks begin with searching before deciding what the map is for. Spend the first hour answering four questions in writing:

1. What decision does this map inform? A journal-club update, a grant background section, and a protocol discussion need different depth.
2. What is the focused population and outcome? Name them explicitly. "Adults with a given condition" and "a named outcome at a stated time point" is enough to start.
3. What counts as in-scope evidence? Decide study designs, date range, and language limits now, because Cochrane guidance ties search planning to eligibility criteria rather than to convenience.
4. What will you not cover? Write the exclusions down. A one-week map is defined as much by its boundaries as by its contents.

If you cannot answer question one, you are not ready to search. If you can answer one and two but not three, draft provisional criteria and revise them after a scoping pass.

Plan the week around five checkpoints. Each produces a named artifact, so progress is visible and reviewable.

Treat these as gates. Do not move to screening until the scope note exists, and do not write the map until the evidence table has at least a first pass.

Cochrane's guidance on searching for and selecting studies starts from eligibility criteria and recommends planning searches around them. Apply that principle at small scale. Write your criteria as a short list of inclusion rules and exclusion rules, each with a reason.

For the worked example, take a focused question: in adults with a named chronic condition, what does the recent literature report about a specific functional outcome after a structured rehabilitation program? The population and outcome are fixed; the intervention and comparator can stay broad during a scoping week.

Decide at this stage how you will handle multiple reports of the same study. Cochrane guidance notes the need to link multiple reports of one study, and doing this early prevents inflated counts later.

Checkpoint: your scope note fits on one page and a colleague could apply it without asking you questions.

Cochrane recommends using multiple sources and combining free-text terms with subject headings. PubMed's user guide describes field tags, phrase searching, filters, Advanced Search, saved searches, and a Search Details view that shows how terms were translated and combined. Use that translation view to check that your terms behaved as intended before you trust a result count.

A practical search log records, for each source: the date run, the exact terms, any filters, the number of records returned, and the reason for the source. Run at least two sources so that a gap in one is visible against the other.

For the worked example, run a subject-heading search and a free-text search separately, then compare. If the free-text version returns a very different set, inspect the translation before combining them.

When you want a scholarly search interface to run and refine these queries, WisPaper search is the place to start; for a public explanation of finding academic papers, see WisPaper Scholar Search.

Checkpoint: every source in your log has a date, terms, filters, and a count. If a count looks implausible, you have a search problem, not a screening problem.

Cochrane guidance recommends deduplicating records and screening in stages. In a one-week map, two stages are enough: title and abstract, then full text for a shortlist.

Record an exclusion reason for every record you drop at full text. Reasons should map to your Day 1 criteria, not to impressions. Keep the screening log in the same file as the search log so the two can be read together.

Save the records you retain. In WisPaper, My Library is where you save or upload papers and organize them, which keeps the shortlist separate from the raw search output.

Checkpoint: the number of records at each stage reconciles. Records found minus duplicates minus exclusions should equal your shortlist.

Do not read the shortlist evenly. Identify a small number of anchor studies that define the main positions in the field, then read outward from them.

For each anchor study, extract into an evidence table: study design, population, the outcome you specified, the direction of the finding, and the stated limitations. Then classify each entry on three separate axes:

• Evidence level: what design produced the finding.
• Applicability: how closely the studied population and setting match your question.
• Indirectness: where the study measures something adjacent to, rather than identical to, your outcome.

Keep these axes apart. A well-conducted study in a different population can be high on evidence level and low on applicability; collapsing the two hides exactly the judgment your readers need.

Group the table into evidence streams, meaning clusters of studies that address the same question with the same kind of design. Name each stream in one sentence and note its main limitation.

If you need to ask questions across the papers you have collected, Library QA supports asking questions based on papers uploaded to My Library or added from search results, which suits the stage where you are comparing entries rather than finding new ones.

Checkpoint: every stream has at least one anchor study, and every anchor study has a recorded limitation.

The written map should be short enough to read in one sitting. Use this structure:

1. Question and scope, including population, outcome, and exclusions.
2. Search summary, with sources, dates, and record counts.
3. Evidence streams, one short paragraph each.
4. Evidence table, as an appendix.
5. Limitations of the map, covering search coverage, screening judgments, and indirectness.
6. What this map supports and does not support, stated in plain terms.

Before circulating, rerun the searches to catch records added during the week. Cochrane guidance recommends rerunning searches before publication, and the same discipline applies to an internal brief.

Checkpoint: a reader who disagrees with your conclusions can find the search terms, the screening reasons, and the study-level limitations without contacting you.

Return to the rehabilitation example. On Day 1 the team fixes the population, the functional outcome, and a date range, and writes down that pharmacological studies are out of scope. On Day 2 they run a subject-heading search and a free-text search in two sources, log the counts, and inspect the translation of the free-text query. On Day 3 they deduplicate, screen titles and abstracts, then screen full texts, recording a reason for each exclusion.

On Day 4 they find that the shortlist clusters into two streams: studies reporting the functional outcome directly, and studies reporting a related measure that stands in for it. The second stream is marked as indirect. One anchor study is well designed but drawn from a population that differs from the team's, so it is recorded as high evidence level and limited applicability.

On Day 5 the map states that the direct evidence stream is small, that the indirect stream carries most of the volume, and that the map supports a team discussion about the outcome but not a claim about effect size. That last sentence is the most valuable line in the document.

Use this before you call the map finished.

• Scope note names the population, outcome, eligibility criteria, and exclusions
• Search log records source, date, terms, filters, and count for every search
• At least two sources were searched
• Free-text and subject-heading searches were compared
• Search translation was inspected where the interface exposes it
• Duplicates removed and the count recorded
• Screening done in stages with a reason for each full-text exclusion
• Multiple reports of the same study linked
• Evidence table records design, population, outcome, and limitations
• Evidence level, applicability, and indirectness recorded separately
• Evidence streams named, each with an anchor study
• Searches rerun before circulation
• Limitations section written
• Readiness statement written

A one-week map needs explicit stopping rules, or it expands until the deadline decides for you.

Stop and write when every evidence stream has an anchor study, the search log reconciles, and further searching returns records you have already seen. At that point additional searching adds cost without changing the map.

Escalate to a second reviewer when a full-text exclusion is contested, when two streams could plausibly be merged, or when the anchor studies disagree on the direction of the finding. A second reader resolves these faster than more searching does.

Escalate to a librarian or information specialist when the search translation looks wrong, when a source returns implausible counts, or when your eligibility criteria cannot be expressed as a searchable query.

Narrow the question when the shortlist is dominated by indirect evidence. Reducing the outcome to what the literature actually measures produces a more honest map than stretching the original question.

Stop and report a gap when a stream has no anchor study. An empty stream is a finding, and it belongs in the limitations section rather than in a longer search.

The map is ready when four conditions hold. First, the scope note and the final map describe the same question. Second, the search log reconciles with the screening log. Third, every claim in the evidence streams traces to an entry in the evidence table. Fourth, the limitations section names the specific weaknesses of this map rather than generic caveats.

A useful test is to hand the map to a colleague who was not involved and ask them to state what the map supports. If their answer matches your readiness statement, the map is ready to circulate.

A research assistant is most useful at the steps where volume, not judgment, is the constraint. Use one to run and refine searches, to keep the shortlist organized, and to compare entries you have already selected. Keep the scope decisions, the screening reasons, and the readiness statement in your own hands, because those are the parts your readers will scrutinize.

For longer literature tasks that go beyond a one-week map, Scholar Agent covers literature review, inspiration, and reproduction use cases. If your map is the front end of a larger project, Research Projects gives that work a place to live. And if you are checking a reference list before circulating the brief, TrueCite screens BibTeX against real academic databases to flag hallucinated references.