Set Up Top-Level Facets (Marquee Only)

Full-faceted browsing is a browsing experience for Marquee sites that provides administrators a tool to build a browsing experience where viewers do not need to see the underlying file system. Facet-enabled data fields are shown in field-value pairs at the top level of Marquee, if the site option Show toplevel facets is turned on.

Overview

Sites enabled with toplevel faceting can be thought of as pure consumer sites. This is why we have disabled Uploads for these sites, as well as the Advanced Search option. Since this new view relies entirely on metadata, it is very important to set up your metadata carefully. Theoretically it is irrelevant how your data is organized on the file system, but it is helpful to organize your filesystem structure so it matches or at least relates to your metadata structure.

Example of Toplevel Faceting on a consumer site:

Configure Top-Level Facets

To complement the "Show toplevel facets" site option in Marquee, you can use additional site options such as Use the Portal Navigator and Display folders in the main area. The combination of these options allows users to browse assets on a Xinet server without ever needing to know anything about the underlying filesystem.

To enable a Marquee site to show facets at toplevel, we recommend setting the following options in PORTALADMIN:

•	Display folders in main area: Off

•	Use Portal Navigator: Off

•	Include facets in Top Level: On

•	Show facets for the whole tree starting at the current path when browsing: On

In order for users to see metadata-value pairs on the toplevel page, make sure that you have metadata fields enabled with the facet option and that the fields are in the user's template. Built-in facets may be enabled under the Database > Searching tab and will also show up under the new facet view on the toplevel page.

We have created the toplevel facet view to provide a ‘consumer-friendly’ view for assets on the Xinet server, and have turned off Uploads and Advanced Search by default when the site option Show toplevel facets is turned on.

Figure: Show toplevel facets is turned on:

Customize Top-Level Facets

The preview shown for each metadata field-value pair is by default the first actual preview found by a search. This default is created and used automatically. If you want a different, standard default preview, you can customize the image that is shown for each metadata field-value pair as outlined below.

To set up a facet view at toplevel for Marquee sites:

1.	In PORTALADMIN, we recommend setting the following options:

• "Display folders in main area: Off

• "Use Portal Navigator: Off

• "Include facets in Top Level: On

• "Show facets for the whole tree starting at the current path when browsing: On

2.	In order to view metadata-value pairs on the toplevel page, make sure you have metadata fields enabled with the facet option and the fields are in the user's template. Built-in facets may be enabled under the Database > Searching tab and will also show under the new facet view on the toplevel page.

3.	We have created the toplevel facet view to provide a 'consumer'-friendly view to assets on the Xinet server and have turned off Uploads and Advanced Search automatically.

To customize the styling of auto-generated toplevel facet previews:

1.	On the Portal server under <Document Root>/<sitename> you will find a file called

<IP address>.stackpreviews.sqlite3

2.	Create a new file at the same location by copying this file and adding a '.custom' to it.

<IP address>.stackpreviews.sqlite3.custom

3.	Add key-value pairs to this newly created text file and point each key-value pair to your custom image, as follows:

<key>:<field value>,<image file>

Where:

•	<key> is a combination of the string “field”, the field's keyword ID, an underscore (_) and the string “str” (for text fields). To get the keyword ID, you could either use a tool like Firebug or check the content of the stackpreview table in the sqlite3db database.

•	<field value> is the particular value that may occur in the field

•	<image file> is the image file. You must include its relative filepath starting from the site's <Document Root>/<sitename>/templates/images/ folder (If images are in this location, a filepath is not necessary.)

Notes:

•	It is important to use the comma as a separator and to make sure you have a single comma per line.

•	There are no beginning or end tags required in this file, only the list of key-value pairs pointing to custom images as described above.

•	These custom images will be shown to all users using the site.

•	You can add to, update, or delete the custom file as you need, and the previews will sync automatically.

•	It is also possible to change or overwrite the photostack type styling as well. This is a CSS class (display styling) and could be changed by changing that exact class in the CSS file for that site.

Example:

In the following example, assume all of the images are stored in the default location,
<DOCUMENT ROOT>/<PORTAL SITE NAME>/templates/images/

 

field123_str:Skateboarding,flyingskateboarder.jpg

field123_str:Skiiing,victoriousskiier.jpg

field123_str:Climbing,iceclimber.jpg

field123_str:MTB,windsweptroad.jpg

field123_str: Paddling,kayaker.jpg

field007_str:Avalanche Safety Gear,avalanchegear101.jpg

field007_str:Downhill Skiing, downhill-skis203.jpg

field007_str:Backcountry Skiiing,back-skis446.jpg

field007_str:Crosscountry Skiing,skiboot34.jpg

The screen grab below is a visual representation of how this example will look The first five lines are in the first image; the other lines are in the second image.