# Queries & Suggestions

Setup base queries for the different types as well as suggest fields to use

### Event

**Base query**

The base query for Events

```javascript
contenttype: Event
```

**Event suggest fields + sort order**

The fields to use when using suggest search

```javascript
{
    "name": 0, //{1}
    "section": 0 //{1}
}
```

1. Left part is a property mapping key to fetch while the following number is a rank weight in order to sort the results. Higher number equals higher sorting order

**Event labels**

```javascript
{
    "_all": "Free text", //{1}
    "name": "Name", //{1}
    "section": "Section" //{1}
}
```

1. A mapping from key to a Label, left part is the key specified in the fields config while the right part is the translated label to display in result

### PlanningItem

**Base query**

The base query for Planning Items

```javascript
contenttype: Planning
```

**Planning Item suggest fields + sort order**

The fields to use when using suggest search

```javascript
{
    "urgency": 0, // {1}
    "headline": 0, // {1}
    "statusHRM": 0, // {1}
    "section": 0 // {1}
}
```

1. Left part is a property mapping key to fetch while the following number is a rank weight in order to sort the results. Higher number equals higher sorting order

**Planning Item labels**

```javascript
{
    "_all": "Free text", //{1}
    "urgency": "Prio", // {1}
    "headline": "Title", // {1}
    "statusHRM": "Status", // {1}
    "section": "Section" // {1}
}
```

1. A mapping from key to a Label, left part is the key specified in the fields config while the right part is the translated label to display in result

### Assignment

**Base query**

The base query for Assignments

```javascript
contenttype: Assignment
```

**Planning Item suggest fields + sort order**

The fields to use when using suggest search

```javascript
{
    "headline": 0, // {1}
    "type": 0, // {1}
    "statusHRM": 0, // {1}
    "assigneeName": 0 // {1}
}
```

1. Left part is a property mapping key to fetch while the following number is a rank weight in order to sort the results. Higher number equals higher sorting order

**Planning Item labels**

```javascript
{
    "_all": "Free text", //{1}
    "headline": "Headline", // {1}
    "type": "Assignment type", // {1}
    "statusHRM": "Status", // {1}
    "assigneeName": "Assignee" // {1}
}
```

1. A mapping from key to a Label, left part is the key specified in the fields config while the right part is the translated label to display in result

### Article

**Base query**

The base query for Article

```javascript
contenttype: Article
```

**Article Item suggest fields + sort order**

The fields to use when using suggest search

```javascript
{
    "authors": 0, // {1}
    "channels": 0 // {1}
}
```

1. Left part is a property mapping key to fetch while the following number is a rank weight in order to sort the results. Higher number equals higher sorting order

**Article labels**

```javascript
{
    "_all": "Free text", //{1}
    "authors": "Authors", //{1}
    "channels": "Channels" // {1}
}
```

1. A mapping from key to a Label, left part is the key specified in the fields config while the right part is the translated label to display in result

**Article date options**

```javascript
{
    "label": "Publish date",
    "value": "publishedDate"
}
```

Used to allow date search in linked articles modal. Value pointing to the model key in Article mapping.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/newsroom-planner/admin-guide/settings/configuration/queries-and-suggestions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.