Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Configuring Search Profiles for Primo VE

    To configure discovery options (Configuration Menu > Discovery) for Primo VE, you must be assigned the following role: Discovery - Admin.

    Introduction

    Search profiles enable you to define groups of records that meet specific conditions so that users can search and quickly find materials and services that are offered by your institution. For example, these groups may contain records that belong to a specific library, location, or perhaps a specific resource type. Out-of-the box, Primo VE provides the following search profiles:
    • CentralIndex (Articles and more) – Searches within this profile include collections from the Central Discovery Index (CDI).
    • CourseReserves (Course Reserves) – Searches within this profile include all records that are linked to an active course. By default, this profile is inactive in a view's definition.
    • MyInst_and_CI (Search everything) – Searches within this profile include all resources that belong to your institution and all collections from the Central index.
    • MyInst_andCL_ResearchOnlyInventory (Search everything) – For Esploro environments only, Searches within this profile include all resources that belong to your institution, all collections from the Central index, and research assets with inventory.
    • MyInstitution (Library Catalog) – Searches within this profile include all resources that belong to your institution.
    • MyInstitution_ResearchOnlyInventory (Library Catalog) – For Esploro environments only, searches within this profile include all resources that belong to your institution, including research assets with inventory.
    • DiscoveryNetwork (All Libraries) – For collaborative networks only, searches within this profile include all resources that belong to your institution and other member institutions in the network.
    • DN_and_CI (Search everything) – For collaborative networks only, searches within this profile include all resources that belong to your institution and other member institutions in the network and all collections from the Central index.
    For Esploro institutions, the following search profiles are also provided by default:
    • MyInstitution_ResearchOnlyInventory –  Searches within this profile include all Esploro records (which we refer to them as “assets”). This search profile includes only assets that have inventory – for example, a file or link. Note that Esploro creates assets for many articles that the institution is likely to get from CDI with no way to deduplicate them. This is one way – we are saying only include those assets that have real or more added value by also having inventory.

    • Research – Searches within this profile include all the Esploro assets.

    • ResearchETD – Searches within this profile include all the theses and dissertations from Esploro.

    • ResearchHasInventory – Searches within this profile includes all Esploro records that have a file or link to the actual asset.  Note that Esploro covers all kinds of research outputs – publications but also creative works, datasets, software and more.

    • ResearchNonETD – Searches within this profile include all Esploro assets that are not theses/dissertations

    • ResearchOA – Searches within this profile include Esploro assets that are open access or free to read.

    Each of the above profiles are automatically assigned to their own search profile slot when a new view is created. For more information on views, see Configuring Discovery Views.
    SuprimaDefaultSearchScopes.png
    Out-of-the-Box Search Profile Slots in Primo VE - Course Reserves Inactive
    The slot for CourseReserves is inactive by default in the view. If you want the slot to appear in the UI, you must activate it in the view (see Activating/Deactivating a Search Profile Slot).
    You can create additional search profiles if you want to create scopes that restrict searches to campuses, libraries, the Central index, and custom scopes (see Adding a Search Profile and Defining a Local Data Scope), but the system does not automatically create a search profile slot for any customer-defined search profiles.

    Related Webinars and Training

    Adding a Search Profile

    In addition to the out-of-the-box search profiles, you can create custom search profiles that limit the scope of searches by campus, library, the Central index, and custom scopes. The search profiles are then used to create search profile slots in your view's configuration. For more information, see Adding a Search Profile Slot.
    Before you begin creating any search profiles, make sure that you have already created any custom scopes that you may need. For more information, see Defining a Local Data Scope.
    To add a search profile:
    1. Open the Search Profiles page (Configuration Menu > Discovery > Search Configuration > Search Profiles).
      SearchProfilesTab_NewUI.png
      Search Profiles Tab
    2. Select Add a Search Profile to open the Define a Custom Search Profile page.
      AddSearchProfile_NUI.png
      Define a Custom Search Profile Page
    3. In the List of Scopes included in the Search Profile section, enter the fields listed in the table below.
      Search Profile Details
      Field Description
      Code
      Enter a unique code for the new search profile.
      Display Name
      Enter a display label for the new search profile and then specify one or more of the following scopes: campus, library, custom, entire institution, and Central Index.
      Select the Globe button GlobeButton.png if you want to create translations for the label in the Search Profile Labels code table. For more information, see Configuring Display Labels.
      This label appears in the Search box only when a view's search profile slot contains more than one search profile. For more information, see Adding a Search Profile Slot. In the following example, a new slot called New Slot is defined with two of the out-of-the-box search profiles MyInstitution and CourseReserves:
      SlotWithMultipleSearchProfiles.png
      Display Labels for MyInstitution and CourseReserves
      Description (Optional) Enter an internal description for the search profile.
    4. Add scopes to your search profile.
      Starting from the top of the scopes list, the system matches each record with the criteria of each scope and stops when either the last scope is checked or a match is found. If a match is not found, the record is not included in the results.
      1. Select Add Scope to open the Add Scope dialog box.
        SP_AddScope_NUI.png
        Add Scope Dialog Box
      2. Select one of the following scope types from the Select Scope Type drop-down list:
        Valid Scope Types
        Scope Types Description
        My Campuses
        From the Select Campus drop-down list, select the campus to which you want to restrict searches.
        My Libraries
        From the Select Library drop-down list, select the library to which you want to restrict searches.
        Custom (Local data)
        From the Select Custom Scope drop-down list, select the custom local data scope to which you want to restrict searches. Custom local data scopes must be created in advance. For more information on how to create a local scope, see Defining a Local Data Scope.
        Local scopes can include the following records and will not include CDI records:
        • All physical, electronic, and digital inventory that are managed in Alma.

        • All records loaded from an external data source into Primo VE directly, which are not managed in Alma.

        For consortia, local scopes can also include physical, electronic, and digital inventory from the entire network and other institutions.
        Other Indexes
        From the Select Other Indexes drop-down list, select the third-party index (EBSCO or WorldCat) to which you want to restrict searches. Third-party index scopes must be created in advance. For more information, see Defining a Scope for a Third-Party Index.
        My Entire Institution
        Includes local records from the entire institution.
        If you have already added any of the local data scopes (campuses, libraries, or custom local data), you cannot specify this option.
        Central Index

        Includes records from CDI.

        Configure the following options:

        • Filter by Availability – Select the checkbox if you want to display only CDI records that have full text. After performing a search, users may select the Expand My Results option in Primo VE to display the other CDI records as well.

          If you want to display all CDI records by default, clear the Filter by Availability checkbox. After performing a search, users may select the Full Text Online facet in Primo VE to display CDI records that only contain full text.

        • Exclude CDI eBooks – Select the checkbox if you prefer to display your own eBook catalog records (in your Primo VE local index) instead of the CDI eBook records in search results.

          If this checkbox is enabled, the CDI books are removed from both the 'Filtered' and 'Expanded' search results for all collections that have portfolios in Alma. Only books affiliated with database collections that you have activated (for full text or search) are included in the CDI search results, together with your local eBook catalog records. Chapter-level records are not affected and are still returned as part of the CDI results unless the Do not show as Full text in CDI even if active in Alma option for book collections during the CDI collection activation option is enabled for the electronic collection in Alma. 

           

          • If you are also using Rapido, you can use this option, but some limitation apply. For more details, see Option 2 - Filter CDI eBooks.
          • When this option is enabled, previously saved permalinks for CDI eBooks will no longer function.
        • Search in FT – Configure whether searches check full text for matches in CDI, and whether end users can override this setting in the UI:

          1. Select the Edit FT search configuration row action to open the Define CDI Search Scope - Full Text Search dialog box:

          2. Select one of the following options:

            • Yes, Always – Search queries always check full text for matches in CDI records and there is no end user option to disable it.

            • Yes, Per end-user selection – Search queries always check full text for matches in CDI records, but end users have an option to disable it.

              The user's setting of the Search in Full Text slider is persistent for the entire session and applies for all searches in CDI scopes even if the user signs in after changing this setting. If Primo VE's UI page is refreshed, this slider returns to its default setting.

            • No, Always – Search queries never check full text for matches in CDI records and there is no end user option to enable it. This is the default option.

            • No, Per end-user selection – Search queries never check full text for matches in CDI records, but end users have an option to enable it.

              The user's setting of the Search in Full Text slider is persistent for the entire session and applies for all searches in CDI scopes even if the user signs in after changing this setting. If Primo VE's UI page is refreshed, this slider returns to its default setting.

            For additional information, see Full Text Indexing in CDI.

          3. Select Save.

        If you want to create a specialized CDI search profile that limits CDI searches to specific resource types and disciplines, see Defining Specialized Search Scopes for CDI.

      3. Select Add if you want to add more scopes to the search profile's definition. Otherwise, select Add and Close to close the dialog box.
    5. Select Save to save your changes to the search profile.

    Defining Specialized Search Scopes for CDI

    By default, search profiles that include the Central Index scope are capable of searching all available CDI collections for your library. You can create specialized search profiles that limit CDI searches to specific resource types (such as videos) and disciplines (such as visual arts) on the Define a Custom Search Profile page (Configuration Menu > Discovery > Search Configuration > Search Profiles).

    In the following example, the Central Index search profile has not configured specific resource types or disciplines, which is the default configuration:

     PVE_Selective_CDI_SearchProfile.png

    Central Index Search Profile
    To configure a specialized search profile:
    1. Open the Define a Custom Search Profile page.

    2. On the Search Profiles tab, either edit an existing scope that includes the Central Index scope type or create a new one that includes the Central Index scope type. For more details, see Adding a Search Profile.

      PVE_Selective_CDI_RowActions.png

      Specialized CDI Row Actions
    3. Select the Edit Resource Type Selection row action:

      1. Select one of the following options:

        • All CDI resource types – Select this option if you do not want to limit searches to specific resource types.

        • Selected CDI resource types – Select this option and then add the resource types to which this search profile is limited. You can limit your scopes to a maximum of five resource types. For a list of supported resource types, see Resource Types in CDI.

      2. Select Save to save your list of resource types.

    4. Select the Edit Discipline Selection row action:

      1. Select one of the following options:

        • All CDI Disciplines – Select this option if you do not want to limit searches to specific disciplines.

        • Selected CDI disciplines – Select this option and then add the disciplines to which this search profile is limited. You can limit your scopes to a maximum of five disciplines.

      2. Select Save to save your list of disciplines.

    5. Select Save to save your specialized search profile. In the following example, searches are limited to resources of type Book.

      PVE_Selective_CDI_SearchProfileExample.png

      Specialized CDI Search Profile

    Boosting Records in Blended Search Profiles

    Search profiles that include multiple search engines (such as your local institution, CDI, EBSCO, and so forth) are considered blended search profiles. For blended search profiles, you may want to boost records from a particular source to give them higher relevance in the search results.

    When forced boosting is configured, Primo VE selects the highest ranked record from the search engine and checks to see if it matches the setting of the Boost records with a score field. If the record's score matches, the record is boosted so that it can be placed in the position that is defined in the Position of boosted records field. The system applies the same boost to additional records in the search engine (as defined in the Number of results to boost field) that meet the minimum boost score and displays these records based on their boosted rank.

    In addition, the Boost factor and Deboost factor fields enable you to either increase or decrease the rankings of all records in a search engine.

    SP_BlendedSearchProfile_In_List.png
    Blended Search Profile - Includes Local Catalog and CDI
    To apply positive or negative boosts to blended search profiles:
    1. Open the Search Profiles page (Configuration Menu > Discovery > Search Configuration > Search Profiles).
    2. In the row containing the blended search profile that you want to configure, select the Configure blending row option or the Blended link to open the Edit Blending Configuration page, which displays the list of search engines included in the search profile.
      SP_BoostList_Blending_NUI.png
      Edit Blending Configuration Page
    3. For each search engine, select the Customize row option if you have not already configured this search engine. Otherwise, select the Edit row option.
    4. Select and configure one of the following Boost Types:
      • Boost - This option opens the following page, which enables you to apply positive boosts to records from the search engine:
        SP_Boost_Parameters_NUI.png
        Boost Configuration Details
        Specify the parameters listed in the following table.
        Boost Configuration Parameters
        Parameter Description
        Boost factor

        This field specifies a constant boost factor that is added to the record boost for all records in this search engine. The minimum factor must be greater than 1 (such as 1.5), and the maximum factor must not exceed 10.

        This boost is independent of the boost provided by the following fields.

        The following fields configure a forced boost to a maximum of 9 records in the search engine:
        Number of results to boost
        The maximum number of records to boost in the search results. Select a value from 1 to 9.
        Boost records with a score
        Based on many factors, the search algorithm assigns scores to records returned in the results. This field enables you to specify the minimum score needed before applying this type of boost to a record. Select the minimum score needed to boost a record:
        • high – Only matching records with high scores are given a boost.
        • medium – Only matching records with medium scores and higher are given a boost. 
        • low – Only matching records with low scores and higher are given a boost.
        • none – No boost is given.
        Position of boosted records
        Specify the position within the search results to place the boosted records: top (2nd record), middle (5th record), bottom (9th record), none.
         
      • Deboost - This option opens the following page, which enables you to apply a negative boost to records from the search engine:
        SP_Deboost_Parameters_NUI.png
        Deboost Configuration Details
        Specify the following parameter:
        Deboost factor - The number that is multiplied by the record's original rank to decrease its rank. The factor must be a number between 0 and 1 (such as .25).
    5. Select Save.

    Defining a Local Data Scope

    Custom local data scopes enable you to create scopes that limit searches in the local database to specific library metadata (such as resource type or availability). After a custom scope is defined, you can add it to new and existing search profiles and also to search profile slots in the view's configuration. For collaborative networks, you can also define scopes for other institutions and their libraries.

    To define a local data scope:
    1. On the Search Profiles page (Configuration Menu > Discovery > Search Configuration > Search Profiles), select the Custom Local Data Scopes tab.

      SP_CustomLocalDataScopesTab_NUI.png

      Custom Local Data Scope Tab
    2. Select Add a Custom Scope to open the Define a Custom Scope page.

      SP_DefineCustomScope_NUI.png

      Define a Custom Scope Page

      For collaborative networks, the Scope Population field appears also in the Scope Details sections.

    3. Specify the following general fields:

      Scope Details Section
      Field Description

      Code

      Enter a unique code for the new custom scope.

      Name

      Enter a name for the new custom scope.

      Description

      (Optional) Enter a description for the new custom scope.

      Scope Population

      For collaborative networks only, select one of the following options:

      • My Institution – Indicates that the custom scope includes inventory from your institution only. This is the default functionality for non-collaborative networks.

      • Entire Network – Indicates that the custom scope includes inventory from your institution and/or other institutions in your network.

    4. In the Scope Conditions section, select Add a Condition to open the Add Condition dialog box.

      SP_Add_Up_To_3_Conditions_NUI.png

      Add Condition Dialog Box - First Condition Only
    5. Specify the following fields to define a condition.

      Add Condition Dialog Box Fields
      Field Description

      Search Index

      For non-collaborative networks and collaborative networks (Scope PopulationMy Institution), choose one of the following types of search indexes:

      • Inventory – Limits search results to specific types of inventory (such as available physical records) that were loaded directly into Primo VE from an external source. The following types of inventory are supported: Available Digital, Available Electronic, Available Physical, Available Research (for Esploro), Course Code, External data source, Has Course, Is part of any collection, Is part of a collection/subcollection (note that is includes inventory only within a collection or subcollection and does not include inventory within any of its subcollections), Location, Physical Availability - Campus, and Physical Availability - Library.

      • Local Fields – Limits search results to records that match data in a specific local field.

      • Metadata – Limits search results to records that match specific bibliographic record metadata (such as Subject, Title, ISBN, and so forth).

      For collaborative networks only (Scope PopulationEntire Network), choose one of the following types of search indexes:

      • Entire Network Inventory – Limits searches to available digital, electronic, and physical inventory in the entire network.

      • Other Institution Inventory – Limits searches to inventory at other institutions in the network. The following options are valid:

        • Other institution – Limits searches to the following types of inventory for a specified institution:

          • All – Limits searches to available digital, electronic, and physical inventory.

          • Available Digital – Limits searches to available digital inventory.

          • Available Electronic – Limits searches to available electronic inventory.

          • Available Physical – Limits searches to available physical inventory.

        • Other Institution Libraries – Limits searches to a specific library at an institution.

        • Other Institution Locations – Limits searches to a specific location within a library.

      • Metadata – Limits searches to bibliographic record metadata (such as Subject, Title, ISBN, and so forth) in the entire network.

      You can define up to three conditions for each custom scope. If you need to support more institutions/libraries, create a custom scope for each institution/library and link them to a search profile.

       

      Operator

      Select one of the following operators, which may not be available for all types of search indexes:
      • Contains Keywords – This condition checks to see that the record contains the specified keywords, which are entered in the Value field.
      • Doesn't Contain Keywords – This condition checks to see that the record does not contain the specified keywords, which are entered in the Value field.
      • Contains Exact Phrase – This condition checks to see that the record contains the specified exact phrase, which is entered in the Value field.
      • Doesn't Contain Exact Phrase – This condition checks to see that the record does not contain the specified exact phrase, which is entered in the Value field.
      • Equals – This condition checks to see that the search index matches the value selected from the Value drop-down list.
      • Exists – This condition checks to see that the record contains this type of metadata.
      • Doesn't Exist – This condition checks to see that the record does not contain this type of metadata.

      Value

      Specify a value if the selected operator requires one.

      Logic (conditions 2 and 3 only)

      Specify the boolean operation that is applied to the second and third conditions.

      • And – indicates that this condition and the previous condition must be met.

      • Or – indicates that this condition or the previous condition must be met.

      This field only displays for the second and third conditions.

      Precedence is given to the AND operator. In the following example, either condition 2 and 3 must be met or condition 1 must be met:

      condition_1 OR (condition_2 AND condition_3)

    6. Select Add Condition to save your new condition. Otherwise, select Cancel to exit the dialog box without making changes.

    7. If you want to add another condition (a maximum of three conditions is permitted), repeat steps 5 through 7. Subsequent conditions require you to specify the Logic drop-down field.

      SP_Add_Another_Condition_NUI.png

      Add Condition Dialog Box - Additional Conditions 2 and 3
    8. On the Define a Custom Scope page, select Save to save your changes and to return to the Search Profiles tab.

      In the following example, both conditions must be met to be considered a match.

      SP_CustomScopeConditionExample.png

      Example Custom Scope

    Defining a Scope for a Third-Party Index

    Other index scopes enable you to limit searches to third-party search indexes (such as EBSCO and WorldCat). After an index has been defined, you can add it to a Search Profile, which can then be used in a view.

    It is not recommended to blend third-party indexes with local and CDI searches in the library's default scope since this may impact the end users experience in the areas of facets and relevancy between the different indexes. In addition, slow responses from the external index will impact the response time for all results. For more information, see Details Fields for Other Indexes.

    In addition, you can create deep search scopes that enable users to search the catalogs of other Primo VE institutions that have provided access to your institution. When a remote scope is searched, the local institution requests the following information from the remote institution so that it can be displayed to users in their search results: matching records, facets, and availability of records. As with other blended search scopes, you can boost records in deep search scopes to increase their relevancy in the results.

    In the first phase of this capability:

    • The information retrieved from the remote institution includes the bibliographic records and the remote institution's holdings information, which appears in the Get It from Other Institutions section. In addition, the searching institution retrieves the records within its own interface and offers its own fulfillment options to request the records, such as ILL requests. The availability indicator appears as Check for available services in the Brief Results page for records retrieved from remote institutions. When users open the record's full display, the availability and services are calculated.

    • The translations for the location's facets are not supported.

    • The Availability top-level facet will not be available for Primo VE deep searches.

    • Dedup\FRBR will display according to definitions in the remote environment:

      • If Enable FRBR is selected in the remote view,  FRBR appears (regardless of the configuration in the source view).

      • If Enable FRBR is not selected in the remote view, FRBR does not appear (regardless of the configuration in the source view).

    • If a remote record and a local record are the same, they are not deduped.

    • Search Profiles defined with multiple deep search scopes is not supported.

    To define a scope for a third-party search index:
    1. Open the Search Profiles page (Configuration Menu > Discovery > Search Configuration > Search Profiles), select the Other Indexes tab.
      PVE_AddSearchWebhook.png
      Other Indexes Tab
    2. Select Add Other Index and then select one of the following third-party indexes: Ebsco, WorldCat, Deep Search, or Search Webhook.
    3. In the Scope Details section, specify the following general fields:
      General Fields for Other Indexes
      Field Description
      Code
      Enter a unique code for the new other index scope.
      Name
      Enter a name for the new other index scope.
      Description
      Enter a description for the new other index scope.
    4. Depending on the selected search scope type, specify the following fields as needed by the third-party index.
      Details Fields for Other Indexes
      Field Description
      EBSCO Only:
      User name

      Specify the user name supplied by EBSCO to access the service. To use this functionality, you must have an EIT profile. If you do not have an EIT profile, or are not sure if you have one, contact your account manager for details or contact EBSCO Support.

      The EBSCO plug-in enables Primo VE to query and receive results from the EBSCOhost API. End users who are logged on to Primo VE do not need to log on to EBSCO to search for EBSCO content.
      The EBSCOhost API does not support the following:
      • Starts with option for title searches. The API returns all results, not just the titles that start with the search term.
      • Pre-limiting the search by language.
      • Facet record counts. When searching in a scope that includes the EBSCOhost API, none of the facets will have record counts.
      The EbscoHost API returns only the following facets, which are mapped to Primo VE facet codes for display in Primo VE:
      • JN (Journal) – maps to jtitle in Primo.
      • ZE (SubjectThesaurus) – maps to topic in Primo.
      If the EbscoHost API does not return a SubjectThesaurus facet, the EBSCO adaptor attempts to use one of the other EBSCO subject facets in the following order: QZ (Subject), ZG (SubjectCompany), ZO (SubjectGeographic), or QN (SubjectNAICS).
      For blended searches:
      • The system returns all relevant facets for non-EBSCO results, but they do not include record counts.
      • Other than Resource Type, facets that are not supported by the EBSCOhost API do not return results from EBSCO.
      • If users select a Resource Type facet value, the system returns the non-EBSCO results and also query EBSCO to return EBSCO records of that facet value. If any other non-supported facet is selected, no EBSCO results are returned.
      • Because the EBSCOhost API results do not include all of the facet values, counts, and advanced search options, it is recommended that you display EBSCOhost API results in a separate search scope.
      Password
      Specify the password supplied by EBSCO to access the service.
      Databases
      Enter a list of EBSCO short name databases to which you subscribe. For a list of database names, refer to the following EBSCO page:
      For example: rlh, ah1, 8gh
      WorldCat Only:
      WorldCat API Key

      Specify the API key supplied by WorldCat.

      The WorldCat plug-in enables Primo VE to query and receive results from the WorldCat Search API. End users that are logged on to Primo VE or using an on-campus terminal do not need to log on to WorldCat to search for WorldCat content.

      Because the WorldCat Search API does not return facets, search profiles that only include WorldCat do not display any facets. For blended searches that include WorldCat:

      • The system will display facets, but they do not include the total number of records.

      • When a facet is selected, the system queries WorldCat for additional results.

      Deep Search Only: This option requires configuration in the remote Primo VE institution to enable your institution to access its catalog. For more information, see Configuring Deep Search in a Remote Primo VE Institution.

      Define allowed users (New for April)

      Configures user restrictions for the index. For more details, see Defining Allowed Users for Other Indexes.

      Environment

      Enter the base URL of the Alma institution that you want to access (for example: https://university.alma.exlibrisgroup.com).

      Institution Code

      Enter the institution code of the remote Alma institution (for example, 01ALMA_INST).

      Display Institution Name

      Enter the display name of the remote institution, which appears under the Get It from Other Institutions section in the record's full display.

      Search Webhook Only: This option requires you to develop the Search Webhook first. For more details, see Search Webhook in the Ex Libris Developer Network.

      Define allowed users (New for April)

      Configures user restrictions for the index. For more details, see Defining Allowed Users for Other Indexes.

      URL

      The URL of the remote search index. 

      Example: http://docs.newsbank.com/api/primo/PrimoSearch/

      API Token

      The key that was set in the search webhook server. It enables Primo VE to authenticate with the search webhook services.

      Example: ncdprimo

    5. Select Save to save your new other index scope. Otherwise, select Cancel to exit the dialog box without making changes.
      SP_OtherIndexExample_EBSCO_NUI.png
      Example EBSCO Scope

    Defining Allowed Users for Other Indexes

    The Allowed Users page allows you to limit searches of Deep Search and Search Webhook search scopes to users who are within the following restrictions: IP address, on campus, restricted, or user group. Users who do not meet these restrictions receive the following message after attempting to search the index when off campus or not signed in:

    You must be signed-in or on campus to search in this resource.
    To restrict user access for other indexes:
    1. On the Search Profiles page, select the Other Indexes tab.

    2. Add or edit an index of type Search Webhook or Deep Search to open its configuration page. For details on how to configure a third-party index, see Defining a Scope for a Third-Party Index.

      PVE_DS_Index_DefineAllowedUsers.png

      Other Index Configuration Page - Deep Search Example
    3. Select the Define allowed users option to open the Allowed Users page, which lists all rules defined for this index. Rules are processed starting at the top of the list, and if a user matches the criteria defined by that rule, the user is permitted to search the scope.

      PVE_AllowedUsers_April2022.png

      Allowed Users Page
    4. Select Add Rule to open the Define Allowed Users page, which allows you to configure the parameters which define the criteria used to determine whether a user is given access. For a rule to pass, users must match all criteria specified for each parameter.

      PVE_DefineAllowedUsers_April2022.png

      Define Allowed Users page
    5. Select Add Parameter to open the Input Parameters dialog box. For each rule, you can add one parameter for each of the group type specified in the Name field.

      RSGD_AddParameter_NewUI.png

      Input Parameters Dialog Box
    6. Enter the following fields:

      • Name - Select one of the following group types: IP Range, On Campus, Registered, or User Group.

      • Operator - Select one of the following operators: =, Not Equals, In List, Not In List, or Contains.

      • Value - Depending on the type of group and operator, specify a value.

    7. Select Add Parameter to add the parameter to the rule.

    8. Select Save to save your rule.

    9. Select Save to save your rules and to return to the other index definition page.

    10. Select Save to save your changes to the other index.

    Deleting a Search Profile, Custom Scope, or Other Index

    The Search Profiles, Custom Local Data Scopes, and Other Indexes tabs enable you to remove unwanted search profiles, custom scopes, and other indexes, respectively.
    If a search profile is being used by a view, it may still appear in the view, but it will be deactivated.
    To delete a search profile, custom scope, or other index:
    1. Open the Search Profiles page (Configuration Menu > Discovery > Search Configuration > Search Profiles), select either the Search Profiles, Custom Local Data Scopes, or Other Indexes tab.
    2. Select Delete in the row action list in the row that contains the profile, scope, or index that you want to delete.
    • Was this article helpful?