emergency-response
Here are 84 public repositories matching this topic...
-
Updated
Aug 31, 2019
-
Updated
Mar 20, 2022 - C#
-
Updated
Mar 30, 2017 - PHP
-
Updated
Dec 18, 2019
Deal with timezones
The first step to handle timezones would be to add the current timezone as a parameter, and replace all Europe/Paris values in the project.
-
Updated
Nov 15, 2021 - PHP
-
Updated
Jun 27, 2019 - Jupyter Notebook
-
Updated
Oct 1, 2019 - Python
-
Updated
Feb 11, 2022 - JavaScript
-
Updated
Mar 7, 2022 - JavaScript
-
Updated
Nov 22, 2017 - Python
-
Updated
Oct 30, 2021 - Batchfile
-
Updated
Feb 11, 2021 - JavaScript
-
Updated
Mar 11, 2022 - Vue
-
Updated
Jan 19, 2019 - HTML
Describe the bug
The file "/Bmore-Responsive/docker/README.md" erroneously contains content from another project (MPSM). This file needs to be cleaned up to be accurate for Bmore-Responsive.
-
Updated
Nov 28, 2020 - Java
-
Updated
Sep 12, 2016 - JavaScript
-
Updated
Jul 13, 2020
-
Updated
Mar 2, 2022 - TypeScript
-
Updated
Jan 3, 2021 - MATLAB
-
Updated
Jan 28, 2019 - Python
-
Updated
Jun 22, 2018
The code does not follow any architecture but introducing one would be helpful
-
Updated
Sep 15, 2019 - Java
-
Updated
Feb 22, 2017 - Python
-
Updated
Feb 4, 2022 - Python
-
Updated
Feb 13, 2022 - PHP
Improve this page
Add a description, image, and links to the emergency-response topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the emergency-response topic, visit your repo's landing page and select "manage topics."


When making a New Person, people are often entered as Prospect or Applicant. Rank is required in order to save, and currently we are using 'unknown' to meet requirements.
Accurate logic would not require a rank for 'prospect' or 'applicant'. A rank is only needed for people who have joined. This would also require a blank or null choice for rank.