Framework Folders are now Enterprise Libraries? Sort of...
By Ken Walker-Oracle on Dec 11, 2013
As a Computer Science major, you will probably be required to take a course in "Symbolic Logic." This is the class where they teach you how to think logically and how to solve puzzles in logical ways, so that you can teach computers to do the same. For example, we all know that while all golf balls are round, not all round things are golf balls. This seems logical to us, but computers have to be told such things.
The new release (188.8.131.52) of WebCenter Content has some people similarly confused. Many new significant features were introduced with this release and, naturally, new features bring questions and changes, and these questions are addressed in our documentation and in our Knowledge Base. We've introduced a new User Interface with this release called the ADF-UI and with it, we've introduced the notion of "Enterprise Libraries." Content Server has had a popular "Folders" interface for many years. The migration of the product has brought migration to the Folders component as well, Folders became Folders_g and then "Framework Folders," etc. Now, we have "Enterprise Libraries," so, with the introduction of 184.108.40.206, do all of your Framework Folders have to become Enterprise Libraries? Think of Enterprise Libraries as "Folders" for the new ADF-UI.
I know what you're thinking, "If all Enterprise Libraries are Folders, then do all of my Folders have to become Enterprise Libraries?" No. If you choose to use the new ADF-UI, and you would like for your users of this new user interface to be able browse through content with a Folders-like hierarchy, then you'll need to be using Framework Folders, and you'll need to move those to Enterprise Libraries, (Please see Note 1591450.1 for details on this). Enterprise Libraries show up, by default, when you opt to use the new ADF-UI.
So, if you decide to stick with the original user interface, you can keep your Folders exactly how they are. The Folders_g component is still supported in WCC 220.127.116.11, and "Framework Folders" is obviously supported, as well.