Export a research evidence packet another reader can reopen
Export a research packet with a readme, source manifest, relevant notes, and reproducible locators. Test it from a new folder before handing it over. An export is successful when another reader can inspect the evidence and understand its limits without access to your browser history or personal file layout.
The Library of Congress format resources offer background on sustainable formats. W3C provenance offers background on relationships between source and derived objects. The packet below is a manual handoff design, not an advertised export feature of any product.
Define the packet’s purpose and cutoff
Write one sentence explaining what question the packet supports and the information cutoff. Include its preparation date separately. A current export can contain a historical information set, so the two dates should not be silently merged. State the inspection scope and which documents remain unread.
Include only the materials needed for the handoff. A packet containing every download can be harder to review than a small, indexed set. Keep originals distinct from annotated copies and extracted tables. If a source file is not included, give its public reference and explain how the reader can identify it.
Hypothetical packet manifest
Assume fictional Harbor Glass has a project-status review prepared for a colleague. This is an invented local-file example.
| Packet item | Purpose | Reopen check |
|---|---|---|
| README | Question, cutoff, scope, limitations | Understand without outside chat |
| sources.csv | IDs, titles, URLs, local paths | Every cited ID resolves |
| originals | Included source objects | Files open in available readers |
| notes | Review narrative and questions | Citations point to manifest |
| changes | Relevant correction history | Current and historical roles clear |
The manifest should identify whether a document is included or linked only. A missing local file is not necessarily an error if the packet says so and provides a workable public route. A broken relative path presented as included is an error.
Make paths portable
Use paths relative to the packet root for included files. Avoid references to a personal desktop, temporary folder, or local drive letter that the recipient cannot access. Preserve official URLs as provenance even when local copies are included. The two serve different purposes: retrieval within the packet and return to the publication record.
If notes use application-specific links, provide a plain-text or broadly readable alternative where practical. An exported note that only opens inside your account is not self-contained. Do not claim universal compatibility; record the formats supplied and the readers used for your actual check.
Run an isolation test
Copy the packet to a fresh location and open its readme first. Follow every material citation using only packet contents and public references. Check one source in detail against the note’s locator. Then inspect missing-file declarations and unresolved questions. This test checks portability, not the truth of every underlying assertion.
If a public link requires permissions or no longer opens, record that limitation and retain the document identity needed to search again. Do not describe the packet as complete when essential evidence cannot be inspected. A partial packet can still be useful if its missing inputs are explicit.
Limits and common mistakes
An evidence export does not transfer ownership rights or guarantee permission to redistribute every source. Include material appropriate to the authorized task and use source links where needed. It also does not make a research conclusion independently reviewed simply because the files are neatly packaged.
Common mistakes include exporting only screenshots, leaving absolute paths, dropping source IDs during conversion, and omitting the information cutoff. Another is including a corrected source while the note still cites an earlier version without explanation. Keep document roles and revision history aligned with the narrative.
A final record check
Run the packet test after extraction, not only before compression. Archive creation can preserve files while the recipient’s extracted folder structure changes paths. Open the readme at the new root and follow a citation through the manifest to the source. Record any reader or network dependency that prevents the packet from being used offline or in another environment.
FAQ
Is a zip file enough to call the export complete?
No. The archive must contain a usable index and working references. Verify the contents after extraction in a fresh location.
Must I include every original file?
No. State what is included, what is linked only, and what could not be obtained. The recipient should not have to infer those distinctions from missing paths.