It’s official. We’re three for three in the Nashville Business Journal’s annual Best Places to Work contest. We’re proud to be the place people want to come work. It certainly makes it easier to bring on more great people and I love the fact that nobody seems to want to leave. Great people are the foundation of a great company and we have some of the best. I can’t want to see what they do next. The post Three For Three appeared first on SCORM - .

The past week or so Nashville has experienced some pretty intense heat. This wasn’t the normal kind of heat where the temperature and humidity levels are roughly the same. This was a  new kind of heat. Suffocating, debilitating, triple digit heat. The kind of heat that does this to frogs….. Now, I know you’re asking yourself  "why do you care about this frog". The answer is simple. This frog was on a mission. Chris found this frog stuck to the middle of the sidewalk outside our office. Our office is comfortably situated at the end of a long building. We have a sidewalk that completely surrounds 3 sides of our office. The long stretch of sidewalk on the end has a small creek. This creek is usually filled with fast food trash (we pick it up!) courtesy of the hoodlums that hang out on our deck. That creek was where the frog was headed. This frog was killed mid-stride as he tried to approach the watery goodness of the creek. All he wanted was to spend an hour or two in the cool water, maybe cover himself with mud (do frogs do that?) and cool off. To get away from the heat that literally sucked him dry. Poor guy.   The post It’s hot outside. appeared first on SCORM - .

I love SCORM. I’ve built a career and a business around SCORM. When I first read the SCORM spec, I admired its elegance and foresight. SCORM has revolutionized the elearning industry and allowed a market to flourish. SCORM certainly has some warts and even a few character flaws, but I love it all the same. I love SCORM so much it’s even written all over my bicycle. But, SCORM is showing its age. It has carried us as far as it can take us. It’s time for something new, something fresh, something innovative. Something that can propel this stagnant industry forward and become its workhorse for the next decade. Fortunately that something is here. The Tin Can API is the future. From now on, we will be a "Tin Can First" company. We announced our "Tin Can First" strategy at our company-wide planning meeting last week; we have pivoted. Tin Can is happening. Tin Can is real. Tin Can is going to revolutionize the industry, and we’re going to lead the way. You should come along. We are going to ensure Tin Can’s success. We are going to help our customers embrace its capabilities. We are going to help foster a community of adoption and provide adopters with the resources they need to succeed. We are going to develop new and innovative products around the Tin Can API. We will dedicate our energy, thoughts and innovation to projects empowered by the Tin Can API. Tin Can will be our growth engine. We aren’t abandoning SCORM, there’s just not much new that can be done with it. We will still maintain our products and help people implement SCORM. You will still get the same great support you have come to expect. We still love you Grandma SCORM, but we’re going to spend a lot of time with the Tin Can Toddler we have running around. We started a new website dedicated to the evolution of the Tin Can API. Check out tincanapi.com and sign up to receive updates from that site if you haven’t already. The post Tin Can First appeared first on SCORM - .

One learner launching a course in a browser from within an LMS that can’t talk to other LMSs. SCORM’s done a lot a great stuff, but it does come with baggage, doesn’t it? Today’s learning world requires something more, doesn’t it? Project Tin Can gave us the opportunity to throw off SCORM’s shackles, and we took it. Tin Can provides the plumbing that will free us, as an eLearning industry and beyond, from these limitations. ADL is sprinting toward a wide release of Tin Can API, and it’s going to change that opening statement dramatically. One learner or many launching a course or any other activity from wherever they like on any device and communicating that experience to an LMS or any other system, all of which can talk to each other. We’ve all wanted SCORM to get out of our way at some point, the Tin Can API is happening. So, now what? What experiences will you design? What tools will you build? We’re excited to announce TinCanAPI.com to focus on all things Tin Can.Take a look and let us know what you think.

