Boss wrote:

Fussbett wrote:

Boss wrote:

Fussbett wrote:

Hello Boss,

Just dropping you a note as a reminder to let me know of anything production-related you're telling to Tom or Dick or Sally, working on Project X. I wasn't aware that Sally would be downloading company photos off the FTP for us, and copying over the photo folder on the server. As a result, yesterday Sally overwrote all of Jill's photo editing work, in an effort to update the photos. Oops.

Thanks.

OH NO - suggest workstations also maintain a local working copy on their internal HD.

Note that it is also all TOO easy to INSTANTLY delete files off the production server - there is no stop-pover in a TRASH folder.

We do have a daily backup now, so only 1 day of work was lost. Copying all materials from the server to the local hard drives is a messy workaround because it reduces the benefits of a central resource and introduces version control issues.

Noted about the trash on the server, but in this case the problem arose from Sally copying over an entire folder full of subfolders. This would replace the subfolder content even on a local hard drive.

glad the daily back-up is working

my suggestion is that each individual maintain at their workstation a "LOCAL CURRENT WORK" older which is their local BU for their recent work - because we all have ADMIN access privileges to the server - a LOCAL folder would be protected from accidental overwrites because it is not shared and no one but the local work station user has overwrite privileges

if everyone has equal access to a central server, and if the current and only copy of files are kept there; overwrites will inevitably continue to happen