If you are searching for how to translate Dewey Decimal Classification numbers, how to translate Library of Congress Classification codes, how to translate UDC numbers, or how to localize a library catalogue without changing where a work belongs in a classification system, the first rule is to separate notation from language. Translate captions, notes and user-facing explanations; preserve the assigned classification notation unless an authorized cataloguing decision changes it.
This matters in libraries, school libraries, university catalogues, national bibliographies, archives, discovery systems, cataloguing projects, multilingual metadata, shelving guides, subject browsing, knowledge organization and library-system migrations. A translation can be elegant and still make a collection harder to find if it changes a decimal number, mistakes a Cutter element for prose, flattens a hierarchy, or treats Dewey, LCC and UDC as if they were interchangeable translations of one another.
This guide explains how to translate around Dewey Decimal Classification, Library of Congress Classification and Universal Decimal Classification safely. It focuses on notation, hierarchy, subject captions, editions, local call numbers, multilingual displays, mapping, structured metadata and quality assurance. It connects to the wider eduKateSG translation architecture while remaining a specialist page about library classification rather than another broad language hub.
1. Classification notation is not ordinary language
Library classifications organize knowledge through controlled notations linked to subject concepts. The number or letter-number string is not a sentence that becomes more understandable if translated character by character. Its meaning comes from the scheme, edition, schedules, tables and cataloguing rules.
Translation control: preserve the notation first and translate the accompanying caption. Quality assurance: verify that the target caption still belongs to the same classification record or authorized local assignment.
2. Dewey Decimal Classification organizes subjects numerically
The Dewey Decimal Classification, or DDC, organizes knowledge through decimal notation and hierarchical relationships. OCLC maintains Dewey and releases regular updates. In 2026 OCLC announced an updated print-on-demand edition and noted that Dewey remains widely used internationally in multiple languages.
Translation control: preserve the assigned Dewey number and use authorized terminology where available. Quality assurance: record the edition or data source used when a classification decision depends on current schedules.
3. LCC uses letters and numbers in a different architecture
The Library of Congress Classification, or LCC, divides knowledge into major classes identified by letters, with subclasses and numerical ranges providing additional detail. The Library of Congress maintains and develops the system and publishes updates through its cataloguing services.
Translation control: treat the complete class number as protected cataloguing data. Quality assurance: do not translate letters as if they were initials from the English subject caption.
4. UDC is a multilingual universal decimal classification
The Universal Decimal Classification is maintained by the UDC Consortium and is used internationally in libraries, documentation and information services. The Consortium states that UDC is used in more than 130 countries and has been published in more than 40 languages.
Translation control: preserve UDC notation while translating the verbal description. Quality assurance: distinguish the official or authorized UDC data used by the project from locally improvised captions.
5. Dewey, LCC and UDC are not interchangeable code systems
All three systems organize subject knowledge, but they use different structures, histories and notations. A number in Dewey is not “translated” into an LCC call number merely by finding a similar subject phrase. Moving between systems is classification mapping or recataloguing.
Translation control: keep the classification namespace explicit. Quality assurance: label any cross-system correspondence as a mapping rather than a translation.
6. Subject caption and class notation belong in separate fields
A catalogue record can store a classification number and a human-readable caption. The caption may be displayed in several languages while the underlying notation remains the same. This separation is the foundation of safe multilingual discovery.
Translation control: localize captions, notes and interface labels without editing the notation. Quality assurance: switch languages and confirm that the bibliographic record retains the same class number.
7. Hierarchy carries meaning
A classification schedule places broad concepts above narrower concepts. The same word can mean something different depending on its location in the hierarchy. A translation project that exports captions without parent relationships can lose this context.
Translation control: preserve parent-child links, indentation or hierarchical identifiers. Quality assurance: rebuild sample branches and confirm that every translated caption remains under the same parent concept.
8. Decimal notation should not be localized like a number
In classification notation, a decimal point can have structural meaning. It is not a decimal quantity that should use a comma simply because the target locale formats numbers differently. Changing punctuation can create another notation or an invalid one.
Translation control: keep classification punctuation canonical. Quality assurance: compare literal notation strings rather than numeric values.
9. Leading and trailing digits are classification data
Spreadsheet software may remove zeros or treat class numbers as ordinary decimals. That is dangerous because classification strings should be preserved exactly as cataloguing data.
Translation control: store classification numbers as text. Quality assurance: scan imports and exports for truncated zeros, scientific notation or automatic numeric conversion.
10. LCC letters are not abbreviations to translate
An LCC class letter represents a position in the classification, not a word that should be replaced with the first letter of the target-language subject. Translating the caption for a class does not change its letter.
Translation control: preserve the class and subclass letters. Quality assurance: compare target records with the Library of Congress schedule or authoritative catalogue data.
11. LCC numeric ranges add specificity
Within an LCC subclass, numbers identify subject ranges and topics. A translator should not convert those numbers into local shelving sequences or remove punctuation to make the call number look simpler.
Translation control: treat the number range as protected notation. Quality assurance: verify sorting and shelving behavior after localization.
12. Cutter numbers are part of call-number construction
Many LCC call numbers include Cutter numbers that help arrange names, titles, places or other elements. A Cutter may resemble an abbreviation but functions as notation. Translating an author’s name and then rebuilding the Cutter without cataloguing authority can move the item on the shelf.
Translation control: preserve assigned Cutters. Quality assurance: distinguish display-name transliteration from call-number construction.
13. Publication year can appear in a call number
Library call numbers can include a year or other local elements after the classification and Cutter. Translators should not reorder those elements according to target-language sentence conventions.
Translation control: preserve call-number sequence exactly. Quality assurance: compare source and target spine-label strings.
14. A call number is more than a subject classification
The call number used to shelve a physical item can combine classification notation with book numbers, Cutters, dates, volume numbers or local location data. Translating a subject caption does not authorize changing the complete shelving string.
Translation control: separate class number, call number and shelf-location fields. Quality assurance: test that the translated catalogue still directs users to the same physical item.
15. Dewey numbers can be extended through tables and notation-building rules
Dewey classification can use tables and notation-building instructions to express geographic, chronological, form or other aspects. A long number may therefore encode a deliberate cataloguing construction rather than an arbitrary sequence.
Translation control: preserve the assigned number as a whole. Quality assurance: do not shorten a number because the translated caption appears simpler.
16. Dewey captions should reflect the authorized concept
A class caption may be concise and may not list every topic included in the class. Translators should resist expanding it into a broader explanatory phrase that changes scope.
Translation control: translate the concept at the same granularity as the source caption. Quality assurance: check scope notes and hierarchy when a short caption is ambiguous.
17. Dewey editions and updates matter
Classification systems evolve as knowledge and language evolve. OCLC’s 2026 Dewey update includes revised and expanded treatment in several areas. A library translating an older catalogue may legitimately preserve older assignments while using current captions for new work under controlled policy.
Translation control: record the classification data version. Quality assurance: do not silently reclassify old records during a language-only project.
18. LCC schedules are maintained and updated
The Library of Congress regularly reviews proposals and publishes approved additions and changes. A class number in a historical record can therefore reflect the state of the schedules at the time of cataloguing.
Translation control: distinguish translation from recataloguing. Quality assurance: preserve historical call numbers unless the library explicitly authorizes reclassification.
19. UDC notation can express complex relationships
UDC is analytico-synthetic and can combine concepts using auxiliary signs and structured notation. A string can therefore express more than one facet or relationship. Translators should never simplify the notation because it looks complicated.
Translation control: protect the complete UDC expression. Quality assurance: validate complex notations using authorized UDC resources.
20. UDC punctuation is semantic syntax
Colons, slashes, parentheses and other symbols can have defined meanings in UDC. Replacing them with target-language punctuation conventions can change the expression.
Translation control: treat punctuation inside UDC notation as machine-like syntax. Quality assurance: compare each symbol and its position exactly.
21. Common auxiliaries should not be translated inside the notation
UDC can use common auxiliaries to express place, language, form, time or other facets. The verbal explanation can be translated, but the auxiliary notation itself should remain unchanged.
Translation control: translate only the human-readable expansion. Quality assurance: ensure each auxiliary still modifies the intended base concept.
22. Local classification extensions need clear provenance
Libraries sometimes use local expansions, prefixes, shelving codes or institutional conventions. Those can resemble official classification notation but may not be part of the standard scheme.
Translation control: label local data separately from standard classification. Quality assurance: keep documentation showing which part of a call number is official and which part is local.
23. Branch-library codes are not subject classifications
A location code such as MAIN, REF, CHILD or a local-language equivalent can identify where an item is held. It should not be confused with the Dewey, LCC or UDC subject code.
Translation control: localize location labels only according to the library system’s rules. Quality assurance: preserve the link between location ID and physical branch or collection.
24. Collection labels can be translated without changing classification
A library may label collections “Reference,” “Children,” “Local History” or “Rare Books.” These user-facing terms can be translated naturally while the subject classification remains unchanged.
Translation control: keep collection, location and subject fields separate. Quality assurance: search the translated catalogue by each dimension independently.
25. Subject headings and classification numbers solve different problems
A bibliographic record can contain controlled subject headings as well as a classification number. Subject headings provide verbal access points; classification organizes subjects in a systematic notation. Translating one should not overwrite the other.
Translation control: preserve field identity in MARC or other metadata. Quality assurance: confirm that translated subject headings remain separate from call-number fields.
26. Keywords are not controlled classification
Users may search a natural-language keyword that does not appear in the official caption. Discovery systems can map synonyms to the relevant class without changing the class notation itself.
Translation control: keep search synonyms in an access layer. Quality assurance: ensure synonyms are not displayed as if they were official classification captions.
27. Translation can improve discovery without rewriting the scheme
A multilingual catalogue can show localized captions, explanatory notes and cross-language synonyms while preserving one canonical classification assignment. This lets users search in their own language and still reach the same bibliographic records.
Translation control: separate discovery language from classification identity. Quality assurance: run equivalent searches in several languages and compare the underlying result set.
28. Crosswalks are not translations
Libraries may create mappings among Dewey, LCC, UDC or national classifications. A mapping can be one-to-one, one-to-many or approximate. It requires subject analysis rather than word substitution.
Translation control: label crosswalk relationships and confidence explicitly. Quality assurance: preserve the source classification even when a target mapping is added.
29. One Dewey class may map to several LCC areas
Different schemes partition knowledge differently. A broad Dewey class can correspond to several LCC subclasses or ranges depending on topic, form, geography or other details.
Translation control: avoid promising a universal one-number conversion. Quality assurance: use bibliographic context and authorized mapping tools when recataloguing is required.
30. The same subject phrase can classify differently by context
A phrase such as “data science,” “education,” “law” or “art” can appear in works with different disciplinary emphases. Classification follows the intellectual treatment of the work, not merely the words in the title.
Translation control: translate title and subject notes faithfully without inferring a new class from the translated wording. Quality assurance: preserve the cataloguer’s assignment unless subject analysis is in scope.
31. Bilingual books are not automatically reclassified by language
A book can be written in one or several languages while its subject remains the same. Language metadata and subject classification are separate dimensions.
Translation control: preserve language codes, subject class and translated display fields separately. Quality assurance: confirm that changing interface language does not change the item’s subject shelf.
32. Translated editions may have different bibliographic records
A translated edition can be a separate manifestation or edition with its own publication data and sometimes a distinct local call number. That bibliographic difference should not be confused with translating the classification label.
Translation control: link translated editions through bibliographic relationships. Quality assurance: do not overwrite the source edition’s record when creating target-language metadata.
33. A new edition does not automatically require a new subject class
Different editions of the same intellectual work can retain the same broad subject classification, though cataloguing decisions may vary. Translation teams should not reclassify merely because title wording or pagination changed.
Translation control: leave classification assignment to cataloguing policy. Quality assurance: compare editions through work-level or authority relationships.
34. Fiction shelving can use local schemes
Public and school libraries sometimes shelve fiction by author or genre rather than by Dewey. A multilingual catalogue may therefore contain local fiction codes alongside standard classification numbers.
Translation control: document the local scheme and translate genre labels separately. Quality assurance: test physical shelving directions after localization.
35. Children’s collections often add local notation
Labels such as J, YA, E or local equivalents can indicate audience or collection rather than subject. Replacing them with target-language initials may break local shelving and barcode workflows.
Translation control: preserve machine-facing collection codes while translating their display labels. Quality assurance: scan sample items and confirm the same collection routing.
36. Reference and special collections can have separate call-number policies
A reference copy and a circulating copy of the same work may share a class number but differ in location prefix or item status. Translation must keep those operational distinctions intact.
Translation control: localize user-facing status text only. Quality assurance: confirm circulation rules still attach to the correct item records.
37. MARC fields must retain their semantic roles
Library metadata formats such as MARC distinguish fields for classification, call numbers, subject access, notes and publication data. Translating field content without respecting tags and subfields can destroy the record structure.
Translation control: localize only approved textual subfields. Quality assurance: validate the record and compare tag-subfield structure before and after translation.
38. MARC indicators and subfield codes are not language
Indicators, delimiters and subfield codes may look like punctuation or single letters but have machine-defined meanings. They should never be translated.
Translation control: exclude structural markup from CAT tools. Quality assurance: parse the final MARC or MARCXML file with library software.
39. BIBFRAME and linked-data identifiers need protection
Modern library systems can represent bibliographic and authority data as linked data using URIs. Those identifiers should remain stable while multilingual labels are attached as language-tagged literals.
Translation control: localize labels, not URIs. Quality assurance: resolve linked-data identifiers and check language tags after transformation.
40. Authority records help control translated names and subjects
Authority control connects variant names, preferred forms and related headings. Multilingual discovery works best when translated forms are linked to the same authority entity rather than stored as unrelated strings.
Translation control: preserve authority IDs. Quality assurance: search variant forms and confirm they converge on one authorized entity.
41. Spreadsheets are dangerous for call numbers
Call numbers contain decimals, letters, spaces and punctuation that spreadsheet software may normalize. Sorting can also be lexicographic or numeric in ways that differ from shelf order.
Translation control: import every call-number field as text. Quality assurance: compare sorted samples with the library system’s native shelflisting order.
42. CSV exports need delimiter discipline
Bibliographic titles and notes can contain commas, quotation marks and multilingual punctuation. Poor CSV quoting can shift call numbers into another column while leaving every individual token valid.
Translation control: define encoding, delimiter and quoting rules. Quality assurance: round-trip representative records through the destination library system.
43. Unicode normalization can matter in catalogue data
Names, titles and subject captions can contain diacritics and non-Latin scripts. Unicode normalization should be handled systematically so that search and authority matching remain reliable.
Translation control: normalize textual fields according to system policy without changing protected notations. Quality assurance: test search using composed and decomposed character forms where relevant.
44. OCR can damage spine labels and historical catalogues
Digitized card catalogues and shelf-list scans may contain tiny call numbers. OCR can confuse letters and digits, drop decimal points or merge lines. Translating the resulting text without verification can create false shelf locations.
Translation control: verify OCR-derived classification data against the catalogue or schedule. Quality assurance: treat impossible class patterns as exceptions.
45. Machine translation should not receive raw call numbers as prose
An MT engine may leave a call number alone, but it can also alter spacing or punctuation. Protecting the notation explicitly is safer than assuming the engine will recognize it as data.
Translation control: replace call numbers with stable placeholders before MT. Quality assurance: restore from source-controlled values and compare exact strings.
46. Generative AI should not assign a class from a title alone
A title often underdetermines the intellectual subject of a work. “Networks,” “Justice,” “Learning” or “Climate” can belong to very different disciplinary treatments. A model can suggest possibilities, but final classification requires subject analysis.
Translation control: use AI for explanation and discovery assistance, not authoritative classification. Quality assurance: require cataloguer review for newly assigned numbers.
47. Generative AI should not invent crosswalk precision
Because classification schemes divide knowledge differently, a model may produce a confident one-to-one mapping where none exists. This can be especially misleading in migration projects.
Translation control: represent approximate mappings honestly. Quality assurance: use authorized tools, schedules and bibliographic context to confirm each conversion.
48. Right-to-left catalogue displays need notation isolation
Arabic and Hebrew interfaces can place Latin letters, decimal numbers and punctuation inside right-to-left text. Without directional controls, an LCC or Dewey call number can appear visually scrambled.
Translation control: isolate classification strings in their canonical direction. Quality assurance: test display, copy-paste, search and printed spine labels.
49. Accessibility needs spoken subject labels as well as call numbers
A screen reader can read a call number character by character, but users also need a meaningful subject description. Accessible catalogues can expose both while keeping the underlying notation exact.
Translation control: provide localized accessible labels. Quality assurance: test catalogue navigation by class, subject caption and item title.
50. Printed signage can translate subject areas without changing shelf numbers
A library may place bilingual signs such as “History,” “Science” or “Literature” above ranges of shelves. Those signs are navigational aids, not replacements for call numbers.
Translation control: map each sign to the documented range. Quality assurance: walk the physical shelf and verify that the bilingual sign covers the intended span.
51. Worked example: Dewey in a multilingual school library
A school library displays Dewey numbers on spine labels and adds English, Chinese and Malay subject signage. The same book remains at the same Dewey number regardless of interface language. Students can search localized subject words and still reach the identical shelf range.
Lesson: multilingual access does not require multilingual classification numbers. Check: compare catalogue result, spine label and shelf sign for one sample item.
52. Worked example: LCC in a university catalogue
A university localizes its discovery interface into several languages. An LCC call number such as a class-subclass-number-Cutter sequence remains unchanged. The subject caption and help text are translated, and the item still sorts correctly among neighboring records.
Lesson: display language and shelflisting notation are separate layers. Check: test browse order before and after localization.
53. Worked example: complex UDC notation
A documentation centre uses a UDC expression combining a main subject with place or form auxiliaries. The target interface translates the explanatory expansion but leaves every punctuation mark and auxiliary symbol in the notation unchanged.
Lesson: UDC punctuation can carry conceptual relationships. Check: validate the notation in an authorized UDC tool or schedule.
54. Worked example: mapping during a system migration
A library moves from a local Dewey-based arrangement to an LCC-based academic system. The project does not call this “translation.” It retains the old Dewey number for provenance, assigns or imports the LCC number through cataloguing rules and translates user-facing subject labels separately.
Lesson: classification conversion is a data and cataloguing project. Check: preserve old-to-new mapping provenance.
55. Search intent: “translate Dewey Decimal number”
A user may want to know what a Dewey number means in another language, not to change the number itself. The useful answer identifies the class, provides a localized explanation and notes that exact assignment can depend on edition and cataloguing rules.
Best practice: show the original Dewey notation unchanged and translate the caption or explanation separately.
56. Search intent: “translate Library of Congress call number”
A user may be asking what the class letters and numbers represent, where the book belongs, or how to explain the subject in another language. The call number should remain intact while the class meaning is explained.
Best practice: parse the class, subclass, numerical topic, Cutter and date as applicable, but do not rewrite the call number into target-language initials.
57. Search intent: “translate UDC number”
A UDC query often requires explaining the main class and any auxiliaries or combination signs. Because complex notation can encode relationships, a simple word-for-word translation is insufficient.
Best practice: preserve the notation, decode it with authorized UDC resources and translate the resulting conceptual explanation.
58. Official reference route: Dewey
OCLC maintains Dewey and provides WebDewey and updated print versions. OCLC’s March 26, 2026 announcement states that the DDC is regularly updated and widely used to organize library collections in multiple languages.
Reference: OCLC Dewey Services. Use current authorized data for cataloguing decisions rather than copied internet tables.
59. Official reference route: Library of Congress Classification
The Library of Congress maintains LCC through its Policy, Training, and Cooperative Programs Division, publishes classification schedules and approved changes, and provides Classification Web Plus for current web-based access.
Reference: Library of Congress — Classification and Shelflisting.
60. Official reference route: UDC
The UDC Consortium maintains and develops the Universal Decimal Classification and publishes information about UDC structure, revisions and authorized products. The Consortium describes UDC as an international system used in more than 130 countries.
Reference: UDC Consortium. Use authorized schedules for precise decoding and assignment.
61. Connection to the master translation architecture
This specialist article belongs beneath eduKateSG’s Master Art of Translation — Technical Translation System. The master owns the broader controls for terminology, data integrity and change management; this page owns library classification notation and multilingual subject discovery.
Readers who want to strengthen the language side of subject knowledge can use the Vocabulary Learning Hub, while this article remains focused on classification evidence, not a competing vocabulary or English-system owner.
62. Release checklist
Before release, verify the classification scheme, edition or data source, complete notation, hierarchy, call-number elements, local prefixes, subject caption, authority links and item relationships. Protect decimals, letters, Cutters, UDC punctuation and MARC structure; validate structured exports; test RTL display; confirm shelf order; and ensure every translated subject label still points to the same bibliographic and classification record.
Then perform ordinary linguistic QA for clarity, cultural readability, terminology and search usefulness. Cataloguing integrity and language quality are different controls and both must pass.
63. Final rule: translate the subject explanation, preserve the library’s organizing evidence
Classification systems help readers move from a question to a shelf, from a subject to related works and from one catalogue to a larger map of knowledge. Translation should widen access to that map without redrawing it accidentally. Preserve the assigned notation and its provenance, translate captions and explanations carefully, and treat recataloguing or cross-system conversion as a separate, authorized knowledge-organization task.