As my bio would suggest, I’m the office talker. I talk faster, louder and more frequently than everyone here in the office. This fact also explains why I get teased about my Southern accent, but that’s neither here nor there. If this was a "loudest laugh" contest, it would be a tie between Freddie and TJ. When it comes to talking, I take the cake. So instead of bothering the people around here with my chatter, I’ve decided to make my talkative nature more productive. I’m taking my talking to the Cloud. You can now chat with me LIVE about all things SCORM Cloud Monday - Friday. I’m usually around my desk from about 9am- 5pm Central time. I wish I could be available all the time, but hey, a girl’s gotta sleep sometime, right? That should give us enough time each day to talk about all the awesome things SCORM Cloud can do and hopefully, I’ll be able to help answer some questions along the way. Each chat will generate a support ticket with us, so if you need to follow up or have other questions, our support staff is there to help you out. You can find me hanging out in the Help button on the SCORM Cloud support page. It looks like this…. So pop on over and chat me, maybe? It’s awfully lonely in there without you. The post Chat me, maybe? appeared first on SCORM - .

Several people have been asking us of late how we intend to charge for the Tin Can API/LRS component of SCORM Cloud. To be candid, we haven’t entirely figured out how we should charge for the standalone LRS capability found in SCORM Cloud. So, our thinking is this: We’re going to wait a little while to figure that out, and during that time, externally-generated Tin Can statements will remain free. For example, statements that originate from our Tin Can bookmarklet will be stored at no cost. At this point, we commit to keep externally generated Tin Can statements free of charge until the formal release of Tin Can from ADL (currently rumored for the end of Q1 2013). One key distinction is that if you use SCORM Cloud to import a Tin Can package and then assign that course to a user via SCORM Cloud or one of its plugins, you will consume a registration, and registrations cost money. For pricing purposes, we treat Tin Can packages just like SCORM packages. Our best guess is that as we move beyond the formal release of Tin Can next year, we will probably base our pricing around the number of users for whom you report statements on. We want you to collect a huge pile of statements this year. We want you to collect a huge pile of statements going into the future. More Tin Can statements will make Tin Can more effective, and it will allow us to better support our users. We will find a reasonable way to relate the utility of those statements to your costs. At this point, though, we still feel it’s too early to specify that pricing. The post Pricing Tin Can in the Cloud appeared first on SCORM - .

Last week I called my favorite bike shop to schedule a tune up. Unfortunately, they are lots of people’s favorite store, so the wait time was a bit longer than I would have liked — like 2 weeks too long. So, then we started talking about what I really needed. It turns out that it was just a couple of minor adjustments, which only take about an hour. They managed to fit me in the same day. WINNING! Recently we had a customer that uses SCORM Cloud Dispatch ask us if there was a way to control how many people were accessing their course from the Client LMS. At the time there wasn’t — but you know what? It’s a great idea. So, we added some functionality that lets you set just how many users can access your course from a Client LMS. (See how it works here). Why did we add this? Because someone asked and it made sense for that customer and many others. We love having these conversations because it helps us understand how people use our products and how we can make them more useful. Lesson learned? It never hurts to ask. We’re listening and welcome the requests and feedback.  Send them our way! The post We’re All Ears appeared first on SCORM - .

You already know that Tin Can is going to change our corner of the world (and maybe a few other parts of the world as well). We’re leading the charge, but we’ve only just begun. We’ve got a pile of opportunity in front of us just waiting to be tapped and we need your help to turn vision into reality. If you’re the right person for any of these positions, come have some fun and change the world with us. Software Developer We’re always looking for amazing software developers and we’ll probably hire as many as we can get our hands on over the next few months. Quality Ombudsman We’re looking for a particularly anal-retentive form of geek to push us to use best practices, ensure we’re testing the right things with every release and squash bugs with vengeance. UX Designer / Ombudsman We’re a bunch of developers who think we can do design, but we don’t do a good job. We need a pro. A tireless advocate for the end user, an advocate for simplicity, an advocate for taste and elegance. Start here for more information about these jobs and why Rustici Software is the best place you will ever work. The post We’re Hiring - Come Build the Future With Us appeared first on SCORM - .

