Search queries

To construct a Power Search query, you need to use the search syntax specific to Solr, the third-party search software embedded in Contenta.

Data is indexed in Solr fields. Therefore, queries are preceded by the name of the index field you want to search, followed by a colon.

Search query index fields include:

  • Default fields that are part of Solr, such as CONTENT_EN for querying English language content.
  • XMLCONTENT for querying XML structures such as elements and attributes, as well as content.
  • S1000D properties, available to Contenta S1000D users.

Search Query Examples

You can use verbatim, quotes, logical operators, and regular expressions to construct a query, as these examples describe.

  • The word Condition in the content of S1000D version 4.1 objects, when you are not sure about sentence case, but you want those that start with capital C to be ranked the highest:

    S1000D_VERSION:4.1 AND (CONTENT_EN:Condition CONTENT_EN_LC:Condition)

    • same search, but you want only those that start with a capital C returned:

      S1000D_VERSION:4.1 AND CONTENT_EN:Condition

    • same search, but you want all objects with the word condition returned, regardless of the case combination:

      S1000D_VERSION:4.1 AND (CONTENT_EN_LC:condition)

  • Objects that have the word Bicycle, but not the word guard in their content:

    CONTENT_EN:Bicycle AND NOT CONTENT_EN:guard

  • A regular expression that limits the scope of your search in the Contenta hierarchy. You must escape with a backslash (\) special characters like the forward slash (/) :
    • objects with Bicycle under the namepath /S1000D/Data Modules/SAMPLEBIKE/D00\/

      CONTENT_EN:Bicycle AND NAMEPATHS:/\/S1000D\/Data Modules\/SAMPLEBIKE\/D00.*/

    • objects with Bicycle using a less exact namepath:

      CONTENT_EN:Bicycle AND NAMEPATHS:/.*\/SAMPLEBIKE\/D00\/.*/

  • All objects that contain a warning element, regardless of whether there are attributes on the warning elements:

    XMLCONTENT:<warning>

  • All objects that contain a warning element in Issue 4.1 and the Document Type is proced:

    XMLCONTENT:<warning> AND S1000D_VERSION:4.1 AND DOCUMENT_TYPE:proced

  • All objects with the word bicycle in their content and proced as their document type:

    CONTENT_EN_LC:bicycle AND DOCUMENT_TYPE:proced

  • All objects with an Issue date in the year 2012:

    ISSUE_DATE:*2012

  • All objects with a Model ID of S1000DBIKE, which are not Data Modules:

    MODEL_IDENTIFICATION_CODE:S1000DBIKE NOT TYPE:DModule

  • All CGM graphics files with DA52000 in their name:

    MIME_TYPE:image/cgm AND NAME:*DA52000*

  • All objects containing the case-sensitive exact phrase Remove and install in their content, with a Tech Name of either Bicycle or Lighting:

    CONTENT_EN:"Remove and install" AND (TECHNICAL_NAME:Bicycle OR TECHNICAL_NAME:Lighting)

  • All objects with an Info Name of Description and a Tech Name of either Bicycle, Horn, or Lighting:

    TECHNICAL_NAME:(Bicycle OR Horn OR Lighting) AND INFORMATION_NAME:Description

XML Queries

These Power Search queries apply to the XMLCONTENT field, as shown in the following examples. You should precede search queries with the XMLCONTENT: field name.

To search forthiswill result inand be indexed (content + markup) no stemming supported
Text“security”Objects that contain "security" in element content, attribute values, comments, or processing instructions. Will not match objects that have only a <security> element.“security”
An XML element“<security>”Objects that contain <security> elements.“<security>”
A public identifier“-/W3C/ / NOTATION Portable Network Graphics //EN”Objects that contain -//W3C//NOTATIONPortable NetworkGraphics//EN.“-//W3C//NOTATIONPortable NetworkGraphics//EN”
An attribute value“U8025”Objects that contain this text in attribute values, element text, processing instruction text, and XML comments. Attribute values containing the characters <, =, > cannot be found this way; therefore, searching for "4 > 3" will not work. We recommend that you always include the attribute name as shown in the following row.“U8025”
An attribute“enterpriseCode=\"U8025\"" Objects that contain anenterpriseCode attribute set to "U8025"

When performing this search, enter a backslash in front of each quote that wraps the attribute value.

“enterpriseCode=\"U8025\""
A specific element with text"<simplePara>Default BREX coding</simplePara>"Elements that contain the exact text."<simplePara>Default BREX coding</simplePara>"
A specific processing instruction“<?xm-replace_text Paragraph?>”Objects that contain this processing instruction.“<?xm-replace_text Paragraph?>”
A specific comment"<!--Arbortext, Inc., 1998-2009, v.4002-->"Objects that contain the given comment."<!--Arbortext, Inc., 1998-2009, v.4002-->"
An XML element

(special case)

“<msgph/>”Objects that contain the <msgph> element, including empty <msgph> elements.“<msgph>”

Custom Queries

You can search for any custom field name by specifying all caps, replacing spaces with an underscore, and preceding the search term with a colon. For example, a field named Access Level would be specified as ACCESS_LEVEL_S.

S1000D Queries

S1000D users can search for the following property sheet metadata fields:
  • APPLIC_CROSSREF_TABLE_REF
  • BUSINESS_RULES_REFERENCE
  • COUNTRY_ISO_CODE
  • DATA_MODULE_CODE
  • DISASSEMBLY_CODE
  • DISASSEMBLY_CODE_VARIANT
  • DOCUMENT_TYPE
  • INFORMATION_CODE
  • INFORMATION_CODE_VARIANT
  • INFORMATION_NAME
  • ISSUE_DATE
  • ISSUE_INWORK_NUMBER
  • ISSUE_NUMBER
  • ISSUE_TYPE
  • ITEM_LOCATION_CODE
  • LANGUAGE_ISO_CODE
  • LEARN_CODE
  • LEARN_EVENT_CODE
  • MIME_TYPE
  • MODEL_IDENTIFICATION_CODE
  • NAME
  • ORIGINATOR_CODE
  • ORIGINATOR_NAME
  • PUBLICATION_MODULE_CODE
  • PUBLICATION_MODULE_ISSUER
  • PUBLICATION_MODULE_NUMBER
  • PUBLICATION_MODULE_TITLE
  • PUBLICATION_MODULE_VOLUME
  • PUB_ID_NUMBER
  • QUALITY_ASSURANCE_VERIFICATION
  • RESPONSIBLE_PARTNER_CO_CODE
  • RESPONSIBLE_PARTNER_CO_NAME
  • S1000D_VERSION
  • SECURITY_CAVEAT
  • SECURITY_CLASSIFICATION
  • SECURITY_COMMERCIAL_CLASS
  • SHORT_PUBLICATION_MODULE_TITLE
  • SKILL_LEVEL_CODE
  • SUBSUBSYSTEM_CODE
  • SUBSYSTEM_CODE
  • SYSTEM_CODE
  • SYSTEM_DIFFERENCE_CODE
  • TECHNICAL_NAME
  • UNIT_OR_ASSEMBLY_CODE
  • VERIFICATION_TYPE