eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

How People Translate Quickly | LIDO 1.1 Museum Records: Translate Object Labels Without Losing Provenance or Identity

—

by

eduKate Asia

To translate a museum collection record in LIDO 1.1 quickly, work with language-tagged human-readable display text while protecting the identifiers, controlled concepts, event relationships and rights statements that anchor the object. LIDO is an XML schema used to share cultural-heritage metadata with portals and aggregators. It supports multilingual description, but a new language version must still describe the same object, the same documented evidence and the same level of certainty. Translating a caption is not permission to rewrite a provenance chain.

The practical approach begins with an inventory of the actual LIDO record, not with a spreadsheet of isolated English nouns. Select the public-facing fields to translate, retain their place in the document hierarchy, use appropriate xml:lang attributes where the schema permits language variants, and compare immutable object IDs, concept references, dates, events, person identities and licensed-use information before distribution. A museum conservator, collection specialist and bilingual editor should agree on what the institution knows, what it suspects and what the record must not imply.

A safe deliverable may be a multilingual LIDO record, a locale-specific portal rendering or a reviewed translation companion to the canonical metadata. Each has different technical consequences. The fastest reliable path is to use LIDO’s defined display/index distinction, preserve source wording for disputed evidence, and test both XML validity and public interpretation. The article addresses museum-object presentation; it does not replace the separate archival-finding-aid task of retaining EAD3 series hierarchy or a library catalogue’s MARC record semantics.

Begin with the reader’s museum task

Imagine a visitor searching for an early twentieth-century Singapore classroom object in a museum collection portal. They want to know what the object is, what it was made from, where it was used and why the museum associates it with a particular history. A bilingual website can make those facts accessible without requiring the visitor to decode database codes. Yet the visitor also needs to recognize whether a date is documented, estimated or disputed. A translation that silently turns “possibly used in a school” into “used in the school” changes the evidence, not merely the language.

Museum metadata is layered. A public display label might summarize an item in clear words; an index term might connect it to a controlled vocabulary; a collection identifier may point to an inventory record; and an event record may describe production, acquisition or use. The translation job is to make the public display layer comprehensible while retaining the links that let researchers verify it. That is why a literal swap of English terms is rarely sufficient. The translator needs the object context and the authority information behind the words.

Write down the audience before drafting. A general visitor needs straightforward descriptions and transparent uncertainty. A researcher may need transliteration, historical names and references. A school group needs careful explanation without oversimplifying contested attribution. These are different renderings of the same evidence. The underlying LIDO record should not be made internally inconsistent simply to satisfy different reading ages. Prepare approved presentation variants rather than quietly changing the source’s cataloguing claims.

What LIDO 1.1 actually represents

LIDO, Lightweight Information Describing Objects, is maintained by the ICOM-CIDOC LIDO Working Group. Version 1.1 was published in December 2021 and supports multilingual collection descriptions. A LIDO record can contain identifying information about objects, descriptive information about events and relationships, and administrative information about the record or resources. The standard is designed for moving information between collection databases and public discovery services; it is not itself a visitor-facing page template.

This matters because a portal may map one LIDO element into a card title, another into a search facet and another into a longer object page. A translation can be valid XML yet land in the wrong place if the receiving portal’s mapping assumes a particular preferred display value. Before making multilingual copies, inspect how the institution’s export and the destination service treat repeated language variants, blank fields and display ordering. Do not assume that every language-aware consumer automatically selects the correct variant.

The LIDO Primer explains the distinction between display and index elements. Display elements provide human-readable renderings of information that may also be structured as indexing elements. For example, a materials description can be offered in a sentence familiar to visitors while the associated concept references remain suitable for cross-collection matching. This dual representation is particularly important when a target language lacks a neat single-word equivalent for an old craft, plant material or traditional measuring device. A fluent display phrase can coexist with a stable concept identifier.

Identify the version and local profile first

An institution may export LIDO 1.0, LIDO 1.1 or a profile layered on top of the core schema. A profile can impose rules that are narrower than the base XSD, such as mandatory elements, preferred vocabularies or local field cardinalities. Confirm the actual export target and the aggregating portal’s requirements before translating a record. The fact that LIDO 1.1 is backward compatible with 1.0 does not mean every institution will accept every repeated display element or every new interpretation of a multilingual field.