First impressions are important, there’s no denying that. Most people that I see in my day-to-day life only see what I wear, and that usually includes what Jena and I refer to as "a good ol’ pair of jeans." A good pair of jeans is a wonderful thing. If you’ve ever found the perfect pair for you, then you know exactly what I mean. Finding good jeans used to be a real struggle for me. I knew what I wanted, but I just couldn’t make it happen. I finally found my process, and it was well worth the wait. My wife, Ashlee, knows how to pick out the best jeans. Sounds un-manly, but I’m not one to deny a good process once I find it. About once a year, I sit in the fitting room and she throws 3-4 pairs to me. Two of them are perfect. I buy them, and I wear them out. Now, the perfect pair, right off the shelf might still need some work. I’m okay with spending a pretty penny on the perfect pair, then getting them tailored to the perfect length. I’ll wear these jeans a lot. It’s worth taking the time to make sure that they’re exactly how I want them. Why is this important? Because every day I come in contact with loads of people that I don’t talk to, but they’re people that still sum me up only on the basis of how I appear to them. This analogy, for Rustici Software, is like having over 2,000 unique people walk past us on the sidewalk every day and make snap judgements about us based on what they see. …except in our case, it’s unique visitors to our websites. It’s worth it to take the time to tailor our sites to be perfect for our company — our sites are how we’re judged by those 2,000 people that pass us every day on the sidewalk. Just like the perfect pair of jeans isn’t measured only by the perfect inseam, the perfect color or the perfect placement of the pockets, a website is much more than just design. Are you telling a story with your site? Are you keeping things interesting for those that visit your site? Are you creating flashy things that just get in the way of who you are? Our goal is to create sites that are transparent and helpful. Sites that don’t waste the time of our visitors. Sites that say "just by looking at our blue jeans, you can tell that we’ve done the work to make sure that you’re getting helpful, accurate information — we’re here to help, and we’re not here to waste your time." No matter how much time and effort it takes, we don’t need bedazzled fanciness, we just need what’s right for us and for our customers. To see our latest fitting, check out TinCanAPI.com. Tin Can is the next generation of SCORM, and we’ve spent a lot of time trying to make it easy for you to understand. The post A good pair of jeans… appeared first on SCORM - .

It’s that time of year again when the Nashville Business Journal tells us where the best places in town to work are. Rustici Software made the list for the fourth year in a row! It’s been an especially fun year with a great group of people. I’m honored to work with one of the smartest and most entertaining groups of people I’ve ever come across. I honestly look forward to coming to work every morning. We’re hiring more six people right now, come join us. Speaking of a great year. Exciting things are happening with the Tin Can API. This blog on scorm.com has been pretty quiet of late, but we haven’t gone away. Most of our efforts are going into the blog over on tincanapi.com. Go check it out and sign up for our Tin Can newsletter that we send out every month. The post Four for Four appeared first on SCORM - .

There are some deployment scenarios that SCORM makes difficult. One of them in particular is when you have content on one domain, and an LMS on a different domain. There are several solutions for this with varying merits, and all of them require effort of some sort. Further, cross domain solutions aren’t necessary in most cases. For these reasons, addressing "cross domain" scenarios is specifically excluded in some of our SCORM Engine licenses. Why the cross-domain limitation, and how can you get around it? Basically, SCORM requires that content be served from the same domain as the LMS API. Browsers intentionally prevent the javascript in the content from communicating with the SCORM API if they originate from different domains. This is intentional on the part of the browser makers because it’s a security risk. If you control both domains (content and LMS), then this security risk shouldn’t be a particular concern to you, but that’s not easy to convey to everyone’s browsers. There are several ways to deal with cross-domain situations, all of which have downsides. Alter the settings in every browser that will play content. (This is a bad idea.) Manipulate document.domain in each piece of content. (Also not a good idea, because the content vendors have to be involved. Any solution that requires cooperation on the part of the content and LMS vendors basically defeats the purpose of a standard like SCORM.) Use Tin Can, because it works via web services. (Good idea long term, but it doesn’t solve your current problem of playing SCORM content.) Manipulate this via networking magic. Make each additional machine appear to come from the same domain. You can run multiple SCORM Engine installations in a single domain, essentially behind a load balancer. You could even go so far as to have something like http://scorm.domain.com/customerA and http://scorm.domain.com/customerB if you wanted different content stores for each of them, with each communicating back to http://scorm.domain.com. These would be virtual directories that are housed on different machines (with content in each) but appear to come from the same domain. This requires some skill in proxies. (Note: This wouldn’t work if you asked for http://customerA.domain.com, http://customerB.comain.com communicating with http://engine.domain.com. That would require central/remote, listed below.) You can also do a lot of funny business down in apache with redirect forwards, virtual hosts, etc and make those domains look however you want to the outside browser. Use what we call a central/remote architecture. This is a great solution to the problem, and something we’ve built out well in SCORM Engine. It does, however, carry an extra cost because it requires reintegration and is explicitly excluded in our SCORM Engine contracts. Basically, this allows you to have a single core Engine installation. You then replicate the remote component at each content store, wherever that might be. You would be responsible for replicating the content files to those locations. We would collectively write logic that determines which of the remote locations should play the content for each user. So, there are options. They generally require extra work and extra costs. If you’d like to discuss these options, just get in touch with us. Ask us anything, really. The post Solving the SCORM Cross Domain Issue appeared first on SCORM - .

