This is why I recommend keeping only working drafts in personal space, and using SPA-owned space or even old-fashioned file servers as the repository for 'final' documents. But this is just advisory - there is no way to enforce it.
Unfortunately not every one departs in a controlled manner. Deaths in service, or just cases of 'I'm outta here!' do come up, and no amount of exit planing will help there. There is a similar problem with calendars widely shared by departed people - they cannot be changed or revised. They can be hidden, and replaced by another calendar, but nothing short of admin intervention will change the owner or even stop it. Graham On 8/27/15 3:53 PM, Richard DESHONG wrote: > For reference, I did submit the question to bConnected and this created > a ticket. From my research, it appears that the options are: > > 1) Have the original owner transfer ownership to another account. > > This is the "easiest" and could be incorporated in the off-boarding > process. So when an employee gives notice, the transfer of ownership of > dept files from box and google can be part of the process. > > 2) My researched noted that the "google admin" could change ownership of > selected files. This would imply that the bConnected group should be > able to do this. > > 3) Make a copy of the files in another account, share this new file as > appropriate, and remove the shares from the original. > > This last option could be used to make sure that the files do not > disappear if an ex-employee deletes there account. > > Not sure if the bConnected admin has the ability to mitigate this risk. > > On Thu, Aug 27, 2015 at 3:16 PM, Jon Hays <[email protected] > <mailto:[email protected]>> wrote: > > Hi Richard, > > The short answer to your question is that it is complicated and, > yes, not terribly easy with Google Drive. > > It looks like there are several good ideas floating around out > there. Ian Crew from the bConnected Team is working on a more > detailed response with a few general recommendations and best > practices to share with the list. > > He'll post his response in the next day or so. In the meantime, if > anyone on the list has an immediate issue or concern, please go > ahead an submit a ticket with the help desk > at: https://shared-services-help.berkeley.edu/new_ticket/it > > Best, > > Jon > > > University of California, Berkeley *Jon Hays* > Service Manager, bConnected Collaboration Services > IST-Architecture, Platforms & Integration (API) > [email protected] <mailto:[email protected]> | 510-672-5493 > <tel:510-672-5493> > > <http://www.linkedin.com/in/jonmhays> <http://twitter.com/vcrkid> > <http://plus.google.com/+JonHays-Berkeley> > > > On Thu, Aug 27, 2015 at 2:20 PM, Richard DESHONG > <[email protected] <mailto:[email protected]>> wrote: > > In bDrive, how do we change ownership of a doc? > > We have a shared folder, and various staff have created docs. > When a staff member leaves our dept, I'd like to transfer > ownership to someone still in our dept. > > I've looked at: > https://support.google.com/docs/answer/2494892?hl=en > > which suggests that in Advanced sharing, I can click on the menu > next to someone name and select an option "Is Owner". This > option does not exist for me. > > -- > Richard DeShong, Systems Analyst, Athletic Study Center, > U.C.Berkeley > 164 Chavez Student Center, Berkeley, CA, 94720-4220 > 510-642-5123 <tel:510-642-5123> asc.berkeley.edu > <http://asc.berkeley.edu> > > > > ------------------------------------------------------------------------- > The following was automatically added to this message by the > list server: > > To learn more about Micronet, including how to subscribe to or > unsubscribe from its mailing list and how to find out about > upcoming meetings, please visit the Micronet Web site: > > http://micronet.berkeley.edu > > Messages you send to this mailing list are public and > world-viewable, and the list's archives can be browsed and > searched on the Internet. This means these messages can be > viewed by (among others) your bosses, prospective employers, and > people who have known you in the past. > > ANNOUNCEMENTS: To send announcements to the Micronet list, > please use the [email protected] > <mailto:[email protected]> list. > > > > > > -- > Richard DeShong, Systems Analyst, Athletic Study Center, U.C.Berkeley > 164 Chavez Student Center, Berkeley, CA, 94720-4220 > 510-642-5123 asc.berkeley.edu <http://asc.berkeley.edu> > > > > ------------------------------------------------------------------------- > The following was automatically added to this message by the list server: > > To learn more about Micronet, including how to subscribe to or unsubscribe > from its mailing list and how to find out about upcoming meetings, please > visit the Micronet Web site: > > http://micronet.berkeley.edu > > Messages you send to this mailing list are public and world-viewable, and the > list's archives can be browsed and searched on the Internet. This means > these messages can be viewed by (among others) your bosses, prospective > employers, and people who have known you in the past. > > ANNOUNCEMENTS: To send announcements to the Micronet list, please use the > [email protected] list. > -- Graham Patterson, Systems Administrator Rm 111, Lawrence Hall of Science, UC Berkeley 510-643-1984 "...past the iguana, the tyrannosaurus, the mastodon, the mathematical puzzles, and the meteorite..." - used to be the directions to my office. ------------------------------------------------------------------------- The following was automatically added to this message by the list server: To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site: http://micronet.berkeley.edu Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet. This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past. ANNOUNCEMENTS: To send announcements to the Micronet list, please use the [email protected] list.
