Forum Discussion
What do you use for storyline file Version control tools? Git?
At two previous organizations, I used Box. Box created a directory on the local machine where the development file was stored. Whenever the file was Saved, the version was committed to the cloud. It also updated the local version for others on the team who had that file on their local machine.
My current organization is a Microsoft O365 shop. IT deployed SharePoint which replicates a lot of Box's functionality. The local version of the file is always the most-current, is managed through the OneDrive interface, and I can go to the cloud via the web interface to view and manage the complete version history.
Opening a file on the local machine does not automatically Check Out and lock the file, you have to check it out via the the web interface to engage Pessimistic Lock, THEN open and edit the file as usual.
Just be sure to check it back in when you're done, or you might get a nastygram. 😉
you used shareponit to engage a pessimistic lock? I've heard source control through sharepoint is horrendous and doesn't work well.
If I and my team were doing actual app development, then I'd want something a whole lot more robust than SharePoint. When I was writing ASP/VBScript which tied into a SQL back-end, then yeah, TortoiseSVN committing to Apache was the way to go. That was also better than 15 years ago.
eLearning development in Storyline is not app development. SharePoint is quite a bit better than it was 15 years ago. And good technology will not solve for poor or non-existent processes and procedures.
I beg to differ a bit. Years ago when I worked in software development, you had to check out a file to work on it. So if you went to work a file, and it was already checked out, you could not edit it. This ensured multiple people were not working on the same file at the same time. And if they did need to, they would talk to each other about it. No one is going to jump up every 10 minutes and announce that they need to make a quick fix to a file they just realized affected a different project. Source control is not a perfect solution, but it would go a long way and should be able to be a part of a technical/automated solution.