Skip to content

KCRW Wins a Webby!

April 30, 2015

KCRW Wins Webby Award

Kudos to KCRW for the vision, Hard Candy Shell for the design, the Plone content management system for providing a great platform, lead developer Alec Mitchell, and Jazkarta team members Cris Ewing, Carlos de la Guardia, David Glick, and me. We are very proud to have been a part of it.

You can read more about the project on this blog post.

Replacing Faculty Staff Directory

April 7, 2015

Faculty Staff Directory is a venerable Plone add-on that integrates with Plone’s users and groups infrastructure and provides content types for creating and organizing personnel directories within educational institutions. It adds academic profile information such as job title and contact details, and provides an area for personnel to add their own bibliographies, as well as pages and other content. Faculty can be associated with departments, committees and specialties, and these groupings can then be used to control access and editing permissions throughout the site.

UW Radiology Faculty Profile Example

Originally released in 2007, FSD is an “old-style” Archetypes add-on that is currently in use by many universities and colleges. As Plone moves away from Archetypes and embraces the Dexterity content type framework, the Plone community needs to decide what to do about old but important add-ons like FSD.

A group of concerned Plone citizens convened an open space at the Plone Conference last October to discuss this. There was clear consensus on the way forward: replace FSD with a Dexterity-based add-on and provide a migration path for existing FSD content.  We also agreed that the new FSD should be based on an existing add-on rather than starting from scratch, and we identified several existing add-ons as potential candidates:

Two months later, Jazkarta was tasked with recommending a replacement for an FSD-like custom add-on that was developed at NYU’s Institute for the Study of the Ancient World to manage faculty information.

ISAW Faculty

This provided the perfect opportunity to assess the above set of candidates.

Cris Ewing did the evaluation and concluded that collective.roster is the only package suitable as the basis for an FSD replacement. does not allow the extended profile data that is needed. collective.contacts is Archetypes-based. ibme.persondirectory is a bit too bare-bones and does not provide enough of a starting point to be reasonably useful on its own. collective.workspace is more like a building block (for example see this post about using it to build a badge system), and is discussed further below.

collective.roster is dexterity-based so features can be easily added with behaviors. It has a nice viewlet-based system for extending views. It can use dexterity.membrane to provide integration with Plone’s membership system. Groups are currently implemented as a simple keyword behavior, but it could use collective.workspace to group-based rights management.

In short, we have a winner in collective.roster. Instead of implementing a specific use case it provides an easy way to add features via behavior add-ons. This building block approach is what gives the Dexterity framework its power. The next step on the path to replacing Faculty Staff Directory will be to combine collective.roster, dexterity.membrane, collective.workspace, and other add-ons to provide the FSD features that users rely on.

Adding SCORM packages to Open edX via SCORMCloud and LTI

February 8, 2015

Do you want to be able to use existing training content in an Open edX course? SCORM – the “Sharable Content Object Reference Model” – is a set of interoperability standards for e-learning software that governs how online learning content and Learning Management Systems (LMSs) communicate with each other. It allows units of online training material to be shared across e-learning systems.

Open edX doesn’t support SCORM natively yet, but here at Jazkarta we’ve successfully integrated SCORM Cloud and Open edX. SCORM Cloud is a third party service that wraps e-learning content in a SCORM dispatch package that can be embedded into an LMS. The gist of this integration is as follows:

  1. Export a learning module from your e-Learning authoring tool as a SCORM package.
  2. Upload SCORM package to SCORM Cloud.
  3. Configure SCORM Cloud dispatch to serve them up as LTI (Learning Tools Interoperability) components.
  4. Use the LTI component in Open edX to add these packages, which are actually being hosted on SCORM Cloud.

The user doesn’t need to login again as this is transmitted via LTI, and the activity is passed back into edX for grading purposes.

Here is a detailed how-to for people who would like to duplicate our work. I found some sample courses in this blog article and used the “Picture Perfect_Simulation Sample” course. Open that course in Adobe Captivate and follow these instructions for prepping, uploading, and using this sample in Open edX. (You can download Adobe Captivate 8 here – a free 30 day trial is available by clicking the ‘Try’ link on that URL.)

Mark interactive elements as graded and assign points


For each interactive element that you want graded, you need to click on the element, click on the Properties icon (in the upper right corner of the screen), mark it as graded in the properties panel, assign a point value that will count towards the grade, and check the Report Answers checkbox.

Set project end action to close project


In Publish Settings -> Project -> Start and End, set the Project End Action to “Close project” (I think it defaults to Stop project). That way the window showing the assessment will automatically close when it’s done playing.


In Publish Settings -> Project -> Quiz -> Reporting, set the Standard form to SCORM 2004, and then click the Configure button.

Give the course an identifier and title


