#11 Exactly what was NOT supposed to happen
So we had a scare at work on Tuesday this week. For months, my company has been talking about the process for moving all of our documents—personal and shared—from our C drives and LAN folders to our own SharePoint sites. I have a few LAN folders that I work in daily, along with a few other members of that team.
Now we’ve been told to “put our important documents in “migrate” folders and wait for further instruction"—(because they haven’t quite figured it out yet). Anyway, March 31 was a former cut-off date for this migration to happen. We’ve known for months now that the cut-off date has been pushed back several times, but I’ve been here long enough to know that I should probably back up my important stuff somewhere anyway. Too bad I didn’t do every folder…
Another part of our migration instructions were to only “clean up” the folders we were responsible for. A co-worker and I went through the 3 folders we use for our job a long time ago. However, our folders are quite a ways down the folder structure inside bigger folders, and exactly what I feared would happen sure did—someone moved our folder because they didn’t know what it was. After a few phone calls to the tech people to try to recover it and doing a little digging ourselves, we found the folders that we work out of EVERY DAY in a new folder called “(compound#) nonspecific docs.” Ok, they may not have been “specific” to whoever decided to move them, but they were specific to other people.
When you have many people working with files in an electronic environment, version control and document storage can be big problems.
Now we’ve been told to “put our important documents in “migrate” folders and wait for further instruction"—(because they haven’t quite figured it out yet). Anyway, March 31 was a former cut-off date for this migration to happen. We’ve known for months now that the cut-off date has been pushed back several times, but I’ve been here long enough to know that I should probably back up my important stuff somewhere anyway. Too bad I didn’t do every folder…
Another part of our migration instructions were to only “clean up” the folders we were responsible for. A co-worker and I went through the 3 folders we use for our job a long time ago. However, our folders are quite a ways down the folder structure inside bigger folders, and exactly what I feared would happen sure did—someone moved our folder because they didn’t know what it was. After a few phone calls to the tech people to try to recover it and doing a little digging ourselves, we found the folders that we work out of EVERY DAY in a new folder called “(compound#) nonspecific docs.” Ok, they may not have been “specific” to whoever decided to move them, but they were specific to other people.
When you have many people working with files in an electronic environment, version control and document storage can be big problems.
