Organising a Digital Resource Library

Worked example: organise a digital teaching resource library

A useful resource library answers a teaching question quickly: “Which learner task fits this lesson, and where is the answer guide for this exact version?” A tidy folder alone cannot answer that. The catalogue must distinguish the subject, audience, resource kind, version, answer partner and conditions of use.

The example below is a small, original fictional library. Its twelve current resources are supplied as real plain-text demonstration files, with a completed CSV catalogue, a blank CSV and a retained superseded file. They illustrate organisation; they are not a complete subject, term or year collection. All examples are grade-neutral and contain no actual learner information.

Prepared example companions: the completed CSV catalogue, blank CSV template and field guide are prepared for this example. Website hosting and access are pending verification.

Build one record for each resource

The stable identifier belongs to the resource, not its current filename. TR001 identifies the length questions; TR002 identifies their answer guide. Keeping different IDs makes the relationship explicit. A reference note without questions does not need an invented answer partner. The current catalogue has twelve IDs; the archive adds an earlier version of TR001 without inventing a thirteenth resource.

Use a short controlled list for resource kind: questions, answers, reference, template or checklist. Record audience separately from subject: a mathematics answer guide is teacher-facing, while a mathematics question sheet is learner-facing. “Teacher” is a descriptive audience field here, not a technical access restriction.

Every completed CSV row also records the source, initial source date, curriculum reference, actual file format, rights status, access status, relative location and current status. Here the common source is “Original fictional demonstration”, the initial source date is 2026-10-01, the format is UTF-8 TXT, and the curriculum field says no grade or syllabus mapping is assigned. Rights records make no third-party licence claim. Access is “supplied local artifact”; no live website availability is implied. These repeated values are present in every row so that exported selections remain understandable.

A completed naming and folder convention

Use resource ID, topic and version: TR001_length-endpoints_v1.1.txt. Put current learner materials in mock-library/learner, current teacher materials in mock-library/teacher and superseded copies in mock-library/archive. Keep catalogue-completed.csv and version-history.csv beside that tree. These are locations inside the supplied example package, not website links.

Do not put every useful fact in the filename. The catalogue can carry long titles, rights notes and curriculum references without making names unwieldy. Conversely, a filename should still identify the resource when a copy leaves its folder. This example does not impose a universal character limit. A different operating environment may have restrictions that need checking separately.

File extensions must describe the underlying format. Renaming a text file with a PDF extension does not make a PDF. Likewise, editing the catalogue’s format cell does not convert the file. Create the intended format properly, open it and record its new path only after checking the result.

Worked retrieval 1: questions plus the right answers

Request: find the current mathematics learner questions about length endpoints, together with teacher answers. Filter subject to Mathematics, audience to learner and kind to questions. TR001 and TR003 initially survive. The topic selects TR001 v1.1. Follow its paired-answer ID to TR002, then confirm TR002 points back to TR001 and carries partner version 1.1.

Open both files. The first question gives endpoints 2 cm and 9 cm; its key subtracts 9 − 2 = 7 cm. The second gives 3 cm and 8 cm; its key gives 5 cm. The metadata located the pair; inspection established that the actual tasks and solutions correspond.

Worked retrieval 2: a teacher checklist without a key

Request: find a cross-subject teacher checklist for printing. Cross-subject and teacher selects TR010, TR011 and TR012. Kind checklist selects TR011. Its paired-answer field is blank because a print checklist is not a question paper. Do not treat every blank partner field as an error, and do not attach the nearby mathematics key merely to make the column complete.

Worked retrieval 3: preserve an earlier version

Request: find the original wording of the length task before the schematic-scale clarification. The current catalogue still identifies TR001 v1.1, while version-history.csv points to archive/TR001_length-endpoints_v1.0.txt. Read the retained file and the change entry together. Version 1.1 clarifies that the scale is schematic; the endpoints and answers are unchanged.

The old version remains 1.0 with its original 2026-10-01 date. The revision is dated 2026-10-04. The current pair uses TR002 v1.1, whose record states the version it supports. Neither date becomes a curriculum date. The history explains supersession without rewriting evidence of what was previously supplied.

Three solved catalogue tasks

Task 1: repair an answer link

A copied row for TR003 says paired-answer ID TR002. Repair it and explain the check.

Answer: use TR004 v1.0. TR003 asks about 7 and 12 counters; TR004 gives 12 − 7 = 5 and 7 + 12 = 19. TR002 solves length endpoints. Correct both directions if either link is wrong, then record the correction. Sharing a mathematics subject label does not make keys interchangeable.

Task 2: repair a misleading date

Someone copies TR007 onto a device on 6 October and records “curriculum 2026-10-06”. What should replace that entry?

Answer: restore “Not assigned; no grade or syllabus mapping claimed” in the curriculum field. Keep TR007’s version date 2026-10-03. If the receipt date matters, record it in a separate receipt log. A local copy event proves neither content revision nor curriculum alignment.

Task 3: retrieve a different subject

Find the question that asks learners to order letter-writing actions and explain the appropriate answer.

Answer: TR005 v1.0, with TR006 v1.0. Write the letter first, put it in the envelope, then seal the envelope. The first action creates the item that must be enclosed. This checks both retrieval and the reasoned answer, rather than merely trusting matching titles.

Use the blank catalogue carefully

Copy the header-only CSV for a new library. Add one inspected resource at a time and allocate a stable ID before distributing it. Mark unresolved fields explicitly rather than guessing. Test at least one subject query, one audience query and one version-history query. Keep access and permitted use separate: being able to open a file does not establish permission to share it.

Frequently asked questions

Does a new filename need a new resource ID?

No. A harmless rename can retain the ID. Record the new location and keep the version unchanged if the content has not changed.

Can questions and answers share one ID?

A combined resource can, but this catalogue uses distinct IDs for separate files and explicit partner links. Apply one model consistently.

Is the newest file always the right one?

No. The required task, version, audience and use conditions matter. An older version may be needed to interpret an earlier classroom activity.

Does a folder named teacher protect its contents?

No. Here it organises files. Actual access controls are separate and must not be inferred from a folder label.

Why keep both source and version dates?

They describe different events. Retaining the initial source date prevents a revision from erasing the resource’s earlier provenance.

Must every reference note have answers?

No. A blank partner is appropriate when answers are not applicable. For a question resource, an unresolved expected key should be recorded as missing.

Does this catalogue establish curriculum approval?

No. It records what is known. Grade and syllabus applicability require separate evidence and review of the actual content.

Reference: the U.S. National Archives guidance on organising digital files supports consistent directories and metadata. The teaching catalogue, field choices, examples and retrieval rules here are original.