This chapter contains the following topics:
Content Folios is an optional component that is automatically installed with Content Server. When enabled, it provides a quick and effective way to assemble, track, and access logical groupings of multiple content items from within the secure environment of Content Server. For example, all items relevant to an upcoming brochure, such as images, logos, legal disclosures, and ad copy, can be assembled and sent through a workflow process. Once approved, all associated content can be downloaded and sent for print. Or perhaps a new project requires a virtual place to assemble all relevant content items in a particular hierarchy, whenever they are checked in, with restricted access to particular areas of the hierarchy. Or a video may need to be associated and tracked with release waivers and narration text. All this can be done with Content Folios.
Technically, a content folio is an XML file checked into Content Server that uses elements to define a hierarchical structure of nodes, slots, and specified content items in Content Server. In practice, a content folio is a logical grouping, or a framework in which content stored in Content Server can be structured. Simple folios are a flat container, while advanced folios can nest content in a hierarchy within folders. In an advanced folio, the hierarchy may be established prior to assembling content items, or it may be created during or subsequent to assembling the items.
Existing folios can have content added to them, or can be locked so that no changes can be made. Content items can be added to a simple folio by searching Content Server, and to an advanced folio by checking new items into the content server repository or by searching for content that has previously been checked in, all through the folio interface. An advanced folio can even contain hyperlinks to outside resources such as web sites or shared network drives.
This section contains the following topics:
Content Folios adds the following functionality to Content Server.
Organize content into a simple, flat folio structure
Organize content into an advanced hierarchical folio structure
Create pre-structured templates for selection when creating folios
Modify folio structure dynamically
Lock folio structure to prevent it from being modified dynamically
Lock content folios to prevent additions
Unlock folios to allow additions
Modify folios without tracking revisions in Content Server
Take a snapshot of a folio in order to track revisions in Content Server
Download renditions of folio content in .zip, .ppt, .pdf, or XML format
Create multiple unstructured content baskets for use in collecting content items
Several changes are made to Content Server during installation of Content Folios:
The following metadata fields are added to Content Server to record the current state of a folio or template:
CpdIsTemplateEnabled
CpdIsLocked
The following views are added to Content Server and are used on the Folio Edit page to communicate Content Folios tables to JavaScript.
NodePropertyView
LinkPropertyView
NodeRemovalTypeView
CpdTreeDisplayFunctionMapView
CpdPopupEditActionsView
ItemPropertyView
PneDocProfileView
The following relation is used by PneDocProfileView:
GenericUserProfileRelation
The following tables record the links that folios and content baskets have against content in the system
CpdLinks
CpdArchiveLinks
CpdBasketLinks
CpdEditHistory
Note:
Changes made to Content Server during installation of Content Server remain even if Folios is disabled or removed.Content Folios provides the means to organize content into a hierarchical structure. The structure of a folio can be modified dynamically when creating or editing it, or the structure can be static based on a pre-defined template selected when the folio is created, or lastly it can be a combination of the two.
This section covers the following topics:
Folio templates offer the user a predefined organization of nodes, subnodes, slots, and any required content items when creating a folio. A folio template can be selected by a user at the time they create an advanced folio. Folio templates are XML files checked into and managed by Content Server, and can be edited and revised at any time. Revisions to a template are not applied retroactively to existing folios based on that template, but only apply to new folios created based on the template's new revision.
To create folio templates, you must have administration rights to Content Server. Templates are created using the Create/Edit Folio Template Page, accessed by clicking the Create Folio Template link in the Folio Administration folder on under the Content Server Administration tray.
To create a folio template, do these steps:
Open the Folio Administration folder on the Content Server Administration tray and click Create Folio Template. The Create/Edit Folio Template Page is displayed.
Select Save template from the page Actions menu. The Set Folio Template Profile page is displayed.
Important:
You must save the folio template before navigating away from it. Saving the folio checks the folio into Content Server. If you do not save the folio, it and any changes to it will be lost.Choose the profile to be used with the folio template, if any, and click Next. The Folio Template Check In page is displayed.
Enter the required information and click Check in. The Folio Template Check In Confirmation page is displayed. It is a good idea to choose a descriptive title for the template, as it is the title that is displayed in the Folio Template choice list on the Pick Folio Type page.
Select how to proceed and click Finish. Options are:
Continue editing the folio template to add structure or content. The Create/Edit Folio Template Page is displayed. Add structure and content to the template and set template properties.
View content information for the folio. The Content Server content information page for the folio is displayed.
Currently Content Server ships with a default viewer that mimics the structure of the Create/Edit Folios page, and the following rendition options:
Zip
XML
Custom viewers and renderers can be developed, but at a minimum, require an understanding of the following:
the structure of the folio XML
the folio Idoc Script functions and their proper usage
the Iterator/Renderer architecture
the method for using a component to modify/add to the list of viewers and renderers
If you would like to have custom viewers and renderers added, contact Oracle Consulting at http://www.oracle.com/consulting/index.html.