User talk:Dalba/Archive 1

Welcome to Meta!

Hello, Dalba/Archive 1. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!

• Trijnstel_talk 20:43, 12 June 2012 (UTC)

Hi Trijnstel, and thanks for all your helps and efforts for the project. Best regards :) -- Dalba^(talk) 25 Khordad 1391/ 04:12, 14 June 2012 (UTC)

Translation notification: FDC portal/Proposals/CentralNotice2012

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page FDC portal/Proposals/CentralNotice2012 is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is بالا. The deadline for translating this page is 2012-10-15.

This banner will invite logged-in editors on all projects to participate in the current public review phase about funding requests by 12 organizations, regarding more than 10 million US dollars of donation money. (Questions about the translation notification system can be asked at [1], and you can manage your subscription at [2].)

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 08:07, 14 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/AdrianneW Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/AdrianneW Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-10-31.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 17:10, 23 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Landing Page and Banner messages

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Landing Page and Banner messages is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is بالا. The deadline for translating this page is 2012-10-26.

Update: New facts banners ___URGENT___

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 07:59, 24 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Poongothai Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Poongothai Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-10-31.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 14:52, 25 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Ravan Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Ravan Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-11-03.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 15:26, 29 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 22:47, 31 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 22:48, 31 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 04:48, 1 November 2012 (UTC)

Translation notification: Wikimedia Highlights, September 2012

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Wikimedia Highlights, September 2012 is available for translation. You can translate it here:

• translate to فارسی

Please consider helping non-English-language Wikimedia communities to stay updated on the most important Wikimedia Foundation activities, MediaWiki development work and other international Wikimedia news from September. You are receiving this message because you signed up to the translation notification system. Questions about this system can be asked at [3], and you can manage your subscription at [4].

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 11:34, 1 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Srikeit&Noopur Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Srikeit&Noopur Appeal is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is بالا. The deadline for translating this page is 2012-11-14.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 11:55, 9 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Landing Page and Banner messages

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Landing Page and Banner messages is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is بالا. The deadline for translating this page is 2012-11-21.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 16:54, 14 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Thank you letter

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Thank you letter is available for translation. You can translate it here:

• translate to فارسی

The priority of this page is بالا. The deadline for translating this page is 2012-11-21.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 14:41, 15 November 2012 (UTC)

2016 Community Wishlist Survey

Hi,

You’re getting this message because you participated in the 2015 Community Wishlist Survey and we want to make sure you don't miss it this year – or at least can make the conscious choice to ignore if it you want to. The 2015 survey decided what the Community Tech team should work on during 2016. It was also the focus of Wikimedia hackathons and work by other developers. You can see the status of wishes from the 2015 wishlist at 2015 Community Wishlist Survey/Results.

The 2016 Community Wishlist Survey is now open for wishes. You can create proposals until November 20. You will be able to vote on which wishes you think are best or most important between November 28 and December 12. /Johan (WMF) (talk) via MediaWiki message delivery (talk) 11:17, 14 November 2016 (UTC)

Yadkard translation?

Hi there. Is there a way to translate Yadkard to work for other wikis? While we have the Citoid now on Polish Wikipedia, I prefer to work in sfn-style refs anyway - and your splendid tool works with them. Sadly, there's no easy way to convert English WP's sfn to Polish odn template, let alone convert all those cite book, cite journal and whatnot to the single Template:Cytuj we use at pl.wiki (it's great, it formats itself basing on the fields you use). So, is there a way to add Polish as an option in Yadkard? Halibutt (talk) 20:18, 20 July 2017 (UTC)

Hi Halibutt! Thanks for your interest in Yadkard. Unfortunately, as it currently stands there is no easy way to add new languages. It's not totally impossible though, for example there is also a localized version of Yadkard for Persian Wikipedia running at http://tools.wmflabs.org/yadfa/ . The problem is that each new language will require localizing a few Python/HTML/CSS modules, which is a technical and time-consuming work. I need to simplify the code to ease the process of i18n and add instructions on how to add new languages.

Another issue is maintaining separate web-services on tools.wmflabs.org which seems to be inefficient (both in terms of resources used and maintenance).

To address this issue I may need to create a single web-service which will allow users to localize the output by choosing their preferred language/project via a simple drop-down menu. It requires rewriting and changing the structure of some parts of the source code.

Alas, I probably will not be able to investigate these ideas in a near future due to lack of spare time, but I do have them in mind.

Dalba 06:30, 21 July 2017 (UTC)

Thanks for the info, I'll stick to using it for en.wp for now then :) Halibutt (talk) 09:49, 21 July 2017 (UTC)

JSTOR account redistribution (The Wikipedia Library)

Hi - according to our records you received a free account for JSTOR through The Wikipedia Library. Because we’ve used up all of our allocated accounts, and it’s been some time since they were distributed, we want to redistribute any accounts that aren’t being used to users on our waitlist.

If you’re still using, or plan to use, your JSTOR access, no problem! Simply head over to the Library Card platform, log in, and request a renewal of your account. You should be able to do this from your user page, or the JSTOR signup page. If you can’t find the renewal button, or have any other issues or questions about this, please feel free to leave a message on my talk page. We’ll begin redistributing inactive accounts in September; if you request renewal after then we will only be able to reactivate your account if we have spots remaining. Thanks, MediaWiki message delivery (talk) 13:32, 20 August 2018 (UTC)

Citer

does not work for any web-page on this news-domain, which is rapidly becoming a major source in Indian ecosystem. Citoid does not work, either. Also, please ask folks to report bugs over here rather than your Wikitech t/p. Wikitech is not under CentralAuth and we need to create a separate account to access it; even anonymous editing is disallowed. The lesser hoops to submit feedback, the more will be recieved. Regards, Winged Blades of Godric (talk) 15:30, 12 March 2019 (UTC)

@Winged Blades of Godric. I've updated citer. It should now be able to process ThePrint URLs. Also updated the talk page link. Thanks for the feedback. ‍Dalba 11:23, 15 March 2019 (UTC)

Many thanks for your prompt response. Winged Blades of Godric (talk) 05:45, 22 March 2019 (UTC)

Citer problem 2019-05-16 12:33pm PDT

Hi, currently dropping in a URL, https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708 & seeing this in response:

{{sfn | ''{{title}}''}}

* {{cite web | website={{title}} | url={{websiteUrl}} | ref={{sfnref | {{title}}}} | access-date=2019-05-16}}

and:

<ref name="{{title}}">{{cite web | website={{title}} | url={{websiteUrl}}}} | access-date=2019-05-16}}</ref>

Yours, Peaceray (talk) 19:33, 16 May 2019 (UTC)

Seeing the problem in Edge, Chrome, & IE. Don't have access to Firefox on my current computer. Peaceray (talk) 19:37, 16 May 2019 (UTC)

Hi, Peaceray. Unfortunately I don't think I can fix this one. Citer uses the meta tags on a webpage, if available, to gather the citation info. Looking at the source code of that webpage I can see the following:

    <meta property="og:title" ng-attr-content="{{windowTitle}}" />
    <meta property="og:site_name" ng-attr-content="{{title}}" />
    <meta property="og:description" ng-attr-content="{{pageDescription}}" />
    <meta property="og:type" content="website" />
    <meta property="og:url" ng-attr-content="{{websiteUrl}}" />

Even if I make Citer somehow detect the inappropriateness of the gathered data, there is currently no simple way for it to find the correct ones since that page requires a JavaScript-enabled browser to load completely, but Citer does not process the JavaScript portion of pages right now (for performance reasons, and also, it's a complicated process).

Dalba 00:35, 17 May 2019 (UTC)

Ah, yes. OK, you shouldn't muck with things to handle a truly exceptional outlier. Peaceray (talk) 21:09, 17 May 2019 (UTC)

Citer bugs

Hi, thanks for maintaining the citer tool, it is very useful for making good citations quickly. I've encountered a two bugs that I hope you might take a look at. First, some non-functional DOIs (particularly with the IEEE journals):

• 10.1109/TIM.1985.4315297
• 10.1109/TIM.1976.6312276
• 10.1524/teme.1979.514524.jg.59

These DOI do seem to work on the DOI wikipedia reference generator, so maybe this is fixable? Second issue is something I've only seen with the APS journals, which work but sometimes are mysteriously missing the page number:

• 10.1103/PhysRevB.71.045110
• 10.1103%2FPhysRevLett.102.017002

The DOI reference generator also fails to work on these ones, so maybe APS just has bad metadata on their website. Let me know what you think. Forbes72 (talk) 21:35, 1 June 2019 (UTC)

Hi, Forbes72! Thanks for reporting this. I fixed the issue for the first three DOIs. It was a bug in Citer, expecting the `volume` value to be numeral-only.

Regarding the missing page numbers, Citer is using http://api.crossref.org/ . For the last two DOIs crossref does not provide any page numbers, but Citer always adds a `|page=` to the generated journal template in hope of making it easier for the end user to add the page parameter manually.

Dalba 06:18, 2 June 2019 (UTC)

That makes sense. Thanks for improving the tool! Forbes72 (talk) 19:17, 2 June 2019 (UTC)

More citer bugs

Mostly citer has been pretty reliable. However, I thought I'd let you know of a few more DOIs that citer returns only an error. The same DOIs work on DOI Wikipedia Reference Generator, so I think we can conclude that these are citer bugs and not crossref problems.

• 10.1007/JHEP10(2017)157
• 10.1088/0004-637X/705/1/978
• 10.1126/science.1169101

Maybe these are not too difficult to troubleshoot? Sorry I don't have the programming knowledge to be more specific here. Forbes72 (talk) 03:08, 17 August 2019 (UTC)

@Forbes72:, I just fixed and updated citer. Thanks for reporting the issue. Dalba 05:58, 17 August 2019 (UTC)

Looks great! Thanks. Forbes72 (talk) 18:16, 17 August 2019 (UTC)

doi 10.1093/ww/9780199540884.013.U245351 updating only cite

it is not creating cite web or cite journal or other. it is just creating cite. Leela52452 (talk) 10:41, 30 March 2020 (UTC)

The CrossRef server describes this DOI as a "reference-entry". I'm not sure what kind of citation template is appropriate for this type. I checked Citoid's result and it creates a general citation, too. Dalba 00:09, 3 April 2020 (UTC)

citer

Thanks for the tool. It simplifies my life. It would be even more useful if I could easily use it for other Wikipedias than the English one. Maybe one day you could make it output templates for other wikis, have a project/language switch in the UI, ..?--Cartoffel (talk) 16:17, 5 September 2020 (UTC)

I'm glad to hear that it's been useful to you. Your suggestion totally makes sense, thanks, but unfortunately I'm very busy these days with several other projects. Implementing it requires some major refactoring in code . . . can't make any promises, but I'll keep it mind. Dalba 04:24, 6 September 2020 (UTC)

Citer query

I too want to thank you for creating such a fabulous time-saving tool. Just one thing, which may be down to the site rather than the tool, I've noticed that it never picks up the author on the newer style of ABC News articles, for example this one. I usually add the authors manually afterwards, and overwrite with "website =ABC News |publisher =Australian Broadcasting Corporation", no biggie, but thought I'd mention it just in case there's a possible programming solution. Laterthanyouthink (talk) 14:01, 7 September 2020 (UTC)

Thanks for the feedback. I've updated author detection algorithm of Citer. It should work now. Regarding the publisher, in short, the site does not introduce itself like that and I don't want to rely on domain/url-specific settings... Dalba 16:24, 25 September 2020 (UTC)

Hi Dalba, sorry for the late response but I didn't get notified and have only just spotted your response now, when I came looking for another reason... I did notice that the ABC citations had improved, so thanks very much for that, mostly 100% now, which is great. (I mostly only add the publisher if it seems necessary to avoid confusion with the American ABC.) Another thing I've noticed on and off (I don't think it happens all the time, but I don't always check), which may be something to do with time zones(?), is that the date sometimes shows the previous day's date, for example with this Guardian article, the date comes out as 14 June. Not a big worry, but just passing on FYI in case you want to tinker some more. Laterthanyouthink (talk) 00:55, 25 November 2020 (UTC)

Hi Laterthanyouthink. Me too, I can hardly find time to visit the wiki these days :) Sometimes sites provide contradicting information. For example the article mentions "Thu 14 Jun 2018 19.00 BST" right under the author name and there is also a <meta property="article:published_time" content="2018-06-14T18:00:07.000Z"/> tag inside the source code of the page. "14 June" does not seem wrong to me here, even though that's one day earlier than the date in the URL itself. Dalba 13:36, 8 January 2021 (UTC)

