Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • What to expose?  Only mark "fresh"?  Overdue?  By how much? Delinquent?  
  • How to represent in the interface?
  • Sorting and/or filtering by freshness?
  • Add a "Make Fresh" button for data contributors?  If we do this, we may want to implement as an api call so that contributors could click a link in the overdue email to have the same effect.
  • Related to this is this old Jira about making revision_last_updated visible in the UI  
    Jira Legacy
    serverJIRA (humanitarian.atlassian.net)
    serverIdefab48d4-6578-3042-917a-8174481cd056
    keyHDX-4894
    .

See Data Freshness in the UI

5. Data Partnerships Team: Define freshness workflow for handling delinquent datasets and ones with broken urls

...

DP have a draft of their process here https://docs.google.com/document/d/1b77sksL5UiDF1jrMAU9bxN8BTVrM5XXgj1gOS6ZgN-E/edit and from their feedback, the first task is to create Tasks (issues) in Zoho. The assignee is obtained by reading the DP weekly duty roster, here https://docs.google.com/document/d/1uFe6uWS9iMSHsiFyvlYYmP1b_C2xc8F0wTowm2LuajE/edit to see who is on duty.

Plan:

  • Examine Zoho api and try to make a Task programmatically
  • Read assignee from DP duty roster
  • Create freshness database query and generate Task
  • Create Docker image and deploy

6. Mike: Implement emailer for broken urls 

...