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

• [ ] #398 @joeflack4
• [ ] #396 (mostly @Sigfried
• [ ] #526 @joeflack4
• [ ] #498 @Sigfried @joeflack4
• [ ] #399 @joeflack4
• [ ] #397 @joeflack4 @Sigfried
• [ ] #401 @joeflack4
• [ ] #433 (mostly done; maybe test different ways / re-test)
• [ ] #341 @joeflack4
• [ ] #448 @Sigfried @joeflack4 low priority; minimal performance gain
• [ ] #694
  • [ ] #481 @Sigfried?
  • [x] #695
• [ ] #754 @joeflack4
  • [ ] #518 @joeflack4
  • [ ] #499 @joeflack4

Unit testing

• [ ] #522 @joeflack4
• [ ] #484 (related) @joeflack4

Done

• [x] #447
  • [x] #519
• [x] #408
• [x] #444
• [x] #402
• [x] #485
• [x] #395
• [x] #442
• [x] #443
• [x] #451
• [x] #437
• [x] #432
• [x] #400
• [x] #259
• [x] #237
• [x] #357
• [x] #376
• [x] #725
• [x] #735

Counts / vocab refresh

• [x] #735 @joeflack4
• [ ] #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.