PK C_Eoa,mimetypeapplication/epub+zipPKC_EiTunesMetadata.plist^ artistName Oracle Corporation book-info cover-image-hash 259385735 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 911800271 publisher-unique-id E26695-03 unique-id 318625648 genre Oracle Documentation itemName Oracle® Fusion Middleware Using Oracle WebCenter Content, 11g Release 1 (11.1.1) releaseDate 2014-01-22T13:34:14Z year 2014 PKTc^PKC_EMETA-INF/container.xml PKYuPKC_EOEBPS/records.htm Working with Records

25 Working with Records

This chapter provides an overview of common tasks involved in managing content that is designated as a record. A record is usually managed with a retention schedule and is assigned a life cycle according to disposition rules for the content. The retention schedule and life cycle are developed by a person designated as a record administrator.

This chapter covers the following topics:

25.1 Understanding Retention Management

The Records software managed content items that are on a retention schedule. The focus of records management tends to be the preservation of content for historical, legal, or archival purposes while also performing retention management functions. The focus of retention management tends to be the scheduled elimination of content based on a schedule designed by a record administrator.

This software combines both record and retention management into one software system. It can track and preserve content as needed, or dispose of content when it is no longer required.

The following terms are used when explaining retention management:

25.1.1 The Retention Process

The following steps outline the basic workflow of retained content:

  1. The retention schedule and any required components, such as triggers, periods, classifications, and custom security or metadata fields are created by an administrator.

  2. Items are filed into the retention schedule by users. The filed items assume the disposition schedules of their assigned category.

  3. Disposition rules are processed in accordance with the defined disposition schedules, which usually have a retention period. The processing is activated by either a system-derived trigger or custom trigger. The trigger could affect one or more items simultaneously.

  4. Whenever a disposition event is due for action (as activated by a trigger), an e-mail notification is sent to the person responsible for processing the events. The same is true for review. The pending events and reviews are displayed in the pages accessed from the Retention Assignments links within the user interface.

  5. The Records Administrator or privileged user performs the review process. This is a manual process.

  6. The Records Administrator processes the disposition actions on the pending dispositions approval page. This is a manual process.

  7. A batch process is run to process an approval.

Many disposition schedules are time-based according to a predictable schedule. For example, content is often filed then destroyed after a certain number of years. The system tracks when the affected content is due for action. A notification e-mail is sent to reviewers with links to the pages where reviewers can review and approve content and folders that are due for dispositions.

In contrast, time-event and event-based dispositions must be triggered with a non-system-derived trigger (a trigger that was defined for a particular scenario). For example, when a pending legal case starts litigation, the Records Administrator must enable the custom trigger and set its activation date because the start date information is external. Custom triggers can define event and time-event based disposition actions based on the occurrence of a particular event.

25.1.2 Physical Content Management

While the Records system enables organizations to manage the retention and disposition of content, PCM provides the capability of managing physical content that is not stored in electronic form.

All items, internal and external regardless of their source or format, are managed in a single, consistent, manageable infrastructure using one central application and a single user interface. The same retention schedules are used for both electronic and physical content.

PCM tracks the storage locations and retention schedules of the physical content. The functionality provides the following main features:

  • Space management, including definition of warehouse layout, searching for empty space, reserving space, and tracking occupied and available space.

  • Circulation services, including handling reservation requests for items, checking out items, and maintaining a due date for checked-out items.

  • Chargeback services, including invoicing, for the use of storage facilities and/or actions performed on physical items.

  • Barcode file processing, including uploading barcode information directly into the system, or processing barcode files manually.

  • Label creation and printing, including labels for users, storage locations, or individual physical items.

  • Retention management, including periodic reviews, freezes and litigation holds, and e-mail notifications for pending events.

25.1.3 Understanding Roles and Permissions

The Records functionality contains several default roles which allow users to access specific parts of the product. Administrators can customize these roles by including specific rights, providing a fine level of access to tasks.

The following list describes default predefined roles. Consult your administrator to see what additional roles may be in use at your site:

  • rma, or the Record User. This role is usually assigned to basic users and allows them to perform basic management tasks.

  • rmalocalrecordsofficer, or the Records Officer. This role is usually assigned to "privileged" users, who have all the permissions assigned to basic users (rma role) but are also granted rights to perform additional functions.

  • rmaadmin, or the Records Administrator. This role is usually assigned to administrators who are responsible for setting up and maintaining the management infrastructure and environment. These users have the widest range of rights to perform management tasks.

  • pcmrequestor, or PCM Requestor. This role is usually assigned to users who have all the permissions assigned to basic users without a Physical Content Management role but are also granted additional rights to perform some functions not allowed for basic users.

  • pcmadmin, or the PCM Administrator. This role is usually assigned to administrators who are responsible for setting up and maintaining the physical content management infrastructure and environment.

Each of these predefined roles comes with a default set of permissions and rights, but these can be modified. New roles with assigned management rights can also be created.

To view assigned roles and rights, click the user name in the top right portion of the window. The roles assigned to the logged-in user appear at the top of the My Profile information.

To see rights assigned, choose Records then Rights. The Assigned Rights shows the rights assigned to the current user for the enabled components. To view details about each component, click the Show link for that component. To view details about all rights, click the Show All Rights link at the top of the window. To hide rights again, click the Hide link in the component section or at the top of the window.

25.1.4 Interface Overview

Four main menus are used to access functionality; however, this product is highly configurable, so the options seen on any menu may vary depending on what options have been enabled.

The following four primary menu locations are available:

  • Top menu: This menu contains a Records option as well as a Physical option (if Physical Content Management is enabled). This menu can be used to quickly access different parts of the Records system and Physical Content Management (PCM) products.

  • Page Actions menu or Page menu: On many pages, an Actions menu (a small box with horizontal lines in it) appears at the top of the page. Options in this menu pertain to the items at that level in the hierarchy. For example, an Actions menu appears on the Exploring Retention Schedule page. At that level of the product hierarchy, reports about the retention schedules can be created.

  • Table menu: On most pages that list items (triggers, retention categories, content items) a menu appears at the top of the listing. By selecting a box next to an item, multiple items can be affected at one time. For example, on an Exploring Retention Category page, options appear above the listing of items in that category.

  • Individual Actions menus: Items listed on a page will often have an individual Actions menu. The options on these menus vary depending on the item and its location in the retention hierarchy.

    The following list summarizes the most commonly seen individual Actions menu options:

    • Information: Used to access information pages for folders, life cycle of the item, recent reviews, metadata history, and retention schedule reports. On some Information pages, additional options appear to edit or revise the displayed information.

    • Edit: Provides quick links to edit pages for folders or reviews, and options to alter an item's status by moving, closing, freezing, or unfreezing an item.

    • Set Dates: Provides quick links to actions associated with dates, such as marking items for review, canceling, rescinding, and expiring items.

    • Delete: Provides options to delete the item or perform a recursive delete (delete an entire tree if multiple items are checked).

    • Create: Provides options to create items appropriate to the location in the hierarchy. For example, if this is the Actions menu for a retention category, Create sub-options include Series and Retention Category.

25.1.4.1 Dashboards

Dashboards allow immediate access to frequently used aspects of the software. Each dashboard is composed of panes that hold different types of functionality, such as search boxes, lists of information, or access to other websites. The dashboard can be customized so frequently performed tasks, such as pending reviews, pending approvals, and so on, are easily accessible.

If actions can be taken in a dashboard pane, icons appear in the top right corner of the pane. Those icons can be used to perform actions directly from the dashboard. For example, if you have a Pending Review list in one pane, you can select the check box for a review then click the Approve icon (a green checkmark). The review will be approved directly from the dashboard.

Default dashboards are provided. To access this functionality, choose Records then Dashboards. Choose User to access the user dashboard. If you are assigned administrative privileges, another dashboard is available. To view it, choose Admin.

To select a dashboard for use:

  1. Choose Records then Dashboards.

  2. Select the dashboard to use from the list.

  3. On the Dashboard page, choose Actions then Set as Home Page to use the dashboard as a home page at login. To remove the dashboard as the home page, click the user name in the top right corner of the window. On the My Profile page, select Remove Dashboard Home Page.

To edit the default dashboards or other personal dashboards:

  1. Choose Records then Dashboards. Select the dashboard to edit.

  2. On the Dashboard page, choose Save As from the Actions menu. The default dashboard must be saved under a new name before it can be edited. Enter a new dashboard name and a dashboard title. Click OK when done.

  3. The dashboard opens in edit mode.

    • To move a pane from one location to another, put the cursor on the border of the pane. Hold down the left mouse button and drag the pane to another location.

    • To delete a pane, click the X in the upper corner of the pane.

    • To set individual options for each pane, click the Options menu in the upper corner of the pane. Note that not all panes have an option list.

    • To replace a pane, first delete the pane. An empty pane is displayed. Click Other Dashboards to populate the search list. The Search for Items dialog opens. Use this search form to find panes to use in the dashboard.

      Select metadata fields for searching or click Search to search the entire database.

      The Dashboard Results page opens, showing those items that can be used in the dashboard.

      Select the box next to the items to include and click Next. The Select Dashboard list is populated with the items that were selected. Click an item from the list to include in the pane and click OK.

  4. When done, choose Save Changes or Save As from the Actions menu to save the dashboard under a new name.

To create a personal dashboard:

  1. Choose Records then Dashboards then Create New from the Top menu or choose New Dashboard from the Content Management menu.

  2. On the Create/Edit Dashboard page, choose the number of columns to appear on the dashboard by selecting a number from the list.

  3. In the first pane, click Other Dashboards to populate the list of dashboards for use.

    Use the displayed search form to find panes to use in the dashboard. Select metadata fields for searching or click Search to search the entire database.

  4. On the Dashboard Results page, select the box next to the items to include and click Next. The Select Dashboard list is populated with the selected items.

  5. Select an item from the list for the pane and click Ok. Repeat this process for the other panes in the other columns. To delete a pane click the X in the corner of the pane window.

  6. When done selecting panes for use, click Actions then Save Dashboard.

  7. To use a Simple Profile to associate with the dashboard, select it from the list. Click Next when done.

  8. Enter the necessary metadata on the check-in page to save the dashboard. Click Checkin when done.

25.1.4.2 My Favorites

Users can create a listing, similar to bookmarked browser Favorites and add series, categories, folders, reports, report templates, users, and aliases to this listing. Users with administrative privileges can add other objects such as freezes to the listing.

If an item can be added to a Favorites listing, the Add to Favorites menu option is displayed on a page. To add items to these lists, select the box next to an item and click Add to Favorites.

Favorites can be shared with other users. To make a Favorites list available for sharing, click the user name in the top right corner of the window. On the My Profile page, click Yes in the Share RMA Favorites box. Click Update when done. The Favorites list will then be available to other users to select from.

To share an item in that list, select the check box for the item then choose Sharing and Share from the Table menu. To prevent sharing, choose Sharing then Unshare.

To add a favorite from another user, choose Records then Favorites from the Top menu. If a favorite list is available from another user, the Import From User table option is available in the list of favorites. Choose the Import From User option and select the name of a user from the list. All of that user's favorites for that particular Favorite type (for example, a Series or a Category) appear on the Favorites list.

Sharing favorite items is based on assigned rights. If a user does not have rights to share items then the Import From User option does not appear on that user's My Favorite list. For example, if you do not have the category.freeze, folder.freeze, or record.freeze right, you cannot access favorite freezes from other users.

To view items in the Favorites list, choose Records then Favorites from the Top menu. On the My Favorites page, click the indicated tabs to quickly find the favorites of a specific type (for example, Categories or Series).

Use the Up or Down arrow on the My Favorites page to rearrange the favorites in the list. The reordering in the list is not saved until the Save Now button is clicked, which appears when reordering begins.

Favorites items are used to populate option lists, such as when creating freezes or when checking in content. For example, if an item is on a Favorites list, it appears on the list when a freeze name is selected or when a category is selected during content checkin. This helps to narrow down the choices on large option lists.

25.2 Creating Records and Physical Content

Content can be created from the Main menu, from within retention schedules, or existing content can be marked as usable for retention. For example, if you work with Oracle WebCenter Content to manage content outside of a retention schedule, you can file content into a retention schedule without moving outside of the Content Server. You do this by accessing the content check-in form from the Main menu.

If you work mostly within retention schedules and are within a schedule hierarchy, you can create the content item at your current position in the hierarchy by choosing Check in New Content Item from the Actions menu for the retention object.

25.2.1 Checking In From the Main Menu

If profiles have been created by the administrator, those profiles appear on the New Check In menu. A profile "hides" fields so only those fields essential for check-in are shown. This makes the process faster and less prone to error.


Important:

The fields on the check-in pages are dependent on the profiles used for the check-in and the configuration of the system. See the Records Administrator for details about what triggers are used for profiles and what fields are to be expected on the check-in pages.


Content can be checked into a category or a record folder. To check in content:


Tip:

Use this method of filing content items when filing items to disparate locations and to navigate to a different location within the retention schedule with each checkin.


  1. Choose New Check In. If profiles are available, several different options may be available. Select the profile or type of check-in to do.

  2. Enter or choose information pertinent to the item. The following list describes some of the common fields on the checkin page:

    • Type: File type chosen from a list.

    • Title: Descriptive name for the item. Maximum: 80 characters.

    • Filer: User checking in the item. Administrators can choose a user name from a list.

    • Security Group: Security group associated with the item. Default: RecordsGroup.

    • Primary File: Path and file name of the item. Maximum: 80 characters for file name, 8 characters for extension. Click Browse to select the item.

    • User, Group, Role Access List: if Access Control Lists are enabled, this is used to set permissions for specific users or groups.

    • Alternate File: Path and file name of a web-viewable file or one that can be converted to be web-viewable. The file extension cannot be same as that used in the Primary file. Maximum: 80 characters for the file name, 8 characters for the extension. Click Browse to find and select the item.

    • Content ID: Identifier for the item. Maximum: 30 characters. No special characters can be used. If this field is filled in, the system is automatically configured to assign IDs.

    • Revision: Generated automatically with each iteration of the item. Do not change this value.

    • Comments: Additional notes. Maximum: 255 characters.

    • Date, Format and Audit Information: Date a record is activated or expired in the system, as well as information about the auditing of the item.

    • Security information: Classification information, supplemental marking information, and classification topic information.

    • Subject to Review information: Fields indicating if an item is subject to review, and the reviewers and review period.

    • Correspondence Information: Information pertaining to e-mail.

  3. If an auxiliary metadata set has been created, click that option in the top right corner of the page. Additional metadata fields appear containing information for the item.

  4. To associate the item with a category or folder, click Browse next to the Category or Folders field at the bottom of the page.

  5. In the Select Category or Folder dialog, choose the category or folder in which to file the item. If categories or folders were added to a My Favorites list, they appear on the list and are easily selected.

  6. Assign a supplemental marking to the item. A user must be assigned a supplemental marking in order for markings to appear on the list of supplemental markings that can be used at checkin.

  7. Click Life Cycle Preview to view the disposition actions associated with the category selected earlier.

  8. After entering all the appropriate metadata values, click Check In. A confirmation page is displayed.

25.2.1.1 Checking in Items Using DIS

If Desktop Integration Suite is installed, new files can be checked in from Microsoft Office by using the Copy and Paste options in the right-click menu. If an item is currently checked out, a user can check it in using the Offline Content Manager or by choosing the Check In option on the right-click menu.

To check in an existing file from Microsoft Office, click File then Save and select the server option in the Save dialog. The content check-in form opens for the last instance used.

If the DoD component is enabled, files may not be able to be checked by copying and pasting or dragging and dropping them into contribution folders. When using DoD features, the Category or Folder field is required. This means an item cannot be checked in if that field is empty. The actions of copying and pasting or dragging and dropping into a contribution folder often doesn't require further user intervention, so often the check-in cannot complete successfully.

25.2.2 Checking In Through a Retention Schedule

The proper security privileges are required to access the category or records folder in use. To create an item from within a retention schedule:


Tip:

To save time when filing multiple content items into the same category or folder, check in the content from within the retention schedule this way. It eliminates the need to select the Category or Records Folder ID fields to navigate to the location each time because the check-in form is presented in context to its location as shown in the Retention Schedule locator links. To further expedite the filing process, use the Check In Similar feature.


  1. Click Browse Content then Retention Schedules.

  2. On the Exploring page, choose a Retention Category for use. From the item's Actions menu, choose Create then the type of content: Record, Folder, New Content Item, or New Physical Item.

  3. Click Life Cycle Preview to view the disposition actions associated with the category selected earlier.

  4. After entering all the appropriate metadata values, click Create.

  5. If similar content is available to check in, click Check In Similar on the confirmation page to pre-populate the form and expedite the process.

25.2.3 Checking In a Classified Item

Classified items require protection against unauthorized disclosure (for example, because they contain information regarding security or insider information). Unclassified content is not and has never been classified. Declassified items were formerly classified, but the classified status has been lifted.

Classification is an optional security feature certified to comply with the Chapter 4 requirements of the DoD 5015.2 specification. A site administrator can choose whether to enable this functionality and make it available.


Important:

Executive Order 12958: Classified National Security Information describes in detail the system for classifying, safeguarding, and declassifying national security information. If you are using this product to comply with that order, you should be familiar with proper classification protocols.


To check in content from the Main menu:

  1. Access the content check-in form as described previously.

  2. Enter optional information pertinent to the item.

  3. To associate the item with a retention schedule, click Browse next to the Category or Folders field at the bottom of the page.

  4. In the Select Category or Folder dialog, choose the category or folders in which to file the item. The file pathname is displayed under the field.

  5. Specify information pertinent to classifications:

    • The agency classifying the content (optional).

    • The person classifying the content. This is mandatory unless the data is derived from a specific topic, in which case it is optional.

    • What the classification is derived from. This is mandatory unless there is a specific "classified by" person identified.

    • The topic derived from unless there is a specific person classifying the item.

    • The classification at the time of record creation. For example, Top Secret, Secret, Confidential, and so forth.

    • The type of classification. For example, military plans, foreign government information, cryptology, and so forth.

    • A declassification exemption category. For example, reveal intelligence source, reveal military plans, and so forth.

    • The event triggering the declassification of the item.

    • A date triggering the declassification of the item.

    • Enable automatic declassification. If this functionality is enabled the Is Auto Declassification Date option appears. Select this option to allow automatic declassification of the item.

    • How the item can be downgraded. Choose date, event, or date and event.

    • An event triggering the downgrading of the item classification. This is mandatory if it was specified how the item can be downgraded.

  6. After entering all the appropriate metadata values, click Check In. A confirmation page is displayed.

25.2.4 Folios and Content Basket

Content Folio is an optional component automatically installed with the Records system. It can be used to assemble and track groupings of content items in a virtual container such as a content basket. The Content Basket can contain any number of items managed by Oracle WebCenter Content, the Records system, Physical Content Management, or other add-on products.

Folio configuration is performed by administrators and can include custom template design and the creation of specific folio hierarchies designed to help manage content. This chapter does not discuss the details of folio use except how it interacts with the Content Basket. For more details about the use of folios at the organization, see the site administrator.

Items can be added to the Content Basket from the item's information page or Search Result page using options from the menus on those pages. The information in the Content Basket page includes a thumbnail depicting the type of item, the content ID for the item, the item's title, native file name (if any), and source name. If the item is a physical item, source will always be Physical.

The default order for items in the content basket is the order in which they were added. Any new items are added to the bottom of the list. If adding multiple items at the same time (from a Search Result page), then the items are added in the order in which they were displayed on the Search Result page. The order of the items in the basket can later be changed.

In previous versions of this product, each user was automatically assigned a content basket. In the current version of the software, users must create their own content baskets. Any items in the user's basket prior to upgrading are not retained.

25.2.4.1 Creating, Updating, or Deleting a Basket

To create a basket or update an existing basket:

  1. Choose My Content Server then My Baskets.

  2. To create a new basket, click Append Content Basket on the Content Basket Manager page and enter the name of the new basket.

  3. To delete a basket, select the Delete check box next to the basket name. If items are in the basket, they must first be removed before it can be deleted.

  4. To change a basket, edit the information.

  5. When done making all changes, click Update. The Content Basket Manager page opens again with the changes in place.

25.2.4.2 Setting an Active Basket

Before using content baskets, set one basket as the default to be used for activities involving content.

  1. Choose My Content Server then My Baskets. A list of defined content baskets appears on the menu.

  2. Select the name of the basket to be made active.

A user can also navigate to the Content Basket Manager page and click Active next to a content basket name. Click Update to make that basket the active basket.

Only one basket can be active at a time and it can be changed at any time.

25.2.4.3 Adding or Removing Items

To add items to a content basket:

  1. Search for the item(s) to add to the content basket.

  2. On the Search Result page, select the check box of each item to add to the content basket.

  3. Choose Actions then Add to Active Content Basket in the Table menu. Items can only be added to a basket designated as active. The Content Basket page opens, with the new item(s) added at the bottom of the list.

When items are removed, they are only removed from the content basket. They are not deleted from the system. To remove items from the basket:

  1. Choose My Content Server then select the name of the basket to use.

  2. On the Content Basket page, select the check box of the items to remove. Choose Actions then Remove Selected Items from the Table menu.

  3. To remove all items, choose Actions then Empty Content Basket from the Page menu.

25.2.4.4 Sorting Items

The order of the items can be changed by modifying the numbers in the Order Priority column.

  1. Click My Content Server then the name of the basket to reorder.

  2. On the Content Basket page, click Actions then Toggle Row Reorder. Click the Up or Down arrows on individual rows to move the item upward or downward.

25.2.4.5 Creating Reservation Requests for Items

To make a reservation request for one or more physical items in a content basket:


Note:

You can only make reservation requests for physical items.


If the content basket does not contain the item(s) to reserve, add them first.

  1. Click My Content Server then the name of the basket to use.

  2. On the Content Basket page, select the check box of each physical item and choose Request then Request Selected Items from the Table menu. To reserve all items in a content basket, choose Request then Request All Items.

    A prompt is displayed asking if the selected items should be removed from the content basket after they are reserved.

  3. Click Yes or No. Click Cancel to stop the reservation request.

  4. On the Create or Edit Request page, specify the properties of the new reservation request, such as the transfer method, priority, and delivery location.

  5. Click Create when done. The items are now reserved, and the administrator is notified of the reservation request. After the administrator processes the reservation request, it can be fulfilled in accordance with the procedures in an organization. If a reserved item is already checked out, the user is placed on a waiting list for that item.

25.2.4.6 Downloading Items

To download a zip file with one or more items in a content basket:


Note:

You can only download items in a zip file if the system has been set up to support this feature.


  1. Click My Content Server then the name of the basket to use.

  2. On the Content Basket page, select the check box of each item to download, and choose a download option from the Download menu on the Table menu.

    Selecting to download to a workspace stores items in the user's workspace location. A workspace is defined on the user's profile page. It can be an FTP or WebDAV server, a path on the local file system to a location, or Other (which downloads a zip file to be saved at a specified location). Selecting to download to the workspace stores the items in the user's workspace location. If the location is an FTP or WebDAV server and authentication is needed, a dialog is displayed and credentials must be entered.

    • Download Selected Items

    • Download All Items

    • Download Selected Items to Workspace

    • Download All Items to Workspace

    A zip file named Bundle.zip is created and a dialog is displayed with a prompt for the location to open or save the file.

The contents of the zip file depends on the type of item:

  • Internal (electronic) items: The zip file contains the selected rendition file for the item. The file name for the item is built up as follows:

    <Item_Title> (Primary|Web) [<Content_ID> Revision-<Rev. No.>].<File_Extension>

    where Primary refers to the native file rendition, and Web to the web-viewable rendition. For example: Report2005 (Primary) [CS12025 Revision-2].doc.

  • External (physical items): The zip file contains a file with the metadata, location, and retention information about the physical item, in the archive metadata format as specified on the Configure Records Management page. (See the Oracle Fusion Middleware Managing Oracle WebCenter Content for details.) The file name is built up as follows:

    <Random_Number> (External Item) [<Item_Name>].<File_Extension>

    where the file extension depends on the configured format setting. For example: 810871584 (External Item) [Contracts2009].hda.

25.2.4.7 Creating E-Mail Links to Items in the Content Basket

To create a new e-mail message in the default e-mail client, with information and links for one or more items in a content basket:

  1. Click My Content Server then My Content Basket.

  2. On the Content Basket page, select the check box of each item (rendition) to include in the e-mail message, and choose E-Mail Links then E-Mail Links to Selected Items from the Email Links menu at the top of the page. To include all items in the e-mail message, choose E-Mail Links then E-Mail Links to All Items.

    A new e-mail message window for the default e-mail client is displayed, with Content Item Rendition Links as the subject line and links and information for the items in the message body.

Some e-mail clients have limitations regarding the number of characters used in the body of a message. Adding a large number of items as links to an e-mail may exceed the limitation, resulting in some links not being listed.

Contents of E-Mail Message

What is included in the e-mail message for an item depends on the type of that item:

  • Internal (electronic) items: The e-mail message contains the content ID and title of each selected item, links to the selected rendition file(s) for the item.

  • External (physical) items: The e-mail message contains the name and title of each selected physical item, a link to the item's information page.

25.2.5 Folios and Cloned Content

Automatic cloning occurs when working with folios that are filed into restricted categories. A default rule in the Records system is followed that states all folios must be editable, revisionable, and deletable. If a folio is filed into a category that restricts any of these actions, it is cloned when a new revision is checked in.

If a folio is frozen, a clone is created because freezing restricts deletions and edits. If folio content is filed into a category that restricts edits, deletions, or revisions, it is cloned.

You can also manually create a copy of a specific revision of a content item by cloning the item. Unlike a simple copy of a content item, a fixed cloned copy is linked to the original version. A newly cloned copy can also replace (supersede) any previous cloned versions. The functionality to manually create a fixed clone is only available if the RmaEnableFixedClones configuration variable has been set to TRUE.

When creating a fixed clone, specify which category or folder will hold the item. The clone name is created with the title of the current revision with a suffix appended. Administrators can change the value of the suffix by changing a configuration variable. See the Oracle Fusion Middleware Managing Oracle WebCenter Content for details.

Cloning rules can be customized to override record restrictions. This process is not discussed in this documentation. See Consulting Services for more details.

The fixed clone appears in the original content item's Revision History Section with the Fixed Clone Icon designating its status. It also appears in a separate section in the Exploring page for the category or folder where the item was stored. If the clone has been frozen, the Frozen Fixed Clone Icon is displayed. Click either icon to view the Content Information page for that clone.

A new metadata field, Working Copy, is added to the Information page of the fixed clone. The name of the original content item or folio appears next to this field with a link to that item.

If a user has permissions to freeze an item (assigned to the Records Administrator role by default) the user can freeze fixed clones and freeze the revision associated with the fixed clone. Freezing is done by searching for the folio then selecting a Freeze option from the Table menu on the Search Result page. See the Oracle Fusion Middleware Managing Oracle WebCenter Content for details.

25.2.5.1 Creating a Fixed Clone

To create a fixed clone (this menu option is only available when a content item matches the criteria for cloning):

  1. Use searching or screening to find the content item to clone.

  2. Click the Info icon for the item.

  3. On the Content Information page, select the revision to clone by clicking the revision number in the Revision History Section.

  4. Choose Content Actions then Create Fixed Clone from the Page menu to create a fixed clone of the revision. Choose to supersede previous clones with this version by selecting the appropriate box. A prompt appears for the clone name and the location for storage (folder or category). Enter the name of the category or click Browse to choose an item from the Select Category or Folder dialog.

  5. Click OK when done. The Content Information page opens with the fixed clone icon in the Revision History Section indicating the action taken.

25.2.5.2 Adding a Folio to a Restricted Revision Category

To create a folio that is cloned for use in a restricted revision category:

  1. Choose Content Management then New Folio.

  2. Choose the type of folio to create and choose Load Folio.

  3. Click the plus icon to add a folio. Click Next. Select items from the search results for inclusion and click Next.

  4. On the folio page, choose Actions then Save Folio from the Page menu.

  5. Click Next in the dialog. Choose a title for the folio and a security group for the folio.

  6. In the Category or Folders field, choose a category that restricts revisions.

  7. Click OK and check in the folio.

  8. Browse to the category with restricted revisions. Note that the folio and a folio clone are listed.

25.2.6 Creating a Physical Item

When creating a new physical item, you check in its metadata, storage information, and retention schedule in the repository. This information is subsequently used to track the physical item and manage its life cycle.

You can also create a new physical item by choosing New Checkin then Electronic/Physical Checkin. Use that option to check in an item that is stored on another repository (such as an adapter system). The procedure is the same as that described here. Only the menu option is different.

A physical item can be created by simply checking in the item as a physical item. Other methods can also be used to create a physical item:

25.2.6.1 Using the Storage Page


Permissions:

The PCM.Physical.Create right is required and the Record.Create right is needed in the Records system to perform this task. The PCM.Physical.Create right is assigned by default to the PCM Requestor and PCM Administrator roles. The Record.Create right is assigned by default to the predefined Records Privileged and Records Administrator roles.


Use this option when creating a record for an item which has no electronic equivalent (such as a tape or a CD).

  1. Choose Physical then Storage.

  2. On the Exploring Storage page, choose Create Physical Item from the Actions menu for the location to store the item.

  3. On the Create or Edit Physical Item page, provide the information for the new physical item as required, including it storage and record-related information:

    • Title: Item's title. Maximum characters is 80.

    • Filer (author): Person submitting the item. The default is the current user. Administrators can select an alternative filer.

    • Security Group: Group where the item should be assigned.

    • Object Type: Select a type matching the object type of the storage location, if one is specified.

    • Media Type: Available media types depend on the object type.

    • Permanent Location, Current Location: Enter a location or click Browse to open a dialog used to browse the storage space hierarchy. Use the plus and minus symbols in front of a storage location to unfold or collapse all child locations. After selecting the desired location, click OK to return to the Create or Edit Physical Item page. Click Clear to delete the current storage path and select a new one.

      After selecting a location, the Permanent Location field contains a reference to that location. This is the barcode for the location or if no barcode is specified, it is a 19-digit number. Below the Permanent Location field, the full hierarchical storage path to the selected location is displayed.

      If a current location isn't set, it is set to OTHER. To set the location to a user, select Set Current Location to a User. If needed, enter a comment about the current location (for example, handling instructions).

      If a permanent location isn't provided, it is set to the current location.

    • Barcode label: Label for the item. This text is printed below the barcode on the label. If not set, it is set to match the item name in all upper case letter. If content IDs are automatically generated, the barcode matches the generated ID.

    • Type: Content type of the item.

  4. Click Create to submit the information about the new physical item to the repository.

25.2.6.2 Within a Retention Schedule


Permissions:

The PCM.Physical.Create right and the Record.Create right is required in the Records system to perform this task. The PCM.Physical.Create right is assigned by default to the PCM Requestor and PCM Administrator roles. The Record.Create right is assigned by default to the predefined Records Privileged and Records Administrator roles.


To create a new physical item in a retention category or records folder:

  1. Choose Browse Content then Retention Schedules.

  2. Navigate to the records retention category or records folder in the hierarchy to store the physical item.

  3. Choose Create then Check In New Physical Item from the Actions menu of the location where the item will be stored.

  4. Provide the information for the new physical item as required.

    The page does not contain the Life Cycle field because the physical item is automatically assigned the retention and disposition rules of the current (or inherited) retention category.

  5. Click Create to submit the information about the physical item to the repository. The Physical Item Information page for the new physical item opens with the Is Record field set to Yes.

25.2.6.3 Creating a Physical Item Within Another Item


Permissions:

The PCM.Physical.Create right is required to perform this task. This right is assigned by default to the PCM Requestor and PCM Administrator roles.


To create a new physical item within an existing physical item:

  1. Choose Physical then Storage.

  2. On the Exploring Storage page, choose Create Physical Item Within from the Actions menu for the location where the item will be stored.

  3. On the Create or Edit Physical Item page, provide the information for the new physical item as required, including it storage and record-related information.

  4. Click Create to submit the information about the new physical item to the repository.

25.3 Finding Records and Physical Items

The Search option can be used to search for records, just as any type of content can be searched.

When using Oracle Text Search the system does not index external items, including physical items. Therefore those items and other items stored externally (for example, on an adapter system) are not available for searching.

For details about using Federated Search for legal discovery purposes, see Managing Oracle WebCenter Content.

In addition to search-like functionality, screening can isolate retention categories, record folders, and content by their attributes. Screening enables a user to see what has happened or what could happen within a retention schedule.

If more results are returned than are configured in the User Profile page, the page navigation menu will change, indicating other pages of information available for viewing. The list of page numbers is updated as the user navigates through the pages. If there are fewer search results than are configured in the User Profile, no page navigation is displayed.


Important:

Depending on a user's role, rights associated with that role, and profile, different menu options may appear on a search or screening page. In general, system administrative users will see menus similar to those used to configure the system while end users will see menus containing typical functionality for users.


25.3.1 Searching for Content

To search for content:

  1. Choose Search then the repository for searching.

  2. On the Standard Search page, enter the criteria to use for the search. When searching folders, it is best to use Substring as an operand instead of Matches. Using the Matches operand narrows the search results considerably. Using Substring returns all internal content items as expected.

  3. To create a query for later use, select the search criteria and click Save. A prompt appears for a query name. Enter a name and click OK. The query is saved in the user's My Saved Query list in the My Content Server menu.

  4. To run the search immediately, specify the search criteria and click Search when done. The Search Result page opens, which lists all items meeting the search criteria.

25.3.1.1 Using the Search Forms Option

An expanded version of the search form can also be used or a custom search query can be constructed. To access these options, choose Search Forms from the Page menu of the Standard Search page.

  • Expanded form: By default, several sections of each search form are displayed using the collapsed format (for example, Correspondence Fields). When the expanded version of a search form is selected, all of the sections on the form are displayed.

  • Query builder: The Query Builder form is available from the Search Forms menu at the top of the page on any of the search pages. It enables a user to easily build and save complex queries by selecting options from a series of lists and operator fields. After a query is built using the Query Builder from, the user can edit the query directly, perform the search, or save the query for easy access from the saved queries list or through a targeted quick search.

    The Query Builder form displays the Include Child Records Folders box. If selected, the search function returns any matching results within child record folders. For comprehensive information about the Query Builder form, see Section 17.5.3.

25.3.1.2 Using Auxiliary Metadata Sets

If an auxiliary metadata set has been created, the Auxiliary Metadata Set option appears next to the Search Forms option on the Page menu.

To search using metadata from that auxiliary set, click Auxiliary Metadata Set then click the name of the set before performing a search. Click OK. The search page is populated with the additional metadata fields, which can then be used for searching.

25.3.2 Searching for Physical Content

Physical content metadata (including storage information and retention schedules, if any) are stored in the repository. Information about physical items managed by PCM can be found using the basic search page or the advanced search page.

To search for physical items:

  1. Choose Search then Physical.

    To use the advanced search page, choose Search then Advanced Search on the Page menu.

  2. To create a query for later use, select the search criteria and click Save. A prompt appears for a query name. Enter a name and click OK. The query is saved in the user's My Saved Query list in the My Content Server menu.

  3. To run the search immediately, specify the search criteria and click Search when done. The Physical Search Result page opens, which lists all items meeting the search criteria.

25.3.3 Screening for Content


Important:

Depending on a user's role, the rights associated with that role, and the user profile, different menu options may appear on search or screening pages. In general, administrative users will see menus similar to those used to configure the system while end users will see menus containing typical functionality for users.


After installation, an additional Screening menu is available on the Search menu. In addition to search-like functionality, screening enables a user to isolate retention categories, folders, and content by their attributes. Screening enables the user to see what has happened or what could happen within a retention schedule.

Screening reports can be created immediately or they can be scheduled to be generated at a later time. This is especially useful for screening reports affecting large sets of content. Creating the screening report immediately might put a heavy load on the system, which could diminish its responsiveness and/or result in browser time-outs. To avoid the load on the system, schedule screening reports to be performed at midnight, an off-peak time in most environments.


Note:

Scheduling reports is usually limited to those users with administrative privileges.


The screening interface may use user-friendly captions or may use standard retention terminology. The interface depictions in this documentation show user-friendly captions.

The following screening topics are discussed in this section:

25.3.3.1 Performing Screenings

This section describes a general procedure to perform screenings. A search can be done by retention categories, record folders, and content by disposition, disposition event criteria, record folder and/or retention category criteria. Click Search without entering any criteria, and all items are returned in the results. Different repositories can also be searched (physical and electronic).


Permissions:

The Admin.Screening right is required to perform screening actions. This right is assigned by default to the Records Administrator role.


To screen data:

  1. Choose Search then Screening. Select the screening type (Categories, Folders, or Content).

  2. When screening content and records, you can select the sources to use for the screening on the Screen for topic page. If additional repositories are available (for example, physical content or an adapter repository), you can select the source from the list. If an additional repository is chosen, you should verify that the screening criteria used is also available in that repository. If a field is used for screening and it is not used in the external repository, an error is displayed.

  3. Depending on the type of screening chosen, different screening options are available. Select the criteria for the search from the provided menus.

    When screening content and records, the Update Sort Fields button is displayed. Click this button to open a dialog where the user can select multiple fields to use for sorting. For each field selected and moved to the Search Fields pane, a check box appears below the fields section. Select the box to further refine if the sorting for that field should be in ascending order. If not checked, sort order is descending.

  4. (Optional) if screening for a review or due date, specify the date in the Review Due By box or Due for Action box.

  5. Select a Freeze Status to filter by items that are frozen or not frozen.

  6. Select sorting preferences in the Results Options area.

    1. Sort by the default or select another option from the Sort By list.

    2. Sort in the default descending order or select the ascending order.

  7. Click Search. Any results matching the screening criteria appear in the Screening Results.

25.3.3.2 Scheduling a Screening Report


Permissions:

You must have Records Administrator or PCM Administrator rights to schedule screening reports.


You may be able to only schedule screening reports and not execute them immediately, depending on the setting of the Only allow scheduled screening option on the Configure Retention Administration page. See the Oracle Fusion Middleware Managing Oracle WebCenter Content for details about configuring the system.

To schedule a screening report:

  1. Choose Search then Screening then the screening type.

  2. On the Screen for Topic page, select the criteria for the screening and click Schedule.

  3. On the Schedule Screening Report page, provide a name for the screening report.

  4. Provide the start date of the screening report. This is the date the scheduled screening report will be generated. If the screening report is recurring, the first screening report will be generated for the first time on this date, and all subsequent reports at the end of each recurring period after this date.

  5. To create the report periodically rather than just once, select Is Recurring. Specify the interval at which the recurring screening report will be created (for example, every 2 weeks).

  6. Click OK when done.

The Scheduled Screening Reports page opens, which now includes the newly created scheduled screening report.

25.3.3.3 Setting Default Metadata For Reports


Permissions:

You must have Records Administrator or PCM Administrator rights to schedule screening reports.


Recurring screening reports are automatically checked into the repository. To set the default metadata for these checked-in reports:

  1. Choose Records then Configure. Choose Metadata then Screening Metadata Defaults.

  2. On the Default Metadata for Checked-In Screening Reports page, specify the default metadata for checked-in screening reports.

  3. Click Submit Update when done.

25.3.4 Browsing the Retention Schedule

Browsing content and navigating the hierarchy in the retention schedule can be done using various techniques. A user's permissions and security configuration determine what portions of the schedule the user can view. A user can navigate using these methods:

  • Accessing retention schedules using the Browse Content menu: When an object is clicked in the Browse Content area, the tree expands or collapses. By default, retained items can be accessed in the retention schedule object.

  • Accessing retention schedules using a search result: Click the link in the Name column on a Search Result page to navigate to child objects. Hover the mouse pointer over the name of a category or record folder to quickly view its description. Descriptions over 100 characters are truncated in the popup for easier viewing. The full description of a category or folder can be viewed on the relevant information page.

  • Accessing retention schedules using locator links: The locator link provides a convenient means of navigating a retention schedule. It shows the location in the schedule hierarchy, and provides links to click to quickly move between parent and child levels.

To view the contents of a retention object (a category or series):

  1. Choose Browse Content then Retention Schedules.

  2. On the Exploring page, click the name of the object to view.

  3. The appropriate object page opens. For example, if you elect to view the contents of a category, the Category or Series Content page opens.

To view information about a series or retention categories:

  1. Choose Browse Content then Retention Schedules.

  2. On the Exploring page, navigate to the item for which to see information.

  3. In the row for the item, do either of the following:

    • Click the Info icon.

    • Click the item's Actions menu and choose Information, then select the type of information to view:

      • Series: Information about a series.

      • Category: Information about a category.

      • Metadata History: A list of changes to the metadata of the item.

      • Disposition Information: Disposition instructions, defining how items in the category are handled.

    The appropriate information page opens (for example, the Series Information page or the Category Information Page). The page shows relevant information about the selected item.

25.3.5 Browsing the PCM Storage Space

PCM uses a defined physical space environment to keep track of the storage and retention of physical items. When working with a physical item, the item is assigned to a storage location, so PCM knows where it is stored and can track it.

Storage space in PCM is set up hierarchically. Storage locations contain other, smaller storage locations that contain still smaller storage locations, and so on. The default PCM functionality comes with the following storage space hierarchy (from large to small).

This section describes browsing the defined storage environment in PCM. It covers the following topics:

25.3.5.1 Browsing the Storage Tree

The Browse Content menu contains an item called Storage. This option enables a user to browse the defined storage space environment in a tree view with all defined storage locations in their hierarchical order. Note the following considerations:

  • The icons indicate the location type of the storage locations.

  • All storage locations include a percentage that shows how much of the available storage space in the location (and all its children) is currently occupied. For example, 25% means one-quarter of the maximum allowed number of stored items is currently assigned to the storage location (and all its children). The percentage of a storage location is automatically updated. However, the percentages of the parent storage location(s) are not updated automatically. This is done automatically daily (see next note).

  • By default, the available storage space for the entire hierarchy is recalculated daily at midnight. Therefore, the storage availability information may not be entirely up to date as the day progresses because it still reflects the situation from the night before.

  • The Browse Storage tree will always include a storage location called Other at the bottom. This is the default storage location for any physical items not explicitly assigned to another storage location.

  • Click any linked item in the storage space tree to see its Location page.

25.3.5.2 Using Exploring Pages

The Exploring [Location] pages show the child storage location of a defined storage location. A list of all physical items stored in it can also be shown.

  1. Click Browse Content then Storage.

  2. The Exploring page for the top level (called Storage) opens. Use the links on this page to drill down in the storage space hierarchy. In the default Trays layout, navigate to a storage location in the tree view and click its link in the tree.

At the top of the page are locator links showing the current location in the storage space hierarchy. This trail allows a user to easily navigate between the levels in the hierarchy. Click any linked item in the trail to go to that level and show its Exploring page.

25.3.5.3 Viewing Information about a Storage Location

To view information about a storage location:

  1. Choose Browse Content then Storage.

  2. On the Location page, navigate to the storage location and click the Info icon.

    You can also choose Information then Storage from the Actions menu for a storage location in the list to view that location's properties.

  3. Click OK when done viewing information.

25.3.6 Generating a Retention Schedule Report

A report can be generated at any time for any portion of the retention schedule to which a user has permissions. To generate reports for retained items:

To generate a report:

  1. Choose Browse Content then Retention Schedules.

  2. On the Exploring page, select the box corresponding to the item to use for the report. Choose Reports then Retention Schedule on the Page menu.

    A retention schedule report is generated. Open the report and view it or choose to save the report as a file.

  3. Close the browser window when done.


Note:

The report is generated in either PDF or HTML form, depending on how the system is configured. If the generated file is in PDF format, it must be viewed using Adobe Acrobat version 6.0 or later.


25.4 Reservations and Chargebacks

Reservations are used to manage physical items. Items can be checked out to users, reserved for later use, or requested. A user can put a hold on items that are currently unavailable (for example, someone else has the item). If others also made a reservation request for an item, that reservation is put on a waiting list, which specifies the order in which people made a reservation for the item. A reservation request may comprise multiple items.

Chargebacks are fees charged to people or businesses for the use of storage facilities or actions performed on physical items in the storage facilities. They can also be used to provide an explanation for storage actions.

Invoices can be generated for the storage, use, reservation, and destruction of the managed content. The invoices can then be sent to internal or external customers in accordance with applicable business procedures.

For complete details about creating customers, charges, and reservations, see Managing Oracle WebCenter Content.

25.5 Creating a Records Profile

Profiles limit information shown on often-used pages, thus making it easier for users to see or enter only information that is directly relevant. Profiles can be considered a type of filter for what information is displayed.

Simple Profiles are based on Content Profile functionality. Content Profiles is a field-based approach to customizing content pages. Simple Profiles is a form-based application. A software wizard tool steps the user through the process of creating a profile. Users can customize the forms by choosing what fields will appear, the order of the fields, and can create tool tips and prompts to remind the user of needed actions and valid entries.

Most users do not have the security privileges required to use the Content Profile tool in the Configuration Manager applet, but all users are able to use Simple Profiles, regardless of their security privileges.

The Simple Profile functionality meets Department of Defense 5015 certification requirements and enables individual users to set their own defaults for a personal profile.

25.5.1 Creating a Profile

System profiles are created by an administrator and can be accessed by any user. Personal profiles are created and configured by a user for personal use. If a administrator sets up a personal profile, it is available for use only by the administrator, not to others in the enterprise.


Permissions:

The Records User right is required to create a personal profile. To perform any administrative functions, the Record Administrator or PCM Administrator role is required.


A profile is composed of rules and a trigger value, based on a trigger field. Select the trigger field in the initial step of setting up the profile then use the Simple Profiles interface to set the rules to control the trigger.

The following topics are discussed in this section:

25.5.1.1 Trigger Fields

The first step in the profile process is to determine a trigger field. The trigger must match the following criteria:

  • It must be an option list metadata field. The fields that are defined as option list fields are the only fields that appear in the list for trigger selection.

  • After a trigger field has been defined for a system profile, it cannot be deleted from the system. (A user can delete a trigger field defined for a personal profile.)

  • A trigger field can be disabled by a administrator using the Profiles tab of the Configuration Manager applet. Click Select, then select none specified from the Add Profile page, then click OK.


  • Caution:

    If a trigger field is disabled, all profiles are disabled but they remain listed on the Search and New Check In menu. If a trigger field is changed after profiles have been created that use that field, the existing profiles could become invalid.


If a metadata field in a document matches a trigger value for a profile that profile is used for the document.You can have an unlimited number of profiles, but only one trigger value per profile. For example, if a trigger field is dDocType, Profile 1 can use a trigger value of ADACCT. Profile 2 can use a trigger value of ADSALES.

25.5.1.2 Rules

A rule is a set of metadata fields that determine how the fields are shown on the Check In, Update, Content Information, and Search pages. It also determines if fields are editable, required, hidden, excluded, or read-only. A rule can be evaluated for every profile (global) or can be evaluated for a specific profile.

A global profile is one that is always evaluated. Because profile rules are evaluated after global profiles, global profiles can be superseded by profile rules. However, administrators can set the priority for the global profile and increase its precedence.


Important:

Global system profiles affect all personal profiles that other users create. The defaults, descriptions, and labels that an administrator creates in this type of profile are used on the personal profiles other users create if the profile is made global.


25.5.1.3 Profile Pages

After determining the trigger value, set up the following elements in Simple Profile pages by using either the profile configuration Wizard (when creating a new simple profile) or the following page menu options.


Note:

Some of these elements are restricted to use by administrators only at a site. Available elements also may be limited by the configuration for a site.


  • Configure fields: Used to choose the fields to appear on forms and whether those fields are excluded, hidden, un-editable (read-only) or required.

  • Set field formats: Used to specify the formats for fields.

  • Set default values: Used to set the default values for fields.

  • Set derived values: Used to set the derived values for fields.

  • Group fields: Used to determine how the fields are grouped, the headings used, and any other descriptive information about the groups.

  • Set labels: Used to change the display names for the fields used in the profile.

  • Set descriptions: Used to add a field label tool tip for a field to explain the field usage.

  • Restrict options: Used to restrict what appears on a form or to determine the order of options in a list, depending on the field choice.

  • Set activation condition: Used to set the activation condition that changes profile behavior based on different inputs.

  • Limit access (Administrators Only): Used to limit access to a system profile based on a security group.

  • Set search order: Used to set the search order for search results and the direction of a search (ascending or descending).

Include as many of these elements as needed in the profile.

Designing a profile consists of a number of steps. The exact number and order of the steps depends on the elements to be included in the profile. This document describes all the steps. Choose the steps needed for the profile.

25.5.2 Designing a Simple Profile

System profiles are profiles that can be used by all users. These are typically created by administrators. Personal profiles are profiles that are created by individual users for their own personal use. The following sections describe how to create and configure a profile.


Note:

Some tasks are restricted to administrators.



Tip:

When creating a new profile, you can test the effects of the profile and then edit the functionality. You can exit the Wizard at various points in the profile creation process and view the effect of the profile. To return to editing the profile, choose Edit, then Update Profile from the Page menu bar for the profile. If you have closed the profile, from the Profile Listing page choose Edit, then Update Profile from the Actions menu for the desired profile. Use the Wizard page menu to quickly navigate to the specific page you need to update.


25.5.2.1 Adding a New Profile

Follow these steps to create a new system or personal profile using Simple Profiles. Add as many elements to the profile as needed. The pages shown in the Wizard depend on the elements selected in the Wizard fields.

  1. Access the Simple Profile functionality on the system depending on the type of profile to be created:

    • To create a personal profile, choose My Content Server then My Simple Profiles then choose the profile type. Select Create then Create Profile. Profiles created in this fashion will appear as a menu selection on the Check-in and the Search menus.

    • Administrators: To create a system profile that can be used by all users, choose Records then Configure then Simple Profiles. Choose the profile type. Select Create then Create Profile.

    • To create a system profile for Physical Content Management, choose Physical, then Configure then Physical Profiles. Select Create then Create Profile.

    • To create a global profile that will be applied to every profile, choose Create Global Profile instead of the Create Profile option. A global profile is one that is applied to every profile and which may override other profile behavior. Global profiles are applied in order of the priority assigned to the profile. Use this option with caution.

  2. Enter a name for the profile. This name can be a maximum field length of 50 characters and cannot contain special characters (; @ &, and so on).

  3. Enter a label for the profile. This name appears in the New Check In menu list and in the Search menu list.

  4. Enter a description for the profile.

  5. Choose the trigger value for the profile. When the trigger field matches this trigger value, the profile is used. Depending on the type of trigger chosen, a list may be available where a value can be selected.

  6. If the rules in a profile should be used globally, select Is Global. Global rules are those that are always evaluated, regardless of the criteria selected for the profile. An administrator can apply global rules to a system profile, which will affect all users. A user can apply global rules, but those rules apply only to the user's personal profiles.


    Important:

    Global rules for a system profile may affect personal profiles. The defaults, descriptions, and labels created in the system profile may affect pages used in creating personal profiles.


  7. If global rule is selected, choose a priority number. A low priority number gives a lower precedence. The rule is executed before other higher priority rules, which means any changes made by higher priority rules may override those made by this rule.

  8. Leave Clear Search Trigger Value unselected to prevent pre-populating the trigger value specified in step 6. Default behavior is to allow the trigger value to be inserted on the Search pages that use the profile. By selecting this option, the trigger value is not used.

  9. Select the auxiliary metadata set or sets to use as a source for field values.

  10. Select the elements to include by selecting the appropriate check boxes in the Wizard Fields list.

  11. When finished selecting elements to include, click Save.

    The first page chosen for configuration opens.

  12. Make any configuration choices for each page in the Wizard. After specifying the configuration for each page, click Save, and the Wizard will continue with the next page in the sequence.

    To avoid saving the configuration for a page, click Reset to return the settings to their original values. At any time during this process the user can click Exit Wizard and the configuration is saved in the new profile, even if the user has not completed all the pages.


    Note:

    In some pages, if you choose a field but don't specify a value for it, a message will appear to tell you to specify a value.


  13. When you finish configuring the last page in the profile Wizard sequence, click Save. The Simple Profile Information page opens. From this page the user can update, delete, or copy the profile.

25.5.2.2 Using the Create/Update Profile Pages

The profile pages available for configuring a new simple profile depend on the options selected on the Create/Update Simple Profile page.

The following general procedure can be used to manage the information on any of the pages:

  • Click a field name to designate it for use. To designate a block of fields, click the first field, then press the Shift key and click the final field in the block.

  • Click the arrows to move the field from one location to another. A field can only be used in one location at a time. On some pages, arrows also can be used to sort the order of fields.

  • If a field has an additional element, such as a label to be associated with the field or a value that can be selected, that information appears at the bottom of the page.

  • To save the page and move to the next page in the Wizard sequence, click Save.

  • To exit the process and save the profile at any point, click Exit Wizard.

  • To reset the values on the page, click Reset.

  • To receive help information for the page, click Quick Help.

Actions Menu

The Actions for the individual profiles lists the following frequently used actions:

  • Profile Information: Opens the Simple Profile Information page for the profile.

  • Update Profile: Opens the Create/Update Simple Profile page where elements can be selected to include in the profile.

  • Delete Profile: Deletes the current profile.

Wizard Page Menu

The Wizard page menu shows the pages available for use in the profile using the configuration wizard. Move between pages in the profile by choosing a page from this menu.

Saving and Exiting

To exit the profile design process, click Exit Wizard on any design page. A message is displayed, indicating the configuration wizard has been exited. Click OK.


Important:

When you click Exit Wizard while using the configuration wizard, your profile is saved temporarily and does not appear on New Check In or Search menus for use. You must complete the design process and click Save in order to use the profile.


To reset the current page and lose all changes made to it, click Reset.

When finished the configuration on the page, click Save. The next page in the profile design sequence opens. When a user reaches the final page and clicks Save, the process is complete.

Selecting Fields for Inclusion

To select fields for inclusion, select Field Configurations from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Configuration page opens. Use this page to determine actions for the specified fields.

  • Excluded Fields: These fields are not available for use on any future pages used in the profile design process.

  • Hidden Fields: These fields can continue to be used even though they are not displayed. This allows a user to set defaults, descriptions, and other useful information for those fields that will remain on the form when the document is checked in.

  • Uneditable Fields: These fields cannot be altered during the Check In or Update process.

  • Required Fields: These fields must be filled in by the user. If a field is designated as required, a message can be included when prompted at the bottom of the page.

  1. Select the available fields to use and move them into the appropriate box on the opposite side of the page. Use the arrows to sort the order of the fields in each box.

  2. If a selected field also has a required message, it is shown in a Required Messages section on the page. Review the information and make modifications.

  3. When done, click Save.

    The next page in the profile creation process opens.

Set Field Formats

Select Field Formats from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Formats page opens. Use this page to specify formats for the fields in the profile.

  1. Select the available fields to use and move them to the Format Fields box.

    When a format field is selected, a Format Values section is displayed.

  2. In the Format Values section, for each format field, click the check box if a format hint is needed on the Check In page.

  3. For each selected field, enter a format value for a format different than the existing format. Formats specify the type of information that can be entered by the user when the field appears on a form, usually alphabetic, numeric, or alphanumeric.

    Use braces { } around a value to specify a regular expression. Pattern values include the following. All other characters are treated as literal values.

    • N or n: Can be any digit. Example: 0 to 9.

    • L or l: Can be any lowercase alphabet characters. Example: a to z.

    • U or u: Can be any uppercase alphabet characters. Example: A to Z.

    • B or b: Can be any lower- or uppercase alphabetic characters. Examples: a to z; A to Z.

    • A or a: Can be any alpha-numeric characters. Example: a to z; A to Z; or 0 to 9.

  4. After setting all the field formats, click Save. The next page in the profile creation process opens.

Set Default Values

  1. Select the available fields to use and move them to the Default Fields box. When specifying a default field, a Default Values section is displayed.

  2. In the Default Values section, for each default field a field value can be entered. Select Advanced where Idoc Script can be entered to specify how the default value is used after evaluation for processing.

  3. After setting all default values, click Save. The next page in the profile creation process opens.

Select Field Defaults from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Default Values page opens. Use this page to set default values for the fields in the profile.

Set Derived Values

Select Field Derived Values from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Derived Values page opens. Use this page to set derived values for the fields in the profile.

  1. Select the available fields and move them to the Derived Fields box. When a derived field is specified, a Derived Values section is displayed.

  2. In the Derived Values section, for each derived field, specify a derived value. Select Advanced where Idoc Script can be entered to specify how the derived value is used after evaluation for processing.

  3. After setting all derived values, click Save. The next page in the profile creation process opens.

Grouping Fields

Select Field Groups from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Groups page opens. Use this page to group fields together on the Check In, Update, Search, and Content Information pages.


Note:

If you chose to configure fields and excluded some fields on the Simple Profile Field Configuration page, those fields do not appear for use on this page. In addition, if you chose to hide fields, those fields do not appear for use on this page.


  1. Select the available fields to use and move them to the Default box or an added group box. The Default box can be used for information that has pre-defined defaults, or for any fields that should appear at the bottom of the form that uses the profile.

  2. To create a new group, click Add Group then enter the following information on the Edit Profile Group dialog:

    1. Enter a name for the new group. The ID can be a maximum of 50 characters and should not include special characters (#, @, etc.)

    2. Enter a header for the new group. The header appears on the form when the profile is used.

    3. Enter a description for the new group. When the user's cursor is placed on the title on the form, this description appears as a field label tooltip.

    4. Enter any detailed information that identifies the new group.

    5. Select Is Allow Collapse to allow users to collapse the group when viewing the page.

    6. Select Is Initially Collapsed to collapse the group on initial use of the page.

    To exit without saving the group, click Cancel. When done creating the new group, click Save.

  3. To edit any group on the page, including the Default group, click the page icon next to the group title.

  4. To delete a group, click the delete icon in the group title line.

    The fields that were selected for inclusion in the group are returned to the Available Fields box.

  5. To rearrange the order of fields in a group, select a field, then click the Up or Down arrow to move the field into the appropriate position.

  6. When finished arranging the groups on the page, click Save. The next page in the profile creation process opens.

Setting Labels

Select Field Labels from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Labels page opens. Use this page to add labels to fields on the Check In, Update, Search, and Content Information pages.


Note:

If you chose to configure fields and excluded some fields on the Simple Profile Field Configuration page, those fields do not appear for use on the current page. In addition, if you chose to hide fields, those fields do not appear for use on this page.


  1. Select the available fields and move them to the Labeled Fields box. If a labeled field is specified, a Label Values section is displayed.

  2. For each specified labeled field, a label can be entered for the field next to the field name.

  3. When done, click Save. The next page in the profile creation process opens.

Setting Descriptions

Select Field Descriptions from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Descriptions page opens. Use this page to add field label tooltips on the Check In, Update, Search, and Content Information pages.


Note:

If you chose to configure fields and excluded some fields on the Simple Profile Field Configuration page, those fields do not appear for use on the current page. In addition, if you chose to hide fields, those fields do not appear for use on this page.


  1. Select the available fields and move them to the Description Fields box. When specifying a description field, the Description Values section is displayed.

  2. Enter a short description for each field in the Description Values section. This description appears as a field label tool tip when the user places the cursor on the field label.

  3. If needed, enter a detailed description for a field. This description appears when the user clicks on the field label.

  4. When done, click Save. The next page in the profile creation process opens.

Restricting Options

Select Field Restricted Options from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Field Restricted Options page opens. Use this page to restrict the choices on any option lists used in the profile.


Note:

Only fields that have option lists associated with them appear for use on this page.


  1. Select the available fields and move them to the Restricted Fields box.

  2. Select the field to restrict in the Restricted Fields box and click Update Options.

  3. In the Restricted Options dialog, select values to use in the Available Options box and move them to the Selected Options box.

  4. To change the order of the options, click the Up or Down arrows. Use this tool to place more frequently used items at the top of the list.

  5. To exit without saving the group, click Cancel. When done selecting and arranging the options, click Save.

  6. When done selecting all option lists, click Save. The next page in the system profile creation process opens.

Setting Activation Conditions

Select Activation Conditions from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Activation Conditions page opens. Use this page to specify the event, action, or state that triggers the rules in the profile.


Important:

By default all of the conditions are selected. Remove the selection for those conditions you do not want the profile to use.

Not all combinations of activation conditions are valid and some may be mutually exclusive. Be careful when using combinations of condition types.


  1. Choose activation conditions by selecting the check box next to the appropriate activation condition:

    Event Activation Conditions

    • On request: When a search request is initiated.

    • On Submit: When a check in is initiated.

    • On Import: When an archive is imported.

    Action Activation Conditions

    • Check In New: When checking in new content.

    • Check In Selected: When checking in selected content.

    • Info: When accessing content information.

    • Update: When updating content information.

    • Search: When searching for content.

    Flag Activation Conditions

    • Is Workflow: When a document is in a workflow.

    • Is Not Workflow: When a document is scheduled for a workflow but not active in the workflow.


      Note:

      If no workflow check box is selected, the workflow state is ignored as a criteria for activation.


  2. Advanced box: To have a script activated whenever this profile is submitted, enter the Idoc Script here. See the Oracle Fusion Middleware Managing Oracle WebCenter Content for details about creating profile scripts.

  3. When done, click Save. The next page in the profile creation process opens.

Limiting Access (Administrators Only)

Select Limit Access Values from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Limit Access Values page opens. Use this page to specify if access to the system profile should be limited according to pre-defined security accounts, roles, and groups for the Check In and Search pages.


Important:

You can limit access based on a security group and an account (if accounts have been enabled). A user must belong to the security group and account in order to use the profile.

If a user is not a member of a security group, or a security group and an account, then the user will not see the profile in the Search or Check In menus.


  1. Limit access to the Check In page by choosing the security group from the menu. Only users in that security group are able to check in content using this profile.

  2. If accounts are in place, choose the account from the menu for the Check In page. Only users with that account and in the security group specified in step 1 are able to use this profile on the Check In page.

  3. If roles are set up, choose the role from the menu for the Check In page. Only users with that role and the account and in the security group specified in step 2 are able to use this profile on the Check In page.

  4. Limit access to the Search page by choosing the security group from the menu. Only users in that security group are able to search for content using this profile.

  5. If accounts are set up, enter the account name or choose the account from the menu. Only users with that account and in the security group specified in step 4 are able to use this profile on the Search page.

  6. If roles are set up, choose the role from the menu. Only users with that role and the account and in the security group specified in step 5 are able to use this profile on the Search page.

  7. When done, click Save. The next page in the profile creation process opens.

Setting the Search Order

Select Search Order from the Wizard Fields section on the Create/Update Simple Profile page. The Simple Profile Search Order page opens. Use this page to specify the criteria and order for Search fields. Move higher priority fields to the top of the Search Fields list.

  1. Select the available fields and move them to the Search Fields box.

    When a search field is selected, it is listed in the Search Criteria section.

  2. You can set the search order of fields by using the Up or Down arrows to assign a field a higher or lower sorting priority.

  3. In the Search Criteria section, to sort a field by ascending order, select the check box by the Search Field name. Fields are sorted in descending order by default.

  4. When done, click Save. If no more modifications are needed to the profile, click Exit Wizard. The Simple Profile Information page opens.

25.5.3 Profile Management

Keep the following points in mind when managing system and personal profiles created with the Simple Profiles component:

  • A copied profile contains all of the information in the original profile. Make certain to change any labels, defaults, or security groups in the copied profile.

  • All management functionality (updating, copying, deleting) is available from the page menu bar on the Simple Profile Information page and from the Actions menu for a profile.

  • When creating a profile, if the wizard was exited before finishing the profile by using the Exit Wizar%d option, any changes made up to that point by using the Save button are saved. The Reset button cannot be used to change them. Edit them using the Update Profile option.

  • Administrators Only: If a profile is moved to the Content Profiles applet it can no longer be modified using Simple Profiles.

  • Administrators Only: View the details of profiles created with Simple Profiles by using the Rules tab on the Configuration Manager applet. All of the rules created with Simple Profiles appear on that tab.


    Caution:

    Do not edit any rules created for a simple profile by using the Rules tab. Editing or deleting the rules invalidates the profiles.


The following tasks are typically done when managing profiles:

25.5.3.1 Viewing Profile Information

To view information about system and personal profiles:

  1. To view personal profiles, choose My Content Server then My Simple Profiles then the profile type to access the Profile Listing page.

    If you have administrative privileges, to view system profiles, choose Records then Configure then Simple Profiles. Choose the profile type to display the Profile Listing page.

  2. Click the Info icon for the profile to view.

25.5.3.2 Updating a Simple Profile

Updating a simple profile involves accessing a profile and modifying, adding, or deleting information.

  1. Access the Profile Listing page.

  2. Use one of the following methods to update information for the profile or its fields:

    • Click the Actions menu for the profile and select Edit, then Update Profile to access the Create/Update Simple Profile page for the profile.

    • Click the Info icon for a profile. This opens the Simple Profile Information page. From the Page menu choose any of the Configure Fields or Configure Profile options to configure the profile.

      Also, from the Page menu bar a user can choose Edit then Update Profile to open the Create/Update Simple Profile page.


    Note:

    A profile can be updated by using the Actions menu or a profile's Page menu bar to choose Edit then Update Profile to open the Create/Update Simple Profile page. When the Update Content Profile page is saved it automatically starts the Wizard for modifying the profile configuration. If you do not want to use the Wizard, use the Page menu bar to directly select a profile configuration type to modify.


  3. When finished making changes to a profile, click Save.

25.5.3.3 Copying a Profile

To copy a system or personal profile:

  1. Access the Profile Listing page.

  2. Click the Info icon for the profile to copy.

    The opens, showing the details of the profile.

  3. On the Simple Profile Information page, on the Page menu, choose Edit, then select Copy Profile.

  4. On the Copy Simple Profile page, enter the new profile name and new label.

  5. Click Copy when done. To change edits, click Reset to clear the edits made.

  6. Update the profile as needed.

25.5.3.4 Deleting a Profile

You must be an administrator to delete a system profile. You can delete your own personal profile. To remove a system or personal profile:

  1. Access the Profile Listing page.

  2. To delete a specific profile:

    • Click the Info icon for the profile to delete. The Simple Profile Information page opens, showing the details of the profile. On the Page menu bar choose Delete Profile.

    • Choose the Actions menu for the profile and choose Delete Profile.

    • Click Delete on any profile configuration page.

    A message is displayed, prompting to confirm the deletion.

  3. Click OK to delete the profile, or click Cancel to retain the profile.

25.5.3.5 Moving a Profile

To move a system profile to the Configuration Manager:


Important:

If you move a system profile to the Content Profiles applet in the Configuration Manager, you can no longer modify or work with the profile using the Simple Profiles component. You must use the Configuration Manager Content Profiles functionality instead. Note that physical profiles cannot be moved.


  1. Access the Profile Listing page.

  2. To move a system content profile to the Configuration Manager, use one of the following methods:

    • Click the Info icon for the system profile to be moved. The Simple Profile Information page opens, showing the details of the system profile. On the Page menu bar choose Edit then Move to Configuration Manager.

    • Click the Actions menu for the profile to move, then choose Edit then Move to Configuration Manager.

    A message is displayed, prompting to confirm the move.

  3. Click OK to move the profile, or Cancel to leave the profile as is.

25.5.3.6 Changing a Trigger Field (Administrators Only)

To modify the trigger field for content profiles:

  1. Access the Profile Listing page.

  2. To change the trigger field for content profiles, on the page click Configure Metadata Set.

  3. On the Simple Profile Information page, select a different trigger field from the list and click Save. A confirmation prompt is displayed showing that the profiles configuration has been saved.

  4. Click OK. The Profile Listing page opens.

25.5.3.7 Troubleshooting (Administrators Only)

To temporarily disable the Simple Profiles component to resolve an issue, change the flag to the following setting in the \config\config.cfg file:

IsSimpleProfilesEnabled=false
PKm %%PKC_EOEBPS/content_search.htm Finding Documents

17 Finding Documents

Oracle WebCenter Content stores the metadata you enter when you check in a content item in a database set up by your system administrator. You can search for content items using these metadata values. If your system administrator has configured the Oracle Text Search option or the database full-text search capability, then the text of content items is indexed and made available for searching as well.

Check with your system administrator to see which search solution or database is used and to see if full-text indexing is enabled.

This chapter covers the following topics:

17.1 Search Pages

You can search for content using one of the following ways:

17.1.1 Quick Search Field

With the Quick Search field, you can perform a search regardless of the page in the content area. The Quick Search field performs a substring search of the title and content ID metadata, and the indexed full-text if it is supported on your system.

A substring search is equivalent to including a wildcard at the beginning and end of the search term. For example, if you enter form in the Quick Search field, the search returns items with words such as forms, performance, and reform in the title or content ID metadata, or in the indexed full-text if it is supported on your system.

You or your system administrator can also build custom searches targeted to search one or more metadata fields you specify, and make them available through the Quick Search field. You can create targeted searches with either the Query Builder Form or Expanded Form.

The Quick Search field supports Internet-style search syntax, complex construction, and alternate query formats. For more information, see Section 17.9, "Using Additional Search Capabilities."

17.1.2 Home Page Search Fields

With the search fields on the Home page, you can perform a metadata search, a full-text search, or a combination of both. Only the most commonly used search fields are available from the home page.


Note:

Your home page may have a different appearance than the default "out-of-the-box" content server home page, which includes search fields. If search functionality is not available from your home page or to search on additional metadata fields, use the Search Tray or Advanced Search Page.


17.1.3 Search Tray

With the Search tray, you can perform a metadata, full-text, or combination search. Only the most commonly used search fields are available from the Search tray.

The Criteria tab on the Search tray displays a form where you can enter your criteria. The Results tab displays the search results.

17.1.4 Advanced Search Page

With the Advanced Search page, you can perform a metadata search, full-text search, or a combination of both on all available fields.

To access this page, click the Advanced link in the Search Tray or use the Search menu on the Toolbar.

The expanded form on the Advanced Search Page displays all search fields available to you on a single page. You can alternate between the expanded form and the query builder form using the Search Forms menu at the top of the search page.

You can also select a different search profile from the Switch Profile menu, if your system administrator has defined them for you. You can specify the default search form to use the Advanced Search page.


Note:

Queries built using the Expanded Form separate the metadata fields with the <AND> operator. Each search criterion entered into each field must be met for a result to be returned. For example, if you enter January into the Title field and presentation into the Type field, then a search finds content only if it has a presentation type and has January in the title.



Note:

When using Oracle Text Search with your Content Server instance, you cannot enter complex search queries into the Full-Text Search field on the Expanded Form of the Advanced Search page. Instead, you must use the Query Builder form.


17.1.5 Query Builder Form

The Query Builder form creates and saves complex queries by selecting options from a series of lists. After a query is built, you can edit the query directly, perform the search, or save the query for easy access from My Saved Queries.

With the Query Builder form, you can separate the metadata fields with either the <AND> operator or the <OR> operator. If you use the <AND> operator, then each search criteria entered into each field must be met to return a result.

If you use the <OR> operator, then only one of each field's criteria must be met. For example, if you enter January into the Title field and presentation into the Type field separated by <OR>, then results include content that has either presentation as the type or has January in the title.


Note:

When using Oracle Text Search with your Content Server instance, you cannot enter complex search queries into the Full-Text Search field on the Expanded Form of the Advanced Search page. Instead, you must use the Query Builder form.


17.2 Working with Search Results

You can specify how to display the results of your search based on the number of content items returned per page and the order of the content items. For example, to find the most recent files that match your criteria, sort the results by release date. If you are searching for specific text such as changed address, sort your search results by score.

Use the Results Options area of the Advanced Search Page to control the display of the Search Results page:

17.2.1 Displaying Search Results

To specify how to display the search results:

  1. Display the home page search fields or the Advanced Search page.

  2. Scroll down to the Results Options.

  3. Set Results Per Page to the maximum number of content items to display on each Search Results page.

  4. Specify the Sort By method and order.

  5. Click Search.

  6. From the Content Actions menu on a Search Results page, choose the view option to specify the search results view.


Notes:

  • The Clear button clears the search fields, but does not clear the Results Options settings.

  • The system administrator can use the Content Server Configuration Manager to add or remove sortable fields. To change the fields available for sorting, see your system administrator.


17.2.2 Changing the Search Results View

To change the default search results view:

  1. Display the User Profile page.

  2. Scroll down to the Search Template option.

  3. Click Search Template, and select the search result view.

  4. Click Update.

17.3 Search Result Templates

You can customize the metadata information you want to see on a search result. You can even specify different search results templates to be used for different saved queries. To personalize how search results are displayed, select an option from the list on the User Profile Page, or from the Search Results page. There are three templates available by default, and you have the option to create new views based on the three provided templates using the Search Results Templates for User page to identify the information and specify display options:

17.3.1 Classic View Template

The Classic template lists content items sequentially in single rows, based on the default sort field and order set on the User Profile page.

Graphic of native 11g classic view results
ColumnDescription

Content icon or Thumbnail image

Displays an icon based on the content type. Optionally, if your system administrator has set up Content Server to create a thumbnail image of the content, then it displays the thumbnail image.

Description

Title and Content ID: The title and unique identifier of the content item, linked to display a Web-viewable version of the content, if it is available. If no Web-viewable version is available, it links to the native file.

The title and content ID are displayed in all custom search result templates based on the Classic View, even if those fields are not specifically selected from the Classic View Template section of the Create/Edit Classic View Search Result Template page.

Author: The person who checked in the content item.

Revision: Identifies the revision number of the content item.

Release Date: The date the content item was released.

Comments: Comments entered when the item was checked in, if any.

Content Format: The format of the native file.

Rev.

Displays the revision number of the content item.

Actions

Displays the Actions menu for an item and the Content Info icon.

Actions icon: Click this icon to open a menu of actions for the selected content item.

Content Info icon: Click this icon to display the Content Information page.


17.3.2 Headline View Template

The Headline template by default lists items in a single line, with a minimum of information. The Headline template uses the sort field, sort order, and result count fields on the User Profile page to arrange the results.

Graphic of native 11g headline view results
ColumnDescription

ID

A unique identifier of the content item, linked to a Web-viewable version of the content item, if it is available. If no Web-viewable version is available, it links to the native file.

Title

Displays the title of the content item without any associated link.

Date

Displays the date the content item was released.

Author

Displays the user name of the person who last checked in the content item.

Actions

Displays the Actions menu for an item and the Content Info icon.

Actions icon: Click this icon to open a menu of actions for the selected content item.

Content Info icon: Click this icon to display the Content Information page of the selected content item.


17.3.3 Thumbnail View Template

The Thumbnail template by default lists items in a grid from left-to-right and top-to-bottom and displays an icon based on the content type, or a thumbnail image of the content if your system administrator has set up Content Server to create one. This template is particularly suited for displaying images and other graphic content. The grid arranges results based on the sort field and order set on the User Profile page.

Graphic of native 11g thumbnail view results
ItemDescription

Icons

Displays the Actions menu for an item and the Content Info icon.

Actions icon: Click this icon to open a menu of actions for the selected content item.

Content Info icon: Click this icon to display the Content Information page of the selected content item.

Thumbnail Icon or Image

Displays an icon based on the content type or a thumbnail image of the content if your system administrator has set up Content Server to create one, linked to a Web-viewable version of the content item, if it is available. If no Web-viewable version is available, it links to the native file.

Title

Displays the title of the content item without any associated link. To maintain the grid structure, long titles are truncated to a single line. Rolling the mouse over the title expands the text to display the full title.


17.3.4 Creating a Custom Search Result Template

To create a custom search result template:


Note:

If you have Oracle WebCenter Content: Records installed with Department of Defense (DoD) functionality enabled, the Security Classification field must always be displayed in a search result. If you do not include the Security Classification field when you customize a search result template, the Security Classification field is included automatically.


  1. Navigate to the Search Result Templates for User page.

    • From a search results page, choose Customize from the Actions menu.

    • Open the My Content Server tray and click My Search Result Templates.

  2. Click the Add Template icon in the Actions column next to the provided List template on which you want to base your custom template.

  3. If your custom template is not based on the provided Headline View template, skip to the next step. If your custom template is based on the Headline View template, on the Create Custom Template page, select a metadata field to display as a column from the Available Fields box, and click the right arrow. The selected metadata field is added to the Columns field. You must select and move each field separately.

    To reorder the column display, use the up and down arrows next to the Columns field. Click the up arrow to move the selected column to the left in the results template. Click the down arrow to move the selected column to the right in the results template.

  4. Select a metadata field to display in the Description column from the Available Fields box, and click Move Here beneath the Description box. The metadata field is added to the Description box. You must select and move each field separately.

    To reorder the column display, use the up and down arrows next to the Main Information field. Click the up arrow to move the selected item up in the Description column. Click the down arrow to move the selected column down in the Description column.


    Important:

    To display the selected fields, you must also display the Description metadata field as a column.


  5. Click Save.

17.4 Saving Queries

You can save and reuse search queries:

17.4.1 About Saved Queries

To quickly display results for a search that you perform often, you can save the search in the My Saved Queries folder in the My Content Server tray.

After you save a query link, you can modify or delete the link from your Saved Queries page.

You or your system administrator can also build custom searches targeted to search one or more metadata fields you specify, and make them available through the Quick Search field.

17.4.2 Saving a Query

To save a search as a query link on the Saved Queries page:

  1. Specify the search criteria you want to save.

  2. Choose Save Search from the Actions menu on the Search Results page.

  3. In the prompt dialog, enter a title to use as the link name for the saved query.

  4. Click OK.

    The new link is shown under the My Saved Queries tray.

17.4.3 Rerunning a Recent Query

To rerun a recent query:

  1. Open the My Recent Queries folder in the My Content Server tray.

  2. Double-click the link for the query you want to run.

    The output from the query displays on your Search Results page.

17.4.4 Clearing Recent Queries

To clear all recent queries from your My Recent Queries tray:

  1. Open My Recent Queries in the My Content Server tray.

  2. Double-click the Clear link.

    Content Server deletes all links except Clear from the My Recent Queries folder.

17.4.5 Creating Quick Search Queries

You can create targeted searches with either the Query Builder Form or Expanded Form. To customize the query string directly, you must use the Query Builder Form as shown in this procedure.

To build a targeted search available through the Quick Search field:

  1. Click My Quick Searches in the My Content Server tray.

  2. On the Quick Searches page, click Create New beneath the My Quick Searches area.

    To edit an existing Quick Search, choose Edit from the associated Actions menu. You must be an administrator to modify the quick searches defined by administrators.

  3. From the Search form menu on the Create/Edit Targeted Quick Search page, select the form to use to create the search query.

    The form you select when you create the quick search is the form you must use when you edit the quick search (the Search form menu is not available when you edit an existing quick search.)

    The Expanded Form is selected by default. If you want to manually edit the query text, use the Query Builder form.

  4. Specify a Quick Search Key to select the search from the Quick Search list. Use lower case letters or numbers. Searches are listed in ascending order based on this key.

    Duplicate keys within the My Quick Searches table are not allowed. Although it is best to use a single character, you can use multiple character keys to avoid duplicate key names. Only the first character acts as the shortcut. For Example, if you have keys a1, a2, and a3, the first time you press "a", you select the search associated with key a1. The next time you press "a", you select the search associated with key a2, and so on.

  5. Specify the Quick Search Label to display in the Quick Search list.

  6. Enter #s in one or more fields to represent the search terms entered by the user in the Quick Search field. To further restrict the search, you can provide specific values for one or more search fields, but you must include #s in at least one field.

    If you use the Query Builder form, you can manually edit the query when you click show advanced query builder options and then select Modify Query Text.

    For example, if you select the date field, the On or After operator, and specify #s to represent the user input, the resulting query text is:

    dInDate >= `#s`
    

    To create a query that shows check-ins within the last specified period of days, subtract the number of days entered by the user from the current date returned by the dateCurrent function:

    dInDate > `<$dateCurrent(-#s)$>`
    
  7. Specify the number of results to show on each page, or use the default.

  8. Specify how to sort the results, or use the defaults.

  9. Specify the template to use to format the results, or use the default.

  10. Click Save.

    The searches you create are displayed under My Quick Searches in the Quick Search menu.

17.5 Searching with Oracle Text Search

If you have a license to use Oracle Text Search (in Oracle Database 11g) or Oracle Secure Enterprise Search 11g, the Oracle Text Search option enables the use of those technologies as the primary full-text search engine for Oracle WebCenter Content Server.

Oracle Text Search can filter and extract content from different document formats in different languages. It supports a large number of document formats, including Microsoft Office file formats, Adobe PDF, HTML, and XML. It can render search results in various formats, including unformatted text, HTML with term highlighting, and original document format.

If the system administrator configured Oracle Text Search, this option enables you to find a content item or items based on information about the file, actual text in the file, or both. The system administrator can also configure Oracle Secure Enterprise Search (Oracle SES) as the back-end search engine for Oracle Text Search.

If your system administrator has configured the Oracle Text Search option, you can specify full-text and metadata searches and select options to filter the results of a search by categories:

17.5.1 Searching with the Expanded Form

On the Expanded Form, you can specify a metadata search, a full-text search, or both to identify a content item or items to search for. Also, you can specify result options.

Figure 17-1 shows part of the Expanded Form for specifying Oracle Text Search queries.

Figure 17-1 Expanded Form for Oracle Text Search

Graphic of native 11g expanded search form

To specify a search on the Expanded Form:

  1. On the Content Server home page, display the Home Page Search Fields from the Search menu or the Search Tray.

  2. In the Metadata Search area of the Expanded Form, you can enter one or more search criteria for metadata fields:

  3. In the Full-Text Search area, you can enter text to search for in a content item or items, to refine your search.


    Note:

    When using Oracle Text Search with your Content Server instance, you cannot enter free-form metadata queries into the Full-Text Search field on the Expanded Form. Instead, you must use the advanced options on the Query Builder Form. For more information, see Section 17.5.3, "Searching with the Query Builder Form."


  4. In the Results Options area, you can change the Results Options for displaying the results.

  5. To save the search query under My Saved Queries, click Save.

  6. To run the search query, click Search.

The content item or items that match your search criteria are displayed on the Search Results page.

17.5.2 Filtering Search Results

The Search Results page displays a menu bar with metadata categories you can use to filter the search results. Each category lists values that are valid for the particular search results. The system administrator can add or remove categories. The default set of categories include Content Type, Security Group, and Account.

Figure 17-2 Search Results with Oracle Text Search Default Menu

Graphic is described in surrounding text

An arrow next to the category name indicates that the search results include multiple values for that category. When you move your cursor over the option name, a menu displays the list of the values found in the search results for that category and the number of content items for each value. Click a value to filter the Search Results page to list only the items that have the selected value in the selected category.

Figure 17-3 shows a list of categories under Security Group and the number of items found in each category.

Figure 17-3 Search Results with Expanded Oracle Text Search Menu

Graphic is described in surrounding text

17.5.3 Searching with the Query Builder Form

On the Query Builder form, you can select search criteria from menus as required. You can build and save complex queries by selecting options from a series of lists. You can also manually edit the query text.


Note:

When using Oracle Text Search with your Content Server instance, you cannot enter free-form metadata queries into the Full-Text Search field on the Expanded Form. Instead, you must use the advanced options on the Query Builder Form. For more information, see Section 17.5.3, "Searching with the Query Builder Form."


Figure 17-4 shows the Query Builder Form for specifying Oracle Text Search queries.

Figure 17-4 Query Builder Form for Oracle Text Search

Graphic is described in surrounding text

To specify a search on the Query Builder Form:

  1. On the Content Server home page, display the Home Page Search Fields from the Search menu or the Search Tray.

  2. On the Search Forms menu, choose Query Builder Form.

  3. To edit the query, click show advanced query builder options, and then choose Modify Query Text.

    For example, if you select the date field, the On or After operator, and specify a date, the resulting query text is similar to the following:

    dInDate >= `9/22/11 12:00 AM`
    

    To create a search that shows check-ins within the last specified period of days, subtract the number of days (7 in the example below) from the current date returned by the dateCurrent function:

    dInDate > `<$dateCurrent(-7)$>`
    
  4. In the Results Options area, you can change the Results Options for displaying the results.

  5. To save the search query under My Saved Queries, click Save.

  6. To run the search query, click Search.

17.5.4 Metadata Search Operators for Oracle Text Search

On the Advanced Search Page, you can use search operators to refine the search criteria. These operators are listed as options in lists to the left of each field.

The following table describes the search terms used and provides examples for use.

OperatorDescriptionExample

CONTAINS

Finds content items with the specified whole word or phrase in the metadata field.

This operator is available only for Oracle Text Search, or for Oracle Database and Microsoft SQL Server database with the optional DBSearchContainsOpSupport component enabled. For more information, see your system administrator.

If you enter form in the Title field, the search returns items with the whole word form in their title, but does not return items with the word performance, reform, or format.

MATCHES

Finds items with the exact specified value in the metadata field.

When you enter address change form in the Title field, the search returns items with the exact title of address change form.

A query that uses the MATCHES operator on a nonoptimized field behaves the same as a query that uses the CONTAINS operator.

For example, if the xDepartment field is not optimized, then the query xDepartment MATCHES 'Marketing' behaves like xDepartment CONTAINS 'Marketing', returning documents that have an xDepartment value of 'Marketing Services' or 'Product Marketing'.

HAS WORD PREFIX

Finds all content items with the specified prefix at the beginning of at least one word in the metadata field.

If you enter form in the Title field, the search finds all content items whose title includes the words form and format, but does not find the words performance or reform.


17.6 Searching with Database Metadata Search

Database metadata search enables you to find a content item or items based on information about the file. The metadata search functionality is installed by default and is available even if other search engines are configured.

17.6.1 About Metadata Searching

Metadata searching is similar to finding a book in a library by searching for its author, title, or subject. When you search by metadata, you specify as much information as you know about a file or a group of files. For example, to find all files written by your supervisor for your department that were released on or after 1/1/2002, specify the following on the search page:

  • Author: supervisor's user name

  • Department: department name

  • Release Date From: 1/1/2002


    Note:

    When you search for metadata, case sensitivity varies depending on how your system administrator has configured Content Server. For your specific configuration, see your system administrator.

    When you use full-text searching, a search is case sensitive for metadata and case insensitive for full text. For Content ID, however, lowercase letters are converted to uppercase letters, so you cannot search Content ID with lowercase letters.


17.6.2 Performing a Metadata Search

To search for files using metadata as the search criteria:

  1. Display the Home Page Search Fields or the Search Tray.

  2. Enter your search criteria in the Expanded Form.

  3. Select the Results Options for displaying the results.

  4. Click Search.

The files that match your search criteria are displayed on the Search Results page.

17.7 Searching with Database Full-Text Search

Database full-text search enables you to find a content item or items based on the actual text in the file. The database full-text search is available if the system administrator configured it.

17.7.1 Performing a Full-Text Search

To perform a full-text search:

  1. Display the Quick Search Field, Home Page Search Fields, Search Tray, or Advanced Search Page.

  2. Enter your search terms in the full-text search field.

  3. Select the Results Options for displaying the results.

  4. Click Search.

The files that match your search criteria are displayed on the Search Results page or in the Results tab in the Search Tray.

17.8 Searching for Expired or Expiring Content

By default, if you have write permission to any security group, you can access the Expired Content page and perform a search for expired content. The search results include only the content for which you have at least read permission.

To search for content that has expired or is set to expire:

  1. Log in to Content Server.

  2. Click Content Manager in the left navigation bar and click Expired Content.

  3. To search for content within a particular date and time range, on the Expired Content page, specify dates and times in the Before and After fields or select a value from the associated list that is a day, a week, or a month before or after the current date and time.

    By default, if you leave the Before and After fields blank, the search effectively returns all content set to expire after the current date and time.

  4. To restrict the search results to expired content only, select Expired Content.

    If you select Expired Content and leave the Before and After fields blank, the search effectively returns all content that expired before the current date and time.

  5. The Expired Content page displays the date range applied and the expired or expiring content items that match the specified criteria.

17.9 Using Additional Search Capabilities

This section covers the following topics:

17.9.1 Metadata Wildcards

A wildcard substitutes for unknown or nonspecific characters in the search term. You can use wildcards in metadata searches, even when using the Quick Search field.

Available wildcard characters and behavior are dependent on the search engine being used and how Content Server is configured. Check with your system administrator for guidance on what wildcards are available and how they behave. Asterisks (*) and question marks (?) are often used as wildcard characters, but not always. When available as wildcard characters, asterisks and question marks typically behave as follows when entered into metadata search fields:

  • An asterisk (*) indicates zero or more alphanumeric characters. For example:

    • form* matches form and formula

    • *orm matches form and reform

    • *form* matches form, formula, reform, and performance

  • A question mark (?) indicates one alphanumeric character. For example:

    • form? matches forms and form1, but not form or formal

    • ??form matches reform but not perform


Note:

Because asterisks and question marks are often used as wildcards, it is not recommended that they be used in metadata fields such as title or Content ID when checking in a document.


17.9.2 Internet-Style Search Syntax

Search techniques common to the popular Internet search engines are supported in Content Server. For example, new product entered in the Quick Search field searches for new <AND> product, while new, product searches for new <OR> product. The following table lists how Content Server interprets common characters.

CharacterInterpreted As

Space ( )

AND

Comma (,)

OR

Minus (-)

NOT

Phrases enclosed in double-quotes ("any phrase")

Exact match of entered phrase


The following table lists examples of how Content Server interprets Internet-style syntax in a full-text search.

QueryInterpreted As

new product

new <AND> product

(new, product) images

(new <OR> product) <AND> images

new product -images

(new <AND> product) <AND> <NOT> images

"new product", "new images"

"new product" <OR> "new images"

The following table lists examples of how Content Server interprets Internet-style syntax when searching title metadata using the substring operator.

QueryInterpreted As

new product

dDocTitle <substring> 'new' <AND> dDocTitle <substring> 'product'

new, product

dDocTitle <substring> 'new' <OR> dDocTitle <substring> 'product'

new -product

dDocTitle <substring> 'new' <AND> <NOT> 'product'

"new product"

dDocTitle <substring> 'new product'


Note:

Internet-style search syntax is enabled by default, but your system administrator can disable it. Check with your system administrator if you have questions.


17.9.3 Complex Queries and Alternate Query Formats

Content Server allows for the use of parentheses for complex query construction and field:value and site:value formats when creating a query. By using these alternatives, you can more easily search the metadata field you want across multiple servers, if necessary, and refine your results. For example, to search only the title metadata for new product without having to go to the Advanced Search page, enter dDocTitle:"new product" into the Quick Search field. The search looks only in the field you specified before the colon. You must know the Content Server identifier for the metadata field you want to search.


Note:

When using Oracle Text Search with your Content Server instance, you cannot enter complex search queries into the Full-Text Search field on the Expanded Form of the Advanced Search page. Instead, you must use the advanced options on the Query Builder Form.


The following table lists some examples of complex and alternate query formats.

QueryInterpreted As

dDocTitle:New

dDocTitle <contains> `New`

dDocTitle:New product

(dDocTitle <contains> `New`) <AND> <ftx>`product`</ftx>

dDocTitle:New dDocTitle:product

dDocTitle <contains> `New` <AND> dDocTitle <contains> `product`

dDocTitle:New,dDocTitle:product

dDocTitle <contains> `New` <AND> dDocTitle <contains> `product`

dDocTitle:New dDocType:Presentations

dDocTitle <contains> `New` <AND> dDocType <contains> `Presentations`

dDocTitle:New,dDocType:"Test Plan"

dDocTitle <contains> `New` <OR> dDocType <contains> `Test Plan`

17.10 Searching Referenced Links (optional)

If your administrator installed the optional Link Manager component, it evaluates, filters, and parses the URL links of indexed documents and then extracts the links for storage in a database table, making them available for searching. After the Link Manager component populates the table with the extracted URL links, it references this table to generate link search results, lists of link references for the Content Information page, and the resource information for the Link Info page. The Link Manager component shows these items:

The search results, link references lists, and Link Info pages are useful to determine what documents are affected by content additions, changes, or revision deletions. For example, before deleting a content item, you can verify that any URL references contained in it are insignificant. Another use might be to monitor how content items are used.


Note:

Because the Link Manager component extracts the URL links during the Content Server indexing cycle, only the URL links of released documents are extracted. For content items with multiple revisions, only the most current released revision is available for searching.


This section covers the following topics:

17.10.1 About Searching Links

Use the Search Links page to search for links, using criteria stored in the repository database. Use this page to validate links, to determine where a resource is used, to determine if deleting a content item affects other documents, and so on.

The Link Search Results page displays items matching your search criteria. Invalid or broken links are listed in bold font. Each item has an Link Item Actions Menu and an Info icon which displays a Link Info page.

17.10.2 Link References on the Content Information Page

Use the References options to see whether the content item references or is referenced by other content items. References provides two options:

  • Show: By default, the links are hidden when the Content Information page opens. Click Show to display all applicable links. If this content item contains one or more references to other documents, then these links are listed in the Links contained in this content item section. If other documents reference this content item, then those references are listed in the Links to this content item section.

    Links that are invalid or broken are listed using bold font. Click the Info link in the Actions column to display the Link Info page for that particular link.

  • Hide: Click Hide to hide the link information.

To access the available link information for content items, click any Content Information icon, which displays the Content Information page and the References options. Or, you can choose either Content Information or Target Content Info from the Link Item Actions Menu, which also displays the Content Information page and the References options.


Note:

You cannot delete a content item revision if other content items reference it unless the system administrator has set the AllowForceDelete configuration variable to true. When you delete a content item revision, the message indicates if another content item references the content item and asks if you are sure you want to delete it. In this case, deleting a content item that is referenced by another content item breaks those links and makes them invalid.


17.10.3 Notification of Expiration

With Link Manager installed, the Notification of Expiration page includes additional information for each content item that is expiring soon. The e-mail notification specifies if the expiring content item is referenced by another content item:

  • Is Referenced: Yes

  • Is Referenced: No

The e-mail does not provide a list of the content items that reference the soon-to-expire document. This information is available in the References section on the Content Information page. For more information, see Section 17.10.5, "Checking Content Item Link References."

If the Content Server configuration variable (EnableExpirationNotifier) has been enabled, an e-mail notification is sent to each author when content expires. For more information about setting this configuration variable, see "EnableExpirationNotifier" in the Oracle Fusion Middleware Configuration Reference for Oracle WebCenter Content.


Note:

When a content item expires, it still exists in the Content Server. Expiration only removes the item from the index. Therefore, all links associated with an expired content item are functional if they involve a valid document.


Figure 17-5 Notification of Expiration E-mail for Author

Graphic is described in surrounding text

17.10.4 Performing a Link Search

To search for links in content items:

  1. Click the Managed Links Search link in the Content Management tray.

  2. On the Search Links page, enter the applicable values in the field(s).

  3. Click Search. The Link Manager component generates and displays the search results, as shown in the Link Search Results page.

17.10.5 Checking Content Item Link References

Use the Content Information page to display, check, and verify all the link references associated with a specific content item. You can access the Content Information page for a content item from either of two pages, as described in these topics:

17.10.5.1 Checking Link References from the Search Results Page

  1. Search for the specific content item using the Content Server Search page.

  2. Select a content item from the Search Results page, and click the corresponding Content Info icon in the Actions column.

  3. On the Content Information page, click References Show.

    References Show is displayed only if the content item contains links or has links that reference it.

    All applicable links are displayed. The Links contained in this content item section lists all the links included in this content item that reference other documents. The Links to this content item section lists all the links in other documents that reference this content item.

17.10.5.2 Checking Link References from the Link Manager's Search Links page

  1. Open the Search Links page and search for links. For more information, see Section 17.10.4, "Performing a Link Search."

  2. Select a link from the Search Results section.

  3. Click the Content Info icon in the Actions column.

  4. On the Content Information page, click References Show.

    References Show is displayed only if the content item contains links or has links that reference it.

    All applicable links are displayed. The Links contained in this content item section lists all the links included in this content item that reference other documents. The Links to this content item section lists all the links in other documents that reference this content item.


    Note:

    To display the Link Info page for any link listed in the References sections (either Links contained in this content item or Links to this content item), click the corresponding Info link in the Actions column.


17.10.6 Checking the Link Information About Specific Links

Use the Link Info page to view additional information about a specific link. You can access the Link Info page for any link from either of two pages, as described in these topics:

17.10.6.1 Checking Link Information from the Content Information Page

  1. Open the Content Information page for a specific content item and display the applicable links. For more information, see Section 17.10.5, "Checking Content Item Link References."

  2. Select a link from a list in the References sections (either Links contained in this content item or Links to this content item).

  3. Click the corresponding Content Info link in the Actions column.

17.10.6.2 Checking Link Information from the Search Links Page

  1. Open the Search Links page and search for links. For more information, see Section 17.10.4, "Performing a Link Search."

  2. Select a link from the Search Results section.

  3. Click the Actions icon in the Actions column.

  4. From the Link Item Actions Menu, choose Link Info.

17.11 Content Data Tracking and Reporting

Content Tracker and Content Tracker Reports are optional components that provide information about system usage:

17.11.1 About Content Tracker

Content Tracker monitors your system and records information about various activities. Content Tracker collects this information from various sources, then merges and writes the information to a set of tables in your Content Server database. You can customize Content Tracker to change or expand the types of information it collects. Content Tracker monitors activity based on:

  • Content item accesses:

    Content Tracker gathers information about content item usage from Web filter log files, the Content Server database, and other external applications such as portals and websites. Content item access data includes dates, times, content IDs, current metadata, user names, and profile information about users.

  • Content Server services:

    Content Tracker tracks all services that return content and services that handle search requests. And, with a simple configuration change, Content Tracker can monitor literally any Content Server service, even custom services.

17.11.2 About Content Tracker Reports

After Content Tracker extracts data and populates applicable database repository tables, the information is available for report generation. With Content Tracker Reports, you can:

  • Generate reports:

    Content Tracker Reports queries the tables created by Content Tracker and generates summary reports of various kinds of activities and the usage history of particular content items. The reports help you analyze specific groups of content or users based on metadata, file extensions, or user profiles. You can use the pre-defined reports that are provided, customize them to suit your installation, or use a compatible third-party reporting package.

  • Optimize content management practices.

    You can also use the reported data for content retention management. That is, depending on the access frequency of particular content items during specific time intervals, you may decide to archive or delete some items. Similarly, applications can use the data to provide portlets with the top content for particular types of users.

This section covers the following topics:

17.11.2.1 Content Access Reports

Each report produced using the Content Tracker Report Generator main page has the same general format and visual layout. Only users that actually request and open content items are included in the Content Tracker Report Generator's compiled results. Users that open only the Content Information page are not included in the tracked data.

The opened content item can be the Web location file (the absolute path to the content item), an HTML version (by using Dynamic Converter), or the actual native file. There is generally a one-day delay from the time that a user accesses a content item until the Content Tracker Report Generator's access history includes the information.

17.11.2.2 Content Dashboard Feature

When a generated query report contains an active link to a specific content item, click the link to display the corresponding Content Dashboard. The content dashboard image shows that one version of a particular content item was accessed three times by one user.

Graphic is described in surrounding text

17.11.2.3 Drill Down Report Feature

There are various levels of report results that are generated for each predefined report. Depending on the search criteria you enter on the Content Tracker Report Generator main page, the results are filtered accordingly. The top level reports are summary reports and provide very general information. You can use the links on the top level reports to drill down to more specific information.

PKz6WWPKC_EOEBPS/dcommon/oracle.gifJGIF87aiyDT2F'G;Q_oKTC[ 3-Bq{ttsoGc4I)GvmLZ).1)!ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPKC_EOEBPS/dcommon/oracle-logo.jpgyJFIFC    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222'7" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE!KEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEzE7V%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((?l:ϊw "{{-3j3%{+Zoi.{YUڪ1kcMմfݮ4Br%*8%I.QT-[MѭT-,`g]L)lXqjV4Ķ%ѡ')$r_Ĭ AVuoż9#`FApA+麶۵ƗZ_@QeP#8 Uh燮,/jXJ}9Q]рN:]dko-ıH^I$`I$$:[zޛ}:v%`$)' gVko-ıH^I$`I$$..3D ?+pcV4[MmK-/W(Z̲lTq(Q@'94 >SJJFCI'L~yᵷX$/$0UE$xs@U{=2K--cFI,٬|Cό<)a-8nQǰ_VBNM>rE+/uoż9#`FApA椬 eq-"mV89 Wcag]E7dt&i5j K%-p 3N=\o?:evjh$#b9#hɫirLiJ*+rcTY2K;iVQ|3@#*NFA7'u@yi}ŭim=춎if@NXr???6޽ +/R.\-3X&+2qF}\㼰L $0? ESVf&-P7h)Y3>e֍KVtku5 K,S,J[ g{EG[qo,sA*H2AG9z\][j3>˘]lNTC@(O]O+[U"ߌg2:zMմfݮ4Br%*8%I.QU9//വA.H,x$ƩxAn/u6 m$H2' 0zZԢxn⸷9$l]H #<4Ķ%ѡ')$r_Ĭ APQ@w?±k(yV?-{V=<7^Ig *r?i_n|}?3ݛss[QT-[MѭT-,`g]L)lXqj~%f"}ݭ8^ =hR ặXTeu# 8 sRPEPEPEPEPEPEPEPEPu|?K9b^PlSQs&h"PTz ƻwIKeL; WizC²訫+xG𮝭xWiz$.D$ld-J[$ՕXzHveRs|=oMkj6c˾ 8Ŏ3p8ow:/CcaSm$](5<5C|#5KСcT1$ z?, wɫ#Ai"BʒHmmګԑ4-3oޙOۼ?vwc#8q\?&'hQtԮdAaX,@MyG;~{:Rx2^3W9*~дOiO}+o7n.d82hIZ7u+RjpO4m;6ÖPQdWk~ᶩ:C(L 8KYpz |*7<hLW"% |Jf 9Y5M/JDR Hm Dϝ _$](-;W4sJ7Wn~X .^ow:< $_ K@oGU-K 4۫AۗGjy w7aͣlӔekh% ` 5h6-as/6Cp`y2t@ Xk>g7RFV$r aӸJ> jIĞտ4_.XYH|x|۸>1}ޟ?x"7VQ,7I4vT10NMzEx$O*Z >ܽ~M_HٻnɫxjZt.gX ݴ;d<9;IaXT|E7kyC><ͻ~n>lq^_G_=>dWD~nPr+ߩxR2TO [nIrǟLbxKLx4%@cUv5ot ]]ﳋI.SFy`;@?NѷCCĿ9Cu%&9 7s(Ɍ:Mn| ;£FQ: *O4/x&}K+KYoyÌ|셶u8=fWj^?vp$*:I=7 1zx$P**->2XKpvZvFڪ !˳ τg1>ᇓO#4HH,I}8;A+__7ᾷ|? vzRDnHUa~Si>6IDŽ%ޕyuylLaXdp< $_ K]syZ襮 ( ( ( ( ( ( ( (1 hv~}֗/fkS)=+b(_?#yhOt:̌;Aln;b( } toeI$Ww–6N3uzw]ɍ<V(n%;yfE(ڻK =2;; H--c`FIŽI'P?-xGNC%<ד.@=~UcYaA{j;&L$OUl#<Т8gt E/LymC(+r=k [q 29P~itˋ{>Xē'U hv~}֗/fkS)=+b(߅oXhvdS3'e'ʶ(1 hv~}֗/fkS)=*Ʒi#ukXϷ̋{&rZP{ }3N˵!7'ZC>*ƉC|̄P+8YFlVQ1TEwq)io|  K2II%F',y>Q@K3kYF|%$nsln88<[oqsA*92<G(u . #" d"0QӰZ4mKEVfcqɭ (G𶍠:g]j׏y9.1֋ h~(,{{H0\y6! ۨ( [F%gKY%32y&\ ˒z(be4OZlӼ.L Y!Vy}O ࿅ wwzèWե՘@RJZ>kiV7N|ۤ3p8OAFh'Xy>noqg=}MI5n4VX(PNr(((((((((|xGq\[.9(gʌ='?ut΁4,k l1qW^x>s'5 W4J[̑$8*sNH}ClCj%2A+$ AbSӮl/#-nxfMnF0dҼyk$3ɾ;MBX`@؅RB8;}}1@E|={m}XfШTNl'V95v_>|9-b{ہ/nY] cY UC'_ U~ I&ǓTFi󒬥ݞ $w&*>%ּXlHD7q$"`sn -z~=?Z:{Y=J \oh۰Wx?g])mfR$ n08P 7|mCۿG]?xkV)kg6"K"LhsNIz5xNLYILIڋ8zPQEx>}wn|I]V};ÒJEg lo]?(`čK705g5終XVI]ϴu*۸o,vND|On$p#r7f=mg'kuM #r0N# b[FwsIcVԵ_ݎwen׷a3)0IHD0q)R6|mDKgoped%V̟ J4Y  ' 0F=?(ֆ’G336 r2n*F4{9s˽1$3!Q'FxQ6sfY^&%k99,ϖyd=wNM2Iw֊Gb! NpHRƀ>?Y>uVv/r Ȯ'<=ˏ 4(N~W 0_x,Ç\ND8@ŶPƉmk̓&4Ef3>X|(f=]<ӝq#F=>TQǧk(xX|k,m-IUnPB;J +]W4<[Xii;QA,p98Ҽ/mω/_[5;9<[fhFAh( |i-'S񆿪`RW XOjǃ>ashYE,e$S<ߍu/ ]A^{.)HzWy_>|dV7 4aIz:L*|&|ͪiwznR#(RQNrwW|iKB=F=畃)T:ӵIPkVi2+HMݔ)X[1oEOPsxZo4htR{`n]Ueܬ1=*煼7gZhvO%;sǵyu)M[BFhb2O;n\ul~DP`0scSy'7x7*w[[)'E;;aBF3r+'/Nkj+Enld\׃fyHvvrY8g'ߊ5-{V{ٵ) @#Md*b020q@OGCWUyy\DD$y/ < gͮ,'r3@ЍIAV4k=„|9(uWA6[0D#5 `(x< yy0Y\XJkv򨀣&]Nlxmm常8` $Q@$?|x56;āK20pA#88??j; sKޓx~ -r @sm89 >ŶfWu[A+qBIՐ©: g? x?@}h:lvi;gg `ep2}Ma?my';CUUp߇~ӞWej湄n Gl' >+/v T%AF#=ǟ5ަT*sP(`x`>w.;'fq uQڀ+I熿k?t>T zãh:]HY[oHAbA8gV=i0{X[xW_( ۜ~ xm|uX-MI$`%$xs^X~+=z2I26BYCpH x PkWmzڦwMV!mq|O ,u^g<3n>s=;AEPEPEPEq%~!>_;y~?wch8]QEV?n5O](/uux' #6Ie軏Q?YK]wPE66JyL$ېǩ(?W9 >dwwwdghG2|m WV/çA jɄ X{QEQEWMgo k0Y[pueBylĖ<ԗ׿g&i^!`m kycB0ݒ@QX /k;>[L3 dq[QEQ^W VԵ\jȋ%+88'R ( ( ( ( ( (e_ɥhF}$.Ag/{-8umZd7mp]QEQEQEQEQEQEQEQEQEQEx!'_oQ7᷒nLGݐP[F=\x[>69 LH.A DI۸ 8>j:o1&N? ypE\7G?ZWʅ$ Zȭ ]i`T|Ult=.ScM2IrId?^'>?x;-N]@W&Ub# |d؜g  Gwٍ|?l|*o]bCKL_1Wfc 7&:פW GGhpC81*9V$ g`hP.VO|C]`&޹i ^Au ;Al)*Ux7>CaQn+$](# 0G&zdlia ÎÏku;zk7&ȱ+%Qk޿TJ> !пJ$ 7+CK[_jҋm>$?ṬQĝn#k鶓kd\ g q Ox#kVs+R#v* Uuoſfh%@ԌhxJ׀guVqe}2"U2&K?sŖ-/zz[@d2c >H8  VLJ>h4VRp]|ǏiCiXS(< eLOR7T^ě{95{_ZbXː̊Kۜ <:O%ᦻV65Q.ϖT Ýo01^^?8?iYxo^F/j0eAk#&I`67cvG,>$;﵍hIޤAݷ`@%IgӴmsreBd8`$=Fv>;6_ /..cKXOޔrzrR<<^IJM.Z/k1-@WڼsM𾥩|^1Mz0nXٞ@r(ʣm$3p6tÿW~"jZݪu'ݰPIG@X+;v4_?|sc։f+ B`|?uČ2+-s\t<]wWi*!eI* 0k^o|_f]^NEs2P N66.ZX?6[*H`@xp$ Vuo?^B=ux.WԂcx>_s +u׃|[wSd[]l*ݎ8,GQRKw=Y~f(A[7?qx { [BBnB,w3uU £ĺ^ 7LBV;2HJ|Z~|Xb6KWUpd` y_(`ENĽv.OĶz +*E5tIu9_Ht/x҉++ !пJ$@(((((((((( zw]ɍ<^W?%/|>iFuaFC\mo]~HÓ % \dǢxZGc0$9 4rme1 1=A(Jk \U {m.vcq^O i цC$p$i$.IT(?S>'տ~w+|6;c8=C>/Wlw#9ێ렢2;¶: Ǘyvry*C9 tzZS>!k:V[(bwm)"N:`sײQ@]*\4N;;,OчG F'nP:_x[TMJuxUq 򪪠A@ٴo ]FYCo#FIRȁI#VPx5ohm?#^Cv}n{ (?>;\sjr4k'}6Ч$c`8Ty _׆K]Be7A¸?}d索<za>&O'Gt2)R199^tՐZZTs1$1><`sԢ8'Gu\G.nog9Qឋxk@^8WcpzPo^:^#$E*F28<##k4O izfMhbKqf$c8(UΝ^jZˆ4—YT22NIm"Y5u۹5 +վk r~sp+(O4_ū=Ofk Vܧp OLsozXgur$P敀EW I'h((((((((((5?hw쵴| cH<r umwķ;eim-V ?.k+CaQn(+K h?GyͶxI&<ą{g+*E5WwKxM/;7z@ +$;Q^KIoQ%z)bމO$㕂d(b pEp kx·Z3z궨ʥB#df9˞W?O5 `?^oɩqn&ۑU2/,8=yEyxڏxI F5QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE !пJ$@<Ú<N \[7ŏ-'O&]g\}{IbyO.FBF #@W?+Xt(l umǩP?$P**  5:K 0dː9x lcFT9na^P{z W@'<=qg_RT2O29 qӟz]+E VH ]͖TuxCaQn++GT y9@@ۦ:װxZ]%W]h>]^t??mOPSt0?(A{+|r}o :z (((((((((((((((((((((((((((*WZ}oHaTi$c''((((((((5[z} ;XV%-2B3}\(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PK yyPKC_EOEBPS/dcommon/cpyr.htmD Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Oracle Logo

PK0hPKC_EOEBPS/dcommon/blafdoc.cssc@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.8.12 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; text-align: left; } h2 { font-size: 152%; font-weight: bold; text-align: left; } h3 { font-size: 139%; font-weight: bold; text-align: left; } h4 { font-size: 126%; font-weight: bold; text-align: left; } h5 { font-size: 113%; font-weight: bold; display: inline; text-align: left; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; text-align: left; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } li { text-align: left; } dd { text-align: left; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #f00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #f00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKr.hcPKC_EOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PKC_EOEBPS/workflows_concept.htmL Understanding Document Workflows

7 Understanding Document Workflows

This chapter describes workflow concepts in Oracle WebCenter Content. It has the following topics:

7.1 About Workflows

A workflow specifies how to route content for review and approval before it is released to the system. The workflow notifies users by e-mail when they have a file to review, and when using the Oracle WebCenter Content user interface, a notification flag is displayed next to the user name in the banner.

7.2 Workflow Types

From a workflow participant's point of view, there are two types of workflows:

  • A basic workflow defines the review process for specific content items, and must be initiated manually.

  • In a criteria workflow, a file enters the workflow automatically upon check-in when its metadata matches predefined criteria.

7.3 Workflow Steps

Each workflow can include multiple review and notification steps, and multiple reviewers to approve or reject the file at each step. For each step in a workflow, a set of users and a step type must be defined. The users defined for a step can perform only the tasks allowed for that step type.

Step TypeDescription

Contribution

This step is the initial step of a basic workflow. The workflow defines who the contributors are.

Auto-Contribution

This step is the initial step of a criteria workflow. There are no predefined users involved in this step.

Review

Users can only approve or reject the file. Editing is not allowed.

Review/Edit Revision

Users can edit the file if necessary and then approve or reject it, maintaining the existing revision number.

Review/New Revision

Users can edit the file if necessary and then approve or reject it, creating a new revision.


7.4 Workflow Process

The workflow process is as follows:

  • When the required number of approvers for a particular step approves a revision, the revision goes to the next step in the workflow.

  • If any reviewer rejects a revision, it goes back to the most recent review step that allows editing.

  • When reviewers approve a revision in the last step in the workflow, the content item is released to the system.

  • A basic workflow containing multiple content items can release some items in the workflow to the system before all of the revisions have completed the workflow.

7.5 Postprocess Workflow Options

Workflows or individual workflow steps can allow for items in review to be released into the system for indexing, searching, and viewing, even though the workflow to which they belong is not completed. For example, items in a workflow process can be made available to others not in the workflow, or a workflow can update the content information of an item without advancing the revision of that item.

7.6 Authentication

Workflows provide authentication options for individual steps and for the content item itself.

When you approve a revision, you also have the option of providing an electronic signature for the content item itself (not the step). The electronic signature uniquely identifies the contents of the file at a particular revision and associates the revision with a particular reviewer.

An electronic signature is a unique identifier computed from the content of the item and associated with other metadata such as the user name of the reviewer. Multiple reviewers can "sign" a particular content item revision. Modifications to the content item itself result in a different identifier. By comparing electronic signatures, Content Server can determine whether a content item has changed and whether existing approvals are valid.

For more information about electronic signatures, see Section 18.4, "Signing Content Electronically."

PK3ofPKC_E OEBPS/toc.ncxB Oracle® Fusion Middleware Using Oracle WebCenter Content, 11g Release 1 (11.1.1) Cover Title and Copyright Information Contents Preface What's New and Changed in This Guide Part I Getting Started with Oracle WebCenter Content 1 Introduction to Oracle WebCenter Content 2 Accessing and Navigating Oracle WebCenter Content 3 Understanding Content Management 4 Understanding Documents and Document Properties 5 Understanding Libraries 6 Understanding Folders 7 Understanding Document Workflows Part II Using the WebCenter Content User Interface with Oracle WebCenter Content 8 Getting Started with the WebCenter Content User interface 9 Finding Libraries, Folders, and Documents 10 Viewing Documents 11 Uploading and Checking In Documents 12 Checking Out and Downloading Documents 13 Working with Libraries 14 Working with Content Folders 15 Using Workflows Part III Using the Native 11g User Interface with Oracle WebCenter Content 16 Getting Started with the Native 11g User Interface 17 Finding Documents 18 Viewing Documents 19 Uploading Documents 20 Checking Out and Downloading Files 21 Working with Content Folders 22 Grouping Documents Using Folios 23 Using Workflows 24 Working with Images and Videos 25 Working with Records Part IV Using Other Ways to Work with WebCenter Content 26 Accessing Managed Content Directly from Within Your Desktop Applications 27 Working with WebCenter Content from Mobile Devices Copyright PK4PKC_EOEBPS/content.opf1Mβ Oracle® Fusion Middleware Using Oracle WebCenter Content, 11g Release 1 (11.1.1) en-US E26695-03 Oracle Corporation Oracle Corporation Oracle® Fusion Middleware Using Oracle WebCenter Content, 11g Release 1 (11.1.1) 2014-01-22T13:34:14Z This user's guide describes how to use Oracle WebCenter Content Server, including how to manage and revise content, how to use security and content metadata, how to search for and view content, how to organize content into folders and libraries, how to use workflows, and how to use images and videos. PKM6M1MPKC_EOEBPS/content_use.htm Viewing Documents

18 Viewing Documents

This chapter describes how to work with content item revisions and metadata including how to sign content items electronically, how to participate in a discussion about a content item, and how to subscribe to content item revisions.

18.1 Viewing a Content Item

After you find a content item, you can view it in several ways, depending on the available renditions of the content item, the conversion setup for your system, and the configuration of your Web browser. Depending on your access permissions, you may also be able to open or get a copy of the native file.

This section covers the following topics:

18.1.1 Viewing a Web-Viewable File

To view the Web-viewable rendition of a content item, you must have the appropriate helper application or Web browser plug-in installed. For example, to view the PDF version of a content item, you must have the Adobe Acrobat plug-in.

You can view a Web-viewable file as follows:

  • From a Content Information page, click the Web Location link.

  • From a Search Results page, click the Content ID link in the ID column (Headline view) or Description column (Classic View), or the thumbnail (Classic and Thumbnail views).

If a Web-viewable file does not exist, or you do not have the correct helper application or plug-in installed, you are prompted to either save the file or open it in its native application. For more information, see Section 18.1.2, "Viewing a Native File."

18.1.2 Viewing a Native File

When you view the native file of a content item, you are prompted to either save a copy of the file or open it in its native application. If you choose to open the file, you are actually opening a copy of the native file that is stored in a temporary location on your hard drive. You are not opening the native file that is stored in Content Server repository.

You can access a native file as follows:

  • From a Content Information page, click the Native File link.

  • From a Check-Out Confirmation page, click the Download native file button.

  • From a workflow review notification message, click the Review workflow item link to open the Workflow Review page, and then click the Native File link under Renditions.

18.2 Discussing Content

Content Server comes with the ThreadedDiscussions component. If enabled, it allows contributors to post questions and comments about the content item throughout multiple revisions. This component must be installed and enabled by your system administer for this functionality to be available.

This section covers the following topics:

18.2.1 About Discussion Posts and Threads

Threaded discussions provide question and answer feedback about a content item and help record how and why changes were made to a content item. Because threaded discussion posts follow content through multiple revisions and refer to the revision for which the comment was made, threaded discussions help contributors keep track of enhancement requests or other recommendations for future changes to the content. Each discussion post conveniently lists the revision number of the content to which it refers, so you do not have to view the content information of previous revisions to post to a discussion item.

Discussions are managed content items. When you begin a discussion thread about a content item, an .hscp form for the discussion is created, given the same ID as the content with _d appended to the end, associated with the content item, and automatically checked in to Content Server.


Note:

If you have a content item that has a document name that is within one character of the database storage maximum, which is 30 by default, you cannot create a threaded discussion for it.


Unlike other content items, edits to a discussion do not create new revisions of the discussion content itself. Instead, the .hscp form that contains the discussion is modified. The Revision History for discussion content is always Revision 1. The revision number does not increment for discussion content. The number of the post represents the chronological order in which the comments were posted.

In Figure 18-1, each top-level post represents a thread. Posting number one (#1) and posting number two (#2) are threads. The reply (#3) to thread number two represents a post within a thread.

Figure 18-1 Threads and Posts

Graphic is described in surrounding text

Figure 18-2 shows posts #1, #2, #3 and #4. The reply to "Change to Introduction (#1)," "RE: Change to Introduction (#3)" was made after "Change to Conclusion (#2)."

Figure 18-2 Posting Order

Graphic is described in surrounding text

18.2.2 Initiating a Discussion from the Content Information Page

To initiate a discussion from the content information page of a content item:

  1. Browse or search to locate the content item and open the Content Information page for the item.

    If you are checking in a new content item, you can access the Content Information page by clicking the Content Info link on the Check-In Confirmation page. For more information about checking in content items, see Section 19.4.1, "Checking In a New File."

  2. In the Links area, click the Create Discussion link.

  3. On the Post Comment form, enter a subject for the posting in the Subject box.

  4. Enter your discussion question or comment in the comment text box.

  5. Click New Post. The Post Comment form (Brief Content Info page) displays the new post.

18.2.3 Initiating a Discussion from the Search Results Page

You must be using a search results view that provides access to the Content Actions menu, such as the Headline or Thumbnail views. If you are using the thumbnail view, then you can click the discussion icon to access the discussion.

To initiate or enter a discussion in progress from the Search Results page:

  1. From the main menu, choose Search.

  2. On the Advanced Search page, enter any search metadata fields to narrow your search, and click Search. For example, to exclude content items that are discussions, select Discussion Type=Not applicable. Your search results are displayed.

  3. In the Content Actions menu for the content you want to discuss, click Create Discussion.

  4. On the Post Comment form, enter a subject for the posting in the Subject box.

  5. Enter your discussion in the comment text box.

  6. Click New Post. The Post Comment form (Brief Content Info page) displays the new post.

18.2.4 Initiating a Discussion from the Workflow Review Page

To initiate a discussion about a workflow document:

  1. Open your My Content Server tray and click the My Workflow Assignments link.

  2. In the Actions column on the Workflow in Queue page, click the Workflow Review icon.

  3. In the Links list on The Workflow Review page, click the Create Discussion link.

  4. In the Subject box on the Post Comment form, enter a subject for the posting.

  5. Enter your discussion in the comment text box.

  6. Click New Post. The Post Comment form (Brief Content Info page) displays the new post.

18.2.5 Viewing and Replying to a Threaded Discussion

Users with read permissions can view the messages within a threaded discussion, but only those who can edit the content can post messages. You can access an existing discussion from the following links:

  • On the Content Information page, click the ID of the content item to discuss link.

  • On the Workflow Review page or Search Results page, click the Discuss This Item link.

  • On the Discussion Info page, click the Web Location link.

  • On the Search Results page of a discussion, click the Content ID link.

The Discussion link indicates how many discussion posts have been created for the document. The Discussion Count custom information field generates the number of items.

To view and reply to a discussion thread:

  1. On the navigation bar, click Search.

  2. On the Advanced Search page, specify the search criteria for the content you want to discuss. In the Discussion Type field, select N/A.

  3. Click Search.

  4. On the Search Results page, click the Content Info link or icon for the item you want to discuss.

  5. To view the discussion, in the Links area on the Content Information page, click the Go to Discussion link.

  6. To reply to a post, beneath the post to which you want to reply, click Reply To This.

  7. Enter your reply in the comments text box, and click Post Reply. Your post is added to the discussion.

18.2.6 Printing a Threaded Discussion

To print a threaded discussion.

  1. On the navigation bar, click Search.

  2. On the Advanced Search page, specify the search criteria for the discussion thread. In the Discussion Type field, select Single Content, and click Search.

  3. In the ID column of the Search Results page, click the ID of the discussion thread. The ID should have an underscore d (_d) suffix.

  4. In the discussion thread, click the Print View option.

  5. On the print view page, click the Printer icon or use any of the print options supported by your browser.

18.2.7 Deleting a Threaded Discussion

To delete a threaded discussion. You must have delete permission for the content to delete the discussion.

To delete a discussion:

  1. In the Search Results page, click the Content Item info link for the discussion you want to delete.

  2. On the Discussion Info page, click OK. A message indicates the revision has been successfully deleted from Content Server.

18.2.8 Searching with the Discussion Type Field

You can use the Discussion Type metadata field to narrow your search criteria when searching documents. The Discussion Type search field enables you to refine a search for content associated with discussions. The discussion type options are:

  • N/A: A search applies to all documents including those without associated discussions. A search returns content both with and without a discussion, but does not return any content that is a discussion itself. That is, content IDs with an underscore "_d" are excluded from the search.

  • Single Content: A search applies to documents that have a discussion focused on a single content item. A search using this option returns the discussion content itself (it returns only content that is a discussion). Only content IDs with an underscore "_d" are included in the search results.


    Note:

    If you do not select any criteria for Discussion Type, all content with or without discussions are displayed, including the discussion content itself.


18.3 Subscribing to New Revisions of a Content Item

This section covers the following topics:

18.3.1 About Subscriptions

Subscriptions notify you automatically whenever a content item is revised. There are two types of subscriptions:

  • Content item subscription: Users manually subscribe to individual content items.

  • Criteria subscription: The system administrator sets up a subscription based on one or more metadata fields. When a user subscribes to the Criteria subscription, they are automatically subscribed to all content items that match a particular value of those metadata fields.

    For example, the system administrator sets up a criteria subscription with Author values as the criteria. Whenever you view a Content Information page, you can choose to subscribe to all content items checked in by the author of the current content item.

The system administrator can subscribe users to specific content items or to criteria subscriptions, but users have the ability to cancel these subscriptions.

18.3.2 Subscribing to a Content Item

To subscribe to a content item:

  1. Display the Content Information page for the content item.

  2. From the Content Actions menu, choose Subscribe.

  3. If the item is part of a criteria group, on the Subscribe to "content_item" page, click Subscribe under the Subscribe To This Item section.

  4. If no e-mail address has been specified in your User Profile page, you are prompted to enter an e-mail address for this subscription. Enter an e-mail address, and click OK.

18.3.3 Viewing Your Current Subscriptions

To view your current subscriptions, Open the My Content Server tray, and click My Subscriptions.

18.3.4 Unsubscribing from a Content Item

To unsubscribe from a content item:

  1. Open the My Content Server tray, and click My Subscriptions.

  2. From the Actions menu on the Subscriptions page, choose Unsubscribe.

18.3.5 Unsubscribing from a Criteria Group

To unsubscribe from a criteria group:

  1. Open the My Content Server tray, and click My Subscriptions.

  2. From the Actions menu on the Subscriptions page, choose Unsubscribe.

18.4 Signing Content Electronically

If the Electronic Signatures component is enabled, you can optionally sign a content item with an electronic signature that uniquely identifies the contents of the file at a particular revision and associates the revision with a particular user.

This section covers the following topics:

18.4.1 About Electronic Signatures

An electronic signature is a unique identifier computed from the binary content of a content item and associated with other metadata such as the name of the user who signs the content item. Unlike a digital signature, which uniquely identifies both the document and the signer and encrypts the information with the document, an electronic signature is not stored with the document.

When you check in a content item, Content Server generates the identifier and stores it with the revision metadata for the content item. When you "sign" a content item, a copy of the identifier is stored with the electronic signature metadata. When you check in a modified revision of the content item, a new identifier is calculated.

Content Server can compare the identifier stored with the content item to the identifier stored with the electronic signature to help you determine if a signed content item has changed and if existing signatures for a content item are valid.


Note:

The identifier is computed from the content only, not the associated metadata. A change in the metadata for a content item does not invalidate the electronic signature for the content item.


Because electronic signatures are stored separately from both the content item and from its metadata, multiple users can sign a particular content item revision. For example, in a workflow approval process, multiple reviewers may sign a revision of a content item.

Any user with access to the Document Information page for a content item can sign the content item. You can also provide an electronic signature as part of a workflow approval step. For more information, see Section 23.3, "Reviewing Revisions in a Workflow."

You can access signature information for a signed content item from the Content Information - Signatures tab. For more information about signing a content item, see Section 18.4.5, "Signing a Content Item Electronically."

18.4.2 Signable Objects

The following table describes the restrictions on objects that you can sign electronically:

ObjectDescription

Content Items

You can sign any content item, such as a document, an image, a zip file, and so on. You can sign the native file, but not other renditions, such as web-viewable versions of the native file.

Folios

You can sign a folio, provided it has been frozen.

Metadata-only

You cannot sign items that do not have an associated content item, such as metadata profiles or Content Server folders.

Because metadata itself is not used to calculate the signature ID, a change to the metadata for a content item does not constitute a change to the electronic signature for the content item.


18.4.3 Signature Metadata

When you sign a content item electronically, the signature is automatically associated with your user name and certain information about the content item such as the content name and revision ID. You must provide your user name and password to sign a content item revision, and you typically provide additional information such as the reason for signing the document.

Your system administrator may also define additional metadata fields that are stored as part of the metadata for the electronic signature.


Note:

Because signature metadata is stored separately from content item metadata, you cannot search for electronic signature metadata with the standard search options provided.


A system administrator can use signature metadata in a watermark to indicate that a PDF document has been electronically signed. For more information, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

18.4.4 Signature Verification

When a content item itself is modified, it produces a different computed identifier. By comparing the identifier of a content item with the stored signature, Content Server can determine whether the signature for a particular revision is still valid.

Because identical files produce the same calculated identifier, you can compare a file in a local file system to a particular content item revision to determine if the files are identical. For more information, see Section 18.4.7, "Search for a File in Revisions."

You can also verify a file from a local file system against all signed or unsigned content to which you have access. For more information, see Section 18.4.8, "Search for a File in the Repository."

18.4.5 Signing a Content Item Electronically

To electronically sign a content item:

  1. Display the Content Information page for the revision you want to sign.

  2. From the Content Actions menu, choose Sign Content.

  3. On the login page, specify your user name and password to provide signature authentication.

  4. On the Sign Content Item page, your user name is preselected. Specify additional metadata fields as necessary.


    Note:

    The Reset button returns the fields to their original values.


  5. Click Sign.

  6. To view signature information for the current revision, on the Electronic Signature Confirmation page, click the View Signature Information link.

    The Content Information - Signatures tab opens. This page is also accessible as a tab on the Content Information page.

18.4.6 Viewing Electronic Signature Information

To view signature information for an electronically signed content item:

  1. Display the Content Information page for the content item.

  2. In the Revision column, click the revision for which you want to view signature information.

    If the selected revision of the content itemN has one or more electronic signatures, a Signatures tab is included at the top of the page.

  3. Click the Signatures tab.

  4. To view complete signature metadata for a signature, on the Content Information - Signatures tab, click the Signature Details icon in the left-most column for the associated signature.

    The Content Information - Signatures tab provides information about the all signatures for the selected content item revision, including any associated workflows the validation status of each signature.

  5. To view signature information for all revisions of the current content item, choose All Revisions from the Change View menu.

    The Signatures tab updates to show signature information for all revisions of the current content item.


    Note:

    The column with validation status is replaced by the revision number in this view with the currently selected revision in bold and surrounded by brackets. Validation of signatures is provided for a single revision only.


  6. To view complete signature metadata for a signature, click the Signature Details icon in the left-most column for the associated signature.

18.4.7 Search for a File in Revisions

To compare a file in a local file system to the signed revisions of a content item:


Note:

The external file is compared to signed revisions only.


  1. Display the Content Information - Signatures tab for the signed content item you want to compare with the external file.

  2. Click Search For Local File In Repository in the menu area.

  3. To select an external file, on the Search for Local File page, click Browse.

  4. In the File Upload window, navigate to the location of the external file, select the file, and click Open.

    The file path for the selected file is shown in the File Path field. Click Reset to clear the field.

  5. Click Validate.

  6. If the external file matches a signed revision, in the signature validation window, you can click the View Content Info link to display the Content Information page with the matching revision selected.

    If the external file matches a signed revision other than the most current revision, you can click the newer signed revision link to display the Content Information page with the newer revision selected.

18.4.8 Search for a File in the Repository

To compare a file in a local file system to all signed or unsigned content in the system to which you have access:


Note:

The external file is compared only to revisions to which you have access.


  1. In the Content Management tray, click Search For Local File In Repository.

  2. To select an external file, on the Search for Local File page, click Browse.

  3. In the File Upload window, navigate to the location of the external file, select the file, and click Open.

    The file path for the selected file is shown in the File Path field. Click Reset to clear the field.

  4. Click Validate.

  5. If the external file matches a signed revision, in the signature validation window, you can click the View Content Info link to display the Content Information page with the matching revision selected.

    If the external file matches more than one signed revision, the results are displayed in a table format. You can click the Information icon to the left of the matching item to display the Content Information page for that item.

    If there are multiple matches, the window remains open until you click Close Window.

PKkdXNPKC_EOEBPS/get_started_oldui.htmp< Getting Started with the Native 11g User Interface

16 Getting Started with the Native 11g User Interface

The native 11g user interface offers a full-featured user interface capable of. It offers a simple way to store, secure, retrieve, and share any type of document.

This chapter covers the following topics:

16.1 Working with Oracle WebCenter Content

You work with Oracle WebCenter Content to upload documents to the repository and search for and view documents that others have uploaded. Several pages are used in Oracle WebCenter Content:

Home Page

The Home page is displayed when you first log in to Oracle WebCenter Content. The content of the home page can be configured by a system administrator to display content pertinent to your company and often includes a simplified search form for finding documents. Detailed information about the Search page is in Section 16.3.1.

Search Page

The search page is one of several options for finding documents available in the native 11g interface. The search page uses criteria you specify in a search form to find documents. The search form may vary depending on Oracle Content Server is configured, but offers the most flexible way of searching for content. Detailed information about the search page is in Section 17.1.4.

Check-In Page

The check-in page is used to check files in to Content Server. The standard check-in page displays all available metadata fields in Content Server. If profiles are set by your system administrator, different profiles can be selected when checking in content to limit the displayed metadata fields to only those needed by the type of content being checked in. Required fields on the check-in page are indicated by an asterisk (*).

Content Information Page

The Content Information page is displayed when you open a document from a search results list. The page allows you to view the contents of a document, the metadata properties of the document, and provides ways to update the document to a new revision, update the document metadata properties, or download the document.

Depending on how Oracle WebCenter Content is configured, you also have additional options when using the native 11g user interface. They include:

  • grouping content into folios

  • managing and converting digital assets

  • integrating with desktop applications

  • managing records, either electronic or physical

16.2 Accessing WebCenter Content Server

To access Content Server, enter its Web address (Uniform Resource Locator or URL) in a supported browser and log in. The URL specifies the host name and port number for Oracle WebCenter Content Server.

The host name is the name of the computer that is running the Oracle WebCenter Content Managed Server. The default port number for Content Server is 16200.

To access WebCenter Content Server:

  1. Browse to your Content Server instance with a Web URL in this format:

    http://host_name:port_number/cs/
    

    For example:

    http://example.com:16200/cs/
    
  2. On the Content Server home page, click Login.

  3. Enter your user name and password, and click Sign In.

16.3 Understanding the Native 11g User Interface

The native 11g user interface is a feature-rich interface offering a familiar user experience for those who need to manage rich media beyond traditional office documents, including images, records, and videos. The following sections describe the main interface features:

16.3.1 Home Page

The home page opens when you first log in. The home page typically includes the tray navigation, the top toolbar, and other page content and functions as determined by your system administrator. To return to the home page at any time, click the Oracle WebCenter Content in the upper left.

Graphic of native 11g home page

If you set up a default saved query, the results are displayed on this page (you may have to scroll down to view them).

16.3.2 Toolbar

The toolbar at the top of Content Server Web pages contains navigation links, online help, and the Quick Search feature.

Graphic of native 11g toolbar

Note:

The Search and New Check-In links may list multiple options if your system administrator creates and enables Content Profiles to provide alternative metadata forms.


LinkDescription

WebCenter Content

Displays the Home Page.

Search

Displays the Advanced Search Page, which you can use to perform metadata and full-text searches to find specific files.

New Check-In

Displays the Content Check-In Form, which you can use to check new files in to Content Server.

User profile link

Displays the User Profile Page and provides information for editing your user profile. The link is either a user name or the user's full name.

Logout

Logs out of Content Server.

Help

Displays the online help system.

Refresh Page

Updates the current page.

Quick Search

Searches for the specified term in the supported metadata fields and in the content item text if supported by your system. For more information, see Section 17.1.1, "Quick Search Field"


16.3.3 Trays

The trays on the left side of Content Server Web pages provide quick access to most of the functional areas in Content Server. You can add functions you use often, such as predefined searches and links to your favorite web sites.


Note:

Trays are part of the frame-based Trays layout option, and are the default navigation tool for Content Server. If you select Top Menus on the User Profile Page, then you can access Content Server functionality from a series of menus located above the main content area.


LinkDescription

Microsoft Login

If you are logged in to your Microsoft network, click this link to log in to Content Server.

This link is present only if your organization is using Microsoft Network security to log in to Content Server. Many browsers, such as Mozilla Firefox, support logging in with this security.

Your Content Server instance may be integrated with your enterprise login system. For more information, ask your system administrator.

My Content Server

Displays the My Content Server Tray with options to view URLs and queries you have saved, content you have checked out, open workflow assignments, available metadata profiles, personal folders, and so on.

Browse Content

Expands to display a hierarchy of folders. You can expand and collapse the levels of folders in the tray and click a folder to show the content of the folder in the work area.

Search

Displays the Search Tray. From this page, you can perform metadata and full-text searches to find specific files.

Content Management

Displays the Content Management Tray with options to view content items that are checked out or expired, or that are active in workflow.


16.3.4 My Content Server Tray

Use this tray to display URLs and queries you have saved, content you have checked out, open workflow assignments, available metadata profiles, personal folders, and so on. To open this tray, click My Content Server in the trays area.

Graphic of native 11g My Content Server tray
LinkDescription

My URLs

Expand My URLs to display previously saved URLs. Click a URL to open the target address in the work area.

Click My URLs to specify and save links you want to make readily available:

Title: The displayed name of the link.

URL: The complete Uniform Resource Locator (URL) of the website; for example: http://www.example.com.

My Saved Queries

Opens the Saved Queries Page page to modify or delete previously saved queries. Expand My Saved Queries to display previously saved queries. Click a query to execute the associated search.

To save a query, choose Save Search from the Actions menu on the Search Results page.

My Recent Queries

Expand My Recent Queries to display the text form of the queries you performed recently. Click a query to execute the associated search. Click Clear to remove all queries from the list.

My Recently Viewed Content

Expand My Recently Viewed Content to display the most recent Content Information Pages you have viewed. Click a list item to open Content Information Page for that item.

My Quick Searches

Displays the Quick Searches Page which lists both the quick searches your administrator creates and the quick searches you explicitly create with the Create New option on this page.

My Workflow Assignments

Displays the Workflow in Queue Page which lists of all content items currently in a workflow for which you have responsibility.

My Content Profile Links

Displays a list of your defined content profiles. Click a link to display the profile.

My Subscriptions

Displays the Subscriptions Page which lists of all content items to which you subscribe.

My Checked-Out Content

Displays the Checked-Out Content for User Page which lists of all content you have checked out.

My Search Result Templates

Displays the Search Result Templates for User Page, from which you can build custom search results views.

My Folders

Displays a list of personal folders. Expand or collapse a particular level in the folder hierarchy to view folders contained within that folder. Click a folder name to display the contents of the folder in the work area. For more information about folders, see Section 21.1.2.

My Downloads

Displays a list of recent content items that you have downloaded from Content Server.

My Scheduled Jobs

Displays a list of jobs requiring your attention.


16.3.5 Content Management Tray

Use this tray to manage content in Content Server. You must be a Contributor to access this tray. To open this tray, click Content Management in the trays area.

Graphic of native 11g tray area
LinkDescription

Checked Out Content

Opens the Checked-Out Content for User Page that lists all files currently checked out of Content Server.

Work In Progress

Opens the Work in Progress Page that lists files that have been checked in, but not released.

Active Workflows

Opens the Active Workflows Page that lists the currently active workflows.

Expired Content

Opens the Expired Content Page that lists files that have expired or that are set to expire soon.

Search For Local File In Repository

Opens the Search for Local File Page that lets you select and compare a file from a local file system against all electronically signed content to which you have access. You can validate an external file against a single content item from the Content Information - Signatures Tab.


16.3.6 Quick Search Field

Use this field to perform a search at any time. By default, the Quick Search field searches for the specified search terms in the title, content ID metadata, and text indexed for full-text search if your system supports it. You can also create custom search queries that incorporate the specified search terms.

Graphic of native 11g quick search field

Note:

If you have changed your layout to the Classic layout, you can select Quick Search on your Adding Links to Favorites page to enable the Quick Search field.


ItemDescription

Quick Search

Displays available search queries. The default query (labeled Quick Search) searches for the specified search terms in the title, content ID metadata, and text indexed for full-text search if your system supports it. The name of the selected query persists until you select another query.

The list can contain queries created by your administrator (listed under System Searches), and queries that you create (listed under My Quick Searches) with the Quick Searches Page.

Text entry field

Enter search terms for use with the selected query.

Search icon

Initiates the search and displays a search results list for specified query and search terms.


PKQ ppPKC_EOEBPS/folders_concept.htm6' Understanding Folders

6 Understanding Folders

This chapter describes folders and how they are used by Oracle WebCenter Content to organize and aid in retrieving documents. It has the following sections:

6.1 About Folders

Folders in Oracle WebCenter Content are used to organize documents. In the WebCenter Content user interface they are always created in the context of a library, and like libraries, they can be shared, followed, copied, moved, and secured. By using folders to organize content, you can:

  • Find content quickly by browsing the folder structure.

  • Create a query folder to organize content associated by search criteria.

  • Share groups of content easily with co-workers.

6.2 Folder Differences Between the WebCenter Content and Native 11g Interfaces

The folders in the WebCenter Content user interface are not visible in the native 11g user interface by default but can be enabled. If enabled, folders as used in the WebCenter Content interface are displayed in the Browse Content tray under Folders. Using folders differs between the WebCenter Content and native 11g user interfaces. This chapter focuses on common features. Where features differ, this chapter focuses on the WebCenter Content interface. For details about understanding and using folders in the native 11g interface, see Section 21.1.2.

Figure 6-1 Folder Comparison Between Interfaces

Folder Comparison

6.3 Browsing the Folder Hierarchy

When you open a library from a results list in the WebCenter Content interface, a hierarchy of folders is displayed in the side bar. Like traditional folder hierarchies, you can expand folders to display subfolders, also called child folders. Selecting a folder in the hierarchy displays the contents of the folder in a results list.

When you expand the Browse Content tray in the native 11g user interface, several folder options are available and are listed in Table 6-1. If the folder option has been enabled in the native 11g user interface, then virtual folders can be created and used to help organize content.

Table 6-1 Folder Options

NameDescription

Library Folders

Library folders in the native 11g user interface are not organizational folders in the traditional sense. Instead they refer to web pages predefined by your system administrator.

Folders

Folders are virtual folders that organize content. These are not available by default and must be enabled by your system administrator.

Query Folders

Query folders are virtual folders that function much like a saved search; each time you access the folder, you initiate the query associated with the folder. The contents of a query folder are the content items returned by the query. The contents of query folders can change dynamically as the contents of the repository change.


6.4 Searching For Folders

In the WebCenter Content user interface, you can search for folders using either the search field above the hierarchy in the side bar, or using the search box in the banner area. Results are displayed in the side bar if using the search field, and in the results list area if using the search box.

6.5 Working With Folders

In the WebCenter Content interface, either right-click the folder in the side bar hierarchy and use the contextual menu, or select the folder in a results list and use the tool bar to create new folders, modify folder properties, set the folder as a favorite, or make other changes to the folder.

Figure 6-2 Folder Contextual Menu

Folder Contextual Menu

6.6 Understanding Folder Security

In the WebCenter Content user interface, security can be set at library and folder levels as well as the document level. Security is inherited from the containing library unless it is set independently. For more information, see Section 4.5.1.


Note:

It is possible that you can have rights set to a folder in a library or containing folder that you do not have access to. In this case, you can find the folder by searching but not by browsing. You cannot browse to the library or folder it is in because you do not have rights to do so. Once you have found the folder, mark it as a favorite or create a shortcut in a folder to which you do have access in order to find the document quickly.


6.7 Saved Searches and Shortcuts

In addition to folders, any saved search or shortcut you create in a folder is displayed in the folder hierarchy. To use them, you must double-click a saved search or shortcut.

PKXs;'6'PKC_EOEBPS/libraries_concept.htm9JƵ Understanding Libraries

5 Understanding Libraries

This chapter describes document libraries and how they are used in the WebCenter Content user interface to organize and aid in retrieving documents.


Note:

Libraries are used differently in the native 11g and WebCenter Content user interfaces. In the native 11g interface, the Browse Content tray lists Library Folders, which can be set up by your system administrator as links to custom web sites for your organization. This is very different from how libraries are used in the WebCenter Content user interface. Libraries in the WebCenter Content user interface behave as the top level of folder hierarchies. In fact, if Oracle WebCenter Content is configured to do so, what show up as libraries in the WebCenter Content user interface are displayed under Folders in the Browse Content tray of the native 11g interface. This chapter focuses on how libraries work and are displayed in the WebCenter Content user interface. For more information on the differences between interfaces, see Chapter 6.


This chapter has the following topics:

5.1 About Document Libraries

Libraries provide structure and organization to documents in Oracle WebCenter Content. They are the top level of a folder tree in which all folders and documents should be stored. This is important to note because libraries as used in the WebCenter Content interface are listed as folders in the Browse Content tray of the native 11g user interface.

When a document is uploaded to a library, the library provides context to the document, helping to determine what metadata fields are associated with it and in some cases assigning values to the metadata automatically.

Documents can be uploaded to Oracle WebCenter Content outside of a library context as an unfiled document. However, organizing documents in libraries helps to ensure documents are secure, can be shared, and are easily found by yourself and others. In addition to containing documents, libraries can also contain folders and shortcuts to other libraries, folders, and documents. This provides a secure, fast and familiar way to navigate Oracle WebCenter Content.

There are two types of libraries:

  • Enterprise Libraries, created by individuals to provide flexible security and comprehensive document management used by an entire organization.

  • System Libraries, created and managed by Oracle WebCenter Content to organize documents that are in a system process, such as checked-out or expired documents. Documents cannot be uploaded to a system library.

Library Ownership

Libraries are owned by the people who create them. Enterprise library owners can transfer ownership, but as system libraries are created by Oracle WebCenter Content, they cannot have their properties edited.

5.2 Understanding Enterprise Libraries

Enterprise libraries are a robust way to secure, manage and share content that is accessed by many people in your organization. In an enterprise library you can set access at the document level, lock documents while editing, and maintain a comprehensive revision history of documents. You can create and share any number of enterprise libraries and folders or shortcuts within enterprise libraries.

5.2.1 Using Enterprise Libraries to Manage Documents

Enterprise libraries provide a secure area in Oracle WebCenter Content to store documents that need to be seen and accessed by many people. For example, you can create an enterprise library for a project team to use as a workspace for shared documents. Or a Human Resources department can use an enterprise library as a place to store forms that are used by all employees. In both cases, many people can access the documents and any changes can be managed by checking documents in and out while tracking revision history.

Uploading documents to an enterprise library offers the following benefits:

  • Available to many people unless you choose otherwise. An enterprise library gives you the ability to control access at all levels: library, folder, and document. Only an enterprise library lets you define different access permissions to different folders or documents in the same library.

  • Full choice of metadata options through profiles and the ability to enter and modify values for all necessary metadata fields.

  • The ability to control changes to documents by checking it out. Checking out a documents locks the document while you make changes, keeping others from accidentally overwriting your changes.

  • The ability to access documents from mobile devices. Enterprise libraries can be easily accessed from an Apple or Android device using the Oracle WebCenter Content mobile app.

  • Ability to share enterprise libraries and folders with others. You can collaborate with others on documents in a shared enterprise library or folder.

5.2.2 Setting Security for Enterprise Libraries and Folders

When you set security permissions for an enterprise library or folder, you allow people access to the documents contained in the enterprise library or folder based on the library or folder access permissions, or you explicitly define different access for the documents in them.

You can allow access to individual documents in an enterprise library. This can be done in different ways:

  • By explicitly defining access rights to each document, either as it is uploaded or by modifying the document properties after the documents has been uploaded or revised. For more information on uploading documents, see Chapter 11.

  • By creating a folder and defining the access rights you need at the folder level, then moving documents into the new folder and propagating the folder access down to the contained documents. For more information on propagating metadata, see Section 13.4.

5.2.3 Resolving Upload Conflicts and Tracking Revision History

If two people have modified a document in an enterprise library or folder and then try to upload the documents, the changes may conflict. In this case, the first revision checked in will be overwritten by the last. However, Oracle WebCenter Content maintains revision history. This allows you to manually compare each document revision and merge changes.

5.2.4 Using Enterprise Libraries and Folders to Manage Document Access

Access to documents in an enterprise library can be managed at the document level, but access is controlled initially at the library or folder level. All documents uploaded into the context of a library or folder use the permissions for that library or folder by default unless an access control list is defined.

For example, consider that:

  • All legal documents are stored in a library titled Legal.

  • All documents pertinent to pending litigation are stored in subfolders of the Litigation folder in the Legal library.

  • All engineering documents are stored in a library called Engineering.

  • All engineering specifications are stored in subfolders of the Specifications folder in the Engineering library.

Figure 5-1 Legal Library Hierarchy

Folder Hierarchy

There are many lawyers with access to the Legal library, but only a few who are qualified to review technical specifications. The security group for all lawyers is assigned to the Legal library when it is created. All documents uploaded to the Legal library and its subfolders can be accessed by all lawyers unless limited by an access control list, which can limit other security. For example, a shortcut to the Engineering Specifications folder can be created in the Legal library and an access control list can be used to set security for the Specifications folder to allow only those few lawyers who are qualified to review specifications.

Now consider that engineers must also review technical data included in legal presentations and pending litigation documents. The engineer that needs access varies depending on the document, but no engineer should have access to legal documents outside of what they need to review. When a document in the Legal library is ready for technical review, the document properties can be modified and an access control list defined for that document that gives read permission to a specific engineer.

Table 5-1 Enterprise Library Structure Example

Folder NameSecurity GroupAccess Control ListsPeople

Legal

legal (R, W, D)


tjimenez (lawyer)

Contracts



tjimenez (lawyer)

Litigation



tjimenez (lawyer)

Case X



tjimenez (lawyer)

Document X


R

tjimenez (lawyer), jmarshall (engineer)

Engineering

technical (R, W, D)


jmarshall (engineer)

Specifications



jmarshal (engineer)

Product Y


R

tmano (lawyer)

Document Y



tmano (lawyer)

Product Z


R

tjimenez (lawyer)

Document Z



tjimenez (lawyer)


Note that in this case, Table 5-1 shows the access control list is set at the document level for giving engineering access to legal documents, but it is set at the folder level when giving lawyers access to the engineering specifications. In this example, one engineer is reviewing only the one document, but each lawyer reviews all specifications for a specific product.

5.3 Understanding Shortcuts, Favorites, and Following

You can easily access and follow libraries, folders, and documents in several ways. Setting any item as a favorite adds it to your Favorites list for quick access by clicking Favorites in the side bar. You can create a shortcut to a library, folder, or document and put it in a convenient location for quick access. You can also follow items so you are notified by e-mail when they change.

PKY>J9JPKC_EOEBPS/intro.htm Introduction to Oracle WebCenter Content

1 Introduction to Oracle WebCenter Content

This chapter provides a general introduction to Oracle WebCenter Content and describes some of the many benefits to your organization WebCenter Content provides. It covers the following topics:

1.1 About This Guide

This guide details how to use Oracle WebCenter Content. It is divided into the following parts:

Part I provides overview information about Oracle WebCenter Content and content management and includes concepts common to all ways of working with WebCenter Content. Part II includes information on using the features available in the WebCenter Content user interface, while Part III details how to use the features available in the native 11g user interface. Lastly, Part IV provides information about accessing Oracle WebCenter Content through desktop applications or through a mobile device.

The information contained in this document is subject to change as the product technology evolves and as hardware, operating systems, and third-party software are created and modified. Due to the technical nature of browsers, databases, web servers, and operating systems, Oracle cannot warrant compatibility with all versions and features of third-party products.

1.2 What is Oracle WebCenter Content

Oracle WebCenter Content manages information you use every day. Information found in e-mails, reports, memos, slide presentations, and more. Oracle WebCenter Content stores it, organizes it, and secures it so that only the people needing the information have access to it. And most importantly, it helps you find it quickly when you need it and view it through a standard web browser, even if you do not have the software that created the document.

1.3 Benefits of Using WebCenter Content

Communication fuels organizations and helps them effectively coordinate and execute everything from global business plans to personal task lists. Necessary information in today's organizations is captured in office documents, personal e-mail, memos, video conferences, and a variety of other types of unstructured content. Left unmanaged, critical information is lost, business processes become strained, the right people don't have the right access to documents, and you make poor decisions based on inaccurate and outdated information. Oracle WebCenter Content lets you find critical information in a comfortable environment, with applications you already use every day.

Designed for You

You can contribute documents using a standard web browser, but also through Windows Explorer and familiar desktop applications such as Microsoft Word, Excel, and Outlook. You can route a critical contract through a workflow, allow others to see the latest design specifications, or upload a training video for your team. Oracle WebCenter Content brings you drag-and-drop convenience for uploading documents, and you have the choice to find and view content in a variety of ways using Windows Explorer, your favorite web browser, or even your Apple iPad, iPhone or Android device.

Saves You Time

How many hours have you spent trying to find one critical bit of information about a project, customer, or legal challenge? Was it in an e-mail? Did you see it in a slide presentation? Oracle WebCenter Content brings a powerful way of searching to help you filter and retrieve the information you need quickly.

Reduces Your Risk

With the increase of documentation-intense compliance mandates, the need to store and retrieve compliance evidence has also increased. Using Oracle WebCenter Content records management capabilities enables you to manage records and retention policies and easily retrieve the information, saving you time and reducing your risk.

Meets Your Needs

If your content management needs extend into rich media industries such as advertising, distance learning, web development, or other lines of business requiring use of images and video, Oracle WebCenter Content allows you to manage such digital assets simply and effectively. Store high-resolution source videos on one server while resized conversions are served out of a separate streaming server. Or group advertising collateral for a catalog in a folio, route it through a workflow, then zip it into a compressed file for distribution to a vendor. All these options are possible with Oracle WebCenter Content using the native 11g user interface.

1.4 Basic WebCenter Content Concepts

Oracle WebCenter Content provides an automated system for sharing, managing, and distributing business information. This information can be in documents or some other type of content, and in this guide the terms document, content, and file are often used interchangeably. In some cases, for example if image conversion is enabled, multiple files may be managed together as one document. Whatever term is used, the information is being stored electronically and is managed as a single item. Oracle WebCenter Content manages the item by providing a means for you to find the information you are looking for while controlling access to the document so that only authorized people can use it.

You can access current information quickly and securely from any standard web browser. You can manage letters, reports, engineering drawings, spreadsheets, manuals, sales literature, and more, in one powerful content management system.

For typical business document management, Oracle WebCenter Content offers an easy and intuitive user interface with drag-and-drop convenience and sophisticated searching capabilities through the WebCenter Content user interface. If your needs require a more specific feature, such as managing videos, images, or records, then the native 11g user interface provides a fully featured and familiar user experience. In addition to accessing your content through a web browser, Oracle WebCenter Content provides several alternatives for those who want an experience more integrated with their office applications, or for those on the go. Desktop and WebDAV interfaces allow you to perform primary content management actions from your desktop using folders and files to represent documents, and applications are available for accessing your documents from your Apple iPad, iPhone, or Android device.

1.4.1 Useful Vocabulary

The following terms are used throughout this guide and it is useful to understand their definitions.

TermDefinition

WebCenter Content user interface

An easy and intuitive user interface offering drag-and-drop convenience and sophisticated searching capabilities. This user interface was introduced in Oracle WebCenter Content 11gR1 (11.1.1.8.0). For more information, see Part II, "Using the WebCenter Content User Interface with Oracle WebCenter Content".

native 11g user interface

A feature-rich user interface offering a familiar user experience for those who need to manage rich media beyond traditional office documents, including images, records, and videos. For more information, see Part III, "Using the Native 11g User Interface with Oracle WebCenter Content".

content server

Oracle WebCenter Content uses a content server as a repository for storing and managing your documents. Multiple content servers can be used to help your company manage performance or to separate content to provide additional security or features.

document, content item, file

Any file uploaded to Oracle WebCenter Content is referred to as a document or content item interchangeably. They are discreet items tracked by the content server even though they consist of metadata and one or more files, revisions, or renditions.

metadata

Metadata is information about a document, such as the title, author, release date, and so on. You can use metadata to find documents in WebCenter Content, much as you would search for books in a library by author or subject. When you upload a document, you assign some metadata values, while Oracle WebCenter Content assigns some metadata values automatically. The metadata is stored in a database that works with Oracle WebCenter Content.

To simplify metadata entry and selection, libraries and folders have metadata predefined. When you upload a document to a particular library or folder, the document is assigned the predefined metadata, as well as any metadata you specify. In some cases, your system administrator can create Profiles that specify which metadata values are displayed when you upload, search for, or view documents and document properties.

It is important that you understand your organization's metadata fields and always assign metadata carefully. Proper metadata makes documents easier to find, and ensures that only users who have the proper permissions can access a document.

document properties, content information

Document properties and content information are used interchangeably in this guide. They refer to the metadata associated with a file uploaded to Oracle WebCenter Content as well as other associated information. Associated information can include additional renditions, revision history, security and sharing options and any file attachments, among others. The terms are specific to the information in Oracle WebCenter Content and do not refer to document properties associated with a file outside of WebCenter Content, such as those assigned by Microsoft Word, Excel, and other applications.

search

Search for documents using metadata. If full-text indexing has been configured by your system administrator, it also allows you to search for text within documents. In the WebCenter Content user interface, you can apply filters when searching to refine your results. For example, you can enter search terms then limit the search to libraries only, documents you are following, just images or a variety of other filter options.

browse

Browse through libraries and folders to find documents. As with searching, in the WebCenter Content user interface various filter options are available to you when browsing.

content repository

When you upload a document, the electronic file is stored in a content repository. The original, or native, file is stored in a central repository for native files. If your system has conversion features installed and enabled, a web-viewable version of the file (such as PDF) is created and stored in a special repository for web-viewable files. If you are not using conversion, or if a particular file type cannot be converted, a copy of the native file is placed in the repository for web-viewable files.

Any user with the correct security permissions can view the web-viewable version of a document or get a copy of the original file from the repository of native files. Security permissions determine who can view, revise, and delete a particular document.

The native file and any web-viewable files associated with a document are called renditions. For example, the PDF version of a document is a rendition of that document, as are the HTML and XML versions.

revision control

To change a document that is uploaded to Oracle WebCenter Content, you must check in a new revision to the repository. It is good practice to check out a document prior to making changes. Checking out the document locks it from being checked out by anyone else, alerting them that you are making changes. Only one person can have a document checked out at any given time, but others can view the released version of the file.

When you upload the modified file back into Oracle WebCenter Content, it is automatically stored as a new revision of the document. You can view or copy previous revisions, but the latest revision is displayed by default.

workflow

In some cases you may need someone to review or approve a document before it is released for others to see. A workflow specifies how to route content for review and approval before it is released to the system. Each workflow can include multiple review and notification steps, and multiple reviewers to approve or reject the file at each step.

persistent URL

Every document in the repository for web-viewable files keeps a permanent web address that does not change from one revision to the next. The most current version is always displayed when you point your browser to the persistent URL of a document.

security groups and accounts

You can set Oracle WebCenter Content security to control which users can view, edit, and delete particular documents. In some cases when you upload a file, you may have to specify a value for the following security-related metadata fields:

  • Security group: All users belong to one or more security groups. They also have a specific level of access within each security group determined by their role and the permissions the role grants. The security group is a required metadata field for all documents and may be assigned by default. Only the users who have permission to that security group can work with the document.

  • Account: Accounts are an optional feature that your system administrator can use to define a more flexible security model. As with security groups, only users who have permission to a particular account can work with documents that belong to that account.

roles

A role is a set of permissions (Read, Write, Delete, Admin). For example, as a team member, you can view a schedule (Read access), but as the team leader, you may also have to update the schedule (Read and Write access).

The system administrator assigns roles to users to define their level of access within a security group. Available roles depend on your company needs and are created by your system administrator. Examples of typical roles are:

  • guest: The guest role has Read permission to the Public security group. Users can search for and view content in the Public security group.

  • contributor: The contributor role has Read and Write permission to the Public security group. Users can search for, view, upload, and download content.

  • sysmanager: The sysmanager role has privileges to access the Admin Server links under the Administration menu in the native 11g user interface.

permissions

Each role can have the following permissions for each security group:

  • read (R): The person can view and copy files in that security group.

  • write (W): The person can view, upload, download, and get a copy of documents in that security group. Authors can change the security settings of a document if the author has admin permission in the new security group.

  • delete (D): The person can view, upload, download, get a copy, and delete files in that security group.

  • admin (A): The person can view, upload, download, get a copy, and delete files in that security group. If this person has Workflow rights, they can start or edit a workflow in that security group. The person can also upload documents in that security group with another person specified as the Author. Non-authors of a document with document admin permission can change the security settings of a document if the non-author has admin permission in the new security group and optionally, account.

The permissions for a security group are the highest permission defined by any of the roles for that group. For example, if you are assigned Guest and Contributor roles, where guest is given Read permission and Contributor is given Write permission to the Public security group, you have Write permission to content in the Public security group.

access control list (ACL) security

An access control list is an explicit list of individuals or groups with permission to access or interact with a specific document.

Depending on how access control list security is configured, up to three additional fields are available for use when adding, modifying, or searching for documents:

  • User Access List

  • Group Access List

  • Role Access List

Important: To use an access control list on a document, the document must be uploaded to a security group that supports access control lists, or the added security does not work. If you are uncertain if the security group you are using supports access control lists, check with your system administrator.

To use access control lists with documents, you assign one or more predefined users, groups, or roles to the document. In addition, you assign the permissions (Read (R), Write (W), Delete (D), or Admin (A)) to each of the access list entries you specify.

For example, suppose you add a document and you want guests to have read access and you want all logged-in users to have read and write access. First, add the guest role to the document and click the R (Read) permission icon. Then, add the authenticated user role to the document and click the W (Write) permission icon to grant both the read and write permissions.

If either role is valid for the user, they have the access specified for the valid role. If both roles are valid for the user, they have the greater of the two permission sets. If a user has admin level access to a security group, then an ACL does not apply.

Important: If no access control list is enabled for a document, then the document is available to any user whose security group and account permissions allow them access. However, once a user or group has been added to the access control list of a document, then users not explicitly added lose access to the document.


1.4.2 Document Libraries

When using the Oracle WebCenter Content user interface, documents in the content server are organized into libraries that can also contain folders and subfolders. There are the following types of libraries:

  • System Libraries, created and managed by Oracle WebCenter Content to organize documents that are in a system process, such as checked-out or expired documents. Documents cannot be uploaded to a system library.

  • Enterprise Libraries, created by individuals to provide flexible security and comprehensive document management used by an entire organization.

Documents are uploaded to WebCenter Content in the context of a library or folder. To upload documents to a specific library or folder, you must navigate to the library or folder first, and then upload the document. Doing so applies the correct metadata to a document and organizes it in Oracle WebCenter Content so that you and others can find it. For detailed information on libraries and folders, see Chapter 5 and Chapter 6.

1.4.3 Folders

Folders in Oracle WebCenter Content are used to organize documents so that you can find them quickly by browsing the folder structure. There are two main types of folders in Oracle WebCenter Content:

  • Traditional folders, which are similar to folders you use to organize your files in your computer file system.

  • Query folders, or saved searches, which are collections of documents based on search criteria you have saved.

Traditional folders in Oracle WebCenter Content are like folders on your computer with one important distinction: they have metadata associated with them. They can automatically assign default folder metadata to the documents organized in them, and you can easily change metadata for multiple documents by propagating metadata assigned at the folder level to documents in them. Having default metadata or being able to change metadata to a group of documents through propagation saves you time. You can upload documents to a folder and know that they are secure and easily found without having to manually assign security and other metadata, and you can change the metadata of multiple documents easily when information changes.

Query folders aren't actually folders in the traditional sense, but rather they are search criteria that you have saved that are executed when you click the query folder. They give you the experience of browsing through a file system while in reality searching for content using metadata. For example, a query folder can be created titled Today's Documents that when clicked displays all documents checked in today. The contents change every day without people having to upload documents to a specific folder, because clicking the folder tells Oracle WebCenter Content to find all documents uploaded on the current day and display them in a list.

1.4.4 Shortcuts

You can create shortcuts to any item (library, folder, or document) to which you have access in Oracle WebCenter Content. A shortcut points to an item, allowing you a way to quickly organize how you access items pertinent to you. For example, you may work on several projects, each requiring a specification document, and each specification document is stored in the associated project folder. You can create a folder containing shortcuts to each specification document. So instead of having to search through multiple project folders to find the documents you want, you can click your folder and have shortcuts to all specification documents listed there for quick, convenient access.

1.4.5 Favorites

Each person's Favorites listing is private and always available in the side bar. You can easily add to your Favorites folder by clicking the star on a document list or from a document properties page. Favorites provide a quick and easy way to navigate to those items you use frequently or those items you want to quickly find later.

1.4.6 Finding Content

There are two ways of finding documents in Oracle WebCenter Content:

  • Browsing

  • Searching

In the WebCenter Content user interface, find content using the Search, Browse, and Favorites links in the side bar. The first time you log in to Oracle WebCenter Content, the Search link is active in the side bar and the latest revision of all documents in Oracle WebCenter Content to which you have access are displayed in the content area. In this view, all documents are displayed in a single flat list regardless of what library or folder they may be in. You can review the documents in the content area or filter the results using the search box above the content area. You can personalize this page to display all documents, all libraries, or your favorites the next time you log in.

In the native 11g interface, browse for content using the Browse Content or Content Management trays in the side bar, or search for content using the Search tray, Quick Search field, or other search form.

You can search for a document by its metadata, by full-text, or by a combination of the two. Only the documents you have permission to view are displayed in the results list.

You can specify search terms for one or more metadata fields. Depending on how your system is configured, you can use search operators that specify if the search term is a whole word or part of a word, or if it appears at the start or the end of the field. You can also use wildcard characters to match one more characters in a search term.

To simplify or customize the search form, an administrator can create one or more metadata profiles that specify the metadata fields that are included on the form.

With the Quick Search function, you can search at any time from the home page. You can specify a search term for a selected field or for all supported fields. If your system is configured for full-text search, Quick Search also searches for the search term in the text of documents.

1.4.7 Managing Images and Videos

If Oracle WebCenter Content is configured to manage digital assets such as images or videos, you can use the native 11g user interface to quickly find, group, convert, and download images and videos of various sizes, formats, and resolutions to meet your business needs. This helps maintain a consistency of use across your organization. For example, an organization's logo can be available in a variety of sizes for advertisements, web pages, and presentation, or a company training video can be available in a variety of formats for streaming on an intranet, presenting to an audience, or copying to tape.

1.4.8 Managing Content through Office Applications

Oracle also offers Oracle WebCenter Content: Desktop, which can enhance the WebDAV client environment by more closely integrating with Windows Explorer, Microsoft Outlook, Lotus Notes, and other applications. For more information, see Chapter 26.

1.4.9 Grouping Content into Folios

A folio is a logical grouping or framework to organize content stored in Oracle WebCenter Content. Folios are available through the native 11g user interface and useful when you want to organize groups of documents, such as contracts or sales information, that include some common components and some unique components, and assemble them in a standardized sequence and hierarchy. Folios are also useful when you want to create and review a group of documents as part of one or more workflow processes.

With a simple folio, you collect one or more items in a single level. With an advanced folio, you can organize content in a hierarchy of folders.

An advanced folio can contain folders, called nodes, placeholders for content, called slots, and documents. These elements are displayed by default in a hierarchical structure, similar to a standard file system.

1.4.10 Routing Content Through Workflows

In the native 11g user interface, the workflow process routes a file for review and approval before it is released to the Oracle WebCenter Content repository. Users are notified by e-mail when they have a file to review.

You can optionally sign and approve a file with an electronic signature which uniquely identifies the contents of the file at a particular revision and associates the signature with a particular reviewer.

You can create two types of workflows in Oracle WebCenter Content:

  • In a criteria workflow, files automatically go into a workflow if the values entered in the metadata fields upon check-in meet certain criteria. Criteria workflows are useful for individual documents that are approved by the same reviewers on a regular basis (newsletter articles, for example).

  • In a basic workflow, files are specifically identified in the workflow, along with the contributors, reviewers, and steps. This type of workflow requires an administrator to initiate the process, and is best suited for groups of documents that go through a workflow or individual documents with unique workflow requirements.

1.5 Basic WebCenter Content Tasks

Regardless of whether you access Oracle WebCenter Content from your desktop, mobile device, or web browser using either the WebCenter Content interface or the native 11g user interface, managing your documents has several common factors:

  • Logging in to gain access to your documents

  • Finding the documents you need

  • Viewing documents and their properties

  • Uploading documents you want managed

  • Downloading documents you need

  • Organizing documents in useful ways

  • Sharing documents with others through workflows

PKp-e%PKC_EOEBPS/part_android.htmK Using Other Ways to Work with WebCenter Content

Part IV

Using Other Ways to Work with WebCenter Content

Oracle WebCenter Content can be accessed through means other than a web browser, such as through Windows Explorer or Microsoft Office applications.

This part contains the following chapters:

PK4xPKC_EOEBPS/desktop_integration.htm48 Accessing Managed Content Directly from Within Your Desktop Applications

26 Accessing Managed Content Directly from Within Your Desktop Applications

Oracle WebCenter Content: Desktop provides a simplified interface for managing files in a unified way from all your familiar desktop applications.

This chapter has the following topics:

For more information on using Oracle WebCenter Content: Desktop, see Using Oracle WebCenter Content: Desktop.

26.1 About Oracle WebCenter Content: Desktop

Oracle WebCenter Content: Desktop is optional software that you install on your computer and that allows you to access content servers from within popular desktop applications (for example Microsoft Word).

You can perform content management tasks (checking out, checking in, and many more) directly from your desktop application, without using the content servers' own interfaces.

In addition, you can set up your web browser to search a WebCenter Content repository directly from the browser search field.

You can use the following desktop applications:

  • Microsoft Windows Explorer (file management)

  • Microsoft Word (word processing)

  • Microsoft Excel (spreadsheets)

  • Microsoft PowerPoint (presentations)

  • Microsoft Outlook (email)

  • Lotus Notes (email)

  • Internet Explorer (web browsing)

  • Mozilla Firefox (web browsing)

  • Google Chrome (web browsing)

For more information, including supported versions, see "Supported Client Applications" in Using Oracle WebCenter Content: Desktop.

You can use the following content servers (although not all servers support all features):

  • Oracle WebCenter Content Server

  • Oracle Content Server

  • Oracle Content Database

  • Generic WebDAV-based repositories


Note:

Administration of the content servers cannot be performed through the supported desktop applications: administrative tasks must be performed through the content servers' own interfaces.


26.2 Managing Content Through Windows Explorer

After you install the Oracle WebCenter Content: Desktop client software on your computer, you can see a node named "WebCenter Content Servers" in the folders pane of Windows Explorer. Beneath this node are all the content servers that you can connect to. A hierarchy of libraries, folders, and files is shown for each content server. What the hierarchy looks like depends on the content server type, version, and configuration. Content from the servers can be shown in the content, preview, and details panes.

Desktop integration into Windows Explorer

Here is what you can do from within Windows Explorer (if allowed by the content server type and configuration):

  • Create and remove certain types of library and folder. (Some types can only be created or removed by administrators.)

  • Add new documents to the content server, so that they become managed documents. You can also remove documents from the content server.

  • Check out documents from the content server. You can also check them back in or undo a checkout.

  • View documents that are on the content server, without checking them out.

  • View the properties, metadata, preview, and other information associated with a managed document. You can also change some of this information.

For more information, see "Integration into Windows Explorer" in Using Oracle WebCenter Content: Desktop.

26.3 Working With Managed Content Within Microsoft Word, Microsoft Excel, and Microsoft PowerPoint

After you install the Oracle WebCenter Content: Desktop client software on your computer, a WebCenter Content menu or ribbon is added to the Microsoft Office application.

Desktop integration into Microsoft Word

Here is what you can do from within the Microsoft Office application (if allowed by the content server type and configuration):

  • View a document on the content server without checking it out. You can also view a document that has already been checked out.

  • Open a document on a content server. This will check out the document and lock it from other users.

  • Modify documents.

  • Update the currently open document to the latest revision on the content server.

  • Create an unmanaged version of the of the current managed document.

  • Check the current document in to the content server as a new revision.

  • Save the current document as a new content item on the server.

  • Compare different revisions of managed Microsoft Word documents on a WebCenter Content instance.

  • Insert links to files that are on a content server.

  • Add document management properties to documents.

  • Update document metadata and manage other properties of the document on the content server.

For more information, see "Integration into Microsoft Office Applications" in Using Oracle WebCenter Content: Desktop.

26.4 Working With Managed Content Within Microsoft Outlook and Lotus Notes

After you install the Oracle WebCenter Content: Desktop client software on your computer, a number of content management functions become available in your email client (Microsoft Outlook or Lotus Notes).

For more information, see "Integration into Email Clients" in Using Oracle WebCenter Content: Desktop.

Integration into Microsoft Outlook

Content management items are added to menus or ribbons in Microsoft Outlook. Additionally, a node named "WebCenter Content Servers" is optionally added to the mail folders panel. This shows all the content servers to which you can connect, and a hierarchy of libraries, folders, and files for each server. What the hierarchy looks like depends on the content server type, version, and configuration. The preview pane shows tabbed panels for summary information, metadata, security information, and document preview.

Desktop integration into Outlook

Here is what you can do from within Microsoft Outlook (if allowed by the content server type and configuration):

  • Check in email messages and their attachments, to preserve them exactly as they were received, and to share them with others in your organization. Checked-in email messages are not intended to be checked out, modified, and checked back in.

  • Open and view email messages managed by a content server.

  • Send managed email messages to other people. They become unmanaged email messages when you do this.

  • Save copies of managed email messages. Again, they become unmanaged email messages when you do this.

  • Check in email distribution lists.

You can make changes to the email messages that you open from a content server, but you cannot then check them back in to the content server.

You can never check in email messages that have been modified since they were checked out.

Integration into Lotus Notes

Content management items are added to the Actions menu in Lotus Notes.

Lotus Notes Actions menu

Here is what you can do from within Lotus Notes (if allowed by the content server type and configuration):

  • Check in email messages and their attachments, to preserve them exactly as they were received, and to share them with others in your organization. Checked-in email messages are not intended to be checked out, modified, and checked back in.

  • Check in email distribution lists.

26.5 Using Web Browser Search Fields to Search for Managed Content

If you want, you can set up your web browser to use Oracle WebCenter Content Search as a search provider (instead of, for example, Google). This enables you to search for content on a WebCenter Content instance directly from your browser search field.

Desktop search facility added to IE web browser

Here is what you can do from within your web browser (Internet Explorer, Mozilla Firefox, or Google Chrome):

  • Search for content on an Oracle WebCenter Content Server instance, directly from the search field.

  • View the search results in the web browser.

A content server search provider in your web browser is for a specific Oracle WebCenter Content Server instance. You cannot search multiple content servers using a single search provider.

If you are logged in to the content server that you are searching, you will see all content items that meet the search criteria and for which you have access privileges. If you are not logged in, you will see only public content.

For more information, see "Integration into Web Browsers" in Using Oracle WebCenter Content: Desktop.

PKs44PKC_EOEBPS/folders_old.htm Working with Content Folders

21 Working with Content Folders

This chapter describes how to use alternative folder and WebDAV interfaces, similar to a conventional file system, to organize and manage some or all of the content in Oracle WebCenter Content Server.

21.1 Introduction

Content Server includes components that provide a hierarchical folder interface, similar to a conventional file system, for organizing and managing some or all of the content in the repository.

  • Folders: This component (FrameworkFolders component) provides a hierarchical folder interface within the browser, similar to a conventional file system, for organizing, locating, and managing repository content and content item metadata. The Folders functionality is installed but disabled by default. Folders is a scalable, enterprise solution and is intended to replace the earlier Contribution Folder interface.

  • Contribution Folders: This optional component (Folders_g component) provides a hierarchical folder interface within the browser, similar to a conventional file system, for organizing repository content. The component is installed but disabled by default. The newer, Folders component is meant to be a replacement for Contribution Folders.


    Note:

    Running both Folders and Contribution Folders is not a supported configuration. Content in Contribution Folders should be migrated to the Folders interface. For more information about migrating Contribution Folder content, see the Oracle Fusion Middleware Administering Oracle WebCenter Content.

    WebCenter Portal 11.1.1.8.0 and earlier supports the folders_g component only. For information about configuring Content Server with WebCenter Portal, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.


  • WebDAV (Web-Based Distributed Authoring and Versioning): Both folder components work with Content Server's built-in WebDAV functionality to allow users to remotely manage and author content using clients that support the WebDAV protocol. The WebDAV interface provides a subset of the options available through the browser interface. In general, you can create, delete, move, and copy both folders and content items, and you can modify and check in content items. To check out content items through the WebDAV interface, you must use a WebDAV client that can open the file. To perform other management tasks, such as specifying or propagating metadata values, you must use the standard browser interface.

Oracle also offers Oracle WebCenter Content: Desktop, which can enhance the WebDAV client environment by more closely integrating with Windows Explorer, Microsoft Outlook, Lotus Notes, and other applications. For more information, see the Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.

This section covers the following topics:

21.1.1 Browsing to Content

This section covers the following topics:

21.1.1.1 Browse Content Tray

Browsing content in Content Server is similar to looking for a paper document in your organization's file cabinets. In a file cabinet, you find the file drawer, then the folder, then the document. In Content Server, you find documents and links to websites in folders in the Browse Content tray.

The Browse Content tray is a hierarchical link structure (the Library), where metadata define the folders in the hierarchy. The folder, Library Folders, is set up by default. Your system administrator determines the hierarchy of any folders within Library Folders. Click the plus sign (+) next to a collapsed folder to expand the contents of the folder. Click the minus sign (-) next to an expanded folder to collapse it.

Click a link in the last folder of a hierarchy to display:

  • A list of content items that match the folder's metadata and that you have permission to view

  • A website

  • A report that provides information about content items, users, metadata fields, or other content server elements.

21.1.1.2 Browsing Content to Find a File

To find information by browsing content:

  1. Click Browse Content Tray to expand the tray.

  2. Scan the list of folders until you find the one you are looking for.

  3. Click the plus sign (+) next to the folder to expand the folder contents and continue drilling down through the folders until you reach a link to the following:

    • A search results page

    • A different website

    • A content server report

21.1.2 About Folders

Folders is an optional component (Framework Folders component) for use with Content Server that, when enabled, provides a hierarchical folder interface, similar to a conventional file system, for organizing and locating some or all of the content in the repository.

Folders is a scalable, enterprise solution and is intended to be a replacement for the earlier Contribution Folders component. Some of the benefits that Folders provides include:

  • No practical limits on the number of folders or files (content items) in the Folders interface

  • Default metadata for content items added to a folder

  • Metadata inheritance for newly created folders

  • Metadata propagation for new or modified metadata values

  • Query-based folders for dynamically retrieving content items from the repository

  • Query-based retention folders for specifying basic retention rules for the items returned by the query

  • Folder-level security using the standard Content Server security model

  • Integration with the WebDAV interface for local folder and file authoring and management

  • Integration with Oracle WebCenter Content: Desktop for enhanced local folder and file authoring and management

This section covers the following topics:

21.1.2.1 The Folders Interface

The Folders hierarchy is accessible through both the standard content management pages and the WebDAV interface.

The familiar folder and file model provides a framework for organizing and accessing content stored in the repository. Functionally, folders and files are very similar to those in a conventional file system. You can copy, move, rename, and delete folders and files. You can also create shortcuts to folders or files so you can access a content item from multiple locations in the hierarchy.

You can think of the files in the Folders interface as symbolic links or pointers to content items in the repository. The operations you perform in the Folders interface, such as searching or propagating metadata, effectively operate on the associated content items.

21.1.2.2 Folders and Files

As with a conventional file system, Folders offers a convenient way to organize content. Users can easily view the relationship between folders and subfolders and can browse to a group of content items.

Using Folders, users can perform the following actions with the privileges defined by Content Server's standard security model:

  • Browse to locate content items for check-in, check-out, and to view and change folder and item information.

  • Create new folders and subfolders.

  • Create new content items in a folder or add existing repository content to a folder.

  • Add shortcuts to folders or content items in one or more locations. Shortcuts act as placeholders for the referenced content item.

  • Move or copy folders or files to other locations.

  • Rename a folder or file.

  • Remove a file from the folders hierarchy. This does not affect the associated content item.

  • Delete a folder or file. When you delete a folder or file, the folder or file and any shortcuts to it are removed from the folders hierarchy. Any content items associated with the files are set to expired in the repository.

  • Create a query folder that contains content items returned by the query associated with the folder. For more information about query folders, see Section 21.1.2.4, "Query Folders and Folder Search."

  • Create a retention query folder and assign retention rules for the content items returned by the query. For more information about query folders and retention scheduling, see Section 21.1.2.5, "Folders Retention."

  • Assign folder security and default metadata values for content items created in the folder. You can also propagate specified metadata values to the contents of a folder or block propagation for a given folder. For more information, see Section 21.1.2.9, "Folder and Content Item Metadata."

The Folders interface follows several conventions familiar to users of file systems:

  • Use standard Windows naming conventions when creating folders. Do not use the following characters:

    ? # & / \ * " | < > :

  • Content Server can store multiple files of the same name as separate content items. However, in the Folders interface, file names in a given folder must be unique (in the same way that a folder in Windows cannot contain two files with the same name).

21.1.2.3 Shortcuts

With Folders, you can reference the same folder or content item in multiple locations using shortcuts that act as placeholders for the referenced folder or file. You can create shortcuts to folders or files to help you locate and manage the target content items within the folder hierarchy.

21.1.2.3.1 Folders and Shortcuts

Folders and folder shortcuts are identified with different icons:

IconDescription
Folder icon described in the description column

Folder: Folders can contain other folders, content items, and shortcuts to other folders and content items. Folders are identified by a standard folder icon.

Folder link icon described in the description column

Folder Shortcut: A folder shortcut includes the contents of the associated folder in the hierarchy at the point where the shortcut is stored. Folder shortcuts are identified by a folder icon with an arrow and can reference either a folder or a query folder. Folder shortcuts are excluded from metadata propagation actions.

Query Folder icon described in the description column

Query Folder: The contents of a query folder are the repository content items returned by the query associated with the folder. Query folders are identified by a folder icon with a magnifying glass.

Retention Query Folder icon described in description column

Retention Query Folder: Similar to a query folder, the contents of a retention query folder are the repository content items returned by the query associated with the folder. You can additionally specify retention rules for the content items returned by the query. Retention query folders are identified by a folder icon with a magnifying glass and a clock.


21.1.2.3.2 Content Item Links

You can think of content items in the Folders interface as links to items in the repository. There are two types of links for content items:

IconDescription
Primary Link icon described in the description column

File (primary link): There can be only one primary link to a content item in the Folders interface. The primary link represents the content item in the repository and is identified by a standard document icon. In most respects, working with a file (or primary link) is the same as working directly with the content item in the repository. For example, if you delete a file, the status of the associated content item in the repository is set to "expired."

Secondary Link icon described in the description column

Shortcut (secondary link): There can be any number of file shortcuts in the Folders interface to an associated content item. A file shortcut is identified by a document icon with an arrow indicating that it is a reference to the actual content item. Shortcuts are excluded from metadata propagation actions. Changes you make by means of the shortcut (such as metadata changes) are made to the underlying content item. Changes you make to the shortcut itself (such as deleting the shortcut) do not affect the underlying content item.

Secondary Link icon described in the description column

Query result: The contents of a query folder are the repository content items returned by the query associated with the folder. Query content items are identified by a document icon with a magnifying glass.


21.1.2.4 Query Folders and Folder Search

A query folder functions much like a saved search; each time you access the folder, you initiate the query associated with the folder. The contents of a query folder are the content items returned by the query. The contents of query folders can change dynamically as the contents of the repository change.

Query folders contain the actual repository content items returned by the query. That is, folders and shortcuts are not included in the contents of query folders.

With the contents of a query folder, you can copy the associated content items, view and update metadata information for individual items, or propagate metadata changes through all items in the query folder.

Folders also expands the standard search results options to include the Create Query Folder option to save a search query as a query folder. For more information, see Section 21.2.4.2, "Save a Search as a Query Folder."

To search for folders or files from within in the Folders hierarchy, use the options in the Search menu in a given folder. You can search any or all folder metadata fields to find folders or files within the folders hierarchy that match the specified search criteria.

21.1.2.5 Folders Retention

With Folders, you can perform basic content retention scheduling by creating a retention query folder, assigning retention attributes to the folder, and then configuring the retention schedule. You can assign retention rules based on the age of the content item or on the number of revisions. If you have a license for Oracle WebCenter Content: Records, you can also define retention rules based on categories defined in Records.

You must be an administrator to specify retention rules or schedules. For information about specifying retention scheduling, see the Oracle Fusion Middleware Managing Oracle WebCenter Content.

Considerations

The following considerations apply to retention query folders:

  • Retention rules are associated with the retention query folder but are stored separately from the standard folder metadata. For this reason, you cannot search for a query folder based on the folder's retention attributes.

  • Unlike standard query folders, retention query folders search only database values and cannot perform full-text searches even if full-text search is supported on your system.

  • If you specify multiple retention rules for a particular retention query folder, all the rules must be satisfied for the disposition to occur. For example, if you specify the age as 1 calendar year and the number of revisions to keep as 3, only those items that are more than 1 year old and that are older than the last three revisions are deleted.

  • Different queries can include the same content item in their results. In this case, the retention rules for each retention query folder are applied independently from one another. For example, if one query folder specifies the number of revisions to keep as 2 and another specifies the revisions to keep as 3, only two revisions of the item are retained.

  • Folders retention is treated differently than that in Oracle WebCenter Content: Records. When using Records, if multiple delete actions are called, the retention with the longest interval is used. In Folders, the shortest interval always runs first.

Considerations with Oracle WebCenter Content: Records

If you use both Folders and Oracle WebCenter Content: Records on the same system, the following additional considerations apply:

  • If you have Records installed, it is possible to have two retention schedules (as well as multiple rules) for the same item. If a content item has retention rules defined in both Content Server and in Oracle WebCenter Content: Records, only the retention and schedule defined by the Records system are used.

  • If you have Records installed with a level of DoD Baseline or higher, retention query folder options are not available in the Content Server interface. Any existing retention query folders retain their icon and (inactive) retention attributes, but function as a standard query folder.

    If the level is then set to Standard or lower, then retention query folder options are enabled in Content Server and the rules for any existing retention query folders become active.

21.1.2.6 Personal Folder

In the root folder of the Folders hierarchy is a Users folder that contains a folder defined for you as an authenticated user. You can create subfolders and content items in the same way you do with other folders in the hierarchy. Every authenticated user can have a personal folder.


Note:

You can only add folders and content items to your personal folder. Changes you make within the /Users folder are not maintained.


Folders provides menu options to quickly add folders, files, and shortcuts to your personal folder, referred to in menus as Add to My Folder. Although your personal folder is visible only to you, the items in the folder are governed by the security settings for the item itself and not necessarily those of the enclosing folder. Some items may be accessible to other users, for example, in search results.

To access your personal folder, click My Content Server in the trays area and then click My Folders.

21.1.2.7 Security and User Access

Users can create and edit folders, shortcuts to folders, and links to documents as allowed by Content Server's standard security model. Folders are assigned security attributes in the same way they are assigned to content items, including security group, account, and Access Control List attributes, if enabled.

By default, folders inherit the security settings and other default metadata defined for the parent folder. You can, however, explicitly set security and metadata values for a given folder and propagate those values to folders and content items within the folder.

21.1.2.8 Content Item Versioning

You can check out content items and check in new versions of those content items through the Folders interface in much the same way you do through the standard content management pages. When you view or edit the metadata information for a particular content item, you can choose menu options to check out the item and then check in a new version of that item.

Folders provides two modes for viewing content item versions:

  • Published Items (consumption mode): The latest released revisions of documents are displayed. These are the same revisions that are returned in search results listings.

  • All Items (contribution mode): The latest revision of each document is displayed, regardless of its state. These can include the revisions of documents that are still in workflow.

As a user, you can switch between the two modes to see released content items only or to see content items that require work before being released. The selection you make remains in effect until you explicitly change it.

21.1.2.9 Folder and Content Item Metadata

Every folder has a set of metadata values that can be applied to content items added to the folder. You can configure folders to enforce metadata rules on their content items or allow any or all values to be modified. For example, a folder could be configured to enforce 'Secure' as the value for the Security Group metadata field. Then, when a content item is added to that folder, the Security Group value automatically updates to Secure.

Folders inherit the default metadata assigned to their parent folders unless the folder is explicitly configured otherwise. Subsequent changes to a parent folder's metadata do not affect the metadata for existing subfolders unless explicitly propagated down through the hierarchy.

Folder metadata inheritance and propagation make it easy to apply metadata to content items. Whether you are an administrator managing all folders and files or a user managing your own folders and files, it is a good idea to plan your metadata strategy before you start creating folders and adding content items. Your strategy should include the following basic steps:

  1. Determine whether specific folders or branches in the hierarchy have unique metadata requirements and how best to identify and manage those requirements.

  2. Determine which metadata fields (if any) a user should specify when adding or checking in a content item through a particular folder.

  3. Determine which metadata fields (if any) should have a default value or an enforced value for a particular folder.

  4. Determine which subfolders (if any) are eligible to be changed when propagating metadata through a folder.

  5. Determine whether to use profiles to manage metadata requirements. An administrator can create one or more profiles to organize, selectively display, and control access to metadata fields based on rules associated with the profile.

21.1.2.9.1 Default Metadata

Default metadata values are automatically applied to new content items created in or checked in to a folder. To modify the default metadata values for a folder, you must have Delete permission to the folder or be the Author and have Write permission.

If default values are not provided for all required fields, you are prompted to provide them when you create or check in the content item. If the folder has the Prompt for Metadata option selected, you are prompted to provide metadata values for the item rather than relying on the folder's default metadata settings.

Default metadata values are also used as the default values when propagating metadata.

21.1.2.9.2 Metadata Propagation

With proper permissions, you can propagate metadata values from a folder to its subfolders and content items. To propagate metadata to the content items in a particular folder, you must have Write permission for the folder and the content items themselves. To propagate to any folders below the folder in the hierarchy, you must have Delete permission the folders.

Content items in a folder do not necessarily have the same security settings. To propagate metadata to content items, you must also have Write permission for the content item. To restrict changes to folders only, you can optionally select the Propagate To Folders Only option.

When you propagate metadata, you select the metadata fields and can specify the values to propagate from the metadata available for the current folder. You can propagate any metadata value that you can change. For example, you can propagate the Security Group or Owner values, but you cannot propagate the Content ID. You can also propagate a blank field, such as the Comment or Expiration Date fields, to clear the associated values from content items.

You can configure folders to prevent propagation by selecting Inhibit Propagation in the folder information for that folder. You can optionally override a folder's inhibit setting using the Force Propagation setting on the Propagate window. For more information about propagation, see Section 21.2.2.3, "Propagate Folder Metadata."

21.1.2.9.3 Metadata Profiles

An administrator can create sets of metadata as one or more profiles that the administrator or other users can easily apply to folders when specifying folder defaults or when propagating metadata. For more information about using profiles, see the Oracle Fusion Middleware Managing Oracle WebCenter Content.

21.1.2.10 Migrating Contribution Folder Content

If you have content in an existing Contribution Folders hierarchy (folders_g component) and want to migrate the folders and files to the Folders interface, you can use the Folders Migration utility to replicate the folder hierarchy and selectively migrate folder content. For more information about the Folders Migration Utility, see the Oracle Fusion Middleware Administering Oracle WebCenter Content.

21.1.3 About Contribution Folders

Contribution Folders is an optional component for use with Content Server that, when enabled, provides a hierarchical folder interface to content in Content Server in the form of contribution folders. With contribution folders, you can create a multilevel folder structure.

Users can use the familiar folder and file interface to organize and manage content items. Users can create, delete, copy, and move content items. Users can check content items in, and out, and apply default metadata to content items by checking them in through a particular folder.

21.1.3.1 Content Item Security

The user logins and security controls in Content Server also apply to content that you manage through contribution folders. For example, if you have Read permission for a content item, you are able to view the file, but you are not able to check in a revision to the file.

21.1.3.2 Folder Metadata Inheritance

When you create a new folder, the metadata from the parent folder populates the fields for the new folder. The folder initially inherits metadata, but you can change its values without affecting the parent folder. A folder has the same metadata as a content item.


Note:

Specifying a default value for the Author field will limit the users who can check documents into the folder. Only users with Admin permission to at least one group will be able to check documents into a folder for which a default author is specified.


Subsequent changes to a parent folder's metadata do not affect the metadata for existing subfolders. To apply a parent folder's metadata to subfolders and content items, you can use the metadata propagation function. For more information, see Section 21.1.3.5, "Metadata Propagation."

21.1.3.3 Default Metadata Values

When a file is checked in to Content Server through a contribution folder, default metadata values are entered on the content check-in form automatically. Default metadata values are evaluated in the following order:

  1. Contribution folder default values: When you choose New Folder from the New Item menu, any content default metadata values defined for that contribution folder are entered on the content check-in form. These values are defined on the Hierarchy Folder Configuration page.

  2. User default metadata values: If any content metadata defaults are not defined for the contribution folder, the user's default metadata values are applied. These values are defined by each user for new content items on their Default Information Field Configuration page, and for revised content items on their Revision Information Field Configuration page.


    Important:

    User default metadata values are only applicable when creating new content items using WebDAV. They are not applicable when using the Content Server web browser user interface.


  3. System default metadata values: The system default values are applied to any fields that are not defined by the contribution folder or the user's default metadata. These values are defined by the system administrator.


    Important:

    System default metadata values are only applicable when creating new content items using WebDAV. They are not applicable when using the Content Server web browser user interface.


  4. None: You can leave a metadata field blank if it is not a required field. If you leave a required field blank, an error occurs and the content item is not checked in.

21.1.3.4 Trash Bin

The Trash Bin function is an optional feature that sends deleted items to a Trash folder, rather than permanently deleting the items. Items in the Trash folder can then be permanently deleted or restored to their original location in the folder hierarchy. This enables users to recover files and folders that have been mistakenly deleted.

Please note:

  • The Trash folder works much like a normal folder except that items deleted from the Trash folder are permanently deleted.

  • Deleting a revision from a content information page bypasses the Trash folder and permanently deletes the revision.

  • Users can select whether to make use of the Trash folder or permanently delete items immediately. They can also select whether to see all deleted items in the Trash folder or just the items they deleted themselves.

  • Deleting an item from the Exploring page puts the item into the Trash folder.

  • Deleting an item from WebDAV puts it into the Trash folder.

21.1.3.5 Metadata Propagation

The metadata propagation function enables contributors to copy default metadata values from a folder to its subfolders and content items. Typical uses for this function include:

  • After moving a large number of content items to a new folder structure, you want to apply the top-level folder's default metadata to all subfolders and content items.

  • You revised the default metadata for a folder, and you want to apply it to subfolders and content items within that folder.

Please note:

  • The propagation function applies each folder's metadata to all "uninhibited" subfolders and content items within those folders. Each uninhibited subfolder and content item inherits the metadata of the folder from which propagation was launched.

  • When you inhibit a folder, it is not affected by metadata propagation from a higher-level folder. However, you can still launch metadata propagation from an inhibited folder.

  • The system administrator selects which metadata fields are included in propagation. (This setting is systemwide.) By default, no metadata fields are included until they are specifically selected for metadata propagation.

  • If a folder metadata field does not have a value defined, subfolders and content items within that folder may not inherit the "blank" value during propagation and any existing metadata values may stay intact for these items. The system administrator specifies how the system handles blank fields.

  • When you launch metadata propagation, only folders and content items for which you have Write permission to the security group are affected.

21.1.3.6 Folder Content Item Revisions

When documents are edited and checked in to Content Server, the revised document must be converted, indexed, and released. Before this process is complete, the system considers the revised document to be the "latest" version. After the process is complete, the system considers the revised document to be the "latest released" version.

Depending on how Folders has been set up, users with read access to the content item see either the latest version or nothing at all if the item is not released. Authors, however, always see the latest version. By default, the latest version is available to all users with read access.

21.1.4 About WebDAV

WebDAV (Web-Based Distributed Authoring and Versioning) provides a way to remotely author and manage your content using clients that support the WebDAV protocol. For example, you can use Microsoft Windows Explorer to manage content in the repository rather than using the browser interface.

21.1.4.1 What is WebDAV?

WebDAV is an extension to the HTTP/1.1 protocol that allows clients to perform remote Web content authoring operations. The WebDAV protocol is specified by RFC 2518.0. For more information, see the WebDAV Resources website at

http://www.webdav.org

When a content management system such as Oracle WebCenter Content uses WebDAV, the WebDAV client serves as an alternate user interface to the native files in the content repository. The same versioning and security controls apply, whether an author uses the Web browser interface or a WebDAV client.

The WebDAV interface provides a subset of the options available through the browser interface. In general, you can create, delete, move, and copy both folders and content items, and you can modify and check in content items. To check out content items through the WebDAV interface, you must use a WebDAV client that can open the file. To perform other management tasks, such as specifying or propagating metadata values, you must use the standard browser interface.

You can use the WebDAV interface in Content Server with either the Contribution Folders interface or the Folders interface. For more information about the Contribution Folders interface, see Section 21.1.3, "About Contribution Folders." For more information about the Folders interface, see Section 21.1.2, "About Folders."

21.1.4.2 WebDAV Clients

A WebDAV client is an application that can send requests and receive responses using the WebDAV protocol. With a WebDAV client, you can check content out of the e Content Server repository, modify the content item, and check in a new revision using the native application menus.

You can use WebDAV folders in Windows Explorer to manage files that are created non-WebDAV application, but you must check content out of the Content Server repository using the Content Server browser interface rather than the native application.

21.1.4.3 Oracle WebCenter Content: Desktop

Oracle WebCenter Content: Desktop provides a set of embedded applications that help you seamlessly integrate your desktop experience with the WebDAV-based Content Server repository. Desktop provides convenient access to Content Server directly from Microsoft Windows Explorer, Microsoft Office applications (Word, Excel, and PowerPoint), and supported e-mail clients (Microsoft Outlook and Lotus Notes). Integrating Content Server with your desktop applications improves your ability to work with files on Content Server. You can easily manage files on the server and share files with other users directly from your desktop in addition to logging in to Content Server and using the Web browser interface. For more information about Desktop, see Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.

21.2 Working with Folders

Folders provides a hierarchical folder interface, similar to a conventional file system, for organizing and locating some or all of the content in the repository.

This chapter provides information about using Folders:

21.2.1 Folder Navigation

To view the folder hierarchy, click Browse Content in the trays area and click Folders. The Browse Content tray shows a tree view of the folder hierarchy. The basic hierarchy includes standard folders, such as the Users folder and any other folders created by your administrator.

To expand or collapse a particular level in the folder hierarchy, click the plus or minus icon next to the folder name in the Browse Content tray. To view the contents of a folder, click the folder name.


Note:

Individual folders are displayed only if you have Read privileges for that folder.


When you open a folder, its contents are displayed in the folder content area with folders in the top portion and content items in the bottom portion. Page menus provide options for adding folders and content items and for managing the current folder. Folder content menus provide options for managing selected items (folders or content items) in the current folder. Individual folder and content item menus provide options for managing the associated item.

The path to the current folder is displayed at the top of the page. You can click any folder in the path to open the contents of that folder.

21.2.2 Working with Folders

Working with folders in the Folders interface is similar to working with folders in a conventional file system. You can copy, move, rename, and delete folders and files. You can also create shortcuts to folders or files so you can access a content item from multiple locations in the hierarchy. Additionally, you can use folder to apply and manage metadata for the content items contained in the folder.

This section covers the following topics:

For information about copying or moving folders, see Section 21.2.3.4, "Copy or Move Folders and Files." For information about deleting folders, see Section 21.2.3.6, "Delete Folders and Files."

21.2.2.1 Create a Folder

Use this procedure to:

  • Create a folder

  • View and change folder information

  • Rename a folder

  1. Navigate to the folder where you want to create the new folder. You must have write permission in the folder where you want to create the new folder.

  2. Choose New Folder from the Add menu on the folder page.

  3. On the The Folder Creation form, specify a name for the folder.

    Use standard Windows naming conventions when naming folders. Do not use the following characters:

    ? # & / \ * " | < > :

  4. To specify Additional Fields, click show advanced options if the fields are not displayed.

  5. Choose an Owner for the folder from the list of defined users. By default, the current user is the owner.

  6. Choose a Security Group from the list of defined security groups. By default, the folder uses the security group of its parent folder.

  7. To prevent the folder from having its metadata modified unintentionally, select Inhibit Propagation.

    You can override this setting by selecting Force Propagation during metadata propagation. For more information, see Section 21.2.2.3, "Propagate Folder Metadata."

  8. To prompt the user to specify metadata rather than relying on the folder's default metadata settings when they create new content items in the folder select Prompt For Metadata.

  9. Click Create. The folder page shows the new folder and its associated Actions menu.

    If a folder with the specified name already exists in this location, the newly created folder is named Copy of name.

  10. To rename the folder, choose Rename from the folder Actions menu, specify the new name and click OK.

    Use standard Windows naming conventions when naming folders. Do not use the following characters:

    ? # & / \ * " | < > :

    For more information about copying and moving folders, see Section 21.2.3.4, "Copy or Move Folders and Files."

  11. To change other metadata values, including the name, choose Update Folder Information from the folder Actions menu, change the values outlined in the steps above and click OK.

    To change metadata values for the folder when you are viewing the contents of the folder, choose Folder Information from the Edit menu on the page.

21.2.2.2 Specify Default Folder Metadata

This procedure shows you how to define default metadata values to apply to new content items added to a folder. Default metadata values are also used as the default values when propagating metadata.

To change folder metadata, you must have Delete permission for the folder or be the Author and have Write permission.

  1. Click Browse Content in the trays area, then locate and open the folder for which you want to define default metadata.

  2. From the page Edit menu, choose Metadata Values.

  3. On the Editing Default Metadata Values page, specify the metadata values you want to apply to new items added to the folder.


    Note:

    Specifying a default value for the Author field will limit the users who can check documents into the folder. Only users with Admin permission to at least one group will be able to check documents into a folder for which a default author is specified.


    These values apply only to new repository content items. They are not applied to content items defined in the repository when they are added to a folder. Although you can modify the values before propagation, these values also act as the default values for propagation (described later in this section).

  4. Click Save.

21.2.2.3 Propagate Folder Metadata

This procedure shows you how to propagate metadata values to the items in a query folder or to a folder and its subfolders.

To change folder metadata, you must have Delete permission for the folder or be the Author and have Write permission. To change content item metadata, you must have Write permission for the content item.


Note:

Depending on the contents of a folder, propagation can change metadata values for a significant number of folders and content items. Before you begin, make sure you know what the consequences of propagation are.


  1. Click Browse Content in the trays area, then locate and open the folder or query folder in which you want to propagate metadata.

  2. From the page Edit menu, choose Propagate.

    The fields on the Propagate page are initially populated with the metadata values defined for the folder. Query folders show general defaults.

  3. On the Propagate page, select the check box next to a field you want to propagate.

  4. If necessary, specify the value to propagate in the associated field. If you propagate an empty field, it clears the field for all affected items.

  5. Repeat steps 3 and 4 for each field you want to propagate.

  6. To exclude content items and propagate metadata changes to subfolders only, select Propagate To Folders Only.

  7. To override the Inhibit Propagation setting specified for all subfolders, select Force Propagation.


    Caution:

    Propagation is recursive through all subfolders in the propagation folder. Propagation can change metadata values for a significant number of folders and content items. Use caution when propagating metadata and when using the Force Propagation option in particular.


  8. Click Propagate.

21.2.3 Working with Content Items

Working with content items in the Folders interface is similar to working with files in a conventional file system, except that the "files" represent content items stored in the repository.

This section covers the following topics:

21.2.3.1 Add a New Content Item to a Folder

To check in a new content item through the folder interface:

  1. Navigate to the folder to which you want to add the content item.

  2. Choose New Content Item from the page Add menu.

  3. On the Content Check-In Form, provide metadata information as necessary. The form is populated with the default metadata values defined for the enclosing folder. Required fields are indicated with an asterisk (*).

    For more information about checking content items, see Section 19.4.1, "Checking In a New File."

  4. After you enter all the appropriate metadata values, click Check In.

  5. If the check-in is successful, and you are working with published items only, the Check-In Confirmation page opens. If you are working with all items, the new revision is added to the list of available revisions.

    The content item is checked in and is represented by a file in the current folder. The name of the file in the folder is the name of the native file you checked in.

    If an item with the specified name already exists in this location, the newly created folder is named Copy of name.

  6. To rename the file, choose Rename from the file item menu. To change other metadata, choose Update Content Information from the file item menu.

21.2.3.2 Add an Existing Content Item to a Folder

To add a content item that is already in the repository to the folders interface:

  1. Navigate to the folder to which you want to add the content item.

  2. Choose Existing Content Item from the page Add menu.

  3. In the Add Existing Content Item window, provide metadata search information to locate the content item using any of the supported forms.

    For more information about the expanded search form, see Section 17.1.4, "Advanced Search Page." For more information about the query builder form, see Section 17.1.5, "Query Builder Form."

  4. After you enter all the appropriate metadata values, click Search.

  5. The Search Results page displays the repository content items, if any, that match your search criteria. To add an item to the folder hierarchy, click Select next to the associated item.

    If the Select button is not available for a particular item, it is because there is already a file representing the item in the folder hierarchy.

  6. The content item is represented by a file in the current folder. The name of the file in the folder is the name of the native file you checked in.

    If an item with the specified name already exists in this location, the newly created folder is named Copy of name.

  7. To rename the file, choose Rename from the file item menu. To change other metadata, choose Update Content Information from the file item menu.

21.2.3.3 Create a Folder or File Shortcut

To create a shortcut to a target folder or file listed in the current folder and store the shortcut in a selected destination folder:

  1. Navigate to the folder that contains the folder or file for which you want to create a shortcut.

  2. Choose Create Shortcut from the folder or file item menu.

  3. In the Create Shortcut window, Browse to the destination folder where the shortcut will be stored and select the folder.

  4. Verify the selected path in the Folder box at the bottom of the page and click OK.

  5. Specify a name for the shortcut.

    Use standard Windows naming conventions when creating folders and files. If a shortcut with the specified name already exists in this location, the newly created shortcut is named Copy of name.

  6. Click OK. If the shortcut is successfully created in a destination folder other than the current folder, click Yes to view the destination folder and click No to return to the current folder.

    Folder shortcuts are identified by a folder icon with an arrow. File shortcuts are identified by a document icon with an arrow.

21.2.3.4 Copy or Move Folders and Files

This procedure shows you how to copy or move folders or content items to another location:

  1. To copy or move an entire folder, navigate to the parent folder of the folder you want to copy.

    To copy or move one or more selected items, navigate to the folder containing the items.

  2. To copy or move a single item, choose Copy or Move from the associated item menu.

    To copy or move multiple items, select the items and choose Copy or Move from the folder Actions menu.

  3. In the Choose a Destination window, Browse to the target folder, select the folder, and click OK.

  4. To specify how naming conflicts are resolved, click Show Advanced Options.

  5. Copied files inherit the default metadata defined by the enclosing folder. By default, moved items retain their metadata values, including security metadata.

    If your administrator enabled the Auto propagate destination's metadata to folder option, you can select this option to have the moved items inherit the metadata defined by the enclosing folder in the same way that copied items do.

  6. Specify how to resolve duplicate names when you copy or move folders or files. After the copy or move operation completes, a window lists any conflicts and their resolutions.

    • Resolve conflicts if file/folder exists: Folders or files with name conflicts are renamed in the destination with a prefix of "copy of". If more than one copy is created, each subsequent copy is given a numeric increment (1, 2, 3, and so on.)

    • Override file/folder if exits: For one or more files, delete the duplicate file in the destination and replace it with the source file.

      For folders, merge the contents of the source and destination folders and replace the security attributes and metadata of destination folder with those of the source folder. For file conflicts within folders, delete the duplicate file in the destination and replace it with the source file.

      Deleted files are expired in the repository and removed from the folders hierarchy. Any shortcuts to deleted items are also removed from the folders hierarchy.

    • Skip copy/moves if file/folder exists: Skip individual items with folder or file name conflicts, but continue with the remainder of the copy or move operation. Folders with name conflicts are skipped in their entirety, including their contents.

  7. Click OK. The items are copied (or moved) to the destination folder.

  8. A window opens confirming the copy or move operation and any naming conflicts and resolutions. Click OK.

    As with any content item created in a folder, any new content items in the repository are created with the default metadata values assigned by the parent folder according to the rules of inheritance define for the chain of folders.

21.2.3.5 Check Out and Check in Files

The folder interface does not provide special options for checking out content. Use the check-out options provided by the Content Information and Search Results pages.

For more information about standard content check-out, see Section 20.2, "Checking Out Single Files."

Files in the folder interface always point to the most current revision available. When you check in a new version of a content item using the standard check-in options, the file and any shortcuts reference the new version.

For more information about standard content check in, see Section 19.4.3, "Checking In a Revised File."

21.2.3.6 Delete Folders and Files

Use this procedure to:

  • Remove a content item from the folder structure while leaving it in the repository

  • Delete a content item from both the folder structure and the repository


Caution:

When you delete a folder, all files within the folder and its subfolders are also deleted. All deleted files and associated shortcuts are removed from the folders interface and expired in the repository. Use caution when deleting folders.


  1. Navigate to the folder that contains the folder or file you want to delete.

  2. To remove a single file from the folders interface but leave it intact in the repository, choose Remove From Folder from the item action menu.

    Alternatively, select one or more files in the folder and choose, Remove From Folder from the folder Actions menu.

  3. To delete a single folder or file from the folders interface and expire the related content item in the repository, choose Delete from the item action menu.

    Alternatively, select one or more items in the folder and choose, Delete from the folder Actions menu.

21.2.4 Working with Search Options and Query Folders

This section covers the following topics:

21.2.4.1 Search for a Folder or File

Folders and shortcuts are not included in standard search or query folder results. To search for a folder, file, or shortcut in a given folder:


Note:

Folder and file searches search the specified folder only. They do not search subfolders.


  1. Navigate to the folder you want to search.

  2. To search for a folder within the current folder, choose Folder from the page Search menu. To search for a file, choose File from the page Search menu.

  3. For a selected field on the Folder/File Search form, choose a comparison operator that specifies whether the value matches exactly, is a substring within the actual value, and so on.

    For more information about search field operators, see Section 3.4.3

  4. For a selected field, specify a search value. If you leave a field blank, it effectively matches all values.

    Some fields allow you to directly enter a full or partial value. Other fields require that you choose a value from a list of values or through another selection process.

  5. Repeat steps 3 and 4 for each field you want to specify search criteria.

  6. Under Results Options, specify how to sort the search results. Choose a sort value from the Sort By list and choose whether the results are sorted in Ascending or Descending order.

  7. To initiate the search, click Search. To cancel the search, navigate away from the Folder/File Search form.

21.2.4.2 Save a Search as a Query Folder

With Folders, you also have the option to save a standard search query as a query folder.

  1. Enter your search criteria in the Quick Search field or the Expanded Form and click Search.

    Search options vary depending on system configuration. You can save any search you create as a query folder. For more information about creating and performing searches, see Section 17, "Finding Documents."

  2. On the Search Results page, choose Create Query Folder from the Search Actions menu.

  3. In the Create Query Folder window, Browse to the Parent Folder, or destination, where the query folder will be stored, select the folder, and click OK.

  4. Specify a Folder Name for the query folder.

    Use standard Windows naming conventions when creating folders.

  5. Click OK. The query folder is created in the destination folder.

    Query folders are identified by a folder icon with an magnifying glass.

  6. To modify the search criteria associated with a query folder, choose Folder Information from the associated item or page menus and click Edit next to the Query Text field.

    The Expanded Search form opens and displays the criteria currently defined for the query folder. Modify the criteria and click Save. Click Save to save the changes to the query folder information.

21.2.4.3 Create or Modify a Query Folder

To create or modify a query folder:

  1. Navigate to the folder where you want to create the new folder. You must have write permission in the folder where you want to create the new folder.

  2. Choose New Query Folder from the Add menu on the folder page.

  3. On the Query Folder Creation Form, specify a name for the folder.

    Use standard Windows naming conventions when naming folders. Do not use the following characters:

    ? # & / \ * " | < > :

  4. To specify the search criteria, click Edit next to the Query Text field.

    Search options vary depending on system configuration. For more information about creating and performing searches, see Section 17, "Finding Documents."

  5. To specify Additional Fields, click Show if the fields are not displayed.

  6. Choose an Owner for the folder from the list of defined users. By default, the current user is the owner.

  7. Choose a Security Group from the list of defined security groups. By default, the folder uses the security group of its parent folder.

  8. Click Create. The folder page shows the new folder and its associated Actions menu.

  9. To rename the folder, choose Rename from the Actions menu, specify the new name and click OK.

    Use standard Windows naming conventions when naming folders. Do not use the following characters:

    ? # & / \ * " | < > :

    For more information about copying and moving folders, see Section 21.2.3.4, "Copy or Move Folders and Files."

  10. To change search criteria or other metadata values you specified when you created the folder, choose Update Folder Information from the folder Actions menu, change the values and click OK.

    To change metadata values for the folder when you are viewing the contents of the folder, choose Folder Information from the Edit menu on the page.

21.2.5 Folder Access Example

Folders are a convenient way to grant access to certain content items. You assign security attributes to folders in the same way that you assign them to content items, including security group, account, and Access Control List attributes, if enabled. By default, content items inherit the security settings and other default metadata defined for the enclosing folder.

For example, assume you have a number of projects that members of your team are working on. You want each project to have its own folder (Project_1, Project_2, and so on) and separate folders to store project-related documents (Documents folder) and status documents (Status folder).

Project folder structure

The security considerations for the folder structure are as follows:

  • You want only members of your team to be able to add or modify the documents within the Projects folder.

  • You want project team members to be able to read status documents for each project, but you want only project leads to be able to add and modify status documents.

  • You want team members to be able to add and modify documents for a specific project. Some individuals may work on more than one project.

  • Within each project, you may want to restrict the number of team members who can modify a given document. This requires Access Control Lists (ACL) to be enabled.

To accomplish this, ask your administrator to set up the following group, roles, and accounts and to enable Access Control List functionality. For more information about groups, accounts, and Access Control Lists, see the Oracle Fusion Middleware Administering Oracle WebCenter Content.

  • Roles: Have your administrator create the following roles:

    • Team_Lead

    • Team_Member

  • Group: Have your administrator create a group called Projects and designate it as a special authorization group so you can use Access Control Lists. Have your administrator assign permissions to the roles in the group as follows:

    • Team_Lead: Assign Read (R), Write (W), Delete (D), and Admin (A) permissions.

    • Team_Member: Assign Read (R), Write (W), and Delete (D) permissions.

  • Accounts: Have your administrator create the following accounts for each project:

    • Project_1

    • Project_1/Documents

    • Project_1/Status

  • Users: Have your administrator assign roles and accounts to users as follows:

    • Team lead: Assign the Team_Lead role and the Project account with Read (R), Write (W), Delete (D), and Admin (A) permissions.

    • Team members: Assign the Team_Member role, the Project_1/Documents account with Read (R), Write (W), and Delete (D) permissions, and the Project_1/Status account with Read (R) permission.

Create the folder structure and assign security as follows:

Projects folder:

  • Group: Projects

Projects/Project_1 folder:

  • Group: Projects (inherited default)

  • Account: Project_1

Projects/Project_1/Documents folder:

  • Group: Projects (inherited default)

  • Account: Project_1/Documents

Projects/Project_1/Status folder:

  • Group: Projects (inherited default)

  • Account: Project_1/Status

The Team_Lead role has the additional option of specifying Access Control List security on any content item in the Project_1 folder or its subfolders, further restricting access to those items.

21.3 Working with Contribution Folders

Contribution Folders is an optional component (Folders_g component) that provides a hierarchical folder interface within the browser, similar to a conventional file system, for organizing repository content. The newer, Folders component is meant to be a replacement for Contribution Folders. For more information about Folders, see Section 21.2, "Working with Folders."

If you have content in an existing Contribution Folders hierarchy and want to migrate the folders and files to the Folders interface, you can use the Folders Migration utility to replicate the folder hierarchy and selectively migrate folder content. For more information about the Folders Migration Utility, see the Oracle Fusion Middleware Administering Oracle WebCenter Content.


Note:

WebCenter Portal 11.1.1.8.0 and earlier supports the folders_g component only. For information about configuring Content Server with WebCenter Portal, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.


This section covers the following topics:

This guide assumes that your Content Server instance is using the Trays layout with the Oracle skin, which is the default for Content Server.

21.3.1 Naming Folders

The Folders component mimics the Windows file system. Therefore, when you create a folder, you are not allowed to use double quotation marks in the name (for example, "doublequotedfolder"). Using double quotation marks causes an error. You must use the standard naming conventions for Windows when creating folders.

21.3.2 Defining User Configuration Settings

To define your contribution folder configuration settings:

  1. Click the My Content Server tray.

  2. Click My Folder Configuration.

  3. On the Folder Configuration page, Select a Content Style option.

  4. If the Hide/Unhide feature is enabled, select or deselect the Show hidden when browsing check box.

  5. If the Trash Bin function is enabled, select or deselect the following check boxes:

    • Remove items immediately when deleted

    • Show only items that user has deleted in trash virtual folder

  6. Click Update.

21.3.3 Defining User Metadata Defaults for New Content

To define default metadata values for new content checked in by a particular user.

These defaults are applied to any new content item checked in through a contribution folder only if a value is not defined for the folder. For more information, see Section 21.1.3.3, "Default Metadata Values."

These metadata values are applied only on initial check-in of a content item. These settings do not affect revisions to existing content. For information about how to set metadata defaults for revisions, see Section 21.3.4, "Defining User Metadata Defaults for Revised Content."


Important:

Each user should follow this procedure to define their default metadata before using WebDAV to check in content through a contribution folder. Defined defaults help ensure that content items do not all have the same metadata, and that content can be checked in if required values are not defined for the folder or in the system defaults. Each WebDAV contributor should repeat this procedure after a required metadata field is added or after accounts are enabled.


To define user metadata defaults for new content:

  1. Click the My Content Server tray.

  2. Expand the My Folder Configuration link.

  3. Click Default Information Field Configuration for user.

  4. On the Default Information Field Configuration page, specify the default values to be applied to new content upon check-in. Use Idoc Script in any information field.

  5. Click Update.

21.3.4 Defining User Metadata Defaults for Revised Content

These defaults are applied to any content item revision checked in through a contribution folder only if a value is not defined for the folder. For more information, see Section 21.1.3.3, "Default Metadata Values."

These metadata values are applied only upon check-in of a revision; these settings do not affect new content items. For information about how to set metadata defaults for new content, see Section 21.3.3, "Defining User Metadata Defaults for New Content."

To define default metadata values for revised content checked in by a particular user:

To define user metadata defaults for revised content:

  1. Click the My Content Server tray.

  2. Expand the My Folder Configuration link.

  3. Click Revision Information Field Configuration for User.

  4. On the Revision Information Field Configuration page, specify the default values to be applied to revised content upon check-in. Use Idoc Script in any information field.

  5. Click Update.

21.3.5 Viewing Contribution Folders

To view a contribution folder from a content server Web page:

  1. Click the Browse Content tray.

  2. Click the Contribution Folders link.

  3. On the Exploring Contribution Folders page, click folder links to drill down to the folder you want.

    Depending on how the system administrator set up the system, long display lists may be truncated and spread out over multiple pages. Navigation links are then provided to move between pages.

  4. To view the Hierarchical Folder Information page for a folder, click the Folder Information icon, choose Folder Information from the Action menu, or explore the folder and click the Info link.

  5. If the Web Folder feature is enabled and you are using Internet Explorer 5.0 or higher, choose Open Web Folder from the Content Actions menu to view the folder in Windows Explorer.

21.3.6 Viewing Content Items

To view content items from a contribution folder:

  1. View the Exploring page for the contribution folder that contains the content item.

    Depending on how the system administrator set up the system, long display lists may be truncated and spread out over multiple pages. Navigation links are then provided to move between pages.

  2. To view the content information for a content item, click the Information icon, or choose Content Information from the item Actions menu.

  3. To view a file, click the file link in the Name column.

    • If you selected the Native option under Content Style on the Folder Configuration page, you can optionally open or save the file.

    • If you selected the Web Viewable (Browse only) option under Content Style on the Folder Configuration page, the Web-viewable file opens.

21.3.7 Checking In Content

To check in a file through a contribution folder:

  1. View the Exploring page for the contribution folder you want to check the content item into.

  2. Display the content check-in form using one of the following methods:

    • Choose New Content from the Actions menu.

    • Click the Actions icon for an existing content item, and then choose Check In Similar.

    • Click New Check-In on the top menu, and then specify a folder in the Folder field on the check-in form.

  3. On the content check-in form, enter the required metadata and any optional metadata for the content item.

  4. Enter the path and file name of the Primary File. You cannot check two files with the same file name into the same folder.

  5. In the Inhibit Propagation field, specify whether the content item receives propagated metadata.

    • Set the value to false to apply propagated metadata to the content item.

    • Set the value to true if the content item's metadata should remain unchanged during metadata propagation.

  6. Click Check In.

If the number of content items in the folder exceeds the limit set by the system administrator, you receive an error message and cannot check in the new content item.

21.3.8 Adding Contribution Folders

To add a contribution folder, you must be a contributor.

To add a contribution folder:

  1. Choose New Folder from the New Item link on the Exploring Folder page:

  2. Specify an owner for the contribution folder.

  3. Specify any additional metadata values for the folder.

    • These metadata values are applied to content items upon initial check-in to this folder.

    • These metadata values override any values inherited from the parent folder.

    • Use Idoc Script in any information field.

  4. In the Inhibit Propagation field, specify whether the folder receives metadata propagated from a higher-level folder.

    • Set the value to false if the folder receives propagated metadata.

    • Set the value to true if the folder's metadata remains unchanged during metadata propagation.

  5. Click Save.

    The Exploring Contribution Folders pages shows the new contribution folder.

If the number of folders exceeds the limit set by the system administrator, you receive an error message and cannot check in the new folder.

21.3.9 Modifying Contribution Folders

To modify a contribution folder, you must have Write permission to the folder's security group. Folders without security metadata can be modified by all users.

To modify a contribution folder:

  1. Open the Hierarchical Folder Information page.

  2. Choose Update from the folder Actions menu.

  3. On the Hierarchy Folder Configuration page, revise one or more metadata values for the folder.

    • These metadata values are applied to content items upon initial check-in to this folder; these settings do not affect revisions to existing content in the folder.

    • These metadata values override any values inherited from the parent folder.

    • Use Idoc Script in any information field.

  4. In the Inhibit Propagation field, specify whether the folder receives metadata propagated from a higher-level folder.

    • Set the value to false if the folder receives propagated metadata.

    • Set the value to true if the folder's metadata remains unchanged during metadata propagation.

  5. Click Submit Update.

    The Exploring Contribution Folders pages shows the modified contribution folder.

If the number of folders exceeds the limit set by the system administrator, you receive an error message and cannot check in the new folder.

21.3.10 Moving Contribution Folders and Content

To move contribution folders and content items from one contribution folder to another:

  1. View the Exploring page for the contribution folder that contains the folders, content items, or both to move.

  2. Select the check boxes next to the folders and content items to be moved.

  3. Click the item Actions icon, and choose Move.

  4. Click the folder to move the selected items to. (You may have to navigate to a higher-level folder to display its subfolders.) The target folder is the open folder.

  5. Click OK.

    The selected items are moved to the target folder.

If local folder mapping is setup, if you move a file from one folder to another (either through the Folders user interface or WebDAV), the copy of that file in the local folder associated with the source folder is not deleted. For example, if you have a folder WebSite, files in this folder are automatically copied to its local folder, C:/Website/. If you now move a file from the folder WebSite to another folder, say, Intranet, with Z:/Intranet/ as the local folder, then the file copy in C:/Website/ is not deleted.

21.3.11 Creating a Shortcut

You can create a shortcut link to a contribution folder or content item in the folder hierarchy in two ways:

21.3.11.1 Creating a Shortcut from an Exploring Page

To create a shortcut from an exploring page:

  1. View the Exploring page for the contribution folder that contains the folder or content item for which you want to create a shortcut.

  2. Choose the folder or item Actions menu, and then choose Create Shortcut.

  3. In the Browsing window, click the folder where you want to create the shortcut link. (You may have to navigate to a higher-level folder to display its subfolders.) The target folder is the open folder.

  4. Click OK.

    A shortcut link is created in the target folder.

21.3.11.2 Creating a Shortcut from a Folder Information or Content Information Page

To create a shortcut from a folder information page or content information page:

  1. View the Hierarchical Folder Information page or Content Information page for the folder or content item for which you want to create a shortcut.

  2. Choose Create Shortcut from the Content Actions menu.

  3. In the Browsing window, click the folder where you want to create the shortcut link. (You may have to navigate to a higher-level folder to display its subfolders.) The target folder is the open folder.

  4. Click OK.

    A shortcut link is created in the target folder.

21.3.12 Deleting Contribution Folders and Their Content

This section covers the following topics:

21.3.12.1 About Deleting Folders and Content


Caution:

When you delete a folder, all subfolders and all revisions of all content items in the folders are also deleted. When you delete a content item, all revisions of that content item are deleted. Be extremely careful when deleting folders and content items so that you do not accidentally delete content.


Keep the following in mind when deleting contribution folders and content items:

  • When you delete folders and content items from the Folders hierarchy, the action that occurs depends on whether the Trash Bin function is enabled and whether you have chosen to use the Trash Bin function in your user profile:

    Trash Bin Function Enabled by System Administrator"Remove items immediately when deleted" Check Box on the Folder Configuration PageResult of Delete Action

    Enabled

    Cleared

    Deleting a folder or content item moves it to the Trash folder. Items can be permanently deleted or restored from the Trash folder.

    Enabled

    Selected

    Deleting a folder or content item permanently deletes it. Items cannot be restored.

    Disabled

    Selected or cleared

    Deleting a folder or content item permanently deletes it. Items cannot be restored.


  • To delete a content item, you must have Delete permission to the content item's security group. If accounts are enabled, you must have Delete permission to the account as well.

  • To delete a contribution folder, you must be the owner of the folder or a user with Delete permission to the folder's security group. If accounts are enabled, you must have Delete permission to the account as well.

  • If a folder contains any content items or subfolders that you do not have permission to delete, you cannot delete the folder.

21.3.12.2 Deleting a Folder or Content Item


Caution:

When you delete a folder, all subfolders and all revisions of all content items in the folders are also deleted. When you delete a content item, all revisions of that content item are deleted. Be extremely careful when deleting folders and content items so that you do not accidentally delete content.


To delete a content item, you must have Delete permission for the security group of that content item. To delete a folder, you must be the Owner of the folder or have Delete permission for the folder's security group, and you must have Delete permission for the security groups of all subfolders and content items within the folder.

To delete folders and content items:

  1. View the Exploring page for the contribution folder that contains the folder or content item you want to delete.

  2. Select the check box next to each folder and content item to be deleted.

  3. For multiple selections, choose Delete from the Actions menu. For an individual selection, choose Delete from the item Actions menu.

    You are asked to confirm the action.

  4. Click OK.

    All revisions of selected content items, any selected folders, any subfolders of selected folders, and all revisions of content items in these folders are deleted. Whether they can be restored depends on how Folders has been set up.

21.3.12.3 Permanently Deleting Folders and Content from Trash

To permanently delete items from the Trash folder:

  1. View the Exploring page for the Trash folder.

  2. Select the check box next to each folder and content item to be permanently deleted.

  3. For multiple selections, choose Delete from the Actions menu. For an individual selection, choose Delete from the item Actions menu.

    You are asked to confirm the action.

  4. Click OK.

    All revisions of selected content items, any selected folders, any subfolders of selected folders, and all revisions of content items in these folders are permanently deleted from Content Server. They cannot be restored.

21.3.13 Restoring Folders and Content from Trash

If you delete a folder or content item from the Trash folder, the folder or item is permanently deleted from Content Server. To prevent permanent deletion of folders and content, you can restore them from the Trash folder to their original parent folders. Items that remain in the Trash folder are still searchable.

To restore an item from the Trash folder to its original parent folder:

  1. View the Exploring page for the Trash folder.

  2. Click the Actions icon and choose Restore. (You can restore only one item at a time.)

  3. Click OK.

    The item is restored to its original parent folder.


    Important:

    If the original parent folder has been deleted and is still in the Trash folder, the restored item is moved to the original folder. If the original folder has been permanently deleted, you cannot restore the item.


21.3.14 Propagating Metadata

This procedure replaces metadata values for folders and content items that are not identified as "inhibited," and there is no "undo." Be extremely careful when propagating metadata so that you do not accidentally change values you meant to keep.

The system administrator selects which metadata fields are included in propagation. This setting is systemwide. Be certain that you know which metadata fields are enabled for propagation before launching the process.

You can only propagate metadata for a folder if you are the owner or administrator of that folder. Empty metadata field values may not be propagated, depending on how the system has been set up.

To copy metadata from a folder to its subfolders and content items:

  1. Display the Hierarchical Folder Information page for the folder from which you want to propagate metadata.

  2. Choose Propagate from the Folder Actions menu.

    The metadata values defined for the current folder are copied to any uninhibited subfolders and content items within those folders. Only content items and folders for which you have Write permission to the security group are affected.

21.3.15 Searching for Content in Folders

Your Content Server instance might or might not be configured for subfolders. If it is not, then you can still search for items in a single folder. Otherwise, you have the choice to search for content in a folder or the folder and everything below. If there are many subfolders, you might be limited in how many are actually searched.

If Folders supports searching in a folder and its subfolders, then follow this procedure to search for content items in Folders:

  1. Click Search.

  2. On the Search page, click Browse to find and select the folder, including its subfolders, to search.

  3. Specify any other parameters on the Search page and click Search.

21.4 Working with WebDAV

You can use the WebDAV interface in Content Server with either the Contribution Folders interface (Folders_g component) or the Folders interface (FrameworkFolders component). Except where noted, the topics in this section apply to both components.

This section covers the following topics:

21.4.1 Working with Folders

This section covers these topics:

21.4.1.1 WebDAV Folders

You connect to WebDAV folder as you would a networked location. The credentials you use are the same as those you use for the standard browser interface for Oracle WebCenter Content Server. You can work with folders and folder content as defined by your user permissions. For example, if you have Read permission for a content item, you can view the file, but you cannot check in a revision to the file.

The WebDAV interface provides a subset of the options available through the browser interface. In general, you can create, delete, move, and copy both folders and content items, and you can modify and check in content items. To check out content items through the WebDAV interface, you must use a WebDAV client that can open the file. To perform other management tasks, such as specifying or propagating metadata values, you must use the standard browser interface.

21.4.1.2 Connecting to a WebDAV Folder

You connect to a WebDAV folder as you would connect to a networked location. For example, to connect to a WebDAV folder in the Windows XP operating system:

  1. In Windows Explorer, click My Network Places in the Folders (left) pane.

  2. Double-click Add Network Place.

  3. In the Add Network Place Wizard window, click Next.

  4. Click Choose another network location and click Next.

  5. Enter the Web address of the WebDAV component using the following syntax:

    http[s]://host-name:[port]/web-root/idcplg/webdav

    For example:

    http://server.example.com/cs/idcplg/webdav

    If you are not sure which protocol, host name, or root folder to enter, see your system administrator.

  6. Click Next. You are prompted to enter a user name and password.

  7. Enter the user name and password that you use to access Content Server and click OK.

  8. Enter a name for the WebDAV folder to display in My Network Places and click Next.

  9. Optionally select Open this network place when I click Finish, and click Finish.

    A shortcut with the name you specified is displayed in My Network Places. With Windows Explorer, you can navigate the folder hierarchy, create, move, copy, paste, and delete folders and files.

21.4.1.3 Viewing Folders

To view folders in Windows Explorer or from the Open or Save As dialog in a WebDAV client:

  • Click the Web folder under the My Network Places node

  • Expand the Web Folders node under the My Computer node, and then select the Web folder

21.4.1.4 Creating a New Folder

You can create a new folder in Windows Explorer or from the Open or Save As dialog in a WebDAV client. Right-click an existing Web folder, choose New, and then choose Folder.

  • The newly created folder has the same default metadata as its parent folder. For information about how to modify the default metadata for Contribution Folders, see Section 21.3.3, "Defining User Metadata Defaults for New Content." For information about how to modify the default metadata for Folders, see Section 21.2.2.2, "Specify Default Folder Metadata."

  • You cannot create a new folder at the root level.

  • You can create folders within your personal folder (/Users/username/), however you typically cannot create a new folder in the Users directory itself.

  • You cannot create a new query folder. To specify the associated query, you must have access to the folder metadata which is only accessible through the Folders browser interface.

  • Do not use the following characters in the folder name:

    ? # & / \ * " | < > :

21.4.2 Working with Content

This section covers the following topics:

With WebDAV folders in Windows Explorer, you can check in, view, delete, copy, and move files that were not created in a supported WebDAV client, but you must check them out through the browser interface.

21.4.2.1 Checking In Content

To check in a content item through Windows Explorer, use either of the following methods:

  • Drag and drop a file from your hard drive or another network drive into a folder.

  • Copy a file from your hard drive or another network drive and paste it into a folder.

To check in a content item through a Microsoft Office application (Word, Excel, PowerPoint, and so on), Save a file in a folder and then close the file.

21.4.2.2 Check-In Troubleshooting

Placing a file in a folder checks the file in to the Content Server repository. Keep the following points in mind when checking in files through WebDAV.

General Check-In Considerations

  • You can use Windows Explorer to manage files that were created in a non-WebDAV client, but to check content out of the Content Server repository, you must use a WebDAV client.

  • You cannot check two files with the same file name into the same folder.

  • Make sure you define default values for required metadata fields for a folder or an error will occur when you try to check in content.

    For information about how to modify the default metadata for Contribution Folders, see Section 21.3.3, "Defining User Metadata Defaults for New Content." For information about how to modify the default metadata for Folders, see Section 21.2.2.2, "Specify Default Folder Metadata."

  • If the Save As window opens when you attempt to place a file in a folder, you do not have Write privileges to the security group defined for that folder. You must select a different folder, or save the file on your hard drive and then check in the file through a Web browser where you can select the appropriate metadata.

  • If your file has double-byte characters (for example, Chinese, Japanese, or Korean) in the file name and Content Server is running on a Western European operating system, you may not be able to check in the file through WebDAV due to a limitation in Microsoft's WebDAV clients. Eliminate double-byte characters from the file name or check in the file through the Web browser interface of Content Server.

  • Do not use the number sign (#) in your file name. The number sign (#) is an illegal WebDAV character.

  • If you use a shortcut to open a folder, the folder might not show recent changes to content items until you refresh the display by pressing F5 or selecting Refresh from the View menu. This is a known cache problem with folder shortcuts in Microsoft Windows.

Check-In Considerations for Contribution Folders

  • The title of the checked-in content item depends on the value of the WebDAV title allocation configuration parameter as set by the system administrator. The title is either the file name (with or without the file extension) or the default title metadata value defined for the folder where the content item resides. Content item titles are assigned as follows:

    • If the WebDAV title inheritance configuration setting is disabled (the default value), the title is the file name without the file extension (for example, "monthly_report"). This naming convention is applied even if a default title metadata value is defined for the folder.

    • If the WebDAV title inheritance configuration setting is enabled and no default title metadata value has been defined for the folder, the title is the file name with the file extension (for example, "monthly_report.doc").

    • If the WebDAV title inheritance configuration setting is enabled and a default title metadata value is defined for the folder, the title is the defined name (for example, "Monthly Report").

  • In most WebDAV configurations, an open file is not checked in to Content Server repository until the file is closed, so you can save the file repeatedly without affecting the revision number. Your system administrator can change this so that each sy-ave creates a new revision in Content Server.

21.4.2.3 Checking Out Content

Opening a file from a folder either through Windows Explorer or through a WebDAV client such as a Microsoft Office application checks out the file from the Content Server repository and locks the file so that other users can only view it.

The Undo Check Out option cancels the content item check-out. This option is displayed only if the content item is checked out, and it is only available to the user who checked out the content item.

21.4.2.4 Viewing Content

You can view a content item without affecting the revision number by opening the content item and then closing the file without saving it. This action results in an "undo check-out" rather than a check-in of a new revision.


Caution:

If you save any changes to a file opened from a WebDAV folder, you create a new revision.


21.4.2.5 Modifying Content

Use one of the following procedures to modify and check a new revision of a content item.

21.4.2.5.1 Modifying a File in a WebDAV Client Format

To modify a file that is in a WebDAV client supported format (Word, Excel, PowerPoint, and so on):

  1. Open the file from a folder, either through Windows Explorer or from a WebDAV client.

    The file is checked out of the Content Server repository.

  2. Make changes to the file.

  3. Save the changes.

  4. Close the file.

    The file is checked in as a new revision.

In most WebDAV configurations, an open file is not checked in to the Content Server repository until the file is closed, so you can save the file repeatedly without affecting the revision number. Your system administrator can change this so that each save, including automatic saves, creates a new revision in Content Server.

21.4.2.5.2 Modifying a File in a Non-WebDAV Client Format

To modify a file that is not in a WebDAV client supported format:

  1. Copy the file from a folder to a temporary location. Do not change the file name.

  2. Modify the file.

  3. Save the changes to the temporary file and close the file.

  4. Move or copy the file to its original folder, and replace the existing file.

    The file is checked in as a new revision.

21.4.2.6 Deleting a Folder or Content Item

You can delete a folder or content item from Windows Explorer or from the Open or Save As window in a WebDAV client. Browse to the folder or content item you want to delete, right-click and choose Delete from the menu (or press the Delete key).


Caution:

When you delete a folder, all files within the folder and its subfolders are also deleted. All deleted files and associated shortcuts are removed from the folders interface and expired in the repository. Use caution when deleting folders or content items.


For more information on security and the Trash Bin function for Contribution Folders, see Section 21.3.12, "Deleting Contribution Folders and Their Content." For information about the effects of deleting content in Folders, see Section 21.2.3.6, "Delete Folders and Files."

21.4.2.7 Restoring a Contribution Folder or Content Item

If you are working with Contribution Folders and the Trash Bin function is enabled, you can restore a folder or content item from Windows Explorer using one of the following methods:

  • Drag and drop the folder or file from the Trash folder to another contribution folder.

  • Cut the folder or file from the Trash folder and paste it into another contribution folder.

21.4.2.8 Copying Content

Copying a file from one folder to another checks in the copied file as a new content item. If the file has the same file name as an existing file in the target folder, a new revision is checked in. The new content item or new revision is stored with the file name and metadata of the latest revision of the source.

21.4.2.8.1 Copying Through Windows Explorer

Use one of the following methods to copy a content item through Windows Explorer:

  • Right-drag a file from a folder to another, release, and choose Copy Here.

  • Copy a file from a folder and paste it into another folder.

21.4.2.8.2 Copying Through Microsoft Office

To copy a content item through a Microsoft Office application (Word, Excel, PowerPoint, and so on):

  • Open a file from a folder, from the File menu, choose Save As, select a different folder, click OK, and close the file.


    Important:

    If the Save As dialog opens twice, you do not have Write privileges to the security group defined for the folder. You must select a different folder, or save the file on your hard drive and then check in the file through a Web browser where you can select the appropriate metadata.


21.4.2.9 Moving Content

Use any of the following methods to move a content item from one folder to another:

21.4.2.9.1 Moving Through Windows Explorer

Use one of the following methods to move a content item through Windows Explorer:

  • Drag and drop a file from one folder to another.

  • Cut a file from a folder and paste it into another folder.

21.4.2.9.2 Moving Through Microsoft Office

To move a content item through a Microsoft Office application (Word, Excel, PowerPoint, and so on):

  • Open a file from a folder, from the File menu, choose Save As, select a different folder, click OK, and close the file.

Moving a file to a different folder does not change the metadata. To apply the new parent folder's metadata, you can use the metadata propagation function. For more information, see Section 21.1.3.5, "Metadata Propagation."

21.4.3 Displaying Web Pages

You can access Content Server folder Web pages through Windows Explorer rather than through a Web browser.

21.4.3.1 Configuring Windows Explorer

To be able to display Web pages through Windows Explorer, the application must be set to display the full path in the title bar:

  1. In Windows Explorer, from the Tools menu, choose Folder Options.

  2. In the Folder Options window, click the View tab.

  3. Under Files and Folders, select the Display the full path in title bar check box.

  4. Click OK.

21.4.3.2 Displaying a Web Page

To display a content server Web page from Windows Explorer:

  1. Access the Web Folders folder in Windows Explorer. This folder is usually under My Computer.

    If the Web Folders folder is not displayed, access your folders under My Network Places. You might have to do this a few times for Web Folders to appear.

  2. In Windows Explorer, double-click the folder on the right for which you want to display the Web page.

  3. Click the Address bar at the top of the window.

  4. Press the Enter key.

    The exploring page for the folder opens.

PKPw-y-PKC_EOEBPS/downloading_oldui.htm#Fܹ Checking Out and Downloading Files

20 Checking Out and Downloading Files

This chapter describes how to check out one or more content items from Oracle WebCenter Content Server.

20.1 About Manual File Check-Out

Check-out is the process of locking a content item so that no other users can revise it. You must have write permission to the content item to check out a file or undo a check-out. Only one user at a time can check out a file; however, multiple users can continue to view the released file.

There are two approaches to checking out files manually:

  • For content items that could be revised by other users, it is a good idea to check out the file as soon as you know that you must edit it to prevent other users from checking in a new revision with potentially conflicting changes.

  • For content items that are unlikely to be revised by other users, you can make revisions to a copy of the file, check out the content item, and immediately check it back in with the edited file.

After you have checked out a content item, you can either check in a revision or undo the check-out.

You can check out files automatically through your desktop application by using Oracle WebCenter Content Desktop. For more information, see "Checking Out Content Files" in Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.

20.2 Checking Out Single Files

To check out single files from a Content Information page:

  1. Display the Content Information page of the content item you want to check out.

  2. Choose Check Out from the Content Actions menu.

  3. If applicable, on the Check-Out Confirmation page, click Native File Link to get a copy of the native file.

  4. If a dialog window opens before the Save As window, choose to save the file to disk.

  5. In the Save As dialog box, navigate to the location where you want to save the file, and click Save.

  6. Start the native application (for example, Word or PowerPoint) and locate the file where you saved it in Step 5.

  7. Edit the file in its native application and then save the file.

To check out single files from a Search Results Page:

  1. Search for content to view a search results list.

  2. Choose Headline View or Thumbnail View from the Content Actions menu.

  3. Click the Actions icon, and choose Check Out from the contextual menu.

  4. If applicable, on the Check-Out Confirmation page, click Native File Link to get a copy of the native file.

  5. If a dialog box opens before the Save As window, choose to save the file to disk.

  6. On the Save As window, navigate to the location where you want to save the file, and click Save.

  7. Start the native application (for example, Word or PowerPoint), and locate the file where you saved it in Step 6.

  8. Edit the file in its native application, and then save the file.

20.3 Using Check Out and Open

With the Check Out and Open component, you can open content items from Content Server directly in a WebDAV-compliant native application. The Check Out and Open component is enabled by default and adds the Check Out and Open option to the Item Actions menu on a Search Results page and to the Content Actions menu on a Content Information page. Before using Check Out and Open, verify with your system administrator what WebDAV-compliant applications are in use, and that the content item you are checking out is associated with a compliant application.

This section covers the following topics:

20.3.1 About Checking Out and Opening Content

When you check out and open a content item, the content item opens in its native application if the application is WebDAV-compliant (for example, Microsoft Word). You can edit the content item and check it back into Content Server using that application. Each time you save the content item in the native application, a new revision of the item is checked in to Content Server.


Important:

Pay close attention to the status of a content item you attempt to check out using Check Out and Open, both in Content Server and in the native application you are using to edit the file. If you open the file and notice that the title bar designates the file is read-only, you are prompted to save the file as a new item on a local file system.

A file is read-only if it is in a workflow process. As with a read-only file in a conventional file system, you can view the file or edit a copy as a new item. You cannot open a content item if it is checked out by another user.


Figure 20-1 Check Out and Open Option on Search Results Page

Graphic described in surrounding text

Figure 20-2 Check Out and Open Option on Content Information Page

Graphic described in surrounding text

20.3.2 Opening Content from Content Server

To open content from a Content Information page:

  1. Display the Content Information page of the content item you want to check out.

  2. Choose Check Out and Open from the Content Actions menu. The content item is checked out from Content Server transparently and opened in a WebDAV-compliant native application, such as Microsoft Word.

  3. Edit the content item, save the changes and close the file. The content is checked in to Content Server as a new revision.

To open content from a Search Results page:

  1. Search for content to view a search results list.

  2. Choose Headline View or Thumbnail View from the Content Actions menu.

  3. Click the Actions icon and choose Check Out and Open from the contextual menu. The content item is checked out from Content Server transparently and opened in a WebDAV-compliant native application, such as Microsoft Word.

  4. Edit the content item, save the changes and close the file. The content is checked in to Content Server transparently as a new revision.


    Note:

    The Check Out and Open options are available in the Content Actions menu of a content item's current revision only.


20.4 Checking Out Multiple Files

This section covers the following topics:

20.4.1 About Multiple File Check-Out

To get copies of multiple content items, use the download applet. When you download files, you also have the option to check out the content items and uncompress any compressed ZIP files.

20.4.2 Download Applet Requirements

You can use the download applet to check out multiple files if the following conditions are true:

The system administrator has enabled the download applet on Content Server.

  • You selected the Enable download applet check box in your User Profile page.

  • You are using a Java-enabled Web browser.

The download applet requires permission to access the local drive. When you run a search for the first time after enabling this applet, you may see a Java security warning:

  • If your system is using the Oracle Java plug-in, when you encounter this message box, click Run. If you do not want to be prompted again with this message box, select Always trust content from this publisher, then click Run.

  • If your system is using the Microsoft plug-in for Internet Explorer, click Yes to give full permissions. If you do not want to be prompted again with this message box, select Always trust software from Oracle Incorporated, and click Yes.

20.4.3 Download Options on Search Results Pages

When the download applet is enabled, it adds the following features to search results pages.

ElementDescription

Download

This link downloads the selected content items.

Select All check box

Selects all items in the search results list.

Select check boxes

Selects content items to be downloaded when you click the Download Selected button.


20.4.4 Downloading Multiple Files

To download and check out multiple content items using the download applet:

  1. Browse or search to locate the files to download. For more information, see Chapter 17, "Finding Documents."

  2. To download all content items on the Search Results page, click Download All.

  3. To download selected content items, select the corresponding Select check boxes, and click Download Selected.

  4. In the Download Files window, select the type of file to download: Web Viewable or Native.

  5. To uncompress ZIP files during the download process, select the Extract zip file contents check box.

  6. If you selected the Native option and you want to check out the content items upon download, select the Check out file check box.

  7. In the Download Location field, enter the path where you want the files to be copied. You can click Browse and navigate to the directory to select it.

  8. If you want a different file name for the downloaded file, change the file name in the Download Location field. This applies only to the current file. If you click Download All, all other files retain their default file names.

  9. Click a button:

    • Download: to download the current file only.

    • Download All: to download all selected files that have not been skipped (you are not prompted for each file that was selected).

    • Skip: to not download the current file and go to the next selected file.

    • Cancel: to cancel the download.

  10. If a file with the same file name exists in the target location, you are asked whether you want to overwrite it. Click a button to indicate whether you want to overwrite one or more files.

  11. In the Download Results Summary, click OK.

PK(F#FPKC_EOEBPS/digital_assets.htm Working with Images and Videos

24 Working with Images and Videos

This chapter describes how to use Oracle WebCenter Content Server to manage digital assets and quickly find, group, convert, and download images and videos of various sizes, formats, and resolutions.

This functionality is installed but disabled by default. Your system administrator chooses whether to enable this functionality for your site. The chapter covers the following topics:

24.1 About Digital Asset Management with Oracle WebCenter Content

Using Oracle WebCenter Content to manage digital assets enables you to quickly find, group, convert, and download images and videos of various sizes, formats, and resolutions to meet your business requirements, while maintaining a consistency of use across your organization. For example, an organization may have a logo in a variety of sizes for advertisements, Web pages, and presentation, or a training video in a variety of formats for streaming on an intranet, presenting to an audience, or copying to tape.

Work with your system administrator and other contributors to define the appropriate size and output. At check-in, the digital asset is automatically converted into the defined formats and sizes, known as renditions. You can then search for the asset using standard metadata or closed-caption text if it is a video asset. From the Rendition Information page you can add renditions to a digital asset basket and download a single compressed file that contains all of the renditions.

Figure 24-1 Overview

Graphic described in surrounding text

When enabled, the ability to manage digital assets adds the following pages to Oracle WebCenter Content Server:

The ability to manage digital assets also adds functionality to the Content Check-In, Content Information, Content Information Update pages, all search result pages, and the My Content Server tray.

The ability to manage digital assets enables you to create and find images and videos in specified formats and sizes. This helps your organization maintain consistent standards for branding and asset use, while providing the right content to the right people in the right format.

Managing digital assets allows you to create multiple formats of digital assets automatically when they are checked in to Oracle WebCenter Content Server, and lists the formats under one content ID. Digital assets, such as a corporate artwork or commercial videos, maintain a standard size and quality in each format required by your organization. The content management and workflow features of Oracle WebCenter Content Server uses only approved versions because assets are created from a single source managed by Oracle WebCenter Content Server.

Managing digital assets with Oracle WebCenter Content Server gives you the confidence that you are using the approved asset in the proper format. For example, an image of the logo in a format for use on a Web-site can be bundled and downloaded with other formats of the logo for use in office presentations or print collateral, all from a single digital asset checked in to Oracle WebCenter Content Server. Or, a low-bandwidth version of a training video can be posted to a streaming server while a high-bandwidth version can be provided to a vendor for replication to tape or DVD.

Each format created of a digital asset is called a rendition. Each image rendition includes information about size, color, format, and other criteria defined by your system administrator. Each video rendition includes information about display size, bandwidth, and expected use. Renditions are grouped into rendition sets. When you check in a digital asset, you choose a rendition set, which then determines what renditions are created for the asset. When finding a digital asset for use, all renditions of the asset are listed on the asset's Rendition Information page, and are available for download.

Figure 24-2 Example Image Rendition Set and Resulting Rendition Listing

Graphic showing image rendition

Figure 24-3 Example Video Rendition Set and Resulting Rendition Listing

Graphic showing video rendition set

24.2 Supported Input Formats

Supported input formats are determined by the graphic or video conversion application as set up by your system administrator.

Image Input Formats

Common image input formats include the following:

  • JPG/JPEG (Joint Photographic Expert Group)

  • GIF (Graphics Interchange Format)

  • BMP (Bitmap)

  • PNG (Portable Network Graphics)

  • TIFF (Tag Image File Format)

  • PSD (Adobe Photoshop)

  • AI (Adobe Illustrator)

  • PDF (Portable Document Format)

Image Video Formats

Common video input formats include the following:

  • Flash Media Format

  • MPEG Layer 3 and 4 Elementary Stream Media Format

  • PacketVideo MPEG4 Format

  • QuickTime Media Format

  • QuickTime Streaming Format

  • Windows Media Format

  • AVI Media Format

  • DVD Stream Media Format

  • MPEG1 System Stream Media Format

  • MPEG2 Program Stream Media Format

  • MPEG2 Transport Stream Format

  • MPEG4 Media Format

  • Pinnacle MediaStream Media Format

For a comprehensive listing of supported format, see the conversion application documentations.

Formats supported by the conversion application must also be associated with the conversion process within Oracle WebCenter Content Server by the system administrator using the Oracle WebCenter Content Server Configuration Manager. If a supported format is not rendering, see your system administrator.

24.3 Supported Video Output Formats

Output formats are limited to what your browser displays effectively. Only output formats supported by Windows Media Player, Real Player, Flash Player, or Quicktime Player are available for viewing in your Web browser. Any assets rendered in a format not supported by those players is still be managed by Oracle WebCenter Content Server, but is available only for download only.

Oracle WebCenter Content currently supports the following video output formats:

  • MPEG Layers 1, 2, and 4 (.mpg, .mpeg, .mp2, .mp4)

  • Quicktime (.mov)

  • Audio Video Interleave (.avi)

  • Flash Video (.flv)

Other output formats not listed here but supported by your media player may work when set up properly by your system administrator. For additional format requests, see your system administrator. For information on formats supported by your media player, see the player's help system.

24.4 Checking In a Digital Asset

When the ability to manage digital assets is added to Oracle WebCenter Content Server, the Rendition Set list is displayed on the content check in form.

Figure 24-4 Content Check-In Form with Rendition Set List

Graphic showing rendition option on check in

To check in a digital asset, perform these steps:

  1. Open the content check-in form.

  2. Choose a rendition set from the Rendition Set list.

  3. Enter a title and any additional metadata for the asset. The title you enter must be 249 or fewer characters in length.

  4. Click Browse to locate the primary file.

  5. Click Check In.

Oracle WebCenter Content Server uses the file extension, such as .psd, .jpg, .mov, or .avi, to determine if an item is a digital asset. Digital assets checked in to Oracle WebCenter Content Server must have the correct file extension appended to the file name. For example, a Photoshop file named CorporateLogo.psd is correctly identified by Oracle WebCenter Content Server as a digital asset, but one named CorporateLogo is not.

Do not select an alternate file when checking in a digital asset. Doing so prevents the primary file from rendering.

24.5 Finding Renditions and Information

Searching for digital assets is identical to searching for other types of content. Digital assets have an additional icon displayed in the standard Search Result page. The Rendition Information icon links to the Rendition Information page of the asset.

Figure 24-5 Search Result Page with Rendition Information Icon

Graphic showing rendition icon on results page

Because you are working with images and videos, you may want to set your default search result view to Thumbnail View. To do so, choose Thumbnail View from the Content Actions menu on a Search Result page.

Figure 24-6 Thumbnail View Search Result Page.

Graphic showing thumbnail view for results page

24.6 Rendition Information Page

When a digital asset is checked in to Oracle WebCenter Content Server, multiple renditions are created based on the rendition set chosen at the time of check-in. Just like with standard content, information about the original content item is indexed and displayed on the Content Information page. However, with a digital asset, information about the created renditions is also displayed on the Rendition Information page, and on the story board and any closed-captioned text for video assets.

To access the Rendition Information page, click the associated link on the Content Information page, or from a search result page using the Rendition Information icon or the Rendition information link in the item Actions menu.

Accessing The Rendition Information Page

To access the Rendition Information page of a digital asset from any page in Oracle WebCenter Content Server, perform one of these steps:

  1. Search for the digital asset for which to view rendition information.

  2. Click the Rendition Information icon next to the appropriate digital asset on a Search Result page, or choose Rendition Information from the item Action menu.

Alternately, you can access the Rendition Information page from the digital asset basket by performing these steps:

  1. Click the My Content Server tray, click My Baskets, and then click Digital Asset Basket.

  2. Click the Rendition Information icon next to the appropriate digital asset in your digital asset basket.

When the Rendition Information page opens, click the tabs at the top of the page to switch between the Content Information page, the Rendition Information page, and the Image Data page for the asset.

24.7 Image Data Page

The Image Data page displays information about the native image file checked in to Content Server. However, what that information is and how it is displayed is contingent on:

  • The specific information the camera or application captures, and

  • Whether the image is generated by a digital camera or an application (such as Photoshop).

Image Information

The specific information that is displayed is dependent on the type of camera or application used to generate the image. Different digital cameras collect different information, depending on the camera features and capabilities.

Additionally, one camera might have a built-in GPS system and can record GPS coordinates into the image file. Another camera might not have that capability, and so wouldn't be able to output that information to the Image Data page. Similarly, an application such as Photoshop may generate information specific to its feature set while Paint Shop Pro would generate different information specific to its different feature set.

Display Formats

How the information is displayed on the Image Data tab is dependent on whether the native image file is a JPEG from a digital camera or if it is from an application. Digital cameras store information using the EXIF standard (Exchangeable Image File format), which is a subset of the XMP standard (Extensible Metadata Platform). Both methods use the Oracle Outside In filters to generate XML to structure the data.

If the image is a JPEG from a digital camera, Outside In specifies the document type as JPEG File Interchange, and the EXIF data is displayed on the Image Data tab in a flat listing. If the image is from an application such as Adobe Photoshop, Outside In specifies the document type as coming from the application (for example, document type="Adobe Photoshop"), and the XMP data is displayed on the Image Data tab with some hierarchical structure.


Note:

If the image is a digital photograph that has been manipulated in Photoshop, the EXIF data gets aggregated and formatted as part of the XMP data, because EXIF is a subset of XMP.


Figure 24-7 shows the contents of the Image Data tab for a checked in digital photo. In this case, the information includes the image thumbnail and the photo's digital properties.

Figure 24-7 Image Data Page of a Digital Photo

Graphic of image data page

Figure 24-8 shows the contents of the Image Data tab for a Photoshop document with the XMP data displayed in a hierarchy.

Figure 24-8 Image Data Page of a Photoshop Image

Graphic of Photoshop image data page

Accessing the Image Data Page

To access the Image Data page of a digital asset from any page in Oracle WebCenter Content Server, perform one of these steps:

  1. Search for the digital asset for which to view rendition information.

  2. Navigate to either the Rendition Information page or the Content Information pages, and click the Image Data tab

  3. Click the Image Data tab.

Alternately, you can access the Image Data page from the digital asset basket by performing these steps:

  1. Click the My Content Server tray, click My Baskets, and then click Digital Asset Basket.

  2. Click the Rendition Information icon next to the appropriate digital asset in your digital asset basket.

When the Image Data page opens, click the links at the top of the page to switch between the Content Information page, the Rendition Information page, and the Image Data page for the asset.

24.8 Rendition Parameters Page

To access the Rendition Parameters page, click the Rendition Name Information icon next to a rendition name on the Rendition Information page.

If an image rendition fails, the format column in the Renditions section of the Rendition Information page displays Not Converted for that rendition. In the case of a failed rendition, the Rendition Parameters page displays information about the cause of the failure.

Figure 24-9 Example of an image Rendition Parameters page.

Graphic of Image Rendition Parameters page

Figure 24-10 Example of a Video Rendition Parameters Page.

Graphic of video rendition parameters page

Accessing The Rendition Parameters Page

To access the parameters of each specific rendition, perform these steps:

  1. Access the Rendition Information page.

  2. Click the Rendition Name Info icon.

24.9 Video Preferences Page

To play a video rendition, use the preview section of the Rendition Information page or click a Web-viewable link on the Content Information, digital asset basket, or Search Result pages. Oracle WebCenter Content determines what format to use as the default for the preview window based on information you specify on the Video Preferences page. You can also specify the number of keyframes displayed in the storyboard on the Rendition Information page, and your preferred bandwidth for the preview.

Other features of the Video Preferences page enable you to specify a video player for each rendition format and to set a No Player Option and a No Format Option for both that affect the preview display on the Rendition Information Page. To open and play renditions in a standalone player, click the rendition name in the rendition section of the Rendition Information page. The player chosen is then determined by file format and helper application settings unique to your computer and browser, outside of Video Manager.

Graphic of video preferences page

Accessing the Video Preferences Page

To access the Video Preferences page, perform these steps:

  1. Access the Rendition Information page, or click the My Content Server tray.

  2. Click Video Preferences.

    Page ItemDescription

    Video Format Preference Order

    Specifies the preferred media format used in the Rendition Information page preview section for renditions, and with a rendition's Web-viewable link in a search result, digital asset basket, or content information page. Because a rendition set may not have a rendition in the preferred format, Video Manager plays the rendition using the first available format found in the order listed here.

    The NoPlayer option enables you to suppress one or more of the media formats here, depending on your preference. The placement of the NoPlayer option determines what media format is available. For example, if you move the NoPlayer option immediately following WindowsMedia, then all other formats are ignored. For more information, see Section 24.9.1, "No Format Option."

    Move Up

    Moves a selected media format up in the preference order.

    Move Down

    Moves a selected media format down in the preference order.

    Video Bandwidth Preference

    Specifies the preferred size of streaming and local videos by using the size information from the rendition listing.

    Low: Smaller video best suited when connecting to Video Manager using a modem to dial in.

    High: Larger video best suited when connecting to Video Manager through a high speed connection, such a corporate network or broadband internet connection.

    Max Keyframe Segment Length

    Specifies the maximum number of keyframes displayed at each drill-down level in the storyboard section of a Rendition Information page.

    Player Preference By Format

    Enables you to specify a video player for each media format included in the list. For more information, see Section 24.9.2, "No Player Option."

    Update

    Submits changes made to the Video Preferences page.


24.9.1 No Format Option

Depending on what priority you have assigned to the No Format option in the Video Format Preference Order section on the Video Preferences Page, the preview area of the Rendition Information Page may or may not display the video preview player. For example, the following graphic illustrates that this rendition set does not contain any preferred video format. That is, all formats available in this set appear below the No Format option in the Video Format Preference Order which means that they have been suppressed.

Graphic showing No Format option

24.9.2 No Player Option

The Player Preference By Format section of the Video Preferences Page enables you to set a video player for each media format included in the list. For example, if you set the preference for Quicktime to be No Format, then this option suppresses that format in the preview area of the Rendition Information Page as illustrated in the following graphic. Click Access this rendition directly to open a new window and play the video using the applicable default player.


Note:

The No Format Option placement always overrides the selected settings for media formats listed in the Player Preference By Format section.


Graphic showing No Player option

24.10 Working with Renditions

The ability to manage digital assets not only creates renditions automatically, it provides a personal space where you can store renditions you are currently working on, called the digital asset basket. Your digital asset basket is unique to you, and contains only the renditions you choose to include.

You can add items to your digital asset basket from a Search Result page, from the Rendition Information page, or from the Content Information page. To view the items in your digital asset basket, click My Baskets and then Digital Asset Basket in the My Content Server tray.

By design, the digital asset basket can contain renditions from different revisions of the same digital asset. If you use your basket to quickly find a rendition of an asset, such as a corporate logo or video, remember that you may not be accessing the most recent revision of the asset. If a newer revision has been checked in to Oracle WebCenter Content Server, a notification is displayed next to the revision number in the Description column. Click the notification to display the Content Information page of the latest revision.

You can do the following tasks with renditions:

24.10.1 Storing Renditions in Your Digital Asset Basket

You can store any rendition from any revision of a digital asset in your digital asset basket, and the Web-viewable or native file from any revision of a content item, provided the revision is released by Oracle WebCenter Content Server.

From the digital asset basket, you can select renditions from one or multiple assets to be compressed into a single file and downloaded to a local or networked drive, or send links to selected renditions in an e-mail. You can also use the digital asset basket to access the content information and rendition information pages of content items and digital assets.

You can add items to your digital asset basket from the following pages:

  • Rendition Information page (native file and all renditions)

  • Content Information page (native and Web-viewable files only)

  • Search Result page (native and Web-viewable files only)

When you add a rendition to the digital asset basket, it may not be listed at the top of the digital asset basket page. Items in the digital asset basket are listed in descending order first by content ID and then by revision number. If a rendition of a content item revision is in the digital asset basket, additional renditions are added to that revision's listing. Additionally, if a newer revision of a content item in your digital asset basket has been checked in to Oracle WebCenter Content Server, a notification is displayed next to the revision number in the Description column. Click the notification to display the Content Information page of the latest revision.

To add renditions to your digital asset basket from the Rendition Information page, perform these steps:

  1. Access the rendition information page of an asset.

  2. On the Rendition Information page, select the check box next to a rendition to add the rendition to your digital asset basket.

  3. From the Renditions list, choose Add to Basket. The Digital Asset Basket page opens with the renditions you selected listed in the Selected Renditions column of the item.

To add all renditions to your digital asset basket, select all items. You do not have to select the check box next to any rendition if using this option.

To add the native or Web-viewable file to your digital asset basket from the Content Information page:

  1. Access the Content Information page of an item.

  2. From the Content Actions menu, choose one of these:

    • Add Native File to Digital Asset Basket

    • Add Web-Viewable File to Digital Asset Basket

The Digital Asset Basket page opens with the selected items listed in the Selected Renditions column of the item.

You cannot add both the native file and the Web-viewable file to the digital asset basket at the same time using the Content Information page. If the item is a digital asset and has a Rendition Information page, use it to add multiple items to the digital asset basket at the same time.

To add the native or Web-viewable file to your digital asset basket from a Search Result page:

  1. From a Search Result page, select the check box next to the item or items you want to add to your digital asset basket.

  2. From the Content Actions menu, choose either of these items:

    • Add Native Files to Digital Asset Basket

    • Add Web-Viewable Files to Digital Asset Basket

    The Digital Asset Basket page opens with the selected items listed in the Selected Renditions column of the item.

To add all native or Web-viewable items on a Search Result page to your digital asset basket, choose All from the Select menu. You do not have to select the check box next to any item if using this option. Also, Web-viewable files of video renditions added to the digital asset basket are suitable for viewing only from the digital asset basket. You cannot download them from the digital asset basket. To download a rendition, use the Rendition Information page.

24.10.2 Viewing Items in Your Digital Asset Basket

To access the digital asset basket, click My Basket and then Digital Asset Basket in the My Content Server tray. From the digital asset basket, you can select renditions from one or multiple assets to be compressed into a single file and downloaded to a local or networked drive, or send links to selected renditions in an e-mail. You can also use the digital asset basket to access the content information and rendition information pages of content items and digital assets.

To access the Digital Asset Basket page, perform these steps:

  1. Click the My Content Server tray.

  2. Click My Baskets.

  3. Click Digital Asset Basket.

Digital Asset Basket Page

Graphic of digital asset basket page
Page ItemDescription

Thumbnail

Opens the Web-viewable rendition in a separate window. Your system administrator specifies the Web-viewable rendition. It is typically larger than the thumbnail or preview renditions. For video assets, you determine the Web-viewable rendition based on the choices you make on the Video Preferences Page.

Description

Title, native file, Content ID, and Revision metadata of the content item.

If a newer revision of the content item has been checked in to Oracle WebCenter Content Server, a notification is displayed next to the revision number. Click the notification to display the Content Information page of the latest revision.

Selected Renditions

Listing of all renditions of a content item saved to the digital asset basket.

Content Info icon

Links to the Content Information page of an item.

Rendition Info icon

Links to the Rendition Information Page of an item.

Items menu

  • Download: Bundles the selected items into a single compressed file and copies the file to a local or networked storage space.

    Web-viewable files of video renditions added to the digital asset basket are suitable for viewing only from the digital asset basket. You cannot download them from the digital asset basket. To download a rendition, use the Rendition Information Page.

  • E-mail Links: Opens a prompt that enables the user to enter one or more e-mail addresses. Then the e-mail is generated and sent from within the server, after which a confirmation page is shown that displays the format of the e-mail. The URL links to the selected items are copied into the body of a new message.

  • Remove: Removes the selected items from the digital asset basket.

  • Empty Basket: Removes all items from the digital asset basket.


Items in the digital asset basket are listed in descending order first by content ID and then by revision number. If a rendition of a content item revision is in the digital asset basket, additional renditions are added to that revision's listing.

24.10.3 Removing Items from Your Digital Asset Basket

Because you can store renditions from different revisions of a digital asset in the digital asset basket, renditions listed in the digital asset basket are not necessarily the latest revision. It is a good idea to remove the renditions from your digital asset basket when you no longer require them.

You can store a link to the most recent revision of any content item in Oracle WebCenter Content Server by searching for the item's content ID, then choosing Save Search from the Content Actions menu on the search result page. The link is saved in the My Saved Queries folder in your My Content Server tray. Click the saved search link to always access the most recent revision of a content item.

To remove individual renditions from your digital asset basket:

  1. Click the My Content Server tray, click My Baskets, and then click Digital Asset Basket.

  2. Select the check box next to the renditions to be removed in the Selected Renditions column on the digital asset basket page.

  3. Choose Remove from the Items menu.

    The items are removed from the digital asset basket.

To remove all items from your digital asset basket:

  1. Click the My Content Server tray, click My Baskets, and then click Digital Asset Basket.

  2. Choose Empty Basket from the Items menu.

    All items in the digital asset basket are removed. You do not have to select the check box next renditions when removing them all from your basket.

Removing renditions and other items from your digital asset basket does not remove them from Oracle WebCenter Content Server. You can remove renditions and other items from Oracle WebCenter Content Server using the Rendition or Content Information pages. Renditions and other items listed in your digital asset basket are not available if they have been removed from Oracle WebCenter Content Server.

24.10.4 Adding and Removing Renditions in a Rendition Set

The ability to manage digital assets automatically creates multiple renditions of digital assets and manages them in Oracle WebCenter Content Server under one content ID. Oracle WebCenter Content provides the content management and workflow benefits of Oracle WebCenter Content Server while ensuring that you have access to all the types of renditions you need. One content ID provides single-point access to all items relevant to the digital asset.

In some situations, you may want to associate an additional rendition or other file to a digital asset, or remove a rendition that is no longer useful. For example, you may need a rendition that is a slightly different size than the one created by the rendition set, or uses a different color palette, so you want to add the new one and remove the old one. Or, you may have a text file with instructions to a vendor on how they are to use a logo. Files such as these can be added to a digital asset's existing set of renditions using the Add a Rendition page, accessed from the Rendition Information page, and removed directly from the Rendition Information page.

Add a Rendition Page

You can access the Add a Rendition page from the Renditions menu on the Rendition Information page of an asset. An added rendition is assumed to be a graphic file, and metadata fields on the Add a Rendition page allow you to manually add information pertinent to graphic renditions. Added renditions can be any type of file, however. For example, if you have a text file with instructions on how to output a PDF file, you can attach the text file as a rendition of the original asset. You should note, though, that Oracle WebCenter Content Server does not manipulate added renditions. It does not modify a rendition based on information entered into the metadata fields, nor does it convert an added rendition to a Web-viewable format, nor index it for searching.

  • Metadata on the Add a Rendition page is for information only. It does not change the size of an added graphic file, and it does not get indexed for searching.

  • You can add any type of file as a rendition. It does not have to be a graphic file. To view added renditions, you must have the native application or suitable viewer for the added rendition's file format.

To add a rendition to an existing rendition set:

  1. Access the Rendition Information page.

  2. Choose Add New Rendition from the Renditions menu.

  3. On the Add a Rendition page, enter a name for the rendition in the Name field (required). The name is displayed in the Rendition Name column of the Rendition Information page.

  4. Enter a description for the rendition in the Description field (optional). To display the description, click the Rendition Name Description icon in the Rendition Name column of the Rendition Information page.

  5. Click Browse to locate the rendition or other file you want to add to the rendition set (required). You can select any type of file.

  6. Fill in the pixel dimensions and resolution information in the Width, Height, and Resolution fields (optional).

  7. Click Add Rendition.

    Metadata on the Add a Rendition page is for information only. It does not change the size of an added graphic file, and it is not indexed for searching.

To delete a rendition from an existing rendition set:

  1. Access the Rendition Information page.

  2. Select the check box next to the rendition you want to delete. You can select multiple renditions to delete.

  3. Choose Delete from the Renditions menu.

    Renditions and other items are not available if they have been removed from Oracle WebCenter Content Server. When you delete a rendition from the system, it disappears from the basket display.

24.10.5 Downloading Multiple Items

You can compress renditions and other content items into a single file and downloaded to a local or networked drive, for example, when you want to send multiple renditions or native files to others. You can do this from the Digital Asset Basket page or Rendition Information page.

To download multiple renditions:

  1. Access the digital asset basket or Rendition Information page.

  2. Select the check box next to the renditions you want to download. The renditions are listed in the Selected Renditions column of the Digital Asset Basket page, or the Rendition Name column of the Renditions Information page.

  3. Choose Download from the Renditions menu on the Rendition Information page or from the Items menu on the Digital Asset Basket page.

  4. Follow the download instructions as they are displayed on screen.


Notes:

  • To download all renditions in your digital asset basket, or on the Rendition Information page, select all items, and then choose the Download menu option. You do not have to select the check box next to any rendition if using this option.

  • Web-viewable files of video renditions added to the digital asset basket are suitable for viewing only from the digital asset basket. You cannot download them from the digital asset basket. To download a rendition, use the Rendition Information page.

  • You can remove renditions and other items from Oracle WebCenter Content Server using the Rendition or Content Information pages.


24.10.6 Creating Renditions

Renditions are created automatically when a digital asset is checked in. The types of renditions created are determined by criteria defined in the selected rendition set.

To create renditions:

  1. Access the Content Check-In Form.

  2. Choose a rendition set from the Rendition Set list.

  3. Enter a title and any additional metadata for the asset. The title you enter must be 249 or fewer characters in length.

  4. Click Browse to locate the primary file.

  5. Click Check In.

Notes

  • Oracle WebCenter Content Server uses the file extension, such as .psd, .jpg, .mov, or .avi, to determine if an item is a digital asset. You must append the correct extension to the file name for all digital assets checked in to Oracle WebCenter Content Server. For example, a Photoshop file named CorporateLogo.psd is correctly identified by Oracle WebCenter Content Server as a digital asset, but one named CorporateLogo is not.

  • Do not select an alternate file when checking in a digital asset. Doing so prevents the primary file from rendering.

24.10.7 Updating Renditions

If an incorrect rendition set was selected when a digital asset was checked in, or if a new rendition set has been created, you may want to update the renditions created for a digital asset.

To update to a different rendition set, perform these steps:

  1. Choose Update from the Content Actions menu on the Content Information page.

  2. Choose a different rendition set from the Rendition Set list.

  3. Click Submit Update.

Notes

  • You cannot display rendition information while an asset is being processed by Oracle WebCenter Content Server. If an asset is being processed, the status in the revision history on the Content Information page is GenWWW, and the Rendition Information page displays a message saying the content item is not released yet.

  • Updating a rendition set replaces the previous renditions with a new set, effectively removing the previous set from Oracle WebCenter Content Server.

24.11 Working with Standard Content Items

The ability to manage digital assets adds functionality to Oracle WebCenter Content Server that extends to content items that are not digital assets. You can add native and Web-viewable versions of content items to your digital asset basket, and add or delete attachments to content items from the Content Information page.

Add/Edit Attachments

In some situations, you may want to associate an additional rendition or other file to a content item that is not a digital asset, or remove an attachment that is no longer useful. For example, you may attach a customer's new logo to a piece of collateral that uses it and remove the old one, or you may attach a text file with project contact information to a project plan. You can add files such as these to a content item using the Add/Edit Attachments page, accessed from the Content Actions menu on the Content Information page. Attached files are not converted to a Web-viewable format, and are not indexed for searching by Oracle WebCenter Content Server.

Figure 24-11 Adding or Editing an attachment with the Edit Attachments page

Image of Edit Attachments page
Page ItemDescription

Attachment column

Lists the name given to an existing attached file at the time it was attached.

Description column

Lists the description given to an existing attached file at the time it was attached.

Name field

Used to enter the name of the file to be attached. Displayed in the Attachments section of the Content Information page.

Description field

Used to enter the description of the file to be attached. Displayed in the Attachments section of the Content Information page.

File field

Used to locate the file to be attached.

Add/Edit Attachment Button

Submits the information to Oracle WebCenter Content Server.


To add an attachment to a content item:

  1. Access the Content Information page.

  2. Choose Add/Edit Attachments from the Content Actions menu.

  3. On the Add/Edit Attachments page, enter a name for the attachment in the Name field (required). The name is displayed in the Attachments section of the Content Information page.

  4. Enter a description for the rendition in the Description field (optional). The description is displayed in the Attachments section of the Content Information page.

  5. Click Browse to locate the rendition or other file you want to attach to the content item (required). It can be any type of file.

  6. Click Add/Edit Attachments.

    Metadata on the Add/Edit Attachments page is for information only. It does not get indexed for searching.

To delete an attachment from a content item:

  1. Access the Content Information page.

  2. Choose Add/Edit Attachments from the Content Actions menu.

  3. On the Add/Edit Attachments page, select the check box next to the attachment you want to delete. You can select multiple attachments to delete.

  4. Click Edit Attachments.

24.12 Managing Digital Assets on a Macintosh Client

Oracle WebCenter Content Server renders digital assets when checked in using a Macintosh client provided the file name of the asset has a valid file extension. However, files created on Macintosh operating systems before OS X may have information stored in a file resource fork. Information in a resource fork may include custom fonts used by the file and is not transferred.

Depending on your organization's requirements, removing the resource fork generally does not create a problem. One exception to this is if the asset uses custom fonts and the rendition set includes a PDF rendition.

PK]PKC_EOEBPS/whatsnew.htm  What's New and Changed in This Guide

What's New and Changed in This Guide

The following topics introduce the new and changed features of Oracle WebCenter Content and other significant changes that are described in this guide, and provides links to additional information.

New and Changed Features for 11g Release 1 (11.1.1.8.0 MLR3)

11g Release 1 (11.1.1.8.0 MLR3) includes the following new and changed features:

  • Workflow support has been added to the Oracle WebCenter Content user interface, allowing for workflow assignment notifications in the banner and a streamlined review process. Using the Oracle WebCenter Content user interface you can now approve, reject, check out to edit, or check in workflow items assigned to you from a search result list or while viewing a document.

New and Changed Features for 11g Release 1 (11.1.1.8.0)

11g Release 1 (11.1.1.8.0) includes the following new and changed features:

  • Oracle WebCenter Content User Interface: This newly developed way of accessing documents offers an easy and intuitive user interface with drag-and-drop convenience and sophisticated searching capabilities. It offers a simple way to store, secure, retrieve, and share any type of document. See Part II. Note that the feature-rich native 11g user interface is still supported for those who need to manage rich media beyond traditional office documents, including images, records, and videos. For more information see Part III.

  • Support for Mobile Devices: Oracle WebCenter Content now offers apps for your Apple iPad, iPhone, or Android phone or tablet, allowing you to work securely where and how you want. See Chapter 27.

PKD PKC_EOEBPS/downloading_newui.htm j Checking Out and Downloading Documents

12 Checking Out and Downloading Documents

This chapter describes how to check out and download one or more documents from Oracle WebCenter Content so they can be revised, as well as downloading copies of documents. It has the following sections:

12.1 About Checking Out and Downloading Documents

You check out a document to lock it so that no other users can revise it. Only one user at a time can check out a file, but multiple users can continue to view the released document even when it is checked out. After checking out a document, you must either check in a new revision or undo the check-out before the document can be revised again. You must have write permission to the document to check it out or check in a revision. To undo a check-out, you must be the person who has the document checked out or have admin permissions to the document.

12.2 Checking Out Documents

You check out a document to lock it while you make changes. To check out a document, select a document then select Check Out from the More menu on either the Find Documents or View Documents page, or select Check Out from the contextual menu on the Find Documents page.

12.2.1 Checking Out and Editing a Document

If a document is not checked out and you have an application capable of using this feature, then you can check it out and open it up in the application for editing. The application must be WebDAV-compliant and able to edit the native file format. If you are uncertain if the application you have is WebDAV-compliant, check with your system administrator. For more detailed information about using this feature, see Section 20.3.

To check out and edit a document:

  1. Select Check Out and Edit from the More menu on the View Documents page. The document is checked out and opened in the native application for editing.

  2. Once you have revised the document, close the document and save changes. The new document is automatically checked into Oracle WebCenter Content as a new revision.

12.3 Downloading Documents

You download a document to copy a version to a file system. A copy can be the native file version, a web-viewable rendition, or an annotated version. You need read permission to download a document.

Some reasons you might download a document:

  • To edit the document after you check it out

  • To send a copy to someone else

  • To review a document when not connected to Oracle WebCenter Content, for example while traveling

  • To compare different revisions

12.3.1 Downloading Native Files

To download a copy of a document in its native file format:

  1. Do one of the following:

    • Click Download on the View Documents page.

    • Click Native File on the summary tab of the Properties section of a specified revision on the View Documents page.

    • Select Download from the More menu on a Find Documents page.

    • Click the document size on the Find Documents page when in List view.

  2. When prompted, navigate to where you want the file stored and save the file.

12.3.2 Downloading a Web-Viewable Rendition

To download a web-viewable rendition of a document:

  1. Right-click Web-Viewable on the summary tab of the Properties section of the View Documents page and select the appropriate option from the contextual menu for saving the file.

  2. When prompted, navigate to where you want the file stored and save the file.

12.4 Checking Out and Downloading Documents from WebCenter Content: Desktop

Oracle WebCenter Content: Desktop provides quick access to Oracle WebCenter through a standard Microsoft Windows files system or through Microsoft Office products such as Outlook and Word. When integrated with Oracle WebCenter Content: Desktop, files can be checked out automatically and downloaded through your desktop application. For details on using the full range of features available in Oracle WebCenter Content, see Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.

12.5 Checking Out and Downloading Documents from a Mobile Device

Documents can be downloaded from Oracle WebCenter Content using your Apple iPad, iPhone, or Android device for review when you are not online, or for sending to others. For more information, see Oracle Fusion Middleware Using Oracle WebCenter Content on Mobile Devices.

PK?N PKC_EOEBPS/part_oldui.htm Using the Native 11g User Interface with Oracle WebCenter Content

Part III

Using the Native 11g User Interface with Oracle WebCenter Content

The Oracle WebCenter Content native 11g user interface is feature-rich and offers a familiar user experience for those who need to manage rich media beyond traditional office documents, including images, records, and videos.

This part contains the following chapters:

PKc  PKC_EOEBPS/viewing_newui.htm. Viewing Documents

10 Viewing Documents

The WebCenter Content user interface has the ability to view documents directly in a standard browser next to the document properties. Single and multipage documents, revisions, and metadata can all be easily viewed without leaving the WebCenter Content user interface.

This chapter has the following sections:

10.1 About Viewing Documents

Oracle WebCenter Content converts many document formats to versions that are displayed on the Document page within a standard web browser. This means that even if someone does not have the native software that created a document, they can still view and share the document. In addition to viewing documents, a variety of additional tasks can be done from the Document page, which has the following main sections:

  1. Banner Section

  2. View Area

  3. Properties Section

Figure 10-1 Oracle WebCenter Content Document Page

Document View Page

10.1.1 Banner Section

The banner section lets you do these tasks:

  • File an unfiled document or view the path to a filed document's location in the context of Oracle WebCenter Content

  • Mark a document as a favorite

  • View links to the document

  • Check in new revisions of documents

  • Access more tasks from the More menu

  • Log out of Oracle WebCenter Content

10.1.2 View Area

Depending on the document format and how your system is configured, Oracle WebCenter Content converts uploaded documents into formats that are viewable using a standard web browser or document viewer. If your system can display a viewable rendition of the document, it is displayed in the preview area. It provides a toolbar for these tasks:

  • Going to specific pages

  • Zooming the page view

Certain types of documents provide additional viewing and navigation tools, if enabled. The side of the view area can expand to display thumbnail images of the document pages which can also be used to navigate to specific pages.

10.1.3 Properties Section

The properties section displays a summary of document properties with the option to display all properties, including security metadata. From the document properties area you can do these tasks:

  • Download a copy of the native file

  • View or download any generated rendition

  • Add attachments to the document

  • View and edit metadata and security properties

  • View workflow details of documents in a workflow and check in, approve, or reject items assigned to you.

10.2 Viewing Documents on the Document Page

Documents can be accessed from the Find Documents Page and viewed on the View Documents Page. How to access the documents depends on if the results list is set to display as List, Thumbnail, or Tabular:

  • If set to List or thumbnail, click either the thumbnail or document name to view the document

  • If set to Tabular, click the View icon or document name to view the document

10.3 Changing the Document View

The View Documents page toolbar allows you to change how a document is displayed in the view area. Using the toolbar, you can:

  1. Navigate multipage documents

  2. Increase or decrease the display size of the document

Additionally, the side pane of the view area can expand to display thumbnail images of each page of the document. Click a page in the thumbnail pane to go to that page.

Figure 10-2 Oracle WebCenter Content Document Page Toolbar

Graphic showing document page toolbar

10.4 Viewing Alternate Renditions

Alternate renditions are available for most documents when converted to HTML dynamically or when converted to some other web-viewable format at the time a document is uploaded. Dynamic conversions are not available for some native document formats, and also must be converted each time you select it. Web-viewable renditions are typically available for a wide range of native document formats and are converted once when a document is uploaded.

Dynamic conversions of documents can be viewed in a standard web browser outside of the View Documents page by:

  • Selecting View Dynamic Conversion from a contextual menu. To access the contextual menu, right-click a document in a results list.

  • Clicking Dynamic Conversion under the Renditions area in the Properties section of a View Documents Page.

Figure 10-3 Contextual Menu from Search Page

Contextual Menu

Web-viewable renditions of documents can be viewed in a standard web browser outside of the Document page by:

  • Selecting View Web Rendition from the list toolbar menu. To access the list toolbar menu, select a document in a results list.

  • Clicking Web-Viewable under the Renditions area in the Properties section of a View Documents page.

Rendition area of Summary Tab in Properties section

10.5 Viewing the Native File

If you have the software to open a native version of a document, you can download a copy and view it using the native software by clicking Native File in the Renditions area on the Summary tab of a View Documents page. See Chapter 12 for information on downloading a document.

10.6 Viewing Previous Document Revisions

The view area of the View Documents Page provides access to all previous revisions of a document. Revision numbers are listed above the View Documents page toolbar. Clicking a revision number displays that revision of the document in the view area and the metadata of that revision in the document properties section.

Figure 10-4 Revision Tabs in Document View

Revision Tabs in Document View

10.7 Using Links

Links to view a document can be easily shared with others. If a person does not have rights to view a document, it remains secure and is not displayed. Document links can be displayed in these ways:

  • Clicking the Link icon in the View Documents page banner section

  • Selecting Get Links from the More menu in the View Documents page banner area

  • Clicking the Get Links icon in the results list toolbar on the Find Documents page

  • Right-clicking a document in a results list and select Get Link from the contextual menu

Links can also be displayed for folders and libraries.

PK-z`I..PKC_EOEBPS/understanding.htm Understanding Content Management

3 Understanding Content Management

This chapter describes basic concepts of content management, including definitions of unstructured content, unfiled documents, uploading, checking in, checking out, revisions, revision history, and document metadata properties. It has the following sections:

3.1 Managing Unstructured Documents

Unstructured documents are all the documents, files, e-mails, memos, images, videos, slide presentations or other work product that fill your inbox and clutter your desk. Filing them in a drawer or letting them sit in your e-mail might get them out of your way, but often they are filled with critical information. Oracle WebCenter Content allows you to take those documents and the information they contain and organize them, making them easy to find, access, and share.

3.2 Understanding Uploading, Checking In and Checking Out Documents

To organize unstructured content, you upload documents to Oracle WebCenter Content. Many times a document that has been uploaded to Oracle WebCenter Content needs to be revised. Oracle WebCenter Content controls access and tracks changes to documents, providing access to a history of document revisions.

3.2.1 Uploading Documents

Uploading is the process of getting new documents into Oracle WebCenter Content. You can upload an electronic file by browsing a file system or upload a physical document by scanning it in. Documents are uploaded into the context of a library or folder already set up in Oracle WebCenter Content. When it is uploaded, the document is assigned information, or metadata, that is associated with the folder or library. The metadata becomes the document properties, and can be used to find documents in Oracle WebCenter Content.

3.2.2 Checking Out Documents

Check-out is the process of locking a document so that no other users can revise it. Only one user at a time can check out a file; however, multiple users can continue to view the released file. There are two approaches to checking out files manually:

  • For content items that could be revised by other users, it is a good idea to check out the file as soon as you know that you must edit it to prevent other users from checking in a new revision with potentially conflicting changes.

  • For content items that are unlikely to be revised by other users, you can make revisions to a copy of the file, check out the content item, and immediately check it back in with the edited file.


    Note:

    You must have write permission to the document to check it out or undo a check-out.


3.2.3 Checking In Documents

Check-in is the process of uploading a new revision of a document already in Oracle WebCenter Content. You upload new documents and check in new revisions of existing documents.

3.3 Understanding Document Metadata Properties

Metadata, also called document properties, or content information, is information about a document, such as the title, author, release date, who can access the document and its metadata, and so on. You can use metadata to find documents in Oracle WebCenter Content, much as you would search for books in a library by author or subject. When you upload a document, you assign some metadata values, while Oracle WebCenter Content assigns some metadata values automatically. The metadata is stored in a database that works with Oracle WebCenter Content.

3.3.1 Using Document Metadata Properties

You use document properties for the following reasons:

  • To secure documents to control access. Security Group is a required metadata field anytime you upload a document. In some cases, the security group may be set for you automatically.

  • To refine access. Access control lists are optional metadata that can control who has access to folders or documents at the folder or document level.

  • To categorize documents. Document type is a required field that helps you organize documents.

  • To track multiple revisions of documents. A revision history is useful when you need to see how a document has changed.

  • To track who uploaded or edited the document and when.

  • To find documents. Metadata associated with a document can be easily searched and used to filter documents so that you can find the one document you need out of many managed by Oracle WebCenter Content.

For more information about document metadata properties, see Section 4.4.

3.4 Understanding How to Find Documents

A critical reason for managing unstructured content is so that you can find pertinent information quickly. To do this, Oracle WebCenter Content uses a powerful combination of browsing through libraries, searching for metadata and filtering results. If your system is configured to do so, Oracle WebCenter Content also indexes the full text of a document, making it available for searching.

3.4.1 Library and Folder Context

Documents uploaded to Oracle WebCenter Content can be unfiled, meaning that they are not uploaded to any library or folder, or organized in the context of a library and folder. If you know in what context documents are organized, it is easy to browse for them using the Library and Folder options in the side bar. For more information on libraries, see Chapter 5.

3.4.2 Metadata Search

You can search for documents using the metadata values associated with the documents. This is useful when:

  • The documents you are looking for are not filed in the context of a library or folder.

  • You do not know how the documents are organized.

  • You want to refine your search within the context of how the documents are organized.

When searching using metadata values, you can use a search operator to narrow or broaden your search criteria.

3.4.3 Metadata Search Operators for a Database Metadata Search

If you use a search form rather than the search box, you can use search operators to refine the search criteria. These operators are listed as options in lists to the left of each field.

The following table describes the search terms used and provides examples for use.

OperatorDescriptionExample

Substring

Finds content items with the specified string anywhere in the metadata field. This operator has the same effect as placing a wildcard before and after the search term. This is the default operator.

This operator is not available for implementations that use Oracle Text Search.

When you enter form in the Title field, the search returns items with words such as forms, performance, and reform in their title.

Matches

Finds items with the exact specified value in the metadata field.

When you enter address change form in the Title field, the search returns items with the exact title of address change form.

Starts

Finds items with the specified value at the beginning of the metadata field. This operator has the same effect as placing a wildcard after the search term when using the Matches operator.

When you enter form in the Title field, the search returns all items with a title that begins with form, including forms, forming, and so on.

Contains

Finds items with the specified whole word or phrase in the metadata field.

This operator is available only for Oracle Text Search, or for Oracle Database and Microsoft SQL Server database with the optional DBSearchContainsOpSupport component enabled. For more information, see your administrator.

When you enter form in the Title field, the search returns items with the word form in their title but does not return items with the word performance or reform.

Ends

Finds items with the specified value at the end of the metadata field. This operator has the same effect as placing a wildcard before the search term when using the Matches operator.

When you enter form in the Title field, the search returns all items with titles that end with form, such as form, perform, and chloroform.

Not Substring

Finds content items that do not have the specified string anywhere in the metadata field.

When you enter form in the Title field, the search returns items without words such as forms, performance, and reform in their title.

Not Matches

Finds items that do not have the exact specified value in the metadata field.

When you enter address change form in the Title field, the search returns items without the exact title of Address Change Form.


3.4.4 Metadata Search Case Sensitivity

Case sensitivity for metadata searches varies depending on how your system administrator has configured Content Server.


Note:

For information about your specific configuration, see your system administrator.


  • Microsoft SQL Server: If Content Server is using database searching with Microsoft SQL Server, metadata searches can be case sensitive or insensitive, depending on how the database is set up.

  • Oracle Database: If Content Server is using database searching with Oracle Database, metadata searches are always case sensitive and full-text searches are not case-sensitive.

  • IBM DB2: If Content Server is using database searching with IBM DB2, metadata searches are case sensitive.

3.4.5 About Full-Text Searching

Full-text searching enables you to find a content item based on the text contained in the file itself. When you check in a content item into Content Server, the indexer stores all of the words in the Web-viewable version of the content item (PDF, HTML, text, or other supported file formats) in an index. A full-text search compares the search expression with the index and returns any content items and discussions that contain the search text.

You can include the following in a full-text search expression:

  • Strings: partial words (such as addr)

  • Words: individual whole words (such as addresses)

  • Phrases: multiple-word phrases (such as new addresses)

  • Operators: logic applied to words and phrases (such as news AND addresses)

For more information, see Section 3.4.6, "Full-Text Search Rules."

Search terms can be highlighted in the returned text, provided Content Server is using Oracle Database full-text search and your administrator has enabled the functionality. Forward (>>) and back (<<) navigation links bracket the highlighted text. Click the links to go to the next and previous result in the text.

3.4.6 Full-Text Search Rules

To refine your full-text search criteria:

  • You can use wildcards in full-text search queries.

  • You can use search operators in full-text search queries.

    For more information, see Section 3.4.8, "Oracle Database Full-Text Search Operators."

  • You can use Internet-Style Search Syntax.

  • When you perform a full-text search, the search finds the word you specify and words that have the same stem. For example, searching for the word address finds files with the word address, addressing, addresses, or addressed in them. To limit the search to the word you specify, place the word in double quotation marks (for example, "address").

  • You can sort full-text search results by the number of occurrences of the search terms and the proximity of the search terms when you use an operator such as <NEAR>. Select the Score option from the Sort By list on the Oracle WebCenter Content.


    Note:

    You can sort the results using the Score option only if you are using the Oracle 11g database search solution and have installed the Oracle Text Search option.


3.4.7 Full-Text Search Case Sensitivity

Case sensitivity for full-text searches varies depending on how your system administrator has configured Content Server. By default, full-text searches with Oracle Database are not case sensitive. Full-text searches with Microsoft SQL Server vary based on how the database is set up.

If your Content Server configuration includes an optional search engine, case sensitivity depends on the search engine. For information about your specific configuration, see your system administrator.


Tip:

Generally, you should use all lowercase search strings to find all of the files that match your search expression. Use mixed-case search strings only if you are looking for a specific combination of lowercase and uppercase.


3.4.8 Oracle Database Full-Text Search Operators

Use the following operators to refine your Oracle Database full-text search expression.


Note:

For clarity, the operators are shown in uppercase, but they can also be in lowercase.


OperatorDescriptionExample

AND

Finds content items that contain all of the specified terms.

address AND name returns content items that contain both specified words.

OR

Finds content items that contain at least one of the specified terms.

safety OR security OR protection returns content items that contain at least one of the specified words.

NOT

Finds content items that contain the term that precedes the operator (if any), and ignores content items that contain the term that follows it.

NOT server returns content items that do not contain the word server.

internet NOT server returns content items that contain the word internet but do not contain the word server.

NEAR(term1, term2)

Finds content items that contain the specified terms near to each other. Terms that are closer receive a higher score.

NEAR(internet,server) returns content items that contain the specified words close to one another.

ISABOUT(phrase)

Finds content items that contain the phrase specified in the parenthesis.

ISABOUT(changed address) returns content items that contain the specified phrase.


3.5 Understanding How a Document is Processed Within Oracle WebCenter Content

Oracle WebCenter Content must process documents when they are uploaded or checked in. This process includes:

  1. Determining the metadata options based on the document context.

  2. Assigning values to the metadata that are either provided automatically by the system or manually by the person who uploaded the document.

  3. Converting the document if necessary using the conversion options specified by a system administrator. Conversion options may provide one or more types of web-viewable options for the document so that people throughout the organization have access to see it even though they may not have the native application that created the document.

  4. Storing the documents and web-viewable conversions based on rules defined by a system administrator. Native and converted documents can be stored in a database, on a file system, or using a combination of the two.

  5. Routing a document through a workflow if it meets the criteria to do so. Workflow criteria are defined by a system administrator and documents that meet the defined criteria are automatically routed.

Releasing a Document

Once a document has been processed successfully, it is indexed by Oracle WebCenter Content so that others with proper access can find the document. The document or its metadata only are indexed when the document meets all of the following criteria:

  • The document converts successfully or passes through without conversion if no conversion is necessary

  • The document is approved at all steps of a workflow (if any)

  • The document reaches its release date

Once a document is released, you can:

  • Find the document by browsing or searching

  • Retrieve the web-viewable file, the native file, the metadata, or any combination of these

Figure 3-1 Revision Process

Graphic of Revision Process

3.5.1 Revision Status

A document changes status several times when it is uploaded or revised. It is useful to know what types of status there are in case you have difficulty finding a document or need to locate a document that is not yet released.

StatusDescription

Waiting

The document has a revision in the system but has not been sent for conversion.

GenWWW

The document is being converted to web-viewable format or is being indexed, or has failed conversion or indexing.

Done

The document is waiting to be released on its specified release date.

Released

The revision is available in Oracle WebCenter Content.

Review

The revision is in a workflow and is being reviewed.

Edit

The revision is at the initial contribution step of a workflow.

Pending

The revision is in a basic workflow and is waiting for approval of all revisions in the workflow.

Expired

The revision is no longer available for viewing in Oracle WebCenter Content. (The revision is not removed from the repository, but only an administrator can access it.)

Deleted

The revision has been deleted and is waiting to be completely removed from Oracle WebCenter Content during the next indexing cycle.


3.5.2 Understanding Revision History

Each time you check out a document and check it back in, Oracle WebCenter Content creates a new revision of that document. The new revision has the same content ID as the previous revision, but the native file and the metadata can be the same or different. The system stores the previous versions o!f a document, so you can review them as necessary.

3.5.3 Expired Content

A document can have an expiration date that specifies when the document is no longer accessible through the standard interface for searching or viewing. All revisions of the document expire when the document expires.

To determine if a document has expired, use the Expired Content page in the Content Management tray.

When a document expires, it and its revisions are not deleted from the repository, but they can be accessed only from the Repository Manager by an administrator unless Notification of Expiration is in use.

3.6 Understanding Document Security

Document security determines who can view a document, who can edit it, and who can modify the document properties. Access is controlled by a combination of roles and security groups created by a system administrator, and access control lists you define when uploading a document. Optionally, an account can be set up to refine security. For more information, see Section 4.5.

3.7 Understanding Library and Folder Security

Security can be set at library and folder levels as well as the document level. Security is inherited from the containing library unless it is set independently. For more information, see Section 4.5.1.

PK |އPKC_EOEBPS/workflows_oldui.htmA9 Using Workflows

23 Using Workflows

This chapter describes how to participate in and manage the workflows to which you belong.

This chapter has the following topics:

23.1 About Workflows

A workflow specifies how to route content for review and approval before it is released to the system. The workflow notifies users by e-mail when they have a file to review. For information about workflow types and uses, see Chapter 7.

23.2 Entering a File to a Workflow

When a basic workflow starts, it sends an e-mail message to the contributors, who must check in the designated files as the first step in the workflow.

To check in a file to begin a basic workflow:

  1. Read the Workflow Started Notification message.

  2. On the Workflow Content Items page, click the Review Workflow Content link.

  3. Choose Check Out from the contextual menu in the Actions column.

  4. On the Check-Out Confirmation page, check the content item into the system using one of the following methods:

    • If the check-out confirmation page is still displayed, click Check In.

    • Choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

    • Open the Content Management tray, click Active Workflows, click the name of the workflow, then choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

  5. Fill in the content check-in form.

    • If you select the Revision Finished Editing check box, the revision moves from Edit status to GenWWW status and goes to the next step in the workflow.

    • If you leave the Revision Finished Editing check box unselected, the file is checked in but remains in Edit status instead of moving to GenWWW status. Return to Step 3 to check out the file and check it back in.


      Tip:

      If a document included in a workflow fails to convert in the check-in process, the content item is set to Edit status automatically. For this reason, include documents in the workflow that are valid for conversion.


  6. Click Check In and provide user credentials if prompted.

23.3 Reviewing Revisions in a Workflow

When the next step in a workflow is a review step, the reviewers receive an e-mail message. When the appropriate number of reviewers approve the revision, the content item goes to the next step in the workflow.

To review a file in a workflow:

  1. Read the Workflow Review Notification Message.

  2. Click the Review Workflow Item link.


    Note:

    For a reviewer step, you can choose to Sign and Approve, Approve or Reject the content item. For a reviewer/contributor step, you can choose to Check Out, Approve, or Reject the content item.


  3. On the Workflow Review page:

    • Review the file in the area to the right of the Workflow Review panel.

    • Click the Web Viewable link to see a version of the content in your browser.

    • Click the Native File link to save a copy of the file in its original format.

    • Click the HTML Rendition link to view the file as HTML in your browser.

  4. If you have reviewer/contributor permission and you would like to edit the file, click the Check out link in the Workflow Review panel to check out the content item for editing. Otherwise, continue with Step 12.

  5. On the Check-Out Confirmation page, get a copy of the original file and edit it.

  6. Check the content item back in to the system using one of the following methods:

    • If the check-out confirmation page is still displayed, click Check In.

    • Choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

    • Open the Content Management tray, click Active Workflows, click the name of the workflow, then choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

  7. Fill in the Checked-Out Content page.

    • If you select the Approve Revision box, the revision moves from Edit status to GenWWW status and goes to the next step in the workflow when the required number of reviewers approve. Step 8 is not required.

    • If you leave the Approve Revision box unselected, the revision is checked in but remains in Review status instead of moving to GenWWW status. You must still approve or reject the revision.

  8. Click Check In.

  9. To reject the revision, click the Reject link in the Workflow Review panel.

  10. On the Reject Content Item page, enter a message explaining the reason for rejecting the content item. When you reject a content item, it is sent back to the most recent workflow step that permitted contribution.

  11. To approve the revision, click the Approve or the Sign and Approve link in the Workflow Review panel.

  12. If you click Sign and Approve, on the Sign Workflow Content Item page, specify your password and any additional metadata values and click Sign and Approve.

  13. Review the information in the confirmation window and click Close Window.

23.4 Working with a Rejected Revision

When a revision is rejected, the users assigned to the most recent contribution step receive an e-mail message.

To edit a rejected file:

  1. Read the Workflow Content Item Reject Notification message.

  2. Click the Review Workflow Content link.

  3. On the Workflow Content Items page, choose Check Out from the contextual menu in the Actions column.

  4. On the Check-Out Confirmation page, get a copy of the original file and edit it.

  5. Check the content item back into the system using one of the following methods:

    • If the check-out confirmation page is still displayed, click Check In.

    • Choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

    • Open the Content Management tray, click Active Workflows, click the name of the workflow, and then choose Check In from the contextual menu in the Actions column on the Workflow Content Items page.

  6. Fill in the Checked-Out Content page.

    • If you select the Revision Finished Editing box, the file moves from Review status to GenWWW status and goes to the next step in the workflow.

    • If you leave the Revision Finished Editing box unselected, the file is checked in but remains in Review status instead of moving to GenWWW status. You must still approve the file.

  7. Click Check In.

23.5 Viewing Workflow Information

There are several ways to view information about a content item in a workflow. With links between workflow pages you can perform the following tasks:

23.5.1 Viewing a List of Active Workflows

To view a list of all active workflows in the system:

  1. Open the Content Management tray.

  2. Click Active Workflows.

    The Active Workflows page opens.

23.5.2 Viewing a List of Your Workflows

To view a list of workflows that require action from you:

  1. Open the My Content Server tray.

  2. Click My Workflow Assignments.

  3. To remove content items from the Workflow in Queue page, choose Remove from Queue from the contextual menu in the Actions column. (The content item is not deleted from the workflow.)

23.5.3 Viewing Workflow History and Information About a Workflow Step

To view workflow history and information about a workflow step:

  1. Display either the Workflow Content Items page or the Workflow in Queue page.

  2. Choose Workflow Info from the contextual menu in the Actions column.

    The Workflow Info for Item page opens.

23.5.4 Viewing Content Information

To view content information for a revision in a workflow:

  1. Open the My Content Server tray.

  2. Click My Workflow Assignments.

  3. On the Workflow in Queue page, choose Content Info from the contextual menu in the Actions column.

    The Content Information page opens.

PKd tF9A9PKC_EOEBPS/get_started_newui.htm Getting Started with the WebCenter Content User interface

8 Getting Started with the WebCenter Content User interface

The WebCenter Content user interface offers an easy and intuitive user interface with drag-and-drop convenience and sophisticated searching capabilities. It offers a simple way to store, secure, retrieve, and share any type of document. This section has the following topics:

8.1 Working with Oracle WebCenter Content

You work with Oracle WebCenter Content to upload documents to the repository and search for and view documents that others have uploaded. The two main pages used in Oracle WebCenter Content are the Find Documents page and the View Documents page.

Find Documents Page

The Find Documents page is displayed when you first log in to Oracle WebCenter Content. You can personalize this page to display all documents, all libraries, or your favorites the next time you log in. The page also provides ways to filter what documents are displayed to help you find specific documents more quickly. Detailed information about the Find Documents page is in Section 8.3.1.

View Documents Page

The View Documents page is displayed when you open a document from a results list. The page allows you to view the contents of a document, the metadata properties of the document, and provides ways to update the document to a new revision, update the document metadata properties, or download the document. Detailed information about the View Documents page is in Section 8.3.7.

8.2 Accessing Oracle WebCenter Content

To access Oracle WebCenter Content using a standard web browser, enter the web address and log in. The web address is configured when Oracle WebCenter Content is installed. You must be given rights to log in. Rights may be shared with other systems in your organization. If you are uncertain if you have rights to log in or what user name and password to use, contact a system administrator for Oracle WebCenter Content.

8.3 Understanding the WebCenter Content User interface

The WebCenter Content user interface is focused on helping you find and view documents. The Find Documents page and View Documents page provide access to the most common features necessary for managing documents. This section describes the main pages and features of the WebCenter Content user interface.

8.3.1 Find Documents Page

The Find Documents page is displayed when you first log in to Oracle WebCenter Content. You can personalize this page to display all documents, all libraries, or your favorites when you log in.

Figure 8-1 Oracle WebCenter Content Find Documents Page

Oracle WebCenter Content Find Documents Page

The following areas of the Find Documents page are used to quickly find documents:

  • Banner: Located at the top of the page, the banner contains the following items:

    • Search box: The search box is a field that expands as you enter text to show instant results organized by libraries, folders, and documents. Selecting an option helps narrow the displayed results so you can find documents more quickly. Steps for using the search box are detailed in Section 9.4, "Searching Using the Banner Search Box".

    • User Name and Preferences: Selecting the user name in the banner displays a menu allowing you to set preferences for working with Oracle WebCenter Content or log out of the system.

    • Workflow Notification Icon: If you have pending workflows, the workflow notification icon is displayed next to your user name. Click the icon to display a list of documents in workflow that are currently assigned to you.

  • Side bar: Located to the side of the page, the side bar provides a way to browse through libraries and items you've marked as favorites. Once you've selected a library, an additional option to search for and browse through folders is also displayed in the side bar. Steps for using the side bar are detailed in Section 9.3, "Browsing Using the Side Bar".

  • Results list: The results when you search or browse are displayed in the main content area of the Find Documents page. The results may come from a search using the search box, through browsing using the side bar, or a combination of the two. Steps for working with results are detailed in Section 9.9, "Working with the Results List".

8.3.2 Search Box

When searching for documents using Searching Metadata, entering text into the search box expands the box to display libraries, documents, or folders whose names are close matches to what you enter. It does not only show exact matches. This means that you may see results in the expanded search box that won't be displayed in a results list. For example, entering moto in the search box may show suggestions for documents with motorcycle or photo in the name, and a folder called Notes.

Any filters applied to the search are displayed in the search box. Closing the filters in the search box removes the filter and broadens the search to a larger context.

Figure 8-2 Oracle WebCenter Content Search Box

Search Box

Filters predefined by a system administrator based on document properties are available by clicking the arrow next to the search box. Depending on how the filter list is configured, some filters in the list may display the number of documents within each filter.

Figure 8-3 Predefined Filter Choices in Search Box

Search Box Filters

Note:

When browsing for documents in Browsing, entering text into the search box searches only the names of documents in the library or folder you are browsing, not any other metadata or full-text. For example, if you browse to a library called WebCenter Content Documentation then to a folder called Administration and enter report into the search box, the results list displays documents in the administration folder whose names contain the word report, such as Q3 2011 Report, Bob's Status Report, or New Financial Reporting Procedures. To search for metadata within the folder you have browsed to, you must first switch to Searching Metadata by clicking the Search <Folder> and Subfolders icon in the results list toolbar.


8.3.3 Side Bar

Using the library and folder features in the side bar provides an easy way to organize documents and navigate document storage in Oracle WebCenter Content. The Create Library option allows you to create a new library. It is only available when browsing at the top level of libraries. The Upload options enable you to upload documents using the profile options available in the Upload menu. The Upload menu is not available when browsing at the top level of libraries.

Use the Search link to enter Searching Metadata and display all documents in Oracle WebCenter Content to which you have access, or use the Browse link to enter Browsing and display a list of libraries available to you in the results list. After you have opened a library, then the option to search for and browse folders is available in the side bar.

In addition to navigating libraries and folders, the side bar gives you quick access to all items you have marked as favorites. Clicking Favorites shows a results list that includes all of your favorites, whether they are documents, folders, or libraries.

Figure 8-4 Oracle WebCenter Content Side Bar

Side Bar

8.3.4 Results List

The results list displays documents in the main content area based on the filters you use when browsing and searching. Folders and shortcuts to folders are typically not listed in the results list, but are displayed in the side bar when a library is opened. There are two situations when folders are displayed in a results list:

  • When clicking Favorites in the side bar. Any document, folder, or library set as a favorite is displayed.

  • When clicking Folders if you search using the search box and then select Folders from the suggestion list (see Figure 8-2).

The title of the results list shows the context of the listed documents. For example, if you click Search in the sidebar, the results list displays all documents in Oracle WebCenter Content to which you have access, with no filtering by library or folder, and the title displayed is Searching Documents.

If you navigate to a folder within the library and click the Search <Folder> and Subfolders icon, then the title changes to Searching <Folder> and Subfolders. This is important because the title tells you the context in which you are searching for a document. If you want to browse after searching but remain in the library or folder you are in, click the title of the library or folder tab in the search box. For more information on the differences between browsing and searching, see Section 9.3.4.

Figure 8-5 Results List from Searching with the Search Box

Graphic of search results

Once you click Browse and open a library, though, the title changes to the name of the library. In addition, a toolbar is displayed under the Library that includes a path to where you are browsing and several tool options:

IconOptionDescription

Search This Location


Search <Folder/Library> and Subfolders

Click to use the search box to search metadata or the full-text of documents within the folder or library you are browsing, rather than only the name of the document or folder.

Get Link Icon


Get Link

Displays a URL to the library or folder in which you are browsing.

Folder Properties


Folder/Library Properties

Displays properties of the library or folder you are browsing in.


Oracle WebCenter Content behaves differently depending on if you search for content using the search box or browse for content within libraries or folders. Consequently, the results list is also slightly different. For example, if you search using the search box without first navigating to a specific folder or library, the results list displays the documents that match your search criteria regardless of what library or folder context the documents are in. Figure 8-5 shows an example of results listing documents regardless of what library or folder the documents are in.

If instead of searching using the search bar, you browse to a particular folder in the Motorcycle library, then the results list displays only those documents within that folder and location links show the path of the folder hierarchy. Figure 8-6 shows an example of results returned when browsing through libraries and folders. Additional differences between searching and browsing are detailed in Section 8.3.6.

Figure 8-6 Results List from Browsing Using the Side Bar

Browse Results List

Note:

When browsing, entering text into the search box searches only the names of documents in the library or folder you are browsing, not any other metadata or full-text. To search for metadata within the folder you have browsed to, you must first switch to Searching Metadata by clicking the Search <Folder> and Subfolders icon in the results list toolbar.


8.3.5 Results List Toolbar and Contextual Menu

You can change how results are sorted and also how they are displayed using the options in the toolbar below the results list title. Selecting one or more documents in the results list adds options to the toolbar, such as letting you copy or move one or more documents to different folders or libraries, or do a variety of other tasks.

Figure 8-7 Results List Toolbar

List Toolbar

Selecting a single document displays the results list toolbar. Right-clicking on a document displays a contextual menu. Both provide a convenient way to do a variety of functions which vary depending on the permissions you have. Functions you do not have permissions to are not displayed or grayed out. The full extent of the options available are detailed in the online help system and also in the procedures throughout this guide.

8.3.6 Searching and Browsing

Oracle WebCenter Content provides two powerful ways to find content: searching metadata and browsing content. They can be used separately or in combination, and have slightly different behavior and appearance.

8.3.6.1 Searching Metadata

When you log in to Oracle WebCenter Content the first time, you see a list of all released documents to which you have access on the Find Documents page. When searching, the search box searches all indexed metadata of the documents within the library or folder you are searching, including subfolders. If your system administrator has configured full-text indexing, then the full text of each document is searched as well. If you are not in the context of a library or folder, then all documents in the system are searched.


Note:

Only the latest released documents are returned in a results list when searching metadata. Unreleased documents and shortcuts are not displayed.


Figure 8-8 shows an example of the Find Document page with the following features specific to searching metadata noted:

  1. Search in the side bar is highlighted.

  2. There is no folder hierarchy in the side bar.

  3. There are no locator links in the title bar.

  4. Library and folder tags in the search bar display the context you are in. Clicking the title of a library or folder tag switches you from searching metadata back to browsing documents in that context.

  5. No folder tools are available in the title bar.

  6. The Save Search menu is displayed next to the search box.

Figure 8-8 Searching Metadata with Search Features Noted

Graphic of search mode features

8.3.6.2 Browsing

Click Browse in the side bar of Oracle WebCenter Content to see a list of libraries in the main area of the page. Click a library to see a listing of documents within the library to which you have access, with folders displayed in the side bar. When browsing, the search box no longer searches through document metadata by default, but rather searches through names of documents in the particular library or folder you are browsing.

If you want to search metadata and optional full-text within the context of the library or folder you are browsing, you need to click the Search <Folder> and Subfolders icon in the title bar. Doing so lets you search metadata within the context of the library or folder you are browsing, including subfolders. To return to browsing, click the title of the library or folder tag listed in the search box (see 4 in Figure 8-8).


Note:

Both released and unreleased documents are returned in a results list when using browsing, as well as any shortcuts.


Note that when browsing system libraries or favorites, you do not have all of the options available when browsing enterprise libraries. Figure 8-9 shows an example of the Find Documents page when browsing through enterprise libraries, with the following features specific to browsing noted:

  1. Browse in the side bar is highlighted.

  2. There is a folder hierarchy in the side bar

  3. There are locator links in the title bar.

  4. Library and folder tags in the search bar display the context you are in. Clicking the X in the tag closes the tag and backs you out of that context.

  5. Folder tools are available in the title bar allowing you to switch to searching, as well as see properties and links for the library or folder you are in.

  6. The Save Search menu is not displayed next to the search box.

Figure 8-9 Browsing with Browse Features Noted

Graphic of browse mode features

8.3.7 View Documents Page

Depending on the document format and how your system is configured, Oracle WebCenter Content can convert many uploaded documents into formats that are viewable using a standard web browser. In addition to the current released version of the document, all previous revisions are easily accessed, as well as all the metadata properties of the current and previous revisions of the document.

Figure 8-10 Oracle WebCenter Content Document Page

Oracle WebCenter Content Document View Page

The following areas of the Document page are used to quickly view and update documents and document properties:

  • Banner: Located at the top of the page, the banner displays the path to the document location in the context of Oracle WebCenter Content. Click on a step in the path to navigate to the step's location.


    Note:

    If a document is unfiled, the document is listed as Unfiled and a link allows you to file the document.


    Additionally, the banner is used to log out, mark a document as a favorite, provide links to documents, and open a menu that provides various options for working with a document.

    Figure 8-11 Oracle WebCenter Content Document Page Banner

    Oracle WebCenter Content Document View Page Banner
  • Properties section: Located to the side of the page, the properties section provides a summary of document properties at a glance. The Renditions section allows you to download a copy of the document and any other renditions. The Attachments section allows you to attach additional items that may be useful only when associated with the document revision. For example, you can attach a photo of a job candidate with the candidate's résumé. The photo does not have to be managed as a separate document in WebCenter Content, but instead provides support for the revision being managed. Note that attachments are specific to a revision.

    If a document is in a workflow, an additional section is added to the summary tab. If the document has been assigned to you, the section provides options to review workflow details and approve or reject a document. See Section 15.4 for more information on reviewing workflow items assigned to you.

    Tabs in the properties section can be used to display all document metadata and if you have the rights to do so, change the security access to a document.

    Figure 8-12 Oracle WebCenter Content Document Properties

    Oracle WebCenter Content Document View Page Properties
  • Document view area: The document is displayed in the body of the View Documents page. The document view area has a toolbar that provides various options for manipulating the document view such as zooming in and out or changing pages. Above the view toolbar are the revision history tabs. Clicking a tab quickly displays a view of that revision, including the metadata of that revision. Adding a tab is a quick way to upload a new revision. Steps for working with document view area are detailed in Section 10.2.

    Figure 8-13 Oracle WebCenter Content Document Page Toolbar

    Document View Toolbar

8.4 Personalizing WebCenter Content Preferences

Clicking your user name in the banner opens a menu allowing you to set several preferences. When the preferences page is displayed, the general preferences tab typically has the option to use an external user directory to control preferences enabled. This means your name, e-mail address, locale and time zone are specified by information managed externally by your system administrator. In some cases you may want to manage these yourself, for example by adding a nickname to your full name or changing your locale. If so, disable Use external user directory settings. It is a good idea to check with your system administrator before doing so.

Figure 8-14 Oracle WebCenter Content General Preferences

Graphic of general preferences

Oracle WebCenter Content offers extensive guidance messages throughout the product. As you do something for the first time, a message is often displayed on the page beneath the title bar to help you with the task. You can leave these messages open so that they are displayed each time you do the task, or you can hide each message by enabling Do not show this message again. If you hide messages and would like to have them display again at another time, you can reset the guidance messages preference under the personalization preferences tab.

Also under the personalization preferences tab, you can set the home page preference to always show a list of libraries, recent documents, or your favorites each time you log in. You can also enable WebCenter Content to accept scanned documents, as well as clear recent and pinned items from selection lists.


Note:

The Scan button is displayed on the Upload page when you select Enable upload by scanning from the Preferences page. You must also have a TWAIN-compliant scanner properly connected to your workstation to use this option. For detailed information about the options available in the scanning application, click the Help icon in the scanning application to see the online help system.


Figure 8-15 Oracle WebCenter Content Personalization Preferences

Surrounding text describes Figure 8-15 .

Oracle WebCenter Content also lets you adjust accessibility settings to your preference. If you prefer to use a screen reader, like a high contrast display setting, or use large fonts, you can set these options using your preference settings.

Figure 8-16 Oracle WebCenter Content Accessibility Preferences

Oracle WebCenter Content Preferences
PKJu)"PKC_EOEBPS/workflows_newui.htm7- Using Workflows

15 Using Workflows

This chapter describes how to participate in and manage the workflows to which you belong.

This chapter has the following topics:

15.1 About Workflows

A workflow specifies how to route content for review and approval before it is released to the system. The workflow notifies users by e-mail when they have a file to review, and by displaying a workflow notification icon in the banner next to their user name.

15.2 Workflow Types

From a workflow participant's point of view, there are two types of workflows:

  • A basic workflow defines the review process for specific content items, and must be initiated manually.

  • In a criteria workflow, a file enters the workflow automatically upon check-in when its metadata matches predefined criteria.

15.3 Entering a File to a Workflow

If you have been assigned as a contributor to a basic workflow, it notifies you that you have an item in workflow both by e-mail and by notification flag on the banner of the WebCenter Content home page. To start the workflow, you must check in the designated files as the first step.

To check in a file to begin a basic workflow:

  1. Click the Items in Workflow notification icon (Items in Workflow icon) on the home page banner to display a listing of all workflow items assigned to you.

  2. Do one of the following:

    • Right-click on the item in the result list to check in and select Check In from the contextual menu.

    • Select the item in the result list to check in and click the Check In icon (New Revision Check In icon) in the toolbar.

    • Open the document in the View Documents page to display the document properties and click Check In.


      Note:

      Document properties of workflow items also link to workflow details and subsequently to workflow history. From the document properties tab in the View Documents page you can also approve, reject, or check in workflow items assigned to you. You can access document properties in a number of ways, including right-clicking an item in a result list and selecting Properties from the contextual menu.


  3. Select a destination and profile to use and click Continue. For detailed information about checking in a file, see Section 11.2.

  4. Select a file to check in and fill in the check-in form, then click Upload, noting the following:

    • By default, Submit document to workflow is enabled and any item checked in moves to the next step in the workflow.

    • Disabling Submit document to workflow and clicking Upload checks in the file but keeps it in edit status. It does not move to the next step in the workflow.

15.4 Reviewing Workflow Items Assigned to You

When you are assigned to the current step in a workflow, you receive an e-mail message and a notification flag on the banner of the WebCenter Content home page. When the required number of reviewers approve the revision, the content item goes to the next step in the workflow.

To review a file in a workflow:

  1. Click the Items in Workflow notification icon (Items in Workflow icon) on the home page banner to display a listing of all workflow items assigned to you. Workflow items are assigned to you when you have a responsibility to check in or review the item.

  2. Select one of the following options pertaining to workflow items on the listing toolbar when an item is selected, or on the summary tab of the document properties on the View Documents page:

    • Approve Approve workflow icon : Approves the item in a review step. There are three types of review steps: review, review/edit revision, and review/new revision. Once the required number of reviewers approves the item, it moves to the next step in the workflow. The option to approve is not available for an item in a contribution step.

    • Reject Reject workflow icon : Rejects the item in a review step and returns it to the most recent review step that allows editing. If there is no previous review step that allows editing, then it returns to the original contribution step.

    • Check In New Revision Check In icon : Uploads a revised document for an item in a review or contribution step. If you check in a document in a review/new revision step, the revision number increments with each check in. This allows you to manage changed revisions to a document throughout the workflow process.

      If you check in a document in a review/edit revision step, then the revision number stays the same throughout the step. If it is the final step in the workflow, it stays at that revision even when the document is released at the end of the workflow. This allows you or others to change the document several times and only manage approved and released revisions.

      Note that you have the option to approve the document when you check it in.

    • Remove From Your Assignments: Removes the document from the Content in Workflow list results when the Assigned to you filter is applied. Selecting this option does not change the document's workflow status or the operations you can perform on the document. If a subsequent workflow step assigns the document to you, it will again appear in the list generated by the Assigned to you filter. This option is available only if the Assigned to you filter is applied.


      Note:

      If you remove a workflow from your assignments but need to contribute to the workflow, you can find the workflow by browsing the Content In Workflow system library without the Assigned to you filter applied.


Figure 15-1 Summary Tab Showing Workflow Options in Document Properties

Summary tab of document properties showing workflow options.

15.5 Viewing Workflow Information

There are several ways to view information about a content item in a workflow. With links between workflow pages you can perform the following tasks:

15.5.1 Viewing a List of Your Workflow Assignments

To view a list of workflows that require action from you, do one of the following:

  • Click the Items in Workflow notification icon (Items in Workflow icon) on the home page banner to display a listing of all workflow items, filtered by default to those assigned to you.

  • Navigate to the Content in Workflow system library:

    1. Click Browse in the side bar.

    2. Select the System Libraries filter from the Library type list in the search box to filter the library results list so that only system libraries are displayed.

    3. Click Content in Workflow in the result list. By default, only those workflow items assigned to you are displayed.

15.5.2 Viewing a List of All Documents in Active Workflows

To view a list of all active workflows in the system, follow the steps in Section 15.5.1 to view all items assigned to you, then expand the results to include all active workflows by clearing the Assigned to you filter in the search box.

15.5.3 Viewing a List of Documents in a Specific Workflow

To view a list of documents within a specific workflow, first view a list of all documents in active workflows (see Section 15.5.2) and select the workflow name from the filter list of the search box. Surrounding text describes filter_by_workflow.gif.

15.5.4 Viewing Workflow Details and History

Workflow details are accessed from the properties page of a document in workflow by clicking the View workflow details link under the properties summary tab or by selecting it from the More menu on the View Documents page. Workflow details include information about the current step and any completed steps in the workflow. This option is available only if the document is currently in a workflow.

Workflow history lists the workflows that a document has been part of and provides details about the steps and actions in each workflow. Workflow history is available on any document whether or not it is in an active workflow. For documents in an active workflow, access workflow history by clicking the View Workflow Details in the document properties summary section and then View Workflow History on the Workflow Details page. For documents not in an active workflow, access workflow history by selecting View Workflow History from the More menu of the View Documents page.

PKWS_77PKC_E#OEBPS/img/newui_searchbox_arrow.gif qGIF89a33324Yѹ1VY423233YcY33eY~3Z3~2}33ߠߠZZ3Y~3Za~~ڟ~42fff33}c2c2vvvV32x123W\V3xݙ˖1VUUUї᾿W3їxVMMc2x34YїWw\2w~\2x!!!ƠcY賳W!M3{绎uߞ~\2ѥvѹpppvM!uwZZ3M!!c񷸹™MMd!^ȥvїvvZ~Êvvvv\Vvvդx}Y33YY<<@3Y}xɭx3XϘ!!MzzzcYWxv˻{Y~z~~~!!ucY˴~Z4~ּu!3{{щߠ\V xWїxѓꍟvf$r&ihesfn6Sti}ycpDUgGmG< I8:H#r*+ꦤV*a>u;ܐKQ(^ۈ @hނk"Ob@,K[DٻD꣯E3I߲ʬ&VlqzB o^J>"[oD,qIKnD0lsqGn: q T/ ܠ>B7**0@ןefOݴ>&bH$}!L7Q306b>x;n %v`6? L9z]Tmp.z⨧(j!׮G21$&]bn;O.:>7':^Dy_~ ?GVIѤ'/~:pEa/5|dYlGHB &QȠ W1A@H 8̡wz$j AH"HL&:PH*ZX̢Xh 0!;/6pMQ\x̣> IBL"F:򑐌$$:2 pI!  (GIRL*WJR*ele)IMr2u.w^ue>hILC&r)f:4SS!LbĘS&.q nz&RYZ:Kӗ6MOr'*iw2'8zLBi6gT3$j3*d?il iFЎ ),Є)f2Q@V` ( t%Lŧ@=OrS4|!(J@TneRӜzp{(ߐ+m)ThA fJSܔJF>Tե*G_m*c@,WڔT7iTMYƲ!+mZYRխoi\:Ӛ2y,P::@$,թn-W@6Y/vS]-n^ ۢE,NkW2iQ[\6Wuػv8`GcGqWO'nj{DWwv.4ޜ:Ej Vm[we"VPdPh `k]5MpSġ쬃?+cc@|AMNm*WKWŽD ,d |௪9P]%3d:@7_XXŠ5ʖŌ7Xr6%f FlbSս4W;ݯ ]pVh V-ʧ{x4U%[C9+m20# jPX(&-YMlOnB; ]RV%[kWn3ea= [0K uJ 5y@ǬW%[N󡭫H.wus_NpXv] };FtQjd ɢ(adZl(oco@͆l6SkmFO2fJ|&;b%׬^,;ag(mNHv?\u{RjB?{=9~j}+i)P>myE y ng<& d@"crum eFSgNv]z{W^ba'%r?onp3y-{{OKPt6~NNZCuyP>4/U%z@WVgtgJgeEevSRi ڀhnU7k{Vg7i^U\%#ց# *8~_Me](^,hg@iׂh[Gu]7V8h"'](kApfnFQk&ZzZsWy'csJ5FW k ȀJGn]]}UEp`_|^[6|L^4]Fv8^\HUŷhoxUPQO]SY&Ї{fh#8.X|׉S5zCyPy~zgk8&S;mAD7txyԀt$MTqݘgNxNG2raX|1HQxД5jɔ^ 0?J ypϗܖkC9P ioHlC{;ڟY0])mKkˤ\t 2@$  Nlթg꼱LLoIРԌP _F@U -՜Y՗:QōrL &K\qMNٖ&uR nBIAX (yC}8R=֘:+\֗]--&)۬X=Q}3ە:ۣQI]Qƛ mܼȰw͖-vJݱ余UI睾m&}}[aLM]TI3'RkS Kyž4]@z. ڟ=:- ȁJAD>ٝ\+@˵,Ҁv༊=귎jb}͋xz 0 *_P^L p)VSί`]~VNDm0^:z:F᪈In@{Aokqʥ $NgLno+ *%GuKJ͟ۀ.}>ҎܦYYpjmO)ۚ:۳+k;2k.P{m»ګǪ[y ,@.*ȤA_  .ݸ K씹eQ p>?|ƄKln>ɫС [ 8˺ M0{4 >9. +L,n[=nkɼQ>;R@m~,+C ֢k ̧zjU]E|*jwl_ J!ȯpǂ<>4~-o`N0zh,\/ߩߦ~nD K0C2TH[C hPJ!BBdI dΤ)S3e'}x`C}p@O@C$BXJ<ZSH2Cٚ2ĵS nԺw߯_>m*(GοN;@N@)2d}skk7MmaiԘڣ'53-F2"E4xP1 IhJo @'&6$|<,ne"+N\xzg;|Ρ.m+[ysP: `Kl0\( Q mBPA}d ,.$@*@z)j,ѭRk6 DN 1d\J0E;}r\t\H@Ѐ{"k1jh+"ﶇÛ"4 pD4L7z()"hdL",f9:dQ;I?`SPC)"IQz U!4' FluYKGVK%HMiDX0 TAR\b+Vci[pw\rŏ) VȲJ|gNvqJ)襲ޟaӰI%SƮ^^o|nz(X_WkcZ|'f/Os37wczf.{^ֽU}.t˟`h\2 8h;]wAd0p`iA$x$/wO2n>hfM< ;J''O5{R^= 8!U;a#QۅP=[ r`iSu~WU\XFY CAo>@~T A '3| \&WXVFC&AE0V AGz}u%++6G`]؅jn#!q00eev0e6$0Weg*#`'p|*9$e(p'PSpcifYcYSY`r9Gp+``+`x((-;`^V ƈ`_%Vc@8X;EyD =9l yFVBr඄)e`huV޵g晕g[\fc8m^1ÊtCjVb}&^!"g&Y2X-!VrT@\\^Ռ&Y \bsp!]^EPM[a7)>h*6-`h/](PqWc@Y >\hEi.FZo57=\q}-MmCp/9z8ZDy?+X7b=E#8.Dڤx<0LJ<:s6C\:Oj:>l#dZ}qm>[*J:ntdF@YZ,sz䳧æv zqḊ;3}sJw|ʣ '55~کuQ*sQ+ᣨZHګʫ:*1jeŪkìКHPBsq89&:!hJ[7Z3oJ ɚ3ꚑڭjmzzpJ/:r2@!J2:ȣT1j ! ;"[%&-h#';-4;[ kA3[DIA!Im[7K[6KAج'QKװEb ´;A/{0\˲e{BK <?۵w++m+d۷2To˷S˶Sk: klkaAK`[!⴯Rڸ[4ڨYB iS;Z+۩ [nz˥ʻMڼM5{R{KM۽ 1P{蛾껾۾++{++ۿ<𫆯ۧ:p <\|"<"$|(L7P:412<4\6|8:<=>B<> D|H|FL9ˆs.PV|XZ\^`ab\f|bLhljp] j*`z|~ǀȂ<Ȅ\Ȇl{ȊȌ|ȉȐɐȒ\ɖ,tlQ/ɠʢ<ʤ\ʦ|ʨʪʮ,ʔʲLʭʱ<˩|˸L˯˦ ̾əL51\\ pڼ̼<\\v\y#1ϔ]< =,Ml =!#Lϒ㭭.02=/M 1=.mq;?4=DM[H]2m>MPG}0V8 L[^~"&>(!%~&7N-+N356.BD;^-[  PR>T^V.0Y[\^`W^fn{jl.bnr.iN^dcxm}^u~~{~dy^KœP~阞难N >>.@nꜾꬮ갎^굮NN~...쫾뜮Ď>n9S >^~뾿^^~RPB Dp9#:<s@tEʃqFd]4#qEZqHr$,#F"wTtJTJr&-dK/UR0I5\1isAsO>O@tPB 5КUtQFQH#4QI+P)39;MO5T$պLSOULuW[s;Ϝ5Z]ueT\aey7*WcDEL{,ʞ.g5Mm MW5c7Lnɝ.Cʒ04һ)x!,xiGTm^VdG/ ,{onݻjGMcw%JX2hπ bȬ ʁߌ5!y 38l1 *]"Pe1[e9sY2^cȫ *!DE>: tQVm!L8F||@&!z]X8 fm'n#Ex9:=4KGpb'aZx8;ND'>NJG$m)j6j$9 fup}f 3V%MFFN #_މtl74mp~ =Mm*3:̄AuKVUڳH(|Pv[H$)B"˗'-4DC~ʛ&_dBS8]g?:UQӔk P)hTAv+DTO** :#kY?i-ZJVyYhWq'4}nKeZBϮ ,5^aذm&|B׺*v)C_K*R!F[F.2tpL{Q0AlJ9֥Ld7؉m' a{맰ܘ,B% ķA-xSN/'KnŘכ|4.cIn*epoH)J Eәit:œ&RaNE5#2a]l @:Vk _KZ3XR* bD$E]|4k(L&tqLc;︀B:'}]wc6R.u##[PG˳Kc:h} K؎*{0G`BѶ4i ۲Եx<|9E VlRRh\AMf5q:[tYm_L`vlhG[Ӧv}mlg[vmp[& 5Xfwۭnw[}o|Zw\'x]p'Vx>p?\w)~qx q\M~6 bahoY+i_xcTn,<6-t7.H`Z l E:]ЩϹ.l)]a'{^:i([on{u]ko;uE]<{Ύu߷ q?;nK>yW>>\\\w˜fffd1;Frrr  111+2:[ ',0@M[$,yzzGS`cls 8 jt|/8?  邂m kp ž$ &,vHN@N! K/LR!\s L@%6LA"p,Mj[q!p6 rwn;bqhĶ۽oۻ&w/jMGhb6.4TAވSe;7,Bְ7,߈Px#z>ƙ] oBǧIJ[ M(ѥN[ئDn z4a\aqs&D0Da~̢ x7bp!a[7wagwnopV  Av PF Pl bp( ? 8 ,x'yx gy R& pc 8YhfpP<0 { sn'€P x7 Ykw$y ~ ' P  m@'pZ0$f@gƀ' 8h 6 q` qf 0 hH0 f @ @@Řq pcq} '{O` g  HX XX b ~9YayjhG'0Y~`%``` >`0  h{șy8~@~wY~f蛞yiwWow PsF{xWsxFh8z` +6 ` o 9q%gLI0q{|Byts<7| P mBb w ":`0x( s°yP) 0 y0 Y~̉&q( ȉ' x 6yIsp* 6G h&  цf 4P_ochfht Y,V5fgvƘaiڊVyp_Ul_ʦΧt :Zh'ʤ ry% ɑy  ' ʤ o 0n0 PW;jAi`@Ȁ dB,fhd]|&jȎcs~p,V*jfc}9e}dhz %ʥ)%Pp$i+ $KJJڙXjѹ'̆cqKCf67@ ` P` ()ʴLyR*KQZ[0b;d[60[*l۶&tjfz| fbf&;f0+k۸|[f7c۹AG{4jek ;[ {ۻƘx ;[{țK @ ؛ڻ۽ !ֹ.'{dƐ&֍;{ Еxɾ|u sb :_KLPR:k1Ԁ 0&\j *\ _&f JxG Ozgн:PJr2a`k ,͐fVlŋZk ӷv3U{el%PNf4 NjM MƜtl; ,@` }R=Ֆi }_W x_ΰkI`=>2f lKܽ\K MՒ=b^ ʯFf@L=! Wٔڮ}}-`Lڶ-|ɫڼ<½ }K X<ܗнz6]}4Xڽ- }kzV =(ݍ=]mߪѽ>ߵ n1r |`N ">$^&~(*,.02>4^6~8:<>@B>D^F~HJLNPR>T^V~XZ\^ b>d^ffjn bאz-l bNa~L=X^~阞难>4?0^~ꨎ|p?>n;rw^1P\Ppl~n>22ھ= =~P䩎>1@IP5> {p 3tP~P3```lM$^"m> 40 w~ H0 OԾ..I"^@30FIHNOK3EoL\?J?Nw6Pf/0`flAl_׊p|xp{P Alk Hp f `p qoհ knx: :ppUrTPJ[:Bo@;Uura6p U /<).9P303<0U>>oOO< O3p?3K?  ?hBc|1!1ln>H:/E-~Q>q XtN8iıQq?:v KD d! !ӥ0YKI!r,'[H~m_&\aĉ/fc2r'Ȁg1Ç<c y>$I vC}! 34o}Ԇöԟu63,@G;"z)۵}$!@W&iBul$nPii;>ЀfBiTgࡩs%@#-0j# -<jLE: exY$I7ц[erK.K0L:qŕ'$!ֈ``>lx-z8 3`85"8D !58* hB8ۭ|!7 8x "߀;*2v[5*L\kjC@5 >AC> .l0jJ"P?Ca`,`zB@Uf Xt%b)D@J:!PqdN T3p$!l`@ }@Dʓb06Lf THD4 G: g=ci Ñ>(l"F( "d}K`leA b0+2@p1 @ :p B NPC4r P*xhLh& U 4 r'% Q @( WAcdT1±dp.x[ScAYC@܂P(A6aZ0A 5dC(*lqxAXB$ *@4 L>) \hc(/0# ܢ W(F {X6fAWWQc`˘<a= j2!TT`-B%ȀzQPv jNK:dA hhQ[@ IEoX%hBb+ +@Dp'"!GQziwkRRaZ7!FB>H`f c(@m A}{_'~  WE.@|G_ӧ~}g_~C{_'~_OHC(A_(OCDlO >pDIDJO62CND_(;@?&(K,=OL-W(%RM3DA$Z;Hu)7axZDd4Fb4ƍxWx\82FlFmFnmgH0V,Gs%P$4(R9<`*4@@Ђ:E(2 HRxapaXXg9+9`xg\x' 6aW#5PXhI|IIɘ|2$GzI$P,8 ` UI(0p\-4HˆUX>0HWX`@gHQ8XQ`x,hWH`@KQaKK LLPMDJLLHG;؀N6RlãTLpEaE܅[ÀBF`O0`;X@B #hD[8DR8FZXK\6XF@,MlN|NNDLNEK&#&G1)0Eh%C(B0M`pL@#xxYdL4<<#X`P P P P P QMN;`2&KK0J`=,>p*bєJ4OxQp؜`u(ZKtMQ@MBBR.R/R0 S.eBDQ4ULxV6}S2HL`AW"3B.EB(A%ST`<@EA%G9ATX SGUhL8T1TP 20+8UTMUU]UVmUW}UXUYUZU[U\U]U[E A\P9S`ixqB R-RP-, P WqRB/58u]WvmWw}WxWyWzW{W|W}W~W؁@E7p-@TVCS(V(MXXXXXE<.6 Y-Y=YMY]YmY}YYYYYYYYٝ& X5"`EHVM,M(;(ZZZZ ۫%[sh m[}[[[[[[[[[4=x4xڅUp;t9ʭ\˽\\\ĘZ(@\]-]=]M]E]m0(p6^aÌZMhN؄"(58^pф@ }K7°y*p#Q= %:)X  \_8Vܿ(9Ȅ _ջt?e]CP ?xReӈ +"*9HL(=0((H)[^ -3 K(IyBb  ,@452+b,b-b.bbÐ_h36c,16ހ6~c7c8c9c:3>c@AQ+.$kdG~dHdIdJt]VNM6PxZ,@79(Ђ 3*('J:t%AȎ/@@7@'H&'xx4@߮Kl@-qh9(=Ƃ)|g}g~ggy=6>=0hhhhhhii.i>i鞤 ,бDH97Np' %:P[2ah'(V@ 81 6*) )؊ /A@hȂ=1hݸX Mk֍xk؂-bc . \ (NphDN`tdi _`q 0&Xa%:8-: "10iۀ؀ H P .Pe4@ /0/Ѓ(1.,V!^/Pe°l0 7C䰍MɷH@  0l NƞN.l?8X:sHpIf17%?A )-m>6ih(aP(ހ@h30C:)&+38(00x33}o 'h+*h'( oT!5PBF0~燍~pĊɮI(O؆r?po1)xJOxO3U 0M"`1HP6VgkF6_V@`%1xI-4 -8Q/; :6k&ȍ &d4(0h&q,@::)9xCXh3vllcN&'8tNxC[CVH'R p&hMch&d (M@yc*~>ޏx >D0(?6'-h5p"-h抂:h{N4xe57?Nt(dtxx>DuRgACpêOxR0Ȃ'f=.1::SȨ)8 0{!@3p8}ׂ(0A:PB9:m/p?_xE GcG?,Hc_s0e7^|]$U ȈX,6@(*/r1 45ȈB *j!sF͗Q4Q "albʔ*Q2srYK0?0Dad cH0d`#CAa"h1cK3NxDI MX-c&bx Ci,޼z/.lE(ʨ;nzpY)#̚ۈ !i"HȌ,2%iE^ aF[`$⣀D4 ?4^4 @oaӇ 3JJLhP"I .J4!K4Zh^gU]@\]I8!Zx!cE qELVJixa}6[ zA 30(30:r >TC0 :H$6JQ+6wR^%݀$24U)Jg&> 2S$G"v1 ܅"}'Xc8e K6$q JcQ@g x*):* ΰETe%^XRND]D! ~pN uޙ瞌*,.a HY.j 2A*{.A{Zj}jSqk,Z/ Jh'[ xK0[LqIAKWΔKkgz.2-[[Ӗ.k伳=A=:pGudzZ r!@APQGBÞ|6}6|0 6M!4q+LF~(# 7;ڇR͏[0݂{@hY.~9꩛ժzYy",鉓2,S˾v& b]Px>v=7j3PyROz@ERrȐZ/ٗ??9͈?ǝ/%鋝 / ^B3 kLWr^̄ b$x/DwB R @6ςCN!qP !' _Ht&XA/m-D,IHbA [(,UKW>kd]|! Z.<(0|aK)hB @y j!Jr\ݡ a 6@alPExdC ! pxҒsʻI R6u>/` ^$7il jN)dH*h \[*, ne\NGܬT@`H%W8pA *D @ l lfM46=+l٬o=D h;|@D U"$} 3`BMJdxF`NSkLVimj MkH{~ z߀wKE,ړ=p?v"0w,m}/^hB\Utb~'b>)x%bhWҰxkT8$ I^VȂtˋO xYߊ jhBxA 5 =8>!Hт*СEт'P a@|2پoh Q%5H:"! ][&y:r 4(! JB `C j=L `HB>ƹt:).  [ `LpQZp(axC!_7H;)CG٠! _ޠ@ - Jyh;&.LM.AZB b@ >v5  X8!0PB[]k%0$w(PNݼ\כ'vNj.?8S{.}~CW 1d+iA0~nN ;D3BL`h3(n&MdsX! h2m&hzX~}"%@l$!0?`a /S@X7h]T P lXN AkNJAPՖЀ]Xt@Aԏ8d9Tp8AdA(AxJDA{@ D0'][f@HlL|pyP!PL@X@ ^Nu lA@ɵӝ0D@@,`2 !@| @vi 4}$ TAP hRGD |@Pi(X@:͟BhpH5 @ d:jA(@@ "NA^m}RA|AEJ@(|TeqRA7Ā$J@t@ .H A |q%J]|Adց5޻aYHHl|@ H4ACLT!J! A V(P5kn+@hhkH dB:I C&xkl,΀\D*P5xNV1L4B  @x.*cUOA@~pA$9QH$ <>~AsDA SS HjSV$D(?A R@(\ Z%@$bAcQ/ D@HlkD@P dApȥ3]jpx ]T@AD@>#e@ @ pm8  jK@|(K>aptdl?D-2xbKZlP%H>[aF 2!J=zx@ e`F bIXf`)(K"&,h-Fg39% ȖȚE\ M.f?{o^{u+ƭ 6|1}2WLȐ} '8˫WǸkn ز]}wnݻyE[r}yrx3v3Co%\KN=|xɗ{m۷q5n~6~Y|աc-4P@5 <<+c¼>򫐿ӎ;[6JD"KF n=ܓQ8cդLl/ `0na0#0 H#Ƚ$ xB A! hNfToz,H# HcQR x">!U@̈%ӻ.+C$P3=m#PA5h Ttt .`C (( ! C/ 4`H6 >@ :J!C/@ PC":l(A" ):=;qOJ#+>衋 h‹1" : .(@,Ì/#&<?+6IN -U< 6cB\J@C((u(h77x&&A @ -(SW0B=P !fbΘ%L$,c,x 2Ѓ/x Ʌ%K2Ɯ9U(GD0 [4>&> a8  (((@XJh"6(a >AlPB,KT>0 C0%Ԡk6Ax "Bj$KH.4!D8&l! P: 6 lp AHB =t! X N%I;{XXiJJ@6ah8@@,oC ΰ ]  \iGAe|o)0KhA1 Jj@:A0(|cx\/ht8j28 NP(8auNxZP/@a TPC4 MBd3J%4' CL9 ]B 7hA _! 0 ZCM@(A ʬ3@/K <8\ 3@B6z@<΢ʬՓ c(@J/T7 be,!5j(ta @8d3 +$FfF) oPB@3Da1aPCD Dh:dL`7T I1&A IYFlUuPD! zM zoEAȀ A0C"3D5N5  hIbo l D@̀Fts#%\=Hmk )ZYA iqӐ1bix! b`p%+5H =$CI aBH\UmjT!Y` rbaa<`Z\ ghgڳQ/W K˘,d3'YƧje3>T!\d9xJi|<I '^T=v!Pܰ@GLg'?3 jЁYtpMeP6hYA/ʙkGun#H LV@ 3%0 `Ix!Hb8*ځA z@D5՜u]*?:ҭ,{`\1M(t .@4_ !`?ו%@* V@[ -|KUһnC[H5׏0 |H%t1H@lP,dI`vBH 6!L@`x`f\}<yww@f;Pf Ax Z Aƪ@@l0H % ,JU @ P^%E'9H:AX' Si d Kx"!9If$ FzR@(eIJ dZ,D DHBC&`!b/"!f@`*tBzBk"a&Z $z!m!o(`)B NC.cPgkoex-A@  @ " G]) Ȣ٨ ΀ gr @ @ؠ GN M ꀣ Ԏ x@ Рh `_ @ ꢢ@ b&m X@Jp @)QȩHџ@ @i "q誥*lԠ ̀ @ 䠡(*` QPTSX:f #  ! q- `H$M? b@xa> z m h!> " ~, ,z5-#2 h@ t5jh6-! ",l f@)(u 4ESRS `b*g @) ))2)@ @,g +)u@+Q+ l )))/)ò-f) r3)u*@22g.2 ..`, /5Ls/ Qh7s37O7S8qm:Xxr6sb9F:q&@; R:a r!Q9< :ϳN;s s;۳=#v:a!?y,=9 .Pr?6{6S8`>:S9E @ rD9,F ,6j >HTA(T8S 4 G?sA2 r`පFD ` @ j@ ` FIw=47` `B47C@ @ 8FHSР {b >L,gʂ $4 dȠ 2 4SqL:xPVuSNN>@JЇV Ȃb $@*n[2X_65^,@ ^ b ` `[ʹN]AsU^sWE3>` `z &Xe (# ` tI ]S[ " @R VK`b-#Vf^Oz5A l \Hg@ &F  &X[Jp f @ @ `e6 | @ € ̄ J e xE @ @ ` <& @ge Рm=&6 ,% TXq@ b 2kp ct6 j c   e H @rj`mqv  m V F j& ! 6 " 6T @Z J}*+RZ j`rVbLk emecV3,H j k@O,| ЀJa -ƹsǕ, B Ҁj7d_7 2Fed@c 4& f ̠ @ <JѠ N % 6bz S Ȱ `l & `Wxz ع8U;€ j`TUmȠJs`3澼@pu Di A V@ UcƠ`cZ8 e_S0osYw{S JnfC,S+c#r"fydٚ#V[͛YǙ pT̀8@ٝL8ƞY)sY@8Eh.nnJءuc3]mTCzlS7T x6pBQ@RT.%ZIh`Pڦ6t `54.|a2a 26@ >-Aq粃~Z׺52R, tƠ/ f Ua ᢗ SFk} rEhD:v@ @ | P " u Yƀ f j@ ؀>F b3 s'4Z@<CۺQ `S*  K|߸ޠ hj %iTMG? . ' ɂf @XgJZ!'d{ ~j@⧣*^/@U\@b ZB6f4H`B*dN/H `Z%p#'hؠDC ct (<E%|Dp9L"2"}Echp %ذJhC@tڽ7޽|7F5; 'a/2a> l)6@M>}1Bҏ/4P 61^D0x> 2SpG"v1qv%TpQJpF q@O93bb!c R@J@&iA H`@tpPHqF6G%DQIx`ѓ, S 5FO@GlSm@~44xiN*a!cv=fiCh 5AMxFidA =A1o8Al(rAhPD1CD_hůBP aAdzd4AųNPä~{wށ` 块W HI|P ؀jtЭ]3_Lȧ >^'Wy5z4Fp!EBFZhB0L>z TQA]%ePG_hFHifDбLP@C%ŔM,ThŎ9PcK(A aJ&bp~GZia%XctqZWrDL̀4QEupRT'2hQLPaC F f8ABCl@4Qf:Edͼ]x XQE4DC,Zl |o}tPt^R`-,! ]=@&D!/^@ 0/W@-L}ЂL32T=y9( `X!ЇbQHC3$Wz aAPCp WcHpϱa -`JDA4  P: QC Z,R 0xA$/,^Xb0AQ>.le)ÉqtI P4x! cAh`,!c_@`.='5AQh@ae@iϘ,@ aP@3 rH [R/y6D dS5D ]@/ax6!3 A4$~+%`` 8Pmolߊm*xQ`!1A^ibU 5h(`"l30&楶f^@ P z &5R+bu Կa 'm2o>8p^>y\|(oI  ]rBbV/2$@B9=}Az@E$Ku#sLkzӜЗ:NoK5M\ B3p5 ~ҋDi.  6ZxZ꺜xuTԀx2H"a4*A#,܈!>k. 1..w<}qoe.N5^ (C} 0Ģ@` !=z1# *X֣ `e[ׇ&16@]x_"wHMzD8."B΋޷jk-Vº`3@lGkt} $l$|.Krٶx -$!= Є-tt< 7Zԁ"B 헦 1| @@p_/1AR"2@~')ju!*a`kiD.%<0ZZ0jaJT3[9<%JZz"=%fq'&f[0j@p55Uaa AR$gh}}=N}mK"!BA_02g_A04N / &1kbN9)rR01PD@6/4`P"aeLʼnD`063pc@Tp8 XmuQcphs_0fPXaPMPiUM cj6/gZQ1y4[ēY勓"v@v{!riAgj8TTd4N8E Wdsw!@f@Z`/Gt{Jph Z@rp\_03105`Wp_i0`X'gsE1pQ ]ВZ^6bP[Q"DS0<`hP]ZIZ=c\`T]J 2JR s=pujHU5*Qa\#gWu'A@gp`U ]]2`;C]a5:J 8zR$l L TGQ7D%m^21s}w{Pd1Qal 2%5c2@`0DQ"^T%TQ0g@@@4 lh0u`IN'uh@4rO`IJ uu0P@(tP/@IWpvqczck_@AP^P$/"4n&`0! TPYapTZM52t`"ǃw=IP,f@GVGA D^:@bzD ew}Oՙi+ iƝq@IQ  %c9IzZr!Qpfp#o TP E)Eb-4WL 5gaMAPʡP`V0[@`(38L V:D0DUsQ6pD`CH[:=z3D`ZW@ L0V ˯;dH'f9p <aಜxR2EcTb8@HJpa+j3*N+x;(gl/=/M=t-Ўi0M3&IR:t>{wd]i Zh g7׷:[pYdJ`ZJlrpu%t@a0BPl`Q\Z 9 X-"J`Y:d`Z@Uٲ@B0IlP0 9Pi8:M0ɍ^g_Pct)H[^`YfTtP)"c{ZДЈߛPTP>t"l06\\t`,iJ04a6VDҐJT|d3;-U u ?EEٕ`WIzԌ{h^ n@ =jЀS< sP;[)$;Lr@h@ Jg%P1@cY~@㏞fgpYZ0t0\%5@lp&{Np&@I+JQ@(Cj03`2C,C%Tp^:`(*Z<PHP0:%`rrH `|Pfih\&ݑqel0U"y: P@X CYTި 3$E QYB)NTnbABD%p:br%\B&2@Ɣ=(%@ D@ɻ$j89+m[Pzb00 YtDQ$$r쎣2 |p zѦ8 >fiy4 Ykx;,*K5#% jrO:Y,bjglbygsC:"@`$3̖B%.0/kY0a0c4>p&hBYP[.Nh)~@0h0g[A)*CeZЮAI(ZhЗr|S94 3JQ9K:Q5qrP E(J@Aԝ2r|@TRM>UTU^Ŋ eh6,$=K X> 3DvzRdG>hBPN$@D`*I>A/-f|!H/>B䃎&tC2b8CK ~HRCb|@HO0]8 3!ŐAJ &*)S+N)LweUbXSxC >੩]Jx5SNEKt $Ef(ne]w3*bwғ>㚫a{&O *pEa_mLvS9M7xN{;*_3P8)NI9fg/a2:q+ui:h>~*z:)z_Yc5~Kj)pd4κ쎉vhFNzPA А!*̐*%JB*(*)/A)zl?XD%!s F)BjlZ F9=%&ª& ""Wa ' +<&B ( !`vxEC.#D ~St0d cL8-1C@иյ tP4P DJ`%l@ 5 ! l@%&PN*M((I&|@ l8 *AW8Ib :C<n聉3^M2\ &١_v Qfl?pF*_.G Jx9~u@0do@ MhҰ'R@%@@0)*xq PB-'0-, NPPQJ `BJ*h! `(bA@T(Θ~.,G*Zeڐ8<Uf \"62H!R@'\ 0hgT6Pn{oP:t(9iB$%:lx7xabLI-$Pָ.hj "1@hdZBT3 @`3A  ϝp]zu\"( ݎ#y _ x _=Du0`_LST%|&wវNsЈP-@ U F-~!APt[p5@ʲ%B& Ih>PZ lb zpIA! .df`Lj8H/@Y@(YKP!N PhB*ɷ1 P. Z%A^BPxqkZrlVJ*A`Zh J_Bh%<T`upX@! `ЂzP@4N-dVkVŊ=B` ۳ "X'R-"JGA i P^ЃK!s%x ӁjTAh!p+@ 48*I  з 9B f)0 D.Gt"8Vz) Hgzĩ~[]ĨB uG1YzQ^]WbOSeN%kms:=aX P WB[H4?.cHV@η |__ Ρϊ"B!}CxۮWvU CʗrAm-Tbs|o#~mV Zud ֔Y3D LP@'I+`4OY-Tx-ٖ`C #A^j?zy?ŋ{q)(a` Ђj 98 3P #RQ K'(3؂7P48 `7h#At!9sq{\&mxʂ",'4!U .4ߚ ثh* #(؀R(1H%%18<Z&; :DAHkł7SIr(-!G$PH%Y D 00@C*.P%Cn$/3qdK433-؀ (+M ;뉞dHH $,ȇH(H>dEQH\I< $;<"<9J!lHȖHKY;Tȅ ɓtIII8I\̶'@//+@Ł FƛI )?!,0"7 <'J"H;%:*C,z/G!0p h Hx=(- K1,.(I74&H3$.HؑDȑL.0Ь37H)D2=4㬁 pM 8Ax0`xh81.PO"h=H1@C 3O3pN锁D2.;0˫<Cb?9!Q"Ђ h,,:$ +ֲ9ز1H¡/8z!PH., (E ph5RDP/P$JKw :؈p/P-d*-5Ȃ,(?%4/P&S-P:0p,*h'Ђx@PX 2@S/Ѓ@=O%@pT*@Q0DU% %@ I%-'x\738R P- ! 5!5$'xRbQ5qQC7;c~} pDTؘݨp>Ta&@%8丢rjzX*qJ[)QmYٙؤ#'Q!̴708*n2((D3%n.٬ezA ӑ"d'^ KȅڵݶE1؀")$%/8'('HS3%0x4-C%ƴ\ȍ\^I\@XQZ N5DWQ + Q\q8";HɜY9L;*`".Ta"4x׍ ؙLX\)"\ܴ?B0+ &Ȃ@3jLX/¦-I ?u_,=H{ނYȄ)* Kx\_قX<4`⩸($5[ـ/4X&@'AB% ͬ4R5/ $1f-3h47fb`ۓ Ι"0 `"!`"I! P,4.MLL< 7++dѲ P00J0(ʄWb򒿻6bܓ` Ɖ/0~c`28` (@4!) )5DžJF|T:z%'0H0P(Odn])8pq&r6sFtVufvvgwf"“Y-.e0T&%% &aY(h hX~1f(N33K vB @&/Ѓ.,N3Ȃ<4h.8.=`13+xl0Ȃ3M 4,HA x.cj/`47p3@8/O NV ȂTDT8Kbb{ `%82 hEp9@mn{e/'ȅAȅA*`Q ,x^7IוiL HڞS 9&@ٿNGAwAOHLL? t<HE?4t ]NgLGDtCDuEusYAHNOiPsr)mSr~C&/hvL`׼LȦa U`1-,Z '?Y`g*/e ?i:2)4; 4J;fEȁb,A`0w7!3P $&P13hAHœbwc*w G%5Rl0&x,8TT&4iLy64hio=a&pj mo  8V/0Ю/naz%|Ov~A"x@ˎ s;h)].qYM?/A"9؊@-px)[ %/H=/`ow: y7``V5h1甊 3-@G}ɟdw5v)}A| P) HeC(> #FBad0lp4 q#ǎ? )r$ɒ&OȚE\ M.e8f'&jҜ-Ih 4JP#' 4[>)H3cie f$d 3d(5PC2iчG:QΘ5$TYfN-cIB1"\i{bqɠa9;nBd1%(hP '\PaF(P򅍒>)5ϣO~}ȕ-_i!N\.c"|pF ^4Xf|W=0!tDt1CAEhCD! ]C4xaCYŃhD _xaFQDh‰(Bdf(YhVZɤ(AHpQ%DdHU8 ^tJEh%Ai0RAф4DcRZL2w[6 DXA` 3@w!` : 6!0!C YZ`4T 10qG 2 :dE2`20ʸR٤d]))Yye~Ǽ#Bc@Qg6JAh0i gPN``A1^LBqF ",Q,sC>lsIn~tB.={4sqZR] ѓ_c]gFK]^%\8HLPQB&r J2q`` :lIEh)QH TD`|Trh^Pt0^(aX@8oN ;BMN<(AW_Z|ZD!|Q3PM@1+)Aż6 Q0`HNP/$d4jtt i(c% OLFOYd0x{1B"h#"1H H摭])Z`u+bZ/z1]pkKZfɀ h(Ԃ$R TedoP@3Є7 4`M2 t A 9PpAf  Aa BTق,A bi!AB^)S4 i+2IH `,l! 9O@ $!C|M^ b`@ %j-H+T9 ^F gA(2 ͦ 0yʀA dž OCl!2)Mkjӛ4:)O{ӟ=;+̀ J]*SԦ!ABԫbU38#ݦF͡tGl G~$jVj׻ QJq)6,a k"6],c摨C5*j^` L̂6]Rabx]-H6^kWt-&ˑ6  h ]hZZ/ҝ.u+vn݊2wP>wi|nv ?p7殺Rgm0Px-pZ+܂5m $ chLIl cnۑ@aAd[lW80@H(x  PF^BЄ +b-X(K !(DA f3h '] &la2IdpЂlpBd 9̀rЭ\Ag@r$ u㊪p]A.5{`<č= Th" BЊL%&4< T"B)Dz5T Ӟ J19^NHtcͦC+C7 -mH9 jT\S De%C(_p0'L s60 HqZ$tR8)JA<%`2x6A J6%Z.* =JI t`(L*PWP/fhe~jRϝRa[61&D@XP6`C6y3`P'09@P aeQb %86@1! #PAG܀MPpD(BA  `u)( GB&B RdBTxcjKV ik.E(p$NjY̖ m@@PlD&=LNLQYpF L@(P l @! LT  !ƀPA!l !(!@ LXA@ Pa x!" h @ ` @n b!  Tiaja `RE«PE"j!"! TW܁Q\C^P)Ԝ )8#U_1ADL$A@ PADԁTX`Mݹch d^ep`HDEwDhAADA h|x @APA!m 8h(㐁t NG*uqA J)%I5A @ l$ȁPt @peMjO^R`M~*A0%AJ*tAdȁ%T􀤰RA<85$ P "֩%- ,\& @+B\%_+P$T/!܁0A8mbkZ`BXHc8AdAՁ F5٩ dNc<9՛l]b\īDV{ R)֝UD} x @ l]bB Z'ڧ HAFJcJRR>R肆hjhjhFNhhjfčʂVZĐV)(HUhPv^ClB*0B(Q_Ii3,AbTm!EZ@|#g A(2j:BjJ*iqjD@©f"*!B**)|Z!Dag k"kJېVL%yjZl|30=&LlB^kj\[$'XaZU}+mI*&Bl"l*2l:BlJkCNnKh]B"0 k1@D!jF0ȊqD ZJWn+A m"m*2m:Bqž6׳+H0”@lHx|@A |@ T(`D` <] @ly$!@8.0 2A  ܮ)@Ȱn,nnnn.LHP-\j,h8ۤFrmȲ-UG@|A AXo6HAA@ADXlLpmLhA o΀dV:nhta-̫i` xPZxL:I&ɀp l@AtA˔B lD$ @x@@nj$ 0& @`^Fp@p!1OGI_-rl{IVUd`IJAFL@ e~D XA ƤuAA @ Ɖ$xLxH@FB.`"B"& !R V!%b -cA/A d! M b3&nsj4@b9#`@@UL $``3 &*|0_Z.j%'+kE@ƁAl0pIP (HF|/@pE !䀐Or(ܞ$PA@XPl@<4L#DA@PKʀ4 A8# @ZȀpAWNqAI $qp Ё8OPA_Gdlf&]z84AЁ(AEKn@AatBP.U)܁DBD4Bl!קּ@HȀ ^g`7=tjJD) Q\B@U!dن ڀ:'&܁= \25 X Tgd\]( VA'dx!  @40A9KЍ¯@'v[T@ t⑏%#\!x/(l9 |K 9n)h2PDh!A+\B ! )7uG Ar AtZ3|x4@4flA FH@*A(_YCYHwڷ'24law?_*_)5P:A(&l^|*#{+W΍:n# &W+B\&tv0JJ@5ǰn tA plK]B-AASCyqxg-}Ǎ'x.3}`^<#)X ä1"0B¼' M|nhAkVV ;yygDh l (A@4ACTA4dl7G|;_B{ӻ+ӏ!&HBZAB&%(!%&1J͝&;(G <KJAEt%~>vcxDAXAd!pc @& 2"铤&}bE Dhc);vs%xbK/aƄI6!ӥ+xAC1g9piKV6 @+f 0;"kB"! M.eLC$MrD 1T%HBQs+FG Qڋ!SzM 8^Gԇ"@QƘi5I`4Q/T| 2srp܈% [4F7z)rI;*Y6nQ.~eDIJd(P Il!I/V^6%t ?A076B/J 5Bb8+z;( `lL2pDMq/EJLnd<0rb f†*Ѓ _⍧߂8㸴9 iîL݂8 d xb/*60H Cx3@#xc("@ 6.d("hAhH".(`/` 1h83` Zb*J4z袆$0h7t/H "AJh/x0Ë/`! :`Cj@[&́"*C@ M1k4GbcÉ\]7e4B#5井f 9 lbtc b/` BP + &p&K %8O(J(!Z@B ׌g & :;ӠB:(%*3P' 7 P6ؠB68@,+2xCbX7>"[Z>M(Dz౿80D ]3K:6/!M 8 b !F!(hMt @x@V *D o?;[>P B`P)qg(@ (G`}(.(@)A070!pq·7@{B @0P"3$Pobӄ 0hT@@7R~8T]d?G=1#?4!HE1(ۃI=T5JP#7[It6` P3)d@d0;d,F oBJ.İ8u.V`b5^R I/H @@ I@pC8Z6 9A rAm@ =@J*aZf5  K/A %z'L  @P(H zP~2 .C4 hB0/V5P@: DS4(* M0CLY HBB31alcEr mu[WΕu]W #aI2ńt "4A XaP6xl-B@ N 39%'J=!;l j'&A /@,U( `P"!dp~( %Bt!OC"D@Aj*W B% 9%|!Z<k ^}:3h L/,"WPþa; A-`BЄ/ B/}! Z0@UCX\ =hD3X?a4YHh M~Cv<9@t8/ CĀ(d kJZ{g=eLHrDf0x'  [C +/ zЃ d0C=![AЃĴ-P_jOֺ"DBp, g KԒ(݄6 ,x nVW"">El`)"ЎжGnItЂ~.l X̠Ċvb> vcp<g8>߉-KKHCp$^0Z K=IƄT^`.Ez{@$"-zP$k9uGiQ24L "u-&(pBu7'7^KPQ Yļ %[W`2dΠCp,I/a:j Rv|Ca66T/Bw I.zֳӁu4?k76Ga3(C S/!B|P`3 BV|i(`o&ւ4`5C$(6ipހ `j b!JfgxN@ "@z`(9@%%b۴K`` ,doC*Jn4d`( GP 2p O, O f)l XBlx(Z%zP&*b &j d z@ @ ȫ @Ҡ^aޠ d@x |aN& X(B'*p(^(h ) @ (x(•c @pz ,M \hеL~1Ba~B`"~1ڠ . Zc~@/`/ q C+ xa>>Nl AXu@"`  Bp I %| ̠ H' Xf(b Bd@"V,zg&P^ab&f؄򂀣C`o - &* @nZJY؀@lh&9@6H匴K ` > A ؀ @ Ɲ΀_ x@ $@ 'Ia6@@(`(~ @3&c34p ?$\/aFB4ts8c fVC AnT($"I Y ) cB@ Q _Zhdj 9'b"@#' @Aj@zI=lId(Kƨ $ r``4@N(D'm>"]F YIK6233 `L3t6 \\$F6)Ab8ua9FP  @HLA GQ9K` S @G $" `@ `  sf @``|j l *$f@l  O$:\MU `LQ` )6 GYVu h@ [r8B@ A 0i Z`) sl.@Nrl@F+  F &LVl$4cAc9hd~ 8-di 4e^Vc neOd;Vhw18Vc"d_6iv(vvefgi,KN]ZM[!.1@/~8 'n5q/( (ab$S / b@l 4K S&`x J%$.%e _ r 3 `@Z 4Kt"A}n&- @J=$UžFif ^ ,4@@  FbؠL# iJ@ `€1@l8 & ~  ΀ `2- Az@ @X `@^ $" @C& @a'dw@x) > `@~^YУ C  K"``@ֱ/PAcT95#G18r8 7b}D3/V&|)! j@J&bt| eAt`JTcB @ f J3 L,锕Y.|% : V 2y,W{`Jz Z K0d` + `, +d ( Ӥ6~z bd`>J0fk+R r@@ d`8 QC Z8p "P P xx`[`0mz =Hx#`z[Zs0yb@3F! !Azậ!QQz:!#cZZWyttn%/e a d rU2͠ (\ld E&~yaxǎ'>#{P+l%vabDT6&~z lvm`Mbikd Bgݠ@dAcVq'NYgO8D,y @ `<谛*Xm'0{,';Ƭ3;LTu] "@IH`}@+?`@ HtO UÍȍoK"֪ ɡ<ʥ|ʩʭʱ<˵|˹˝I7䛱lJVdW:͠ (h l P&b$cbUսh|ZK\| !=%})-1=5}9}ӯ Zd`Ȁ"R $4 Q;)bܽ\<+ n( u^e>@ : h dť>X{]ۮ)RX |t& ]W]&X:UByþ?G<& @Z / !2VDv],}~^|] bC  ] r`Ꝁ $Jb7X@ b=Ԡq ҂kRΠ; b 8&5JŒ0gQK'r (_QDM3`z"PQhi&7PP!CL:Q4I4gJQB8ć4Z|2M nq*hDdR^jI@1Qɕpa9 +^̸ǐ#KL˘!̜-Bƒ@<8fL hљ/Hٱj.4#3"gLj!EL6z$r$ !H jD#(B0ՐaG@a pE[AC F2QŀBXC A$!zmaF5԰\thF 0C2p(}bE F@E 7C_zc>Ȱ_9r~5_ apd=)CܗZ!VCb7y՗mbj衈&Jf}Z (=BlQ`ۤ*ꨤjj}`.F詰*+dFhE:e>)muj)j&l`&fV+d>kگnrk[Ҫ+/>m-l鸼- 6b vpF|*kثgk+ڶ6.EֵWD̍I<ǘ DTcDWCDht?+.-7h+n;-hi@QAFQ$[PŇp t C0z@T D PA aA<5ӇEMVՐfkv]a B2<|͗3@ %Pt`NlQ|3@P1+fzY RHL(5uε5@ՠ}0@F j+PAlbA*l _0Ɛ`(@ hQA B0aa Q&pӋ*uH2hLј(b2TeGA}vCE(m#h`o6a@z P7n؄ ͓3J  NKΏr8~"`BAxPatd,NV"abAxC 9 gKd"32 G;#df X`8u l9o1H )vJ ]'1[Lps6'/gԁ28F:̑8iJMҖ4 Ia aҴ&iIG*Aqhr$5;KYk۲@=y`(@A@͌`'a~`Z BP Z(8a W*d %H4a lz4Ԁ $E _`@!uBȠH Q(Nr.J #d+E %dB-Ba^"x x@Xp*a{oC ]'Ё%5Hp CGFF>8 7=D证 <d֯!` >~3-,2q4ZGkzTک(B:(4|7D`&p ƄfRH Zp`:֩ ``Xa:`$0U` 00B9"bbg"9hev2Lf;~f3>3ap 9'y bg9C3PDFh19̐ @"=+"y j6`ӛhr}' 8 āA! OF-M ,`T;` H7mK&ąȯL.7+|Up,-:tcz:7A sq(lxX je5NBЅ 4ajxC5< Z8C R Q]Aؼ7~ ?n{dAT_!0;R: WN 0 Jh f0!%=g@!0H2 Ph!=JB̠@1%"1/|Qk [Xua<cPݎLye@Ba$ϏBܞ&$ X P( ]׻.4\uZ0tuxdI Ce|ssXCb?wx\| -2PMp TPd1uB3AxfPd{xy ~`k_0!x7\Pvcta@d6P q@up#cv^f@|0%_0^"sbt(t6ؗ81>fpϑ9YMa@JuKf@Sa@?h_30Fp#@__tt &miVLtQ&4FN`̈Q<if`xs@|(G~8AhbhkP h.PPT`cQfDhaPBPjpj`3D kubE1o@ p1hItIՑQ"9$ )ƈ9ɷ>xT(CSlK$@3HW2z-C9PlB@ ?;:` H2jlٖnpr2K?(sX-/P @x dDpI r @0%apH%p0%`8Yyj0_^ ui 0fpha0Qu_Bo0diCAMPu`uQ0ibgC<a@a^G]YN1d@8YНdrM[uH)bt]pt!MЃu t9gЃ7-ɞ5cf>\ [SPd EfytRRB:DZFzB m x-3ɗ5x -TPA`!V:TJUfFA6Tu`H!:_Ѓu'yYɜcn۹ JIJgמ hu"GrѨiZך ʠI.Jz2t |"P *1:\I G` tZ:1n(Iˢw@4R4}P0!Zfẕ  B :yJ:{I-}5)8ٰ5OV1;T| _Y(A 71 !#{A -@  O*8.%'{G`.91 RT[8 Y zGa@Xk.G[w pr;t[vW`}|۷~;[{۸}ctKhP>}dY c0td[r햲 k;[[ۻ;[{țʻۼλi ;`[z0!g ~лb0jꂺHj{;*+1[{HOij<\lLDLp<\@ U@KVpGv: N)bPK"&;- ش^~ :H;ثۆ Y "aZg |,)d&>&7~g0=3~BnB;)3KZ7'~OM2n8EWVZ.[^LJ^2n g#i&cnnxYuf >^~舞芾Y%68>^~ꨞꪾ~I911뺾뾎䚺~˅}بʾ숢|˓^~;PKotd0&PKC_E OEBPS/img/vm_image_photoshop.gif7dGIF89aiKMNJceccfa #"" #;               !2-3164777>=59>9>9=;<8< I>A;DIE]bcq픔ݮѾ!,iK H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ˗0c.@͛8sɳϟ@ JѣH*]ʴӧPJJXjʵׯ`ÊKvU2Ӫ]˶۷p-Hܻx˷ߌuKÈ+8xǐ#KLec3k̹3݈MӨS^ͺ_˞Mͻ N8o%ƕУKNسk&Ë4'_xys˟os+h& 6FȠ+5'fR[z׀h'z((s<(=)2ڨ8&ٖCHSV" $1\Ť6AXecX.Yf?N`V)k>xfu&E&de71DHviK_a 2(&jm.tr褘z)%)Wy竰9 )O^묹뤕+f.[",Ω~P`DП߆:n nB.Ih^z랎{*+p ֫pL Glo}znkhv19FBG/0q\3&7/oH-sAܖ,Au|rX55`krDg=3LmvRZEߝt|G=r'u8|}ꜯjMp{'}Ϲsmin-w}xvm,9I-7?g}JÊ<2|KO|uN_s=8ǰ/n`۾ܨ;t5X?/dZW_?ЀL@N"HA/$sa~ !&1W[6&a&(i!WZZІ"! f=r&"zHEApI[w` H2hLcӣ6phF)nx̣!=KIB%<"^$%IZ򒓬$&7Bj ?)R!H*WV򕰌,gIKXo̥.2K 0IbL0pK*AJP׬f6YMmv6)rD'8J03k狦QTCpIӪ6rȪV!ծf6*WUFdYUf4j\*VJVͫ!G@_ V`ve,a'İM, YHz -#>=mjQͲֵ59f[ڤ-nib۲um[K\ٚ-g#*溅#1]Z׺՝.a`mv+\Wx[n襮we/u{й!HJ5g_W/+aVw xk>}m63e~t1.d(qc?1,x#oc[ *|bbSC`8,Ycp^=&8 @XD:Ѓ^ A/:ЍVD C/ҖV4) GwzӓvMhC:ыH1tqW`"yc{vuq|owjT!D$يp6mg/&NĢES[̮ mnlG[پ-i[{~ɜY#s6i-qŎU,] v듵omp^">#>DH)g9G#pQ(}.fj.\!2~KLw:"tS}VzԷ^ucW`~yXZ\9M.'v-0D/ 7|x;gW/|1=;V?S'߇;d;7dȽwO|o=g՝f~{H`/$92cΞo@B (o~g/??w|q1c%(*H2QK(pq$X~|JZ"6&x vp(,(S-0X08Wp8:<؃>@B8DXFxHJL؄N(46TSx`c7^`b8dXfJY\ﲆ 1r8tXvxxz|؇~8(hnȆ 1y8Xx؉X]r؊8Xx؋X$Xʸ،8Xxؘڸ؍(q("8蘎긎؎8XxQ )M~P~ i ِ Yyّ !090 o6I8Y96ٓ?9DYFyHJLٔN$i') V . /W ia_9Widhlٖnpr9tYvyx9Q900  i٘99Yyٚ|%) .i2YɛIyi©9Yyؙڹٝ i o @ @  YIi)yYz ڠZ7   'z&+)ʢ/,3J2ڢ7Z:<ڣ>@B:DZFz=Z") N o R* oNY[\b ^ڥXʥOdenpr:tZvzxzpK*$ * Y* y:Jک:Zz~둒Ъ:ZzګꫩȑpȚʺڬ:ZzؚڊJ:Zz蚮꺮ڮ:*꭛گ;[{ ۰˰O8+31۱ ";$[&{(* y 4Q>@0p@PPI )yT[V{XK3KO[?C۶lCKppg`/;[{۸ -4p7[6qfۺ{QIw+7ۻ])9{țʻۼXd۹k[|ۂ) ;[{蛾(z{˹P{[K^<\|Ⱦ({琻K ˿t ˂)X&|(*, Q<=M#gZbcɦ6٥jhʧ>^~ 0,PRK0LmP,n.+PPX`W 'B>D^F~H䣪 P*ެm4/nXZ&POGPojlnp `7 R{NP}`.p }@>^^tvz綽T>^Z~G苞Ǎ~{>~(}>ށҎn.Nچ^~.ب~^K\׾翾Z. (跓?_ϸ^ގ妎>;z>oNn>ܨ2?4_6(A)-/N{HJL{~+/E{`b?d_3+>^Cj~&'-|~<_YO[ON8kL,G,Ĕ_RY/j/?Onr?F{4\),:EIFIȵ/ɼ?o_?ϼl9x'xG>ygy矇>!7ۺ&{&r~ 'p|u۽~u`8@ЀD`@6p{´~X?聏?<8BzP~9wnc|?w?dvEuCЇ?b8D"шGDbD&*[(H>av5 ǗBЋm{W mF6Jnc8G:юwcG>яd 9HAiSp ɸ,۸INzne(E9JRҔDe*UJVҕe,e9X>1iAay9aC|;cBW:b(d2ȝN6әj81MjVӚf6Mnvӛg89NrӜ%"qyO$$9C=iϷŒ3:PD3EhBP6ԡhD%:QVԢhF5tF1fAfev'_JQ\ԥd:SԦ7iNuSԧ?jP:Tu 42Tn-}iTsg7>TժWjVUvի_kX:VլgEYj"vG#%"1(Uvn}l51lbld%;YVֲlf/V)խ<0~ aä,a Nk_eF~xC/t^~m [vEp\6׹υnt;]V׺m.g))t׻ox;^׼lKCȭn ݾ0{Wo_Fp`7V 4 79ްa@D&̆s⃰.@W cǘ7quc?rtEGGzҕt7~4dK'>?\  kK͂ ,Ì?4L@SA(AĿCAfۊ/ :®!$"4#D$. tBS?<п+,+C:A+>0AƋ/"0087:;<=L0&'̽;(\A4ADA,L/B0lA3$ 3 ۰{1E"#R4SDTTU$1?=@CDH4DEl>cZLD3[l +DsAD-Ӿwt>46 V Ӱ :(Ȁȁ$AFsD A Gs(J{OCȌȍH9H[Ȩ 15/59ѵbӵfsɗɘəDDțj3Dvi6ui$ʢ4ʣDuIdJڊ&ʨʩʪ jʭt˰˱$YJD5c˶t˷˸}G5(,| MDYl?мkD$RB5 O]?&-JlR'UElRa J,xA-b T. \.!T789.U= 55#SADD+/.G,m+ EFGz5ޚ8PQR5SETC;ҞR(,VVEOAAH%T/lKS,p̿}\4cEDDzK 1M4N EQDVopUC??UZSY)UUcE/=`PDC4F`\0BJETY\I^Z4keeT,BWΨO-b~aFa֔Yb$#` RM >1FWJW,TReBY=ـR>E`Q5n6ޮ7>|*]`5EEbcbc#d S38aU _aDEq%[[cVLMF2Z~!eh咳^eL fDKf^ge~fhN@fTG*LmV/i6on]4bnb&q.y;gr69.fgw~xv5bUAmgwiA^fWRz&kNgI^ׇ或ghE[ShDhhnNbE&i<&hlvNh}Dr>i^.*&A)ZPʚdze6ad&Hj魦!j갮&k6fe^ʹv1븶KkFKnJ_I6l^).;f)Y&:ǖl(f&lekaℋ-eQVXQ M]36e1^m})lfu ҮUeD6}W`W"njIVn4Nݞ)鼻3S‘F=~neU?;.ԑ*ܖnnԍUW>mb.c6c @ 㘽j&D}Yn&QoHnd\`4v>6GDpNoo%P!FA wa~և'n8gOo!w^ o/p/^'V%$qeg^<=rn~pG*rt~cT~x*`Yr-p&p_Ztr@RӛopnPwq$ؒ\gyx#Gxw3g%nzz_nsG?Oxi/Μ{x|7;~9~yoolD/#}|/bj_}Oяg}'&և}'~'{NWgw~?~LOGWg'I7G,h „1l!Ĉ'Rh"ƌ7r#Ȏ4iQ@”*Wl%̘2gҬi&Μ C'РB5(E:2m)ԨR"\H*֬ZrDTǒ-k,ڳVm-܏_IV.޼z/.l0Ċ3nxmȒ'S:̚7s3М!W.m4jn5زg&6mW' ‡/׶ʗҧS;@ֱ>v^x#G?/}z͏>{W?z rx 9'8 JuZHaZj< J($z""xxb$ʘ3(0Ҩc:xb 9dr Fr<1dMfdRRdNbX%%H_fcآ* &H39hX&#ƈ#ibYgz$*Z!i(JJvaf9妕Zhk+&娩^~x'ꪨޚ ! ;,[>hR,>6짯Zꮻkق;Ybb;/B?B)f*Q),n[ 9g k#܊."q.+ /;2P>v/?Ӳ,0m5;S̭꾈ͱ> t *rM;M 58.nڽ7>9~9 /7Jn'-݆]#n;n:ᗬ:۾vÿ_?K~?p, @.EqP 3 r C(&0.LW(Ұ6!sC>\N w(!F<"A27()RV"-r^"(1f4FS\5IMlJs&8Y[s# ':t$7dΓf=Y|'0Y΁Z$AЅ* }C: 3yV4QgD2s$$&3Ҕ#eHYkT״iIY ӒBt;)Je҄TCN_Ԛ9uSҩBT AЭj|*X*ֱd6~U:)X[*VUdX񊍑|U|k_ ꕰ-_XU-` &y_++Y2vakђc(WS[, 2-lckWVmj؊,f{Y:%Ys W--jUZ^s+nߺƕhCrvmtK]̍o_\޷ot=Vn%k]{$x-y+ۺ 6/A\aj3`g`F5F+g+Wլ Y7(62lY)% KeU{;d>a*Q2c_ aN옉f4Ww˲m1m c?=C/}nhU43MsӞ4CihԢ>5SUsԬ~ua-NKzҠs]׾5-lL֔e3~mlDV6ls{6-p{.7ϭt{n7-x{G7.?838#.O3͗E>Sֿ>sЏ??O?QW?/ӿo_P% &FN ^: s@`n v] * Ơ ֠ `n nxW.j!>!F!VLf n~Y}!!!!ơ!֡!!! j"!!""&"."#6#>"$!N"%N@;PKO77PKC_E!OEBPS/img/icon_foldershortcut.gif GIF87a=eKy0K任0[¢jft1s_q]o[nYkWjVcz_վBk~{wurpjUhԀ}zwtskXùYVv؄Ӏ}zwnZde_ۇ׃vp[6ފ׃|zq]ن|t`݉مւwd˾JʽIȼGǻGYzfozvspnkzǏ,H AA2tHPșC;xٳO?˘9sM5^ְi8fK/_#f26qJ)S Ç+X"d"F D %Kh1{\|uݕ+w.&2GxYœ;{ 6hq?N38hbJz1^y{%(rxK2J.A珁-:dh.r,9i38b3n;\z '7d%^8ĄxKiYs>S5a)Qp:#͑Kh"aZGcztQ:j$Z9H)5.H)y̡R珿<& l"hyS" b,aM" 8ȜzKdf*Sφ"ﴝ'yn+p_ꊬGn/ 1F j0Q 1Ml_= niݭ;|)%x<#LpW0Iq@\Πdsz'vD}4K7viT-^Mx'ew|~.8̃nNxމ/܍?.ɑOn-w砇.褗n騧ꬷ밣^?n.|o'^;G/W_gw=އ/䗯:槯?|/9  "L:  H Zh@n~A,~(L WD 8! ,x \,"q1ahx&:=D`Ob 8E1Q` a.үQ׈B.qs_d7QF;+{ d zdXRL!!C&2,BBF"/ i`Ij)<'IIY򅂀, GU"sa,qQށ\"TR#% ;&MiJ@CYJ򽲅Lxqі*1 V,;&YL)WX Yirt6oPP hSh(?~@%aQGBS4/y!]T#@iqB.eȡQ[ܴ%"Ɇ\45=M(@&d()UA&,9ՍF3 WohPh?Lr3 @skuDPr~ݫZMx}3iHGK^(Y6%le%Kw' (ЃNEφLNȊR[']9WAF4A赚&?? VokB2Tr`8NnwKö?R^ feS+Wd=GkSi^3pt)iۏ&t0wWV$]0,(7څ +Qהu%l]Q,K5*<3P|3{`4e,s2%r0,[xMcJU_*'g5[K<?8[qG5I9r,G^` &y܉ڷl/;P:9.BStY9oZnvWh\Tך]1r)P&c\3]Rڏrx4lQS2tB(%lQf P/h L(#3" ?x1YVj m9afݻ%M{s?ta-8lk I<WjUkN.\`}c8rd^o(SQ O3)MR]5Bb疣Re=R>8+˶m ^[R^D9ӭnMu&S mtsb%AÞv02C{ۑMo~wJ̻ޑ݌v?xR|.[ϼ7gyDxO҇7WO=k}Ygg;׋^Ͻ{g{/]t\'͏|O̯>kO}g~6ߑ߿~ۿgzHWxx{ۗD8?8>xX>="=!8&(=%C+y.0/ 28RЃ>@B8DXFxHJL>x=p {,N\؅^`b8dXfxhj؅xP+@z0xz|؇~8XxznwWN8XxETzD8X9ĉp8fNJy`(  P|ȋh((ĨH7dXsa:GKpx0CȌxCur9t:ژ;Q0 Ĉ`Ќ鋃0u09鸎؋99 ,i(i9f0u8X~ݸ^Ki[N TW,Ly`K aOY~ 900@ zXXwi츐zY,c 鈌}9|9A)qd&@wGژ[UP(UٚHٖѕxyY)V@Piٖlih 8I -ɒȎ) iuP٘♞9ٙH)|Vx:M xI`jI@ o ,j,TPj  {yrْٝ鞂ٌ)5 "阎y &:)}8 ygHh[pNgf )WڟjG:9䙐92쨎s@Id:99g{>ʇC9DZ|QzUJz|_@|9xJ+9ةts꘦ڦxxyا~IA IiɤʼnOڨ)xʛM@k)ԺIpɎ) J8hj$Y𒵊 :䪲6{? [p K=V E'D{,vE:G+E8{)Ū9hG R\R{B5SV{;>+؂2l۶n{@4hd,W{vJk}wӳ|㷀;㘷 H;;CH):{[/kG F [˺[;j ;{;țP@03ٸI#[s)н @5R :؋þK<ۺ:S0)P[˿p˕ XgYZy[x,!|)2bIb#" z@ۥ eȚ:0%_0ݸJJ(_a eYj\U]AVP kڛiLPJǴ*I+60?`pX\`)J ʠlzJzhILz ,e|g,Ʃ ȷp' j^~ >:M#|s ,u N{">W&z(⦷,Nz.2] H8ΰ7>@=D~F~ڝJLP>R>]堓ڨm=|;V.:d\ǟS lk[l :j;l`.禌%L? |B ĔJqO,>Lv S)Vy(8Z[\I3/\͊Gp2P;^Iv\}5Ltz wȊBm^ K) HǥXnwlز~^.~{쇾0R}d$ykXFo~Rue|[DK.{bLu(Дd(4yXRPx.Qç/D&'j95f]z BCjTMG#!rs 9͉-Y!_tSOlWyR|?EW{&lP|!M)k?Pu!TЅ LS/ܨіC`J;FmzH AٗMLLe.o\[]7pOZF(iqbSxR%<U&Dg9!kOka>U-E8X͊SWtjud#aKMVk#e!s_ Pҏ$܋HVj] YSmmZVn}[%j[\&Fmr1LХnu̺۵qzx{ښ]z$Ց|{_Eh_X&p |`'X fp`GXp-|a ;1D.= ۠~Xī MX:J],X(mX$D@ C&r|d$'YD D ySr'>FR l~Yc&s|f40A^ 4Ys۬r3g1y3 }2 0[ֳhHY yyt-IÍm/~d!u,jӫ%զrTz֘|,hAε q=#] " ]:gDPi&vzn}$M{r"|5Z~'-l; n [W @\f~0w?Cah,06p'ZHAoI{֑Lnl (@?`;.g~+Gò}pab9Am6n<6unvGh6}{8=Exa"wv}k?sblbxvBF;N筋y:o1w>̌7#) ^'3y:Yn`|0O9Y>Nn(`:}8}5}}|54y @K?@@49D @l@B8S4@<4 3e88T?cAԴQ02A"sȲA#< B A&kB($'B**BӘB,׃@.BC1Ȁ1<þ @Ct7 h7|!ȁC7LPlh C@ uȆ@h"DMDNDODP EQER,ES97;"!%EDHQPSMLP!HM[ s548e-.2[Y]DLUIQZ  JIMHGJbae_^a0-1mlo6bR*1w):=DO݀kjm/3;j>Aifj&38A}|k5#鎌#{z}SSYEJZxx|M(WWXb^aedhD8 LyEyg4.igi)(GfFye|)}bjΝmjć*)Gz96y"qG'(:Ia+*'i:9[͖l|E)^HcTkcQKF뭥NnչT+GK40,l' 7G,Wlg1¸Òsl,$l(,J4l8UK<-DmL7PG]+ImXg5˪(* Sdm&c`lW!ijB`l , bbTthn$lc^G 蠀8)X)o#.*180 yw=':ꤋ̺Ű[g3Pr)9Nj8V=0o_??ǿA`Xa =YcU;*4 B\H|KA䤠 Uk+L9|@NF`D#bP<xaEnri6QJV9 X'Oa|425:3~cX׾Xa|25yNKGZvvIeXb2u[Y~U~Mjg c4rrͭn5Yu .Y}vZLM9_fۖKЍ;1Pv]}Y /T+w$:z7]}|V~\?>;6 ~M @Ȱ7{ 7,H`'0G.Ib qIj븸) A'6я"HN&;țPl!Xβ(O$V沘d/$dNA\9p!*rγ\gyπf2@?yl> h,$Yt'GGғH$i&k:. ;OyԤNuMjUǙq^@fS)ԗvu!i]־3,pkIm]:yf mCcC`\6zqk@~0gmҢ4YXsgzNd~cG(o$fxe9$aVm'2_kxy rFK|(˗l2(:hCe;[^\m~$/ɇt1BoѧU'zuZ˚y?q-A=ҩ.}#y4ʶ.8zۍuǼE;~'X%k.nI>GɜÜ}}x'~d/HfRR ~z}(}ԇdyrxlwxr~}Y+Dk/R6|͵z|(u|u6hpz5homxxt#t&e>APnKVz rp{RdZd @oՄNx?HiVhhXChWY& t7 nȆJօn֦v~XkXBxdh>Gn&xbi(ֆgdkZ"1hyhF]&exdk6h(HjH cȘ B0cVǨ8(HaָcƸ,֍ćwHaXX؎X(؏iY ِ9Yyّ "9$Y&y(ɑ,ْ0/43Y8Y7< ;ٓ@TA_8%HPrRh9R:pY<@zZ.rjд] ` R `u ZHp@p p ;ll q`X0Vaʻb"0İq@@8p ?`)j@ pr4`4XRU@@60`  K1Z!5!>ALC<GLEK| ^f (P`0`(9 " P@& P&@P0 yG@8 7{II7ĎMĎ "ElBlM|F<ʡL\ȕ#ʔʯDʚ<˱|C|ʙʗ=a<K'(@*p&`p UP ZE-pP@{@%0{6Ý\èL-*-< ] ],\mmњ\ -йF/ **7y@p@1`:p ) vJ-&L=&`-` p Pj MLiȤlGВ î|Mȓ\,ւ ʅֆ}h؉؈mָ<ћLה=}דٵ-Ҟן=Egpg0S n K!pB6 PP]L`` LݼG`*@GpK  z@[dM؂]ޅ}}Mwm=}=ڙȀ=֍ߌ- ח]]١}MР๬=}ڪڮ^,3@'{ mlpGM6`v`8vp*1` 0->@W 'U-ߍ#M^f y}-  \~iڭ^ 89zlR 0Rm}``|5 9 81m,s~>\ᾜd> keއ]˒~>ͮv˞{xNڄᇞH Up͐ /5` E`-lv*6}-,  ċ1mNk߿quNZw ɾ}0M^52^Y0 < P;P '! | )@8``tp = ϭEy׺&i.=]v=}8:+ GrnO/}2uN(n3 Y"e|V@p: z PL@v-*`,0`@( ).!^,n #O *H BX&6y@KBRUw]v-Tw^z= $H㓸@ P#S ,""@` 2FL .Yˆ̲PP*N .$tݕyfkK wppD+` @ t"v@;,`"bX!;cl@z`P#*&o{n^+=\ 4@ DLiVbP6/:LI#n[wumû3]p L+ 1A<L(B@hbzzK: 6du^Wfv6, sb! tt,8@(W/*P 0 H1 'Se8 :֭}X!LxBعAJwL`H.=.-{ P`&\0`+V"<$$(>aH")KZ/҄%`LfQ3S 5 AYv L ^P$>l["PS >@\  `FH%5AlL)ȄL]Q1AAVe>:D0V0'6mzJm)|a pٷaXuM|bw+fqTbJ/qm, X;~Myc A&rwc#'yHVreFYSr|e,gY[re0Yc&s!;Yk~sư|{Fytm""0t hn [q`)ONs&ң.Ȩ-SI5AZ S_5]kU#ͦ _?6A|=洈xTg]TڪFuW_է]s'la1u*c CM(Xrfm:8½mnnx1^q[ȱ}r0#䡇oxƳmntwx}[AOz7RG]7Ub{M@CD\H xѽt\k\ Wz-됇>~r;.^NOX>?$-lu^wC|:xv?>{zԫK,:OOigAX){wS^':q+~7~u})W\z b@(=gwc=VD-` hwwmGism5ū>c:#5:36es+>c7S?c@|;$0쳉1>[Y22-P+J+5s+! <H`L!B! B"\B" \B@BB$$,"?G LB%2A3|B5|C=@B< 8B. C=\1tX; DAB$$;B=#3j\'\NH@\# ^C|dJhϹ=H''LJG^+p`hT0i`iLLHhjЀHe p.ڍHl ,0@PרP`0 ؉ XΨ Q -QPUQ )̫?!Hh!]0ȁ D"hkxJy`vN!H ZiM%L -ڀQp QH7P E35+`ӥ( > 6S=ѧ8} zTyu  ă^{((OҸFZHoRHUHi@ZK^]4xx: 2%2.pSX @mQDuxP Pz..1,0 W1SCfCB v-8PBD33)؊ qHM4C&=|-(0BOmUIHZHKІi؅0x)p*%5UCWz@]TuQM Se{jYES5 ڦs]wYw]V9TYTűW}WW Co+F? Box$؁@@0PjVvLQ\NR{dڤESby٦7\z5Tj١YƽS}D?mڨ\E]= ZxZG {} ۍX`sB? 8x W : 1!ZxaKb!!8{ x")jg-b`,8#5$9긣E8#*$Er8I* K:$MB9%Yj%]z%a9&ey&i&m$eqisyB''Jݟ*(MNhxF[)F#M$**jF:FZ_++Czѱ&kQ:쳚z?30z߆ [,*{^.,֋ѩk/]ۡ(b4b!b܄HP+FS|qJlqNng|͋Ҳ-/I!?z+r.1r4O[F{tK -\L]oф3D5q[D4p{Xo`U)JE$ /xnݘ=wk*2{̍{z:FmJ +ݒɽ`b/xJ. (h1R^rҸs8N:M>՚[:]6[/z6 [x(J9Jw@)0tJ{%NYBg U{IBXX1VxbU?6!s@ ,`AaGPaDJ`X!01!oj-r1B bЅxg.@ofK9"шA ggb(͐0r#"{,`6aG$r|c!sD&r FbB@O;yU'$'8;q.'t0& hd%0,bJ(@$ H`(/ސ HQYB`F0A6 Aw"0y@ &>u3̍ P0EH@UHM.S6  "`pa q0E00LN; M 3.+,@"0"yLeq6"tZ$X8@XAfh,Pe8a0fÞ/*nԩ2(A$ @QXC5Zwp"AT f@3H psr*K*/Xf6xYg4mxSFS7\ h@9T 3 ]b)Ƀl@t(%s_\Lw=ѝu_$֌ pC20 # X q@q d@#p41unk lR&ٽ.kFHv7"a@x7Ii\bbV.H3#/0c8{̛bd9PɨPlHȀ (l*e-0>|@EU!$ v3ȑ-eӒ1o\c\X&#sFV\8'~pASҏ!hskbބ>5O-~6'`F,0&TxN[&q`C'X w}h* Q|ؠ&n.qaK;ԞV.+vkz19tɭr$wk#zӚt'bx zhv{xԔ-2~)LAU#AЅ&Ԝ'|ao%`PA{$,^`x0a T  =<([|b?\\0q w.AK~7/v\V\w=6zjO8 {>O 7;YY0@8ȗ31Ѓot{@PVa[0O$MDsr]g.rIML]w1Ǿ{;zfp6xmu[ ^oji;{ d@5q^|*hB,D T#%-B(-@؀`DAԡ9 \*1% A[I׉[Hؾ[X)!`؏[qZ͘Ɛ4qAe1!*02h@ 0T\ X)0A $ `D7,BMDuU]L[!FAĕb y݁ݹ],__!aa4A@A*a8A <@L  BX#@ @ @ ;U,BM\ +&ו,F-n(&\™""*ʢkx_1 R$ɟA^"G"/cM#΀(ca3BL4aL`-@$@B!<!<=QN@(B <$; Zc@[C 9EZ(X0c?D'Ba[^&[^b5aZ%Ř]a\Z[%`I!$?B ^L$! !HY^(e!$%*Ă.7;C9$XXN Źr!2$-iX-',C-E"wL XwjR\2@0&U1C3`"'$g4'cJbfur 9$R\(<PBplB!hB(`7<&*\"L%~CPid^!J^&-YĂA&<&|/p(p-<B(|A{$A d5h@ Ab'6iLeJgIX ` /D@,Ă:$@B'7o64/ "H`=@`ʋ=R#+~CBAB p\B ~ UFy}`T>?~s@P0 '@ 4ͬw#>? @@XA`D,`NIrJ 2bD)VxcF9vdH#I4yeʐC/~xQM2sچ/@żbrXթSCK<51 KJ?|Kcɖ5{mZkId+@ 4iz(3n( fрZ:`騢\3þthѣIu s?`zسi QܷsAxB8% ORU ;~{vŞ Ȯ];ܵoa'3?.F VL*V\=-b탙(4 5Pky"WYX1  #}É$ t}ȉ d 2-*⨁٣ ,NXC إ(DqƉBjp O "2k԰ w dBRl$"J%d%oaƂ[!BTԇ;\uOՇ@4b`b`b@%,QنSGTPqDG*`jXMr@w|xYm=kI{-W"~1$o#wU״`c x` ,@ hw"yѶ/RJX1|ʨ|`vᙍy?".)ߤ;2H_ޗ"+:W,Z$'ZGlˎH+:m>[~F+avx5~(#00AjB%l-PP*"hナ^'2:%~mLj\=}$}k?jo]vmFo/b~# !P Q q>$_rmSr+]T#qԭ#DZ kv=xNk%6i!Xmk. cH,5]9H;v0y#7lBkwh" 80)@ppuA ax`@| @!YB"X\JD0Q !]Aְ@PwD08ID^ D%ψ&-B")ZZ\8 (@@1 g(r`bp-e"Xqk:]qKT^r##\^'\4C~ y}"b/y˷/V#Df.43#p" 58 8Q rY< $TnITCT `@m7xHs%ԓiZ(4aԆ h v|,s8CfTc^bJnn'憼ЉfbERe4 0>@h:`6!48 z ôs(ʻtBYkj`xV~d'=:Ҍ~}0vm)0^DZQх * 9a"hp NbՏR G51\!8n);ýi|(ڗ"i^Wn&d3#E.c^n9T]AʖR$pEp` ;@D bԀ cgRHGˬ$l"7Dw h_} G+IQIbkYS;<P@ū`U ',R`>+io7=QUBh{ $y~CM * P@- o ] MD ~6` !OGPE/"'| j ! .  pt ֡" pМVh>,`Bǐ UXR 1j ( p\s R   A\*ab4a A L!c, B`İ CQo S"  pTζ p"4A\Ja d!A ! ^ @q{Q@ , N  @"@`* }&@ ȁ$E 'BA `P 1`zm-? $ 6 ? >0@ l&f@`a@@  ! 0@#b+A+O$MҀHb tWE@)& 0! @bt@Aq^A ]Ǻ, 6SʾR4/,K^2 4, R. p&Ip7 ! R @*,$+N+4r4ÓWH ` Av@ 0 !0 ! bXe`,P PLA|q` :Kӟsʰ,SD?4IRn !`^` $ #`!@xaR|1Gw@  CI;Ƕ,Ȣ(}>Y,͓t,  >   ʠ 6d )> R254`GL+MO`T$ E[B @cX& Z&P~uGo5SWQ,Cp@j|@6@v`RS+M;ECUu,_'" N  W13i[tLM\+6OT5$XW!N` !dOdy#NJ]+:&eg p` tHJ-hcABct_> ƇE6")0eydAk@ kM Tc>lPVv+h6\#4E_St__N֑&P0L'@mqGm_X5SWaAX_rrrW_@ 0_ dVe=ꬳ FE`1B[ x|K+8US1,7߬ 2_B: lI0 g8t-w ] @ X@c%x (F0PX" 7ENWl`9E\ 8r;τU$VGϙώT$cwFk9H ! i@#ءņRrE,F &%E9ZQtwcgV#+cUЏR6ZHHX%1kG4kSICS&5Ȥ9h%r$6ɸ!&<RR&+YYb.gY|IKʼ?:A 2T[ю(G%a CF|):)<)0g(y~rp'E]9ч՞FE 1?Pc2S**Oc҂̨F0& pֲ F3 ` .}iLejN A<;ӧ}>(S$*@GO0H=sAe?WYuBHjU{l6s]f4B2H v֯^ɂSl Gu}.dP쵏j\VFvvhDJYb.tu Pnow8b1W%RGy`)= ˏ̮[>0¯pEY֢aEtͦ@ 4"wk+@1S=}RK: 'kff[2XT9 XβcVWA7~9WɜFS&Lg0;kF*MK I|f3ǂkBGxxim%Jf ^N~FUV f6mF@εq-87ZkkN0f;j{i}]Z ֶ0%, MPvV@zG;Y:4slc;ۺ&$O8䅆; \֒݀<*ȸ7K GN(OW0gN8/9d7 HG!@ p\yI E Ⱥַ{`NhOpZ!۽BϷ xx'Jq8}!x'O[ϼ7{GOқϻK/~o|/`ϽXU_%ރs{+1;L ( @AGKPx /O~_7Wxkib~'81P& kPUXx*8c#X%hȂ6x88}/(H3'B8Dx%.[:/D+~A+Bp`E۴fp@"B j! @bȂ&\[Y"*bEmK9ãrۮ+dkǢ[dʥZebwe{pYȚ::t*t:z+&)Vꤧ[˷՚ik,%뺴ꨩ;cqϫs[&˸ڨ*;U Z׋;c{i˶Js +꼱۬{hb[盪*㫼ƺ Jċ [j{ |gzʶ%|{Œ̬ˮ{ |)E>-ܾ̹8\<,Q Ō;cX,MW*9뾃 qkx ZJel,]:QʻnǻK}Lȳ,b[0lz[{h=kDž L}bV̿uͷ4%zݢ;\3 lH{G[ CjK\v-AjغpiqOzХMΊ\ӆ&}]M6 =:^\ާ8l]&=߂M%]%qlكL\}wݵwL䫧^ݨm^]: ]l%>uּ=,l+&C ~N[ͼ{Ɖ-Nď֞$i OMkN&W 9PkkNsz ^^jN~=}i]ؕ\Ӣ [n|>Qf}Ŝ^VN)Nܧ~w]ٔ}mx^K}D;&Z;햮ѻؾΆ~xccK'WRKYG[ -KC;{=+ly`LNPR?T_g gB%dqpy b?d_fhjjw\@(Iϳ\ppxz|~?_\[߭dq?%Vbݚs?/rҶDߨ?_ȟʿ;PKv+G PKC_EOEBPS/img/life_cycle.gif/BGIF89aTWxvNz2CgN͏ѕd5%A!*UzCmrDiQ)ԿԜ׃Ҏˇ'Yҿd)W&~'ց8N1Pu9)yB9HEȐa8҅~ӆ" F#/x9Ӈ()f碃ZF˜cO$z<#=VyAN',xd 饔4I$QhlPK.$Eآ0IguXfݖ`z)IvIh 梌68hf_J:d^$ rF"jbJ*Bꪬʥ*Z)gj%~uaj]dv;)aRyiylAZXg>'xN)3zk.:TўKn&64en+9-B D"S6,}/E滱,e&\a)W.S2'Esͮ\sH3k> QBmZ1̫B,F% hLWk)Tduלe=- mjSf6h']vG6wuy.xO7M|oKLOX _.S9ßHe騧ꬷr'>c ^20R7{§Ml7g}K?}k[;'?Wz~/|H@ ٮ#Hѯ3A] CHBl($S⭰0 cHå8ȡw@ H"HDb WrBڸ|PH AX"J8'V` BS`Q&k86+Ƒ5lG9α"#kB~4# C" $'3.#4#(ɷt2](wrK/ɑLf{,?ѻSt-Q;Uq%i`Yh4(urRޒ-iH_%aqYL\vR8qRf!yMlZF&%YJtLX8O~l;!"e2O}ğfCPE$/YNi泙)*͑zHJWb?EGC)ːlhM?ҕ.HA=S7ΔCjώv']OTs8EݨV7ZQV'WMVJVN_}P;3ֲU]M+X3ʷuq+:̻yjпg`޴-_`+)ըd.}ˇF6a˛ǚ*lI*LYuzugALca[%ǴcmN[F&'3{ΤR]+gYRW̭vKݐv7)׼mxy͞<7͔KV{x,/TE)w wes+<ʤbMlJZ\L]MT.5 1~[ 6“kwJ+Ă-b8d5ɑY2dBy1R򎫜++&Z,Ā9̐sUˌ3j*75.s`lgzi@BЈNF;ѐg͑ \%1mdARԨNWVհ5J `]Ǡ2S@Ӿb:\\ ${"E?z|Rc#[FVT(qT" C,!zV iwcn$;Q!Xta-000 \[zB<:u]vRB @2R00A(<DGV = ms򎴢yzBNCX:ԭ+A ꡁP0pnqkG* `@!MJns$ZG%2SN,'&w_;9@{onc< ?{*09P bi'nuo=7< @{:dRzmE]lv締o &| 5˾z+xO['M@BX?ׁ \F4'} F `} 3}t}}\W{'WGx~(~~&  q77|0qLWF]0  hzN={wȁU{{xgx S `  s#0:2 07Wppr 8zO؄DŽLxRx ;"=t`2-m7 y*| ysXp }(x~GzWc1  ` wm ] 5s7wrHvs`/9߲)V%Dh\狅᧋苋V8UX/Ha b ЂoH|0 xۘS0Ld;b[AL9;GrHU$dYK1vyx+ -- 0tq HhSP& x3'`R(({-Q(XA:;';xv0,208Ѕx7 צ<[EyS@*P`LN-RR$Y,b $Yy [];_RY) h| 7p qG|`i0U&R(2(*"D;i HtEYМk)u.B/(tnpȖs#pħ yy&KmU+iO3¹Av ǟC!-TrqhI()D詊z s 1 &IY9X&ĩ)ˑ4ڜщ+b:r4ٖWxYz @ }0Y9UJLјoqܷ{wwK+'it$:njGzmqJU 0ڑ(yiW%0`W~ 2qp!ڦR/8Wr 3)5v uFɤJp .d;zx{RG{{WǬ~Z>q@yjGq z蚮꺮ڮ seGeyXh~'*د:GjE**'t2x pv{zbS(8kh)V鑭Ѱ+୮ZyI0pYi9 @a EPCpPKK`N RT8`8Z? kJ8~Hc x"{~+Rx +!06s:IFڌ8+;۳? A;E{CLORUkXZ۵_[a;f+ͪ{˶7u  Do 7 ȳ> BKFJ˴k븏 rثڱź~[+ KF k?.u[y>׷:k;kIۻM۴۸{;k<KQzZ{T{ٛ(p+@j||nsGF| @`$ &\ (*| 2,×Pup uu;>@[q!1 | zq w ym`b!$h.swy;ꬿ`k@B=D]F}F HLNX--nкolыp''d-֖@ 0=pq'nP'00 ; gХ}̽"P yx xA $ˠ=ˣ=˥؍gp;r0 Yws7mpm >"p 5` Xd} flb-M΍} w005P$Xڥ$JMwZ\=HH0'¦@~<یN-/mv <45 cPln=ƍ Zܽv&Qe >A>DH p5 pO SZ<^g`w  DD 43l y`yN&oVvvq sԀ~j;̀wp"P k0*.N=݀%ުfި+zr0y>p 0 ~ >Iӎf.) sJ Yp;@N3p" 1N_n`s Ao 3p  P @JɄ',,$LLD "YH @dϒ,UXҥUf͗*]"dAu"܄eC׬D\MPױw{d2[$]/`,!'*62Ȕ%| )RDT~`tM\@]Jnښ(7Ƣ 8fS0B 03:өIĨ#H;W=DT>{ |e &ÂXBOzjqJ*]p25M,ɚ00+a9BUz{ac vf&C/I8C* ԻI\tӛL*4L2=卭Ӫ-²DÎR?]nM)q%QWx啄8w:a%1'aqDa )z@m4B(2 pq Gx>TJNu%Oe|KB5(W/P^5=| Wu؆!>ׇxΗ]A=ؘaGBmpSIЙe)wk4^sֹ*ZuY .M0,bv#V4;+D`>\>3qđ+D rǶfg:~펍VΉj&Xc G& 4pUIeě+YlМp[n[o[w$Vhbz';*G 'KgsGNioRK}{V{}h&i%$5rަ] -вzJ&A+Zk_[%~ aml_N]lg붱 aR>.d -m| h-w+>qr?Tn%=op!Yhoe[-vŝnܦn!6A\ W8rׄ t_$nÊs۸;mCP~k{9ȭNj;]Rmw]gt~ =EѕjBmkf9 Tt{'G9;IN|$v;Nx6۫i$u`$~l~ر}y-k'xQnwx|mu x*7ӟ^mc7^pa?֙_,q>Z?JS_ٽEn<=e^rӿK??[?#Z?dӳ>j@X24q[% @4# ܐ. LL3|AAAzAx@/t",B#LB%\B&\Al&B)B*$43`"T*B/B'|@C2, B4|:C#;q<+FfEEjŤbՐĘ[ q=nFwFsDt F?m|F pqT9^<,A:F?pGqr|8{GB<+}>kFd \ aQ:@V@Nb?B6d6LddtAGC>d,vKddK^dNdOvaH))eBeSƴQ&UfdWn&UNY京Y[bY5]6^e=dfbF`e.mg]hZ]]fl(djsd>opfA2gsV-hfw/ryfzi|_F1Nx*hnr~zWn2F~nfWvԡCֳ脆׍\+ i{-i~*e1vWi5Eii|i6 顶WNMj8s0*gj>{jn֩jKӰ 6k]mUfnT36khMގV NfkgŽ3^;Ή~vlh~ NV®SF~ vltm.&::xj^mV~#Sv&f~ffFmAmeV N6Vnn&&nn[knng1VZzo)2r2oYo+GjBpopw]-2v maȪh 6g-fk6Z&5Gqvp + "h*# l%gwD\2*?9r-?A|{r0Qr4.Ts8n5?7/ 3/> [t@GW`hA?B"Vt` GtO5xlt7cvnxktWtHOfR'tSپ 6 xu_PYJ:yqVuWv7v)/he_ fwvXh0jGT`^Gvp^lvuWnwywxxg zWJw̶wmOwuwt h}w>w_[xxxoNXxwxsj/ljV@wt 8y(qdp蚨x tgxWWtOxfxGymBzxyjyizx__Űywv0pLO'ߋgy ;K|bøq0y^ 5@{?ג{tWɿ||ͧƓ|c7}Gԏi}W}|گX4} !~<+}淉c|a~ڃ{Bx7Mt:gWey "a „ 2l!Ĉ'Rh"ƌ7r#HF,irȔ*$A"eTH&Μ:wCB(C5(ԨRR:QhSZmK.W:kֲ-T Wo65ּz{ZR떭[*F<6Lj}̘̚7s&*st ˍ|i£g~ۺrˇAӮmvġy[5p׬On[ JѣH*]t%ЦPJJիXM>ʵׯ`ÊuٳhӪ]K,GȝKݻx˷߿ LÈ+^̸nExL˘3k̹s# ӨS^zhc˞Mە_ͻ3֛vfμA+T؟νNKuDsjOv}.'! ^|v!XXڦ}FH[~s@vEs\*bȚtuaF$U0H9Ƨ` F$s$=~XdRF\*F\׉p( a#J&cV^)el?jʹs:Iq)(]j`_4zXd Br&i^yV#n:(jj_Z!yv訛XRi)Z'Κ䝛B둒攧klh-(U/񗮓R˫jqkRu`l!|`GxJhRjk[%zZnwh"|]v/\7|V$oօ+t?r) r B ?DFJ,gm,4UjW PguiROmoo-ئu=5$ln-pmǾF|}k-&k G.]9Ng2Y砇.Zn騧T骷밿zn{߮K{/|o_{7M?/ԗ}gw/Oh@/oǯRȟHL' ,$s'h/}4y0 P 2'L MH;P!#`wAbsFx$g! U"R&z }5+tHET1WdLELq$](Fg! \P5p@(G9(G /| F ,1#t82|#$RHhCExtR/K*HE*QsGd^*IDR KEP/p,e F (s@d+JXDIhh[zc0h!8b΀0,#ڸg.sM5N^z1|$8uIIl^@4avY *P(ӏ8LE''ť'?I͖E1hb[4z)C2HE(@&:vB\('Ο2, LSt"V00que-NZwC2G/ Bq0U UHUU}+\bՕ12+Aժ `?ӈغ贱 f-k < ;`&[I)ػ~YGL/* TMe$zLcxo߻`*K\űMbd|5bh_"90<3btz\E p*B&L_'/ZD2/\gZ:xI<EF p!8XD+YM4Jӻ|RO#`45MMR.B|ki#$nuyk_ѻ6{*[3~WD2X I?*byӤ]Mek=cGMc  وzq2q<7NO"z|&xk0nM_\qx? !9,_!6#@XnE2#8Ij  K9ϱs$Q:onãd}ǮL"m׀!vh:̧%|t8D3>0'wS<7?>s?<3s>_;SJ{{'WF`  )>ß0!!AοF>Gy~~wYY 8Q:Dx~''X55@x#5H3x4x!1r8 oh&Qz{y؇!!)%ZY胎؅X%1$(:`f %pA@"O~臅x(YhTAG~r@P>+(,'88ȅȃQ!$ADX'lb ('8HH8!x't b؎͸h؈(9FDru(ȐX&SɋQ!kH_oo_&II)H .5\Wx5 (IZ{}{ţ\ ^<`^LƸS>>XkZ[kpl:fr7U[Ȓj}țO\k,^:P<<9åtʗi|ylól<|ˇWs˓ˎ ̏'̬LŜ:ʯ̌g̺̊,Ӭ֬wԜlx݌͡}G΄ꌙΏ\کh⻻щz%s9GXQ}~ŗMgͼĸWЙ6ؼm¿౴|ο-Ų̱uvzwvPO. t药ͦӭ5ί|뫫氰,tͿ tˀͰ!,d H*\ȰÇ#JHŋ3j4!R|Iɓ(S\ɲ˗0cʜI͛8scLdRQѣH*]ʴSXXիXjʵh8tKٳh_.:#Qڷpʝt} Lˆ+^<0ǐ#u,O)c̹3M͞Cʔ2SD z4N0u4O]:Gʓ4))~JsnylˏF9vGyBA  =Ym扗42:Oo6|c$%Iґ$-6A򓠜#"H19#QKjҏ\%<Zڲv L ?,U@j,&1)[:F.{K`:p1eLeҕd-Irư%IƒL%'iN6Ӝ =j⑝o3<cr$hsƩφBs5GNV&3InbaCGZQ)IWZH;eTҚҤ0uLEGST.iv6xHI `DR:Q!Nz` X**|/KZ 7p[J׺vͫ^'׾Քx`빹amdZֲfzhњ=jٚպVx}lwV=mpvpw8:ǸBno{[Rqۤ6R׍np˺7S.x6޴Ywr+/w;]:ẃv n׾Eo~]ⷿo}]xo^͵;a='`v6g(nٛ۶y#pS cJEi8}AV!wU} |񇙼 2押dJβacY@rb)_Y˕#jev+<4fn89wS>g É#M*81)gh @0Н=ni_ RX)V[P y_^t A >osGzm `{au}{?^/`y&Çh8Q8hƨ8x:H6؉1h[Њs6hw~8Pp؋MX8kHcmh;`y]X7lB@ࡆsÆoq6sxјC})ӧxx, )9*Xm'u3a*:8735x9oÃ`B|MyQȕZiXy}~Bpg7~xssۇg6W;: |I ƈx8'IW阥C{ɇ{{W|gps|ɷ|K })GyyGz{y|ƧzWlkvowwvwzw x9rSxx#Xv&DԇpfȠC}+&DPɞlvp'wt7gyßxg7`p,p`x:6yyyzY7{970 pHl9|ĩ{i{979|7I-|)6Sw76W}I~~~oFz9@I:3*}Yu5:8ion~jI2Xh-r)7tYncIz_jK隰zJ* p咨0kcX<)7EnIZ pIzȔJNØ窛ɌljuH )7  6apIzy eZو Xi:(yX7ޘx~H7yɎoH ,ЎzɫYjɯHFn3GJz 7kқ?۳&IA˫#X2a8;I7 A 6֪zZ~Y6gZ9Y󘶼Xb#Xygi 7p E @뵈 ˕dkӦ))򗙳(tSnڧ n#]&[ *9HPˮB ;Q{Sj7w?j|ȧ7]Iy)۽z9 z;7˥Kڤ`l)xzcu-1忇[g6- aKöµ9l[l 7z7 0**ʢJ<4*úz)7Aj{Cj7EJ*r%,kk{ {[J7 \rLnjJ'LY+}k7W~wz8q `a9p K$7Ȱ:JmȥCuʊci7ҶyԽ9\F[uS t6кSVY[ +̋˛Inc PO{n˅vSr:y6 M L<Ό|]˽lHwO9|~uC)˾\Ӷ˺ˮ۪G˺ 8Fصֶ{뀌[<ټ 8L[Ҍ 7˕FzK֫7ܿ{Xtϛ=v]*:izkzml{oLvx6q`\g)̢ywp+HJƝ۔7YA{7Ez"'ݙÓ0f3Z2~㯕:Z<@>ZB>UFYH䗵LOYN>UVXX刵\NX^bWd^{uhWjunWpo5tVv~iz.<|;>/芾莾Qn螅qNWN蘞难NTꢞTT>ꨞ#U8uL>J.~4T>F~G>D B~FCBϞB>~5Z..ƾBՎnSھDBN~^NHCϾԮBN?o OGNdM~hl/DD`ro+dV!he%Hk ݍe\ܨ[;j[Й;`?vF'=o u}  L?:OVbedWٿN=/_> 9"]`y Ѭw7Ҕ$J AB[F691LOiZS 8"t:AG&j7 ?]< K4ntYH*.Qd!G R&*H,C͵EOiP%4# D"4Ōhh -BIoZFQ*!-HI Pt)Ui=YwLYSz9Ny:MԙAj2ZTbTRuTQTJ^ՔYj(UN~X%YV6i}$3VpM\U{k_W6Ʈt-O/elcXF0Y,{YfVlg=YІV%miM{ZԦVem0VE[{[Vmo}[;Ím{\&WeoKӥnu{>.v]nq) 2@5-{^w-YWe@_X-}{,{X` U9_nEa X͵0t1_X1=\cӘ9^q}\N`C&& ؽMlw5q|[ GFy`%Ø01akfhe#6hl)ΜpgX\殗g2/y73\<ZҒ0 O$t'+:jtb&ԫfrQ]Cճ{iֻ5o_-X wu_Vn6A*cG[ڟM6lߠ`Z#sdmp[ܑd}t&TCwM{ߛ3oex(,@ gxpG\_<x'nq+D'y#rm? `H­]rC7 XCV3Bns)wt'=YCt˖N?zԭ>۩皚 z]pJB><;[oy0w)x'/ Cv7@wl%?llc|yA[y{z<ئ^{𐿵n|><'&aH~}?=ozKG=owٯ>Ot^oӿ=>+>þSD{Ծܿ @:@>;@ܾ >c>@ ,+@.;A B[A AAA "4 %'$[=*d=P>.C,B d? >EDtAE`>`?ރ5DlDNlOMBDSTt&LL3DS,EWPY:Y\E<Kz[3`a$b Fk:#t&'`9etSg9WFh-l$ K%&p+09r,G59q4Gw|8tTG`wsLZrE}%~GVG<%HQ*H$LHL J`r€$I8&:Yi*? 9,@2NH R@@III JJ,JaУKNػmG\u 摸Ə#˘l̛;=iիZlvs& 69݄Vhfvn%]w_~6a!cA&efFZ lFmG@L6䓼ITViXaw߁(ވwz*b|/ٸ AIB|٧Y*蠄zݖx$gbz)b-G}2W9@ H&穨*rVYb謴:}8ע`ט^iboz㏪9`"V@v"8"  To`&oD/U^nUyEjvn 'a*_ը'왎Y }4#;.;F0,nd:Ϸjt ]e6BAUL4dE5ӌT)O5+<J`uUkq$=h=weMeh FfR|#gZ' , P"jKAVn8䮻X`S⾻, aw XyKT<-qU 8Xվ^fLQ\&kM2YRfNZv3U0UDNhS '0{AfW]ݻJ#%u)*ŻT+*XB^C KAOQe@?+"h/,z_uLzܥ89N,N Z'S%g M )A1  @~ad" Hu`a@C)>!V*C*[V/v%Q,l{@J(ζH 0Lm$H=S,3*Lb p4@&5kf)DSOaC+X%U$@uZV13FC>*A/F0ufūB̩g#gYUOjZU[g=r‰H?W@X *4bPI6u,$! I&,e! F]c5ɇ.V,cS{J>emgY\`C|0ҒYJZ7<%TC*StUy) v> Mx'bJM+`1d{czF6ʌ/z6Kfw]طi~%0߱ ҡ\/kcQ8t$h9k(g[Zz6,~1"C8.m"_+c嬋g{xk hHO*(5XpJE(_OI%ؠrDL^NWӵ}a 7ۍS̺>|@׿ SщA \p+ԕWxհ^2qȪDŽre8~1VxƠeu_Mkڳ51U5s lV;JFB4MNVUBaqk5p+w庲 ? ȀT_E>%ZbC9Th|G8Mh/V+aN;ßEM<ɰDUdYxȌu-k,5] 6Ϲ% ꆮ ' C\6b+n *GzYINskTg_EOo/]rwcx8<KwYbT7^9adz9qN 9G|=@ x l ' t md;rХO u ,o;a6~nǙ*S,fXL\Cgq~oWw+G`Uw~u6Hx\axwaOW"#Pj%yubbA6[%dkeZ7WY#H[E[&xkeckWdDl:X[4#@"@B"3 [NaPs]6lHq7yVh%xpEgp x8yFiXu4bP2"$d r:!AtcLX.L/2dCe6Jw0 #=CnSYKQ!ER^t6&zSNhLwCL6t٨S1MոohȌEݸFa\B88sqg'XwP&fj$1HA< )s93 iXH9(FxHjgPqrؒ.)BA 0(hS.ב<ٓ>)i!ɏ$GX5j%VjP/P  X u"$:`b?(j􀈷aDWqQYvs A0wec9YTxkxb8)IyhywY% :B)ؘ&)(*9uY9WOj9@liG)yqٜ9Yyؙڹٝ9Yy虞깞ٞٝao9Yyٟ:yz ڠjoP/ڡ ":$Z&z(*,ڢ.02 DB q8:J*ѣ@B:FjJLڤ;QPR:TZVzXZ\ڥ^`b:dZ6h>?Jn GzJ:vz2az|ڧ~ilڣoA]@Jt:ZzکZxZzڪ:Zzk ڨ:ZzZ@ Ь:Zzؚa:Z Bګr :t!:^ 0 ;[{ ۰;EʮK#!J `(&{({L`PQ:  P  a>B;BkDJL۴NPT,/af^""0`-; Zʐ"p p ZUKзDA˷ ۸;KX; @K%"`fbKd[pj ʀr 2yyp ۷˻ۻ뷔{țʻ;qOk+;bqIF(&@&kOᲩk s E  y`4A,L;+ \{|PW`!&&[勶{  O0`KALa <  K||X,˽[]ӻ!e!1Go们0UP~P @ `ZQFL ȎRlFLEŠ!|{Ʃli n0!ulx, 0py Ր ` ,0 qN,M1ɘlę\OD,͢ʦ`ikcr{s(!p˾ pp` ƌ B  П А ͑͟1Ω\Ϊ|$lβL$|ϸlP }, mРPD]ɝLђ\HTk*ҭ,X}+mL|(@h-§KӾ< p = ѐU|ث`ƃՃł#]_m!7C$KhM!2Q   ~}ڨ )L-0mlϘ] [Ƞ`01]}flfp) pٷ * 0 @ ]]]Qnp  MmMg3 ~6 U>^Ժ .q$^&~(*,.02>4^6~(^;<>@B>D^F~HJLNPR>T^IPZ^ \]acbh~jNiknnp>e^mNwnorxy耾~X>^~阞难^Q^X~>^~븞>~셙^~ȞʾΓX^~؞ھ>^~^iX^.?_z;P)0 "?$_&((._(_WX8 >O9oA>?*HJ,NT茞T>d_fOMjف[NUq^E_wv^ux{O{_?_ln)m0o)|[zO?o__` )_[џ oo___? $XA .dx@+XE5nG!E$YI)UdK #΄x``9uHaЁϟ  :phB&=T)ҠM ѨS6Wa<91Yiծe[qҜyyw0a|čFdȕ>gСE&]:0وfRT`kرeϦ]6݈쾻@o| űǺ{0щBy/Gsȓ/.遫7Ͼ{巟=j[p@_í&TpAA#pB +B 3pC /2"^@STqE <0:\AkFsԑCDJ!Ysm"<tI(R,/K242|C BÓ[n]P6^iQp#\#9ڢ3<^jCB?d;&/ !7a6}vگ|$)|+p8 0"9:yOOBl֫ucwQG.rA RB}daIr6Hr!h#8I\r@n{Rpl(xEUV< ] $uyMl$| 8cnq_@]f86`0|&qf?mvdP:F@>ڷB##Gx[JT[%ǥ;@"@ 3ŏx@ J8B 3A`T+iOEP]gPQ"qĨ (Rͤ^-"#Nv`UjY#n%39qj+V=ZpoE{HV6zh,L2b-lcՌmhEs,K:&QkjІV%miM{ZԦVemk]Z؂%!,Fr7v#uZnzW ozg\6ŊBgH73NtKk"Z;jWv^nD8B)oigJTʐw_fY\}HmV> |D}K]kPYKn"qUT:>wd)~Jf™HN'"=b9ch!=x򻰏ic@>/ V"ٳ@e*& )@F&,N> l^tм570l&V*n=5upxKȂ@.R&c6+.GMFcC㝄WgL%Ȅl}L\XcdSVspo5lXUk#)u[jf1x1Qlipy: N"9Ll+xeME&.a]FWE覕U¼HHGz`0F*H^r 噞󹛌Y |QB:W5K4낥y9V7*iv^b[Mرhh&go{޳^'| ۼcD퉿w3^3<|翥v ^w|߉nnϧOw[)^/m++nAKu}O+^E :ё˼o7_^~/[''R~Ed- "Ydo}ڣ>L_/$c";:{<⻺?K@o1k# |@֠#Fiy@k)\Ap?ʿ4+!B3"82'2.20KA4TA(dl*lB+4+4?\"CJ6hHC3p4A#4CBC9y?jyC*-/@ӳ: ,3GG܂7<59JUkWCM;B)(?B'EQ4CDP71VwXDIťJЉI%yhj P|b)De<*/@Et@Fu@K>Ӌxy{˷}O$D:xAcOKxqSEVGOtADŊE6BH=3(9A mi | knaFT)۹ӏGǸȒ IԈ󈨛:jG IɟlM|+!%x(dNl$N 9xc'3 F݄O;0töYkOτN NlPY<h,H4( 5eZ3!+%]#!5ñ!}N%LH؜B Q'*S*сN xG6Pvb/-]+;>\̴9-E. ł,P(/@8REݵݯYkF3*+IҘ\ԋ;O!R"5eSD7&(U4HuS?&R/,APͦśP3UFm&4T6eOL(7EMTӍU\`Qֳ0U!$h5uU Q5G6Vx"QZ2Õ=Ou 4B} arݗ[ HefmgPSV"^>_͒pm쏘ɑוHזȮ%e[%-X:XI8NTO{opMX؋4U WXٔr9ʖY>NuQ0ג%VȀ,ʻڟ1N[a%Ƞ5Q+( Y(bJTtKT:J=ȨJ=]uU+YY˽ H-ZLX J%ɗM[=mZ KڝړJN˵]ړMٯ= ˷-]Y]@]n)LƓ\LY|J4K4YuZ%\]]ekzɴ˄. u \kZz$[ݣ][^ EWb۔M#O]Ru[$$OߥT8Ŵf#| u2:إ`_] $4!Ӎ]a`Ք[^ OD SW.X}؈aa%b% a$m;Q1jGյ=:%8Gb1^4@b,]b5fb.U*d%R#]R3cZ{',=\sSU 45^d]i12=S4mXRIU6XP\D4)H_edUF Cae}E6-dZBadN?G SE3U/`ybC6dpc\A TW d6ޚcMEeTge Ƶ?rRd28 VD_1oۯ-ft2c R;.,pƶH%PU^e+O0IfYbqN(7%!fomy˜r8'VWjJmq\Qqo[d2rdC?t8_t9x-fj2U?1R'd(7s$qkDpFsCWfxk>R{1K\hR;tDRuXvMuxEy*u}s`x؈X-ؐXTuC*vpY9Tfo^pOwqt8mvoObuvMEyw(j{g_OUt}zϻ{w7uvll|fgtMu`FvxRx&"o7U`~byywg(oopyyhc͈Lfp6@{1Fz+P (q*6$l1Ww O7o"/R# `֢BVLo{W5rI6JKK7M46EswsG#f&|ǗʷWkT].OR^t7CiViWSwgUo}絀qg-NO4)y' &vx>lQgdijvze wr_8}'w?}W_D` 6 q DPh"ƌ7r#Ȑ"G,i$ʔ*Wl%LgB<&Μ:w!2tHs"ϤJ2mʲԨRR:*֬ZRuN3mdZ`h,ܸJ},(4†g".l0Ċ.t1Ȓ''vlj/Z36s3О-5i4b#M .Imvϟv-7b_)/nRb7덒hECH$(F=.gzDFhA.s't@ hм4nw:8<9Olz;pkaE"`4Ӽww*\ar ·0$PhhCmC_EpAnq/-Vd~:҈En"H9Ur evcQmeJSW슨ruЃaP)< _Ċ4IkKᥦļ#.{lh#LkP!3C<|[w(*Zh9c0!q8s`8<*3#pGI2hc@;F/i"i z,'$](q!2ypN{$7JQqP)V c\IYJp+]rW Pp 1e D 'GT.KcI%(ҘfB"Λ$P+Bk@ܧF)IIn p#4?=Pf"N=H JP'4eC@TJnHhH;R-Ȧi6 >oiQ"XUR'/&=!fʑYuQ;Hrsx, 0Kr` E, ۴5nl(_DэX"KX \:䠸ŕD[9-X7UKuwwa*!6gnvQQom.Wb%I +|mn{F)~ELwd5!MQ<:xNHo[,c@XJ @pS9PN ,d'nN~2.vyKh8ޔu8XB\83Ӭ5jAa01eelR8;xN<&hp>4E3:(6yҖoc:̝v4#QzԤZkq[PܟMB焿,]qGz̦6j}5כ>6-"x6b3i'ٶ&lnH9R<%<֎-pk}mNH^Q <5#s3ȝ}=!KezI ӥw3s[ ?9 ok<"*(|Q!kѱFxu# 1y d[3td_JUvGPY_KEҞy)#w]Ϊޛ kp5&u= 9֣>fjovZ l#/y=#_ǿa:Ϣ9N݀X;SFiԎ_մO-/F>O)eL}s)OSr(h>N?=_\E)% Y %hgJ@$d%h0|(ja$S$1_TԵdPV%P#fi:%f)cNR0=e %)Lv a_] ')ԎgNF|)]^i!ҩae etFN)^*_2X`R*F jdjJhWT:&>jT*zVcE*fjZ*Tj+vi"Z~kJlB%*ijfr:xtk!2k+sn+1r&⺊kp- t#܌k*f0r'y66lxcQKٖz 6c*3Fl.7R- Ȉ `lf9'6> IT_VjDlIE^<,kQ (hMvĪJ2-hD׺dF@OK^fdGJ~m(Tv4D< x f&Ni%`囎_zr.2003112/#373?34G4O35W5_36g6o37w7;32'4Hs 3:s93;;3<dz<3=׳=3>>3?s8/ t A@/4C7C?4DGDO4EWE_4FgFo4G[?4, 4AtxA+tC;JtGoJEEtK״M4NCG4)2r#@ETAE@$t#u(k2RsRgrS'5TGTOu#4Ocb{qAWWsuBtX;@5YJ5Z5Zu[X[Yt^5X_5``6aavXUGbV@ A@d@_5^YfZ{6hk6ggug\#j6kk b/v"v lnWnoA Զo/Jvpp;@qqwrtqoor7trSqvo7www7xx7ywlҶm/Zokt_q#7r[wsvCw|O|WwvGwvwy87z!@38CJ3O8;gcxW8GC{x[c88Ǹ8׸38'x88C9t;@O8(y?oxtKJoy399y9y9y889::'/:7yyW_:goGw!H:GŨzCũz7z:z:; {O/?;GO;G)Gco;w;_6 !!; 2{{{;OS5<&{`S;7?<#|oC_6>ovnv{s|8~>뷾>s~ѩ{7}w?-x98w8?x_?go?w?yCw9s9où?߹? XP A "|̘#sYsͣEw^knjիYv:fޜh׶}wnݻyxpÉ7~ma7wzt2e8p{v۹w|xɗ7}zq2~|V?Pߟ?@ ,AT0A|pA +A ! / sM<K/]|emuܑ}GT"<=[&|(`H$,Rr.0R2<͓{6|8圓:<ܓ>M2B/DSXQF}H%J-L5ݔN=TM5RM>TMaV]!UeZm\uݕ^}`QO=dWKuUWXkuZj}WlgVUnWoaUt͊SȨRZuq 1s=Y/?VxaXÏډ 1ָ⋫XEcCXYVamuޙ?7bhc*F8:S=Y报~bjz꫻zly>g~[];--Ro c '\p_qOrEM?mU_T{w =roqs5xm?XR#F{j{ '{_}_|G~ X@H$@ YH 1x_2pP!xEAR 5}DaIXސ!8#<uy`ZDЉQYD+^6KŲB.~E"Xƺ؇4IchX6qHG7ʱy 3F3[ᒘYHC~ "Y$)YIK^:k&9ymD (I١Rr4*S9JVI[R$".yK_%.YLT2 Ә YMk^365 8YNsT'(9*T,U UP ->;x@mU:`WEA5zQYuT!HiPTu|F⅑yɨ_0 fZ9)LRX$4y-q-CX2qb S]Y*V{S",GK4lh=Z5k)j[UwW.-nwj9u#zw>ѕtkgb{&T+^r"B׃!K_!}_0F FJ`#X`_DG8=b)-aGi\9#1cA6u\4XIV򒙬dpQ\e+_Ye/a\f3iV|e C9Ց\g;yg?Ё ]hCщVhG?ґ)]iK_ә9iOԡI]jSթVYjWֱi;PKfYJJPKC_EOEBPS/img/vm_image_digital.gif@0GIF89a!=      !!!$ #3 #' ''.2-22!2'48*'#3,$1/2:8&<62<@=A#@.I1B9)C:3AD(IF8LQ9[A*SI;TU=DBEMCAIGJMHALMJTJEQNRYVESRTWUX\RRZV[[Y\]\c_djcVIbTQcYSb\\j\SvYEp_Ur_Y`^abdLoaXzfNxeZcebedimebifjkhgjinklqotxrgeriesmm{kdrnsxqnuststzux}{sqxvy{|~ Icqu|u~||{~|}vt}zt{]JbNgXp^mWqZncsgvqxr}{wu{s|zyg}v~z|b}~~nu|~q{|kx~vzž~ħŨɲ֯ѮձصˮȶĻŽʺʽ׻ӾھὛ⾦¶»ƹŧȶӻ̪ϷѪض!,!= H*\ȰÇ#JHŋ3jȱǏ %Iɓ(S\ɲ˗0cʜI͛8sɳϟ@(ѣH*]ʴӧPիXjʵׯ`AٳhӪ]˶mձຝKݻxޅ+W߿  /Ղ\+^̸ǐ#KL2偖3k̹3[BMӨS^z4e R۸sͻYȓ+?N\CU6سk^>Ë?4ϫi mu˟O~(έPz 6Q{(NwTw!b$tX_,Z蝊-(#Ј6)f8c#x>vA _:cP#ߑa)IiI^ x!Y9hf~\ҷ`A%UgC(>dQNIfiߛ JY$!:p>zg\i%WqХ|[vmjXzdfiƪ`r)뭫:l+ZߜtX'IRb;UjZ-  i'q.꼬{k ;o++̯ÆRku4֦TaieR~璘.>I[j0D+۳/,4%D1wLմsl%;x\C|.# }9F6e0? &'cHC.J-t`RPHH#7RuXPH*ZXC.z` #2f$#6BInx^>_# IBbDL"Y-1|$"#IJ&̤&7Nz (GI9ҒLAtt%,g)Zĥ-s]R%.`de+f:Ќ4Ij:#2IeZ 8Fd7v)IOC2J}s 2O-h:Pme7Qjt(FAЎz=)H?jҔjԥICeRT/9f0iPҎDMFZT.U!mQCzԗHe*:S`ecFzu[QպU縪[Jժu$KYZTd5+`*e}wk_)>0e\ V /r5LdHN&;Ps[=>WxE.L2e <&Ü1xγ\lʓp>ֲeytN4APF4MiJOZґ4-KkӞuGRoa 8[ _hF;ָεw^52gZ;#Lfw)]Rډ6ams6Vq57MuݩwMzη~gGĴN8+qdCQ 7C3D<"BL7Its|8WPWiFu|HL9ӧNDTZ.k뮅zNvp}^/ڵrNw"́&No G{'ɺ93 $Oy[f@5C6%xǛ^򑟼Qֻ9=Gӛwz!䴏'xܯ^cᶿ⏟{3AgAaiW_} oՠ-A3cxۋ!/o}3~Z x\~t7dXWzcp7(XX!/ph3xHx^'-3h1B~Fh}e (80 1hZ(]ȅY\baH'7hhrhf82l~t'7Gg()z*x.xU؅WHcHXcxph1l=txh]'wwxGLxg`~TȈZXHbx472e?|axuqx}QzG)x؊ظԈ8؋x(hnXփtXrFbh}bpeЏhKh}WV1 i萸øh|Gu!yIxNRُ-rԎIis(ٔVY*9f bɒXGZ[ѕd}a(hɄgָn\pidguiY dP g0 Rٗ钂9UF珊yiI hPRyXh9vɏd0 ْɒya՚WǙeY gֈْ =%]WXُUV))ɞةƝhGY)؜ 80繒i(iQy(yi 1p9 iYF'( | `S` P `0 e0ejn"$ُ|P PQ 5: TZ)/ *!:5Z%koAuXrxə|ُ ;KTJ yU'٥a6iɎ(kezpgrvh`p*}z ;`^0j(AhHJcsr cʊz v  em1:efX)=89Jāe`ZGgpQ t ךTxڦڏvXxٮzh*ZȊꞎ P `TZ ۚHX{z 5ɱj%)7(}xJ  'j}G{38~;R68[$ (   4 |ʜe:(h`tA= FIpؖXbMP@ p i o[azJ+ yh]Ъy 7M˓HUB@+Kzc }i  { @K zb`P hF+hu˿ P `  +|d@ P k%|̪”` V| ɠ`` + @ qLL „T~` }` ` P p P K* G*č0 p @px HP_K_VŦP 0ŷɟ d d  0 ~}ʠp p 0 @˼ ɰ̟  ռ @ pجG {p @_,. 0ϸLλ ҟ ` `  \ @ 0 Ȁ p"lsxs pҍ ڟ5 0 !]  ߐ  26 8t 0˧ Nՠ  U %=ͼph-Gj `vMy ѻ< p p Z`U P @ٕF jy o}0pq -c̠p  sPWMP P ĭCN| @ ۰ RZ x P^ h pp U9` p X00Ya 4.$f  ` y @ˮ֠   wpRM9  KQ0{䫨^Ž @L*؇` =Jp poM8- Up4xk\  ١ x Ġm`0=n g @PIK6SG7荾_8Zj;sG ߎ  `  /N π l`qIB~M6`B۱N;+{ 퉠oѐmq˻, j ͐u ROp.B@帴0ȴ[P _Ndj↠ 0n \ 0wo@FIpB0871vQ|[Lۮ OϾ#aK*kGP p w wq} Ȁ `oF <+-`v-08@썮Rۀ;`W?vg -/p ik0F֞ u),   10<䫴޴ή軾> 4@! &\Ç-^ĘQF=~RH%MyDB"U-WFh0hBЇFth?7ѶAhJW^6Ȥ-iNW tE=.}:ԤLD޴Q-Cm3qXÚrJ@ҲuFJ<6Hv^޵\lاo)Uf8le"v7K-@`oS{Ei=eds!eRDLI@k;:A%~Pjؾos8x npde*М&v=~s;8ב|/:Aٕ|/z?Ϫ.{<:u=t!r:С-t|/S9ϺwW7'u^O;B}r^{'Bo^]s.Gdi8v<7~w6v<⓽W-ҿ; osW5~m d>{T}Tp}dY~zx)S5Ϳ~w`?,3_ǟS@$Y,`+cQ@l@zclS7S 3c6;;Ӽ< ~9=>@>srC;<+>69=4?R+ +&:kû =7B+&D;1t);cA;A/BkA@C*KB%!jBsB>+; BC[[$CLA ;2'ÙKCV;Թ!98«SN [+4DID.\8E|D"5#tQR23|:c :7뽚=G|D^"]Fn+mo q4ǻ*sTDŽJut(jwyG{G}KFJǁ~F&=ԧ'=H7 D &jEq94=) Ƚ4qVɫ5 l<0ȆIH&̧♺%B6һIKHbIz<4m­;J)JɠZɝHC?<8,;BJJIJHZJ܈<~ıòɫN;"Jfʇ˱˹BFOR4DL>SƄxȤ̺L+δʌ^L$ӄ6dMi:\֔MbQM kKL(v5i"|o4DtM!7Lκ8j47l>G+õ &átiBA<@d?S ˖|+8DXTj[M\N8OIO&'\KkT8,DTФaP?NEErPY΃6 M#u9LO,F,F>d&g|6P?zi:}?-y>/2 3 /-835} 6}SS7:;T>?@%C5D-EETFUFGTGHILMNK{lDRu }8UU?TNWuXmYUZZ[U[\]`Udb_EcUV`edmeuhi}jIM:kVjVkpqrWs%`%teWtusvwz{l]U/W:׀؁؂%؃5؄E؅U؆e؇u؈؊؋،؍؎؏ُؐW5ّ=ٔEٕUٖeٗu٘ٙٚY-ٛٝ}YٟR]EZUڤeڥMٜןmڑ%}(ӫuӫZ!/ٚ [XWe"SuSe۵U٩uZ۹[5}ٺٰ [}WW%\:5\uX%[7]XYU[e~\:܇ۻuT[нE"ܯڱ׫Z]UW5\]u[ =[m%Eޚm\u^^^]5\Åܮ[-_^=\5zޡ߳ ^Uި_5\^%^N`=n`^`.``[~`V"J޵e ܿ]]aE5a>a 6] \a$.%Fb&V&'b'u\.(b-.^ݥ]ma5%a6_% ~.)?@AdBd]dmdE&bH~`F.]cf3~^N~c\P>aRv-\meXVGHIvd\ne]d_e`.faebec^fdf`,vf:ffbk bjEeaa6%e16ef]qF=FU]{ fm~flV`gk}fgh hd~.h:n+>f.hfhiCf`&BfVdh鐦iG錞i阮iiihj꧖ꨎejVv髖jjfk.>jNk^kjn~kkk鵶b}ȇk ll-l~=l7MllFl–lÞllņl̦͎lmmVfmҶdžזFmצն^lmNj&6FVfv&6FVovonp'7G?Ww?p n q /p(e{^|&|(|\qrq'!q$/r q&qo |6r)-)*-72eN|XsV.%r0Or9#s%;/s>>("ŋ3rqǎ G,$I&S\R%̖1_ydΜ9S'Р8,:hMI*mҨNBj*VZKמ^!ֳjӲEv۶pʭmW` Z.ݻ.,0Ê3F\0oнb%*pc̚oНG T2eI^5lֲ_ώϴNԩuZ7‡/n8ʗ3o9ҧSn:qwǓ/o<׳o9w'>q%x9 * :xZx!j^8Ԇ!8"%!Rh"-"81x#9یA 9$HߏE*$Mw99%UZY5^%]^9&,Y_ifg&&q鞛9'y\ݹ' zY}9(YX*(]2JZz)j)z):*z***:XFy+++ ;,{,F桲:,J;-Z{mb-z-;{.骻.і.;/n/ <0;O +0 ;0K<1[|1k1{1!<2%L|'2-21<35l093Ϻ;PK}#JE0@0PKC_EOEBPS/img/context.gifJGIF89an9ggyy\aJJ333§㻻eeeVVX66x~$$UUUr#ۮֺvvve ɬ:8? 񴴼݋22Y%SԶA@C}|ȊQY봻䛀llof gi􋎿 }{}ssz\Z_2﫱KJP囹sW^Ŝrms꼵_`ZQY-66osZBHopyw~PQV@@..Q߈``䇎a`f!,n9 H*\ȰÇ#JHŋ3jȱǏ CHɓ(SLɂF  Dp͛8o@-@AH*]ʴӧ&M$Nί91D0K( PӪ]˶۷pʝKݻ& eLjD i1r=y rYzFDA MӨSջL|d=!NNpY9{obHУKN:\MYyB"8(M` Ⱦ8_} 0ɖ=!t\cB_0]m˕ .vHW&&B 6d $RUf 9@v /`Üg8$ &~uO@Ó\viqAfJB h5ұs"yG~yk#WDޗ) =ǝ>|m (G%땾+^ vw?lv--M >4*8yl%O6oNq 7)h[VdDLM0{ kQ̢iHP4g8.1#|x$=bKEAq k"D<1uh $C?7^[)ɘ<$T(I eRз#@L*WV򕰌,gIZ̥.w! 0IbL&,(o ʌ4IjZp5nze3U) LÐ @JSs*)BK&C'JъJIF7zNGGJRN ,1żntz8M%PVAA QT =8e(PS dJ }V5CQ`-)zJ֞"@ @ZeJ,̡ [0uPmTH\~u_9XcD,/ذ2Ã.Z== T %;@ hIZ֪TDhJZXTֶT0K. >Wj.Ee3<Z- mZfWjzڲ7hzm XƷ+K[U{ Kd,% W` t|/E%fya74:h;P!PkP1l {+d"DZpSA~-此[K+vtowzr9??z @ 0s*T@@Q42 PZk݀;큙yR_Ȯﰃ|E?:яn i#C._*N)"\UNS=UdzWm0 +'=sS), W4pW₵է>ugCq}GJ 8pW'l^֞mAY1Fi z{-o yNyj 4#/CJ~~i$C"Ci]) uC{o? 0oj|%% "&*3OWA %(%>AsXwR>:RcowNJWo 6&tVp%WHgWtWtP8) )t p PHWȁ(MnTooZ0ROx |` >(0 =('LN x! ZK~'&`UA ք6H  'XB"`؆&UDb$Hb` 80d('EhՐRlhYd^)!"$0Q(B?p@Q t9 X6N<e Z`} p$QnxLΤx* Ψq1a'AΨ XE(`q$@@ 1~it |.H1AAxDQAV6=11EA)#Ta\q#$YncAȑ:yUQ"5;Ac@P, Nb,0 P$)?QCRIyS;ѓs3"2E wpIAД1OI98`,&``AFjR FAИ6`9@4/PX[Е@spP+bhYD(g0\9Y Hii@igٛSQ/``ɰ yDp 8z!ljr&9y I @]p@Dpw_1ʠwIz詜{ - Ea&+)c(3krNAja6ꢒy0ڣlR>B2:FzYHLMP@TZ4=\ڥ^`b:dZ^ Vz7Yfprh'Ѧsz:uxڧ 'ڨz2k5zکj'Zz=:ʨ5Zګz(: '!ĺƚH5 ʩzzϚ&ޚIz:cڮʮJJ%p :ï :Zw pqPJ3j 1#(kx<[k咲+:* sZjMZV*ڲ.-0@Dug+M+;js5(۳%T봎jAG 1d۴h˨h:o{Q %0: jz;BTKVSEl[e[fKw˳tKk*sE5] 0+dжpeVkPw=+b*ț+y{ʛ[wר.)A+{U{;?K{J˸뻨[˽+˻̼ ۩߻~Rˬ+a ۿ"[fKKV \Kt5sڬZ{" -#|(\H/1Đjc!xu Zkk;H$,!7>N1M-lQE` a0a 0ľؐP0ѮY~^n(!>~C;!>۱߼m ]l/1`)N.+1xnnB0^0 n `  n `^-_ِEm!պE0 b :(]::   b ba-@IniL?^SUm (b] `O]OpZ-| `Hoon/^ ߶m o ` я` ̀ )+o`+ m_Ցd$Xp` -Aeɲw`UhAĎw(K v S`1eO9u䙳BϞ?%ZQI.eSQmjAtfLwa)Р]; cҐ!kVXc̚ ֬W&\aĉ/fܘi. 4i`ln +-%\weϦ]mܹu7LB2 BD@Oq(D(n")h]Yػŏ'_y{ kw"GwTpAtM? 4 vςwDxG&H" @vqFkF"*!J, G0İʒє;G*J,iq"J +~$"eQ R$B4;SP3"̚NƔTM!WY=Vk0j5WXԅ4Tb5F*ծAP82񫯠! p; QƘ\V*ЛtjuYzSyndW|Cym&ނr/j5Li$7I{LDf`#(uw֍W^ Ogo]~z{'(O>r/|}oՏ#\< ҆ǡ^uQ5Q}10f6"8A Vp3a({"^yc\L nyKZNvC0$4<|Ig/qF4lD(oKO?J`Q@ d420sf'ьom#g7fRO#[ 30zP4yHFdd {8ĕe҇)wO&pe)#IJ=nn(i17 QhPKssЧ?:0Dgh/f@rr+4Rp4S# @b?d$7\ *Ëq.j1&(@2/dE]Gɜ/c(~X@K|f4#}e T 3  Ïԇ@0Ʀ|fD'ZхaꇗG0X%I`:HCYJTZ( u:M}jTcVb(#MiJ݋jڤۦZ&L1F)i*qR"iQ!R"k%La'𒄋mpHyLU<4M\-.:Vk2p[Q35 I{2"˦9)wA`9b A ]" `$#5Ac@8Gω@{C@э~Ayϱs 6ar 09_Ġ9 X`qTԚ2\+QZ%o 0dc$6 >.򒣼19x~G^|-yg^EӧdA 60oH&P`] #ۚSsO'r[i{\')x"l^~}!7)v}83ҞxlR(X"NyJ, 9P<ǃ<Ӽ; s9j ?c:h; #3;8;0C0 38q7qĸ۸£9Xc9" Լ{?;?A Adq?P+0C.$65 *hSs< #+P3 A1,ۋD)D1 8;s—9C@D (xE2 4lY䫾&!{&8xB@SK=0dPP;H44<=Lx9 Āe{T,.xE,EŀGqE]|+c..a(]p @;DB0|DF>+pXw yL)6ŷMB*a|)ܰ<|@H @H#s,?k/IHA}?2XHqԾrLh HI9>r6)>}.YQ:0| B@dJT;1Tȁ*ң8u/CHAE:OeRDTX H;H 5Q Rmk@4eRvUdk0ɋ\M^uS|UɁ0g=MVp ]VKU\Vd9N` W|%3hV,: WvU(w-xmR@;X'ՊӈZZZZZZZZ [[-[=[-ۆ@U%k0s ?[[[ \\-\=\M\]\m\}\ȍ\ɝ\ʅw ،!ŁH:Rk$]`=`k趘PZ+\pKH0]]`c }d]]#V] iޜ{Y^^^ __]-: }mƀ 56j#_____``_=k_ihu_F 8xHi_͉```.`NH{ f``?Ȇf8aaaa$~b`~a {a%^b&nb;,-n "vapb2.c3o_* rw :ch'bd d0b##1 xdHdIdJdKdLdMdNdO~dkHLf8,Gڰc;FedfdF dncQ.e<6!"K\7DB1>fA'"mFK& 2]!stqpc\։-eA]~ \6\&`f$VghvȀ%hP.:dR6Ncԡf7ĤZ$2,ah*gޒ;,\iwf+~I>V &" >]jwj.nC G&hkK fHJ^kdv+,af7Ř<꤮Ǹꝶ)@i滖iɞkw77kciN*jB窞l쮖i NmզȀ kضنU=䑞fvlugvb7.!ǘE}ijNlv.drǛrvghζjl].o`jkPmkfڎfIN 0Jm76.ik5Ǟvfl아ni /6˳nVjFomn6m~c. "/Iv%g$>rgpڽ;&6~ G:,?sUpvgŞ ''s5g jn^oq诖DqN r!rxupGr.gk'njN)oQ䵦.j/'\gᄅnn>BmbeZ?^snжs$^[7mzfjnh>olvAmWhvoE {tvoxvhmJwmIt|uuLoX  RNuVbxp@Nv^t2ׅ[jxxyy/y?OyXb_뎗.ky.y/yyT-ac i=^4 5Gh{Ayz{ZJyy{_몈fȂ+r,7Xb xixE{|{ot_ow{iDA@ࣛ|7¿zkȂ](ڣ;ڍ|}=yf(f0 (_W~ϯ&%=H؂+`(|ST<݇݀P`&Ѕf000]0@UՄՆk*b!Ĉux#I)Rǐ"G,12:@ Å2(Lʜ:w'РB-j(ҤJ2m)ԨEϰL3ʟ&M^+k,ڴja6⚮ aXcHouBp&up,:>"gDZ;~\yl+%lY#`C*ԪWn5L+h ke 1`HZ%R.# <55_9 r_8K? 8 x * : J8!3N,wAd!LJXED\Yŀ#K/5(@funՋprrg"I*if)D%ݱ!x%a9&ey&i&m&q9'u`N<4O$drHq"pc ,q?dv䒩ZR*9 %Dc)@!͇A2!)5;,{,*,:,J;-Z{-jz L'2HThX>5.;/KdBM: PJhqs0x`2f\E;1[|1j1 c0 g268%<35|393=3A =4E}4I+mPss 3 W 'P[!N q C۩6 aF|$ 8,D_cAw8gd3;Xn#a*oH֗~:ꩫ:뭻:>;~;8D@Ć1Z̐Cn⛖a #QE1~5e!<$` "Z#&l@%Lp؈cO(1=p@,Yx3 r C(B=! Eƅ%sY HG:4$խJlذ8B&/*AT<T"!xL pO#`PӥkM38 -6ݦ;p (M)4Y`,:r604A.;X c .0 ΰ C c BцP mz cukI4]ܝXwx7}L Gϲ9*! T~ߍW_y5ֿ50_x7p A@f1  jFDw0@-) h0a/!_ <g(%Ћ-'ְ L @ +X/)T 1c3k:5nknsyu 4(^iPjO4@Xz HAMgf-zv!-i=otiLW:ӓA i6nә&uMMU.\3q,D#մcqJNaF  8C m R`@U AW n 8o!e匠 9 Oͼh1cm9͞vs+mT:qv-Szn]Q^=a.PJY4ՠ5*a!PpB 5[iSԠ9~iLu 'zѓ.hOK> x(` t6M T:э(hu=d$sh&*|[?P6|`#8an/ Lx2wi>s\>?.jK?\%9.ܿ.㌶\;T n HD ( L?+K dַS:=?t'= g?҅{O%]8 VZک%qCݝ ATA>l>/>B>4HAxHA!LA"VH@H!x܂&a:#  ^ޤpW͙]a!ҭι %__UBTBa| ]@5`T8)XA,=4m!]1 5-A d)a@Oi]n` )$-hC]p7L頂$>#Br܂&x;\x `BCỲ@-!,&0L\_@ ́59aqġTaũta^9[A~VCB zbn9a$Ba0AB!"Z"_í!*@2;t$:A%T]%&Ydpb%4C(+^hbz7$#PQ(BB*0.Fk*.X$x4/&hHZ%@T"Eq!)!ͣf2bAbKd>>hEAae!jd;\@W >C"9@ d a%`@R*\d.d$m ܡ(HXBIB 8m$ eq"NjӤ^jVPbjV qGBAI: Nq3P剶j(3W7(3,/`#r@#h@?|/$!(>@/C*' $C!T&ؠjͭ)f_Jޣ=?򫜂&;^&͵¾ڜA2AnB-g%Z BD,B.Br*˶ރrRFvdH @fjY:**Ѯjìb*$݄@,B * `>Yu!/@ A-C( 8X"ԃ/-.Cp>DA73-/r cBA),@#&HX2ԁU#A0^؁Cց$q d0"C+;M4NN4Ot P[ t!C+02&@ |c-x0AW-A#'B>0B#A\*(" ߀/8T) K#&M4^^5__u A 1 I@B؁ &A*T'//@6AtXJ@BA |@=(|Դ_6nn6o0`pp";7Ch ԃ4!4+A hkǁ8j@(|@+$"vo׷}7~7= ?$@)h 5|2B+9&TB( $# a(Ё7Tp$(2OkAз <˰~縎82pt02 )hA+p~߆@/5 "B/\|#3.8(l 09 : &(B= ;؂),)B*l0*,#:\*nwЁ`iA \tM`h@@-B @4 2EL;/{ɟ|/ :C{ʣ<ˣ<׼<<5|#@8x)$A;`Lu>A  59(Cc|yR/ @~B#8B(B z{+&0\йzG;ܷ|̧<=>8 &;B$'Ch"`$9å7&@,`" wtKܫ?'/?#w;)Ե/A0'p^d$0H'`C6,tB'"B3&=|`lWaSYB U,LPaC&JxqE:dH#I4yeJ+YtfL3iքIgNѢI C9yH䃴 N ciDC7H1U6u/LcزUGGwr@(cF;VȐ"!ryqbŋ7vr?w.]4cS@ ^J"N rF!kPfU\Q vpaūC5w:ѧW|xɗ7_2˘_j}L+#V (@]zm66tMP%>͠ p - 5ܐCҳ철qD@9=U\]\emDž>\a| "<$\&(*,ܒ.02<(w\/6|8圓:餕^馝~ꨥꪭ묵X'>^~垛>Ǽޛ ?_WX-5ߜ= \M?U_]כem]}>qމ?_ύo襟z韯ߞү|/_ou9% H4B_@"NPA ^38  IXB. @6XB1 49St"AX"JP:HyXE+^r ؆!`{DR)iq{Ǧb('PgV@g՝hEk1IY~50+a*7ӫzئuܾ11b]\woO0TIO@c R ɎkncX6nad8q ޷]nsVJv޳Kw]o7o[p # ?x7~x)Wx9wxI둗Yr1i^s9ysAЉ^tIWz;PKhJJPKC_EOEBPS/img/newui_searchbox.gif8GIF89aq_vvveeeTTT!!!efffWWW`fbfͩOuuuu䇇222333PPP༼Ҫ얖pppLLL޵ooooyyy꟟}~}ۀCDC1KLKCDD2ijjŸzzzRRR>>?SSS2!, H*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ˗0cʜI͛8sɳϟ@~TѣH*]ʴӧPJJիXjʵׯ]'xKYbϪ5+ʝKݻxuB wj^y4#KL˘3kY*6~ܹӛ?˺.ȞMvضs!GMxXDȓ+_μЍ$iѳk|zÃPѓOϾ}C<乎 qϿ$>$E%`^PFaVh!k tᇟ Iq"s  bs8@3܇.Vi *'\r Vt5b7ln1CjI.y 0C\& #aqਣv"Hfhf%t駠E I]Ljy*G" hN`#rlv ,p\)6HܰP+"akܥY1;(kKBҀ F*#kr>g밿*g;WlZBl]J{p-V. %$l<$% #'p/r/]k!+3=\-Ilr[Bl5:qDܵNwkh{6RiwQio[MwJ(xG-/Ռ͊kZ-׏G7wpf#hqU_ q;g^tGӛ+qǏvRnT#ӭ;l+ .¯0$A#qܯ{8x iH;*Ғ~xH#'?IɥGӚ8iMQ8]4M`HMRԣ2HATQE"!%\WBԢnHZVpU+R < ^ 䝤;{ S_c$֬gŀb6vd,fHXj6zV2K@jY~hںY൰le;%DBK׸=r tKZͮvz xKMzko|+}P!yLN;'L [ΰ+8 GL(NW0\a8αw|bXA<"H1 DNLe#7X~ē *{`6q -aNL6ALgξ@\>9x4b>ЈOB:ѐsqeJKtQ8ёF1MC+%{EhHAuR4鐱,K1̺{ btӡq?Jꁫwlg[Z N'<'>qe[wJ^7sĆ9-v7yaNԠ@zF|6{Jvқl;ଆzMg#ءMاpV9Ys5;_L)@O^qi;~Q!Wj_{E>y{~Pّo֊?Omϝ3~9"4)/kSxM:MAyCSxEj3}V×z~tcs+9ߏ7uUGz߇yv}}Gu× Zk&g~bWw~Ws{Gn7W t Hׂw|p7yGz|7~>z.hh'uȇz(jno1wy'oyG{'(+(|Wvʧu2rN7pp7qn|'qsH}xxrKwMxGF^zfm R)bkg5(r6Xc؈(l)8{\¨؋8bXȃxKWq֌Hwxx[o8CŨȍ獩Wj7rbdh6uiH}lXvg蘎>'tY5ЂIvinj(|<( hxjǀg6zIi稑lgxp0pI#igxȒAؐW|/:9cؓ>ْ]!}I9 ɀGiuXK)+LJ`f;HhBؕ^`IhD ]!sQxMɄ{yuy~٘`zq昖 p5Iayəf♓ ?WD7ٙ)i~ɛ)i{•ę yt·jljVx}o9Y5iǎixJYc艚yhXz"هGpkwҸt8 jhǝO;Ym9xIwmIH݉Rv}XW?ӹ-١a}I(:x|c9ySـC(Kɢ 8%JyBuiY1}Gcʤ }SZp;^gk٤LJ E٢Vitq|DTj9zfةO:Z 5z}EGJJ vj|Jdه*jJhkv!ǪY i*Ӛ viJϊdYBwZ#cC~ɝ*zڭʮ;ZdJȬjc:?k} kjJњ۰;g|[KKɜ9$˯ 'fٜO c%k,x条gm):+ڍ5uAmʩ9z=y$Z蚏7#wŠjv$y%J_Z7&tzjF:ƶ&bf90ykj5چJٝrhKok I}oڦڎnqKWv[ep+(yuH g fۺSZڃeY8h;Ûmd»wchZ׋7;? \j;mٻ˯; tj&_k;,;;̯iVY 9LL"k ,"l<!.lgVۜ#2d4\8ƳB,q ;ˎ2Zڨ5IK̡MIхZTwbhn ^C mLN1J 7n*9^;r_&8Zc&sv R&^g,勾+<0q ܔ&FfYN^qNNtx{.bA.=FgHj.̎nˎȮk붙nP>Bn%^%n.^L>r3N38n=hռNZ]֭,l O?n;s6*L5_eC7j7@75󕪅nP9pH/BFbL/GQ9_IUJneOW'nSh4QswP˕\szu{]{:vu~g_*0Șs&7w ima. B7iO~AՍK`얅|no?ɀZ} [|֟,-lX[  $XA .dC%N5z4G!E$YI)UdeJ66jiF9uQOA%Z‹7vSQBYuʣYn׃I5rrYiբ:*JqΥ[7إee[ne,iaĉ%c|g. \Iř5oL1SE6˅ ٳkر~KmO'$L`p-q>i;ܹ#ʻ;^v(wC?'OztԘ n޾BF WH}Eŗo!u~k/ 4+>so([~3pC4H BODѾ!TA )tq/ J5 <\M~dpE"kE$ϲp4qCH"$,M! 3\I(Q*DtS6.% Ɓl$(QLh7 E,973G3MD)PC3 QE;%i2PG!MpA,qUSU8tVln`յPYi]V^5aMcNYheYgi=Zn V_Wou\tW,\OuE]zy-͋z_xB0`Vxava#xb+b3xc;c1~y #xB[vecyfkfsyg{gzh6'00Buizjjzkk{l;PK)=8PKC_E OEBPS/img/simple_f_structure.gif/XGIF89a -ss)Z &*ʤ鱹WCh- Mu> x#JȦm)hDnj>ס.k/S>ʾ;ʿB3m1Z&. 7D, T -wpKDȱL`(O {0/j:߈b8ls1um0L7HG-uNm>W\/u`bm6uڌp[vt=v78Yb M~-u(J+7P.y$F,YnyOOyϕc.R8$i8ꍛ9밟k::{'oȏ8O󘣮:G/~G9=?_ y;n'}H$Ɂ#d"'IIJ>!Jz (GIRL*WV򕰌,gIZҐ2CKװb2I+G84IjZ̦6nz 8IrL9qi<᝾$ 0!0|'> "X!OQ}MBІ:D'JъZͨF7юj# F-lA(E .0Ѝ'ըFl-0@ ζn{MrNvs<r*4q{?ti H;N[ϸ7{ GN(OWrEL -P s?§ i Hz ;PԧN[XϺַ{`Nk >Rm@ ը8!HA pO;񐏼'O[ϼ7[FO o)L=9&hwOO;'=?f5vhop7OOϿ7}áKpPx ؀8Xx؁ (Kmp(*,؂.0284X6x8:<؃>@B8>HASkJL؄NPR8TXVxXZ\؅^`b8dXfF l؆npr8tXvxxz|؇~8Xx8i(Ј8Xx؉8Xx8h8X舶8XXȘ؈،x8`ڸ؍؍Xx긎؎8􈎍XX؏ֈGHYy y Yy9ّ)"9&y(YyH(.0294X8:)7>@B9DٓDyHɓLFٔPR+K'uZ\ٕ^\`9dY])fjlٖnhr9gوtytx|ٗZY턍|0Yy鈊٘ɘ9Yypٙ)Iٚ !0Yy鈺9AЛٛ9yqɜ9ũйY وӹa晛๞홞 YՊpٟyz * Р: ʠ*z* zJ* Z(YW9 4Z6z8:z4AA@ZF4ڣJڤNZBI:1GUWFO>ʤNR*YʥhzKڈ_z[UzEjHdbʦ7ikPJZ~ʧ1\ :Xʩکpz:*:J:J꨻z:ʪĊZZZJj*0Zz蚮:஑: Z 욯گ* jڰ Ak˰ * {;ʱkk!{"{k+ A֊г>@B;@D۳IMK{EۈR[VMB+QY˴^۵QbW{DkWkJ۶anlkjkP;aK` o+tKh;sy۷roKX۶s}0[{눚;@빢K;۹۹ۺ K+ۻ[kk +Kۼ˺뻘˼+ kkk p蛾껾۾{!! kK{[Kܿ+ ;|,|  ܈,43| 4KzB#WAUaԮ!ԌHM0O-QSJ݊LmU,[zՌqT֦bIGֈ!WIST"EACa|= R 6x lp؈؊،}{}~{nA$ٚ؏]֑=٠1=٦؝ןա1-}ڲM ]C=;k 0] $a#"ܵԭ0 ڭƭݜܘTڕ]PӅ]]}$ٷ-٬-}&=]^ ۃߤ]nӽ ~/-~  5n+N-.!l04^6^~Ⱝ/.?1~7^7n# 2/1H.JA[]_CV^% 09~MrN`P Qs ;>UNndOYs7,~ؐ^0?pҐ :3'$1>^ꢮ꧞.N뱞*DNfV>X^(~!cm'q1&͎ !+;w2/R.Ӯg ~!b" P 0 X@+P~n먎NNOd.-מ&C1^.^+&zr ":Rw+?,##,Fp   @WP>=_.H? 3~ PR?.ބ_.AR.1r-;'2!R(b*& 1R+%_pp* Đ , C~o?A_J^ύ O?Uo~+.",ǁ'왒3 yOu~^)},Y p ` (>/׿@OoVO0,p&!$ '%ǂ.O`A&daA~*,pĊ1jx"E  00 B5e Moꜙ͚@}ʳ?G0iALl\WUYbG`rdGUeZllۯzIW[Kˮ=k,އMߒk} (vW':.ڕ@CHP?Jhi2w{T-kQVmFu]kȺq1;֩kŌ1~Ao.@ÊnmمG}sFABH;-X j5a_쉿3?mo5鵮d*xp7MLPF|0,_* <"c0嘚/l"o\GÊGE d&CJ$f[fdsL23F$n =TL:N<SO=Z S z,IPLRu%Z68CՍSM1]TSSU5U[US]P@A(V^DU/N 4X7;,W~eYfVLiuZk=`%VTpI6qu[sMuU⼝BpC\tշ}W5`-cyC{%X~^Wbs)SzlX[/N7dE>xyrC%lgfq6x7ne$d衑LUKzjj_q^zڭ:듹}ө6[jllَYǕ>j!{`\pOo[\p Wr!sU+{*t=tɬW֏f=q7Zt3'[Wx.Osu/w;}o\Wgzx$VB29sd! yH\&26#+cY&Jk| HO&Ӗdf%Fd4iZ.3f* CiN35%$HmR 7=ؚ"8GKS"\?;rQ!Y1Nz s& ~Ft  %%bZ %SCمOI>*yK PY/=_DAIh>zi$әj"DzLR"hQ džҘ;(Z"y(RwS΄F@)V($?m$Ib]r ,)FIjpdqKL^qxU884$X BP,[YS@e(oyuSN{֌ȥ6:OB;wyh"EiSē.I+mo!ɊA`iNcurS-kg#2ghؒGFp f_Tū;[WI)anۜ'N^"% Pꪆ4M]A#,;-T_48|/bZD-bCNnO9|i`PAj b~>,b/%!͇t>xM)yK)ڔUSOA[V]0s,%#{DJA \@A4l˜) 2̓iLKbM-[XdT4/<#z-,T{$&AJX +eӕ洦3=fb_ӚD2RW6='B .Uko!r#3H2rkid=l7M 똜LA۶p|f+[{Ϙe˜V+q|C籑lD;PcS:^}cҐ=PܖC, s:)Rqۋs J:kTJYR$CN6Xn-^6j$W{Q&ZT]R(ƱcLm]E4" u~ɬju\d=vx!}zˡh𗄇{Gx D"s;[@y@8Ι"'R? D;K@p37"̼<97.4rBĺ?d#¥r? )B*B+B,B-B.Bµ:&$B{›?TBdB?3D@4$CB6T>8ķ9!l)>ìY>ZB}ABECG /BC\}T#SM|,TJU8M+(TOT9TNQ-REMT4UT2eVEMNUU(\EUA]S_&8SSRP dY Sf]2-LY|H~`WBdd'aK'QMdQM_AA}RWOH>ߗd8VdZeeT~M[Qe`&A&cGOƎPHifjfkflfmfnfofpgqgr.gs>gtNgu^gvngwf%>^fdeegebc};^TaUgnLen&&f^߆vhO_`CfNf}C~mƔFnO\iEViY|EU JijO@F~N꘶iŦE~j靖:#1D|åj:C9C@L>6 >#;>CtAblnbz9BA@dT:lS"%TB)nBkt봲 4NB>B $!d*ln&v&C6>'fnbl= IDDlNӋk~kw)f]I/ͶD4lDfa'3=j֮F Y1nAnm *B/fmCFꪯ ճnY"rkb6'Cyӯ:n",B,Ś, 9[,9Ka^*0o6 +-pqj'0/9 I26ZY@.b..2wyrz36-GoP3;+o?o#ѓ׺(8s /'3{[=6Hr00 0 0NxS-.ҷ@+"1/¹@:GMOrq"Sor %K8o32\5XX)+˲- 6J4/?3yErcJRq5Olju{ x>4q- v3WCwiSCKEkG4bǏF?b[e򏋺P>8sCӨOO7wiG<;Do(|m,h B2ǯ!Ĉ'R"ƌ7rÏ"Gb I$ʋ)WlGa2d@:wʄH%ǟ@-PQH\P{h@MZUS#G$kFhE]۱۸N;6՜;RBLxU3߿ l2f3?ngʹtd3fpiӡcsm!z… Z;7/<9ݽnxǡs}Ë&oo'}[hWnk68luGYeńw 2 tBei%]~if( rYFԊOX"/FucR37< Yw8ᑍi$M8y)e|9&{Ia9&ey&i&m&q9'uy'y'xއ% :( EV(*g2(JڒZz).Tz):*'b*z+++ ;,{,*l@;PKe//PKC_EOEBPS/img/newui_sidebar.gifGIF89a;UUUqΨ_2vvv333eeefffMTTTubCCChWWW،uuu[onnn»mmm~~~۬j⋋tttʕԞਨxxx򳵷񯲴oooĄﷷ谴뱳Î!,;tuǝuޱڜ27H H72t79Xw6x.褓'ꋟ .{ݮw2v^zܾ{ָnZ?G?;?O=ֺ7?=wu0;o={ {K=C[ǿO}#.a@Bz˞Al_oLa>o|.,H?Ps,2ȵЅ@ ظHD&.PHNXEm`HF؁jk5֬n㸳9gvcGG(ȗ"$"Ej,XH@R"26pIcW$Lj6>V)O)je % EɄIe'=.V2$0uIafa/c9 jVDеrʋT5Oade:yyr|K#y}'7*P=᳠D(Px(DЉɢ2(F%"эɣ(H!ґƤX(Jҕn. fL1ә"KȩNwӞ@ PJԢHMRԦ:5gKj*U봴*VUF^*X[!ֱf5FYZ):nZJ5w})\:~* Tl&(AJ`l` 0@Yʪ Ȁ ##8gG Tp@ob V1!v6(Fӎ"KMnkE\O4 t[VnŠb,p9!>|%Ez7^MZ|9Q` YώU:`(8[rʅprٻ:o|o[_Qe%B0Z(xj5kL 4{!]Xϝ6(206laA^Ҫԣ=y7WSV{fvE ~mqjN(ъޤ-wMڿnbǠȥ8lbq7aaבgC&'+S~Vt.ok:  ȹw@ЇNHOҗ;}L4 Ⱥַ{`NhOi/8҅,|c`pOO;_%̝#kx0GOқOWֻ]0O|מPg=G1Ͼ}H Oo /}o=I׿9|408)wz7Ggzh'ǁ~|- U)Ȁ~ׁzٗ"Gg| р%Wz5NhP8Q(zSRȅPXaddXgXcȃnHz>z@|`.8}12z(Z~Ȇl(؆mx~Xw]hzq}|'=pGh؊8H؉P/P>PTPz |j([Ȋh爈Ȉݘ0|/PX)귇ȄبȊָxHIhz@|(H("8X!㨋*ّc } Yz 4.pT0~iX_ؒOȒjȅ8e?و8/Ƀ1 g:Y- JxU9Gox7ZI~"*hr|.9Ňؖ=ib)Ynyr^0Ux !e@u\p zzq`wcsQtٚsQ ux5sePr# Ǜ|%yEwetqne3p N-upr ҙ p ׉ %)m 鹞ɝ @( PޙZ z O ꩟ڞJ J' +*(ڢ/z0jʢ-ZM¡ #* ڣI/:) DZ2Z2z1':uУ! EڤBj%jLJNNeRJHjG*G꥟X+MabgVʦ.*[c*cʥ˔+y騍zJڥJ*\jljZ+ 静*j)jDjک?ʧ jQ٫ګː sYJQɚUƺ`)r@*D  Ī&u0:* Q0#R *Z@ ZP|ʧzQꯠ@;; EzKĺ  ;kJ';Q ";3 ,ˡ [sj :<>;JIʩO3zbdì|7:=K)ƻGYCj+L.ֳBdaؔ*M$C-Ƀ [ ]#0 Ű`ڭ$ڸ7eD6Fc۷-67b448[  @یeɝ:8#K]@nBoL=DAB6}69՝<@>>S9덺51?@%^/D>8 ۼ -.acWN-S].WI]yaԄ 3-|z=u}q,+ xN3vm;fրz<֟] Ј}4,.]kˎ.}#Mؠ֍6,tD٫>2܀1¦*Kc_]RӦk1 kkdnͻiMڬ"r>S{.q}!%ꄮ Oiwm]qm~bj,n*ٴNZO*] m4|+4]eI,n "3rC_)Er^ ɷ m9sn:,9*? `oյKӮk֑n';:_=QSՖmϖxI^<E5ʒٓ+>r11[**O''KRR\jp8FM^jpĪUVmx}~}}zzuurrQdo^imXX5ELZZ󅇼}}E`mc嘹Xgl]\Dq}Y{b|}__Uu@^l4ELPhsWgaaccJI}eeMLffdewwwwwwwwwwwwwIwwIIIIII,rwwe`VrmmstuutLNqvqilmnffopL4defghhiYjk`abWWLc44NdVWXZB([\]^_JKLMM5NOPQRSTU?@ABBC)DEFA=,h+RVDp aZfe8DQ0Km9bO5hvMV3N+N6*dc8j4h;)]cH8VM7xcdm8Zm8w[ASD5^a8oGoJ0zffd9QRSKXm\`^RdwnUHkVovdPiij6 377*7 $TRcd,X-S*c0kXv'W7S1v8|G7g7MYF[SkIwpUn]hvmrC[Ku[{txe4 2,,('Q*Yb2S_LLsryw]KF{{pQss8 772)25WQI^spolWNQWmpujcӎ_N_yxs5536)%8dLS/tf5JR0cm3ZJZvmMqm[FtOum<$&9\]IuNyjiSz|g&SjUmRobߛЋ73,ΎQʔpϲRըnLoUg/pː옵ӓꤺӦ֘ղˏ̷ӋڷӱԖҭԶ噍诒乨ɺыЯԎҪ!,. &4‡ !:Hqņ%fƏAz IrɎ(E,ʗ,aIs͖8e欹Ο< JtўH&- J9գJ DH! NٳhӪ]˶۷pʝKݻx˷߿ LÈ+^7_]`Ϛ˘3k̹ϠCMӨS^ͺװc˞M۸s:_9B&TMȓ+_μУKW~BߦkνËO+mNkm^mnm~+n"n槫hr yۦ{k&ۯ / 3, '<_ ?MW\s /"첻83ď?4)<5MsWO-?ׯ{>?ݸXMZ#`0\`(,`+(AR0tcAh@!` MBB%tBІ/ap8Cݐ?ayC ш=ȱ|8P+8 bE(V? >H2gh(_~aX?pThǟwc8bz< Eҏ4$" DNRmZ&GKV"=JL~Ҕ)UJNRt$+Q9KVҕeeKZҖ.u9H_ӘB>Qf2tf9aiF"9y{@ 4)lR`G;ֱvC|;NvƓCP_*PEԠAHr$ԡsCЈ6 uE) IE(G3ёT&FzR(eJE*S )Agӝt8ըN+ӛ4=%OAZTUIR_T*N*T*U2uA-iXWTZ5kZխfjkCqN3əWhfcʜf^׻ ֚+6 uȓ|gd!ɲCШT#%S SВ֟i!:PӦ}mic v-nq{[vn}+\ַemqW\m.p\"wʽq]v׺ŮtZֻnvӋ^e/x\rWz;^׿ 7k%Jr0c4# ,>aʒB§`,"LRPGK6019!˘6αw@L"HN&;PL*[9 ` 560 Bn9]׬e~3٬Xg ;8sLh@zІN4}F+ь~#MiH[zҗ47NgӜCMQZԨ.uOVիe Yۺֈ3k.Zلq\7e4lQylY{7_}B_9c3]Ǿןo06:$CF(*XHLGPR؄9SKQH7HtA`7_0ucegc 0u u7`~ b,8hxE؁X؉8((X8Hȉ(؋؊h苷vQ3 @8Zo(u0aha޸7舎h4vטZŠ$ȏ (I h ɐ 9y9Y9Ii "Y.y/13ْ0y246>?ٓ@ DcK~H)cƍFoKcMY Z o2 v [I X nٖpYo)q9vYxIzy{|~}9IYyi9Yiyn6xg8MIY9Y@ٙ9Yyĉƙ̹ΩٜY)M~9IYgk9Yyٟ:ZKE EӔ OԠFcd oYZ&z(*,ڢ.01 p<6z8:0M4@6ʣ >ꓤHz> ƞ2R:TZVzXZ\ڟPڥ`b:dZfzhjڦnpr:t*Yz|ڧ~*xzZy@yڨ:Zz[: ӣꩢJ5ڪnS zHwH"jzP*ڬ:Zzؚںڭ:Zzo躮ڮʬ&X S@`~G Tz+ Yw 0 W@f$&˱"$% &(#-˲'245 683=˳7BkCA{F@EN2pPX[˴HY۴\^`a۵a{Noj̀T@Zxp@Ttt v{e۸;9[۹+ Vi :LA @ tX\xH kgPƻ{ƛȻۼ;[{֛ػ۽;[{+94PX«鋾;[{ĖI\p\P֐ XP EƻP0fJ@ ;[ы#| ,ݛ<0\45l6>@LB(<l<=̼*.NP|+k8{Ź˿F0G |\p 0pH0Fs[D[|߹r v0м‰ ?/lM Pȍȅ-xJC P@ 0 00t@طp} ?nGo JD\ " \"/0 [Vq -@" Zjz>O oPkh㽮 txk/ oZntMũI = sNԭ f90 eDO q;f9ˑ^|iǰ4w}6[$̑&ⴍ6A> #'b̈3kޜ'N4eS(̟A]kBΧ5:Ja2WNF+FiAB%Xd hrmaZ{u떳kWj]l*XR]yI*U@3$L1b(p5_f>Pw>yCM7| A6롮};7ѝV jsy'cR!Nn\oHɄHe=#VO#у=CxU$$©|'э)ݠk4T*C a5d[5c%B ( 1@{F1FH}) #&rGȬgHyܙ&f2G)R b G&{Ҹ'ha(df<}ǝgdz&!A3ig3g"9O3Oi,3Mq|(?SPJJD(G&B*J,]ia㙶!'/ZYdyʡF:Vj a,Uk $28L3كDzJh!y"إx_mɗKA :|8m?Pw Ec76}1WNi(zia`h#cqf>d"-=y9Ev:S=ݴkCZGqԴ}L`,h%tH#Վ Vɧ[Ag򉴟\HKr{l!ܞiN(K K<='%<ͷ5k]ZG_[rТ{hfb laX]c*G|a ȹcͫ{zE $ Jc̱q'2}(tƇ|g_;p9BOQuG\OŠY'=8 &|AL P/b)=k?@lb!Q>HAy%L:@; vD0"HQ."*>l( WE.nqf$" 1 rFIaMt# FF,#bAyɞbf;NJ{GHhdĒ Q&cRUQ:"*U9E+fѕ7Y@ j9 \5<:,4\/fp+L.S9\¹p 0"SLX LpX̣ML18MP`Aѭ֒%eHϼ9?͗>AԟaUbPq#c<]{>nCo9wPAw3Z  ښȊ=fC՟~@6 #3 t l@s$~;+Ch9ȃ;h<|<08. #ȓ !Q%$&d'?j;^zBGh=p.lFpH0*{ *|y89:;<=>?@A$B4:ԛ>̇yC9GHIDC@*R!PqqOT!Pf ǛViɋ h|HC7ol\]^_`$a4bDcTddetfghijklmng 5,\s tDuTvdGtd5?x@:(A`E란+(iȀ2E ȉȋȌȍȎȏɐɑ$ɒ4ɓDɔTɕdɍ 6EəɚɛIɜɝIʞ ʟʢ$ʣʤ4JDʥtʦIEǨl8h`Hf tôT˵d˶t˷˸˹˺˻˼˽˾˿~[KHD̮lHtDŽȔɤʴͤLV1L$4DT\KEGքؔ٤ڴ,$Ќ ,TdtM׌$4DTdtDϩ8y J%5EUeD㻊L؇p 9<9>V! weu%GE m ]qGl9TR9LR1'-&mRk*],}):(ER(S-R&5S'=8R2%52E8U4R:7S; S9S>S=9=BSCA CeDETBmTHuH]I ΈG(+Tz9ҢSQ]RS-թ']TͺWUCLUYU[\U]"^U_^%`-_VTEcVcue}fijUVk]UluUjnVoVmRnֱ8Ũ5Ӛ :0)سʠvO0x(6 ʡR?3:G}c2.(~r DVEfFvGHIJnT4T HHaE_U=_ eeWȆtoS!(r4s`OVeQN`{gf1_MWeeaD-ci`m[Vtfgnngtvxywgygzfe}Ve||~gfh&N^g^Fn肞hh{fhhh菦耄LWqAR躨6)a]iNe|kev߾@oifJ(0yw0q~iPCie^P6e&jH``V.ii븦k뵮vkkk&l6lVFn2tK}~Iƌu.e̎jD- m6{pfLP`|mvme9·g&nQ-%Nv^&6FVfvo>i)bLIƉI1}`6 fbc =pH؇LfiGq(p(8ޯo '!7"G#W$g%w&%TiJfI(Jg.I'7(G3W4g5w678&W1b\3@x >',A7t t@FsG?GWt@IKOtH_t@LtOt¡tO/P7TGUVWWuWuXguZZ\]^_u_v`ubbdGe?f7gWvgu;^< mn'y]oq'r7sGtWugvwwD;Psɣw|}~'xr%gwtvʟU'HTʝl(dy't7s^ϋp+7GWgz=jWi;'7GWgw7xҿ'ѧ/7gwLJð ys P^GWg:/h٧ڷzӯCU/%D.'}7gC䇞P+7SZU>uS~/6=UU'wG_oO~ Hp`A 2