Translating EAC-F 1.0 archival function records means explaining why institutions performed activities and produced records without confusing the function with the people, offices or files associated with it. A reliable multilingual function description preserves its stable identifier, dates, responsibility changes, related agents, linked record sets and the distinction between a purpose and the organizational unit carrying it out.
This guide explains EAC-F 1.0 localization for archival functions and activities in public administration, education, health, business, cultural institutions and historical research. It covers function names, mandates, business processes, activity hierarchies, temporal change, multilingual terms, linked agents, EAD records, authority control, XML schema validation, practical migration and international discovery.
EAC-F 1.0 was introduced with the revised Encoded Archival Standards suite released on 31 July 2026. In that suite, EAD 4.0 describes what records exist, EAC-CPF 3.0 describes the agents involved, and EAC-F 1.0 describes the functions and activities that help explain why records were created. That complementary relationship is the central rule for careful translation: translate the explanation, not the underlying historical cause.
The missing ‘why’ in archival discovery
A reader can find a file and know who signed it while still not understanding why it was created. Function descriptions address the organized activity behind records: licensing, collecting taxes, inspecting schools, managing water supply or delivering public health programmes. The purpose is to expose context that titles and creator names alone cannot provide.
A government form titled ‘Quarterly return’ makes little sense without the administrative function requiring that return. Different departments may have produced such forms under the same statutory responsibility. If a translation only names the department, the shared function is obscured.
Start by asking what activity the record documents and what purpose or authority motivated it. Preserve any official function identifier and the links to relevant records. A translated name should make the activity clearer without converting it into the name of an office.
EAC-F is a distinct member of the 2026 EAS suite
The EAC-F 1.0 XML standard was released alongside EAD4 and EAC-CPF3. It draws on the International Standard for Describing Functions and supports interoperable descriptions of functions and their relationships. Institutions should consult the current tag library and the published versioned schema rather than copy assumptions from older person or finding-aid formats.
An authority catalogue can contain an EAC-CPF creator record, an EAC-F function record and an EAD archival description for related material. They are not interchangeable XML files even when their human-readable notes use similar phrases. An import process that treats all three as one type may produce plausible but inaccurate displays.
Document the function-record version, XML namespace, validation rules and linked authority models before translation. Test one end-to-end record in the real catalogue. Keeping the three entity classes separate prevents well-meaning multilingual edits from destroying meaningful archival connections.
A function can outlive the institution carrying it out
The same function may be reassigned over decades as administrations reorganize. An inspection duty can move from a municipal council to a ministry and later to an independent agency. The underlying reason for making inspection records may remain recognizable despite changes in the agent responsible.
If a target-language description replaces ‘school inspection’ with ‘Ministry of Education inspection department’, readers might wrongly assume that function existed only while the named department did. Records created by earlier councils would be disconnected from their proper functional context.
Translate the function’s purpose independently of its current owner. Describe transfers of responsibility as dated relationships with agents. A long-running function should not disappear from history merely because the public-facing organization has a new name.
An office is not the activity it performs
Organizational charts describe departments, reporting lines and job titles. Functional classification describes what an organization does. A records officer might manage admissions, archives or procurement at different times; the office’s name alone does not explain the distinct processes and evidence each produces.
A university registrar’s office can oversee student registration, examinations and degree conferral. Translating ‘registrar’ as though it means ‘student registration’ in every case loses the examination and certification activities. It also makes search results incomplete.
Keep organization names in agent authority descriptions and describe activities at the appropriate functional level. Use explicit links between the office and the functions it performed during known periods. Verify that a label’s grammatical form does not quietly shift it from an action to an institution.
Purpose, function, activity, task and transaction
Descriptions can operate at several levels of granularity. A broad function may encompass business processes, activities, tasks and individual transactions. The terminology must be consistent enough that a reader understands the scale of what is being described rather than viewing every action as a standalone administrative function.
Public education is broad; processing a scholarship application is narrower; acknowledging one submitted form is narrower again. A translation that uses the same general term for all three makes it difficult to understand record series or retention rules based on functional classification.
Agree on an explicit hierarchy and a controlled glossary of levels. Keep identifiers and parent-child relationships stable. When a target language lacks a perfect one-word distinction, use a clear descriptive phrase and test it against examples from all classification levels.
Mandates describe authority to act
A function may be carried out because of legislation, a charter, an executive decision, institutional policy or long-standing practice. Its mandate explains why the activity exists and what powers or responsibilities support it. The translator must not turn a historical mandate into a stronger modern legal assertion.
A local board might have been empowered to recommend permits but not issue them. Translating ‘recommend approval’ as ‘approve’ changes the legal force of the record. The resulting description could mislead readers about the board’s historical authority.
Preserve modal verbs, jurisdiction, effective dates and the source of authority. Cite the governing instrument where the record does so. If the original description is ambiguous about legal powers, preserve or flag that ambiguity rather than using confident target-language wording.
Function names should describe a recognizable action
A function label needs to be concise enough for lists and indexes but informative enough to identify the activity. Labels built from abstract nouns can sound natural to one professional community and opaque to another. International readers often benefit from a short explanation accompanying a stable authorized label.
‘Regulation of commercial water abstraction’ may identify a specialized function. Rendering it simply as ‘water management’ broadens the scope beyond the evidence. Conversely, a literal sequence of nominalizations may be unintelligible to a non-specialist and prevent discovery.
Choose a controlled target-language label that preserves the activity’s boundaries, then explain specialized vocabulary in a scope note. Test the label in search results, menus and linked record descriptions, not only as an isolated entry.
Function identifiers are technical anchors
A stable function identifier allows a catalogue to connect the same activity to several agents, dates and collections. It should remain unchanged when translated labels are added. If the identifier changes with the display language, the function may appear to be several unrelated activities in harvested datasets.
Suppose a civic authority uses F-042 for building safety inspections. A translated interface may call the activity by a different name, but the same F-042 should still link to reports created by the original authority and its successor. An invented language-specific code would fragment the history.
Protect persistent identifiers from transliteration and automatic formatting. Use language-specific labels or authorized variants without replacing the underlying record identity. Verify backlinks in the EAD and EAC-CPF systems after every export.
Scope notes define what belongs inside a function
A scope note explains the activities included in a function and may distinguish them from related responsibilities. It is crucial where neighboring terms overlap. Translation must retain those boundaries so a reader can tell what evidence a function record can reasonably explain.
A licensing function may cover application review, renewals and appeals but exclude enforcement inspections. A shorter translation that calls the whole function ‘regulatory control’ suggests a broader remit and may pull unrelated records into the same discovery pathway.
Translate inclusion and exclusion statements explicitly. Check the meaning of verbs such as ‘assess’, ‘grant’, ‘monitor’ and ‘enforce’ because they indicate different administrative powers. Review a sample of connected records to see whether the target-language scope still fits.
Function history follows responsibilities through time
A function record can explain how activities developed: new rules, changing technology, transfers between agencies and periods of interruption. These are historical assertions, not mere background. They help readers interpret why similar records from different decades may have different forms.
An office may have collected paper census schedules before transferring to computerized registration. A translation should not describe earlier records with terminology that presumes modern digital workflows. Nor should it erase transitions that explain shifts in categories or frequency.
Preserve sequence, cause and uncertainty in the history note. Mark the dates associated with each change. When a proposed translation introduces a modern term, ensure the reader can distinguish the historical activity from the modern explanatory vocabulary.
Dates need to describe the correct event
Function dates can mark establishment, operation, suspension, abolition or transfer. A function may have multiple periods and overlapping agents. A date of legislation is not always the date an activity began, and the creation date of a surviving record is another matter again.
A statute approved in 1954 may only enter into force in 1955. The agency may not produce its first inspection report until 1956. Translating all three as ‘from 1954’ distorts the timeline and weakens the user’s ability to interpret the documents.
Record the event attached to each date and preserve expressions of approximation. Keep machine-readable values separate from locale-specific display order. Compare timelines against linked creator and record descriptions to catch contradictions.
Functions can be delegated or shared
An activity may be performed by more than one institution, concurrently or in different places. Delegation can transfer specific powers without eliminating the original authority. Translators should avoid language that suggests exclusivity when the source documents show shared responsibility.
An education ministry might set examination policy while independent boards administer tests. Both are connected to examinations but carry different functions. Calling both simply ‘the examinations authority’ can obscure accountability and the provenance of related records.
Keep relationship roles precise and date them where evidence allows. Distinguish establishing policy, implementing it, supervising it and auditing outcomes. A well-localized description gives readers enough information to understand the division without needing to know the national administrative system.
Business classification schemes are contextual tools
Records-management systems often classify material by function and activity rather than only by department. A code in a business classification scheme can connect documents to retention rules, workflows and organizational responsibilities. Its exact characters and parentage matter.
A file marked F/EDU/03 might refer to student examinations in a local scheme. Translating EDU into another language inside the code can break automated filing, while translating the label displayed beside the code can improve use without altering the classification.
Treat scheme codes as controlled identifiers. Maintain the documented hierarchy and any edition date, because classifications can change. Test whether a user’s search can find the correct code through either the original label or its approved translation.
Retention schedules should not be rewritten by translators
Functional classification sometimes connects to retention and disposal rules. A label that changes the apparent scope of a function can cause people to associate records with the wrong retention class. Translation is therefore a governance issue as well as a linguistic one.
If a schedule distinguishes ‘grant application decisions’ from ‘grant payment administration’, translating both as ‘grant processing’ might conceal different retention periods. A records officer could misread the classification and apply the wrong disposal rule.
Keep retention identifiers, effective dates and rule boundaries explicit. Have the responsible records manager approve localized schedule terminology. Never infer new disposal instructions from a broad function description or treat an educational article as legal retention advice.
Linked EAD records answer what was produced
EAD describes record groups and their arrangement. EAC-F adds the context of the activity that produced or used them. An international archive can connect a function record to several EAD collections, helping researchers see continuity despite changing agencies.
A land-registration function may be linked to historical deed books, application folders and digital transaction logs. These holdings should not be merged simply because the same function underlies them. Each archival collection has its own provenance, dates and physical or digital extent.
Preserve the function-to-record relationships and the record identifiers. Translate the explanatory link labels, not the target URLs or codes. Open links in the public catalogue and check that they point to the relevant holdings rather than generic search pages.
Linked EAC-CPF authorities answer who acted
Agent authorities can describe the persons, corporate bodies or families that performed functions. This is not the same as describing the function itself. A multilingual record should preserve the distinction even if a particular office and activity have nearly identical English names.
A ‘Housing Allocation Bureau’ is a corporate body; ‘allocation of housing units’ is an activity. The bureau could be reorganized while the activity continued under another agency. The names may look similar but should not collapse into one authority record.
Review entity types and stable links when localizing relation labels. Test the temporal direction of responsibility transfers. Good context allows readers to navigate from an agency to its functions and records without confusing the three.
Relations between functions need precise meaning
Functions can be broader, narrower, related, preceding or succeeding within a classification or historical model. The relationship must come from the repository’s supported vocabulary or documentary evidence. Ordinary-language words such as ‘includes’ and ‘replaced’ can carry more certainty than the source permits.
Inspection of food premises may be a subfunction of public-health regulation in one system, but a separate responsibility in another. A translator cannot assume the same hierarchy applies everywhere merely because the labels resemble one another.
Preserve relationship identifiers and direction. Translate the controlled label through an approved vocabulary and document local differences in classification. A diagram built from translated metadata should express the same meaningful connections as the source network.
Relationships must carry time when responsibility changes
A function can pass through several agents and regulatory contexts. If dates are missing or mistranslated, readers may attribute an earlier record to a later institution or imagine uninterrupted responsibility where there was a gap.
Suppose civil aviation licensing was conducted by a ministry until 1997, an independent authority from 1998, and a new regulator from 2015. The function may remain identifiable while responsible agents and legal frameworks change. A single undated association hides this progression.
Use date ranges and related notes in ways supported by the schema and source evidence. Compare the timeline to agency authorities. Do not fill gaps by assuming the next organization began its responsibility on the exact day the previous one ended.
Function status is not the status of its description
A catalogue may distinguish a function that remains active from one that is obsolete, as well as a record that is a draft or has been revised. These concepts can appear together in controlled statuses. Translating them with one word such as ‘finished’ creates operational ambiguity.
An abolished historical function can have a fully approved authority record. A current function can be described in a draft entry. If a user reads ‘inactive’ as meaning that the record itself is invalid, historical research and records management can suffer.
Inspect the actual value vocabulary and field role before translation. Where needed, use labels such as ‘historical function’ and ‘description approved’ separately. Test filters to make sure status displays do not suppress legitimate historic records.
Legal jurisdiction should not be inferred from terminology
Many countries use the same words for administrative functions but assign different powers and responsibilities. A translation for global readers must explain the jurisdictional context rather than mapping every local institution onto a supposedly equivalent foreign model.
Words such as ‘council’, ‘district’, ‘commission’, ‘permit’ and ‘licence’ may have different legal meanings. A function called ‘licensing’ in one administration might involve registration only in another. Substituting familiar foreign vocabulary may create false authority.
Preserve official legal references and clarify their meaning in plain language. Do not claim equivalence across jurisdictions unless the sources support it. A world-facing description should enable comparison without falsely asserting sameness.
A function name can change while purpose remains
Administrative vocabulary develops. Earlier records may use terms now replaced by newer professional language even where the essential activity continued. Localizers need to decide whether a new label is a genuine reformulation of the same function or a historically different responsibility.
An office might once have described immunization records as ‘inoculation registers’. Using a modern umbrella term can aid search, but the historic label has interpretive value. Erasing it may make old documents and catalogue references harder to recognize.
Maintain original and later authorized variants with temporal context. Add readable access labels without claiming that the function was historically called by the modern term. Test older terminology in search and cross-reference tools.
Multilingual functions need controlled labels
Different languages may divide the concepts behind a function name differently. A direct word-for-word translation can overstate scope or create an unfamiliar bureaucratic phrase. Controlled multilingual labels make indexing consistent while allowing short explanations for the public.
‘Public procurement oversight’ may involve reviewing purchasing procedures, not directly purchasing goods. A translation that drops ‘oversight’ turns the monitoring function into the operational one. The same problem arises with ‘authorization’, ‘assessment’, ‘registration’ and ‘enforcement’.
Approve labels with a bilingual subject specialist and use the corresponding stable concept ID. Keep a scope note that explains the action. Search with synonyms when useful, but do not give synonyms the power to rewrite official relationships.
Functions are often described through verbs, not departments
Natural-language clarity improves when a functional label tells readers what is being done: assessing applications, maintaining roads, recording births, licensing operators. Department names can be opaque or too broad. Translators should recover the action from the source without inventing specific steps.
An archival system that labels a function simply ‘Infrastructure’ leaves readers unsure whether it means planning, construction, maintenance or regulation. If the record contains a narrower authorized scope, the target language should make that narrower activity visible.
Use verbs or action nouns where they preserve the original model, and support them with precise scope statements. Avoid converting broad functional categories into narrow activities solely for a more engaging title.
Activities are evidence of processes, not generic outcomes
A public administration may document steps that lead to a decision, not only the final result. A function description can contextualize these processes without implying success, completion or approval. Translation should distinguish receiving, checking, reviewing, deciding and recording.
A folder marked ‘application assessment’ could contain rejected or incomplete applications. Translating the function as ‘permit issuance’ implies a positive outcome the source does not support. This matters for historians and for people trying to understand an agency’s responsibility.
Preserve process stage and outcome language. Use a controlled glossary for verbs with legal or administrative force. Check actual records to ensure that a translated process label does not promise a result.
Evidence about a function comes from several sources
Legislation, administrative manuals, organizational charts, minutes and archival records may all document a function, but they answer different questions. A law may state a mandate; manuals describe procedures; records show how work was carried out in practice.
A policy might require annual inspections, but the surviving files reveal that some years were skipped. Translating the legal mandate as though it proves continuous performance turns prescription into evidence of action. The distinction is central to responsible archival interpretation.
Preserve source attribution and modal language. Use a note to distinguish intended responsibilities from documented historical activity. When sources conflict, describe the conflict or flag it for expert review rather than smoothing it into a neat narrative.
Functions and records are not the same unit of preservation
Records may survive unevenly while the function that produced them is still known. Conversely, a function description may be incomplete even where many documents survive. Localization should make the available relationships understandable without claiming perfect documentary coverage.
A licensing office might have issued thousands of permits while only a small sample survives. A translated function record that says ‘all licensing records’ would exaggerate the collection. EAD access notes and extent information provide necessary boundaries.
Translate claims about surviving evidence carefully. Differentiate the existence of a function from completeness of its archival documentation. Link to collection inventories instead of copying aggregate counts into an unrelated functional summary.
Function hierarchies need stable parentage
A function may have several activities beneath it, but one classification scheme’s hierarchy need not match another. Multilingual mapping requires careful attention to broader and narrower concepts, not just common keywords.
A national agency may classify vehicle registration under transport regulation while a municipal archive groups local vehicle permits under public order. Both descriptions may be useful in their systems. Moving a child function to a different parent merely to make a translated menu more familiar is a structural alteration.
Translate visible headings while retaining coded parent-child relationships. Test hierarchical navigation and exports. Where crosswalks are needed, document the mapping rather than silently replacing the original classification with a foreign one.
Places can determine the scope of responsibility
Some functions are defined by territory: managing a river basin, collecting municipal rates or supervising an overseas district. Translators should distinguish the geographic reach of a mandate from the physical location of the office responsible for it.
A city-based department might supervise water infrastructure across rural districts. Calling the function ‘city water supply’ because the office sits in the city can misdescribe its jurisdiction. Historical boundaries can also shift during the function’s existence.
Retain geographic qualifiers and authority links as recorded. If place names change, include supported historical variants. Confirm that map interfaces and translated text convey the same jurisdictional extent.
Source quotations may contain obsolete language
Older mandates and administrative documents often use historical terminology. A modern translation may need explanatory notes so readers understand the function, but directly replacing a source phrase with current vocabulary can erase evidence of how the state or organization represented its duties.
An old colonial ordinance might describe population registration in terms that are objectionable or misleading today. A translation should not endorse that language, yet the wording may be necessary to understand institutional history and the origins of records.
Mark quoted or transcribed wording clearly and use contextual explanation. Follow institutional policies for potentially harmful descriptions. Preserve the historical relationship between the official source and the modern subject term.
Function records have their own maintenance history
The authority description is a digital record that can be created, revised, corrected and migrated. Those editorial events are different from the function’s historical activities. The date a translator updated a description is not the date an office gained a statutory responsibility.
An authority record updated in 2026 may describe tax collection between 1890 and 1910. If a localized display treats the last modified date as a period of function activity, readers will misunderstand both the archive and its digitization history.
Preserve maintenance-event metadata, reviewer responsibility and version history where supported. Keep historical dates attached to historical assertions. A reader should be able to see what was documented about the past and what happened to the modern catalogue.
XML element names and namespace URIs must remain stable
EAC-F is encoded in XML. The schema controls the structure; human-language notes and selected labels are the content available for translation. Translating XML tags or attribute keys because they resemble English words breaks compatibility with parsers and validators.
A translator might change a field’s technical name to a familiar equivalent while leaving the value untouched. The record could then fail schema validation or be ignored by a downstream service. A malformed relation URI can be even harder to detect from the rendered display.
Extract approved text segments, protect identifiers and machine values, and reinsert translations without altering markup. Validate against the official EAC-F 1.0 schema and appropriate Schematron rules. Inspect the public output as well as the raw XML.
Schemas and rule checks serve different purposes
An XML schema can verify many structural requirements. Schematron can test additional constraints or contextual rules. Neither can determine whether a translated function label is historically accurate, a mandate has been overstated or a linked authority is the right institution.
A record might validate technically while asserting that an education board operated a function decades before it existed. A translated legal term might sound plausible but introduce a power unsupported by the source. Validation software cannot replace archival and legal expertise.
Combine technical validation, cross-record consistency tests and human subject review. Keep reports for each released version. A zero-error XML result should be understood as structural evidence, not a certificate of historical truth.
Worked case: road maintenance after government reform
An urban road maintenance function moves from local borough offices to a metropolitan agency and later to a contractor supervised by a transport authority. Records include pothole reports, resurfacing schedules, contracts and incident investigations.
Different agents carried out different parts of the work across time. Translating the function as ‘transport authority administration’ would erase early borough activity, while calling all contractors government departments would misrepresent their roles. The function record should preserve purpose and date-specific relationships.
Test the translated description against records from before and after reform. A reader should see the activity’s continuity while understanding who performed or supervised it at each stage and why several separate archival series exist.
Worked case: school examinations and certificates
An education department administers public examinations, accredits exam centres and issues certificates. The three activities may be linked under one broad examination function but produce different records and confer different responsibilities.
A translated label such as ‘school results’ is too narrow to represent the whole function, while ‘education oversight’ is too broad. A results sheet is not evidence that the same body accredited a centre or designed the test. The categories matter for citizens seeking specific documents.
Preserve the activity hierarchy, responsible agents and record links. Search for all three kinds of evidence through the target language. The outcome should help a user identify which office and historical record set can answer a real question.
Worked case: public-health reporting during a crisis
A health authority collects case notifications, issues public advisories and coordinates contact tracing. These are related but not identical activities. Their responsibilities may be delegated rapidly during an emergency, making precise dates and actor relationships particularly important.
If the translator uses one word for notifying authorities and issuing public alerts, readers may misunderstand both the data flow and the legal responsibility. A public announcement may not indicate that every underlying case record is publicly accessible.
Translate each activity with clear purpose and scope. Check access limitations on linked patient records, and preserve changes in responsibility. A function record should illuminate administrative context without disclosing sensitive health information.
Worked case: land registration and title dispute
A land registry records deeds, maintains title indexes and processes challenges. Historic legal frameworks may distinguish recording documents from validating their contents, and changing that distinction in translation can mislead future users.
A target-language phrase meaning ‘guarantee of ownership’ may be stronger than the historical registry’s role of receiving a deed. A translated function description that promises legally conclusive title could cause serious misunderstanding.
Keep the actual legal act and outcome separate, cite source mandates and seek specialist review for non-equivalent terminology. This is an example where precise language is more valuable than a smooth, familiar translation.
Interoperability across archival systems needs deliberate mapping
A function record may travel from a local records office to a national portal, a research catalogue or a linked-data graph. Each consumer may interpret identifiers and controlled labels differently. Multilingual display improves access only when the underlying relationships remain consistent.
A receiving catalogue might discard a local extension and show the function as an untyped subject. The text still appears, but the ability to connect activities, agents and records may be lost. This is an integration problem rather than a translation problem.
Test real interchange pathways and document fallbacks. Preserve version information and identify unsupported mappings. Crosswalks should be explicitly approved and checked; a localizer should not quietly substitute a broad subject term for a function authority.
Translation review should model real research tasks
Review by a linguist, an archivist, a functional-classification specialist and an XML integrator catches different kinds of defects. The first can detect language error, the second historical inaccuracy, the third scope or retention confusion and the fourth broken machine relationships.
A technically valid function record may have the wrong legal force; a historically accurate description may use terms that an international reader cannot understand. Review should test both. Narrow samples of easy modern records cannot reveal difficult historical cases.
Use examples with renamed institutions, uncertain mandates, several responsible agents, restrictions and multiple languages. Record decisions with supporting sources. Test user tasks such as finding the records produced by a function before and after an institutional reform.
Final release checklist for a multilingual function record
Check function IDs, exact source labels, translated terms, definitions, classification levels, dates, jurisdictions, legal references, related agent identifiers and links to record descriptions. Inspect whether the function status and the authority record’s own maintenance status are kept distinct.
Verify machine-readable XML and exported displays. Open a function through a target-language search, navigate to its responsible agents and linked records, then return through the reciprocal links. Repeat for a historic function and for one performed by several organizations.
Save the source and translated artifacts, schema-validation report, editorial approvals and known display limitations. Publication is successful when the global reader can understand what an activity was, why it existed, who carried it out, and which records support that account.
Questions readers frequently ask
**What does EAC-F describe?** It describes archival functions and activities, helping explain why records were created and how work relates to agents and record sets.
**Does the function belong permanently to one organization?** Not necessarily. Responsibilities can transfer, be delegated or be shared; historical relationships need evidence and dates.
**Can function identifiers be translated?** No. Translate display labels or explanatory scope notes while protecting stable technical identifiers.
**How does EAC-F differ from EAD and EAC-CPF?** EAC-F describes activities and functions; EAD describes records; EAC-CPF describes people and bodies.
**Is an XML-valid function record historically correct?** Not necessarily. Structural validation must be paired with appraisal of evidence and the translated assertions.
Further reading and related guides
Official EAC-F 1.0 release and schemas: https://standards.openpreservation.org/eaf/v1.0.0
Society of American Archivists EAS Suite and Tag Libraries: https://saa-sdt.github.io/EAS-TagLibraries/
EAC-F XML Guide: https://saa-sdt.github.io/EAS-Best-Practices/docs/eas-suite/eac-f/eac-f-xml-guide.html
Related eduKateSG EAD4 guide: https://edukatesg.com/2026/10/30/translate-like-a-pro-3450-ead4-archival-finding-aids-hierarchy-identifiers-access-digital-objects/
Related eduKateSG EAC-CPF3 guide: https://edukatesg.com/2026/10/30/translate-like-a-pro-3460-eac-cpf-3-creator-authority-parallel-names-relations-identity/
Final thought
The central translation discipline is simple to state but demanding to practice: a public record explains what survives, a creator authority explains who participated, and a function record explains why the activity generated evidence. When these relationships remain intact across languages, archives become more intelligible without losing their history.