A while back I was researching how to manage an office library of families. The main issue being, do you have a 2011 library, which you copy to a 2012 folder and upgrade? That is what I have done for years, and it seemed to be what everyone was doing. I proposed the idea of just having a single library, and upgrading the content once the new version roll-out was complete, but the problem is that you can have a straggler project that doesn't upgrade for some reason holding up the migration of the library to the new version. Enough repetition of the family being upgraded dialog gets old.

So now, one of the big brains in my office had the idea of having a single folder for the "current" library, but with a new version rolled out the old "current" library gets copied and turned into an Archive Library, or even a 2011 Library, to make getting back to old content if a particular project doesn't upgrade a little easier. A shortcut to the Archive library could even be included in the "current" library.
I should note that we are a smaller office, and I would argue for moving to the new version of Revit office wide fairly quickly. But people are still a little gun shy about 2010 and the ribbon I think (yes, really) and are resistant to saying we will always upgrade all projects. But in any case, the entire approach would NOT make sense for a large office who chooses to finish long timeline projects in the version they started in, nor would it work for a consultant who has to have all versions available to use as dictated by the primes.

Anyway, this makes a TON of sense to me, and I am just wondering if I am missing something and that is why this idea has not come up before? Or has someone used this approach successfully and just didn't share? An added benifit is that all of the links to family folders we might include in our OneNote based BIM Manual won't break every year, which is a nice second bird with that one stone.

Thoughts?
Gordon