Project Synopsis
The Wiki Ed Dashboard / Programs & Events Dashboard is a Ruby on Rails + Javascript application that helps people organize groups of newcomers to contribute to Wikipedia. This project aims to use ORES (Objective Revision Evaluation Service) to provide specific useful editing suggestions to newcomers about how they can improve existing Wikipedia articles or article drafts they are working on. This can give an idea of what kind of improvements are needed for the article and gives them a jumpstart in their contributions
Final Summary
- After the project, an Automatic feedback feature is successfully included in the Wiki-Ed dashboard that is shown in the MyArticles component that shows the articles edited by a particular user and also shows them in the Articles Edited Section for the suggestion to be reviewed by instructors.
- There is a feature for users to add their own suggestions on the edits in addition to the Automatic Feedback.
- Adding an easy way for users to give feedback on this feature.
- Even if the Automatic Suggestions couldn’t be made smarter as part of my project I hope the work done to document the ORES features would encourage such improvements.
- Making a spreadsheet of the ORES suggestions pointed to some blatant errors in ORES predictions due to redirects and the issue is notified in this task.
Next Steps
- I couldn’t contribute to making the Automatic Suggestions smarter as I lacked some experience with Wikipedia Editing and this is a major scope of improvement for the project.
- Adding the feature for custom user suggestions on the edits in the Article-Viewer component where it could be more relevant.
| Timeline | Task | Remarks | Work report | Status |
| Week 1 (Due May 18) | Community Bonding period | First Blog post | Done | |
| Week 2 (Due May 25) | Community Bonding period | Introduced myself to the community through mailing list. Joined Zulip. Discussed with mentors about participation during GSoC. Learning new technologies for the project. | Week 2 - Blog Post | Done |
| Week 3 (Due June 1) | Community Bonding period | Updated deliverables. Did some research on the dashboard and finalized the goals of the project. | Week 3 - Blog post | Done |
| Week 4 (Due June 8) | Design and add buttons in the MyArticles component that would display the feedback | The feedback buttons will be a way for users to say how each and every aspect of the suggestion was useful and would be designed in a more sophisticated manner in the future. | Blog post | Done |
| Week 5 (Due June 15) | Add feedback based on ORES features | The features are retrieved and processed in the rails backend to generate feedback. They are not stored in the backend as of now. They are retrieved in the frontend through Redux. The features based feedback should be improved. | Blog post | Done |
| Week 6 (Due June 22) | Add feedback based on ORES rating | The ORES predicted rating is retrieved from the ORES API and was displayed in the frontend | Blog post | Done |
| Week 7 (Due June 29) | Improve Feedback messages | The feedback messages are improved and design for displaying it improved | Blog post | Done |
| Week 8 (Due July 6) | Extend the feedback feature to Sandbox articles and add feedback button to Assigned Articles component. | Extended the feedback feature to sandbox articles. Improved the suggestions to give the users a hint on the Wikipedia Assessment Scale. Added a way to receive suggestions from the users within the modal. | Blog post | Done |
| Week 9 (Due July 13) | Improve the feedback for further testing. Ideation to improve automatic feedback. | An open Excel Sheet to get some resources and all hands on improving the automatic feedback | Blog post | Done |
| Week 10 & 11(Due July 27) | Add Custom Feedback Feature | Users can add a feedback to an article in addition to the existing automatic feedback | Blog post | Done |
| Week 12(Due August 3) | Improve the custom feedback feature | Added user reference to feedback. Added delete functionality. Finalized project deliverables with mentor | Done | |
| Week 13 (Due August 10) | Merging the Custom Feedback Feature | Switched the feedback flow to a design that does not confuse between automatic feedback and user feedback | Done | |
| August 10 to August 21 | Identify areas of improvement in ORES. Write documentation | Making a spreadsheet of the ORES suggestions pointed to some blatant errors in ORES predictions due to redirects and the issue is notified in this task | Done | |
| Final Week | Submit Code and Evaluations | Final Post | Done |