Three years ago, we started on a journey with ADL to help them come up with the next version of SCORM. We’ve come a long way since then (we just hit Tin Can API 1.0!) and Rustici Software has grown quite a bit. Today we’re excited to welcome our two latest additions to the Rustici Software family: Ervin and Nathan (or Ervin and Skirvin, as we call them). If you haven’t noticed, we like to hire in pairs, and rhyming pairs are even better. Ervin Puškar is joining up with our developers and we are really excited about the things he will be working on. Right now he is focused on making it easier for our sales team to interact with prospects, which has a few people around here smiling (I’m looking at you, Chris & Tammy). Wanna learn a bit more about Ervin? This should help. Nathan, on the other hand, is jumping onto Team Delight to help with supporting our customers. Team Delight’s main goal is to dazzle our customers with great support, and we think Nathan is a wonderful addition to the team. There’s a lot more to Nathan than his way with customers, so head over here to learn more. We are so excited to welcome Nathan and Ervin to our team, and we’re always on the lookout for more awesome folks just like them to join us. Check out this blog post to get an idea of who we are looking for. Who knows, we could be welcoming you next The post A big welcome! appeared first on SCORM - .

Quell [kwel] verb (used with object) 1. to suppress; put an end to; extinguish. We base our work year around quarters, like a lot of companies do. At the end of each quarter, we have a "quell" week. It’s the end of the quarter, and it’s time for us to spend some time and think about what we did and what we’re going to do next. Quell weeks are a mix of meetings, good food, and change. We change a lot around here, but that’s how we get better. Quell weeks make some people nervous, and some excited. As our last quarter ended, some of our developers suggested that we do a "hackathon", and see what we could achieve. We decided to do it. But in the true Rustici Software spirit, we couldn’t call it a "hackathon" — we called it a Quack — half quell, half hack. Mike and Tim (the owners) stayed out of it. They let us come up with our own ideas and organize into groups as we saw fit. …and there were awards. $500 to the team that Mike and Tim saw as the winner, and $500 to the team that the company, as a whole, voted to win. We quacked last week. We built things. We created things to help the company and our customers. I’m not going to list them all here; they’ll be explained in a subsequent blog post. While Mike and Tim retreated to Mike’s office to discuss their "winner", we all voted. It’s important to note that we had to put our names on our ballots, so if you self-voted, everybody would know it. It could be an endless opportunity for your peers to shame you (not that we’d do that). There were too many good quacks for Mike and Tim to decide on one winner, so their award was split between two teams. Winner #1 was "Team John and Andy", with their easy-to-use Tin Can API statement generator that can be deployed to customers that want to let their users capture their experiences. Winner #2 was given Ervin, Nathan, and Brian M. for their work in making our software development process more efficient. The "Mike and Tim" $500 award was split between those two teams. It came from an envelope full of $20 bills, so I’m not sure which team got the extra $20. The company-voted prize was awarded to the team of David, TJ, and me, for giving the SCORM Cloud LRS a real home inside SCORM Cloud. So, my team had to figure out how to split up our $500 between three people. You can’t split up twenty-five $20 evenly, so somebody had to get an extra $20. We left that job up to TJ. TJ’s personal quack vote went to Joe Donnelly. Joe didn’t finish his quack because he got wrapped up in helping our customers with their support issues, but TJ realized the value of Joe taking the time to take a deep dive into our code, the Tin Can API spec, and learn more about code in general. When our customers have issues, Joe is the first person that has contact with them, and by Joe having a better working knowledge of the code, over time, the added value to our customers and our company is priceless. TJ divided the cash award and handed me a folded stack of $20 bills. I didn’t count it. I didn’t know where the extra $20 bill went. Mike made a joke about how it would be funny if TJ gave the extra $20 bill to Joe. TJ: "What else would I have done with it?" I was speechless. Awesome. That mindset is what makes Rustici Software the best place to work. The post At Rustici Software, We Like to Quack appeared first on SCORM - .

