Page MenuHomePhabricator

Include incoming redirects in JSON representation of entities (tracking)
Open, HighPublic

Description

Incoming redirects act as alias-IDs for entities. They should be available in the entity's JSON representation, at least in some cases:

  • internal (DB): no
  • API output: optional (T98317)
  • JSON dumps: not in entity, but as separate non-entity entries (T98320)
  • EntityData: always (or at least per default) (T98322)

Caveat: Structural inconsistency between dumps and EntityData. For JSON dumps, it's more sensible (and performant) to have redirects as separate entries, while for EntityData, we don't really have a place outside the entity itself where we could put the redirect info.

Event Timeline

daniel raised the priority of this task from to High.
daniel updated the task description. (Show Details)
daniel added subscribers: Addshore, Wikidata-bugs, Bene and 3 others.
daniel renamed this task from Include all incoming redirects in JSON representation of entities to Include incoming redirects in JSON representation of entities (tracking).May 6 2015, 12:40 PM
daniel updated the task description. (Show Details)
daniel added a project: Tracking-Neverending.
daniel set Security to None.

This blocks "WikibaseDataModelSerialization with what we do with WikibaseLib" and although we have totally removed the Lib Serialization I would not consider this task complete in regards to WikibaseDataModelSerialization.

Again we are still doing this as a bit of a hack shoving the info in after we have the serialization, but no in the Serialization component itself!