Ask for the schema validation process already used by the collections team. Some organizations validate against the official XSD, others also use Schematron rules or collection-specific quality checks. A translated variant should run through the same pipeline, with extra tests for language attribution and content consistency. If the current dataset fails validation before translation, record that baseline failure separately. Otherwise reviewers may blame the translator for historical defects or, worse, normalize an unsafe data repair as a language change.

Preserve the original record as a byte-for-byte reference and record its identifier, source system, export date and rights. A metadata dump can change independently of the visitor site, so the translator needs to know which source revision is being used. Do not translate a stale record from a downloaded PDF while the cataloguer is actively correcting its attribution. A reliable process includes a reconciliation step at release: compare current source claims to the translated claims and re-review anything materially changed.

Separate object identity from a visitor’s label

A collection object’s title is not necessarily its immutable identity. The same painting may have a traditional title, a descriptive title assigned by a museum and several titles recorded in different languages. The record’s identifiers connect these labels to one collection object. Translating a familiar object title might be useful for the visitor, but it cannot replace the object identifier or pretend that the new wording is historically attested if it is only a modern translation.

Keep record IDs and published object identifiers exact. Do not change authority identifiers, references to related works, collection system keys or the URLs of vocabularies solely to make them look local. A bilingual portal can display a localized object name and still expose its accession number unchanged. That number may appear on a gallery label, an image license request, a conservation report and an exhibition loan agreement. Rewriting it would fragment the evidence trail, not increase accessibility.

Named people and institutions need a policy. A transliteration of an artist’s name may help readers who use another script, while the established authority form should remain available for searching. A historical place name may be relevant to the event being recorded even if the same location is known by a modern name. Translate the explanatory context and, when justified, provide both names. Never make a historic person’s identity or an institution’s role appear more certain than the cataloguing evidence allows.

The display/index distinction is the main safety mechanism

Consider a ceramic vessel described in an export as “glazed earthenware.” A public translation may need a two-part phrase to communicate both the material and the surface treatment accurately. The controlled indexing component, however, could reference a material concept used by many museums. Keeping that concept linkage unchanged allows a visitor searching another language to retrieve comparable works. Replacing the concept URI with a translated word would break or weaken those connections.

A display statement can be more natural than the index term because it serves a different purpose. It can include an article, an adjective or a phrase explaining a technique. The index data can remain compact and concept-oriented. The translator should nevertheless check whether the display phrase overclaims anything. “Hand-painted porcelain” is not an acceptable modernization of “glazed earthenware” just because both describe attractive ceramics; it changes material classification and technique. The language reviewer and object specialist need to agree on the physical facts.

Where an indexed concept has an accepted multilingual label from a trusted vocabulary, consult that label as terminology evidence. Do not assume it is the best visitor-facing sentence or that every vocabulary covers the historical context precisely. The term is a controlled entry within a domain, while the museum caption may need caveats about region, period or contested categorization. Use the authority to maintain conceptual consistency, then write the actual display text for the intended audience.

Use xml:lang accurately and consistently

Language tagging lets consumers distinguish versions of human-readable content. LIDO uses the XML language attribute in defined text elements, including display fields that can repeat for language variants. A tag such as en identifies English; a tag such as zh-Hans can identify Simplified Chinese. The correct tag depends on the actual text, not the nationality of the curator or the location of the museum. Language and script distinctions should be chosen deliberately and validated using current language-tag guidance.

Do not assign a target-language tag merely because one heading was translated while the paragraph remains English. A mixed-language record may intentionally contain quotes, personal names or terms that remain in their original script; document that practice so the rendering application can communicate it honestly. For a primarily Chinese description with an English inscription quoted inside, the enclosing field’s language tag can describe the dominant language while the portal’s markup separately identifies the embedded quotation when supported.

Language tagging is not the same as translation approval. XML can contain xml:lang="fr" around a badly translated sentence and still parse. A cross-language review must check truth conditions, terminology and scope. The export test should additionally flag duplicated language variants, missing required source-language values and inconsistent language tags in repeated elements. A portal that falls back unpredictably to one language can make a good translation look incomplete or inaccurate.

A small illustration of language-specific display text

The following XML fragment is deliberately only part of a LIDO record. It shows a lido:objectMaterialsTechSet with two lido:displayMaterialsTech values for different languages, a pattern described in the official LIDO Primer. It is not an entire valid LIDO document: a full record needs the prescribed root, wrappers, identifiers and other required structures. This example is designed to clarify the location of translations, not to suggest that an arbitrary fragment may be imported as a collection record.