If you missed our post about Quack, you should check that out before digesting this post. This post is to tell you about one of the creations that came out of Quack. SCORM Cloud has been the easiest way for you to get your own LRS, but its main use has been for launching Tin Can content packages and for testing Tin Can activities that live outside of the LMS. This is how it used to be.   This is because we hadn’t built a way to provide authentication for an activity provider, which means you had to use your SCORM Cloud root-account credentials in order to send statements from an activity outside of an LMS to your Cloud LRS. Well, using your own SCORM Cloud credentials in a publicly-facing way like that just isn’t practical. It’s fine for testing, but it can’t be used in the "real world." This is what our Quack did.   We fixed it. We gave the LRS a home in SCORM Cloud. Now you can add activity providers to your Cloud LRS, which gives the activity provider a username and a password to use with your LRS. Choose either basic auth or OAuth. This means that now you can use your Cloud LRS to accept statements from anywhere, in a secure and "real-world usable" way. All of the things that couldn’t be done before due to security/authentication issues can be done now. It’s a big step towards having a useful Tin Can LRS implementation in SCORM Cloud. The post The Next Leap for Your Cloud LRS appeared first on SCORM - .

We’re happy to announce we have a new addition here at Rustici Software! When I first heard that we hired someone from Mississippi, I was overjoyed! You see, I get teased a lot around here for my super southern accent. I was thrilled that I would have someone to spread the teasing around with. I mean… he’s from Mississippi, surely he’s got a southern accent, right?! Boy was I WRONG! While Tim Edwards doesn’t have a southern drawl, he has a bunch of other great qualities that made him a perfect fit for our DevOps position. Tim (or Tedwards, as we call him) will be joining Ben, our chief worrier, in the never-ending task of keeping our services available and scalable. If you’d like to learn some more about him, check out his profile! Welcome aboard, Tim! We’re glad to have you, even without a southern accent The post It’s a Boy! appeared first on SCORM - .

You might have heard that we like to take care of our employees by offering them things that most employers wouldn’t ever consider providing, and most employees wouldn’t dream of receiving. Well, we did it again. This young man, Beau, washed and detailed all of our cars this week, courtesy of Rustici Software and Jenafits. Why this week? This is a big week for us here at Rustici Software — it’s Quell Week. Quell week happens once per quarter for us. It’s a time where the entire company gets together and decides how the last quarter went, and what will happen in the following quarter. There’s a lot of food (hence the clean plate part of the blog title), and usually, a lot of change (hence, the clean slate part of the title.) Teams might be rearranged, developers might be assigned to new projects, or new teams could coalesce to meet emerging needs. The change that Quell brings is one of the things that keeps our company fresh, on its toes, and progressing. This is definitely not a place where anyone gets stuck doing the same thing, day after day. "I fear change"…you’ve heard it before. We don’t fear it, because it’s how we keep the company on course with our ever-changing industry, and we do this better and faster than most companies (I speak from experience). Another reason not to fear change? Having a spotless and squeaky clean car is nice, for once. The post Clean Cars, Clean Plates, and Clean Slates. appeared first on SCORM - .

