Appropedia:Status

From Appropedia
Jump to: navigation, search

Default.png    See also the Status  category.
for subtopics, how-tos, project pages, designs, organization pages and more.


This is a proposed Appropedia guideline. You can edit it, or discuss it on the talk page or at the Appropedia policy discussion page.
For now, this should be considered an essay by one or more Appropedians, and not as a policy or guideline.


Often the investment cost of recreating or building an appropriate technology is high. To overcome this cost, first, there must be adequate information and schematics for a user to trust that there is due diligence in a given design and that the designed device can perform to specifications. Second, particularly for small communities with limited access to funding, there must be a successful history of implementation before an investment in time and resources to employ an innovation can be made. This category is the beginning of such a functionality for appropedia. By following the instructions below you can add a status tag to your design to help potential users mitigate the risk of an investment in your technology.

Status Tags[edit]

The status of a particular appropriate technology (AT) can be shown easily by adding the following tags to the top of an AT project page: e.g. {{status-design}}. The hierarchy of deployment runs from design, modeled, prototyped, verified, and deployed. The coloring scheme is meant to denote the amount of risk with ATs that have only been designed in red - those modeled in orange, prototyped in yellow, verified in light green and deployed in dark green. As often an AT will have several tags associated with it - they are best kept together in a Status Box. You can use AppropediaFox to easily add the Status Box and tags to your project.

Instructions for use[edit]

It is used in this way:

 {{Statusboxtop}}
 Status tags go here in template format.
 {{boxbottom}}
 

Example:

This code

{{Statusboxtop}}
{{status-base|yellow|[[:Category:Status#Status:Prototype{{!}} prototyped.]]}}
You can help by contributing to the next step in this [[OSAT]]'s [[:Category:Status|status]].
{{boxbottom}}

Produces this:

Status
This OSAT has been prototyped.

You can help Appropedia by contributing to the next step in this OSAT's status.



Example:

This code

{{Statusboxtop}}
{{status-design}}
{{status-model}}
{{status-prototype}}
{{status-verified|Name of organization}}
{{status-deployed|Whom|How many|Where}}
You can help Appropedia by contributing to the next step in this [[OSAT]]'s [[:Category:Status|status]].
{{boxbottom}}

Produces this:

Status
This OSAT has been designed but not yet tested - use at own risk.
This OSAT has been modeled.
This OSAT has been prototyped.
This OSAT has been verified by: Name of organization.
This OSAT has been deployed by: Whom at least: How many times in: Where.

You can help Appropedia by contributing to the next step in this OSAT's status.



Status:Design[edit]

If your AT project has just been designed and you provide complete instructions for construction add the following template to the top of the page: {{status-design}} - it will create this:

This OSAT has been designed but not yet tested - use at own risk.



Status:Model[edit]

Often ATs can be numerically modeled or simulated before actual construction in order to test the viability. If the AT project has been modeled add the following template to the top of the page: {{status-model}} - it will create this:

This OSAT has been modeled.



Status:Prototype[edit]

After your AT has been actually built and prototyped add the following template to the top of the page: {{status-prototype}} - it will create this:

This OSAT has been prototyped.



Status:Verified[edit]

  • Similar to an online store (e.g. Amazon.com), there must be a degree of product information accompanied by successful customer reviews or testimonials before one can be expected to invest. Appropedia must support a review and rating system for documented ATs. Through user reviews and scoring, successful innovations can be quickly referenced while unproven or unwanted content can be easily avoided by screened sources, and by display ranking.
  • Here we will begin this process with an organizational certification system to convey trust and overcome barriers to innovation diffusion and information adoption. Similar to a Consumer Reports stamp of approval, organizations specializing in particular appropriate technologies are given certification power. This both delegates a certification process and provides organizations a similar incentive to build, highlight, and market, their own set of successful innovations. For example, certain innovations may be Demotech, Practical Action, Peace Corps or Engineers Without Borders certified. This creates a currency for organizational participation and allows users familiar with or trusting of a specific organization to search through their proven, successful, certified technologies.
  • Ideally designs are built and prototyped by organizations that are NOT the creating organization.(Although in some cases such as those developed by Practical Action -- the organization itself holds considerable trust in the technical area).
  • After your AT has been actually built/prototyped and tested by a third party add the following template to the top of the page: {{status-verified}} - it will create this:
This OSAT has been verified by: Name of organization.




There can be multiple Status-Verified tags on a given page - as many organizations may verify that a technology is appropriate and functional in different contexts.

Status:Deployed[edit]

This is the most valuable status indicating that the AT has been deployed. After your AT has been actually deployed add the following template to the top of the page: {{status-deployed}} - it will create this:

This OSAT has been deployed by: Whom at least: How many times in: Where.



Again the Status-Deployed tag can be used more than once for a given technology as many people from around the world begin to use it.

Other Status Tags[edit]

See also[edit]