Challenge Overview
This is a followup challenge for a previous one: http://www.topcoder.com/challenge-details/30066653/?type=develop&noncache=true.
And the purpose of this challenge is updating the MS Teams bot to cover the following extra functionalities:
1. A leaderboard that displays everyone's total points and "status" ranked highest to lowest
3. Admin functionality
- the data is not persisted correctly (always empty), and change the file-name to be more meaningful, which is now a number: http://take.ms/s0ode. And please change the logic to save the file when the data is changed.
- make it work locally: http://take.ms/gt7Ak
And make the following changes:
- Each of the hashtags should have a point value associated. So instead of everything being 1 point, I'd like to be able to specify that #CultureBlog is 10 and #CultureVideo is 20 (as an example).
- If talk to the chat-bot directly, it now gives error after providing URL. We want to change this to respond "please use a channel to log points" whenever user tries to talk to the chat-bot directly.
- The point totals appear to be restarting at 0 each day - they should aggregate ove time indefinitely (unless updated by an admin)
- The spark logo does not appear in the Teams mobile app but appears to be working otherwise
- When the bot responds asking for a URL Please change the text to say "Please provide your proof - this could include a referral name, URL of the content or short description of the activity". It now accepts both text and URL, so please remove the current URL validation as well.
Please also make sure the functionalities from previous challenge are not broken. (Reviewer are required to test the functionalities required in previous challenge as well).
- Updated Source Code
- Detailed deployment guide and verification guide
- Working MS Azure Deployment for easy testing
And the purpose of this challenge is updating the MS Teams bot to cover the following extra functionalities:
1. A leaderboard that displays everyone's total points and "status" ranked highest to lowest
- Ability for user to mention @Spark the bot with relevant tag to view the leaderboard at any point
- scheduled weekly leaderboard posted
- Status will appear next to users names on group scoreboard
- WillLyon (Navigator) - 400
- HeatherBeserra (Scout) - 80
3. Admin functionality
- Create following REST APIs to allow admin:
- Search (support filtering by user, hashtag, team, and support paging as well)
- add point records
- remove point records
- update point records
- export the data as CSV file to download
- Please define postman file for verification purpose
- Create a simple authentication method to protect the REST API (e.g. using hard-coded username/password
- the data is not persisted correctly (always empty), and change the file-name to be more meaningful, which is now a number: http://take.ms/s0ode. And please change the logic to save the file when the data is changed.
- make it work locally: http://take.ms/gt7Ak
And make the following changes:
- Each of the hashtags should have a point value associated. So instead of everything being 1 point, I'd like to be able to specify that #CultureBlog is 10 and #CultureVideo is 20 (as an example).
- If talk to the chat-bot directly, it now gives error after providing URL. We want to change this to respond "please use a channel to log points" whenever user tries to talk to the chat-bot directly.
- The point totals appear to be restarting at 0 each day - they should aggregate ove time indefinitely (unless updated by an admin)
- The spark logo does not appear in the Teams mobile app but appears to be working otherwise
- When the bot responds asking for a URL Please change the text to say "Please provide your proof - this could include a referral name, URL of the content or short description of the activity". It now accepts both text and URL, so please remove the current URL validation as well.
Please also make sure the functionalities from previous challenge are not broken. (Reviewer are required to test the functionalities required in previous challenge as well).
Final Submission Guidelines
Submission Deliverable- Updated Source Code
- Detailed deployment guide and verification guide
- Working MS Azure Deployment for easy testing