Wikidata:Requests for permissions/Bot/Github-wiki-bot
From Wikidata
Jump to navigation
Jump to search
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Approved--Ymblanter (talk) 20:44, 7 January 2017 (UTC)[reply]
Github-wiki-bot[edit]
Github-wiki-bot (talk • contribs • new items • new lexemes • SUL • Block log • User rights log • User rights • xtools)
Operator: Konstin (talk • contribs • logs)
Task: Import metadata from github into wikidata. This specifically means information about stable releases, the release dates and the project's homepage.
Code: https://github.com/konstin/github-wikidata-bot
This bot has been created as part of the wikidata workshop for the German open knowledge labs.
Function details:
- Import all stable releases and the release dates
- Update the project website
- All entries get a source link and a retrieved date alongside with the correct rank
- [Disabled] Normalize the github link
- [Disabled] Update the wikipedia software info box with the new information
--Konstin (talk) 22:20, 29 December 2016 (UTC)[reply]
- Please add P813 to the source-links! And set a maximum number of versions to add (like 100). Otherwise Strong support. -- MichaelSchoenitzer (talk) 00:33, 30 December 2016 (UTC)[reply]
- To avoid duplicate, your bot check for items that already exist? Have you an example of item created by bot? --ValterVB (talk) 09:14, 30 December 2016 (UTC)[reply]
- The bot does not create new Items. It just edits Items wich already have a link to github. -- MichaelSchoenitzer (talk) 13:23, 31 December 2016 (UTC)[reply]
- Additionally, all interaction with claims wrapped through "get or create" functions. -- Konstin (talk) 21:59, 1 January 2017 (UTC)[reply]
- I've added retrieved values to source links. They will not be added to already existing source though as pywikibot is not capable of properly doing that. Although I dislike the idea of allowing incomplete version list, I've also added a limit of 100 for the number of releases that will be added. -- Konstin (talk) 21:59, 1 January 2017 (UTC)[reply]
- I'm also unhappy with arbitrary limiting the version-history list – but I'm feared of what would happen if we would import all version-numbers of projects which release a new version every day or such (For example JOSM is now at version 11425) – the Wikidata-GUI doesn't support lazy-loading or similar and the design of the pages has wide margins making the pages really long quickly. One could skip projects with huge amount of versions in the first runs and do them when the Wikidata-Gui is improved. Alternative Idea: For some projects with big amount of versions one could think of only adding version ending with ".0" but wouldn't help if the version-numbers are counted as integers like with JOSM. Nether the less of these special-cases I'd like to see this bot running soon! -- MichaelSchoenitzer (talk) 15:23, 2 January 2017 (UTC)[reply]
- To avoid duplicate, your bot check for items that already exist? Have you an example of item created by bot? --ValterVB (talk) 09:14, 30 December 2016 (UTC)[reply]
- I will approve this bot tomorrow provided there have been no objections raised.--Ymblanter (talk) 18:56, 6 January 2017 (UTC)[reply]