We are aware of the saving issues and know that saving to a local drive is best. I am curious if anyone has tried saving to an external drive? I have several staff who work in Articulate, if they only save to the local drive, no one else can access those files. How do others deal with this issue?
In my team, since only one person works on any given project on any given day, we each work locally, then copy that day's file into a shared drive as part of our end-of-day routine. If I am out the next day and someone needs the file I worked on, they can access the shared 'back up'. We think of the version of the file on the shared drive as the master, so when I am done working on the project, I delete the project files from my local drive (after updating the shared drive's file).
It also helps to come up with a naming convention that keeps versions or updates clear. It's also important that everyone update the shared drive daily, and that people are able to communicate about who is working on which file, to make sure there are no overlaps.
Always work off your local hard drive and set a baseline version number. We usually use something like, Name_Of_File_D_1.0. If you are lucky, you might have a version control system, like SharePoint or something like that, which helps to keep track of any changes made to the master file. The key to any version control system is that everyone understands how it works and what their responsibilities are. Then all you really have to do is enforce it.
3 Replies
Hi Nicole,
In my team, since only one person works on any given project on any given day, we each work locally, then copy that day's file into a shared drive as part of our end-of-day routine. If I am out the next day and someone needs the file I worked on, they can access the shared 'back up'. We think of the version of the file on the shared drive as the master, so when I am done working on the project, I delete the project files from my local drive (after updating the shared drive's file).
It also helps to come up with a naming convention that keeps versions or updates clear. It's also important that everyone update the shared drive daily, and that people are able to communicate about who is working on which file, to make sure there are no overlaps.
Always work off your local hard drive and set a baseline version number. We usually use something like, Name_Of_File_D_1.0. If you are lucky, you might have a version control system, like SharePoint or something like that, which helps to keep track of any changes made to the master file. The key to any version control system is that everyone understands how it works and what their responsibilities are. Then all you really have to do is enforce it.
Hello Nicole, and welcome to Heroes!
Here is our Recommended Workflow for Collaborative Network Environments.
This discussion is closed. You can start a new discussion or contact Articulate Support.