<lido:objectMaterialsTechSet xmlns:lido="http://www.lido-schema.org">
  <lido:displayMaterialsTech xml:lang="en">Oil on poplar panel</lido:displayMaterialsTech>
  <lido:displayMaterialsTech xml:lang="fr">Huile sur panneau de peuplier</lido:displayMaterialsTech>
</lido:objectMaterialsTechSet>

Both values describe the same material and technique. Neither changes the object identifier, its maker, its event dates or the indexed material concepts held elsewhere in the record. The example also shows why direct placement matters: the translation is a second permitted language version of a display text, not a second claim that the museum possesses another object. A destination portal should choose the display value that matches the reader’s language and fall back coherently if no suitable translation exists.

A real-world caption may require much more than four words. For example, a conservation report might distinguish an original surface from a later restoration, and the display phrase must not collapse them into one material. In that case, the short materials display can stay concise while a separate explanatory note tells readers how the conclusion was reached. Translation should preserve which material is evidence, which is hypothesis and which belongs to a later intervention. Formal validity is only the starting point.

Titles, alternative names and historical labels

Museum titles often carry several kinds of authority. A title inscribed by an artist is different from a title assigned by a collector, and both differ from a modern descriptive title created for online discovery. A translation should preserve the label’s provenance and status. If the source says “Untitled, later catalogued as River Scene,” the target language cannot legitimately present “River Scene” as the artist’s own title. Visitors use titles as evidence about creative intention, so this mistake matters.

In the object-identification area, inspect the structure used for title or appellation values and its repeatability before adding language variants. Use the current LIDO documentation to check the exact element and attribute placement in the exporting profile. A transformation that invents a new nested field simply because the content looks like a title may fail XSD validation or disappear when a portal maps the record. A local spreadsheet column named “Translated title” is not itself proof of a valid LIDO mapping.

When a historical label uses a term now considered offensive or misleading, do not erase it from the source record without an institutional decision. A public portal may present contextualized language, identify the archival wording as historical and explain why the catalogue uses a different contemporary description. The translation team can flag the issue and propose careful wording, but collection policy, community consultation and curatorial governance determine how the record should represent it. Accuracy and respect are compatible when claims are transparently attributed.

Material and technique terms need object-level review

Materials are difficult to translate because ordinary-language categories rarely align perfectly with conservation classifications. “Wood,” “hardwood,” “teak,” “laminated wood,” and “painted wood” do not describe interchangeable facts. Similarly, a painted surface and an applied coating may differ in technique even when the object looks similar in a photograph. Translators should consult the museum’s approved terminology, not choose a common dictionary equivalent without checking the object record and material evidence.

Imagine a woven classroom mat whose fibre has not been conclusively identified. The record says “plant fibre, possibly pandan.” A translation that replaces the uncertainty with “pandan mat” creates a specific material identification that conservators have not made. A better rendering communicates the broader class of material and the possible identification separately. If the source language lacks clarity, request a curatorial clarification and then carry that distinction into both language versions, rather than relying on an optimistic guess.

Technique descriptions also contain action and agency. “Cast,” “carved,” “assembled,” “printed,” and “repaired” can describe different stages in an object’s history. A translator should check whether the text concerns original manufacture, later modification or modern restoration. Mixing those stages can change what students learn about the object’s technology and cultural context. An accurate museum translation teaches readers to distinguish what was made from what subsequently happened to it.

Provenance is a sequence of claims, not a story to polish

Provenance statements may name previous owners, sellers, donors, excavations, collection transfers or gaps in documentation. The sequence and certainty of these assertions matter. An elegant narrative can become misleading if the translator removes “reported,” “attributed,” “before,” “after,” or “not documented.” A chain of custody may depend on those qualifiers. The localized text must not transform a provisional association into proof of ownership, lawful export or a continuous record.

Read each event against its source evidence and role labels. A collector, creator, donor and vendor participate in different relationships. A translated display line that turns the donor into the maker changes the object biography. When the source uses a date range, preserve whether it is an event interval, an approximate century or an uncertain terminus. If the record cites a reference or acquisition register, keep the link or identifier attached to the right claim. A reader in another language deserves access to the same evidence chain.

