Concept for a new Interface to WikiDocs Transclusion
1962 clearly shows that the current interface to WikiDocs is too cumbersome. This page serves as a place to develop an interface which is helpful to WikiDocsModerators. Rob has already stated, that he would work on this, if it were clear, what exactly he has to implement. So here we go:
Widget in MoinMoin
dmppanda suggested the following:
Ok... So:
1. Lack of manpower is just in every MB aspect, right? I don't think that's an issue to consider: either the transclusion system has benefits, or it has not.
2. The "extra work" needed to maintain wikidocs. Certainly true. Reviewing changes on a wiki page:
be mailed of a change in a wikipage
review the change, either do nothing or fix
Additional work if transcluded:
open up a musicbrainz page
login
check the transclusion page for the wiki page
go back to the wiki page, errr what revision was that?
go back to the main site transclusion page and check what revision was that
go back to the wiki page
click get info
diff it to the transcluded revision
review, go back to the website, update the transclusion table
double check you didn't do mistake, as there are no safeguard
Painful. Ideally, it would be *a lot more easy* if we had a very simple additional toolbar on top of the wiki page, that would display (for transclusion editors) the current transclusion status, and allow him to update it.
Something like (ASCII art!):
|------------------------------- | This page is transcluded at version X. | Display a diff between transcluded and current revision: [Diff button]. | Update the transclusion to revision: |_| [Update button]. | Remove that page from the transclusion table: [Remove]. |-------------------------------
or
|------------------------------- | This page is not transcluded! It also lacks proper ACLs. |-------------------------------
or
|------------------------------- | This page is not transcluded! It has ACLs. | Transclude it now to revision: [Go] |-------------------------------
I believe such a new transclusion interface would reduce the "additional work" to almost zero.
I have no idea how much dev work that represent (though I guess it would require migrating the transclusion privs from main server to wiki ACLs).
Plugins
DonRedman suggests to build something which feels integrated, but which consists entirely of plugins and interlinked stuff. I believe that a lot can be achieved if
there is a page on MusicBrainzServer that shows all the relevant stuff to transclude a single page. You can construct the url out of the wiki page name. Therefore Moin can call it.
There is a plugin for Moin that links to this page
(If you want to go fancy, you use XML on the server and the plugin renders that in an appropriate way. But that's an extra bonus.)
Concrete Example
The Moin theme is patched so that it includes a link next to "get info" that says "transclusion status". That link points to http://musicbrainz.org/edit/wikitransclusion/PageName.html.
That page shows the transclusion details for that wiki page. I believe you need:
current revision of wiki page
current transcluded revision
current acl state
link to page history
link to diff between current rev and transcluded rev
link to (or included?) a search for transclusion edits (in the MB edit system) for this wiki page (which don't run out of time)
an of course links to the wiki page and the WikiDocs page
Additionally, if you are logged into the MB server and are transclusion editor, you see the following controls:
Update to rev #xxx preset to the current revision
remove from transclusion
edit note field (so that editors can leave comments to ease collaboration)
This page would be the dashboard for transclusion. It should be reached with one click from every situation in which you might want to work on the transclusion:
from a WikiDocsPage
from a WikiPage
from a diff mail from Moin
The RecentChanges page
That would mean to patch the RecentChanges macro to include a linkt to the 'WikiDocsDashboard', which should be a reasonably simple thing to do.