Loading...
 
Skip to main content

Features / Usability


Workflow for wiki pages?

I would like to completely replace the existing intranet with tiki.
In order to do so, I badly need a possibility to set aside a special
wiki area that has to work in the following way:

  • PrivilegedUser SomeHow build a set of pages.
  • SomeOne notices an error in one of the pages, and fixes it.
    1. The change is NOT shown to all the users yet. ❗
    2. There is some kind of "change pending" sign shown on the page, that clearly shows that SomeOne has posted a change request for this page. Showig the username and/or the request date woudl be a plus
    3. PrivilegedUser(s) get (email) notification that the page has been changed.❗
  • PrivilegedUser checks the changes, possibly edits the content of the page, and then either marks the new page as "OK", or drops the change (possibly with a nasty notice to the user who added the dumb comment in the first place).


What I am trying to do is a way to keep the materials made by some "professionals" up to date with a minimum of fuss. Current situation is that:

  1. Company policy prohibits normal users from doing any changes on "oficial" pages. If/when SomeOne notices a problem on a page, he/she can send an email to page owner, and hope for the best.
  2. Page owners hardly ever update the pages, and there is no way of checking if they even read the emails.🙁


With a system similar to one I proposed above, it woudl be easy to see that person X ignored the proposed changes for the last 2 months, produce HallOfTheShame with most unresponsive authors, or even automatically show the changed version to everyone after a certain time. 😀

Is it possible to build something similar using the tikiWiki + Galaxia? ❓

Note: This system should NOT affect all of the wiki, just a part of it that contains "oficial" pages.

Thats better worked this time 😎

Hi Deno

> I would like to completely replace the existing intranet with tiki.
> In order to do so, I badly need a possibility to set aside a special
> wiki area that has to work in the following way:
-8

> Damian:

> -8

Eer... Does that mean no? 😉

> Deno:
> > Damian:
>
> > -8
>
> Eer... Does that mean no? 😉

Hmm Tiki not behaving for its master 😉

You would need to create a new permission in the database and modify the tiki-admin permissions and admin groups pages.

Then you would need to modify all tiki features to recogonise the new permission.

A lot of work, but could be quite useful 😛

Damian

> Damian:
> A lot of work, but could be quite useful 😛

I know. Unfortunately, I need a way to "sell" the tiki to managment as it is, before being able to seriously work on the code. 😑


> Damian:

> -8

Eer... Does that mean no? 😉

> Deno:
> > Damian:
>
> > -8
>
> Eer... Does that mean no? 😉

Hmm Tiki not behaving for its master 😉

You would need to create a new permission in the database and modify the tiki-admin permissions and admin groups pages.

Then you would need to modify all tiki features to recogonise the new permission.

A lot of work, but could be quite useful 😛

Damian

> Damian:
> A lot of work, but could be quite useful 😛

I know. Unfortunately, I need a way to "sell" the tiki to managment as it is, before being able to seriously work on the code. 😑