Provenance may involve sensitive cultural and legal questions, especially around colonial collecting, archaeological contexts and repatriation. The translation should avoid claiming legal conclusions that the record does not establish. It may need carefully reviewed terminology for “acquired,” “removed,” “collected,” “seized,” and “returned.” These are not interchangeable verbs. Curatorial consultation and, where relevant, community perspectives are part of meaning verification; language software cannot settle historical disputes.

Make event roles visible without inventing them

LIDO event structures can distinguish activities and participants, such as production, acquisition, use or exhibition. A visitor-facing portal may condense these into a timeline. Translation must preserve what the event is, who participated and what the evidence supports. A label that says “made in 1920” when the source event is “acquired in 1920” shifts the date from the museum’s documentation of ownership to the manufacture of the object. The object could be much older.

For each event, create a review card with the event type, linked actor, location, time expression, evidence source and English display wording. Ask the bilingual reviewer to describe what happened without reading the source, then compare that summary with the structured facts. This reverse paraphrase catches a common failure: every individual word is translated plausibly, but the final sentence assigns the wrong role or timing. The user should be able to reconstruct the same event relationship in both languages.

A good translation may leave a historic proper noun unchanged while translating surrounding role words. It should also make clear when a place name refers to a former political entity or a broader region rather than a current administrative boundary. A modern visitor may benefit from a contextual note, but the note should not rewrite the historic claim. Keep contemporary navigation assistance separate from the original event location and cite the authority used to connect them.

Rights descriptions are not decorative metadata

Museum records may refer to reproduction rights, rights holders, institutional credit lines, licenses, access restrictions or image-use conditions. These can affect whether teachers may reproduce a photograph or a researcher may publish a detail. Translation should not simplify “permission required for commercial use” into “free to use,” or confuse public-domain status of the underlying object with rights asserted over a digital photograph. Those are different issues and sometimes vary by jurisdiction.

Preserve license identifiers, URLs and machine-readable rights references exactly unless an authorized rights owner has issued a new canonical reference. A localized explanatory note can help visitors understand what a license permits, but it should not supersede the legal text. If a usage condition is ambiguous, refer it to the institution’s rights team rather than inventing a convenient answer. Accurate translation often means explicitly saying that a particular reuse question requires additional permission.

Credit lines may include punctuation, historic names and donor acknowledgments specified by a loan or donation agreement. Treat them as controlled copy until the owning team approves any localization. A label that accidentally drops a donor designation can cause contractual and reputational problems even if the display otherwise looks polished. Compare these strings at release and distinguish translated reader guidance from exact wording the institution is required to display.

Prevent Unicode, XML and markup errors

An XML parser accepts Unicode text, but special characters must still be serialized correctly. The ampersand has syntactic meaning in XML and must be escaped when it appears as ordinary text. A translator may introduce characters outside the original script without difficulty if the document encoding is correct, but a tool that changes the encoding declaration or mishandles combining characters can corrupt content. Run parse-and-round-trip checks on the exact exported bytes.

Do not treat xml:lang as an arbitrary custom attribute, and do not add XML elements to hold translated labels outside the structure allowed by the LIDO schema. A well-intentioned content editor may paste HTML emphasis tags inside a field that accepts only simple text. The resulting fragment could fail validation or be stripped by a portal. Use the documented content model, and provide richer formatting at the presentation layer when the collection platform supports it.

Bidirectional scripts and long names should be tested in the receiving interface. An Arabic title next to an accession number, punctuation and Latin-script artist name may look correct in the XML but display in confusing order in a browser card. A long translated title may be clipped in search results and lose the qualifying phrase that expresses uncertainty. Review the rendered card, object page, search snippet, mobile layout and screen-reader reading order with real examples.

Validate mappings in the target portal

A record passing an XSD is not proof that a discovery system will show the intended language. The portal might prefer the first display value, fall back to English, fail to index language variants or choose an unexpected title. Test one object with all proposed languages, one object with only the source language and one object with partial translation. Confirm how the destination handles each. If an empty translation causes a blank card, the release process needs a fallback rule or a decision to omit that empty variant.

Also check search retrieval. A visitor who enters a translated craft term should ideally find the object, even when the underlying concept remains identified by a URI. Whether that works depends on indexing and vocabulary mappings, not only the LIDO text. Separate three checks: the word appears in the exported XML, the receiving system indexed it correctly, and a user can retrieve the correct object using ordinary search language. Each stage can fail independently.

