License Management in Bright

May
2015
04

posted by | Comments Off on License Management in Bright

Developing e-commerce solutions for SCORMCloud is an emerging business for Aura Software, and we are happy to hear that Rustici Software AKA SCORMCloud will feature Bright in a business case on ecommerce to be published on the scorm.com website. I just have to get around to writing it….

Since we’ve been talking to Rustici about ecommerce a lot, we have had the opportunity to talk to many prospects interested in using the Bright + SCORMCloud + WordPress + WooCommerce system.

One of things that has fallen out of these conversations is the need for license management in Bright, wired straight into the shopping cart.

The idea here is that a customer might want to buy a 1000 seat license in a single transaction, and then distribute the license internally [or externally] to their organization. You also might want to combine licenses for multiple courses into single transaction, and of course, there has to be reporting.

It seems that many learning content producers make these kinds of deals already, in some cases with considerable manual work or one-off coding. This is something that we feel we can make as seamless as regular single-user course buys already are in the Bright WooCommerce Integration Bridge. Coming soon!

How will it work?

The thinking at the moment is that during checkout, a custom checkout field would be provided for the cart:

license

 

When this is set, instead of an actual course registration being generated via the completed purchase, a license key will be generated and attached to the user’s order.  The license data will be written into the Bright server, storing the associated courses and the # of seats available.

This key can be used in the following fashion:

  • A user can attach this key to their user profile, and we will provide extensions that will allow user profile fields to be mapped to license keys.
  • Thus, when a license key is added to a user’s profile, an API call will be generated which will associate the user with the license.  This call will have the side effect of generating the appropriate registrations for the user.
  • By using Bright templates that require an existing course registration, the net effect of this will be to grant access to users who have added the appropriate license keys.
  • The Bright API will insure that the seat limits associated with the key is enforced.

This model supports:

  • reporting by license key
  • multiple license keys per user.