Skip Ribbon Commands
Skip to main content

User manual for approvers

​Wiki revisions

All the wikis on the FEM Wiki site follow the wiki principle of storing the entire history of revisions for each of its pages, including when the revision was made and by whom.  You can see the history of all versions via the History tab where you can also compare versions.  This allows anyone to change the page since it makes it easy to spot when a page has taken a turn for the worse and recover it.

Approved versions

Given the importance of the FEM Wiki Manual content, we have also added the facility to mark a specific page version as approved to provide confidence in the reliability of its content.

Approval can be performed by any one of a designated subset of group members recognised as domain experts with a single button click using the approval widget described below.  The most recent version that has been approved is then featured.

Approval widget

The approval widget is only shown to moderators (and owners) of the FEM group and sits alongside Manual pages.  For new pages, the widget will appear as below:

Once a page has been approved, it cannot be approved again so the button is removed and the following displayed:

If the page is revised further then the widget again displays the approval button with an appropriate message:

Finally, if an old version is visited then the following link to the latest approved version is displayed:

Notes

Since we are only featuring the most recent approved version, it makes sense to restrict approvals to versions that are more recent than the current most recently approved version.

The date and time of the approval is recorded and the most recently approved version is featured.  The contributing editors of a page are listed alongside it under the header 'Approvers'.

There is currently no 'unapprove' button.  Rather than attempt to 'retract' approvals, recommended practice is to revise content then approve that.

Validate Taxonomy and Tagging fit

The FEM Wiki content is divided into a number of chapters. Pages in each of the chapters have a latest community version (corresponding to the version of the page that was most recently edited by a member of the FEM), and an expert reviewed version (the last version that was reviewed by a domain expert).

On this page, we give a simple overview of the concepts behind the taxonomy and tagging before digging into the detail of how this is implemented on the FEM Wiki site.

Taxonomy

The contents of the FEM Wiki Manual have a tree-like structure of concepts, sub-concepts and so on - implementing a taxonomy.  This lets users 'zoom in' on topics of interest whilst also highlighting topics from the same family.  

Tagging

All pages can be assigned any number of tags - or keywords - which provide a way to bundle pages together around a theme or topic.  They can be applied freely wherever a user feels a tagging would be useful via the Tag link shown below:

Tagging is generally better way to add structure to the Manual without the significance of restructuring the taxonomy.

A simple example

An example using a simple biological taxonomy is given below with the carnivore, colourful and upright tags.

Site usage

We now describe how the above abstract models are implemented on the FEM Wiki.

Tagging

Tagging is very simple, lightweight and reversible.  Any number of tags can be added to a page (or discussion) as it is being created or any time after.  They can be typed as a comma-separated list or selected from a list of previously-used tags.  It is good practice to select existing tags, where possible, rather than creating arbitrary synonyms.

Taxonomy

The position of a page in the taxonomic structure is set entirely by the Parent Page field for the page during editing.  Since all registered users can generally edit any page, they can also edit the taxonomic structure.  However, this should only be done after gaining a consensus on the forum since it is a significant change.

Adding a page is a more straightforward process.  If the page could be better placed, then a confident user can move it (via its parent) to a more appropriate location at an early point.​​