Last modified: 2014-10-19 17:52:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T54156, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52156 - History for annotations
History for annotations
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Annotator (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: richa jain
:
Depends on:
Blocks: 54246
  Show dependency treegraph
 
Reported: 2013-07-27 19:29 UTC by Matthew Flaschen
Modified: 2014-10-19 17:52 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Matthew Flaschen 2013-07-27 19:29:39 UTC
Since annotations allow editing, they should also track history.  This will require schema changes in the extension, and investigation of how core handles this.

Once the history is tracked, there should be a way to display it.
Comment 1 Matthew Flaschen 2013-08-18 21:45:04 UTC
We should discuss possible approaches for this before starting.  It may make sense to switch to ContentHandler before doing this.
Comment 2 Tyler Romeo 2013-08-19 16:07:58 UTC
Well we have two options:

1) Use ContentHandler, store the contents of annotations in some namespace and use MediaWiki's built-in history.

2) Make an annotator_revision and annotator_text file to keep track of history like MW does for pages.
Comment 3 Matthew Flaschen 2013-08-19 18:32:36 UTC
Yeah, I now lean towards supporting ContentHandler, similar to what you suggested earlier (https://bugzilla.wikimedia.org/show_bug.cgi?id=46440#c34).

It needs some more research, and there are questions like performance, how to name the annotation pages (same technique as Wikibase?).  However, all of this should probably be solvable, and saves re-implementing history, etc.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links