wikieducationfoundation/impact-visualizer

impact-visualizer's Issues

Error in Vite build during capistrano deployment

I attempted to deploy to production, but I'm getting an unfamiliar error:

rake stdout: Building with Vite ⚡️
Internal Error: impact-visualizer@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile
    at V0.getCandidates (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:435:5145)
    at kf.getCandidates (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:391:1264)
    at /home/deploy/.yarn/releases/yarn-3.6.3.cjs:439:8033
    at df (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:390:11070)
    at ge (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:439:8013)
    at async Promise.allSettled (index 0)
    at async io (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:390:10398)
    at async /home/deploy/.yarn/releases/yarn-3.6.3.cjs:439:8545
    at async ti.startProgressPromise (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:390:47579)
    at async je.resolveEverything (/home/deploy/.yarn/releases/yarn-3.6.3.cjs:439:6573)

@mattfordham any ideas?

"Total Revisions vs Revisions Created Discrepancy

When a topic has a timeframe

Clearer step-wise UI workflow for setting up a new topic

For the Management Actions component, for initial setup of a new topic, the UI should clearly direct the user through each of the necessary steps of adding articles, adding users, and generating the data. At least for a topic that hasn't yet gone through all three steps, I think it should only show one of these at a time, at the top of the Management Actions, so that it's very clear what they should do next to move forward.

I also think we ought to automatically import users and articles at the time of CSV upload, combing upload and import into a single action.

The current UI is okay for after timepoint generation has been kicked off.

JS error on Topic page during timepoint generation

After the initiation of timepoint generation initiated by a topic owner, at some point the page threw a JS error:

I think we saw this same thing happen during a demo you were doing, @mattfordham.

Subsequently, refreshing the page worked and the timepoint data appears to have been generated properly, so I'm guessing this is just a UI error caused by an unexpected data environment.

"Total Revisions" vs "Revisions Created" Discrepancy

When a topic has a timeframe that goes back to the beginning of Wikipedia, "Total Revisions" and "Revisions Created" should match. The cause of the discrepancy is likely due to different sources of data being used for each count, but so far has not been confirmed.

Articles that do not exist (and have no pageid, first_revision_id, etc) cause error during timepoint generation

In many cases, we'll be looking at a bag of articles where some of the titles do not (yet) exist as articles at the time we analyze them. This should be handled smoothly.