维基文章的两阶段审批流程
我正在尝试配置一个 wiki 以允许两阶段的审批流程。基本工作流程需要类似：
- 一组用户提交一个简短的表单
- 管理员批准后，该组可以使用更大的表单
- 该组提交更大的表单
- 管理员批准后，页面（由表单填写）变为公开
I'我已经研究 TikiWiki 和 MediaWiki 一段时间了，试图配置它们以更接近这个模型，但我遇到了一些问题。
对于 TikiWiki，似乎批准阶段应该是一个过渡，要么更改组权限以允许访问新的跟踪器，要么更改表单类别以关闭一个表单并打开另一个表单，但我还没有无法确定该配置的权限。
对于 MediaWiki，主要问题似乎是后端没有设置复杂的权限。我一直在使用 SMWHalo 和 SemanticForms 来构建这个，但我找不到像 Tikiwiki 的 transitions 这样的东西来自动更改组或表单的权限。
我对 Wiki 开发有点陌生，并且我知道 Wiki 框架有很多选择，因此我寻求有关此产品的良好工作流程的建议。我的目标是只开始实际接触框架代码以进行最终调整，而不是开始修改已经开发良好的代码库。
I'm trying to configure a wiki to allow a two staged approval process. The basic work flow requires something like:
- A group of users submits a short form
- After admin approval, a larger form becomes available to the group
- The group submits the larger form
- After admin approval, the page (filled by the form) becomes public
I've been looking at TikiWiki and MediaWiki for a while trying to configure each to get even close to this model, but I'm having some problems.
With TikiWiki, it seems like the approval stage should be a transition, either changing the group permissions to allow access to a new tracker or changing the form category to close one form and open the other, but I haven't been able to nail down the permissions for that configuration.
With MediaWiki, the main problem seems to be that the back-end was not made to have complex permissions. I've been using SMWHalo along with SemanticForms to construct this, but I can't find anything like Tikiwiki's transitions for changing the permissions for either the group or the form automatically.
I'm a bit new to Wiki development and I know that there are a lot of options for wiki frameworks, so I'm asking for suggestions for a good work flow for this product. My goal is to only start actually touching the framework code to make the final adjustments and not to start off modifying an already well developed code base.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你真的应该问自己为什么想要这个以及为什么你想要在 wiki 中使用这个。
Wiki 的主要优点是快速、简单，从而鼓励用户。添加审批阶段会阻碍用户参与。 任何 wiki 中最困难的部分不是防止破坏或虚假信息。最困难的部分是鼓励参与。
如果您确实需要困难的审批工作流程，您可能需要考虑 CMS 系统。据我所知，typo3 内置了类似的东西。
如果你真的想使用 wiki 和审批流程，对于 DokuWiki，你可以看看发布插件：http://www.dokuwiki.org/plugin:publish
You should really ask yourself why you want this and why you want this in a wiki.
A Wiki's main advantage is being quick and easy and thus encouraging to the user. Adding approval stages will discourage users to participate. The hardest part in any wiki is not preventing vandalism or false information. The hardest part is to encourage participation.
If you really need a difficult approval workflow you might want to look at CMS systems. AFAIK typo3 has something like this built in.
If really you want to go with a wiki and an approval process, for DokuWiki you could have a look a the publish plugin: http://www.dokuwiki.org/plugin:publish
MediaWiki 的 FlaggedRevs 扩展添加了基本权限工作流程：
http://www.mediawiki.org/wiki/ Extension:FlaggedRevs
但是，它更适合控制对现有页面的更改，而不是添加全新的页面。您可以将其设置为创建新页面作为草稿，并默认公共视图仅显示批准的版本，但听起来您想完全隐藏未经批准的版本，这将需要一些额外的黑客攻击（并且，正如安德烈亚斯所说，有点失败）首先是维基百科的要点）。
The FlaggedRevs extension to MediaWiki adds a basic permissions workflow:
http://www.mediawiki.org/wiki/Extension:FlaggedRevs
However, it's geared more at controlling changes to existing pages, not adding entirely new ones. You could set it up to create new pages as drafts and defaulting the public view to show only approved versions, but it sounds like you want to hide unapproved versions entirely, which would require some extra hacking (and, as Andreas says, kind of defeats the point of a wiki in the first place).