# Pure Display

Source: https://www.potatoannotator.com/docs/annotation-types/pure-display

The pure_display type shows content to annotators without collecting any annotation. Use it for section headers, inline instructions, or formatted guidance between annotation fields.

## Basic Configuration

```yaml
annotation_schemes:
  - name: "instructions_header"
    description: "Please read the text carefully and answer the following questions."
    annotation_type: "pure_display"
```

## Configuration Options

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `name` | string | Yes | Unique identifier (not used in output) |
| `description` | string | Yes | Content to display |
| `annotation_type` | string | Yes | Must be `"pure_display"` |

## Examples

### Section Header

```yaml
annotation_schemes:
  # Instructions section
  - name: "instructions"
    description: "## Instructions\n\nRead the text below and answer the questions that follow."
    annotation_type: "pure_display"

  # First annotation task
  - name: "sentiment"
    description: "What is the overall sentiment?"
    annotation_type: "radio"
    labels:
      - Positive
      - Negative
      - Neutral
```

### Divider Between Sections

```yaml
annotation_schemes:
  - name: "classification"
    description: "Classify the document type"
    annotation_type: "radio"
    labels:
      - News
      - Opinion
      - Analysis

  # Visual divider
  - name: "divider"
    description: "---\n\n**Quality Assessment**\n\nNow evaluate the quality of the content."
    annotation_type: "pure_display"

  - name: "quality"
    description: "Rate the writing quality"
    annotation_type: "likert"
    size: 5
```

### Conditional Instructions

```yaml
annotation_schemes:
  - name: "contains_pii"
    description: "Does this text contain personal information?"
    annotation_type: "radio"
    labels:
      - "Yes"
      - "No"

  - name: "pii_instructions"
    description: "**If you selected Yes above**, please identify all personal information in the next section."
    annotation_type: "pure_display"

  - name: "pii_types"
    description: "What types of PII are present?"
    annotation_type: "multiselect"
    labels:
      - Name
      - Email
      - Phone
      - Address
      - SSN
```

### Guidelines Reminder

```yaml
annotation_schemes:
  - name: "reminder"
    description: "**Remember:**\n- Focus on the main claim, not supporting details\n- Consider the author's intent\n- When in doubt, select 'Unclear'"
    annotation_type: "pure_display"

  - name: "stance"
    description: "What is the author's stance on the topic?"
    annotation_type: "radio"
    labels:
      - Support
      - Oppose
      - Neutral
      - Unclear
```

## Output Format

Pure display annotations are **not included** in the output since they don't collect any data.

## Use Cases

- **Section headers** - Organize complex annotation tasks
- **Instructions** - Provide context-specific guidance
- **Warnings** - Highlight important considerations
- **Dividers** - Visually separate different annotation sections
- **Examples** - Show example annotations inline
- **Guidelines** - Remind annotators of key criteria

## Best Practices

1. **Keep it concise** - Long blocks of text can slow down annotation
2. **Use formatting** - Markdown (bold, lists, headers) improves readability
3. **Strategic placement** - Put instructions immediately before relevant questions
4. **Don't overuse** - Too many display blocks clutters the interface