Spike: validate mixed Study/Series send in single association to Oxidicom

[rudolphpienaar]

Spike: validate mixed Study/Series send in single association to Oxidicom

Status

Discussion/test spike only. No implementation commitment in this ticket.

Priority

Low (discussion)

Context / Background

We need an empirical interoperability check for sender behavior when a single DICOM association carries a directory containing a mix of different StudyInstanceUID and SeriesInstanceUID values.

This test should inform current discussion:

• https://github.com/FNNDSC/engineering_man/discussions/46
• Discussion: Oxidicom series registration across multiple associations oxidicom#10

Detailed Scope

1. Prepare a mixed input dataset (multiple studies and series in one directory).
2. Send to Oxidicom using single-association mode.
3. Send the same dataset using per-file association mode.
4. Capture outcome for each run:

• files attempted
• C-STORE accepted/rejected counts
• registered count in Oxidicom/ChRIS path
• error/rejection reason strings

5. Post a concise comparison matrix in an issue comment.

Result Matrix (to fill in)

Mode	Files Sent	C-STORE Accepted	C-STORE Rejected	Registered	Notes
Single association
Per-file association

Acceptance Criteria

• Both send modes executed on the same mixed dataset.
• Comparison matrix completed with quantitative results.
• Conclusion documented on whether behavior indicates:
  • sender-side optimization needed,
  • Oxidicom behavior change needed,
  • or both.

Management Note

Owner: @Sandip117

Boundary:

• In scope: test execution and result reporting.
• Out of scope: implementing sender or Oxidicom code changes in this ticket.