Help:Editing policies
This page contains information on how one should edit this wiki, eg: best practices, protocols, templates and the like.
Contents
Semantic mediawiki extension
The snicdocs wiki uses the semantic mediawiki extension, which enables nifty things like dynamic generation of lists, tables and mashups based on tagged data in ordinary wiki pages. The annotation is unobtrusive, e.g:
- [[competence::Python]] to make Python
and the search/generate syntax is equally straightforward
- {{#ask: [[Category:Software]] [[Category:Bioinformatics]] |?centre }} to make redacted, do not use before the extension is properly installed, or it may mess up the page's categories
as long as we do not let nomenclature run rampant and diverge (see: the problem with the semantic web).
Notice
In case the examples appear in red, or if you see similar broken links with double colons in them in other places on the wiki, do not edit the links. They appear because you have happened to come across the pages before we have managed to install the semantic mediawiki extension properly on our production server. This problem should disappear very shortly, and if it persists beyond your definition of shortly, notify User:Joel Hedlund (NSC).
Recommendations for editors
Set up your watch lists and notifications
- Go to your preferences page and add your email.
- Configure your account so that pages you create automatically get added to your watchlist, and that notifications will go to your email.
- Check the list of Special:UnwatchedPages. Is it zero length? Otherwise something is wrong. Is any of your pages on there? Add them to your watch list.
Set up your user page correctly
- Tag your user page with the categories "Applications expert" and your research area (at least one, eg "Bioinformatics").
- List your special competences using verbatim semantic medawiki property tags, like so [[competence::Python]] to make e.g: Python, note double colons.
Naming scheme and protocol
Titles, headings and names
Capitalisation matters in mediawiki, to the point that you only get to have some control over it. Case in point: Category:Molecular dynamics and Category:molecular dynamics go to the same page, but Category:Molecular Dynamics does not (and don't you go create it!). Therefore:
All titles, headings and names, including category names and property names, should be in all lowercase, except the first character which should be a capital letter, like so:
Recommendations for editors Editing policies Category:Research area Property:Competence
Mediawiki automatically capitalises the first letter of all names, which has the benefit that one can readily type most markup in all lowercase, like so:
[[competence::python]], [[category:research area]], etc...
Widely accepted acronyms like SNIC, NSC or HMMER are of course exceptions from this rule, and should be in all uppercase.
Categories and properties
The snicdocs wiki makes extensive use of categories, in part to simplify navigation for the users, but mostly because it permits straightforward creation of dynamically generated lists, tables and mashups using the semantic mediawiki extension. This, however, requires generous peppering of category and property tags onto wiki pages, using great restraint and strict discipline so that nomenclature does not run rampant and diverge (see: the problem with the semantic web).
- Do not recklessly invent new categories and properties! Check these lists first, to see if any of the already existing ones may suit your needs:
- Use singular for names. E.g. Applications expert, Resource, Centre...
- Use descriptive and unambiguous names. Especially for properties. Keep in mind that these will be used to define searches and will also end up as headings in dynamically generated tables, unless other people do extra work to change it on each use.
- Are you creating a new subcategory? Categories can be nested in a DAG (tree) structure. Look at the current list of top categories:
- Does yours fit on that list, or will it fit better as a sub(-sub)-category? Drill down and see, and annotate your new category accordingly.
- What does the property mean, exactly? How should it be used? Add a brief and unambiguous description to the property page (eg: Property:Competence).
