💡[Feature]: Implement admin workflow support for translated articles submitted from the app.

[SB2318]

Is there an existing issue for this?

• I have searched the existing issues

Feature Description

Currently, users can create translation drafts from existing articles, and the frontend now includes source article + language metadata in the submit payload. Admin/backend workflows should use this metadata to properly review, link, and manage translated articles without treating them as unrelated new submissions.

Requirements

Translation Metadata Handling

• Detect article submissions containing:
  • sourceArticleId
  • sourceLanguage
  • targetLanguage

Admin Review Enhancements

• Display translation-specific metadata in admin panel:
  • Original article reference
  • Source language
  • Target language
• Show clear indicator that submission is a translation, not an original article.

Article Linking

• Link approved translated article to original/source article.
• Maintain translation relationships for future retrieval/grouping.

Validation Rules

• Prevent translated submissions from replacing or mutating original article content.
• Ensure source article exists before approving translation.

Future Compatibility

• Support listing all available translations under a source article.
• Allow admins to navigate between original article and translations.

Use Case

Use Cases

1. Multilingual Content Expansion

A contributor reads an article in one language and creates a translated version for users who prefer another language.

Example:

• Original article: English
• Translation: Bengali / Hindi / Spanish

Admin should be able to review the translated content while preserving the relationship with the original article.

---

2. Source Traceability

Admins need to know which article a translation came from to:

• verify translation accuracy
• compare source and translated versions
• prevent unrelated or duplicate submissions

Without source linking, translations appear like completely new articles.

---

3. Translation Management

Multiple translations may exist for a single article.

Example:

• Article A
  • Bengali translation
  • Hindi translation
  • Tamil translation

Admins should be able to manage all translations under one source article.

Benefits

Benefits

Better Content Organization

• Groups original articles and translations together
• Avoids fragmented duplicate content

Improved Admin Review Workflow

• Faster moderation by showing source article context
• Easier validation of translated submissions

Data Integrity

• Prevents translations from overwriting original articles
• Maintains original article as source of truth

Future Feature Enablement

Enables future capabilities such as:

• "Available in other languages" section on article pages
• Translation analytics
• Translation update sync/version tracking
• Language-based discovery and recommendations

Better Contributor Experience

Contributors can translate existing content instead of recreating articles from scratch.

Add ScreenShots

No response

Priority

High

Record

• I have read the Contributing Guidelines
• I'm a GSSOC'24 contributor
• I'm a IEEE IGDTUW contributor
• I want to work on this issue

[github-actions]

Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