Continuing with the fun of Quell Week, we spent yesterday afternoon at Sky High Sports. We bounced around on a massive trampoline, played dodge ball, and got to dive into large pits full of foam (it was just as entertaining to watch people try to get out of the foam pit as it was to watch them dive into it.) You can see photos here. What was really interesting to me was an interaction that I had with our dodge ball referee. He does this stuff for a living, so believe it or not, he’s seen his fair share of "massive trampoline" dodge ball matches. At one point during our match, he turned to me and said "I’ve never seen anything like this before." Was it the intensity of the competition? The amount of fun we were having (at a work function)? The way that we started making up our own rules to increase the difficulty (and in turn, increase the fun) of the game? I don’t know. But I do know that we get that reaction a lot …usually when someone visits our office for the first time, or when we’re out in public at a company event. "I’ve never seen anything like this" is a really good way to sum up what it’s like to see this company in action. The post I’ve never seen anything like this… appeared first on SCORM - .

"Bravo. You are in the select company of America’s Fastest-Growing Companies".     That’s what was written on the front of the big folder that Mike handed to me last week, the folder that Inc Magazine sent to us, letting us know that we made the INC 5,000 list this year. It’s pretty exciting — even The Tennessean thinks so. We’ve won a lot of awards, many of them we’ve won multiple years in a row, but this is our first time making the INC 5,000 list. We don’t need awards to know that we’re doing great work, but it sure feels nice to get them. The post A first for us appeared first on SCORM - .

When Jeff and I sat down to interview our newest employee, Matt Lefavor, I didn’t know what to expect. You see, Matt has officially taken my title of youngest Rustici Software employee. I held that position proudly for exactly 922 days. As hard as I tried, I couldn’t help but feel a tad replaced. But once Matt started telling us about himself, my feelings were drowned out by the chorus of this Foreigner classic. I really have been waiting for a guy like Matt to come to work here at Rustici Software for so many reasons. He rocks a bowtie almost everyday, hence his nickname- Bowtie. He came to us from NASA. He writes music. He lets me call him Bowtie. And if that wasn’t enough, he’s a rapper. That’s right, people. He raps. I could barely contain my excitement. Want to sample the tracks that Matt’s laying down? Check this out. Matt’s joining our SCORM Engine team, working on everything from integrations to creating new releases, with a side of support here and there. Want to learn a bit more about him, check out his bio. I wish I could write a really awesome rap to welcome Matt to the Rustici family, but I’m lyrically and vocally challenged. Instead, I’ll just say "Welcome, Bowtie, we’re happy to have you here!" The post I’ve been waiting for a guy like you appeared first on SCORM - .

We love it when Brandon Hall announces their Group Excellence Awards winners. Not only do we get to see how innovative our industry has become, but in a few cases, our software plays a role in the projects that have earned the coveted Gold Medal. We even had the honor of winning one ourselves a few years ago for SCORM Cloud. This year, we were excited to see long time SCORM Cloud customer, CA, take home a whopping 5 medals including a Gold Medal for "Best in Learning Technology Implementations" for a solution they built using SCORM Cloud. CA faced a challenge of delivering training for their Global Partners and wanted to explore other delivery platform options for their external partners aside from their primary LMS. SCORM Cloud fit the bill. With the public invite option, CA adds links to their training hosted in Cloud directly on the partner site, making it easy for folks to login and get right to the training in one step. Using tags, CA can easily run reports through the Reportage feature to quickly see training results by each partner. By simplifying access to the training, CA saw a significant increase in training consumption and ultimately sales. Congrats to CA — we are happy to play a supporting role in this great honor! The post SCORM Cloud + CA = GOLD appeared first on SCORM - .

