Thread:User talk:Aaron Schulz/Mediawiki as a CMS

Hi Mr Schulz

I'm Dr Jean-Guy Levreault, in Québec, I'm a clinician seeing patient but also in the medical team of a clinical laboratory. We have procedures, prodedureS with a capital S because we have so many of them Maintaning the body of text as been challenging

We are using a homemade system that tracks versions of text, list of required reading, a log of done readings, scheduled documents updates

I've created it and it works fine but, but...


 * Editing is restricted to assigned reviewers
 * No support for content re-use
 * No statistics

I think mediawiki can fill those missing requirements, mediawiki was build upon democratic editing, we need that. But we also need structured readings and logs

So here is my problem (finally got to the point)

Versionning of templates in a page

With the "freeze" option the templates are loaded at the version approved, that would be the ideal configuration, but there is no special page that gather documents with templates in need of reviewing. In case of multiple templates updating there is no way to accept one update and leave the rest unchanged. I also don't know how to keep records of the update, if I understand correctly your extensions does not create a new version of the container page but simply updates the database for the new templates id.

I understand completely that Wikipedia is living in a different ecology than our future wiki, they have no "slow" time to do expensive database update as we do

Do I understand the current state well? Do you have plans for a new version of FlaggedRevs, will it change the way it handles templates updates?

Thanks a lot Of course if we can come up with code to do what we need we will make it open source