Grouping issue: DB refresh

[joeflack4]

Related Milestones

• DB refresh: core components

Main DB refresh

Issues

To do

These are ordered with most important on top and least on bottom.

DB Refresh backend functionality and frontend interface

• DB refresh: Updated objects (i.e. metadata) #398 @joeflack4
• Clear cache: When DB updates #396 (mostly @Sigfried
• DB refresh (& elsewhere): Objects tables updates (omopconceptset, omopconceptsetcontainer) #526 @joeflack4
• DB refresh: About page updates #498 @Sigfried @joeflack4
• DB refresh: misc #399 @joeflack4
• DB refresh: Status notifications #397 @joeflack4 @Sigfried
• DB refresh: Triggers #401 @joeflack4
• DB refresh: effective delay experiments #433 (mostly done; maybe test different ways / re-test)
• DB refresh: researcher, project #341 @joeflack4
• DB refresh: performance: Derived tables: Inserts > remakes #448 @Sigfried @joeflack4 low priority; minimal performance gain
• DB Refresh: Refresh button #694
  • DB refresh: Button click confirmation #481 @Sigfried?
  • DB Refresh: Refresh button - revert to GH action (bugfix) #695
• Grouping issue: resolve-fetch-failures-excess-items #754 @joeflack4
  • Bug: Fetch failures: HTTP 406 #518 @joeflack4
  • Bug: Fetch failures (excessive items): KeyError #499 @joeflack4

Unit testing

• Test: Long-running (DB refresh) #522 @joeflack4
• Test/DB Refresh: refresh & database integrity #484 (related) @joeflack4

Done

• DB refresh: Vocab and counts tables #447
  • DB Refresh: Bug: Voc/Counts: GH action - not running #519
• DB refresh: Increase rate? 1x/day->2hours? #408
• DB refresh: overall strategy #444
• DB Refresh: 0 members sync issue: TermHub v ConceptSetBrowser #402
• DB refresh: updating documentation #485
• DB refresh: Simultaneous requests #395
• DB refresh: button: Call backend directly #442
• Db refresh: Fix SyntaxError && error reraising #443
• DB refresh: Get all rows into the concept_set_members (and derivative) tables #451
• DB refresh: handle pagination where needed #437
• DB refresh: effective delay experiment 1 #432
• DB refresh: Status variables #400
• DB refresh: Via objects API #259
• DB refresh: GitHub actions: Bugs & major tasks #237
• DB refresh button: basic setup #357
• DB refresh button: Adding functionality #376
• Bug: fetch_failures_0_members() ignored drafts & other fixes and improvements #725
• GH action failures: Counts & fetch_failures_0_members #735

Counts / vocab refresh

• GH action failures: Counts & fetch_failures_0_members #735 @joeflack4
• Counts/Voc refresh: Lock on failure #753 @joeflack4

[joeflack4]

@Sigfried I identified several new follow-up issues we might want to do.
Also, wonder if we should just keep grouping issues closed. I'm not sure if it helps / hurts more to keep them open. Mostly they're good for searching / indexing related stuff, but I suppose we don't need them to be open for that either.

[Sigfried]

@joeflack4: not sure. As I mention in an issue I'm still writing, we've got a lot of db refresh issues and I'm not sure where to put stuff.

Question: Should we keep this code? It's not being used. Is it there because you're planning to wire it into stuff, or is it obsolete/irrelevant at this point?

[joeflack4]

We talked about this at the meeting, but just to be thorough here, that code will be used by #341.