Skip to content

Investigate multipart AJOK lisätiedot mapping for PDF generation #258

@asku1990

Description

@asku1990

Problem

Current 2023 AJOK PDF mapping ignores osa=b and osa=c rows for lisätieto koodit 25 and 27.

However, it is currently unclear whether:

  • only osa=a should be rendered,
  • values should be combined,
  • values should render separately,
  • or whether old AJOK logic intentionally ignored parts b/c.

KOIRATIETOKANTA payload examples contain:

  • P25A1a
  • P25A1b
  • P25A1c
  • P27A1a
  • P27A1b
  • P27A1c

Current implementation drops everything except a.

Goal

Investigate and document the correct behavior before changing canonical PDF mapping.

Investigation tasks

  • Inspect old Beagle v1 AJOK PDF generator behavior for:
    • koodi 25
    • koodi 27
  • Verify whether:
    • multipart values were combined,
    • rendered separately,
    • or partially ignored intentionally.
  • Compare against:
    • current 2023 AJOK form,
    • Kennelliitto/SAJ instructions if available,
    • KOIRATIETOKANTA payload structure.
  • Determine whether renderer layout can support:
    • combined values,
    • multiline values,
    • or separate coordinate fields.

Acceptance criteria

  • Correct intended behavior for 25 and 27 is documented.
  • Decision documented in issue comments or follow-up doc.
  • If implementation change is required:
    • create follow-up implementation task.
  • No schema changes in this task.
  • No speculative implementation in this task.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions