Courses Organization and Management
Apr 29, 2016
Hello,
I am brainstorming ways to help with my organization's course management system. We got a LMS about 3 years ago and since have built and uploaded over 300 courses. My production team has a project organization system. This includes a file for each project which is then broken out in other folders (audio, video, script, story files, published files, graphics, etc.). However I am concerned now with discussion of replacing our current LMS and Legal now needing access to the files that we need a better cataloging and organization process.
I was considering placing all story files and zipped files on our internal server with a spreadsheet of course titles and published dates, but am concerned that this would be easily forgotten about as updates are made. Does anyone have suggestions of processes that have worked for you or your organization?
Thank you!
Karoline
3 Replies
Hi Karoline,
Are you talking about the file structure/organization on the backside of your LMS (ie the "repository" that some folks load courses into for deployment).
Or are you talking about organizing content outside of that for internal review, archiving, etc?
Hi Bob,
Great questions - I am talking about organizing content out of the LMS for internal review and archiving. That being said, all organization suggestions are welcomed!
Thank you,
Karoline
Hi Karoline,
So maybe this isn't very scientific, but I've found over the years that when organizing things it's always best to start with the end in mind. So think about who will need access most often and for what purpose....
If it's outside auditors for regulatory purposes, provide ONLY the finished products, perhaps publishing to stand alone versions in a separate folder with the most recent posted version of each module in it.
If it's your IDs/Developers for routine updates, date driven is one option IF you do you are on a routing update/review cycle. If your review cycle is subject/need driven, then organize by topic. In either case, consider the "top level" of each folder to contain not the story file, but instead a stand-alone version that can be viewed separately along with a print version (if you do such a thing). This makes review by SMEs and others much easier. Only your developers need to dive into the story files and assets., so put those in deeper folders inside each course folder.
Not sure how detailed you are looking for but hope this general info helps a bit.
This discussion is closed. You can start a new discussion or contact Articulate Support.