Record the mapping version and destination portal release. A later portal change may alter fallback behavior without a change to the museum metadata. Keep a small multilingual regression set of representative objects: a known creator, an uncertain attribution, materials terminology, complex provenance, restrictive rights and mixed-script display text. After an upgrade, re-run the same queries and compare results. This turns localization from a once-off translation into a maintainable part of public access.

A practical reviewer-to-reviewer workflow

The collections manager first identifies the authoritative record and approves a field-level export. The localization editor then extracts permitted display text, its context and source references. The translator prepares target-language text without access to immutable IDs and controlled concept definitions as editable targets. A curatorial reviewer checks truth conditions, attribution, chronology and community-sensitive language. The technical reviewer checks XML structure, language tags and consumer behavior. These roles may be performed by fewer people in a small museum, but the checks remain different.

Use a change table with categories such as “direct translation,” “requires curatorial decision,” “historical-language quotation,” “legal-rights wording,” and “source correction needed.” Only the first category should flow through a routine low-risk approval. If source wording is wrong, the collections team should correct the canonical record according to its governance rules; the translator should not secretly repair it inside one language. This avoids divergent truths where the English portal and translated portal describe different objects.

A record is ready for public delivery only after three kinds of evidence agree. XML validation shows the structure is acceptable. A comparison of protected identifiers and relationships shows the new version still concerns the same collection object. Human review and portal tests show that the target-language reader receives the intended facts, cautions and permitted-use information. A green result in one category does not replace the others. Keep the acceptance record linked to the specific source version and output artifact.

Common failures and targeted repairs

A first failure is an invented certainty. The English description says “attributed to a workshop,” while the translation states the named workshop made it. Repair the target wording to preserve attribution and review the source’s underlying evidence. If the source itself is vague, annotate the issue for the cataloguer. Do not compensate by adding words like “allegedly” everywhere; the right level of uncertainty must fit the original documentation, not the translator’s personal suspicion.

A second failure is a vocabulary mismatch. The portal can show the translated material name, yet search results do not connect it to similar objects because a concept identifier was replaced. Restore the original authority reference and let the indexer use multilingual preferred labels or an approved synonym mapping. Retest both the object display and cross-language search. This repair is not merely XML housekeeping; it restores how visitors discover related evidence across institutions.

A third failure is a rights error. A translated reuse instruction suggests that online photographs are unrestricted, while the canonical record requires a credit line and permission for some uses. Suspend the misleading target-language text, obtain the approved wording from the rights team and check the portal’s download or sharing controls. If those controls display a separate untranslated warning, include it in the overall localization scope. Users should not receive contradictory rights guidance from two parts of one page.

Changed-context exercise: a disputed school bell

A local museum records a brass school bell with a firm accession number, an approximate early twentieth-century date, and a donor’s account that it may have been used at a former school building. The English display text distinguishes the bell’s physical material from the donor’s unverified location claim. A new multilingual portal asks for Chinese and Malay object labels. An editor suggests giving the bell the name of the historic school as a definite title and replacing the donor’s uncertain sentence with a confident summary to make the page easier for children. What should the translation team do?

First, preserve the accession number and the date’s approximate status. Translate the materials and object description using the museum’s terminology for brass and bell construction. Treat the former-school connection as an attributed donor claim, not a verified place-of-use fact. If the title is merely assigned for cataloguing, label it accordingly; do not turn an uncertain location into the object’s historic proper name. Keep any linked person, school and location identifiers unchanged, and ask the curator whether a separate educational note can explain the uncertainty clearly to children.

For the technical test, export the two language variants according to the institution’s LIDO profile, validate the complete records, and inspect portal fallback and search. For the human test, ask bilingual reviewers what the bell’s date and provenance actually establish. A pass means they understand that the object is old and associated with a claimed school history while recognizing the limits of the evidence. The lesson transfers to archaeological artifacts, photographs, donated textiles and natural-history specimens: translation carries certainty levels, not just nouns.

