| caption = MediaWiki's logo. The double square brackets around the photo of a [[sunflower]] symbolize the [[syntax]] MediaWiki uses for creating [[hyperlinks]] to other wiki pages.
{{Distinguish2| [[Humane Society of the United States]]}}
'''MediaWiki''' is a [[wiki software]] package licensed under the [[GNU General Public License]]. It is written in [[PHP]] and requires the [[MySQL]] [[relational database management system]] (although it has some [[PostgreSQL]] support). Historically, MediaWiki was developed to serve the needs of [[Wikipedia]], a free wiki-based [[encyclopedia]], but it has since become one of the most popular general wiki solutions. Today, it is used by all projects of the [[Wikimedia Foundation]], all wikis hosted by [[Wikia]], and many other popular and large wikis.<ref>{{cite web| url = http://s23.org/wikistats/wikis_html.php| title = WikiStats by S23 - List of largest wikis| accessdate = 2006-06-29 | author = "mutante"}}</ref> It has also been deployed by companies as an internal [[knowledge management]] solution, and as a [[content management system]]. Notably, [[Novell]] uses it to operate several of its high traffic websites, which are not editable by the general public.
'''HUMANE FARM ANIMAL CARE''' is the independent non-profit organization that conducts regular inspections and administers the “Certified Humane Raised & Handled” program. Participating businesses must pass an initial inspection as well as annual re-inspection to remain part of the Certified Humane Raised & Handled program.
The Certified Humane Raised & Handled Label is a consumer certification and labeling program.When you see the Certified Humane Raised & Handled label it means that an egg, dairy, meat or poultry product has been produced with the welfare of the farm animal in mind. Food products that carry the label are certified to have come from facilities that meet precise, objective standards for farm animal treatment.
== QUALITY STANDARDS ==
A team of veterinarians and animal scientists developed the Animal Care Standards to ensure that producers and processors keep animals in conditions that have met high standards of animal care:
• Allow animals to engage in their natural behaviors
• Raising animals with sufficient space, shelter and gentle handling to limit stress
• Making sure they have ample fresh water and a healthy diet without added antibiotics or hormones
Under the system, growth hormones are prohibited, and animals are raised on a regular diet of quality feed free of antibiotics. Producers also must comply with local, state and federal environmental standards. Processors must comply with the American Meat Institute Standards, a higher standard for slaughtering farm animals than the Federal Humane Slaughter Act.
=== A BETTER CHOICE ===
The quality of the meat, poultry, egg and dairy products depends, at least in part, on the quality of care farm animals receive. The Certified Humane Raised & Handled program lets consumers choose products from businesses that are providing humane conditions for the animals in their care.
MediaWiki provides a rich core feature set and a mechanism to attach [[extension (computing)|extensions]] to provide additional functionality. Due to the strong emphasis on multilinguality in the Wikimedia projects, [[internationalization]] has received significant attention by developers. The user interface has been fully or partially translated into more than 70 languages, and can be further customized by site administrators (the entire interface is editable through the wiki). Due to Wikipedia being one of the world's largest websites, achieving scalability through multiple layers of [[cache|caching]] and [[database replication]] has also been a major concern for developers. Wikipedia and other Wikimedia projects continue to define a large part of the requirement set for MediaWiki.
== History ==
The software was originally written for [[Wikipedia]] by the [[Germany|German]] [[University of Cologne]] student and developer [[Magnus Manske]]. Wikipedia had previously used a small wiki engine called [[UseModWiki]] written in [[Perl]]. On [[January 25]] [[2002]], Wikipedia was switched to Manske's software to offer more functionality and build upon a scalable infrastructure (i.e. a MySQL database). However, the first implementation actually led to significant performance issues, and the software was substantially rewritten by Lee Daniel Crocker. Later on, Brion Vibber would take up the role of release manager and most active developer.
Since the release of the first version of Manske's script, the software had been given multiple nicknames representing the state of development—"the PHP script", "phase II", "phase III", "the new codebase"—but no product name. After the [[Wikimedia Foundation]] was announced on [[June 20]] [[2003]], the name "MediaWiki" was coined by Wikipedia contributor Daniel Mayer as a play on "Wikimedia," <ref>{{cite web|url=http://mail.wikipedia.org/pipermail/wikipedia-l/2003-July/010966.html|last=Mayer|first=Daniel|accessdate = 2006-06-29|title=Phase IV, Wikibooks.org/.com and WikimediaFoundation.org/.com (was Wikis and uniformity)|work=Wikipedia-L mailing list archives}}</ref> and the name was gradually phased in beginning in August 2003. The name has frequently caused confusion due to its intentional similarity to the "Wikimedia" name (which itself is similar to "Wikipedia"). Nevertheless, "MediaWiki" has become a recognizable brand, with a [[Google]] search yielding over 370 million results on the name in September 2006.
The product logo was created using a flower photograph taken by [[Florence Nibart-Devouard]], and was originally submitted to an international logo contest for a new Wikipedia logo held in summer 2003. The logo came in third place, and was chosen to represent MediaWiki instead of Wikipedia, with the second place logo used for the [[Wikimedia Foundation]] and the first place logo for Wikipedia itself.
=== Release history ===
[[Image:mediawiki-edit.png|thumb|300px|Editing interface of MediaWiki 1.7 as rendered in [[Firefox]], showing the edit toolbar and some examples of wiki syntax.]]
[[Image:mediawiki-edit.png|thumb|300px|Editing interface of MediaWiki 1.7 as rendered in [[Firefox]], showing the edit toolbar and some examples of wiki syntax.]]
Line 102:
Line 110:
|}
|}
== Key features ==
== ==
[[Image:Popup-preview.png|thumb|300px|Users can configure custom JavaScript that is executed on every pageview. This has led to JavaScript tools that users can "install", such as ''navigation pop-ups'', small previews of articles which are shown when hovering over link titles.]]
[[Image:Semantic-mediawiki.png|thumb|300px|[[Semantic MediaWiki]] is one of the most powerful extensions to the MediaWiki core functionality. It provides the ability to add structured and searchable relations and attributes to wiki pages (cf. [[semantic web]]).]]
[[Image:mediawiki-opensuse.png|thumb|300px|Some companies use MediaWiki as a [[content management system]]. [[Novell]] has deployed it for several of its product websites, including [[openSUSE]].]]
One of the earliest differences between MediaWiki (and its predecessor, UseModWiki) and other wiki engines was the use of "free links" instead of [[CamelCase]]. Where, in a typical wiki, you would have to type a text like "WorldWideWeb" to create a link to a page about the [[World Wide Web]], links in MediaWiki are created by surrounding words with double square brackets, and any spaces between them are left intact, e.g. <nowiki>[[World Wide Web]]</nowiki>. This change was logical for the purpose of creating an encyclopedia, where accuracy in titles is very important.
MediaWiki provides many features beyond hyperlinks for structuring content. One of the earliest features is ''namespaces''. One problem for Wikipedia had long been the separation of encyclopedic content from discussions surrounding it, as well as personal pages about encyclopedia editors. Namespaces are prefixes before a page title (like "User:" or "Talk:") which allow a page to exist under multiple names, but serving different purposes depending on their prefix. For instance, a page "<nowiki>[[The Terminator]]</nowiki>" could describe the 1984 movie starring [[Arnold Schwarzenegger]], while a page "<nowiki>[[User:The Terminator]]</nowiki>" could be a profile describing a user who chooses this name as a pseudonym. More commonly, each page has an associated "Talk:" page which can be used to discuss its contents. A list of the namespaces and their associated functionality is found below.
Namespaces can be viewed as [[file folder|folders]] which separate different basic types of information or functionality. While new namespaces can be added, the number of namespaces in a wiki is typically relatively low.
{| class="Certified Humane"
!Restaurants that use CHRH products on their menu:
|Prefix to identify functionality provided by MediaWiki that is not regular page content. For instance, "Special:Recentchanges" shows the most recent activity in the wiki. Cannot contain regular wiki pages.
New York, NY
|[http://www.5ninth.com]
|-
|-
|Media:
|Hunter's Head Tavern
|Prefix for linking to any uploaded media file directly, i.e., without passing through a file description page. Cannot contain regular wiki pages.
Upperville, Virginia
|(540)592-9020
|-
|-
|''No prefix''
|Chirs Cosentino; Incanto
|The primary "article namespace" where content is stored if the page title does not have a namespace prefix.
San Francisco, CA
|[http://www.incanto.biz]
|-
|-
|User:
|Robert Weidmaier; Marcel's
|Personal profiles of wiki users.
Washinton, D.C.
|[http://www.marcelsdc.com]
|-
|-
|Project:
|Brian McBride; Melrose
|Typically named after the project itself, e.g. "Wikipedia:". Policies, processes and project background.
Washinton, D.C.
|(202)419-6750
|-
|-
|Image:
|Cathal Armstrong; Restaurant Eve
|Description pages for images and other files. Associated with special functionality related to files.
Alexandria, Virginia
|[http://www.restauranteve.com]
|-
|-
|MediaWiki:
|Patricia Yeo; Sapa
|Editable user interface messages. Only editable by sysops.
New York, NY
|[http://www.sapanyc.com]
|-
|-
|Template:
|Josh DeChellis; Sumile
|Reusable blocks of information, which can optionally be parametrized.
New York, NY
|[http://www.sumile.com]
|-
|-
|Help:
|Cesare Lanfranconi; Tosca
|Documentation. Has to be manually imported when setting up a new wiki.
Washington D.C
|[http://www.toscadc.com]
|-
|-
|Category:
|Colin Alveras; The Tasting Room
|Descriptions for categories added to articles that can also be used to build category hierarchies (by categorizing the category page).
New York, NY
|[http://www.thetastingroomnyc.com]
|-
|-
|Talk:, User talk:, Project talk:, Image talk:, etc.
|Chef Angelo Sosa, New York, NY
|Various discussion namespaces associated with the above primary namespaces. There are no talk namespaces for "Media:" or "Special:". User talk pages come with a special notification feature when new text is added to them.
|
|}
|}
In addition to namespaces, pages can be structured using ''subpages''. This simple feature provides automatic backlinks from a page of the pattern <nowiki>[[Page title/Subpage title]]</nowiki> to the component before the slash (in this case, "Page title"). Finally, MediaWiki supports user-created ''categories''. These are similar to [[Tag (metadata)|tags]] used in many web applications, but hierarchical and descriptive. In large wikis like [[Wikipedia]], very complex hierarchies have grown using this system without any central planning.<ref>Compare Erik Zachte's [http://stats.wikimedia.org/EN/CategoryOverviewIndex.htm category trees] generated from Wikipedia category information.</ref>
The entire MediaWiki user interface can be edited through the wiki itself by users with the necessary permissions (typically so-called "administrators"). This is done through a special namespace with the prefix "MediaWiki:", where each page title identifies a particular user interface message. The "MediaWiki:" namespace was also originally used for creating custom text blocks that could then be dynamically loaded into other pages using a special syntax. This content was later moved into its own namespace, "Template:". Templates are text blocks which can be dynamically loaded inside another page whenever that page is requested. Templates support [[parameter]]s, so that parts of the text can be substituted for each specific use case.
Templates have found many different uses, such as:
* Identifying problems with a Wikipedia article by putting a template (also called "tag" in this context) such as <nowiki>{{Disputed}}</nowiki> on the article. This template will then output a graphical box stating that the article is disputed, and also categorize it so that articles of this nature can be located.
* Creating complex table layouts which are used consistently across multiple pages, and where only the content of the tables gets inserted using template parameters.
* Sending users standard messages when they are blocked from editing, when their behavior is considered inappropriate, and so on. For this purpose, ''template substitution'' can be used: Instead of loading the template contents dynamically whenever the page is loaded, the contents of the template are inserted exactly once into the target page, similar to a [[copy and paste]] operation.
As the name ''MediaWiki'' suggests, the software has become ever more powerful at dealing with a wide variety of uploaded media files. Its richest functionality is in the area of images, where image galleries and thumbnails can be generated with relative ease if the software is set up correctly. There is also support for [[EXIF]] [[metadata]]. The use of MediaWiki to operate the [[Wikimedia Commons]], one of the largest [[free content]] media archives, has driven the need for further functionality in this area.
On the level of editing, MediaWiki currently provides no native [[WYSIWYG]] support, though it does come with a graphical toolbar for simplifying the process of learning the wiki syntax. To make editing long pages such as comprehensive Wikipedia articles easier, MediaWiki supports editing only a small subsection of a page (as identified by its header). In addition, the wiki software comes with a simple interface to allow the transparent use of external editors for uploaded files and wiki pages.
MediaWiki also supports rich content generated through specialized syntax. For example, the software comes with support for rendering mathematical formulas using [[LaTeX]] and a special parser written in [[OCaml]]. Similar functionality for other content, ranging from graphical timelines over mathematical [[plotting]] and [[musical score]]s to [[hieroglyphics]], is available in the form of extensions.
MediaWiki comes with several so-called "special pages" to analyze relations between pages and page content, while also providing importer and exporter utilities. Additional software to analyze page content, such as Erik Zachte's "[[Meta:Wikistats|Wikistats]]" toolset, is available. An experimental [[API]] for external access to the wiki is under development, and a variety of scripts can be used to create "bots" which automatically perform specific tasks on a MediaWiki installation.
If the feature is enabled, users can also customize their stylesheets and configure client-side [[JavaScript]] to be executed with every pageview. On Wikipedia, this has led to a large number of additional tools and helpers developed through the wiki and shared among users. For instance, Wikipedia user "Lupin" created a custom JavaScript tool that shows previews of articles when the user hovers over links, and also provides shortcuts for common maintenance tasks.<ref>{{cite web| url = http://en.wikipedia.org/wiki/Wikipedia:Tools/Navigation_popups| title = Wikipedia:Tools/Navigation popups | accessdate = 2006-06-30 | author = "Lupin"}}</ref>
While MediaWiki comes with a basic set of features related to restricting access and defining user groups, page access control does not tend to be given high priority in development. For instance, it is not possible to define the access permissions to pages on a per-namespace basis. Here, wikis like [[TWiki]] and [[MoinMoin]] provide more power by supporting advanced security mechanisms like [[Access Control List]]s.
Because it is used to run one of the highest traffic sites on the World Wide Web, [[Wikipedia]], MediaWiki performance and [[scalability]] have been highly optimized. MediaWiki supports [[Squid cache]]s, [[load balancing (computing)|load balanced]] database replication, client-side caching, [[memcached]] or table-based caching for frequently accessed processing or query results, a simple static file cache, feature-reduced operation, revision compression, and a job queue for database operations.
== What do the standards require? ==
MediaWiki may be overdimensioned for small-scale usage, where its large feature set and use of a database backend take a performance toll. On the other hand, the software is suitable for the operation of large scale [[wiki farm]]s, such as the Wikimedia project and language family. However, MediaWiki comes with no built-in functionality to manage such installations. <br clear="all"/>
The Animal Care Standards require that livestock have access to clean and sufficient food and water; that their environment is not dangerous to their health; that they have sufficient protection from weather elements; that they have sufficient space allowance in order for them to move naturally; and other features to ensure the safety, health and comfort of the animal. In addition, the standards require that managers and caretakers be thoroughly trained, skilled and competent in animal husbandry and welfare, and have good working knowledge of their system and the livestock in their care.
== See also ==
== How were the Animal Care Standards set? ==
{{portalpar|Free software}}
*[[GetWiki]]: a [[Fork (software development)|fork]].
The standards were created by a team of Animal Scientists, and Veterinarians with expertise in farm animal issues During creation of the standards, the team reviewed the latest research and consulted established standards, such as those in use by the Royal Society for the Prevention of Cruelty to Animals (RSPCA) in England, and other standards and guidelines recognized for the proper care of animals. Input was also obtained from producers.
*[[IpbWiki|IpbWiki - Integration of Invision Power Board with MediaWiki]]
*[[List of content management systems]]
*[[Comparison of wiki software]]
== References ==
== External links to Humane Organizations ==
<div class="references-small">
*[http://www.animalpeoplenews.org/]
<references/>
*[http://www.arlboston.org/]
</div>
*[http://www.ASPCA.org]
*[http://www.atlantahumane.org]
*[http://www.dbqhumane.org/]
*[http://www.flaglerhumane.org/]
*[http://www.hawaiianhumane.org/]
*[http://www.carr.org/humane]
*[http://www.hsco.org/]
*[http://www.HSUS.org/]
*[http://www.verobeach.com/HumaneSociety]
*[http://www.kauaihumane.org/]
*[http://www.mcpaws.org/future_mcpaws.htm]
*[http://www.MSPCA.org/]
*[http://www.mauihumane.org/]
*[http://www.monmouthcountyspca.org/]
*[http://www.nashvillehumane.org/]
*[http://www.peninsulaspca.com/]
*[http://www.potterleague.org/]
*[http://www.SPCAEC.com/]
*[http://www.spcala.com/]
*[http://www.vfns.org/]
*[http://www.whatcomhumane.org/]
*[http://www.wspa-usa.org/]
== External links ==
*[http://www.mediawiki.org/ MediaWiki official homepage]
*[http://sourceforge.net/projects/wikipedia/ Download and project page] on [[SourceForge]]
*[[meta:MediaWiki|MediaWiki on the Meta-Wiki]], [[Wikimedia|Wikimedia's]] [[meta]] website.
**[[meta:Help:Contents|User's guide]]
**[http://www.mediawiki.org/wiki/Sites_using_MediaWiki Sites using MediaWiki]
*[http://pgfoundry.org/projects/wikipedia A Project engaged to use PostgreSQL as the backend database]
*[http://www.mwusers.com A support forum for MediaWiki users and webmasters]
*[http://www.richardkmiller.com/blog/archives/2006/05/password-protecting-mediawiki-with-mod_auth_mysql Password protecting MediaWiki with mod_auth_mysql]
HUMANE FARM ANIMAL CARE is the independent non-profit organization that conducts regular inspections and administers the “Certified Humane Raised & Handled” program. Participating businesses must pass an initial inspection as well as annual re-inspection to remain part of the Certified Humane Raised & Handled program.
The Certified Humane Raised & Handled Label is a consumer certification and labeling program.When you see the Certified Humane Raised & Handled label it means that an egg, dairy, meat or poultry product has been produced with the welfare of the farm animal in mind. Food products that carry the label are certified to have come from facilities that meet precise, objective standards for farm animal treatment.
A team of veterinarians and animal scientists developed the Animal Care Standards to ensure that producers and processors keep animals in conditions that have met high standards of animal care:
• Allow animals to engage in their natural behaviors
• Raising animals with sufficient space, shelter and gentle handling to limit stress
• Making sure they have ample fresh water and a healthy diet without added antibiotics or hormones
Under the system, growth hormones are prohibited, and animals are raised on a regular diet of quality feed free of antibiotics. Producers also must comply with local, state and federal environmental standards. Processors must comply with the American Meat Institute Standards, a higher standard for slaughtering farm animals than the Federal Humane Slaughter Act.
A BETTER CHOICE
The quality of the meat, poultry, egg and dairy products depends, at least in part, on the quality of care farm animals receive. The Certified Humane Raised & Handled program lets consumers choose products from businesses that are providing humane conditions for the animals in their care.
Editing interface of MediaWiki 1.7 as rendered in Firefox, showing the edit toolbar and some examples of wiki syntax.File:Mediawiki-gallery.pngImages can be arranged in galleries, a feature that is used extensively for Wikimedia's media archive, Wikimedia Commons.
The Animal Care Standards require that livestock have access to clean and sufficient food and water; that their environment is not dangerous to their health; that they have sufficient protection from weather elements; that they have sufficient space allowance in order for them to move naturally; and other features to ensure the safety, health and comfort of the animal. In addition, the standards require that managers and caretakers be thoroughly trained, skilled and competent in animal husbandry and welfare, and have good working knowledge of their system and the livestock in their care.
How were the Animal Care Standards set?
The standards were created by a team of Animal Scientists, and Veterinarians with expertise in farm animal issues During creation of the standards, the team reviewed the latest research and consulted established standards, such as those in use by the Royal Society for the Prevention of Cruelty to Animals (RSPCA) in England, and other standards and guidelines recognized for the proper care of animals. Input was also obtained from producers.
