Page MenuHomePhabricator

Have ContentTranslation segment IDs for storage
Closed, DeclinedPublic

Description

Context: Segments need to have stable, hash-based IDs that are robust to article update.

Narrative: As a developer, I can calculate the segment ID based on the article title, segment content and adjacent segments.

Acceptance Criteria:

  • Segments in different block structure, but with the same content and adjacent segments, have the same ID.
  • A document explains and justifies our segment ID choices

Event Timeline

Amire80 raised the priority of this task from to Needs Triage.Feb 20 2015, 4:16 PM
Amire80 added a subscriber: Amire80.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 20 2015, 4:16 PM
Arrbee updated the task description. (Show Details)Feb 24 2015, 5:55 AM
Arrbee set Security to None.
Amire80 triaged this task as Normal priority.Feb 26 2015, 8:27 AM
Amire80 lowered the priority of this task from Normal to Low.Jul 3 2015, 2:46 PM
Amire80 edited projects, added ContentTranslation-Release6; removed Language-Team.
Amire80 moved this task from Needs Triage to CX6 on the ContentTranslation board.
Pginer-WMF moved this task from CX6 to CX7 on the ContentTranslation board.Jul 21 2015, 4:21 PM
Amire80 moved this task from CX7 to CX8 on the ContentTranslation board.Jan 24 2016, 10:31 PM
Amire80 updated the task description. (Show Details)Jan 27 2016, 9:26 AM

This one was migrated from Mingle. Is it still in line with the current state of segmentation and parallel corpora work? Or is it becoming irrelevant?

Amire80 closed this task as Declined.Apr 20 2016, 9:30 AM

This is done differently in the final parallel corpora config.