How can you translate Sakai course Lessons without losing linked files, quizzes, discussion activities or the structure students need to navigate? Sakai LMS localization brings together the Lessons tool, Resources, Tests & Quizzes, assignments and site-level course configuration. A readable translated page does not guarantee that every link or assessment survives a course export and import. The proper aim is to preserve the learner’s pathway as well as the language.
This Sakai Lessons and course export translation guide explains how to handle top-level lesson pages, IMS Common Cartridge packages, referenced activities, resource files, question banks, accessible content and site imports. It serves international universities, academic course teams, LMS administrators, multilingual instructional designers and professional translators. The examples are fictional; the checklists are suitable for adapting to a real institution’s supported Sakai version.
Sakai’s community documentation explains that the Lessons tool can export course content in IMS Common Cartridge format, including certain linked activities and resources. It also notes significant boundaries: student-created pages are not included in that export, exports begin from a top-level Lessons page, and instructors may need different package options for different destination systems. That makes localization a matter of mapping content coverage and dependencies, not just translating a ZIP package’s visible text.
The learning site is larger than a Lessons page
Sakai sites can include Lessons, Resources, Assignments, Tests & Quizzes, Forums, calendar information and other tools. The text students read may be held in one tool while the activity they must complete lives in another. The translator should map the source site’s structure and track links between tools. A lesson title might translate cleanly but still point to a quiz whose instructions and answer options remain untranslated. Review the full learning task and designate an academic owner for each linked resource.
Understand the Common Cartridge export boundary
The community documentation describes exporting Lessons content through an Export CC option when the instructor is on a top-level Lessons page. Certain linked activities and resources may accompany the package, but the export has specified exclusions and options. A package is not necessarily a complete backup of every piece of site data. Before translation, inventory what was included, what was omitted and what requires a separate authorized export. Do not infer that missing learner-created content is a translation error; it may be intentionally outside the export.
Preserve resources and link relationships
An instructional page may point to PDF handouts, external URLs, discussion topics, assignments and assessments. The surrounding words can be translated, but relative file paths, resource identifiers and access rules must still lead students to the intended item. When creating an approved language variant, use the supported Sakai interface and maintain a clear mapping between source and target resources. Avoid changing technical paths for cosmetic reasons. Inspect the package structure before import and confirm link behavior after import rather than relying only on a successful export message.
Distinguish questions from answer data
Tests & Quizzes content is especially sensitive because a language change can alter what counts as a correct answer. Technical question identifiers, scoring rules, randomization and question-bank membership should not change during editorial revision. Translate stems, choices, hints and feedback with subject-expert review, using representative fictional test attempts. Ensure that negation, units and condition words survive. If a question pool is exported separately, keep track of which questions the course requires and what the imported system actually recognizes.
A site import is not just another document copy
The target Sakai site may already contain teaching content and gradebook settings. Importing from a source site or package can have different effects depending on tool support and instructor choices. Decide whether the destination is empty or populated and use the institution’s documented import or merge procedures. The translator should not choose a destructive replacement option just to deliver new wording. Test in a sandbox course and preserve historical student evidence. A multilingual edition must not erase existing material or create misleading duplicate assessments.
Make the translated learning journey accessible
Sakai Lessons may contain rich text, embedded files and links, each requiring appropriate accessibility review. Use semantic headings, descriptive link text, accessible tables, meaningful image descriptions and accurate captions. For global courses, inspect date and timezone wording, mathematical notation and right-to-left text where applicable. A final student-role walkthrough should confirm that the learner can locate a lesson, use its resources, complete the linked activity and understand the same expectations as the source-language cohort.
Twenty Sakai localization decisions: lesson structure, packages and linked assessments
1. Identify the right Sakai site
A university runs successive offerings of the same subject under the same course title. The Sakai site that contains the current cohort’s assignments may differ from last term’s site, even if lesson headings look identical. Establish the authorized source site, academic term and destination before localizing. Record who owns each lesson and assessment, and do not assume that a translated site title identifies the correct technical context. Test a link from the new student’s account and check that enrollment, relevant files and schedule belong to the intended course.
2. Map Lessons and other tools
A Sakai course can use Lessons pages to lead students into Resources, Assignments, Forums and Tests & Quizzes. These tools may store different parts of the learning journey. Translating a Lessons paragraph does not automatically translate a linked quiz or the teacher’s feedback. Build a map of every referenced tool and its responsible owner. The reviewer should be able to trace a task from the page where it is introduced to the activity where it is completed. This prevents a localized heading from concealing an inaccessible or source-language-only assessment.
3. Export from a top-level Lessons page
Sakai community guidance says the Lessons export workflow is initiated from a top-level page. A teacher who is browsing a nested page may not be working at the correct export scope. Explain the route accurately in the localized instructional guide, but let an authorized instructor perform the export. Record the scope of the selected page and the list of included resources. After exporting, inspect the package content instead of assuming that every part of the site has been captured. The word export describes a particular tool operation, not a universal course backup.
4. Know the Common Cartridge boundary
The Sakai Lessons tool can export content in IMS Common Cartridge format, including linked resources and certain activities. That does not mean the resulting file holds every user record, grade or private document in the site. Explain the export’s intended scope to course owners and language reviewers. Inventory the lessons, files, assignment links, discussion references and assessment resources actually present in the package. If an item is missing, determine whether it lies outside the supported scope rather than inventing a file or altering identifiers. Technical completeness must be established through inspection.
5. Do not claim Student Pages are included
The community documentation explicitly notes that pages created by students through the Student Pages tool are excluded from the Lessons export. A translated handbook that says all student contributions are included would be misleading. State the limitation precisely and ask the instructor to identify any work requiring a separately authorized preservation route. Student-created pages may also involve personal information and copyright considerations. Do not copy them into a language package without an appropriate reason and permissions. The export should be described by what it actually contains, not what a reader hopes it contains.
6. Record the supported package option
The Sakai guidance distinguishes export options intended for different destination learning platforms, including options for Moodle or Blackboard and an alternative for Canvas. A translator should not treat these as interchangeable labels. Ask the LMS administrator to select the appropriate option for the actual destination and supported versions. Preserve technical manifest details and package relationships during language work. Test the exported file in a sandbox destination and confirm the desired learning objects appear. A package accepted by one system may still lose useful content in another, so destination-specific validation matters.
7. Understand linked assignments
A Lessons page says submit the fieldwork report and links to the Assignments tool. The displayed phrase may be localized, but the assignment object’s due date, file requirements and grading are configured separately. Ask the instructor to verify the intended learner action, then translate the link label and instructional explanation. Do not invent a new submission object by copying the link text. Test with a fictional student who follows the lesson and completes a harmless sample submission. The same deadline and receipt should be understandable in every approved language.
8. Preserve discussion-topic relationships
A language-learning course directs learners from a Lessons page to a forum discussion. If the translated link points to a general forum rather than the intended thread, the task changes even though the surrounding sentence looks natural. Maintain the correct target reference and translate the discussion prompt where its actual owner permits. Explain expectations for evidence, turn-taking and respectful critique in appropriate local language. Use a test student to follow the route and write a sample reply. The course should preserve the same topic and participation rules across editions.
9. Distinguish Files from URL links
A Lessons item may refer to a file in Resources or an external URL. These are different dependencies and may have different access, download and licensing implications. Translate visible labels with their context, then verify what the link actually opens. A PDF held in Sakai may require an approved language variant, while an external journal site may already have an official translation. Do not rename technical resource paths for cosmetic consistency. Test from a student account without privileged credentials and check that the resource version and rights are appropriate.
10. Preserve file structure and references
A course package may include relative paths, resource names and references used by an import process. A translator who replaces filenames with target-language phrases can break those references even while improving readability. Treat technical paths and identifiers as controlled data. Create friendly display wording in supported fields and update resources through authorized interfaces when a separate file edition is required. Compare the packaged manifest or resource list before and after the change. Import into a safe test site and open every high-stakes file, image and internal link.
11. Check resource permissions
A teacher includes a linked article in Lessons that only teaching staff can access because of permissions on its source location. An instructor preview may open it successfully, giving a false sense that the localized course is ready. Test the resource as an enrolled student who does not have administrative access. Confirm whether the content may be copied, translated or redistributed under its license. If the approved target-language material needs a new location, ask the site owner to configure it. Accurate prose cannot compensate for missing permissions.
12. Keep course navigation meaningful
The source site has a module called Evidence and Interpretation followed by a nested page on source criticism. A literal heading may be too vague in the target language to show the relationship. Translate titles so students can infer their instructional role while keeping the nested structure unchanged. When a title must be shortened for the side menu, retain the full concept in the lesson heading. Test with keyboard navigation and a mobile screen. A learner should be able to locate the next activity without relying on pictures, colour or instructor guidance.
13. Translate rich-text semantics
A Sakai Lessons page contains numbered instructions, headings, a data table and links to two supporting documents. Reformatting every part as a single paragraph destroys the structure the student uses to understand the procedure. Preserve true headings, list elements, accessible table headers and meaningful link text when the editor supports them. Translate mathematical symbols and reference labels with care. Review in the rendered student view as well as in the authoring interface. Where a screen reader is used, confirm that the document can be navigated by topic and step.
14. Translate alternative text properly
A diagram of the water cycle includes arrows that explain evaporation, condensation and precipitation. Its English alternative text may carry more scientific meaning than the visible caption. A language edition should convey the same relationships to students who cannot see the image. Write target-language alt text that describes the relevant process rather than decorative appearance, and keep technical terminology consistent with the lesson. Ask a science teacher to check the description against the figure. Avoid placing an answer to a test question inside alternative text when the original activity requires students to infer it.
15. Manage subtitles and recordings
A Lessons page embeds a filmed demonstration with source-language speech, on-screen labels and a timed safety warning. Translating only the page heading does not create a usable target-language video. Review caption files, transcripts, visual overlays, media permissions and the player controls separately. Preserve scientific units and the order of actions in time-aligned captions. Test the video with sound muted and check the warning appears before the relevant action. If no complete target-language alternative exists, describe coverage accurately rather than promising that all content has been translated.
16. Protect question identities
The Tests & Quizzes tool may use identifiers and structured question data that support grading and item-bank reuse. Such identifiers should not be translated as ordinary words. Translate question stems, options, hints and feedback with the instructor while preserving answer mapping and scoring data. A negative word, measurement or choice distinction can change the correct answer. Use fictional attempts to compare how the source and target questions behave. Never rewrite technical records merely because a question identifier looks linguistically awkward in an export.
17. Treat question pools deliberately
Sakai’s Lessons export guidance discusses an option to include accessible question pools as a question bank when relevant. A quiz may refer to pooled questions that are not obvious from the lesson page itself. The instructor should verify which pools the target lesson needs and whether the chosen export option includes them. Preserve pool identities and scoring logic, then test a representative imported assessment. Translating a few displayed sample questions is not enough when randomized items may appear for different students. The entire assessed set needs academic validation.
18. Understand QTI as a separate layer
Sakai assessments may use QTI export and import routes. QTI is a structured assessment interchange format, not a general-purpose text file. The translator must distinguish visible question content from response processing, identifiers, outcome declarations and scoring logic. For this Sakai guide, the concern is the platform’s use of the package, not a repeat of the general QTI standard. Ask the test owner to confirm the exported questions, their supported import formats and the final behavior in the destination Sakai site. Verify answers using safe test submissions.
19. Verify mathematical notation
An algebra question includes exponents, inequality signs, negative numbers and a decimal separator. The target-language sentence can be fluent while the mathematical expression has been altered by text direction, font substitution or localization conventions. Keep values, symbols and units correct, and confirm how the destination quiz accepts numeric answers. Test significant figures and boundary cases, not just a whole-number example. For right-to-left contexts, inspect both rendered and copied representations of formulas. Have a subject expert confirm that both language groups would solve the same problem.
20. Review grading and feedback as separate content
A student sees a submitted assignment, a score and a teacher comment at different stages. The translated Lessons page should not call all three complete. Confirm how the linked Sakai tool represents submission, marking and result visibility. Translate feedback directions only after checking the actual workflow, and preserve grades and learner records as protected evidence. Use fictional submissions and scores during review. A message asking for resubmission must retain any deadline or permission condition. Learners should know whether they have successfully submitted, whether work has been evaluated and what they must do next.
Twenty more Sakai localization decisions: import behavior, accessibility and governance
21. Keep assessment instructions equivalent
A fieldwork assignment instructs students to justify their choice of sampling site using three criteria. In another language, justify can be weakened to state, leaving the target group with an apparently easier task. Review the intended cognitive demand with the teacher, including length, evidence and referencing standards. Use fictional sample work to check whether the same response would satisfy each version. The linked Sakai assessment may enforce submission settings separately, so preserve the technical rules as well. Educational equivalence requires the task and the mechanism to agree.
22. Distinguish due dates from access windows
A Sakai assignment opens on Monday, is due Thursday and accepts late work according to an institutional rule. A translated Lessons introduction that says closes Thursday may incorrectly imply there is no late-submission route. Verify the actual configuration with the course owner, then use precise language for availability, due time and any final cutoff. Explain the timezone to international learners, especially when a numeric date could be ambiguous. Test the activity with appropriate roles near the relevant moments. Do not alter platform timestamps as part of translation.
23. Treat separate site imports carefully
Sakai Site Info may provide ways to import content from another site, and the effect can depend on whether the destination already contains materials. A language team should not choose a replace option simply because the new translation needs to appear. Have an authorized instructor decide the import strategy after reviewing the institution’s supported version and backup policy. Use a sandbox destination and inspect which tools and objects are included. Preserve existing grading records and student submissions. A successful package upload is not evidence that an existing course remained safe.
24. Distinguish replace from merge
A source-to-destination operation might replace selected existing information or merge material into a site. These words describe potentially different technical actions. Translate the warning text accurately and request explicit course-owner authorization for the chosen operation. Do not simplify a caution to a generic continue button description. Before using any destructive option, document the destination’s existing content and recovery route. After a trial import, compare lessons, assignments, Resources and grades against the expected result. In an educational system, preserving students’ work is more important than making an import convenient.
25. Check tool availability on both sites
An imported lesson refers to an activity from a tool that the destination Sakai site does not enable. The translated heading may appear normally while the target activity is missing. Ask the administrator to inventory the active tools at source and destination before import. If a tool is unsupported, obtain an academic decision about an equivalent activity rather than silently replacing it with a different task. Test every linked item in the intended student view. Record which materials were migrated, which require separate work and which cannot be delivered yet.
26. Preserve assignment identities
A newly imported course may create a separate assignment object from the one used in the source. The source ID and new target ID may differ legitimately. Translators should not manufacture identical IDs or infer equivalence from display titles. Maintain a documented mapping of source activity, destination activity, course term and language edition. Check actual due dates, file requirements and grading settings through an instructor account. Then follow the student-facing link and submit a harmless sample. The mapping should show that the learner reaches the correct newly authorized task.
27. Validate external URL destinations
A lesson links to a digital library that has different paths for its English and Spanish editions. Replacing the visible label does not ensure that the target page uses the equivalent source, edition or dataset. Verify the institution-approved URL, access rights, publication date and cited section. If an official target-language text is unavailable, disclose that limitation rather than presenting an unofficial summary as the primary reference. Test links outside privileged campus sessions. The student should be able to retrieve the same scholarly evidence and identify its provenance.
28. Localize site navigation without losing hierarchy
A Sakai site contains a first-week orientation, a module overview and nested lesson pages. Target-language labels may grow significantly longer and become truncated in navigation. Use clear, concise headings that retain the distinguishing concept, and keep the original instructional hierarchy. Avoid moving pages to make a translation fit without a teacher’s decision, because sequence can communicate prerequisites. Check breadcrumbs, side navigation and internal links at mobile widths and high zoom. A learner should know where they are and how to return to the relevant parent lesson.
29. Preserve glossary distinctions
A sociology course uses evidence, observation, data and claim as related but different concepts. A translator who uses one convenient target word for all four may damage the student’s conceptual model. Ask the faculty member to define each term, create approved examples and record context-specific variants. Use the glossary consistently in course pages, worksheets, rubric descriptions and discussion prompts. Test a few sentences where the concepts appear together. The goal is not mechanical word replacement but clearer recognition of the distinctions the student must learn.
30. Keep Rubric language distinct from grade values
An instructor publishes descriptions of performance levels next to graded assignments. The target-language wording should retain what differentiates adequate, strong and exceptional evidence, while numeric scores and thresholds remain controlled by the assessment system. Use fictional graded responses to calibrate the language with the teacher. Do not claim that a local school grading label automatically means the same qualification as the source. A multilingual student should understand why a response earned a particular result and what higher-quality performance would have required.
31. Protect learner-generated content
Students may create pages or other material containing personal information or their own intellectual property. The Lessons export’s stated exclusion of Student Pages is a relevant limit, not a defect to repair by indiscriminate copying. If learner material genuinely requires migration or translation, obtain the necessary institutional authority, privacy review and rights clearance. Prefer fictional examples for testing platform behavior. Confirm that translation packages, screenshots and vendor handoffs contain no unintended student IDs, submissions or private feedback. A course export should not become a workaround for privacy rules.
32. Audit ZIP package integrity
An IMS Common Cartridge file is a structured package, not a loose collection of documents to rename at will. It may contain manifest references, directories and assets that must remain consistent. The authorized technical team should validate package structure, check for missing resources and compare the expected course inventory before importing. Language reviewers should not edit machine-readable identifiers in an attempt to improve file names. Import into a sandbox site and open each critical activity. If the package is rejected, diagnose format and dependency errors separately from linguistic quality.
33. Test import results rather than success messages
A system may report that a course import completed without guaranteeing every source object behaves identically in the destination. A quiz bank might be incomplete, a file permission may differ or a link may point to an inaccessible service. Review a structured inventory of source and target materials, then perform student tasks from start to finish. Record expected behavior, observed behavior and the owner of any defect. Do not mark the language edition ready simply because the import status indicates success. Functional equivalence must be demonstrated in actual teaching use.
34. Coordinate transcript and caption rights
A recorded lecture may belong to a publisher or a guest lecturer who permits viewing but not redistribution of edited subtitle files. Translation feasibility does not automatically grant permission. Check licenses, attribution and intended access before preparing a new media variant. When an approved transcript is available, preserve quoted terminology and any qualification about uncertainty. Test time-aligned captions and screen-reader control names. If a full translation cannot be lawfully provided, explain which language resources remain available. Avoid making promises that would mislead students about accessible support.
35. Handle different reading directions
A target-language lesson using Arabic or Hebrew embeds Latin filenames, web addresses, formulas and numbered steps. Correct text can appear visually reordered, changing the apparent mathematical relationship or making a filename difficult to copy. Use supported bidirectional rendering controls and test mixed-script content carefully. Preserve values, negative signs, operators and URL characters. Ask a bilingual subject expert to inspect both the rendered presentation and the underlying copied text. A layout fix must not change a scientific expression or an assessment answer.
36. Maintain numerical and date conventions
A global course uses percentages, significant figures, measurement units and dates. Local display conventions may change punctuation, but they must not change a measurement, test duration or submission instant. Confirm the institution’s notation and time-zone policies before translating explanations. Where a quiz expects a particular input format, test the target-language learner’s ability to submit a correct value. Distinguish an inclusive range from a strict inequality and a recommendation from a deadline. This prevents language formatting from becoming a hidden academic disadvantage.
37. Review source versions and term refreshes
A course author updates a laboratory safety paragraph after the target-language package was exported. Without version tracking, the imported translation may carry obsolete advice. Record the source revision date, localized object, academic approval and last test of affected links. Route consequential changes for new translation and functional verification. Maintain an explicit change log for assignments, Resources, question banks and policy references. When copying into a later term, test the current teaching sequence instead of treating an earlier successful import as permanent proof of accuracy.
38. Distinguish accessibility claims from reality
A target-language site is described as fully accessible, but its key diagram has no meaningful alternative and an embedded video lacks captions for the final procedure. Accessibility is not a decorative label. Review each instructional component against its actual function, including headings, keyboard interaction, media alternatives and readable tables. Have a learner who uses assistive technology test the key pathway where possible. State limitations truthfully and assign repairs to an authorized owner. The student should receive the same core learning opportunity, not merely a translated welcome message.
39. Assign release responsibility
A course translation passes linguistic review, yet an imported assessment sends students to the wrong quiz. The language team should not publish the course as complete without platform-owner approval. Require named signoff for educational meaning, technical dependencies, permissions, accessibility and assessment behavior. A final learner-role test should start from the module outline, reach the linked activity, complete it and interpret the result. Record any known exceptions and how they will be handled. This protects students and prevents a formatting success from being mistaken for a reliable course release.
40. Prepare a safe correction and rollback plan
After deployment, a teacher discovers that the target-language instructions omit a prohibition on collaborating during an individual assessment. That omission may affect academic integrity and student decisions. Record the affected version, obtain teacher approval for corrected wording and communicate the material correction transparently. Repair the language without altering historical submissions, grades or course identities. Test the corrected link and learner view, then update the source-to-target map. A good maintenance plan allows a course to improve without erasing the evidence of what students were originally told.
Worked example: translating and importing a Sakai fieldwork course
Consider a fictional twelve-week environmental fieldwork course taught by an international university. Its Sakai site uses Lessons pages to guide students to Resources, a forum discussion and a Tests & Quizzes assessment. An instructor wants a Spanish-language edition for the next academic term. The source Lessons export is prepared from a top-level page using the institution’s supported Common Cartridge route. The team first checks which lessons, linked resources and activities appear in the package. It notices that some question-bank content requires attention, a video has incomplete captions and an assignment refers to a term-specific deadline. A successful translation of the lesson headings alone would not solve these problems.
The course owner approves translated terminology for transects, replicates, sampling uncertainty and field safety. The assessment specialist checks the question bank and answer logic, while the accessibility reviewer prepares a meaningful description of a data figure. Technical staff import the package into an empty test site, verify linked activities, confirm permissions and inspect any import warnings. A fictional learner then follows the new lesson sequence, downloads the intended resource, posts to the discussion and completes a noncredit quiz. The professor confirms that the same task and evidence are required. Only then does the team make the new course available to its intended cohort.
Four-week Sakai localization and validation plan
Week 1 — Inventory the source site and package scope
Record the Sakai version, active tools, Lessons hierarchy, resource dependencies, linked assessments, student-data boundaries and intended destination. Confirm the supported top-level export route and the correct package option. Obtain academic and technical owners for decisions.
Week 2 — Translate and validate content meaning
Review headings, explanatory prose, Resources, assessment language, captions, alternative text and terminology. Ensure no question, safety instruction or grading condition changes meaning. Preserve technical paths, package references and identifiers as controlled data.
Week 3 — Import safely and test activities
Use a sandbox site to inspect the IMS Common Cartridge import and any separately migrated content. Validate link destinations, file availability, question banks, permissions, navigation, timezones and accessible presentation. Perform complete student journeys using fictional accounts.
Week 4 — Obtain release approval and maintenance ownership
Secure instructor and administrator signoff for academic equivalence and functional behavior. Document the source package version, resolved limitations and rollback route. Plan updates when the source site, policy, Sakai version or related resources change.
Frequently asked questions
Does a Sakai Lessons export contain everything in a course?
No. It has a documented scope and exclusions. Inventory linked activities, files and other tools instead of assuming a complete site backup.
Are pages created through Student Pages included?
The cited Sakai community guide states that Student Pages are not included in the Lessons export. Separate handling requires appropriate authorization.
Why does export have different options for target platforms?
Package compatibility differs. Use the option recommended for the intended destination and test imported learning objects in that environment.
Should a translator edit ZIP manifests or resource identifiers?
Not as ordinary prose. Preserve package and path integrity, using supported tools for approved resource changes.
Can quiz questions be localized independently of scoring logic?
Visible question language can be translated with academic review, while response processing, identity and scores must remain controlled and validated.
How do we know the localized Sakai course works?
The intended learner can navigate, access files, understand tasks, use linked tools and complete a safe test activity under equivalent rules.
Official documentation and related translation articles
Use Sakai Community Documentation: How do I export Lessons content? for the Lessons export scope, Student Pages exclusion and destination-specific options. The Sakai 25 export guide from Pacific Lutheran University describes related export practices for Lessons, Resources and Tests & Quizzes. Related eduKateSG articles include Common Cartridge interoperability, QTI 3 assessment localization, Open edX OLX course exports and the Translate Like a Pro series index. This guide focuses on the actual Sakai Lessons and site-import workflow rather than the abstract package specification.