p.s. I forgot to add that I'm very impressed with its citing of scientific journal articles - does a great job in seconds, compared with much longer time needed for manual construction! Laterthanyouthink (talk) 00:57, 25 November 2020 (UTC)

Thank you! :) Dalba 13:36, 8 January 2021 (UTC)

Another minor issue

Hi again. I don't know whether it's just a problem with this source, but Citer doesn't seem to pick up the authors from InDaily, such as this one. Not serious, but thought I'd let you know FWIW, in case there is a simple fix. Laterthanyouthink (talk) 11:04, 22 December 2020 (UTC)

Hi again! Done I've tuned the algorithm a little bit. It should be working now. I just hope it won't cause too many false positives in other cases. Dalba 13:39, 8 January 2021 (UTC)

Thanks very much, Dalba. I'll keep an eye on it, but hopefully won't be pestering you with any further issues! Laterthanyouthink (talk) 01:14, 9 January 2021 (UTC)

Citer in other languages

Citation templates in wp:it are slightly different from those of wp:en. Is there a solution to use the tool in wp:other languages? TX!--Tytire (talk) 19:06, 5 June 2021 (UTC)

Hi, Tytire! Unfortunately Citer does not currently support other languages. Dalba 09:47, 6 June 2021 (UTC)

dead-url -> url status

Hi, thanks for the great tool, I love how it expands archive.org URLs (any chance for archive.is?); I just wanted to alert you that 'dead-url=yes' parameter has changed to 'url-status=dead'. Quuux (talk) 07:19, 19 September 2019 (UTC)

Hi Quuux, I've update the parameter name. Thanks for bringing my attention to it. Regarding http://archive.is/, it should be possible, but I'm busy these days and I don't know when I'll be able to take a close look. Dalba 13:30, 19 September 2019 (UTC)

NCBI

https://www.ncbi.nlm.nih.gov/books/NBK53329/

And I got it all the time in the past few days that "HTTP error:

One or more of the web resources required to create this citation are not accessible at this moment." --It's gonna be awesome (talk) 08:24, 28 June 2019 (UTC)

It seems that www.ncbi.nlm.nih.gov is not accessible from Toolforge:

$ hostname
tools-sgebastion-08

$ nslookup www.ncbi.nlm.nih.gov
;; Got SERVFAIL reply from 208.80.154.143, trying next server
Server:         208.80.154.24
Address:        208.80.154.24#53

** server can't find www.ncbi.nlm.nih.gov: SERVFAIL

The same command works fine on my PC. My guess is that the issue resides in the Toolforge's DNS or is a configuration problem on www.ncbi.nlm.nih.gov. In either case I don't think there is much that I can do to resolve it.

P.S: Also tried Citoid. It fails with "We couldn't make a citation for you" error.

Dalba 09:22, 28 June 2019 (UTC)

@Dalba: I tried Citoid and it did fail with "We couldn't make a citation for you" error. --It's gonna be awesome (talk) 14:12, 30 June 2019 (UTC)

Just checked this and works now. Dalba 08:19, 21 April 2022 (UTC)

Citer bug

huffington post links like this one https://www.huffpost.com/entry/france-bans-spanking-kids-with-new-law_n_5873ccc1e4b02b5f858a39ff return a generic title with no authors etc. eg ref name="HuffPost is now a part of Verizon Media" cite web | title=HuffPost is now a part of Verizon Media | website=HuffPost is now a part of Verizon Media | url=https://www.huffpost.com/entry/france-bans-spanking-kids-with-new-law_n_5873ccc1e4b02b5f858a39ff | access-date=Feb 2, 2020 . I don't know if it's fixable on your end or the websites fault. Hydromania (talk) 05:17, 2 February 2020 (UTC)

Hi Hydromania, unfortunately I don't think I can fix this in a general way. The website requires Citer to accept a data agreement, but obviously Citer is not smart enough to do that. What Citer actually receives is a page with the following text:

Your data, your experience

HuffPost is part of Verizon Media. Click 'I agree' to allow Verizon Media and our partners to use cookies and similar technologies to access your device and use your data (including location) to understand your interests, and provide and measure personalised ads. We will also provide you with personalised ads on partner products. Learn more about how we use your data in our Privacy Centre. Once you confirm your privacy choices here, you can make changes at any time by visiting your Privacy Dashboard.

Click 'Learn More' to learn and customise how Verizon Media and our partners collect and use data.

[I agree] [Learn more]

Dalba 10:29, 3 February 2020 (UTC)

enwiki ending need for |ref=harv for Module:Citation/CS1

Hi, Dalba. FYI, I just saw at wikipedia:en:User talk:Citation bot#remove ref=harv that |ref=harv will be generated by default from wikipedia:en:Module:Citation/CS1. Peaceray (talk) 18:04, 18 April 2020 (UTC)

Hi. Thanks for letting me know. I've updated citer accordingly. Dalba 08:35, 28 April 2020 (UTC)

Many thanks for Citer

What a brilliant tool you have given us! I must have send you a friendly thought a thousand times, and now I'm here to say: thank you!

Citer used to be able to make citations directly from archived URLs in the Wayback machine, including filling in all those pesky fields that go with them in the citation template. That feature seems to have been lost at some point the last year. It would be wonderful if it is possible to get it back. Once again, thank you very much. Best regards, Sam Sailor 12:09, 10 June 2021 (UTC)

Hi, Sam! Thank you! That means a lot to me.

Could you provide sample URLs that Citer fails at them? I just tested [5] and it seems to be working. Dalba 03:44, 12 June 2021 (UTC)

Clicking the bookmarklet on http://web.archive.org/web/20210612025330/https://www.nytimes.com/2021/06/11/technology/apple-google-leak-investigation-data-requests.html takes me to http://web.archive.org/web/20210612025330/https://tools.wmflabs.org/citer/citer.fcgi?user_input=http%3A%2F%2Fweb.archive.org%2Fweb%2F20210612025330%2Fhttps%3A%2F%2Fwww.nytimes.com%2F2021%2F06%2F11%2Ftechnology%2Fapple-google-leak-investigation-data-requests.html&dateformat=%B+%d,+%Y

I then tried to copy-paste http://web.archive.org/web/20210612025330/https://www.nytimes.com/2021/06/11/technology/apple-google-leak-investigation-data-requests.html into https://citer.toolforge.org/ and that works perfectly, forgive me for not trying that to begin with.

So, something is wrong on my end somehow. What could it be?

My bookmarklet should be correct: javascript:void(window.open('https://tools.wmflabs.org/citer/citer.fcgi?user_input='+encodeURIComponent(location.href)+'&dateformat=%25B+%25d%2C+%25Y')) Thanks again, Sam Sailor 05:30, 12 June 2021 (UTC)

Sam, you're totally right! The bookmarklet does not work correctly on archive.org. The reason, I think, is that archive.org messes with the internal open function of the web page, so that every URL that one tries to open will be redirected to archive.org's equivalent of it. I searched for workarounds, but none of them worked. I guess we'll have to use Citer directly in this case :(, at least until a workaround is found, which I'm not sure exists/is worth creating a much more complicated bookmarklet just for one site. Dalba 03:07, 13 June 2021 (UTC)

What you say sounds reasonable, Dalba. Mam'noon! Sam Sailor 04:28, 13 June 2021 (UTC)

who.int

@Dalba: Citer fails for the https version of this URL. It works for the non-https version. (Similar behavior for other URLs at who.int)

• https://www.who.int/publications/i/item/background-document-on-the-mrna-1273-vaccine-(moderna)-against-covid-19

--Whywhenwhohow (talk) 06:30, 24 January 2022 (UTC)

There was a bug here. I think it is resolved now. Thanks for reporting the issue. Dalba 16:07, 17 February 2022 (UTC)

Date lag

Hi Dalba - me again. I thought that I had raised this once before, but I don't see it here. It's about the date quite often showing the date before publication rather than the date shown on the web page, and I wondered if it's something to do with the date lag in the eastern hemisphere. I use Australian sources quite a lot, and I've noticed it particularly with ABC News pages, but also with InDaily. Could this be something to do with the date stamp of the page being in UTC instead of being converted to the local time zone (or one of them - I assume that ABC would use EST)? Just a thought. 114.30.100.149 11:13, 19 February 2022 (UTC)