Practical review checklist

  • Confirm the actual LIDO version, profile, source record revision and intended receiving portal.
  • Record canonical object identifiers, authoritative names, concept URIs and event links.
  • Separate display text from indexing fields and from administrative rights obligations.
  • Tag language variants correctly and avoid unsupported new elements or attributes.
  • Preserve uncertainty, attribution, chronology, materials and role distinctions.
  • Review historic names, contested terminology, cultural context and rights with the responsible specialist.
  • Validate XML and any profile-specific rules; compare protected structures with the source.
  • Test locale selection, fallback, search indexing, mobile display and accessibility.
  • Check credit lines and license references before allowing copying or download.
  • Keep the source version, reviewer, release mapping and correction log together.

Limits and what a dependable publication can claim

LIDO is a metadata exchange framework, not a guarantee of how every museum website will render a language variant. The standard tells producers where content belongs and which structures are allowed; individual systems determine display priorities, discovery behavior and editorial governance. This article uses a small schema-aligned fragment to illustrate multilingual material text, but a real export must be checked against its complete record structure and any application profile. It does not certify a particular museum’s software or establish disputed historical facts.

The safest translation system allows uncertainty and evidence to travel with the public words. A reader should learn not only what an item is called, but why the institution says so, when the claim was recorded and whether other interpretations exist. Bilingual clarity helps people ask better questions of a collection. It becomes harmful only when a fluent sentence erases the distinction between documented fact, cataloguer interpretation and community testimony.

A useful final package therefore combines verified source data, approved language-specific display statements, validation reports, portal screenshots or test observations and a clear owner for future corrections. It does not replace the institution’s canonical accession system or its curatorial decision process. Translate quickly by working within those boundaries, then use the saved time to examine the few ambiguous claims that matter most to how the public understands the object.

Transfer the method to loans, exhibitions and collection updates

An object that travels to another institution may appear under different display conventions without losing its home collection identity. A loan exhibition might need a short bilingual gallery label, while the central catalogue requires a longer provenance note and an internal conservation history. The exhibition text can be edited for reading length, but any change in attribution, date or material must still be checked against the source record. Record which parts were summarized for visitors and which were actually translated. Otherwise a shortened caption may later return to the database as if it were a complete scholarly description.

Consider also a newly discovered ownership document. Curators may revise the provenance record after the initial multilingual export. The translation team should receive a change notification identifying the new evidence, affected event and claim, and the precise passages that need review. Old translated versions may remain visible in caches or printed labels, so correction should include a communication plan rather than only replacing an XML file. Reliable multilingual access means readers in different languages are updated when the museum’s understanding changes, including when that change introduces more uncertainty instead of resolving it.

Frequently asked questions

1. Does LIDO 1.1 support multilingual museum records?

Yes. LIDO is designed for multilingual environments and permits language variants in relevant elements. The exact repeatability and placement depend on the element and the applicable profile; check the official schema rather than adding arbitrary translations.

2. Can a translated object title replace the accession number?

No. A display title helps readers recognize a work, while accession and record identifiers connect documentation, conservation, loans and rights. Keep the identifiers stable.

3. Why not translate controlled-vocabulary URIs into words?

A URI identifies a concept across systems and languages. Its labels can be displayed in different languages, but replacing the URI with a text string breaks the stable reference used for discovery and reconciliation.

4. May a curator change uncertain provenance during localization?

A source correction may be legitimate, but it must go through the collection’s evidence and governance process. A translator should not independently turn a conditional claim into a factual assertion.

5. What does xml:lang prove?

It identifies the language of the text to consumers. It does not prove translation quality, source authority or curatorial approval. Those require separate review.

6. Is a well-formed XML file ready for a museum portal?

Not necessarily. The document may fail the full LIDO XSD, an application profile or the destination’s mapping expectations. Test all three levels and inspect what visitors actually see.

7. How should a historical term with harmful connotations be handled?

Preserve the documentary context while following the institution’s ethical language policy and appropriate community consultation. A public note can explain why a historical expression appears and which contemporary terminology is preferred.

8. Can one translated display text serve every audience?

Not always. Researchers, schoolchildren and general visitors need different levels of explanation. Create approved presentation variants while protecting the same underlying evidence and source attribution.

9. What if the portal always shows English first?

Check the export’s language tags, the destination’s field mapping and its locale fallback settings. The LIDO record alone does not guarantee that a consumer will select the right variant.

10. Which review is essential before publishing rights information?

A rights specialist should verify conditions, credit requirements and license references. Translation must not expand the permissions actually granted for the object or its digital reproduction.

Authoritative sources and further learning

Relevant verified eduKateSG reading