Documenting your Sakai instance as part of the Sakai community
Sakai JIRA production/pilot deployment data project
People learning about and working with Sakai often ask about the choices piloting and production schools have made with respect to deployed hardware and software. In an effort to make this information more readily available to those in the community and beyond, there is now a Sakai Production-Pilot deployment project in our Jira site (http://bugs.sakaiproject.org
), which is used to collect and summarize data about Sakai installations world-wide.
Your assistance in helping provide a more complete picture of Sakai deployments is appreciated. Such data is particularly useful for potential adopters who want to know both who is using Sakai and how it is being deployed. The data collected also provides useful information for the Sakai Community as whole as individual organizations share details on their respective software, hardware and configuration decisions.
It is important to note that the implementation data is limited to physical installations and represents but a subset of organizations who have adopted Sakai. Many institutions utilize Sakai in a shared environment such as that provided by the Etudes Consortium or the Appalachian College Association. Such organizations are not included in the data set although the total number of organizations served by each Sakai installation is recorded.
The current online format is tab-based and information is divided between the following tabs:
- General
- Environment
- Hardware
- Integration
- Map mashup (latitude/longitude coordinates, see below)
For an example of the approach see Whitman College's entry:
http://bugs.sakaiproject.org/jira/browse/PROD-7
(note: other entries may display fewer tabs/fields as JIRA hides tabs/ fields that are blank).
The project can be accessed from the JIRA dashboard (key: PROD) and is viewable by all. Several custom filters have also been created that provide subsets of the available data. For a list of all production/pilot installations see:
http://bugs.sakaiproject.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11294.
Getting involved in the production/pilot data sharing project is entirely voluntary. There is no requirement that you must share implementation details with other members of the community or the wider world.
To have your installation(s) added to the project please contact 
Anthony Whyte, Sakai Community Liaison.
Production/pilot deployment map
On the main http://sakaiproject.org page, a map is displayed indicating where Sakai is deployed around the world. Please consider adding your Sakai installation(s) to our Google map mashup:
http://www.sakaiproject.org/index.php?option=com_wrapper&Itemid=588
To add entries to the map, construct an XML element that includes the
following attributes and values:
- lat (latitude)
- lng (longitude)
- title (site URL)
- country (country code)
- text (organization name)
- color (icon: blue=production, purple=pilot, green=partner, orange=commercial affiliate, red=community server)
The chunk of XML should resemble the following:
<marker lat="41.19221885042551"
lng="-111.94313049316406"
title="http:
country="us"
status="production"
text="Weber State University"
color="blue" />
You can test a single entry by putting the values on the commmand line as follows:
An organization may submit more than one entry. Indeed, some Sakai organizations have multiple entries indicating, for instance, their partner status, their pilot/production status and their hosting of a community server. Once you are satisfied with your XML send your entry/entries to Anthony Whyte, Sakai Community Liaison.
