Backlog/Further work possibilities

[ClFeSc]

Please create a new issue for the feature when you want to discuss it more in detail/start implementing it. This issue should only list further improvements/features.

Copied from internal backlog document of BP2021HG1.

Should have

• verbose map layers (street names, etc.)
• Text fields on map (can also be a workaround for street names)
• adjust website-title and favicon
• time delay for entering, moving, unloading [C3]
  • loading and unloading times of vehicles and material is configurable [C8]
  • loading time to a vehicle based on the distance of the patient to the vehicle [C3]
• See which Clients are on your viewport (especially remote)
• increase popup visibility (maybe popper.js)
• Arrive now button for transfers Add Arrive now functionality for transfers #533
• visualize what happened in previous patient states [C17]
• add all hospital / all transfer points buttons to transferpoints [C15]
• lock objects [C13] Lock MapImages #332
• more default map images (vehicles, cone, absperrband)
• display treatment capacity of personnel, material Vizualize the treatment capacity for personnel and material #535
• increase dropdown size Standardize dropdown-menu heights #529
• show scrollbar on hospital selection menu and others Standardize dropdown-menu heights #529
• time input in minutes and seconds
• auto-generate external name for transferpoints
• patientoverview
• hospital statistics show from which viewport they were sent, (number when implemented)
• show complete information when clicking on patient in the hospital statistic Show more HospitalPatient information in HospitalPatientsTable #558
• Tutorial as a handbook/video
• sort elements in lists/dropdowns/etc.
• allow patient deactivation for patients whose state should not change?
• rotate non-walking patients in patient editor

Nice to have

• Feedback on entering a vehicle
• More options for mapImages
• notification for new rescue personnel in viewport
• Create custom vehicle templates (UI) [B5] UI to edit and create vehicle templates #588
• Elements in transfer need different times depending on their type (vehicle, personnel, (helicopter))
• Search for a real place on the map [B1]
• Alarm groups
  • advanced configurations for targets when alarming alarm groups [C5]
• Vehicle history (AlarmGroup 1, TransferPoint 1, TransferPoint 3, ?Hospital 1?)
• TransferPoints
  • disable/hide transfer points for participants [C11]
  • Directed transferPoint connections
  • limited number of vehicles on transferPoints
• Element placing
  • rotate vehicles [C4], viewports
• grouping of personnel [C1]
• Participent Viewports
  • allow participants to change their viewport by themselves, which takes time [C18]
  • trainer only viewports (relevant when changing the viewport by oneself as a participant) [C10]
• Blobs (from Milestone 3)
• view-only link
• generate patients with UI
• summarise viewport content on a high zoom level for trainers visually
• personnel-only transfer points
• enumerate patients on pretriage
• ticket system
• show scrollbar or some other indication if you can move in your viewport
• patients with special requirements (trapped patients)
• add PLZ and place to adress
• copy & paste function for alarm group creation
• copy transferpoints
• move transferpoints in groups (maybe other objects too?)
• being able to block vehicles that are just not ready to transport patients anymore
• Tutorial as a tour on the webpage
• transfer point naming: internal vs. external confusing

Wild Ideas

• Street-View-like view of the scenario
• no drag-and-drop of vehicles over blocking objects
• timestamps of interesting events in the analysis diagrams
• notebook which allows clients to make notes on certain decisions
• collision models for mapImages [C12]
• collision models for vehicles [C4]
• online library for exercises [C2]
• vehicles only on roads
• blocked areas only for vehicles
• improve helicopter logic
• send NA with patients in vehicle

Related to automation

• automatic actions based on conditions (set by participants during the exercise)
• automatic creation of "average" group of X patients?
• allow creation of sample solution for scenarios?

[Dassderdie]

• Implement a "capacity" model (in contrast to the current implementation based on the patients visibleStatus) to make the treatments more realistic. See here for the proposal Capacity model for patient treatment cost calculation #547

[Dassderdie]

• Elements (Patient, Vehicle, Personnel, ...) should get a type property with a value like patients, vehicles etc. This improves the code in multiple places (search for elementType or just type in frontend and shared) There is no easy way to differentiate between elements #530

[anonym-HPI]

Make it possible to treat blue patients, too.