Managing Content... 3

Transcription

1 Managing Content

2 Contents 2 Contents Managing Content... 3 Configuring Community Content Types... 3 Configuring Spell Check...3 Managing Search... 3 Configuring Content Search... 3 Configuring OpenSearch... 5

3 Managing Content 3 Managing Content Manage the kinds of content your users can create in the community, configure spell check, and your community's search settings. Configuring Community Content Types Select which kinds of content you want your users to be able to create in the community, such as blogs, documents, polls, and projects. Fastpath: Admin Console > Content > Content Types You can set up your community so that users can create a variety of different content types, such as blog posts, discussions, and documents. You choose any or all of these for your community. Note: If you change your mind later, deselecting a content type does not remove existing content from your community, it only prevents people from creating new content of that type. Configuring Spell Check As a community manager, you can customize the spell check feature in the Admin Console. The spell checker uses the main dictionary you specify for all content in the community so that Jive will check spelling as users create and edit content. Consider using the technical dictionary if your community creates content with terms from the computer industry. You can also add words to your custom dictionary; that way, words commonly used where you are (such as jargon or product names) won't be marked as misspelled. Fastpath: Admin Console > Content > Spell Check Managing Search Jive provides configurable search access to content and people, as well as access to external search engines that support OpenSearch. Configuring Content Search Content search indexes documents, discussions, blogs, status updates, and external content. In addition to content written and published with the community's editor, the search feature also searches the following file types:.html,.rtf,.txt,.pdf,.ppt,.pptx,.doc,.docx,.xls,.xlsx,.odt,.ods and.odp (OpenOffice formats). The application will also search the contents of a.zip file.

4 Managing Content 4 Configuring Search Synonyms You can configure the search feature to recognize synonyms for improved search results. The synonym search feature improves search results by allowing you to create lists of synonyms. For example, you might want a search for "big" to return results for "large", and vice versa. Or, if your users search using terms specific to your industry, you might want to set up a synonym that associates commonly used terms, such as "mobile" and "phone". You can also set up synonyms for the names of users. For example, you might want to set up "James, Jim, Jimmy" or "Susan, Suzy, Susie". To set up search synonyms: 1. Go to Admin Console > Content > Content/User Synonyms. 2. Type in a comma-separated list of synonyms. 3. Click Add Synonyms. Promoting Content Search Results You can create rulesets to ensure that particular keywords always return specific content results, even when that keyword does not occur in the content. Fastpath: Admin Console > Content > Promoted Results Promoting a result ensures that when you type certain keywords, a content item you select will always be at the top of the results. You can associate multiple keywords or key phrases with a single content item by entering the terms separated by commas. You can also associate different content items with the same keyword, so that several content items show up when a user queries that keyword. Use the Priority field to determine which promoted results for a keyword appear first. For example, if you wanted the European, American, and Asian holiday schedules in your organization to be promoted for the keyword holidays, you could create a rule for each document linking it to the keyword holidays. Then you could rank these schedules 1, 2, and 3 in the results by assigning the rules priorities 0, 1, and 2. Keep in mind the following limitations when promoting results: Keywords must be at least three characters long. Single keywords can function as wildcards in spotlight search, but when you specify a key phrase, the query must be an exact match for the key phrase. (Standard searches typed in the search page, or entered by typing in the search field and pressing Enter do not support wildcards unless you type * as part of the string.) For example, if you specify "quarter" as a keyword, your selected content will be returned for spotlight search queries on "quart" as well as "quarter." But if you specify "quarterly sales," your selected content will not be returned for queries on "quarter," "quarter sales," "quarterly," or "sales," only for queries on "quarterly sales." No two rules can have the same priority number, so multiple rules for the same keyword or keyword combination must be in sequential order.

