Scriptapedia/Creating and Contributing a Script to ''Scriptapedia''

This section provides an introduction on how to create and edit/contribute scripts to Scriptapedia. Scripts can be created for any number of reasons including documenting a practice that has not yet appeared in Scriptapedia, needing to adapt a script in such a way that the script differs enough from the original authors, and inventing a new script to meet some need in group model building practice.

Elements of a script
One of the initial developments for Scriptapedia was defining a set of fields that could serve to organize elements of scripts. The following list provides a brief introduction to those elements. The current listing is used for Scriptapedia and revisions from using scripts.


 * Context and purpose of the script: The context and purpose of the script refers to when one might use the script and for what reason. This is usually a brief statement of no more than few sentences. The aim is to provide the potential user of the script with a concise statement about when and why they might consider using the script.
 * Status: The status of a script is either established practice, promising practice, or under development. Established practices are scripts that have been repeatably used by multiple teams to achieve predictable outcomes. Promising practices are scripts that have been reputably used by a single team, but not yet independently replicated by another team or group with similar results. Under development refers to scripts that currently being created and may be incomplete or experimental in nature.
 * Primary nature of group task: The primary group task at any time can be distinguished as either convergent, divergent, evaluative, or presentation. Convergent activities have a general arc of consolidating ideas while divergent activities generate ideas. Evaluative exercises force participates to prioritize and make choices and are, in some ways, similar to convergent tasks. Presentation exercises involve didactic presentations to participants on specific skills or insights.
 * Time: The time that a script typically takes should be considered and divided into three periods: preparation before the session, the actual clock time during the session, and the time available for follow.
 * Materials: This lists the materials and equipment needed to successfully complete the script (e.g., markers, paper, data projector). Be aware that materials universally available in one setting may be harder to come by in other settings.


 * Inputs: The outputs from other scripts that serve as an input to this script (e.g., a list of variables from a "Graphs over Time" script.


 * Outputs: The outputs from this script that other scripts can use.


 * Roles: A list of the different roles required along with minimum skill level needed to complete the skill successfully.


 * Steps: An enumerated list of steps describing how to prepare, facilitate, and complete the script.
 * Evaluation Criteria: A list of observable outcomes that would indicate that the script is productive and generating results in a way that would be consistent with an experienced user of the script. If the outputs are visual in nature (e.g., a CLD), it can be helpful to have a set of pictures illustrating the results. Ideally, there are multiple examples by different groups facilitated by different facilitators.
 * Authors: The people or community who invented the script. If the script is based on a tradition of unknown origin, be explicit about this along with the location where the origin has been observed. This will help others find and update the authorship of the script. Note that simply documenting a script is not the same authorship (i.e., invention of the script).
 * History: Describe the history and motivation of the script. This becomes especially relevant when an existing script is modified for some specific reasons or limitations, but it can also used to describe the motivations and nature of the adaptions that led to a new script.
 * Revisions: This refers to changes with the existing script. Generally, it is unnecessary to include minor editorial or formatting changes. The primary focus is capturing revisions that represent incremental changes to a script to improve the script.
 * References: Any references cited should be listed here with the exception of other cross-referenced pages within  Scriptapedia .
 * Notes: This is an enumerated list of notes covering a variety of topics, including variations in facilitating the script and adaptations. This can include cultural adaptations or variations with introducing a specific exercise.

Choosing a status of scripts
Scripts generally fall into one of three categories of development of status: established scripts, promising scripts, and scripts under development.  Established scripts  refers to scripts that have been replicated by multiple teams independently and over time, and hence have not only demonstrated some consensus on what they are and how to facilitate them, but also yield reliable and generalizable results over a wide range of conditions. The general rule is that scripts that have been independently replicated over time by two or more teams meet this standard.

Promising scripts refers to scripts that have only been reliably implemented by one team. This can be because it is a relatively new script and has not had the opportunity to be replicated/tested by another team, or more simply because it is not an interesting or effective script as judged by other practitioners.

 Scripts under development  provides a place for people to share scripts when the scripts may be incomplete or works-in-progress, remain largely uninterested, or require an online collaboration to develop a script.

Review of scripts
Scripts are reviewed by the editorial team. In some cases, the changes are made directly and logged.

New scripts template
To create a new page for a script, add at the start of the page and then save. The latest version of the script template will then be automatically added and available for editing.