Difference between revisions of "Help:Application expert example page"

From SNIC Documentation
Jump to: navigation, search
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Example page]]
+
[[Category:Example page|{{PAGENAME}}]]
Minimal application expert user page. Copy and edit to suit your needs. See [[Template:application expert info]] for details.
+
Minimal application expert user page. Copy and edit to suit your needs.  
  
It is probably best to upload the image first, so make sure that mediawiki likes your filename.
+
See [[Template:application expert info]] for info on how to fill in most of the details.
 
 
In the [[Template:Application expert info|application expert info]] template, all the parameters are named, and can be given in any order. ''office'', ''phone'' and ''other activities'' are optional, all others are required. The template will protest loudly in bold red if required information is missing. If you do not wish to provide a certain piece of required information: do not use this template. Or else you will corrupt the database with incorrect information. In theory, you could abstain from uploading and setting ''image'', but then you will be depicted as a soulless automaton, and a rather chubby one at that.
 
 
 
''phone'' should be a semicolon separated list of telephone numbers (with optional explanation), ''office'' should be a semicolon separated list of visiting address lines, and ''other activities'' should be a semicolon separated list of minimal explanations of things that may steal you away from your pure application expertry at a regular basis, like part time employments, parental leave, special functions like AE/PRACE/etc coordination, or other distractions of that kind. Why semicolon you ask? Because people like to use commas for other things than input field separation. For further reading, see rationales on [[Property:Office]], [[Property:Phone]] and [[Property:Other activities]]. Note that it is currently not possible to put links in properties of Type:String, such as ''other activities''.
 
  
 
List one or more expertises using the <nowiki>[[expertise::Python]]</nowiki> notation. Expertises may be software, programming languages, protocols, algorithms, methods, laboratory techniques, or anything else entirely, and may or may not be related to your research area. See [[Property:Expertise]] for a list of what other people claim to do well. Does any of that apply to you? Slap it onto your page. If you create new expertise, you should probably create the page that it points to, and add at least a little bit of information to it. A red expertise does not look nice on your rap sheet.
 
List one or more expertises using the <nowiki>[[expertise::Python]]</nowiki> notation. Expertises may be software, programming languages, protocols, algorithms, methods, laboratory techniques, or anything else entirely, and may or may not be related to your research area. See [[Property:Expertise]] for a list of what other people claim to do well. Does any of that apply to you? Slap it onto your page. If you create new expertise, you should probably create the page that it points to, and add at least a little bit of information to it. A red expertise does not look nice on your rap sheet.
Line 14: Line 10:
 
Note that we do not promote providing your direct email address here, and especially not using email type properties (e.g: <s><nowiki>[[email::user@server.net]]</nowiki></s>, do not use!), because no obfuscation is applied, and email addresses advertised in this manner are easily harvested by bots using the semantic mediawiki search interfaces.
 
Note that we do not promote providing your direct email address here, and especially not using email type properties (e.g: <s><nowiki>[[email::user@server.net]]</nowiki></s>, do not use!), because no obfuscation is applied, and email addresses advertised in this manner are easily harvested by bots using the semantic mediawiki search interfaces.
  
''first name'' and ''last name'' are concatenated into ''name'', but since this information is already encoded into the user name (which already has the benefit of being a link to the user page), none of these properties are really used for anything clever just yet. The one benefit we currently see is that one could potentially be able to sort dynamically generated tables based on last names, but that is just not worth the layout cost of littering those tables with an additional redundant column. However, as layouts and names may change in the future, we decided to get in early and make sure people fill it in correctly from the start anyway.  
+
See [[Property:General activities]], [[Property:AE FTE]] and [[Property:AE financing]] if you are unsure what to put there.
 
 
 
 
  
 
<pre>
 
<pre>
Line 23: Line 17:
 
|last name=Your last name
 
|last name=Your last name
 
|centre=name of your SNIC centre
 