5 Managing Content 5 Note: Spotlight search does not need to have all promoted words in order to promote a result. To create rules and rulesets for promoting results: 1. In the Keyword(s) field, add one or more keywords separated by commas. 2. In the Content Link field, type the full URL of a content item, for example yourcommunity.com/docs/doc Click Add. 4. If you want more results to be returned for the same keyword(s), add more rules with the same keyword(s) and different content. Then assign a priority to each rule within the group of rules. You can do this automatically by creating the rules in order of document priority, but you can also edit the Priority field after a rule is created to move it anywhere in the list. Moving a rule to a higher priority will move other rules down in priority, affecting the numbering of all rules below it. Priority applies only within a group multiple rules with the same keyword or keywords. Note that when you change the priority of an existing rule, the rules above and below it will be renumbered to create a sequential list. Because the rules will appear in one sequential list, you might end up with a sequence like this one, which represents two rulesets: 24. keyword1 document g 25. keyword1 document a 26. keyword1 document q 27. keyword2, keyword3 document x 28. keyword2, keyword3 document r 28. keyword2, keyword3 document n The first ruleset says that when keyword 1 appears in a query, the first three results will be documents g, a, and q. The second ruleset says that when either keyword 2 or keyword 3 appears in a query, the first three results will be documents x, r, and n. Configuring OpenSearch You can make some external search engines available to people using Jive. If a search engine supports OpenSearch, you can add support for it so that the search engine will be used (in addition to the internal search engine) when people search for content in Jive. Examples of OpenSearch engines include Technorati and Wikipedia, plus Jive communities. Engines that support OpenSearch provide a descriptor XML file and usually publish the file at a public URL. The descriptor tells OpenSearch clients what they need to know to query the search engine. Fastpath: Admin Console > System > Settings > OpenSearch Engines There are two ways you can add OpenSearch engines in the Admin Console: Enter a descriptor URL, then click Add Engine from Descriptor URL. The application will visit the URL to retrieve the descriptor XML file, then retrieve the needed information from the file.

6 Managing Content 6 If the application gets the information it needs, you're finished. However, you might get prompted for more information, such as login credentials if the engine is secure. Note that you can edit engine properties later. Click Add Engine from Form, then fill out the form to include the required information. The information asked for here is what would be included in the descriptor XML file. This is the same information you can edit for an engine, as described below. As you edit the engine's properties, keep in mind that: The icon URL is a URL to an icon representing the search engine. Jive will display this in its UI. The application uses the search URL to send the user's query. The search result content type is the content type, such as application/rss+xml or text/html, that the search engine's results will be returned in. If this is a type that the application can parse, such as application/rss+xml, the results will be displayed directly; if not, the application will display a link through which the user can separately search the engine's site itself. If you specify HTML as the content type, a sidebar will display a link that people can use to search for their phrase at the OpenSearch location. If they search, their results are displayed in a new window. If you specify RSS or Atom as the content type, the application will display a new tab with the Name value. The application will parse returned results into a format that displays on the search results page, under the new tab. (If you want to see a preview of the first 8 OpenSearch results displayed directly inside the main search results, so users are more readily aware of the OpenSearch alternative, you should also select the Show result preview check box. The query test term can be anything you like to test queries. You might need to enter a user name and password if the search engine requires login credentials. The Enabled check box is selected by default, meaning that user searches will query the engine. Uncheck the box to make the search engine unavailable to users. The Show result preview checkbox controls whether OpenSearch results are shown in the body of your search results themselves. When you select this checkbox for any OpenSearch provider, your main search results will show a preview of up to 8 results from the OpenSearch provider after the first four results from your Jive site. This setting makes OpenSearch more noticeable to users who might overlook its presence in the left pane of search. Note: The Jive application is also an OpenSearch provider (although OpenSearch isn't a good replacement for searching content it contains). You just have to point your OpenSearch reader to Jive's OpenSearch XML descriptor. For OpenSearch readers that aren't able to autodetect the descriptor, you'll have to add it manually. The OpenSearch descriptor for your community is located at For example, for the Jivespace descriptor, go to Provide this file as the descriptor for your OpenSearch reader.