Document management system for scorm files

Apr 19, 2021

Hi everyone

Is there anyone who can guide me in the right direction? I am working for a medium sized organization as instructional designer, and we need to find a central place where we can store .story and scorm files (as well as other training material in other formats such as PDF, Word, PowerPoint) in a library so that it can be accessed in future.

We don't want to simply use a sharepoint system, where anyone can just save or access material, as we want to apply version control, as well as ensure that only authorized persons have full read and write access, but most only have viewing access.

Note that it is not a system that needs to play the material, such as an LMS, but more a storage system, similar to a document management system. Our current DMS does not accommodate scorm files.

Background: we recently implemented a new LMS, and found that a lot of the original scorm files were lost after upload in the past. We now need to run an exercise where we contact content developers who created those projects for us, and some are not even in business anymore. We also have a number of instructors that sometimes use outdated versions of training material, and we want to align everyone with access to the correct material at all times.

My primary area of work is content development, but my manager thought it would be a good idea to give me the opportunity to suggest workable solutions for possible implementation, as it was my idea to start controlling all training material in one place that is readily accessible. So please bear that in mind when responding, as I am still very much green in this field.

Thanks!

5 Replies

Judy Nollet
Hero

3 years ago04/19/21 at 12:44 pm (UTC)

Hi, Gerda,

One of my clients did use SharePoint for this type of storage.

They adjusted the access settings to control who could view, upload, download, etc.
SharePoint does offer a version history function, though I don't know how well that would work for Storyline files.
We set up a folder structure to manage versioning. Each project had its own folder. A project folder included a sub-folder for each version, e.g., v1, v2, v3. (And that folder could have more sub-folders, depending on the needs of the project.)
This made it easy to see what was the most recent version while still being able to access previous versions when necessary.

The same type of folder set up would work in Box or any similar online storage system.

3 years ago04/19/21 at 1:00 pm (UTC)

Hi Judy

Thank you so much for the advice. We will consider this as we already have SharePoint set up as a standard storage solution, and it may be more cost-effective. I will ask our IT people to see how the settings can be adjusted to ensure full control. That is our biggest concern with a server-type solution.