Hi. Sorry for my late responses. Could you provide some links that have this issue? My initial guess is that the date is correct, but may differ a little from what actually appears on the page. Sometime websites provide different metadata for their articles than the ones actually shown to end users. You may check the source code of such webpages to see if there is such metadata by searching for the wrong date. Most browsers show the the source code of a webpage using `Ctrl+U` keyboard shortcut. Dalba 04:59, 23 February 2022 (UTC)

Hi, sorry, a late response from me too, as I didn't get notification of the update and don't often log in to Wikimedia, but just noticed something else today. Thanks for yours. A short while ago, I was using the citer tool to create a citation for this URL: https://www.morningtonisland.com.au/arts, which worked fine but I noticed the access-date was 27 Feb, whereas it is 28 Feb where I live (Adelaide, South Australia). However, having just tried it again now, it now returns 28 Feb! I will attempt to look at the source code of pages as you suggest, and also report back to you with a specific example next time I notice the other date issue. (Sorry, I see the problem - I was not logged in before. Also, should change my Wikimedia name to be the same as my Wikipedia one...) Picadder (talk) 00:15, 28 February 2022 (UTC)

Coincidentally, I have had occasion to try Ctrl/U for a different reason, in dispute with a recalcitrant seller, and I wanted to check the date that these t&c were uploaded, so tried ctrl/U on it, but cannot find a specific date (at least, not by looking for "2022"). Can you assist in showing me how to find the date on this one, please? https://ameliasaustralia.com/pages/terms-of-use Picadder (talk) 05:36, 28 February 2022 (UTC)

Unfortunately I cannot find a date either. It's almost impossible to know the exact date if the server does not provide it (or if you don't trust the information the server provides). For popular webpages one might be able to deduce an estimate by looking at the date of the cached versions of the webpage in services like Wayback Machine, but I'm afraid that might not help in this case. Dalba 03:56, 1 March 2022 (UTC)

Okay, no worries, thanks for trying. Picadder (talk) 10:37, 1 March 2022 (UTC)

That's true. Citer does not know where you live, so it fills the access-date using the toolforge's webserver date which I believe is UTC. I might be able to add a feature to inspect user's timezone somehow, but I probably won't due to privacy reasons. Dalba 04:07, 1 March 2022 (UTC)

Ah, I see. I'm sure it doesn't matter that much. Is the page date issue related to discrepancies between when the page publishes according to UTC and the local date that it actually publishes on the article? I don't suppose it really matters either, just one of those niggling things that I spot occasionally! Thanks for following up, anyway. The tool is really a great timesaver so not going to worry about this. Oh, one other minor thing that I have noticed, this one consistently, is that it always lower-cases "the" in The Guardian - is that because they publish it that way? Picadder (talk) 10:37, 1 March 2022 (UTC)

Just FYI, I just came across an example: https://www.abc.net.au/news/2022-02-27/turtle-hatchlings-monitored-on-avoid-island/100847916 - apparently posted on the 27th (which is also part of the url), but citer says 26th. Picadder (talk) 10:45, 2 March 2022 (UTC)

This is interesting. If you disable the JavaScript of your browser the article shows "Posted Sat 26 Feb 2022", but with JavaScript enabled, it changes to "Posted Sun 27 Feb 2022". Anyway, finding the date line is hard and error-prone for computer, since there is no standard way of expressing it. Meta tags on the other hand are defined in a more standard way, therefore citer tries to use meta tags if it finds one. In this case it finds the following meta tag inside the source code of the page:

 <meta data-react-helmet="true" property="article:published_time" content="2022-02-26T20:47:00+00:00"/>

Dalba 04:33, 3 March 2022 (UTC)

"the Guardian" is another case of meta tags taking priority:

<meta property="og:site_name" content="the Guardian"/>

Dalba 04:39, 3 March 2022 (UTC)

Ah, I see. Interesting! And that's cool - I learnt a new thing (how to disable javascript in Firefox). Thanks for the explanation. Picadder (talk) 03:09, 5 March 2022 (UTC)

sanofi.com

Citer removes hyphen characters from this URL. It also places the URL in the website field.

• https://www.sanofi.com/en/media-room/press-releases/2022/2022-02-04-23-00-00-2379517

--Whywhenwhohow (talk) 06:52, 7 February 2022 (UTC)

If you look at the html source code of the page you'll see that sanofi.com is misusing meta tags:

<meta content="https://www.sanofi.com/media-room/press-releases/2022/2022-02-04 23-00-00 2379517"  property="og:url" />
<meta content="https://www.sanofi.com/en/media-room/press-releases/2022/2022-02-04-23-00-00-2379517"  property="og:site_name" />

I'm not going to implement a fix for this; you may want to contact the website's admin. Dalba 09:10, 17 February 2022 (UTC)

cen.acs.org

Citer fails for this URL

• https://cen.acs.org/pharmaceuticals/drug-discovery/How-Pfizer-scientists-transformed-an-old-drug-lead-into-a-COVID-19-antiviral/100/i3

--Whywhenwhohow (talk) 06:45, 24 January 2022 (UTC)

cen.acs.org uses JavaScript and cookies to prevent bots from crawling their website. Without the cookies the server response looks like this:

$ curl https://cen.acs.org/pharmaceuticals/drug-discovery/How-Pfizer-scientists-transformed-an-old-drug-lead-into-a-COVID-19-antiviral/100/i3
<html style="height:100%"><head><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><meta name="format-detection" content="telephone=no"><meta name="viewport" content="initial-scale=1.0"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><script type="text/javascript" src="/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3"></script></head><body style="margin:0px;height:100%"><iframe id="main-iframe" src="/_Incapsula_Resource?SWUDNSAI=31&xinfo=5-37758187-0%200NNN%20RT%281645103975751%2018%29%20q%280%20-1%20-1%20-1%29%20r%280%20-1%29%20B12%284%2c315%2c0%29%20U5&incident_id=484000650050968331-150946707254022213&edet=12&cinfo=04000000&rpinfo=0&cts=u%2b8REw3kg%2bLkfCFPxJ%2bUR3Cdrv2w6xRBfp9ClVu%2bT7oyVKLetFaIzqR6O1XTNYKJ&mth=GET" frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula incident ID: 484000650050968331-150946707254022213</iframe></body></html>

I think Citer won't be able to handle this one either, sorry :( Dalba 13:28, 17 February 2022 (UTC)

Citer doesn't recognize url

For some reason, it's only the AKC urls - https://www.akc.org/dog-breeds/american-bulldog/ I've tried clearing cache, reloading, using Chrome & Safari. Nada. Atsme^📞📧 14:16, 20 April 2022 (UTC)

The size of the web page was unusually large. Citer refuses to process large documents to avoid any malicious requests and/or wasting processing time. Anyway, the previous size limit seemed to be too small, I've increased it to 10MB. That fixed the problem for this case. The size limit may still be too restrictive for some webpages. I may reconsider the size in the future. Thanks for reporting the issue. Dalba 06:03, 21 April 2022 (UTC)

They have recently added video, which may contribute to the larger size? More resources are adding various types of media so it's probably time to increase the size limit for those of us who are highly dependent on your wonderful tool. Atsme^📞📧 12:37, 21 April 2022 (UTC)

Citer date bug

The citer template has an edge case bug for dates on the first day of the month. It uses the previous month in the date. For example, for the URL https://www.bbc.com/news/world-us-canada-59843627, with the date format 1 January 2020, it generates output containing the date 1 December 2021 instead of 1 January 2022. (It happens on the first of any month -- the year change is unrelated). --Whywhenwhohow (talk) 02:47, 1 January 2022 (UTC)

Each click of a date format at the top of the page changes the month to an earlier month.

• Click January 1, 2020 gets November 1, 2021
• Click Jan 1, 2020 gets Oct 1, 2021
• Click 1 January 2020 gets 1 September 2021
• Click 1 Jan 2020 gets 1 Aug 2021

--Whywhenwhohow (talk) 07:28, 1 January 2022 (UTC)

@Whywhenwhohow, you're right. There was a timezone conversion bug. I think I've fixed it with the latest update. Thanks for reporting the issue. Dalba 11:29, 1 January 2022 (UTC)

It looks like there is still a bug. Using the 2020-01-01 format for the URL above displays December 31 instead of January 1. Then clicking any other date format changes the displayed date to December 30. --Whywhenwhohow (talk) 19:01, 1 January 2022 (UTC)

@Whywhenwhohow, I cannot reproduce the issue anymore. Try clearing your browser's cache or if possible on another computer. Dalba 15:39, 2 January 2022 (UTC)

┌─────────────────────────────────┘
It exhibits the same behavior elsewhere. It decrements the date and the access-date.

Start with date format "2020-01-01" for the BBC URL and see date=2022-01-01

Click date format "1 January 2020" (or any other date format) and see date=31 December 2021

Click date format "2020-01-01" and see date=2021-12-31

Click date format "1 January 2020" (or any other date format) and see date=30 December 2021

Click date format "2020-01-01" and see date=2021-12-30

Click date format "1 January 2020" (or any other date format) and see date=29 December 2021

References

I see what you mean, Whywhenwhohow, but unfortunately I can not reproduce. On my machine the converted dates all keep pointing to January 1st.

