Manual:Quality management

There are numerous quality management tools available to ensure the quality of a wiki page.

Document control

In BlueSpice, many users can create information. Specialists can then review the content. This ensures that the quality of the content meets your organization's standards. It should be noted that rigid quality controls and processes quickly limit employee autonomy. Despite the possibility of quality control, you should therefore always ensure that you do not introduce unnecessary hurdles that affect the acceptance of the wiki.

The following areas should be kept in mind for quality assurance in the wiki:

1. Document quality (Quality tools, Templates)
2. Content organization (Structure, Portal pages, Queries)
3. Wiki maintenance (Special pages, Processes, Watchlist, Notifications)

Quality tools

(1) Page approval, (2) Workflows, (3) Expiry, (4) Reminder, (5) Page assignments, (6) Page information, (7) IMS Template

BlueSpice free

• Page assignments (5)
• Page information (6)

BlueSpice pro

• Approvals (1)
• Workflow (2)
• Expiry (3)
• Reminder (4)
• Page assignments (5)
• Page information (6)

Note: To formally support document management, the IMS templates are also suitable for creating process-related wiki pages.

Approval

If the pages in a namespace should have a published and a draft version, the Approval setting must be enabled for that namespace. All changes to a page are recorded in a draft version until a user with approval rights accepts the page.

There is a global option in the configuration manager that can be used to specify which user groups can read unpublished content. By default, all logged in users can view drafts.

Features

• Revision-based: Distinguish between initial draft, draft, and approved
• External files: Embedded media and templates are "frozen"
• Automatic approval as a result of a review possible
• Read-only rights for drafts can be configured (with caution)

More info on approval

Workflows

If a documented review process is desired, users can start a workflow. There are 4 included workflows:

• Release
• Quality-assured review
• Group feedback
• Feedback

Properties

• Usually only one active review is possible per page
• Approval or rejection of participants in approval workflows
• Checkout: Page is locked for editing in the approval workflows
• Special page Workflows overview
• BPMN-based

More info on workflows

Currentness

If a page contains content with a known lifecycle, you can specify that the page expires on a specific date. On the expiration date, an "Outdated" watermark is added to the page if the corresponding option is set in the ConfigManager. In addition, a reminder can be set so that the user receives a notification when the page expires. The expiration can be deleted from the page at any time.

Properties

• Watermark in the page background and in the PDF (depending on global configuration)
• Overview list: Special:Outdated_pages
• Reminder can be activated when creating
• Duration: Outdatedness can be deleted at any time

More info on expiry

Reminder

A user can create a reminder for a page by selecting a reminder date and adding an optional comment. Reminders can also be created by administrators for other users and are a quick and informal way to set due dates for page-related tasks.

Properties

• Notification of your own reminders receives a notification (can be deactivated in user settings)
• Recurring reminders possible
• Reminder list: Special page for administrators (under Global Actions)
• Quick access via the personal user menu

More info on reminders

Assignment

Page assignments offer the possibility of giving one or more users or user groups the editorial responsibility for a page.

It is also possible to set up a namespace in such a way that assigned users must submit a read confirmation for every major change to a page. As assignments are available in the wiki as a page attribute, they can be used in semantic queries.

Properties

• Notification when the page assignment is changed (can be deactivated in user settings)
• Transparency: Assigned users are listed in the page information
• Assignment management: special page for administrators
• Quick access to own assignments via the personal user menu
• Read confirmation possible: Assigned users must then confirm that they have read changes to the page (namespace-specific)

More info on page assignments

Page information

The page information gives you some interesting statistics about the page. You can use this information to decide what measures are required to ensure the quality of the page.

Information listed on this page:

• Number of watchers of the page
• All editors, last edit
• Properties: Embedded templates, embedded images, internal and external links, categories
• Page currentness
• Page authors
• Page readers (only visible to administrators)
• Reminders (all reminders only visible to administrators, otherwise own reminders)

Permissions

This permission table shows which roles have the required permission to perform various quality assurance actions. The name of the right that grants a specific authorisation is shown in brackets:

QM action	user (read)	editor	reviewer	admin	maintenance-admin	bot
Can create and manage assignments for all users (pageassignments)			x	x	x
Can be assigned to a page (pageassigneable)	x
Can create and manage reminders for all users (remindereditall)				x	x
Can create and manage own reminders (read)	x
Can create and manage the expiration of pages (expirearticle)		x		x	x
Can execute workflows (workflows-execute)		x	x	x
Can view workflow elements (workflows-view)	x
Can manage workflows (workflows-admin)				x
Can approve a page (review)			x	x	x
Own changes are automatically approved (autoreview)					x	x
Reverted changes are automatically approved (autoreviewrestore)					x	x

Related info

• Namespace manager
• Workflows

PDF exclude - start

---

To submit feedback about this documentation, visit our community forum.

PDF exclude - end