Skip to content

Frequently Asked Questions

Which upload path should I use: SRW or templates?

See Two Upload Paths for the full decision guide. Short version: SRW for a one-off human-driven registration with no additional structured data; templates for anything you're automating end-to-end.

Can I reuse the same subjects across multiple studies?

Yes — but not through subjectHumans/subjectAnimals again. See Subject Sharing Across Studies for the exact mechanism (study_design_edit's arm_2_subject section) and why the obvious-looking approach doesn't work.

What order do I upload templates in?

See Upload Order for the master decision tree, and the per-assay pages under Workflows → Assay Upload Order for assay-specific sequencing and bundling rules.

My upload failed validation — where do I start?
  1. Pull the summary report via GET /data/upload/registration/{uploadTicketNumber}/reports/summary (see API Reference).
  2. Cross-reference the error message against Common Errors FAQ and the main Data Package Validator troubleshooting table.
  3. If the error references a rule type you don't recognize (e.g. check-value-not-in-entity), look it up in the Validation Rule Glossary.
Does a template's field description always match its enforced behavior?

Not necessarily — see the Subject Sharing Across Studies workflow for a concrete example where generic field-level prose ("conditionally required... when defining a new X rather than referencing one") didn't match that specific template's actual hard-coded rule. When in doubt, check the Validation Rule Glossary and consider that the template's own XML/validator behavior is the ultimate source of truth.

Is there a way to create a workspace programmatically?

Not currently found in the reviewed API surface — workspace provisioning goes through the Workspace Request Form / ImmPort Helpdesk rather than a self-service REST endpoint. See Workspace Setup.

What's the largest file size I can upload directly?

Use the S3 presigned-URL or multipart upload flow for large files (e.g. .fcs, sequencing reads) rather than the simple online/offline upload endpoints — see REST API Overview.