Developer at Wikimedia Sverige (WMSE). Also known as Lokal_Profil when I'm not wearing my WMSE hat.
Note for the future. While the audio needs to be publicly accessible it could be possible to make the main tts server only speak to the wiki by having client requests go to the action api (of the MediaWiki extension) which in turn forwards these to he TTS service and handles the reply. If so the Security group settings are those in T161094#3125200.
Fri, Mar 24
An example PR with CI feedback: https://github.com/lokal-profil/COH-tools/pull/1
The patch looks good but I would like the issues around add_statement in se-bbr - Finalize processing code and T161114: Make the check for existing item more versatile be resolved before moving on with an upload.
Looks like the preview page is struggling to deal with unicode (in the qualifier). Can that be easily fixed? Mainly jsut ensuring that there isn't actual encoding issues which would be pushed to Wikidata.
@Sebastian_Berlin-WMSE Add the following to "To make audio files accessible:"
Thu, Mar 23
Following instruction at https://github.com/stts-se/wikispeech_mockup
- Install the Prerequisites but skip the remaining steps
- Skip Marytts & Lexicon startup steps
- Clone https://github.com/stts-se/wikispeech_mockup.git from Home
- Create tmp directory in wikispeech_mockup: mkdir tmp
- Add host=0.0.0.0 to app.run() in wikispeech.py (see: http://stackoverflow.com/questions/30554702/cant-connect-to-flask-web-service-connection-refused).
- Start wikispeech server: python3 wikispeech.py
@Sebastian_Berlin-WMSE @Alicia_Fagerving_WMSE Would you mind taking a look at the "Result" section above and give a shout about bits which are unclear/missing/unnecessary? Please add these as comments (typos/formatting you may of course edit directly). The plan is to, when ready, add this as a subpage to the DevGuidelines.
Wed, Mar 22
Is the review of this separate of the review of T160341?
How about also changing "itis" to "claim" or "value" for clarity.
I need to ensure my earlier tools specify a version of WikidataStuff so that they do not break with this change.
I think the following sketched solution should solve both issues while at the same time making it clearer in which order we check for matching items.
This will need to be split up into multiple parts:
- Notify on encountering tags
- Interact with encountered tags
- Interact with links (follow)
- Interact with footnotes (read footnote and return to current position)
This is not a blocker for the first demo since users are not expected to have their own accounts. It should however be mentioned in T161091: Documentation for demo wiki.
This will be solved by T159545
There is no point in doing this before T159988: Redirect makes the player skip first sentence it should however be mentioned in T161091: Documentation for demo wiki as something we know does not work yet but which will be implemented.
Low priority since the credentials will not be reused on any non-demo wiki and since initial password generation is pretty insecure anyway.
I've aimed that quarry ids are permanent even for non published queries. Possibly that is not true
Tue, Mar 21
Would be good.
Are the quarry links correct? Seem to go to other queries
Mental note to also update documentation with the new shortcuts.
Tue, Mar 14
WMIT will document the experiences and choices at d:WikiProject_Cultural_heritage/Reports/WLM_on_WD_(Italy)
For completion. Checked this on Firefox 52.0 on Ubuntu