the vault wiki help in the following link discusses some functionality of vault library...
the comment i posted below that wiki help is copied to below for consideration.
ps - also consider in relation to this idea, the autodesk inventor library functionality i posted 29 november 2012, in the inventor idea station, called: "inventor library functionality".
in topic Library Folder Rules above, it states that: quote "...
6.When you retrieve latest versions of files with their dependencies, and one or more of the dependencies is located within a library folder, the vault ignores the file for that operation.
7.When using the Get Previous Version command on a file that has a child dependency to a library file, the library structure is created parallel to the workspace so you can open the previous version of the file.
NoteThis is done to prevent the shared folder of data from being changed while other users are working on the files. Changing a library file can affect many designs and requires coordination with members of the team also using that file
..." end quote.
first of all we need to consider that although it is true to say that library files are static in nature there must be a practical understanding and ability to choose what happens with a library file...
first & foremost though, we must have any library file to download with an assembly that the lib file resides within (depenancy) just like any design file would do.
second, there are library files that represent a vendor item. users may indeed need to make an edit to an iProperty, or even to a note on a lib file drawing. vendors do from time to time make a revision to a commercial item. an engineering office would simple capture that update in the lib file, & bump the revision. as long as the rules of revising are conformed to (fit form & function) then the library file would be not that different to any other file.
i think we must understand and qualify that the key word is "change".
even with design files, we do not "change" files to make them unusable for everyone else. we make sure that if a file must change, it either adheres to the revision rules of fit form and function. if it does not then the files get copied and has a new part no. file name.
library files must not be simply considered as a content center publishing location.
to have the practical functionality required we would need to get rid of library folders and just use a design folder. it just seems like the perfect world that the developers think is workable makes the concept of a library unpractical.
if there is debate on the topic, then i would recommend that we are given a toggle setting for administrators to turn on and off to allow someone with some practical experience & consideration to allow or disallow for the the functionality to be available or not.
i think that it is not good for developers to block functionality based upon their own ideas without providing practical functionality or options that can be chosen to be used by administrators.
=end of comment=