We’re a family here at Rustici Software. We look out for each other, and we tease each other, just like brothers and sisters do. We even call Mike "Dad" and Tim "Mom" — but it wasn’t until our latest hire that we really were a "family affair." Ryan Donnelly joined us about a week ago. Does the name Donnelly ring a bell? Ryan is Joe’s younger brother! How cool is that!? …and we couldn’t be happier to have him. Ryan will be teaming up with Joe on the support side of our business. He’ll be working directly with customers to help them troubleshoot issues and help them find which of our products work best for them. If you’re curious about what else Ryan is in to, check out his bio. We’re excited to have Ryan here at Rustici Software, and we can’t wait for him to start giving up brotherly secrets about Joe. Welcome to our family, Ryan! The post It’s all in the family appeared first on SCORM - .

You don’t have to wait for content players to catch up! If you’re creating Tin Can courses but getting frustrated by the limited number of players that can actually launch and report on them, here’s some great news: SCORM Cloud’s Dispatch service has a new feature that enables a SCORM-only LMS to handle Tin Can packages—without losing reporting data. How is that possible? First, you have to understand how SCORM Cloud Dispatch works. Tin Can data is collected throughout the activity experience and stored in your CLOUD LRS. Once the user exits out of the course, the Dispatch updates the client LMS with the user progress in the form of SCORM data. Why would I want to use this? While the number of Tin Can conformant LMSs is growing, many LMSs are still in transition. Dispatch allows for an immediate way to launch Tin Can activities in LMSs that only support SCORM. You don’t have to be limited to SCORM-only courses while you wait for LMSs to catch up! Content Creator Benefits: There are now more types of courses you can distribute to customers You can now maintain detailed Tin Can statements in Cloud while still satisfying clients’ SCORM reporting needs LMS/Client Benefits: You’re no longer limited to SCORM-only courses You can continue to receive SCORM-conformant reporting data Where do I sign up? It’s available now, so try it out! We even have free trial accounts to help you get started. To learn how to create a Tin Can Dispatch, go here. The post How to Distribute Tin Can Content Through a SCORM-only LMS appeared first on SCORM - .

We love finding ways to use technology to make things better and easier, and we’ve done it again! SCORM Cloud has a pretty nifty feature called Dispatch. It lets you remain in control of your content by doing some pretty clever behind-the-scenes things, and more control over your content is awesome! Well, we’ve decided to add Dispatch to SCORM Engine (the Web Services version of it, at least.) This is a big deal for content vendors. Dispatch lets you manage all of your content in one place, but allows you more distribution. No more handing your valuable content packages off to clients—now you can manage them all from one place. What other kinds of things does it let you do? Update your content in your Engine-powered LMS, and everybody that has your content will automatically receive the update. Play your content through any LMS, while keeping it on your own servers. Cut off access to your content for clients that aren’t paying their bills. Track how often clients are accessing your content. Delivering your content as a Dispatch means that it’s using the best SCORM player in the known universe. You can play SCORM 2004 courses and Tin Can API packages in a SCORM 1.2 LMS. People have been doing these things for years in SCORM Cloud, except for one important part: playing content on any LMS while keeping it on their own servers. Using SCORM Cloud, the content is hosted on our servers. That’s no longer a limitation using SCORM Engine and Dispatch. If you want to learn more about using Dispatch with SCORM Engine, get in touch. You know we love talking about this stuff. The post This is a big deal for content vendors. appeared first on SCORM - .

SCORM Cloud Reportage provides a simple snapshot of your learners’ activities, but sometimes you don’t want a picture of ALL your learners. Want to know the completions of a specific department? The average score of learners within a specific geography? The amount of time new learners are spending per course? By using the tagging feature in SCORM Cloud, you can pull customized reports in the Reportage screen. This allows you to exclude certain criteria and to pull data about isolated groups. With SCORM Cloud tagging, you can do this with only a few clicks. The key is to add appropriate tags to your learners and then filter by those tags in Reportage. Take a look: Manual Adding .CSV Upload If you want to import tags across a large list of learners, you can also import a .CSV file. Just format your .CSV file as shown below: When adding tags to users, you have the freedom to filter data down to the specifics. To get even fancier, next time we’ll take a look at adding tags to registrations and invitations. The post SCORM Cloud What Now?! Using Tags for Custom Reports appeared first on SCORM - .