For future reference, you can see here that the results are coming from Zotero:
Fri, Aug 9
I asked to pull this into "Investigating" because I was very confused by the description. I think it was missing a "not", please check if that's right. Also, the issue is not reproducible at the given URL anymore, because Citoid was apparently enabled on the wiki. Is there another example?
Thu, Aug 8
I think maybe for the future.
This is a big issue for wikibase integration too; at present wikidata has a constraint that the isbn be hyphenated, but in reality some records lack the hyphenation despite the constraint. Thoughts? We need to pick one and stick with it.
So the short answer is - yes, that'd be ideal. But the ISBN situation is kind of a disaster though. The hyphenation position depends on knowing the length of other elements, like registration group, and these change so they need to be *constantly updated in order to correctly hyphenate them.*
Mon, Aug 5
Sat, Aug 3
Fri, Aug 2
With the new patch I'm now getting
I've just quickly fixed the config; it was relatively simple as hi wiki uses all the same templates as en wiki so I just copied some stuff over. Should all be working now!
You've also found a bug, we shouldn't be offering the "convert" option if citoid isn't correctly enabled. Thanks for the reporting! I've separated that off into T229654.
I've temporarily disabled it here, as it is incorrectly configured: https://hi.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A5%80%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A4%BF:Citoid-template-type-map.json&action=history
Thu, Aug 1
I tried to install wikibasecirrussearch with vagrant and it seems to work for me, after manually enabling $wgWBCSUseCirrus = true; (that part is not automatic yet). Maybe some other configurations are interfering? Are there any local configs and where do you configure $wgWBCSUseCirrus = true;? Did you check that you have latest master checkout of all modules (CirrusSearch, Wikibase, WikibaseCirrusSearch)?
Fri, Jul 26
Jul 24 2019
Jul 22 2019
Jul 21 2019
What would be involved in implementing your suggestion of automatically rerouting people to citation template? How often does this happen @mvolvz, the copy tweak makes sense in the mean time.
Jul 19 2019
Jul 18 2019
No longer getting this, so closing.
Jul 16 2019
Jul 15 2019
Jul 13 2019
Jul 12 2019
Jul 11 2019
Is there a replacement target, or should it just be removed outright?
Jul 10 2019
I've reindexed testwikidata last week, the patch should already be there.
Probably same problem as: T226088
Jul 8 2019
Which is to say, my response there on that thread was to the first comment, but not to the later report of the all of pubmed being down, as these are two separate issues- I should have read the whole thread instead of just the first message! Thanks for tagging this @Aklapper so it reached my attention again, definitely not good.
Jul 7 2019
Jul 3 2019
We're going to try to deploy this first on test.wikidata, can this be reindexed as well? Or do they both get re-indexed at the same time?
Jul 1 2019
Jun 27 2019
I'm not sure whether to resolve or decline this as Research wasn't involved here :).
Jun 26 2019
Jun 20 2019
No worries; I wasn't aware the train was broken and wondered if the
reindexing had to be triggered manually or something, thanks for the update!
Jun 19 2019
Jun 11 2019
Jun 10 2019
Jun 6 2019
T224239 was for mobileapps and was originally titled: All mobileapps CI tests requiring external HTTP requests are throwing 504s which seems to indicate they had some test to exercise it and that it failed on patch proposal.
Can we investigate why the test failed on post merge but NOT when the patch has been proposed? I find that concerning. On https://gerrit.wikimedia.org/r/#/c/mediawiki/services/citoid/+/513975/ we had:
Zuul pipe Status Pipeline view Legacy view gate-and-submit SUCCESS service-pipeline-test #1890 https://integration.wikimedia.org/ci/job/service-pipeline-test/1890/ postmerge FAILURE service-pipeline-test-and-publish #209 https://integration.wikimedia.org/ci/job/service-pipeline-test-and-publish/209/
I have flagged both builds to be kept forever by Jenkins so we can investigate.
Jun 5 2019
Also I should point out that using an indexed search is *much* better performance wise!
Jun 3 2019
This has been "undeclined" and is resolved in T224004 - before deploying I was wondering if anyone knew of any adjustments made (.i.e. in bots) to strip out the leading PMC that returning it without the leading PMC would break? Otherwise I'll deploy it (relatively) shortly. I imagine such bots know what to do with the "correct" format anyway for user entered data.