# விக்கிப்பீடியா:தானியங்கி வேண்டுகோள்கள்/தற்போதைய

## தற்போதைய வேண்டுகோள்கள்

### Bot/தானியங்கி அனுமதி - CampWiz Bot

#### Function details

This bot is a part of the tool CampWiz which assists organizers of various edit-a-thon to host, manage campaign, evaluate submissions, publish results (As of now, about 40 campaigns were hosted and 4500+ articles were submitted through this tool). One of its sibling tool helps organizers to generate a list of articles which are not present on their wiki based on topic (As of now, 233636+articles in 150+ lists were harvested). One of our main targets was to reduce the security issue and liability along with privacy issue. As such, this tool uses a single bot account to interact with mediawiki which eliminates the need of storing the user's access token on the server. As of now, the bot would perform the following tasks. *In order to prevent spamming, all the edits on user talk pages would be done by batch hourly, rather than immediately.*
1. **trackingTemplate**: This bot would add a template (configured by the campaign organizers) on the talk page of an article if it does not already exist, whenever that article is submitted into a campaign.
1. **notifyEvaluation**: This bot would add a message on submitter's talk page if any of his submissions get any evaluation by the judge (including any note that judge ).
1. **notifyNewSubmission** (opt-in only): This bot would add a message containing new submission that were added on the talk page of the user who volunterily consented to have updates.
1. 
**notifyStatistics** (opt-in only): This bot would periodically give statistics update about the campaign the user opted-in.
 (For future reference)  
To demonstrate the functionalities, please look at the edits on mrwiki. All the templates that the bot uses should be localized too. These are:  
##### Clarifications
- I would like to point a couple of clarifications before bureaucrats:
- It appears that you may not be familiar with Tamil, and I'm concerned about how you plan to proceed. Please note that immature machine translations could lead to deletion of content and potential user bans.
- Many edit-a-thons utilize additional tools for campaign management, submission evaluation, etc. I'm curious to understand how your bot differs from existing tools and whether there is a risk of duplication or contradiction.
- Your PrefixIndex pages does not give any sense and you shouldn't have created before the approval. --AntanO (பேச்சு) 06:00, 6 ஏப்பிரல் 2024 (UTC)
:: Thank you very much for asking.
::# Yes, I am not familiar with Tamil language, I know Bangla (my mother tongue) and English with some verbal Hindi/Urdu. But, as far as I am concerned, the bot would not add any content to any article (it would not edit on main namespace). It would only work with <code>User Talk</code> and <code>Talk</code> namespace. So, if the templates that I mentioned (using the <code>Special:PrefixIndex</code>) are translated (and localized) correctly, there would be no case of machine translation. Because, the bot would just copy paste those translated templates (and, the templates would be translated by human).
::# Your second concern is answered in the following segments:
::## **Why CampWiz Different?**: CampWiz is a edit-a-thon management tool for submission and evaluation, like other existing tools. But this tool has the ability to determine what is the contribution (**added**) of the submitter in the article, not **total** statistics. For example, if any article has 399 bytes and *User A* adds 1 byte, other tools would be happy that the article is now 400 bytes and the article is eligible for submission. But, CampWiz would consider only the 1 byte *User A* added and there, need to add more 399 bytes to be considered eligible. There are other features as well which would make the reply lengthy.
::## **Risk of Duplication**: This bot is the only bot that would handle all the maintenance task of the CampWiz tool. Whenever we need any bot account (e.g for speed, anonymity etc), we would be using this bot account. Therefore, the bot would never contradict with itself. In case of duplication, for testing purpose, there would be two or three duplication (same user would receive the same updates multiple times). Because, for testing out, I would set the bot in a <code>reset</code> mode to check its consistency. After that testing, no duplication would be done.
::# As far as I know, any bot is allowed to edit its user namespace and its operator's user namespace even without being approved. The templates are located within the bots user namespace, therefore, as far as I am concerned, I did not violate any Bot Policy. But if your local bot policy or convention differs, please let it be an honest mistake.
::For some context, Please look at some conversation with Neechalkaran here. Nokib Sarkar (பேச்சு) 08:37, 6 ஏப்பிரல் 2024 (UTC)  
- Requesting for some edit trials Nokib Sarkar (பேச்சு) 09:15, 9 ஏப்பிரல் 2024 (UTC)
- pinging for attention. Nokib Sarkar (பேச்சு) 04:01, 14 ஏப்பிரல் 2024 (UTC)
- :Pinging active admins @Sridhar G, @Arularasan. G for the permission to test trial Nokib Sarkar (பேச்சு) 15:36, 17 ஏப்பிரல் 2024 (UTC)
- ::I'm yet to look at the full context, but please confirm the namespaces this bot would operate in. And let us get the templates translated to Tamil before operating this bot. -- சுந்தர் <sup>\பேச்சு</sup> 01:01, 30 செப்டெம்பர் 2024 (UTC)