You can optionally give your course an identifier and title. If you skip this step, then all of your courses will have the default identifier “Captivate E-Learning Course” and it will be hard to differentiate between the different courses.

Export from Captivate


From the File menu, choose Publish… and make sure the eLearning output value is set to SCORM 2004, which you should have already set in the previous step. Click the Publish button and it will create a .zip file in the location you specified.

Upload to SCORMCloud


Create a free account at and from the Add Content section of the dashboard, upload the .zip file that you just created.

Tell SCORM Cloud to make it available via LTI


Once the content has been uploaded, you need to create a dispatch that will be used to make it available via LTI.

Create a dispatch


If the first time, click Create New Destination.

Create a destination


Enter ‘Open EdX’ as the name. On subsequent times you can click Add Existing Destination and choose Open EdX. This name can really be anything – it doesn’t need to be ‘Open edX’.

Export dispatch as BLTI


From the Dispatch screen, click on the Dispatch that you just created, and under Export your dispatch, click the BLTI button

Capture the BLTI information


You should see a pop-up with information about the BLTI endpoint URL, key and secret key. Make a note of the URL, Key, and Secret that it displays

Enable LTI in your Open edX course


Login to edX Studio and go to your course, and select Settings -> Advanced Settings. For the Advanced Module List, add “lti” to enable adding LTI components to your course.

Add an LTI passport entry


On the same Advanced Settings page, scroll down to the section entitled LTI Passports, and add a new entry in the form:
lti_id:client_key:client_secret where the client_key and client_secret are the key and secret that you got when you made the BLTI dispatch in SCORM Cloud. The LTI ID can be anything (no spaces) – it’s just an identifier that will be used when we add an individual LTI component to our edX course.

So for our last example, it would be:


Note: you need to add a new entry for each course in SCORM Cloud that you want to embed in an edX course. It’s annoying that this is an extra step required for each item. Open edX assumes that an LTI provider will have one key/secret combo for all courses, but SCORM Cloud uses a different one for each course.

Add a new LTI component in your course


Go to your course outline: Content -> Outline and navigate to where you want to add the LTI component containing your SCORM Cloud exercise/quiz. Click the New Unit button.

Add an advanced component


If you’ve enabled Advanced Components for your course, you should see the Advanced Component button appear when you add a new unit.

Choose the LTI component


Edit the component to set the values


Configure the LTI component settings


For LTI Application Information, you can type “SCORM Cloud” or whatever you want in this field. For LTI ID, this needs to match exactly, the LTI ID that you used in the LTI passports entry. The LTI URL for SCORM Cloud should be set to

The Open in New Page setting should be set to True.

More LTI component settings


Make sure that you set Scored to be True and assign a weight that you want it to have on the total grade. You can also set a Display Name if you want.

Preview or Publish your changes


Once you’ve added the component, you need to click the Preview Changes button or Publish it to your course.

Login as a student and try the exercise


Now we can login as a student and test it out. When you navigate to the page, there is a link “View resource in a new window”. Click on this button to launch the SCORM Cloud exercise in a new window.

Take the exercise


You then take the exercise and SCORM Cloud is tracking your activity.

Complete the exercise


At the end of the exercise, it will compute a score for you, and if the score is above the threshhold to get a passing grade, then get a “Pass” grade.

See score in edX progress page


This grade is sent back into edX and can be seen on the student’s Progress page. Please note that these scores don’t match because I took a screenshot of a different student.


1. Make sure that your Open edX site is at an internet address that can be reached by SCORM Cloud. This means basic auth must be disabled and if you’re using SSL, that you have a real SSL certificate, not a self-signed certificate.

2. A fix to the edX code which parses the SCORM Cloud request handle a non-standard (well, old standard) XML namespace that it uses.

3. A fix for edX’s validation of the oauth signature (


Get involved

We invite you to join the conversation on the edx-code mailing list about SCORM support in edX, and feel free to reach out and contact us if you are looking for professional help with edX.

Or if you want to take Open edX for a test-drive, you can get a free trial from our partner Appsembler.

The Many Options for Hosting a Plone Site

February 4, 2015

Over the last year there has been a lot of work on hosting tools in the Plone community. Here at Jazkarta, most of our client’s sites are hosted using Amazon Web Services and OpsWorks because this platform’s robust tool set and high level of flexibility is a good fit for sites like The Mountaineers and KCRW. But there are many other options, especially for smaller sites.

To provide a forum to discuss all the recent activity, I hosted a panel discussion on Plone hosting at the 2014 Plone Conference. We covered Ansible, OpsWorks, Nix, Docker, OpenVZ, Heroku, and some PaaS providers. The slides from the session provide lots of information about all these options, including links, pros and cons.


You can also watch a video of the panel discussion on Vimeo.


How to Create a Badge System in Plone

January 30, 2015

With thousands of volunteers taking and teaching courses, climbing peaks, and donating time and money for environmental advocacy and youth programs, The Mountaineers needed a way to recognize their members’ contributions and skill levels. To let them do this, we created a badge system for their Plone website:

Mountaineers Badges

Members who complete milestones like graduating from a course or summiting a set of peaks are awarded a badge, which shows on their profile page.

Mountaineers Profile Badges

This feature was easy to implement because of another Plone add-on, collective.workspace, which we had already created to provide roster functionality for The Mountaineers’ courses, activities, and committees, allowing each participant’s role, registration status, and other information to be managed. Here are instructions for how to create a badge system on your own Plone site with the help of collective.workspace. The screenshots are from a Plone 5 site but this will also work in Plone 4.

  1. Add collective.workspace to your buildout:
    eggs = collective.workspace
  2. Start Plone, go to the Add-ons control panel in Site Setup, and activate collective.workspace.

  3. Go to the Dexterity Types control panel and add a Badge content type.
  4. Add an image field to hold the badge image.
    Screen Shot 2015-01-30 at 10.42.39 AM
  5. Go to the Behaviors tab and enable the “Team workspace” behavior.
    Screen Shot 2015-01-30 at 10.44.21 AM
  6. Now add a Badge to the site.
    Screen Shot 2015-01-30 at 10.47.51 AM
  7. There’s now a Roster link on the toolbar when viewing the badge.
    Screen Shot 2015-01-30 at 10.48.47 AM
  8. On the roster, we can add a user, indicating that they have been granted the badge.
    Screen Shot 2015-01-30 at 10.52.57 AM
    (Position is more useful for a committee roster. Selecting the Admins group gives the user permission to help manage this roster.)
  9. Now the user shows up on the badge roster.
    Screen Shot 2015-01-30 at 10.53.29 AM
  10. This isn’t particularly useful unless we make the user’s badges show up somewhere. Customize the author template and add this TAL:
      <tal:b repeat="badge python:context.portal_catalog(portal_type='badge', workspace_members=username)">
        <img src="${badge/getURL}/@@images/image/thumb" class="image-left" title="${badge/Title}" />
      <br style="clear: both;" />
  11. Now the assigned badges show up on a user’s profile!
    Screen Shot 2015-01-30 at 11.12.03 AM

That’s it! Enjoy your new badge system!

Another Plone Site on AWS OpsWorks

January 26, 2015

Congratulations to YES! Magazine on the launch of their redesigned website!

YES! Magazine

This award winning, ad-free, non-profit online (and print) magazine for progressive thinkers runs on Plone, our favorite CMS. Originally launched in 2009 by our friends at Web Collective and Groundwire (RIP), this is the first redesign the site has had since then. The focus was squarely on mobile usability (since 40% of site visits are now mobile) and social engagement. It looks great!

All the planning, analysis, and design work for the new site was done in-house; the Diazo theme implementation and site upgrade were done by Bryan Wilson, formerly of Web Collective. We helped a little bit as well: the YES! technical staff decided to host the new site on Amazon’s AWS cloud platform using the OpsWorks recipes for Plone and Python developed by Alec Mitchell. Alec walked Bryan through some of the technical details of the deployment stack and he was off and running.

We’re very pleased our Plone-OpsWorks contributions helped YES! Magazine!

Botany on the Web

January 8, 2015

Here at Jazkarta we really enjoy innovative uses of web technology, especially in the service of non-profit and educational projects. Go Botany! and Go Orchids! were two such projects – they harnessed Javascript, Python, Django, and Solr to create user friendly plant identification tools. Go Botany! was created by the New England Wild Flower Society with funding from the National Science Foundation, and it was awarded the 2013 NEEEA Maria Pirie Award for Environmental Education Program of the Year. This major award  recognizes outstanding environmental education programs that demonstrate innovation and creativity, have been implemented broadly, and can easily be replicated in other regions.

As proof of that last point, Go Orchids! – created by by the North American Orchid Conservation Center – was able to adopt the Go Botany! code base (which had been released as open source) and create a site focused on orchid identification in a relatively short period of time. Last fall Go Orchids! produced a video introducing the tool to new users:


See our earlier Go Botany! blog post for more information about the technology behind these sites. For an in-depth look at the system architecture, watch this Djangocon 2014 presentation by Brandon Rhodes (start at minute 18:54).

We are so pleased to have played a part in both these projects. And we’d love to do more of them! Go Orchids! contributed improvements to the code base that make the application more flexible and easier to adapt. Any organizations interested in having a plant identification website tailored to a particular region or taxon should contact us or the New England Wildflower Society.


Get every new post delivered to your Inbox.

Join 339 other followers

%d bloggers like this: