A digital archive can look authoritative because it has a search box, a logo, and thousands of items. That is not enough. Before assigning it to students, ask a plainer question: what kind of historical work will this archive actually let students do?
Start with provenance. Who built the archive? Is it a library, museum, university, government agency, community project, commercial database, or individual collector? None of those answers automatically makes a source good or bad. They tell you what to check next. A national archive may have stable links and careful metadata but narrow institutional categories. A community archive may preserve voices missing elsewhere but need more teacher scaffolding around context and description.
The National Archives' Teaching With Documents page frames document analysis as a way for students to act like historians: they examine context and extract information to make judgments. That is the right standard. A digital archive should give students more than things to look at. It should help them ask where the item came from, who made it, why it survived, and what the item cannot tell them.
Next, check the item record. Open three or four individual items, not the landing page alone. A usable record should identify the creator if known, date or date range, collection, repository, format, rights statement, and some description of context. If the record only says "photograph" and gives a keyword, students will need more support. If the record links to a finding aid or collection description, that is better.
The Digital Library Federation's white paper on teaching with digital primary sources is helpful because it refuses to treat digital items as transparent copies. Digitized sources are shaped by selection, scanning, metadata, search systems, copyright, and institutional priorities. A student who finds one newspaper page through search may not understand the issue it came from, the paper's audience, or why that page was digitized while others were not.
Search the archive as if you were a student. Try obvious terms, names, misspellings, and broad topics. Does the search return too much? Too little? Are results sorted by relevance, date, collection, or something unclear? Can students filter by date and format? Can they browse, or are they trapped in keyword search? Browsing matters because historical inquiry often begins before students know the right words.
Save a few example searches before the lesson. This is not over-planning. It is classroom insurance. If the archive search behaves strangely, you can show students a route into the collection without pretending the tool is easier than it is. I like to keep one broad search, one precise search, and one failed search. The failed search is useful because it shows students that absence in a search result is not the same as absence in the historical record.
Then look at the archive's absences. Whose records are easy to find? Whose are missing, misnamed, or described through someone else's language? This is not a reason to avoid the archive. It is a reason to teach the archive as a constructed collection. Students can learn a lot by asking why certain people appear mainly in court records, missionary records, census records, school files, or newspapers written by others.
Rights and reuse matter too. If students will publish a digital project, can they reuse images? Is there a Creative Commons license, a public domain mark, a rights statement, or only vague language? If reuse is unclear, students can still analyze the item in a closed class assignment, but public posting becomes more complicated. Do not discover that at the end of the unit.
Check the reading level and emotional load. Some digital archives include traumatic material: photographs of violence, racist language, medical records, testimony about abuse, or records created by coercive institutions. The DLF white paper notes that digitization can decontextualize records and create new ethical problems around privacy, access, and histories of violence. Teachers should preview these materials and decide what warning, framing, or alternative option students need.
A simple evaluation routine works well. Before assigning an archive, make a one-page teacher note with five parts: what the archive contains, what it leaves out, how search works, what students must cite, and what question the archive can support. If you cannot fill out those five parts, the archive is not ready for independent student use.
Students need a citation routine too. Digital archives make copying links easy, but a link alone is fragile. Ask students to record the item title, creator if known, date, collection, repository, stable URL or identifier, and the date they accessed it. If the archive has a "cite this item" tool, teach students to check it rather than trust it blindly. Auto-generated citations often miss the detail a teacher wants students to notice.
For younger students, narrow the archive before class. Do not send a ninth-grade group into a million-item database and call it inquiry. Build a small source set of six to ten items, then let students choose which two or three to analyze. Older students can handle more open search, but even they benefit from a model search and a warning about misleading metadata.
The point is not to make the archive harmless. It is to make the terms of use visible enough that students can do real inquiry inside it without wandering blind.
Design the task around the archive's strengths. Do not ask students to "research the Great Depression" in a photo database. Ask them to compare how two agencies represented labor, housing, or rural poverty in a selected set of images. Do not send students to a newspaper archive with a vague topic. Give them a date range, a city, and a question about language or framing.
A strong digital archive assignment teaches the topic and the container. Students should leave knowing more about the past, but also knowing that search results are not the past itself. They are a path into evidence, built by people, with limits students can learn to see clearly.