Multilingual research lab on one Lattuce household
Run one Lattuce household for a lab that publishes in multiple languages — collaborative translation locales, shared TM, and honest scope limits.
One household on lattuce.app can serve researchers working in several languages — English papers, Malay abstracts, Arabic supplementary text — without replacing your team wiki or project-management hub.
This guide covers translation workflow at household scale, not enterprise directory features.
Audience split
| Who | Uses Lattuce for… |
|---|---|
| Graduate students | Writer + Translate mode on their papers |
| Bilingual staff | Translation editor on assigned projects |
| Household admin | Invites, billing, translation account linking |
| Everyone else | May still use Notion for ops — alongside Notion |
Workflow overview
- Household shares one library and quota on lattuce.app.
- Each paper can link a translation project per target locale.
- Translation memory accumulates across segments — lab terminology gets consistent.
- Authors export Word per locale after section approval.
Platform primer: Collaborative translation on Lattuce.
Deployment model
| Concept | Meaning |
|---|---|
| Household | Billing + data boundary — lab, family, or research group account |
| Not org tenancy | No university-wide SSO directory in v1 |
| Cloud product | lattuce.app — public blog does not market DIY install |
Malaysian labs often choose cloud households first — see Data residency for university labs.
Locale pairs beyond EN↔MS
EN↔MS is the best-documented example (thesis + journal culture in Malaysia). The same machinery supports other pairs when configured:
| Example pair | Typical use in lab |
|---|---|
| EN ↔ MS | Thesis chapters + abstrak |
| EN ↔ AR | Islamic studies supplementary text |
| EN ↔ ZH | Joint publications with CN co-authors |
Lattuce does not ship “automatic perfect translation” marketing — humans approve segments; TM and AI assist.
Shared translation memory
| Benefit | How |
|---|---|
| Consistent “materials and methods” | TM suggests prior approved phrasing |
| Locked glossary | Lab coinages do not drift between students |
| Faster second paper | Reuse abstract patterns from first submission |
Memory is scoped to translation projects your household owns — not a global consumer TM pool.
Optional semantic suggester features may use embeddings on your account — operator detail stays in /help, not this post.
Household checklist
| Task | Owner |
|---|---|
| Invite members with correct emails | Admin |
| Link personal translation accounts (no shared passwords) | Each translator |
| Add BYOK keys if AI assist is required | Admin or PI — BYOK guide |
| Agree EN authoring + target locales per paper | PI |
| Export Word for faculty DMS | Student |
Week-one smoke test: Household admin's first week.
Related reading
- Collaborative translation on Lattuce
- Translate a thesis chapter
- Bilingual journal abstracts
- Why Lattuce is not trying to replace Notion
Bahasa Melayu: Makmal penyelidikan pelbagai bahasa pada satu isi rumah Lattuce