|centre=name of your SNIC centre
|research area=name of your research area
+
|fields=semicolon separated list of category names; your research area first; then any others; in decreasing order of relevance.
|other activities=50% research at [[http://www.ifm.liu.se/bioinfo IFM Bioinformatics]]
+
|fte=percent full time equivalent that you are employed for application expertise
|image=name of an image file
+
|financing=who finances the application expertise part of your position (ideally: just a single word, or as few words as possible with percentages in decreasing order).
 +
|general activities=Semicolon separated list of things you do as an application expert.; If you feel it is necessary.; Use minimal *but complete* sentences.
 +
|other activities=Semicolon separated list of things you do outside of your work as an application expert.; Like other part time duties.; Use minimal *but complete* sentences.
 +
|image=name of an uploaded image file
 
|office=Semicolon separated lines; of visiting address; newlines
 
|office=Semicolon separated lines; of visiting address; newlines
are ignored
+
are ignored; Provide this only if you want to.
|phone=Comma separated phone numbers (with optional  
+
|phone=Semicolon separated phone numbers (with optional  
explanation), newlines are ignored
+
explanation); newlines are ignored; only add this if you want users to phone you constantly.
 +
|start date=2010-01-01 (or omit if not applicable).
 +
|end date=2099-01-01 (or omit if not applicable).
 +
|is active=yes
 
}}
 
}}
  
Line 42: Line 42:
 
* [[expertise::mass spectrometry]]
 
* [[expertise::mass spectrometry]]
 
* [[expertise::flux capacitor calibration]]
 
* [[expertise::flux capacitor calibration]]
 +
 +
== Projects ==
 +
* [[project::Snicdocs]]
 
</pre>
 
</pre>

Latest revision as of 09:42, 24 March 2015

Minimal application expert user page. Copy and edit to suit your needs.

See Template:application expert info for info on how to fill in most of the details.

List one or more expertises using the [[expertise::Python]] notation. Expertises may be software, programming languages, protocols, algorithms, methods, laboratory techniques, or anything else entirely, and may or may not be related to your research area. See Property:Expertise for a list of what other people claim to do well. Does any of that apply to you? Slap it onto your page. If you create new expertise, you should probably create the page that it points to, and add at least a little bit of information to it. A red expertise does not look nice on your rap sheet.

Remember to create your talk page (Discussion), and add something inviting so that people will feel encouraged to talk to you, or just rip off someone else who said something nice. Remember that your talk page will likely be your primary form of contact for members of the general public who chance upon the wiki.

Note that we do not promote providing your direct email address here, and especially not using email type properties (e.g: [[email::user@server.net]], do not use!), because no obfuscation is applied, and email addresses advertised in this manner are easily harvested by bots using the semantic mediawiki search interfaces.

See Property:General activities, Property:AE FTE and Property:AE financing if you are unsure what to put there.

{{application expert info
|first name=Your first name
|last name=Your last name
|centre=name of your SNIC centre
|fields=semicolon separated list of category names; your research area first; then any others; in decreasing order of relevance.
|fte=percent full time equivalent that you are employed for application expertise
|financing=who finances the application expertise part of your position (ideally: just a single word, or as few words as possible with percentages in decreasing order).
|general activities=Semicolon separated list of things you do as an application expert.; If you feel it is necessary.; Use minimal *but complete* sentences.
|other activities=Semicolon separated list of things you do outside of your work as an application expert.; Like other part time duties.; Use minimal *but complete* sentences.
|image=name of an uploaded image file
|office=Semicolon separated lines; of visiting address; newlines
are ignored; Provide this only if you want to.
|phone=Semicolon separated phone numbers (with optional 
explanation); newlines are ignored; only add this if you want users to phone you constantly.
|start date=2010-01-01 (or omit if not applicable).
|end date=2099-01-01 (or omit if not applicable).
|is active=yes
}}

== Quick facts ==
* Or any other heading. 
* This part is clear text and very much up to you.
* Bullet lists are good 
* for the lazy

== Expertise ==
* [[expertise::Python]]
* [[expertise::mass spectrometry]]
* [[expertise::flux capacitor calibration]]

== Projects ==
* [[project::Snicdocs]]