‘I remember reading that’: connect research sources to the draft

A historical novelist is writing a harbor trial. She remembers an old shipping archive saying that a certain manifest was restricted to winter. She also remembers an interviewee saying the opposite. The PDF is in Downloads, the interview summary is in another note system, and the manuscript contains nothing beyond “verify later.” Months on, “I remember reading that” cannot support the scene.

The difficulty of research-led writing is not merely preserving material. It is preserving the path of judgment. Where is the original? Which copy did the current Project use? How did the writer interpret it? What did the prose finally say? When those four nodes separate, fast search finds isolated content rather than an explainable decision.

Separate the external original from the Project copy

An original may be a web page, archive scan, interview recording, PDF, image, or a research assistant’s spreadsheet. It has its own location, permission conditions, and update path. A long-form Project usually needs the particular material used during this stage of writing and a note explaining why it mattered.

Scroll can import a reference file into the local Project. Scroll manages that imported copy. It does not move or edit the external original, and later changes to the original do not automatically sync to the Project copy. This is a boundary, not live synchronization: the writer can identify the material actually consulted for this draft.

For a changing source, record its original location, access date, and version on the reference card. Refresh it through deliberate review rather than assuming the copy still matches.

Give a future writer more than a filename

scan_0047.pdf does not explain why it matters. A reference card can record a meaningful title, type, source, tags, and Notes: a winter manifest from the harbor authority; the seal on page two matters to chapter fourteen; the date may use an old calendar; compare it with the oral history.

The valuable context is what the file cannot recover by itself: why it was saved, what remains uncertain, who or what it may affect, and where the writer expects to use it. Notes need not become a full summary.

The author can connect material to people, places, events, and prose. Related Files or structured relations preserve navigable Project connections; an ordinary manuscript link can lead from a passage to a relevant Project file; Notes retain editorial interpretation and reminders. These forms can point to the same file without carrying the same meaning. A link means “related,” not “formally cited.”

Project search finds locations, not meaning

Once material is inside the Project, search can recover a term from prose, card titles, and supported content. Searching “winter manifest” may return the PDF summary on a card, a place Note, a chapter-fourteen placeholder, and a character’s incorrect statement. The value is not the number of results but their return to the context of this Work.

Search also helps with renamed material. If “Northern Route” became “Grey Bay Route,” it can recover the former name from indexed passages and cards. At the end of revision, it can locate “verify later,” temporary names, and citation placeholders.

Search does not determine whether a source is credible or whether the same word denotes the same concept. The writer opens the context. A contradiction can become a task—“verify the manifest season” or “assess the interviewee’s memory”—rather than an obligation to solve the entire research system inside the current paragraph.

That distinction protects drafting momentum. If the question changes the scene’s cause, stop and check it. If it supplies a noncritical number, leave a placeholder and task, then return attention to the prose.

Return from conflicting sources to one scene

The archive says that the manifest was restricted to winter; the oral history says it appeared in summer. The writer preserves both. She records source and uncertainty on each card, the trial date on an event, and the relevant port institution on a place card, then connects both sources to chapter fourteen.

Further review may show that the interview describes a wartime exception. That conclusion belongs in a research Note with its remaining uncertainty. The prose may use a legal loophole or an unreliable memory, but a future editor can follow the path back to the evidence.

The day before delivery, a fact checker asks what supports the passage. Instead of re-researching the entire period, the writer restores the access date, conflict, and chapter use, then adds evidence, narrows the statement, or removes what she cannot support. One bounded review replaces a panicked search through the whole book.

If the interpretation remains uncertain, Mindmap, Whiteboard, or Flowchart can hold possible connections. Canvas connections remain exploratory; they do not automatically create formal relations in Story data.

Let research status describe the next responsibility

A research card may be background reading, awaiting verification, cross-checked, used in prose, or requiring formal citation. These are not credibility scores produced by Scroll. They are the writer’s description of the current work stage.

When a source changes, preserve the copy actually used by the Project and record the new version and difference before deciding whether the manuscript changes. For interviews, private correspondence, and unpublished archives, searchability does not grant permission. The author remains responsible for access control, quotation permission, anonymization, and factual review.

Association, citation, and publication are separate jobs

Historical fiction may need an internal evidence chain; biography and nonfiction often need formal citations and a bibliography. Importing a PDF does not create a citation. Linking it from prose does not supply author, title, publication details, and format. Use the appropriate citation workflow and review every field required by the Work.

When the manuscript stabilizes, the author can open the same Project in Scribe, verify the Work, version, and chapters, and confirm any expected structured reference information before Appearance, pagination, and publication output. Scroll supports research context, prose, judgment, and source preparation. It does not directly create PDF, EPUB, or print layout, and upstream records do not prove that Scribe has recognized them.

Use five signs a manuscript is ready for Scribe for the wider handoff. If you are choosing a research system, compare the distinct responsibilities in research and writing tools for historical and nonfiction work. Visual Mode and Source view for Markdown writing covers direct source inspection.

Research organization is not about preserving more. It enables a future writer to review today’s judgment. Return to the Scroll long-form writing workflow for revision and version paths, or see how References, links, search, and prose work around one local Project on the Scroll product page.