Getting Started with Paligo

Advanced Search

The Advanced Search feature allows you to find content easily by allowing for many powerful search options. You can access the Advanced Search in multiple ways.

  1. To access the Advanced Search:

    • To go directly there, you access it from the Magnifier icon , just like the Quick Search. But then click the funnel icon to go to the Advanced Search instead:

    • You can also access the Advanced Search in conjunction with other types of navigation. For instance, if you select a folder in the Content Manager , or if you click a category in the Taxonomy Manager to find content that way, you can then use that search result as the basis for further filtering in the Advanced Search:

      Accessing search starting from filtering by taxonomy

      This is a very quick and at the same time powerful way to drill further down into selected content.

  2. To search in the Advanced Search view, just specify the options you want:

    1. Enter a keyword if you want. That would narrow down the search to only components containing that text. It can be left blank to search only the other options.

    2. The Types field lets you specify a certain type of component, such as a text document, an image, a folder, etc.

    3. The Contains (Element) field is a powerful way to search for text documents that have specific types of content (XML elements) in them. If you want to find only topics that are instructions, and therefore have the procedure element in them, just specify that here. 

      Tip

      For power users it is useful to know that this field actually accepts more advanced expressions too, using Xpath. So you can specify for instance mediaobject[ancestor::procedure] to find any topic where there is a mediaobject inside a procedure.

    4. In the Editors field you can find components by a certain user.

    5. The Date fields provide calendars to specify a date range, to find content from the last week, month, or any date range.

    6. The Resource ID field is useful if you actually know the id and just want to get directly to it. In this case you would normally specify this and nothing else.

    7. The Languages field allows you to narrow down your search to only components that exist for certain languages.

    8. The Taxonomy field can be used to specify components tagged with a specific taxonomy. But it can also be pre-filled if you used a taxonomy to get here in the first place, as in the above example.

    9. Same thing with the Folder field, it will narrow down the search to a specific folder and will be pre-filled if you got here by clicking a folder first.