We don't need the bulk upload to include tons of columns that are irrelevant to the bulk edits. We are going to let users download a template to use on a per-listing basis when they are preparing to bulk upload. The columns should be:
- Application Id - Match key (do not edit)
- Applicant First Name - Context
- Applicant Last Name - Context
- Application Submission Date - Context
- Lottery Position Number - Editable
- Application Status - Editable (enum keys? strings?)
- Application Decline Reason - Editable (enum keys? strings?)
- Application Decline Reason Additional Details - Editable
- Waitlist Position (Accessible Unit) - Editable
- Waitlist Position (Conventional Unit) - Editable
The editable indication matters only during actual processing, but is listed here for clarity on the intent of each column.
We'll need a new endpoint GET /applications/bulk-update/template?listingId=
Questions:
- Should we filter out at this stage if an application has been deleted?
- Should we filter out at this stage duplicates?
AC
- Download returns CSV with exactly 11 columns in the defined order
- One row per application on the listing (per deleted/duplicate rules above)
- All columns reflect current DB values
- Unauthorized users receive 403
We don't need the bulk upload to include tons of columns that are irrelevant to the bulk edits. We are going to let users download a template to use on a per-listing basis when they are preparing to bulk upload. The columns should be:
The editable indication matters only during actual processing, but is listed here for clarity on the intent of each column.
We'll need a new endpoint
GET /applications/bulk-update/template?listingId=Questions:
AC