Difference between revisions of "Template:Application expert info"

From SNIC Documentation
Jump to: navigation, search
 
(22 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
This template creates a standard info blurb for an application expert, and registers the relevant categories and properties (excluding expertises!). Will protest loudly in bold red if mandatory 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.
 
This template creates a standard info blurb for an application expert, and registers the relevant categories and properties (excluding expertises!). Will protest loudly in bold red if mandatory 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.
  
Usage: <nowiki>{{</nowiki>application expert info|''first name''=|''last name''=|''centre''=|''field''=|''image''=|''office''=|''phone''=|''other activities''=<nowiki>}}</nowiki>
+
Usage: <nowiki>{{</nowiki>application expert info|''first name''=|''last name''=|''centre''=|''field''=|''image''=|''office''=|''phone''=|''other activities''=|''start date''=|''end date''=|''is active''=<nowiki>}}</nowiki>
  
 
All the parameters are named, and can be given in any order. ''office'', ''phone'' and ''other activities'' are optional, all others are required.  
 
All the parameters are named, and can be given in any order. ''office'', ''phone'' and ''other activities'' are optional, all others are required.  
Line 8: Line 8:
 
''fields'' should be a semicolon separated list of field category page names, in decreasing order of relevance. Start with your research area.
 
''fields'' should be a semicolon separated list of field category page names, in decreasing order of relevance. Start with your research area.
  
''fte'' = full time equivalent dedicated to application expertise, see [[Property:FTE]] for details.
+
''fte'' = percent full time equivalent dedicated to application expertise, see [[Property:AE FTE]] for details.
  
''financing'' minimal description of where your salary comes from. Ideally: one word.
+
''financing'' minimal description of where the financing for your application expertise (pert) comes from. Ideally: one word. See [[Property:AE financing]] for details.
  
 
''image'' is the filename of an already uploaded image file. See the [[Help:Recommendations for editors#Portrait image requirements|portrait image requirements]] for restrictions of sizes, formats, colors and other things. Read and conform, or risk looking like a doofus in dynamically generated content. It is probably best to upload the file first, so make sure that mediawiki likes your filename. In theory, you could abstain from uploading and setting and image, but then you would be depicted as a soulless automaton, and a rather chubby one at that.
 
''image'' is the filename of an already uploaded image file. See the [[Help:Recommendations for editors#Portrait image requirements|portrait image requirements]] for restrictions of sizes, formats, colors and other things. Read and conform, or risk looking like a doofus in dynamically generated content. It is probably best to upload the file first, so make sure that mediawiki likes your filename. In theory, you could abstain from uploading and setting and image, but then you would 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).
+
''general activities'' should only be provided if you do not feel that "Application expert in ''fields''" is sufficient to describe what it is that you do. If provided, this should be a semicolon separated list of minimal explanations of what you do as an application expert. For rendering reasons: use full sentences, complete with capital first character and ending full stop. Note that it is currently not possible to get [http://xkcd.com clickable links] in properties of Type:String, such as ''other activities''.
  
''office'' should be a semicolon separated list of visiting address lines.
+
''phone'' should only be provided if you think it is a good idea to have all users contact you by phone, and if so it should be a semicolon separated list of telephone numbers (with optional explanation).
 +
 
 +
''office'' can be provided if you like, and if so it should be a semicolon separated list of visiting address lines.
  
 
''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. For rendering reasons: use full sentences, complete with capital first character and ending full stop. Note that it is currently not possible to get [http://xkcd.com clickable links] in properties of Type:String, such as ''other activities''.
 
''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. For rendering reasons: use full sentences, complete with capital first character and ending full stop. Note that it is currently not possible to get [http://xkcd.com clickable links] in properties of Type:String, such as ''other activities''.
  
 
Why semicolons 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]].  
 
Why semicolons 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]].  
 +
 +
''is active'' defines whether or not you are to be considered in active duty as an application expert. Omitted or left empty means 'yes'.
 +
 +
''start date'' and ''end date'' define the period when you are/were working as an application expert. Omit if not appliccable.
  
 
Neither ''fist name'' or ''last name'' (nor the concatenation "name") are currently used for anything fancy, since that information is already provided in the user name (which also has the benefit of nearly always being a link to that person's user page). We thought it prudent to get this filled in anyway, since this might change in the future.
 
Neither ''fist name'' or ''last name'' (nor the concatenation "name") are currently used for anything fancy, since that information is already provided in the user name (which also has the benefit of nearly always being a link to that person's user page). We thought it prudent to get this filled in anyway, since this might change in the future.
Line 34: Line 40:
 
|fte=50
 
|fte=50
 
|financing=SNIC
 
|financing=SNIC
 +
|general activities=Bioinformaticsy stuff.; Web design; Mediawiki wrangling.
 
|other activities=50% research at IFM Bioinformatics
 
|other activities=50% research at IFM Bioinformatics
 
|image=Joel_small.jpg
 
|image=Joel_small.jpg
|office=Room 159, House G; Linköpings Universitet; SE-581 83 Linköping
+
|office=Room X, Some building; My campus; Some city
|phone=+46(0)13 282423 (office); +46(0)734 607126 (mobile)
+
|phone=+46(0)12 3456 (office); +46(0)123 4567 (mobile)
 +
|start date=2010-01-01
 +
|end date=2099-01-01
 +
|is active=yes
 
}}
 
}}
 
</pre>
 
</pre>
Line 46: Line 56:
 
|'''[[first name::{{{first name|<span style="font-weight: bold; color: red;">ERROR</span>}}}]] [[last name::{{{last name|<span style="font-weight: bold; color: red;">ERROR</span>}}}]]''' ([[centre::{{{centre|<span style="font-weight: bold; color: red;">ERROR</span>}}}]]) [[name::{{{first name}}} {{{last name}}}| ]]
 
|'''[[first name::{{{first name|<span style="font-weight: bold; color: red;">ERROR</span>}}}]] [[last name::{{{last name|<span style="font-weight: bold; color: red;">ERROR</span>}}}]]''' ([[centre::{{{centre|<span style="font-weight: bold; color: red;">ERROR</span>}}}]]) [[name::{{{first name}}} {{{last name}}}| ]]
  
{{set category|role|application expert}} in {{set category list|field|{{{fields|<span style="font-weight: bold; color: red;">ERROR</span>}}}}} {{#show: {{FULLPAGENAME}}|?field}}{{#if:{{{fte|}}}|, [[FTE::{{{fte}}}]]% full time equivalent|}}{{#if:{{{financing|}}}|, financed by {{{financing}}}|}}
+
{{set category|role|application expert}} in {{set category list|field|{{{fields|<span style="font-weight: bold; color: red;">ERROR</span>}}}}} {{#show: {{FULLPAGENAME}}|?field}}{{#if:{{{fte|}}}|, [[AE FTE::{{{fte}}}]]% full time equivalent|}}{{#if:{{{financing|}}}|, financed by [[AE financing::{{{financing}}}]]|}}{{#if:{{{snic ae financing|}}}|{{#set: SNIC AE financing={{{snic ae financing}}}}}|}}{{#if:{{{other ae financing|}}}|{{#set: Other AE financing={{{other ae financing}}}}}|}} <!--
{{#if: {{{other activities|}}}|;Other activities
+
--> {{#switch: {{lc:{{{is active|yes}}}}}|#default=;Is active:<span style="font-weight: bold; color: red;">ERROR</span>|yes|1|true|on={{#set: is active=yes}}|no|0|false|off={{#set: is active=no}};Is active: No.}} <!--
:{{set list|other activities|{{{other activities|}}}|sep=;|glue=\n:}}}}
+
--> {{#if: {{{general activities|}}}|;General activities
{{#if: {{{office|}}}|;Office
+
:{{set list|general activities|{{{general activities|}}}|sep=;|glue=\n:}}}} <!--
:{{set list|office|{{{office|}}}|sep=;|glue=\n:}}}}
+
--> {{#if: {{{other activities|}}}|;Other activities
{{#if: {{{phone|}}}|;Phone
+
:{{set list|other activities|{{{other activities|}}}|sep=;|glue=\n:}}}} <!--
 +
--> {{#if: {{{start date|}}}|;Start date
 +
:[[Start date::{{{start date}}}]]}}{{#if: {{{end date|}}}|;End date
 +
:[[End date::{{{end date}}}]]}} <!--
 +
--> {{#if: {{{office|}}}|;Office
 +
:{{set list|office|{{{office|}}}|sep=;|glue=\n:}}}} <!--
 +
--> {{#if: {{{phone|}}}|;Phone
 
:{{set list|phone|{{{phone|}}}|sep=;|glue=\n:}}}}
 
:{{set list|phone|{{{phone|}}}|sep=;|glue=\n:}}}}
 
|}</includeonly>
 
|}</includeonly>

Latest revision as of 11:30, 18 September 2013

This template creates a standard info blurb for an application expert, and registers the relevant categories and properties (excluding expertises!). Will protest loudly in bold red if mandatory 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.

Usage: {{application expert info|first name=|last name=|centre=|field=|image=|office=|phone=|other activities=|start date=|end date=|is active=}}

All the parameters are named, and can be given in any order. office, phone and other activities are optional, all others are required.

fields should be a semicolon separated list of field category page names, in decreasing order of relevance. Start with your research area.

fte = percent full time equivalent dedicated to application expertise, see Property:AE FTE for details.

financing minimal description of where the financing for your application expertise (pert) comes from. Ideally: one word. See Property:AE financing for details.

image is the filename of an already uploaded image file. See the portrait image requirements for restrictions of sizes, formats, colors and other things. Read and conform, or risk looking like a doofus in dynamically generated content. It is probably best to upload the file first, so make sure that mediawiki likes your filename. In theory, you could abstain from uploading and setting and image, but then you would be depicted as a soulless automaton, and a rather chubby one at that.

general activities should only be provided if you do not feel that "Application expert in fields" is sufficient to describe what it is that you do. If provided, this should be a semicolon separated list of minimal explanations of what you do as an application expert. For rendering reasons: use full sentences, complete with capital first character and ending full stop. Note that it is currently not possible to get clickable links in properties of Type:String, such as other activities.

phone should only be provided if you think it is a good idea to have all users contact you by phone, and if so it should be a semicolon separated list of telephone numbers (with optional explanation).

office can be provided if you like, and if so it should be a semicolon separated list of visiting address lines.

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. For rendering reasons: use full sentences, complete with capital first character and ending full stop. Note that it is currently not possible to get clickable links in properties of Type:String, such as other activities.

Why semicolons 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.

is active defines whether or not you are to be considered in active duty as an application expert. Omitted or left empty means 'yes'.

start date and end date define the period when you are/were working as an application expert. Omit if not appliccable.

Neither fist name or last name (nor the concatenation "name") are currently used for anything fancy, since that information is already provided in the user name (which also has the benefit of nearly always being a link to that person's user page). We thought it prudent to get this filled in anyway, since this might change in the future.

Example:

{{application expert info
|first name=Joel
|last name=Hedlund
|centre=NSC
|fields=bioinformatics
|fte=50
|financing=SNIC
|general activities=Bioinformaticsy stuff.; Web design; Mediawiki wrangling.
|other activities=50% research at IFM Bioinformatics
|image=Joel_small.jpg
|office=Room X, Some building; My campus; Some city
|phone=+46(0)12 3456 (office); +46(0)123 4567 (mobile)
|start date=2010-01-01
|end date=2099-01-01
|is active=yes
}}