Google-drive – How to open Google Drive and Google Plus links with the non-primary Google account

Google is unable to read the page via the short link to the answer. On first sight, the headers appear to be identical to the question short link. For the question Server Fault responds:

HTTP/1.1 301 Moved Permanently
Location: /questions/199569/where-to-maintain-central-source-repository

...but for the answer:

HTTP/1.1 301 Moved Permanently
Location: /questions/13267/git-and-mercurial/343603#343603

The only real difference is the #fragment in the redirect URL. Also, when using bit.ly URLs to test redirection with and without such fragment, Google gives the same results. So it's a Google thing.

As an aside, note that any Google tool that requests the page chokes on the short link - http://serverfault.com/a/199572:

Rich Snippets Testing Tool:

• http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fserverfault.com%2Fa%2F199572&view=
• Reports 'empty page'

Google mobile viewer:

• http://www.google.com/gwt/x?u=http%3A%2F%2Fserverfault.com%2Fa%2F199572
• Reports 'HTTP Error 400. The request URL is invalid.'

No good answer from Google as to why. They say it could be 'caused by an issue with web server configuration, an issue with your hosting provider or even an issue with their ISP'. Might take a question on Meta Stack Overflow to resolve?

--

Update: filed as a bug on Meta.SO.

--

Update: resolved on Google's side.

Re your point 2 You are heading in the same direction my company has gone. We have the equivalent of your 'Central System' as a Username, and have created three folders on its Drive - WORK, REFERENCE, EXTERNAL USERS - and shared them with our Sysadmin. Sysadmin shared WORK with Users on an Edit basis and our users built a sub-folder structure for our company to hold all our working files. Sysadmin shared REFERENCE with most Users on Read basis but with some Users granted Edit rights so they could create and maintain the folder/file structure for policy documents, manuals etc.

WORK is shared Edit and REFERENCE is shared Read to new starters as part of the User setup process and new Users immediately acquire inherited rights to all the contents of these folders.

Leavers, we change the User password immediately, use administration advanced tools to transfer ownership to their manager/colleague for any files/folders they may have created and then unshare them from WORK and REFERENCE.

We have not made WORK or REFERENCE to be the Owner of the sub-folders and documents which they contain because it would require that only someone logged into Central System would be able to delete them. We simply use our own version of Central System to provide a unified data structure for our Users. The Users each retain the 5gb of non-Gdocs storage space which is shared with other Users through WORK and REFERENCE.

We collaborate with external organisations and use EXTERNAL USERS as a portal. For example, our Auditors want access to our some of the data on our system. We created a sub-folder AUDITACCESS in the EXTERNAL ACCESS folder and granted our auditors' gmail accounts Read access to AUDITACCESS. We then use the Organise function to give them a View towards the files and folders which they need to access (but remember to hold the CTRL key down when you use the Organise function). This allows us to un-Organise files and folders, if necessary, since they are all listed in the AUDITACCESS folder and to un-share AUDITACCESS with our auditors email accounts, if necessary.

Hope this will give you a few ideas for organising your own system.