Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IndividualStatisticsPresenter and user profile page rely on Revisions table #5995

Open
ragesoss opened this issue Oct 11, 2024 · 3 comments
Open
Labels

Comments

@ragesoss
Copy link
Member

We are deprecating the Revisions table and have removed old revisions from the production databases. However, the user profile pages — particularly, the feature for showing 'contributions as a student' — still relies on data from this table.

We need to either update the way this works so that it does not rely on the Revisions table (which may mean displaying a more limited amount of stats) or just remove this feature entirely.

@ragesoss ragesoss added the bug label Oct 11, 2024
@osujipius
Copy link
Contributor

I will work on this

@EmmanuelEmp
Copy link
Contributor

@ragesoss I would also like to work on this. After looking through the IndividualStatisticsPresenter query logic responsible for extracting the data, I was thinking if it was okay for the statistics section of the dashboard to now focus on articles created by a student rather than those edited (i.e. revisions).

@omChauhanDev
Copy link
Contributor

omChauhanDev commented Jan 18, 2025

@ragesoss Sir, for removing revisions table dependency there were two approaches:

Strategy 1: Create New Contribution Tracking

  • Create a focused StudentContribution model for essential metrics only.
  • Track:
    • Characters
    • References
    • Article creation
    • Views
  • Update statistics presenter to use the new model.
  • Migrate critical historical data.

Strategy 2: Remove Feature

  • Remove the StudentStats component.
  • Remove IndividualStatisticsPresenter.
  • Clean up UI/routes.

Conclusion

  • Strategy 1 if contribution tracking matters for program assessment.
  • Strategy 2 if the feature isn't critical for core functionality.

Kindly share your thoughts on which approach would be best to follow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants