When a language edition is a summary rather than the full report

A language selector can promise more than the material behind it. If three buttons have equal prominence and only a language name, a reader may reasonably expect three complete editions of the same work. That expectation fails when one file is a short summary, even if its translation is accurate.

This fictional publication review follows that problem from the supplied documents to a corrected library record. The question is whether the website describes the available material honestly, not whether the organisation should commission an additional translation.

Start with the work and the reader's question

Publication R-38 is a report called Access to Community Learning. A reader needs to understand how its findings were gathered. The library record offers “English,” “Shqip” and “Srpski — latinica,” with no explanation of scope.

The editor reports that the Albanian file is missing pages. Before changing a link or requesting a new upload, the team inspects the three files and the publication owner's approved inventory.

The Albanian file is complete for its intended purpose. It was never commissioned as a full translation. Its cover already describes it as a summary, but the website's equivalent-looking language buttons hide that distinction until the reader opens the file.

The publication owner confirms that all three resources concern R-38. The complete Serbian Latin edition is not a different report merely because its title is translated. The correction must preserve those relationships.

Diagnose the misleading promise

The failure occurs between the approved resource description and the public choice. The content model stores a language for each file but has no public field for resource scope. The template then presents every attached language as a complete alternative.

This matters for the named task. The reader seeking methods can open the Albanian summary, search it and conclude that the organisation has not explained its method. The full explanation exists in two other editions, yet the page gives no reason to look there.

Adding more language links would not solve the problem. Neither would renaming the Albanian file without changing the record that introduces it. The reader needs the distinction at the point of choice.

Agree the corrected record

The owner approves a record with a common publication identity and three explicitly described resources:

• Complete report — English. Includes methods, limitations and appendices.
• Summary — Albanian. Covers selected findings and recommendations; it does not include the complete methods or appendices.
• Complete report — Serbian Latin. Contains the full report sections.

Beside the Albanian summary, the page offers a labelled route to “Full methodology in the English report” and identifies the relevant section. It also retains the complete Serbian Latin edition. The organisation has not created a new Albanian methods translation, and the page does not imply otherwise.

The record distinguishes the language of its explanatory interface from the language of each document. An Albanian interface can still point to an English source, provided the destination language and purpose are made clear. W3C's language-declaration guidance explains how HTML can identify a page's default language and passages in another language. That markup supports the content; it does not determine whether an edition is complete.

Keep publication identity and citation routes stable

The team retains R-38 as the work identifier and keeps the existing file destinations assigned to their original resources. It adds a scope value and reviewed public description rather than creating a second, duplicate report record for the summary.

The complete Serbian Latin resource keeps its existing association and destination. The source files are not silently rewritten. A reader with an old direct link still reaches the intended file, while the library record now explains the relationship more clearly.

If the organisation later commissions a complete Albanian edition, it should be added as that distinct resource with its own review and publication decision. It should not overwrite the summary's identity simply because both share a language.

Check what readers can now decide

The review uses three tasks, without telling the participants which button to choose in advance.

First, a reader who wants a short Albanian overview selects the labelled summary and can explain its limited scope before opening it. Second, a reader looking for methods identifies that the summary does not contain them and follows the clearly marked English route to the methods section. Third, a Serbian Latin reader chooses the complete edition and finds the methods, limitations and appendices there.

The editor also checks the control case: an unrelated publication R-39 has only one complete English edition and no summary. It remains described that way. The new scope field does not manufacture alternative editions or make every publication appear to have a missing translation.

These checks establish the intended result for the sample. They do not substitute for reviewing the wording and files of every publication in a migration.

Give the next editor a decision rule

The editing instructions now ask for the work identity, language, resource scope and evidence of approval for each attachment. “Summary,” “complete report” and “appendix” are meaningful choices tied to the material, not decoration for a card.

Where scope is uncertain, the editor asks the publication owner before presenting the resource as an equivalent edition. The unresolved item can remain a preparation task. It should not be labelled complete simply to fill a language row.

Use the edition map to prepare the same questions for your collection. The publication-library service covers the record structure and reader routes needed to make those decisions usable on a website.