Emergency.uiowa.edu epic

[briand44]

• hawk alert content type
  • title - will get populated from Rave - need ability to edit in case of a typo in Rave
  • complete
  • status - single valued - they want the ability to add new terms here. They only get output on the hawk alert node as text and don't get linked to. Rabbit hole. Want output higher up on hawk alert node rather than at bottom.
  • body - no summary needed - will get populated from Rave - need ability to edit in case of typo in Rave.
  • Situation Updates - Paragraph collection with date and details similar to ITS alert updates.
    • want to output the date first on the hawk alert node rather than last like it is currently.
    • want this to be a little easier to read
    • would like the date to default to now rather than empty
    • list these chronologically with most recent updates first similar to what we did with ITS
  • Don't need the notes field anymore
• Show active Hawk Alerts at top, stacked if multiple with most recent first
  • If no active Hawk Alerts, want to show the campus status Normal message with additional text as is currently
• Will want to show recent hawk alerts that are no longer active 3-5 on front page with link to all. They are checking on how many past hawk alerts they need to keep and how those should get added/imported
• job to check Rave every minute and create Hawk alert content from that feed. Do we want to revisit this to see about Rave pushing to us?
• Nice to have would be a way to relate a hawk alert to another hawk alert

Questions

We should ask about e.uiowa.edu and www.emergency.uiowa.edu. I'm a little confused on www. The domain exists on 702 but not seeing it covered in the 702 cert.

e.uiowa.edu is covered in the 702 cert and the domain exists on the 702 application. We have an entry in sites.php for this which doesn't seem like how we have been handling things in SiteNow v3. May make more sense as a vulture redirect if it is still needed.

$sites['emergency.prod.drupal.uiowa.edu'] = 'emergency.uiowa.edu';
$sites['emergency.uiowa.edu'] = 'emergency.uiowa.edu';
$sites['e.uiowa.edu'] = 'emergency.uiowa.edu';
$sites['www.emergency.uiowa.edu'] = 'emergency.uiowa.edu';

Tasks

Beta Give feedback

1. Hawk alert content type for emergency site #7501
   0 of 3
   emergency.uiowa.edu medium story +3
   
2. Rave integration #7502
   3 of 3
   emergency.uiowa.edu large story +3
   
3. Establish additional fields for Hawk Alerts #7503
   emergency.uiowa.edu medium story +3
   
4. Display active hawk alerts on emergency front page #7520
   0 of 1
   emergency.uiowa.edu medium story +3
   
5. recent hawk alerts and archive of all #7521
   emergency.uiowa.edu medium +2
   
6. www.emergency.uiowa.edu SSL
7. export of hawk alert content from D7 site #7578
   SiteNow v1 emergency.uiowa.edu small story +4
   
8. Turn off default Hawk Alert functionality on emergency.uiowa.edu #7586
   1 of 1
   Just do it SiteNow v3 emergency.uiowa.edu +3
   
9. recreate endpoints for signage, sitenow, etc to consume #7550
   4 of 5
   emergency.uiowa.edu medium story +3
   
10. Setup emergency endpoint in stage and communicate #7654
    6 of 6
    emergency.uiowa.edu small story +3
    
11. Update Signage/HC Signage to consume Hawk Alerts from new Emergency endpoint #7686
    emergency.uiowa.edu medium signage.uiowa.edu story +4
12. Update SiteNow v2/v3 so it can consume Hawk Alerts from new Emergency endpoint #7687
    SiteNow v2 SiteNow v3 emergency.uiowa.edu medium story +5
13. Update SiteNow v1 to consume Hawk Alerts from new Emergency endpoint #7688
    SiteNow v1 emergency.uiowa.edu medium story +4
14. Test Hawk Alert for emergency.stage.drupal.uiowa.edu #7818
    6 of 7
    emergency.uiowa.edu small +2
    
15. Communicate Emergency site launch date for folks updating integrations #7815
    blocked emergency.uiowa.edu needs grooming +3
16. e.uiowa.edu redirect to emergency.uiowa.edu #7582
    blocked emergency.uiowa.edu small story +4
17. Launch tasks for Emergency v3 site #7689
    0 of 5
    emergency.uiowa.edu needs more info +2

[joewhitsitt]

capturing some of my notes from the meeting:

• situation updates are not connected to rave so the date field could be an actual date field vs the string they currently have.
• they would appreciate an export of current data for redundancy purposes regardless of what legal says needs to be carried over to the new site.
• moderation should not be added or we need to make sure it doesn't interfere with the automated RAVE process or their manual update workflow.

Nice to have would be a way to relate a hawk alert to another hawk alert

This relationship could make it easier to sort/group alerts in the order they desire.

[pyrello]

title - will get populated from Rave - need ability to edit in case of a typo in Rave
...
body - no summary needed - will get populated from Rave - need ability to edit in case of typo in Rave.

Do these get synced regularly? Or is it a one-time thing? If it is a regular occurrence, are we worried about preserving edits they've made to the title?

[pyrello]

job to check Rave every minute and create Hawk alert content from that feed. Do we want to revisit this to see about Rave pushing to us?

I'm assuming we would need an endpoint with POST, which is kind of a big deal from a security standpoint. Something to keep us awake at night...

[briand44]

Do these get synced regularly? Or is it a one-time thing? If it is a regular occurrence, are we worried about preserving edits they've made to the title?

@pyrello my understanding is it is a one time thing. Updates are manually made to a Hawk Alert on the Emergency site and if any changes are made to Rave it would create a new Hawk Alert