Browse Content Portlet

To browse content extracted from the JCR, we provide a dedicated portlet called the BrowseContent one (BC). The idea is to provide an extensible portlet that ECM admin can extend both for rendering issues but also to modify the way the content is extracted.

By default we provide a rendering template that allow you to browse down a JCR tree and to view the children document or optionnaly the document that reference the node. Rendering references is a pretty convenient feature as it allows people to decouple the content location from the navigation paths that end to point to that content. Categorizing a content from the ECM Explorer portlet allows such behavior.

Note that template as well as the one used to render the document itself (kind of decorator around the DocumenType view template) are stored in the JCR itself and can therefore be modified online by the ECM admin. Refer to the administration section that deals about templates. Templates are hence also versionnables.

One can also search for documents, either in a full text way or looking for a keyword that would be contained in the path (category). Some children documents can also reference other documents (called a relation) and if allowed in the configuration then the search will also include those.

There exist many ways to extract content and everything can be configured from the CB portlet edit mode. The current configuration is shown from the main page in the edit mode. By default we extract the content from the root path of the taxonomies (located in the system workspace - one per repository - under the path /jcr:system/exo:ecm/exo:taxonomies) which allow to view all the documents that reference any node in the taxonomy tree.

From there it is possible to access several wizards that allows you to choose among several ways to extract content from a dedicated workspace:

• extract content from a JCR path located in a well defined repository/workspace which includes repository bound taxonomies
• extract content by using a JCR Query (XPath or SQL)
• delegate the content extraction to a Groovy script
• directly display a JCR document with the correct decorating template