This template is part of WikiProject Cricket which aims to expand and organise information better in articles related to the sport of cricket. Please participate by visiting the project and talk pages for more details.CricketWikipedia:WikiProject CricketTemplate:WikiProject Cricketcricket articles
There is a toolserver based WikiProject Cricket cleanup list that automatically updates weekly to show all articles covered by this project which are marked with cleanup tags. (also available in one big list and in CSV format)
Usage:
Designed to be used instead of Template:First Class Matches where an editor feels necessary/prefers working with it. The functionality is similar, but extended, as described below.
Contrary to the name, this template does not have to be used for just Test Matches - it may be used for those that do not necessarily have test status (ie a Tour Match, or a First Class match in domestic cricket). It is simply named as such because 'First Class Matches' would be the ideal name but is currently taken by the old method.
Usage of the template may appear confusing at first but is easily explained. A clean template with all variables available is:
Most are fairly obvious, but some may seem slightly more ambiguous at first:
Team1 should be the team batting first. This is simply to make it easier to comprehend when in use on a page.
runs-teamx-innsx indicate the highest run scorer of the innings. wickets-teamx-innsx indicate the highest wicket taker of the innings.
score-team1-inns1, runs-team1-inns1, wickets-team1-inns1 are defined as the following: The score, runs and wickets gained in the first team's first innings. For clarity, the name in wickets1x1 should be of a player from Team2 because he was bowling during the first team's first innings.
The numbers within each of these 3 tags define two things:
How this applies for other teams/innings: score-team2-inns1 is Team2's 1st innings score, score-team1-inns2 is Team1's 2nd innings score.
Motm is simply short for Man of the Match.
Report should ideally link to a scorecard, from a good source (Cricinfo, Howstat, Cricket Archive or Wikinews if appropriate).
Rain can be used for indicated various issues that reduced the amount of time taken or other issues with the match: ie, major rain interruption, change of umpires.
Advantages of this system:
It is a lot more forgiving and flexible. It is based upon the 2nd version of Template:Limited overs international which was extensively used on the 2007 Cricket World Cup page which made changing various information possible without being forced to {{subst:}} the template in and remove excess/redundant data.
It is less confusing to work with. It is much more simple to work with than having around 9 variables to work with for each innings.
It allows the editor to remove specific information that are not applicable to the match in hand. If an innings wasn't played, no data needs to be entered. The old method involved substituting the template in and removing some of the structure of the table until it looked correct - this is no longer necessary. This was the main reason for creating the template - this was a huge hassle and also ended up with making the coding of the page somewhat messy.
Drawbacks:
No longer a forced naming system for players: the old system used to force you to put in initials and the name (for the page to link) - this now has to be done manually. The up-side is it prevents confusion that the old system created: the variable used to be called 'Highest scorer for first innings of first team' when it actually meant the page link for the person in question, sometimes leading to pointing at a redirect or disambig page.
Similar problems are true for nationalities of the umpires and similar data.
May be a bit confusing to work with at first, admittedly.
The 3 above may all seem like drawbacks for some but, to quote User:Sam Vimes: "... [features] such as lack of standardisation of player names, umpire nationalities, etc. are actually a requirement of well-working templates."
Dates are not handled so well. To be fair, they weren't handled at all beforehand and made putting the date elsewhere on the page a requirement. The current method I have found the best so far is to put something along the lines of the following:
date = [[November 5]] -<br>[[November 8]], [[2007]] |
Although changing the dates is obviously necessary depending on the page. Note: I have plans to possibly change the template to make the column with the date data in it wider so that even long dates can fit on one line. I'll keep this page updated.