Which browser are you using? Have you tried latest version of Firefox? (I'm not suggesting that you should change your browser, just want to figure out if it is browser-related.)

Also, if you don't mind sharing, what timezone is your computer set on? Is it Greenwich Mean Time/Pacific Standard Time/etc? Dalba 04:43, 3 January 2022 (UTC)

It happens in Chrome and Firefox using EST. Can you try it on a mobile device and see how it behaves there? --Whywhenwhohow (talk) 07:57, 3 January 2022 (UTC)

@Whywhenwhohow, thanks. I was able to reproduce and debug the issue in EST timezone and came up with a fix. I've updated citer. Dalba 08:39, 7 January 2022 (UTC)

Thank you. Whywhenwhohow (talk) 19:39, 8 January 2022 (UTC)

Inexplicably setting language to Chinese

I have found since yesterday that Citer seems to be interpreting all Australian ABC articles as lang=zh, e.g. https://www.abc.net.au/news/2022-05-15/malcolm-abbott-domestic-violence-prevention-fails/101059440 - is this something to do with the ABC website, and/or is this something you can fix, please? Laterthanyouthink (talk) 02:53, 17 May 2022 (UTC)

It was something I could fix. Thank you for letting me know. Dalba 09:02, 4 June 2022 (UTC)

Thank you! Laterthanyouthink (talk) 13:20, 4 June 2022 (UTC)

A suggestion

Hi, I've used Citer for years now, a huge help. I didn't realize, however, that it could handle Google Books URLs - never guessed that that's what you meant in "URL/DOI/ISBN". This didn't matter while there was a toolforge tool for Google Books but it's gone. Maybe provide some sort of hint in the tool itself? Chiswick Chap (talk) 16:02, 15 November 2021 (UTC)

Hi, Chiswick Chap! Thanks for your suggestion. Actually there is a hint in the footer message mentioning Google Books. I don't want to make the button's text too long, not sure how I can improve this. Dalba 11:15, 1 January 2022 (UTC)

Failed URLs.

Thank you for creating Citer! Here are a few URLs that fail without giving a helpful message.

• https://www.lamag.com/citythinkblog/who-are-the-phimbys/
• https://www.wsj.com/articles/well-protect-americas-suburbs-11597608133

Additionally, this is an English-language article which comes up with language = de in the generated cite.

• https://www.cnbc.com/2018/06/28/families-earning-117000-qualify-as-low-income-in-san-francisco.html

Additionally, Substack citations have the website as "Substack", when, for example, it should be "The Discourse Lounge" for this link.

• https://darrellowens.substack.com/p/vacant-nuance-in-the-vacant-housing

Grendelkhan (talk) 02:06, 2 January 2022 (UTC)

Hi Grendelkhan,

• lamag: fixed
• wsj: worked for me, but it took several tries. Not sure what is happening here. The WSJ server is responding with 403 (Forbidden) status code when called from Toolforge server, but works on my PC. Could be a temporary issue or maybe they have blocked Toolforge's IP address. I may have to look into this later.
• cnbc: I just improved the language detection algorithm.
• darrellowens.substack.com: It's complicated, but in short, citer can't find the proper site name by looking into usual places in this case, then, as a last resort, it tries to guess the name using the URL (domain name) and the home page title. Of-course it has failed here, but works on some other websites. I may change or remove this algorithm in the future if more cases like this show up. Dalba 15:25, 2 January 2022 (UTC)

Date for archive page

Citer appears to use the date of the archive for the date in the citation instead of the date of the archived page. For example, for the URL https://web.archive.org/web/20121101092633/https://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm307549.htm it uses November 1, 2012, instead of June 8, 2012. For that URL is uses website fda.gov instead of U.S. Food and Drug Administration. --Whywhenwhohow (talk) 22:31, 3 January 2022 (UTC)

References

FixedDalba 13:15, 27 August 2022 (UTC)

Citation spacing and parameters

Current version: | issn= | pmid= |pmc= | doi= | pages=

I would like it changed to remove the spaces inside the citations and move a few of the parameters like this:

Proposed version: |pages|issn=|doi=|pmc=|pmid=

The named reference only needs to include the last names and year of publication without additional spaces inside the named rereference. QuackGuru (talk) 03:07, 27 April 2022 (UTC)

I disagree with the above, as spaces are useful for allowing the citations to wrap on the screen, making reading and editing easier. When there are no spaces, it causes the citations to occupy way more lines than necessary. I hate seeing citations with no spaces! Laterthanyouthink (talk) 02:53, 17 May 2022 (UTC)

When there are no spaces, it causes the citations to occupy less space. When there are spaces it makes it more difficult to edit because the citations look like sentences. I think editors should be given an option. The proposed version above occupies less space. QuackGuru (talk) 15:37, 17 May 2022 (UTC)

Hi! Thanks for the feedback and sorry for my the late response. Although I see that some users might prefer other kinds spacing, but I don't think I'll be adding a setting for this feature in the app because it is a rarely requested feature (actually, this is the first time someone has asked for it) and the added complication is perhaps not worth. Dalba 09:18, 4 June 2022 (UTC)

Incorrect {{citer}} code generated for URL

The URL https://www.utas.edu.au/library/companion_to_tasmanian_history/B/Black%20Convicts.htm returns this reference:

<ref name="University of Tasmania University of Tasmania">{{cite web | title=Black Convicts | website=University of Tasmania | University of Tasmania | url=https://www.utas.edu.au/library/companion_to_tasmanian_history/B/Black%20Convicts.htm | access-date=2022-06-13}}</ref>

which has two stray references to "University of Tasmania" as well as probably one other bug.

Thanks for citer!

DanShearer (talk) 21:05, 13 June 2022 (UTC)

Fixed Thanks! Dalba 09:22, 26 August 2022 (UTC)

Incorrect date generated for URL

I enter this URL into citer, and it offers mostly correct code, but generates the date | date=1917-06-30. Access date is correct. Turtlens (talk) 19:26, 21 August 2022 (UTC)

https://www.cs.rutgers.edu/people/professors/details/emeritus/endre-szemeredi Turtlens (talk) 19:27, 21 August 2022 (UTC)

I can restrict citer's date detection algorithm for more accuracy, but that will also make it leave the date field empty on many other sites which have dates correctly detected. It's a compromise between false positives and false negatives. My experience is that current situation is acceptable, but I may reconsider if get more reports like this. Thanks. Dalba 09:36, 26 August 2022 (UTC)

The url which failed was

https://abelprize.no/abel-prize-laureates/2012

Result generated

"2012: Endre Szemerédi". The Abel Prize. 1917-06-30. Retrieved 2022-08-27. 

Sorry for my incorrect post. 99.192.36.54 05:33, 27 August 2022 (UTC)

Fixed Dalba 13:03, 27 August 2022 (UTC)

Citer not working?

trying to generate a citation for this link https://pubmed.ncbi.nlm.nih.gov/32687126/ Citer doesn't seem to be working at this time. 2601:5CE:4380:B530:0:0:0:4B7E 01:00, 27 August 2022 (UTC)

Fixed Dalba 13:02, 27 August 2022 (UTC)

Thank you. 2601:5CE:4380:B530:0:0:0:4B7E 18:32, 27 August 2022 (UTC)

I'm trying to generate a citation for this link: https://almodarresi.com/en/books/pdf/TheLawsofIslam.pdf?noamp=available but the citer doesn't seem to be working at this time.-2401:4900:2711:B1D8:479D:3693:F220:4BFD 09:48, 20 September 2022 (UTC)

The server is responding with 404 error code for that URL (not found):

$ curl -I https://almodarresi.com/en/books/pdf/TheLawsofIslam.pdf?noamp=availabe
HTTP/2 404
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
link: <https://almodarresi.com/wp-json/>; rel="https://api.w.org/"
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==
x-endurance-cache-level: 2
x-nginx-cache: WordPress
content-type: text/html; charset=UTF-8
date: Sun, 16 Oct 2022 14:43:25 GMT
server: Apache

Dalba 14:46, 16 October 2022 (UTC)

https failure

@Dalba: Citer fails for the https version of this URL. It works for the non-https version.

• https://web.archive.org/web/20121220083825/https://www.ornl.gov/sci/techresources/Human_Genome/medicine/genetherapy.shtml

--Whywhenwhohow (talk) 03:04, 3 January 2022 (UTC)

Fixed. Dalba 04:29, 3 January 2022 (UTC)

┌─────────────────────────────────┘
@Dalba: Thank you for fixing. Citer appears to be having trouble with other archive.org URLs that use https.

• https://web.archive.org/web/20131203040308/https://ethics.missouri.edu/Gene-Therapy.aspx
• https://web.archive.org/web/20121105033602/https://www.uniqure.com/news/167/182/uniQure-s-Glybera-First-Gene-Therapy-Approved-by-European-Commission.html
• https://web.archive.org/web/20140429053945/https://www.thephysiciansclinic.co.uk/first-gene-therapy-trial-for-heart-failure-begins-in-uk/
• https://web.archive.org/web/20150710014412/https://ir.celladon.com/releasedetail.cfm?releaseid=839474

It displays the message

HTTP error:

One or more of the web resources required to create this citation are not accessible at this moment.

Is it a timing issue where Citer doesn't wait long enough for the results? --Whywhenwhohow (talk) 05:12, 3 January 2022 (UTC)

@Whywhenwhohow I just tested and citer was a able to generate a citation for all of the URLs you just mentioned, which makes me wonder, are you using https://citer.toolforge.org/ or some other URL to access citer? Dalba 09:33, 4 January 2022 (UTC)

I am using https://citer.toolforge.org/ but the results for URLs from archive.org frequently fail. Sometimes it displays that "HTTP error" message immediately and other times it generates a citation. I just tried a different archive.org URL and it failed immediately. I tried

• https://web.archive.org/web/20210201143845/https://www.tga.gov.au/apm-summary/comirnaty

--Whywhenwhohow (talk) 23:24, 4 January 2022 (UTC)

Maybe there has been some temporary server issue on archive.org's side. Currently works fine me. Dalba 09:22, 2 April 2023 (UTC)

CDC press

Citer provides the wrong title, date, and language for this CDC press release.

• https://www.cdc.gov/media/releases/2022/s0105-Booster-Shot.html

--Whywhenwhohow (talk) 05:40, 6 January 2022 (UTC)

References

@Whywhenwhohow Unfortunately CDC is misusing meta tags on their website. The following were found on the mentioned webpage:

<meta property="og:title" content="CDC Newsroom">
<meta property="article:published_time" content="2016-01-01">

Citer is using these tags to generate citation. The language issue seems to have been fixed. Dalba 10:02, 2 April 2023 (UTC)

harv errors

Hi, thanks for creating this tool: I find it immensely useful. However, the shortened refs it has generated for me in the last couple of hours have been giving harv errors; which I find baffling, as I cannot see any errors in the syntax. See for instance Almeida et al, in this revision [6]. Thanks in advance for any assistance. Vanamonde93 (talk) 05:06, 16 October 2022 (UTC)

PS: I would appreciate a ping as and when you can get to this; as I'm primarily active on en.wiki, I may miss a response otherwise. Vanamonde93 (talk) 05:07, 16 October 2022 (UTC)

A followup; I believe the issue in some cases is fixed by manually adding the year to the shortened citation; it appears that while citer is able to extract the date, it isn't incorporating the year into the shortened (sfn) template. If this is true, perhaps it's an easy fix? Vanamonde93 (talk) 17:23, 16 October 2022 (UTC)

Fixed Dalba 02:50, 17 October 2022 (UTC)

web resources not available - AWM

Entering the URL https://awm-math.org/awards/awm-birman-research-prize/ generates an error:

HTTP error: One or more of the web resources required to create this citation are not accessible at this moment.

I can certainly browse to the URL. The shorter URL https://awm-math.org/ has the same issue. Turtlens (talk) 16:09, 29 November 2022 (UTC)

Fixed Thanks for reporting the issue. The website uses old SSL methods that are disallowed by recent versions of openssl library and that was causing communication issues. I've changed citer's configuration to allow them. Dalba 15:01, 30 November 2022 (UTC)

Thanks. I'll try and report the issue to AWM so they can update their SSL library usage. — The preceding unsigned comment was added by Turtlens (talk)

In case they need more technical details, this is the error being received on a Debian buster machine:

$ curl https://awm-math.org/
curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

Dalba 14:16, 1 December 2022 (UTC)

Error??

Citer is great. I use it a lot. However, I think this is an error - the book is not Italian.

• Petringa, Maria (2006). Brazzà, a life for Africa (in Italian). Bloomington, IN: AuthorHouse. ISBN 1-4259-1198-6. OCLC 74651678. 

76.14.122.5 19:36, 13 December 2022 (UTC)

Thank you! You're right. The detected language is incorrect. Citer currently uses the book title to guess the language of the book and in this case it has been wrong. Maybe I should disable this feature for English version since most book sources used in English Wikipedia are in English and it won't matter much if the language parameter is not specified for the few others. I'll keep this in mind and will probably change it in the future if I see more requests like this. ‍Dalba 06:06, 26 January 2023 (UTC)

Citer for etwiki

Hey! Citer is working amazingly well. Thank you for putting in the effort to create it!

I was wondering if there would be an option to add wiki specific output format in the near future? Currently Citer is outputting English Wikipedia template syntax (Cite web, Cite journal etc with English parameters). In Estonian Wikipedia for example all the most used citation templates have been translated and have fields mapped to Citoid fields. Basically all English Wikipedia citation template parameters have corresponding parameters in Estonian. Or would this be too complicated to add? Of course we have Citoid configured and working in Visual Editor, but I assume some users would prefer to keep using the wikitext editor and Citer tool for automatic citations. Thanks, Kaniivel (talk) 08:55, 2 January 2023 (UTC)

Hi, Kaniivel! Thanks for the feedback. Theoretically, if only template name and parameters need translation, it should not be that hard to implement. But is usually more than that; for example different languages use different punctuation or require special formatting for author names, dates, etc. Unfortunately, I don't think I'll be able to dedicate enough time to come up with robust solution for this in the near future. Dalba 05:58, 26 January 2023 (UTC)

Date issue

Hi Dalba I wrote about this before... Australian articles (and possibly New Zealand and anywhere where the sun rises earlier than a certain point?) seem to pick up the date a day earlier than the article is dated. I have also noticed recently that when I'm editing in the morning here downunder, the access-date comes up as the earlier date too. Examples on Desperate Measures (2013 Australian TV series). Editing this morning (9 Feb here), it was generating access-date as 8 Feb. It has now clocked over to the 9th. Not terribly serious but thought I may as well report it. Laterthanyouthink (talk) 00:11, 9 February 2023 (UTC)

Hi, Laterthanyouthink. Citer uses Toolforge's server time-zone for access dates which is set to UTC+0. It is possible to change this for each user and adjust according to their computer timezone, but computer clocks are sometimes wrong too for various reasons. I don't think a UTC+0 date is wrong here and as far as I know it is not against Wikipedia's manual of style. Also hiding the user's computer timezone could be considered a feature from a privacy point of view. All of that being said I might consider adjusting the access-dates for user's local time if more users request for it. Thanks for letting me know. Dalba 13:41, 10 February 2023 (UTC)

Ah, I see. Thanks for the explanation. I'll leave it up to you to do as you think best, or leave as is. Laterthanyouthink (talk) 06:15, 11 February 2023 (UTC)

JSTOR

This tool is so brilliant it can convert this: http://www.jstor.org/stable/20557185 into this:

• Bitel, Lisa (1987). "Sex, Sin, and Celibacy in Early Christian Ireland". Proceedings of the Harvard Celtic Colloquium (Department of Celtic Languages & Literatures, Harvard University) 7: 65–95. ISSN 1545-0155. JSTOR 20557185. Retrieved 2023-03-15. 

It's annoying that JSTOR doesn't provide the DOI, but so be it.

Thank you for your efforts. 76.14.122.5 04:53, 15 March 2023 (UTC)

Thanks for the heartwarming feedback! :) Dalba 06:49, 16 March 2023 (UTC)

publication-place=[Place of publication not identified]

Would it be possible to automatically remove "publication-place=[Place of publication not identified]" from the results? That parameter value pops up fairly often. Here's an example:

Wilde, Geoff; Braham, Michael (1995). Sandgrounders : the complete league history of Southport Football Club. [Place of publication not identified]: Carnegie. ISBN 1-874181-14-4. OCLC 650188009.  76.14.122.5 03:21, 24 March 2023 (UTC)

Done Dalba 16:09, 31 March 2023 (UTC)

Thanks! 76.14.122.5 21:32, 8 April 2023 (UTC)

Citer stopped working

Hi Dalba, today I can't your superb CITER to work it gives the message "502 Bad Gateway", some solution? Mcapdevila (talk) 14:40, 3 April 2023 (UTC)

Hi Mcapdevila! Should be fixed now. Thanks for letting me know. Dalba 15:12, 3 April 2023 (UTC)

Yes working fine now, thanks a lot, in my name an others from ca.wiki, for the hundreds of references achieved 93.176.134.117 21:35, 3 April 2023 (UTC)

Same error for ISBNs only

I'm not able to use citer now for ISBNs. Are others having the same problem? Is this related to citoid temporarily not dropping ISBN support? –SJ talk  17:49, 16 May 2023 (UTC)

Hi SJ, yes, it was related to citoid issue. I have now incorporated a fix to use Google books as an alternative source for ISBNs. It might not be as comprehensive as Citoid/worldcat, but is better than nothing. Also, it might be subject to rate limits of Google APIs and might start to fail if users send too many consecutive requests... It is working for now. Let me know if you see any issues. Dalba 04:48, 17 May 2023 (UTC)

Suggestion for improvement

Awesome citer! I love it. I have been using it on the Destruction of the Kakhovka Dam article. The only glitch I’ve noticed is that when I cite a source such as this:

https://www.understandingwar.org/backgrounder/russian-offensive-campaign-assessment-june-13-2023

it comes back with a ref that results in a “DNS_PROBE_FINISHED_NXDOMAIN” error. I then just substitute the correct address in "url=" and the correct title: RUSSIAN OFFENSIVE CAMPAIGN ASSESSMENT, JUNE 13, 2023.

Suggestion for improvement: you add the year to the end of the ref name but I’ve found that this results in duplicate ref names when the same person authors more than one article in that year. I’ve begun to replace the year with the date of the article, so that

<ref name="Melkozerova 2023"> becomes <ref name="Melkozerova 060923">

If you could do this when creating the ref that would eliminate this issue. Again, I just love the citer. It saves me so much work! Swood100 (talk) 21:33, 14 June 2023 (UTC)

Thank you!

The reason for the wrong URL in https://www.understandingwar.org/backgrounder/russian-offensive-campaign-assessment-june-13-2023 was the following open graph meta tag in the source of the webpage:

<meta property="og:url" content="http://dev-isw.bivings.com/" />

Citer uses this because sometimes the given URL contains some private information. "og:url" is usually safer with regard to privacy.

In this case, og:url is obviously wrong. I've updated citer to not use it when it points to a domain name.

It's hard to come up with a meaningful ref name. Adding full date works in some cases, but for others lacking a date or having the same date it may fail. For now, I changed the name generation mechanism to a semi-random string. This is against the recommendation of en:WP:REFNAME which states that "Names should have semantic value". I may revert this change if I get negative feedback from users. Dalba 15:46, 16 June 2023 (UTC)

I just noticed one other item. When using the CITER for this page:

https://www.wilsoncenter.org/blog-post/kakhovka-dam-disaster-responsibility-and-consequences

it came back with a reference containing "date=2023-06-07" whereas the page itself lists a date of "June 14, 2023" and Google in its search results says "6 hours ago". Best regards. Swood100 (talk) 22:14, 14 June 2023 (UTC)

This one is difficult to fix. The page does not provide any meta tags describing its date, so citer fallbacks to to finding the first found date in source code which belongs to an image... I'll look deeper into it if there are more reports like this.Dalba 15:46, 16 June 2023 (UTC)

I have come across a number of foreign websites working on this Ukraine article. When putting this one through the CITER:

https://zn.ua/ukr/war/ochilnik-khersonskoji-ova-serednij-riven-pidtoplennja-na-ranok-5-6-metra-evakujovano-majzhe-2-tisjachi-ljudej-.html

it produced a ref that generated some errors:  : Text "Mirror Weekly" ignored (help); Text "Дзеркало тижня" ignored (help) When I just removed those two paramaters from the ref everything was fine. Swood100 (talk) 23:03, 14 June 2023 (UTC)

Fixed The website title contains one or more | characters which is also a parameter delimiter in wiki templates... Citer will now ignore everything after the first pipe character. Dalba 15:46, 16 June 2023 (UTC)

Terrific! Works like a charm! If people complain that "Names should have semantic value", you might just use the ref name that you originally generated and append the semi-random string to that. Thanks again for all your hard work. Much appreciated!! Swood100 (talk) 16:03, 16 June 2023 (UTC)

I second this comment. It would be good to have the ref names use both the previous author/date combination as well as the random string, e.g.

<ref name="Kausch 2023 i8iia">{{cite web | last=Kausch | first=Katie | title=El Toro reopening at Six Flags Great Adventure after 10-month closure | website=nj | date=June 16, 2023 | url=https://www.nj.com/ocean/2023/06/el-toro-reopening-at-six-flags-great-adventure-after-10-month-closure.html | access-date=June 17, 2023 | page=}}

. This tool has been very useful to me over the years; thanks for keeping it running all this time. Epicgenius (talk) 23:29, 17 June 2023 (UTC)

Done Dalba 20:26, 18 June 2023 (UTC)

Outstanding!!! Many thanks! Swood100 (talk) 20:34, 18 June 2023 (UTC)

Hi again. I found another oddball website:

https://minagro.gov.ua/news/znishchennya-rosiyanami-kahovskoyi-ges-zavdalo-znachnih-zbitkiv-silskomu-gospodarstvu-ukrayini

This produces a <ref> that includes “language=ua”, which produces:

Script warning: One or more   templates have maintenance messages; messages may be hidden (help).

The problem is that it should be “language=uk” — “ua” is not one of the allowed codes on this page: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes See also: https://en.wikipedia.org/wiki/Template:Citation_Style_documentation/language/doc

“ua” does show up as the right code for Ukraine here: https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes

Can’t explain it. No hurry. This is the only time I’ve come across this. Thanks again! Swood100 (talk) 23:29, 20 June 2023 (UTC)

Looking at the source for that page it has lang="ua" on the first line, so maybe they just used an old-fashioned set of codes. Swood100 (talk) 23:38, 20 June 2023 (UTC)

In my original message I misstated the allowed codes. Apparently it is https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes that is expected but this page uses https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes Swood100 (talk) 15:56, 21 June 2023 (UTC)

Thanks for investigating the issue. Fixed Dalba 03:58, 22 June 2023 (UTC)

Awesome tool! Swood100 (talk) 20:40, 23 June 2023 (UTC)

Hello again! Just think of me as your tester, reporting the unexpected.

• This one produces a ref generating: Script warning: One or more   templates have errors; messages may be hidden (help).

https://babel.ua/en/news/94854-russia-submitted-a-statement-against-ukraine-to-the-international-criminal-court-kyiv-is-accused-of-destroying-the-kakhovka-hpp

The resulting ref has some unlabeled parameters:

| website=Бабель | Розповідаємо про політику, культуру і суспільство в Україні. Останні новини детально і неупереджено | date=2023-06-08 |

• Twitter refs always generate this error:  : Missing or empty |title= (help)

Maybe everything after “twitter.com/” and before the next “/” should become the title, so:

https://twitter.com/general_ben/status/1672243986038226946?cxt=HHwWhIC82fPCgLUuAAAA

would generate: title=general_ben

If that runs into difficulties how about just: title=twitter

At least then it wouldn't generate an error.

• This one produces a url different from the one it was given:

https://vk.com/wall-201841296_3412?lang=en

generated a different url:

{{cite web | title=Wall posts | website=VK | url=https://vk.com/video-201841296_456239220 | language=la | access-date=2023-06-24}}

The url generated is the url of the video. Missing is the screen with some text shown by the original url. Also, both urls say lang=’en’ but the ref produced says language=la, which doesn't generate an error but rather a curious "(in Latin)" in the listing.

Of course, it's no problem for me to just manually fix the resulting refs but I'm reporting them as a conscientious and dutiful tester should. Best regards! Swood100 (talk) 16:01, 24 June 2023 (UTC)

Hi! Thanks for reporting the issues!

• babel.ua: Fixed
• Twitter: Twitter does not provide any metadata or even a title for the URL in the HTML of the document. Getting the actual title of the page requires processing the JavaScript inside the page which Citer does not support. I could implement some module as you suggested just for twitter, but the result is still not satisfying. I don't think it is worth it.
• vk.com: url: The website is misusing open graph meta tags:

  <meta property="og:url" content="https://vk.com/video-201841296_456239220"/>
  

  I could just ignore og:url on all websites, but I think this will worsen the result for many other websites that are using the tag correctly.

• vk.com: language: Citer's bug. Fixed!

Dalba 13:17, 6 July 2023 (UTC)

Thanks! I don't know how I got along without this! Swood100 (talk) 00:41, 12 July 2023 (UTC)

Great tool. Consider, when identifiers are available, use the identifier for the value of the name attribute in the ref tag. If a PMID is present, that would be the first choice, if a DOI is present that would be the second choice. There may be other identifiers, but I do not know them. The rational is that wiki contributors may use varying citation tools, but if everyone uses a similar naming convention, there is less chance of chaos from a source being cited in multiple ways on a wiki page. Badgettrg (talk) 03:39, 20 August 2023 (UTC)

Thank you and thanks for the suggestion! I'm fine with that change, but some users find it less meaningful and against en:WP:REFNAME which states "Names should have semantic value, so that they can be more easily distinguished from each other by human editors who are looking at the wikitext. This means that ref names like "Nguyen 2010" are preferred to names like ":31337".". I may change the algorithm in the future if more users request it, but I'm going to keep it as is for now. Dalba 12:02, 24 August 2023 (UTC)

502 Bad Gateway

• OK, here's an odd one. This is link that takes the user to item #16 on the target page:

https://zakon.rada.gov.ua/laws/show/600-2023-%D0%BF#n17:~:text=16.%20%D0%A0%D0%BE%D0%B7%D0%BC%D1%96%D1%80%20%D0%BA%D0%BE%D0%BC%D0%BF%D0%B5%D0%BD%D1%81%D0%B0%D1%86%D1%96%D1%97%20%D0%B7%D0%B0%20%D0%B7%D0%BD%D0%B8%D1%89%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%BE%D0%B1%E2%80%99%D1%94%D0%BA%D1%82%20%D0%BD%D0%B5%D1%80%D1%83%D1%85%D0%BE%D0%BC%D0%BE%D0%B3%D0%BE%20%D0%BC%D0%B0%D0%B9%D0%BD%D0%B0%20%D1%80%D0%BE%D0%B7%D1%80%D0%B0%D1%85%D0%BE%D0%B2%D1%83%D1%94%D1%82%D1%8C%D1%81%D1%8F%20%D0%9A%D0%BE%D0%BC%D1%96%D1%81%D1%96%D1%94%D1%8E%20%D0%B7%D0%B0%20%D1%84%D0%BE%D1%80%D0%BC%D1%83%D0%BB%D0%BE%D1%8E%3A

When I enter that into the citer I get:

502 Bad Gateway

However, when taken to #16 on the target page, the address bar shows:

https://zakon.rada.gov.ua/laws/show/600-2023-%D0%BF#n17

If that is entered into the citer then it produces a normal <ref> to that page which, however, does not take the user to #16. At a minimum, I would guess that you would want to generate and display an error message containing more information than "502 Bad Gateway." Best regards. Swood100 (talk) 20:31, 19 July 2023 (UTC)

It was indeed an odd one. Fixed Dalba 07:46, 20 July 2023 (UTC)

That string is still generating the "502 Bad Gateway" error on my system. Swood100 (talk) 14:46, 20 July 2023 (UTC)

Hopefully it is fixed this time. Several fundamental changes have been made under the hood. Let me know if you see any issues. Dalba 23:15, 20 July 2023 (UTC)

Unclosed ref tag

Hello again. I tried to use Citer just now, but it seems like when I use it, the ref tag doesn't seem to actually be closed. For example, for this url, I get the following:

<ref name="Davidson 2021 j149">{{cite web | last=Davidson | first=Justin | title=Riverside Park Is Falling Apart | website=Curbed | date=May 12, 2021 | url=https://www.curbed.com/2021/05/nycs-riverside-park-is-falling-apart.html | access-date=July 21, 2023}}<ref>

I think the last <ref> should actually be a </ref>. Thanks again for your hard work. Epicgenius (talk) 00:06, 21 July 2023 (UTC)

Hi! Thank you! Fixed Dalba 00:46, 21 July 2023 (UTC)

That was fast, thanks! Epicgenius (talk) 01:05, 21 July 2023 (UTC)

Intentional change?

Hi again. I have noticed a few changes recently, one of which is expanding the ref name, but also leaving the url behind in the input field after creating the citation. Was this intentional? I find it a bit of a nuisance having to clear it each time I want to create another one. Laterthanyouthink (talk) 01:49, 28 July 2023 (UTC)

Hi! I've made a change that brings back the old behavior by clearing the input field after each submit. Let me know if you notice any other/related issues. Dalba 08:04, 28 July 2023 (UTC)

Thanks! :-) Laterthanyouthink (talk) 09:20, 28 July 2023 (UTC)

Sohu

Hello, the Sohu website（https://www.sohu.com/） consistently lacks https:// every time. Could it be fixed, please? Since the Sohu website is one of the larger platforms in China, it's frequently used when composing articles.--日期20220626 (talk) 06:22, 19 August 2023 (UTC)

Sohu is not using "og:url" meta tag properly. I've configured citer to ignore its value when it lacks a URL scheme. ( Fixed) Dalba 11:45, 24 August 2023 (UTC)

IUCN pages

I use IUCN pages for referencing the conservation status of plants. If I enter a specific page like this it references to https://www.iucnredlist.org/en , which is the generic front page that is not directly useful for someone cross referencing sources. --Cs california (talk) 07:18, 26 August 2023 (UTC)

Thanks for reporting the issue. Fixed Dalba 04:44, 27 August 2023 (UTC)

Help" Citer has stopped working

Dear Dalba I am using Citer many times per day, it is possible to fix it? maybe it's just the server.. anyway thanks for your work..Gives de msg. "504 Gateway Time-out" Mcapdevila (talk) 09:52, 12 September 2023 (UTC)

I have also encountered this situation. 日期20220626 (talk) 10:40, 12 September 2023 (UTC)

I just restarted the web-service, it should be back up. Will investigate later. Thanks for reporting the issue. Dalba 10:53, 12 September 2023 (UTC)

Hi, it's working again, thanks.. La-Rierada (talk) 13:58, 12 September 2023 (UTC)

Ça marche de nouveau!, merci!! Mcapdevila (talk) 14:00, 12 September 2023 (UTC)

pip dependencies installation failure on termux

install git on termux. cloned repo and when i pip install --user -r requirements.txt, it shows error:

~/citer $ pip install --user -r requirements.txt
Collecting isbnlib (from -r requirements.txt (line 1))
  Downloading isbnlib-3.10.14-py2.py3-none-any.whl (52 kB)
     ━━━━━━━━━━━━ 52.5/52.5   1.9 MB/s eta 0:00:00
                  kB
Collecting jdatetime (from -r requirements.txt (line 2))
  Downloading jdatetime-4.1.1-py3-none-any.whl (13 kB)
Collecting langid (from -r requirements.txt (line 3))
  Downloading langid-1.1.6.tar.gz (1.9 MB)
     ━━━━━━━━━━━━━ 1.9/1.9 MB 1.7 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting bs4 (from -r requirements.txt (line 4))
  Downloading bs4-0.0.1.tar.gz (1.1 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting lxml (from -r requirements.txt (line 5))
  Downloading lxml-4.9.3.tar.gz (3.6 MB)
     ━━━━━━━━━━━━━ 3.6/3.6 MB 1.9 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting regex (from -r requirements.txt (line 6))
  Downloading regex-2023.8.8.tar.gz (392 kB)
     ━━━━━━━━━━━━ 392.5/392.5 1.8 MB/s eta 0:00:00
                  kB
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
Collecting requests (from -r requirements.txt (line 7))
  Obtaining dependency information for requests from https://files.pythonhosted.org/packages/70/8e/0e2d847013cb52cd35b38c009bb167a1a26b2ce6cd6965bf26b47bc0bf44/requests-2.31.0-py3-none-any.whl.metadata
  Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting numpy (from langid->-r requirements.txt (line 3))
  Downloading numpy-1.26.0.tar.gz (15.6 MB)
     ━━━━━━━━━━━━ 15.6/15.6   1.9 MB/s eta 0:00:00
                  MB
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... error
  error: subprocess-exited-with-error

  × pip subprocess to install backend dependencies did not run successfully.
  │ exit code: 1
  ╰─> [64 lines of output]
      Collecting patchelf>=0.11.0
        Downloading patchelf-0.17.2.1.tar.gz (167 kB)
           ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 167.5/167.5 kB 1.1 MB/s eta 0:00:00
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'done'
        Preparing metadata (pyproject.toml): started
        Preparing metadata (pyproject.toml): finished with status 'done'
      Collecting ninja>=1.8.2
        Downloading ninja-1.11.1.tar.gz (27 kB)
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'done'
        Preparing metadata (pyproject.toml): started
        Preparing metadata (pyproject.toml): finished with status 'done'
      Building wheels for collected packages: patchelf, ninja
        Building wheel for patchelf (pyproject.toml): started
        Building wheel for patchelf (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error

        × Building wheel for patchelf (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [11 lines of output]
            Traceback (most recent call last):
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rxf18cbr/overlay/lib/python3.11/site-packages/skbuild/setuptools_wrap.py", line 645, in setup
                cmkr = cmaker.CMaker(cmake_executable)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rxf18cbr/overlay/lib/python3.11/site-packages/skbuild/cmaker.py", line 148, in __init__
                self.cmake_version = get_cmake_version(self.cmake_executable)
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rxf18cbr/overlay/lib/python3.11/site-packages/skbuild/cmaker.py", line 105, in get_cmake_version
                raise SKBuildError(msg) from err

            Problem with the CMake installation, aborting build. CMake executable is cmake
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for patchelf
        Building wheel for ninja (pyproject.toml): started
        Building wheel for ninja (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error

        × Building wheel for ninja (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [11 lines of output]
            Traceback (most recent call last):
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rjfa4tkz/overlay/lib/python3.11/site-packages/skbuild/setuptools_wrap.py", line 645, in setup
                cmkr = cmaker.CMaker(cmake_executable)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rjfa4tkz/overlay/lib/python3.11/site-packages/skbuild/cmaker.py", line 148, in __init__
                self.cmake_version = get_cmake_version(self.cmake_executable)
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "/data/data/com.termux/files/usr/tmp/pip-build-env-rjfa4tkz/overlay/lib/python3.11/site-packages/skbuild/cmaker.py", line 105, in get_cmake_version
                raise SKBuildError(msg) from err

            Problem with the CMake installation, aborting build. CMake executable is cmake
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for ninja
      Failed to build patchelf ninja
      ERROR: Could not build wheels for patchelf, ninja, which is required to install pyproject.toml-based projects
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install backend dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
~/citer $

rudhrudu (talk) 02:21, 24 September 2023 (UTC)

I do not use termux and I'm not sure how things work there but it looks like that termux is having trouble installing numpy package. According to instructions at https://wiki.termux.com/wiki/Python you should run pkg install python-numpy to install numpy in termux.

You will probably also face issues during installation of lxml and will need to install libxml2 and libxslt. I would try the following commands (not tested):

pkg install clang
pkg install libxml2
pkg install libxslt
pip install cython
pip install lxml
pkg install python-numpy
pip install --user -r requirements.txt

Dalba 04:11, 24 September 2023 (UTC)

@Dalba everything went smoothly except warning, able to access and create citation using port 5000. recently deleted github account, was tired of verification email. hence, contacted you  here.

WARNING: The script langid is installed in '/data/data/com.termux/files/home/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The script normalizer is installed in '/data/data/com.termux/files/home/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.

once again thank you. rudhrudu (talk) 08:22, 24 September 2023 (UTC)

@rudhrudu You're welcome. I'm glad to hear that it is working in termux. To suppress those warnings you can add those paths to your system PATH. You may be able to do that by running PATH=$PATH:/data/data/com.termux/files/home/.local/bin:/data/data/com.termux/files/home/.local/bin in bash. To do it once and forever you may want to add that command to ~/.bashrc or ~/.profile file.

All that being said, why not just use the online version at https://citer.toolforge.org/ ? :)

Dalba 10:42, 24 September 2023 (UTC)

> All that being said, why not just use the online version

nowadays browsers are memory guzzlers and ton of tracking tricks, just minimizing usage ;) rudhrudu (talk) 15:13, 24 September 2023 (UTC)

Unlabeled parameters

Hi again,

Just a minor but curious issue. These two addresses:

• https://www.wsj.com/articles/the-dangerous-denial-of-sex-11581638089
• https://www.wsj.com/articles/wokesters-in-search-of-nonbinary-birds-1d65ed47

result in the Citer putting text that should become the title into an unlabeled parameter.

The Citer is a godsend! Swood100 (talk) 20:38, 13 October 2023 (UTC)

Fixed Dalba 08:29, 20 October 2023 (UTC)

Problem with Citer

Hello, I am getting an error when attempting to use Citer. I am trying to generate a citation for this DOI

10.1111/all.13949

Here is the error I get:

JSONDecodeError('Expecting value: line 1 column 1 (char 0)')

Thanks, Svenskbygderna (talk) 17:32, 3 December 2023 (UTC)

Fixed Sorry for the late reply. Dalba 05:37, 15 December 2023 (UTC)

AttributeError

Hi again,

Given these URLs:

https://books.google.com/ngrams/graph?content=countermeasure&year_start=1740&year_end=1760&corpus=en-2019&smoothing=3

https://books.google.com/ngrams/

https://books.google.com/

citer respond with "AttributeError", whereas it has no problem with the following:

https://books.google.com/books?id=kvpby7HtAe0C&pg=PA18

Best regards. Swood100 (talk) 19:02, 9 December 2023 (UTC)

Fixed Dalba 06:34, 15 December 2023 (UTC)

ValueError

Hi again,

The following produces "ValueError":

https://www.un.org/en/about-us/un-charter/full-text

Best regards. Swood100 (talk) 21:34, 20 December 2023 (UTC)

Hello :) Fixed the error. (The author and date are wrong, but at least the error is fixed) Dalba 11:47, 21 December 2023 (UTC)

HTTP error: One or more of the web resources required to create this citation are not accessible at this moment.

Hi again. This URL:

https://lieber.westpoint.edu/building-momentum-next-steps-justice-ukraine/

produces the above message. Swood100 (talk) 23:56, 24 December 2023 (UTC)

Hi. Fixed Dalba 14:19, 25 December 2023 (UTC)

Thanks! Just came across the following URL which produces the same message:

https://legal.un.org/legislativeseries/pdfs/chapters/book25/english/book25_part2_ch3.pdf

Swood100 (talk) 18:10, 25 December 2023 (UTC)

Fixed Dalba 18:19, 26 December 2023 (UTC)

PMC maintenance message

Hi again,

FYI, this URL:

https://link.springer.com/article/10.1007/s00787-022-02082-8

generates a ref that contains "pmc=PMC10682114" which results in a green maintenance message described here. The maintenance message goes away when the "PMC" text is removed leaving only the number.

Swood100 (talk) 19:07, 27 December 2023 (UTC)

Hello! Fixed. Dalba 09:55, 28 December 2023 (UTC)

CS1 maint: unflagged free DOI

Hi again,

FYI, this URL:

https://journals.plos.org/globalpublichealth/article?id=10.1371/journal.pgph.0001478

generates a ref that results in a “{{cite journal}}: CS1 maint: unflagged free DOI (link)” green maintenance message, described here. The maintenance message goes away when “|doi-access=free” is added to the ref. Swood100 (talk) 18:43, 28 December 2023 (UTC)

Hi! Fixed Dalba 10:29, 29 December 2023 (UTC)

Repeated author in heavy.com citation

Hi Dalba. When I generate a citation for https://heavy.com/sports/pittsburgh-steelers/kirk-cousins-nfl-rumors-free-agency/, the author is getting repeated in the result:

<ref name="Holcomb Holcomb 2024 e511">{{cite web | last=Holcomb | first=Dave | last2=Holcomb | first2=Dave | title=Steelers Connected to Potential 'Splash' at QB to End Playoff Losing Streak | website=Heavy.com | date=2024-02-06 | url=https://heavy.com/sports/pittsburgh-steelers/kirk-cousins-nfl-rumors-free-agency/ | access-date=2024-02-09}}

(Obviously, that is not a good article for a citation, it's just a link I was using for testing.) Thanks. Daniel Quinlan (talk) 07:32, 9 February 2024 (UTC)

It happens on https://www.variety.com/review/VE1117921531/ too. Daniel Quinlan (talk) 10:44, 10 February 2024 (UTC)

Both Fixed. Thanks for reporting the problem. Dalba 06:03, 11 February 2024 (UTC)

error

I can't use citer.toolforge.org , it shows "Webservice request timed out".If you have time.please fix it,thank you.--日期20220626 (talk) 04:39, 10 January 2024 (UTC)

Done Dalba 04:47, 10 January 2024 (UTC)

Sorry, it doesn't work again. This time it's a blank page with only the ERR_CONNECTION_CLOSED prompt. Has the service been unstable recently? 日期20220626 (talk) 05:53, 11 January 2024 (UTC)

It's back to normal now. 日期20220626 (talk) 06:53, 11 January 2024 (UTC)

Citer and SNL/DSD

Hi there, citer is an amazing tool and I use it very frequently. I use it a lot for the two Scandinavian sources lex.dk and snl.no, which use the same underlying software, and it gives usable output, but does not capture author(s) of entries on those sites (marked with "skrevet af"/"skrevet av" on left side and bottom). Do you know if it would be possible to make it pull that info? I have not taken a serious look at the Github repo, but let me know if there are ways I can help. Replayful (talk) 21:22, 6 January 2024 (UTC)

Done Hi! The raw HTML of pages on these websites is too generic and lacks specific metadata about authors, but I have made some changes that will help with detecting the first author (trying to catch the other authors will probably lead to false positives on other websites which I'm trying to avoid). Dalba 07:51, 12 January 2024 (UTC)

Oh wow, thank you so much! This is immensely helpful even if it doesn't capture all. My impression using those sources are that the vast majority only has one author, so no big deal occasionally having to add authors manually. Thank you! Replayful (talk) 18:42, 12 January 2024 (UTC)

An unknown error occurred

Hi again,

The following results in an "unknown error"

https://www.reuters.com/world/europe/russia-says-ukrainian-forces-have-crossed-river-dnipro-face-hell-fire-death-2023-11-15/

Swood100 (talk) 20:41, 16 November 2023 (UTC)

Hi! Fixed Dalba 05:38, 17 November 2023 (UTC)

First and last names in citations

Thanks again for this awesome tool. I noticed that when you use this tool to add a citation to The New York Times, e.g. https://www.nytimes.com/1997/09/30/nyregion/worker-dies-as-scaffold-collapses-in-repair-job.html, it will not add the first and last names of the author, even if one is provided. For instance, inputting that particular URL creates the following citation:

* {{cite web | title=Worker Dies as Scaffold Collapses in Repair Job | website=The New York Times | date=September 30, 1997 | url=https://www.nytimes.com/1997/09/30/nyregion/worker-dies-as-scaffold-collapses-in-repair-job.html?searchResultPosition=1 | ref={{sfnref | The New York Times | 1997}} | access-date=October 19, 2023}}

A similar issue also occurs with other sources such as NPR. Is there a way to modify the tool so that it recognizes the author's first and last names? Thanks in advance. Epicgenius (talk) 01:12, 19 October 2023 (UTC)

Fixed Dalba 08:29, 20 October 2023 (UTC)

Odd error

Entered ISBN 9798863646336 from https://www.amazon.com/RESCUING-HERO-Daughters-Rwanda-Legend/dp/B0CKS4KLVB and got the result: "KeyError('title')" 76.14.122.5 20:15, 1 December 2023 (UTC)

Unfortunately Citer cannot find relevant information for this particular ISBN. I improved the error message. Dalba 15:27, 14 December 2023 (UTC)

Thank you. 76.14.122.5 05:50, 4 January 2024 (UTC)

One or more of the web resources required to create this citation are not accessible at this moment.

Hi again,

The following

http://hyperphysics.phy-astr.gsu.edu/hbase/mi.html#:~:text=For%20a%20point%20mass%2C%20the,a%20collection%20of%20point%20masses

consistently produces: "HTTP error: One or more of the web resources required to create this citation are not accessible at this moment."

An awesome tool! Swood100 (talk) 00:43, 2 December 2023 (UTC)

Fixed Dalba 05:35, 15 December 2023 (UTC)

Problem with Citer II

Hi! I use Citer in the de:WP. A good week ago everyting was OK. Now - if (on https://citer.toolforge.org/ ) I want to cite

https://www.google.fr/books/edition/Die_sch%C3%B6nsten_internationalen_Vornamen/xg9OG2dhvZAC?hl=en&gbpv=1&dq=wigald+vorname&pg=PR8&printsec=frontcover

I get AttributeError. Is there a way to fix this? Thanks! Tardigradus sapiens (talk) 16:25, 30 December 2023 (UTC)

Hi! Thanks for reporting the issue. Fixed Dalba 03:49, 31 December 2023 (UTC)

Beautiful! Works like a charm! All the best for 2024! Tardigradus sapiens (talk) 15:27, 31 December 2023 (UTC)

All the very best to you too, for a happy and fulfilling 2024. :) Dalba 15:35, 31 December 2023 (UTC)

JAMA Pages

The JAMA pages are currently grabbing website links but not adding the title as seen here.

It would be nice if the bot can cite the journal article from the link But I understand if it is a pain to code --Cs california (talk) 08:05, 29 December 2023 (UTC)

Thanks for taking the time to report the issue. It appears that the website employs a rate-limiting algorithm that temporarily blocks Toolforge's IP address when an excessive number of requests are made within a brief period. To address this, Citer has been recently configured to return a general citation template, instead of displaying an error message, in such cases. This allows users to manually fill in or add missing parameters, including the title. While ideally a warning would be displayed to inform users about the issue, I haven't been able to carve out the time to implement it. As a workaround, you can pass Citer the DOI of the article instead of its URL, which not only bypasses the rate-limiting issue, but usually results in more accurate citations. Dalba 16:20, 29 December 2023 (UTC)

This has started to work again. I'm not sure if it is due to recent changes in citer or a temporary. Dalba 16:50, 23 February 2024 (UTC)

Highlighting words on the target page

Hi again. If I enter this address to the citer:

https://books.google.com/books?id=GVIEAAAAMBAJ&dq=oppenheimer+%22if+the+radiance+of+a+thousand+suns+were+to+%22&pg=PA133

it results in a citation without the highlighting instructions:

https://books.google.com/books?id=GVIEAAAAMBAJ&pg=PA133

Of course, I can add it back in, but would there be any way of having the citer retain the highlighting? Swood100 (talk) 17:49, 29 August 2023 (UTC)

Hi! Actually, retaining the search highlights was the way Citer originally used to work, but then some users asked for the highlights to be removed automatically, arguing that the highlights may be irrelevant/distracting. I can't remember if Google provided the "Clear search" link at the time, but I can see it is there now, so it should be easy for users to remove the highlights themselves. I'm OK with this change, just not sure how other editors will receive it. Dalba 11:07, 1 September 2023 (UTC)

An unknown error occurred

Hi again. The following address:

https://www.isu.org/inside-isu/rules-regulations/isu-statutes-constitution-regulations-technical/29326-constitution-general-regulations-2022/file

results in the message: "An unknown error occurred." Swood100 (talk) 19:03, 10 September 2023 (UTC)

Related to the above is this address:

https://www.isu.org/inside-isu/rules-regulations/isu-statutes-constitution-regulations-technical

In the result, the website= parameter is "-", as is the first part of the ref name. Also, two words in the title are run together. Continuing to love the citer! Swood100 (talk) 19:49, 10 September 2023 (UTC)

Fixed Dalba 07:33, 15 September 2023 (UTC)

In case it helps you find the cause of the problem, I just had the same issue with this address:

https://stillmed.olympics.com/media/Documents/News/2023/03/Participation-for-Individual-Neutral-Athletes-Personnel-with-a-Russian-or-Belarusian-Passport.pdf

Best regards Swood100 (talk) 00:34, 13 September 2023 (UTC)

And also with this address:

https://s3.documentcloud.org/documents/23387965/bills-117hr7776eas-rcp117-70.pdf

Are all pdf files broken at this point? Swood100 (talk) 19:28, 13 September 2023 (UTC)

Hi there. Sorry for the late response. Yes. Citer does not currently support PDF files. They are hard to process and the results are usually very unreliable. But at the very least I have to improve the error message. Dalba 11:55, 14 September 2023 (UTC)

OK, no problem. How about the following as a message:

Citer does not yet support PDFs but here’s a generic stub you can begin with: <ref name="">{{cite web | title= | url=[address entered] | access-date=[today’s date]| date= | website=  }}</ref>

By the way, I also got that message when this address was entered:

https://packaged-media.redd.it/phb67w58bvl61/pb/m2-res_480p.mp4?m=DASHPlaylist.mpd&v=1&e=1694710800&s=d44b3be14fe4bcdfc10a04b918fb1e226914557e#t=0

which is a video clip. Also not supported? (I'm not complaining—the Citer is a godsend!) Swood100 (talk) 18:53, 14 September 2023 (UTC)

OK, Citer now generates a general template for these URLs instead of returning an error. But one should note that the {{sfn}} and ref name are almost always useless in such cases and will need to be modified manually if used. Dalba 07:42, 15 September 2023 (UTC)

Terrific! That will be very helpful. But allow me to suggest that you accompany this result with a clear statement that the result you are supplying is incomplete. As is, it is not explained do the user that this result is in a different category from the others, in that PDF files are not supported yet. As it is, the user might be left with the impression that, for some unknown reason, some of the results they get back are unaccountably incomplete. I would put, as the first line in the result box, something like this:

***ATTENTION*** You supplied a citation source that was a PDF file, but the Citer does not yet support these. However, as a convenience we have constructed a template for you to begin with as you create your own. Please examine it and supply the missing parameters.

If you could display this in red that would be even better. The trouble is that after they supply the necessary information and click Copy, they also get the warning text, and if you don't give them the warning text they never read it. Here's an alternative: put the warning text in red on the screen (and perhaps beep at them). Then, beep at them each time they click "Copy" until they click the box titled "I understand" that is next to the warning. It's a lot of work, but you don't want to leave it as it is. Swood100 (talk) 17:30, 15 September 2023 (UTC)

I think I would put the message right inside and at the top of the result box, and beep. Then if they click "Copy," beep again and copy a null instead (to clear the previous contents) and give them a message that after completing the citation themselves they must manually copy it. A special procedure for a special case. This way, you retain your reputation for reliability. Swood100 (talk) 17:52, 15 September 2023 (UTC)

Since this applies to the video as well, maybe you have to use a more generic message. So instead of "source that was a PDF file" you might say "source that was in format not yet supported by Citer." Swood100 (talk) 18:03, 15 September 2023 (UTC)

Thanks for all the suggestions! Delivering a warning requires quite a few changes in the code base. Not sure when I'll find the time to implement it, but I have that in mind. Dalba 04:20, 16 September 2023 (UTC)

OK. all these refs seem to be missing is a title, and that is pointed out when they do a Wikipedia preview. But the addition is a tremendous help. Thanks! Swood100 (talk) 19:09, 16 September 2023 (UTC)