Skip to content
This repository was archived by the owner on Jun 4, 2024. It is now read-only.
This repository was archived by the owner on Jun 4, 2024. It is now read-only.

Submit new mission #15

Description

@EricWehrly

Owned by an organization
This is really an incident
It will need a field for "created by" at some point
All objects, unless explicitly specified, should have a "created date" that is populated by the datastore.

Model: {
id: org-specific identifier (NOT NetEOC id), for paperwork
title
location (lat, long, elevation; can be POI or other already-defined datatype)
startDate (best format for search, can be reformatted at intake or extake)
endDate (best format for search, can be reformatted at intake or extake)
dutyLevel (always positive integer, will probably work as a byte)
staffNeeded (unsigned int)
staffMax (unsigned int)
attachments (file array),
}
Attachments can be one-to-many with a separate table, or a blob array column if you feel like it. As long as it's received and fetched sanely, I don't care.

Missions need to have one-to-one user relationships to determine if a user is in one (if any) of the following mission attendance states:
Eligible
Invited
Accepted
Attending / Deployed

All model items can have keys renamed to something more sane if desired

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions