Choose whether a row describes a file or a document
One PDF may contain several distinct records; one record may arrive as multiple images. State the row unit before assigning references. For a file inventory, one row per file may be sufficient. For a document index, a row may need page boundaries or links to several source references. Avoid changing the row unit halfway through the collection.
Give each record a stable reference
Use an identifier that survives a display-name or folder change. Keep the original source reference alongside the current location. This lets a delivery note, question or revision log refer to the same record consistently. A location is where the record can be found today; the stable reference identifies which record you mean.
Start with a compact field set
Select fields that support retrieval and review. Add specialist metadata only when someone will use and maintain it. A long index with mostly guessed values is less helpful than a smaller one with clear unknowns. Define the source of each field in a short data dictionary.
- Stable record reference and original source reference
- Project, client or other agreed grouping reference
- Document type and known document date
- Current location and recognizable display name
- Revision or version, where established
- Review status, open question and decision owner
Separate facts that sound similar
Document date, received date and file-modified time describe different events. Revision status and approval status also differ. A filename containing final does not establish approval. Use separate fields when the distinction matters and name the evidence or authorized person needed to settle an unknown value.
Make locations understandable without exposing access
Use agreed client-owned folder paths or location references appropriate to the index's audience. Keep passwords, private upload links and access tokens out of a general index. The authorized recipient should check that locations resolve for the people who need them. An entry in an index does not itself grant permission to a file.
Test retrieval and assign upkeep
Ask a recipient to find a few representative records using the index alone: a current item, a revision and an unresolved record. Fix confusing labels before indexing the full collection. Agree who updates the index when files move and how changes are recorded. Save the field definitions and exceptions with the completed handoff.
A few useful answers
Is an index just a list of filenames?
It can be for a simple inventory. A more useful finding aid may add project, document type, known date and status, depending on the retrieval questions.
Should the index contain a private upload link?
Keep private intake links and credentials separate from an index that may circulate widely. Use the agreed access process for actual files.
Does an index replace searchable PDFs?
No. An index locates records by metadata; searchable PDFs help find text within pages. Choose either or both according to the task.