User talk:Citation bot/Archive 6

This is an archive of past discussions with User:Citation bot. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 1

←

Archive 4

→

Bot does not handle aliases

Status: new bug
Reported by: It Is Me Here ^{t / c} 11:31, 3 September 2014 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: If an instance of {{cite journal}} has no |issue=φ, the Bot adds it, even if the {{cite journal}} already has |number=φ, throwing up a red error in read mode.
What should happen: It should do nothing (bypass {{cite journal}}s with |number=φ).
Relevant diffs/links: http://wiki.riteme.site/w/index.php?title=Template:Cite_doi/10.2307.2F1477803&diff=623994852&oldid=623994152
We can't proceed until: Agreement on the best solution

The bot also adds "pages=" when there is already a "p=" or "pp=" or "page=" card. AManWithNoPlan (talk) 21:00, 26 December 2015 (UTC)

...or "at=". Lithopsian (talk) 16:36, 29 December 2015 (UTC)

https://wiki.riteme.site/w/index.php?title=Calutron&type=revision&diff=688482098&oldid=688481880 Hawkeye7 (talk) 07:02, 1 November 2015 (UTC)

Another example of pages= being added when page= already exists: https://wiki.riteme.site/w/index.php?title=Inflow_%28meteorology%29&diff=next&oldid=698774275

Issue and number too: https://wiki.riteme.site/w/index.php?title=Ferruccio_Busoni&diff=prev&oldid=724431335 AManWithNoPlan (talk) 20:04, 16 July 2016 (UTC)

Here is hoses things by replacing a page range, with a page beginning https://wiki.riteme.site/w/index.php?title=History_of_Kentucky&diff=731670614&oldid=731670055 Stevie is the man! ^{Talk • Work}

The solution is to edit objects.php in the functions add_if_new() adding the needed things such as changing

        if (( $this->blank("pages") && $this->blank("page"))

into

        if (( $this->blank("pages") && $this->blank("page")  && $this->blank("pp")  && $this->blank("p"))

Also will need to add some, like this:

      case 'issue':
        if ($this->blank("issue") && $this->blank("number")) {        
          return $this->add($param, $value);
        } 
      return false;

since they are caught in the catch all:

      default:
        if ($this->blank($param)) {        
          return $this->add($param, sanitize_string($value));
        }
    }

AManWithNoPlan (talk) 15:06, 9 August 2016 (UTC)

See this diff, which results in a slew of citation errors for having both pages and pp, and note that in many of those entries, it munges the page range into an (inaccurate) single page. Squeamish Ossifrage (talk) 13:18, 18 October 2016 (UTC)

this is really a bug in the citation templates for allowing a bazillion different ways to say the same thing, but the bot needs to deal with it. The code to fix it is in the git repository. No one with the power upload it to the wmflabs has done so. So, it's also a bug in us meat bags too. AManWithNoPlan (talk) 14:25, 18 October 2016 (UTC)

Bot is running but bug is not fixed. https://wiki.riteme.site/w/index.php?title=S-50_%28Manhattan_Project%29&type=revision&diff=773923091&oldid=773516462 Bot must be shut down until bugs can be fixed. Hawkeye7 (talk) 06:53, 5 April 2017 (UTC)

Anyone with the power to stop the bot probably has the power to upload the fixes. AManWithNoPlan (talk) 15:16, 5 April 2017 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:17, 7 September 2017 (UTC)

Edits citations inside of nowiki tags

Status: new bug
Reported by: Izno (talk) 20:55, 29 April 2015 (UTC)
Type of bug: Inconvenience
What happens: The bot removed an accessdate from a citation without a URL (correctly) where the citation was used an example (and in this case happened to be wrapped in <nowiki>...</nowiki>.
What should happen: I'm not sure, but I think my suggestion is that the bot should not touch citations inside <nowiki>...</nowiki>.
Relevant diffs/links: //wiki.riteme.site/w/index.php?title=Help_talk:Citation_Style_1&curid=34112310&diff=659936244&oldid=659925010
We can't proceed until: Agreement on the best solution

The solution is to deal with this at the same time that the code escapes out comments AManWithNoPlan (talk) 04:42, 6 August 2016 (UTC) In objects.php add these lines right after equivalent comment lines:

    $comments = $this->extract_object(Comment);
    $nowiki   = $this->extract_object(Nowiki);

    $this->replace_object($comments);
    $this->replace_object($nowiki);


class Comment extends Item {
  const placeholder_text = '# # # Citation bot : comment placeholder %s # # #';
  const regexp = '~<!--.*-->~us';  // Note from AManWithNoPlan:  this regex is wrong---it is greedy: see other bot bugs on this talk page
  const treat_identical_separately = FALSE;
  
  public function parse_text($text) {
    $this->rawtext = $text;
  }
  
  public function parsed_text() {
    return $this->rawtext;
  }
}
class Nowiki extends Item {
  const placeholder_text = '# # # Citation bot : no wiki placeholder %s # # #';  // Have space in nowiki so that it does not through some crazy bug match itself recursively
  const regexp = '~<nowiki>.*?</nowiki>~us'; 
  const treat_identical_separately = FALSE;
  
  public function parse_text($text) {
    $this->rawtext = $text;
  }
  
  public function parsed_text() {
    return $this->rawtext;
  }
}

AManWithNoPlan (talk) 16:08, 9 August 2016 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:17, 7 September 2017 (UTC)

Duplicating jstor

Status: new bug
Reported by: Frietjes (talk) 14:11, 23 May 2015 (UTC)
Type of bug: Deleterious
What happens: Bot replaces a jstor url with a jstor parameter, but does not check to see if there is already a jstor parameter in the citation. hence, if there is already a blank jstor parameter, the jstor link is effectively deleted.
What should happen: Bot should first remove the empty jstor parameter, and/or any completely duplicate jstor parameters (i.e., jstor parameters with the exact same value).
Relevant diffs/links: http://wiki.riteme.site/w/index.php?title=Noye's_Fludde&type=revision&diff=663532320&oldid=637085644
Replication instructions: create a citation with both a jstor url and a jstor parameter in the citation template
We can't proceed until: Operator<

The bad code are these lines of get_identifiers_from_url() in objects.php:

          $this->rename("url", "jstor", $match[1]);

          $this->rename("url", "bibcode", urldecode($bibcode[1]));

          $this->rename("url", "pmc", $match[1] . $match[2]);

            $this->rename('url', 'asin', $match['id']);

They should match the doi code, which is a forget followed by a set:

          $this->forget('url');
          $this->set("doi", urldecode($match[1]));

I can't explain why one works and the other does not, but that is what happens. AManWithNoPlan (talk) 03:13, 9 August 2016 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:17, 7 September 2017 (UTC)

Google books data is sometimes rubbish

Status: new bug
Reported by: – Jonesey95 (talk) 04:42, 23 September 2015 (UTC)
Type of bug: Inconvenience
What happens: Bot puts journal name into title=
What should happen: Bot should put journal name into journal=
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Ataye_River&type=revision&diff=682349962&oldid=545633253
We can't proceed until: Bot operator's feedback on what is feasible

Also: https://wiki.riteme.site/w/index.php?title=Homing_pigeon&diff=prev&oldid=682284024

the bot thinks it can interpret Google Books metadata, and fails badly for journal articles that are published within journal issues listed as books by Google Books. —David Eppstein (talk) 04:56, 23 September 2015 (UTC)

(EC) I think you have to propose a solution if you want this fixed - the bot took the "title" from the Google books link, which is generally appropriate. Example of solution: ask the bot to leave the title untouched IF the template type is "cite journal" AND the url contains "books.google" AND the citation is not retrievable through crossref/pmid/etc databases, but still fix the title if the template is "cite book"? (I admit this criterion is somewhat too complex.). Materialscientist (talk) 04:57, 23 September 2015 (UTC)

In my experience the metadata at Google books is too unreliable to ever use without human intervention. It's often a good starting point, but it regularly does things like replacing the actual publisher name with the name of a business entity that later bought the publisher, using publication years that are much later than the actual publisher, mangling author names, listing minor contributors (e.g. the author of a preface) as the author of a whole book, listing multiple book series for a book only one of which is correct, listing publisher names as authors and author names as publishers, filling in the "edition" field with descriptive text instead of the edition number, listing only one author or editor for a book that has more than one, etc. —David Eppstein (talk) 05:33, 23 September 2015 (UTC)

Yes. I think we should avoid ~~any automated, or even semi-automated,~~ any extractions from Google metadata. Even having a human pass on such extractions is too slack, as, at best, such data is in no way authoritative, and suitable only as hints for further research. ~ J. Johnson (JJ) (talk) 21:51, 23 September 2015 (UTC)

I think manual extractions are ok as long as they are doublechecked against either the preview or a hardcopy. And editors who don't have a preview or a hardcopy shouldn't be adding the citation at all. But the bot can't do any of that, it can only copy what Google already has wrong, and that's not good enough. —David Eppstein (talk) 03:04, 30 September 2015 (UTC)

In such cases we are not doublechecking the metadata; we're using it to find an authoritative instance from which to extract the data directly. At any rate, I think we are agreed that a bot should not be making any changes or additions based on the Google metadata. ~ J. Johnson (JJ) (talk) 22:01, 2 October 2015 (UTC)

In objects.php AManWithNoPlan (talk) 02:49, 7 August 2016 (UTC) Change

      foreach ($xml->dc___creator as $author) {
        $this->add_if_new("author" . ++$i, formatAuthor(str_replace("___", ":", $author)));
      }

to:

      foreach ($xml->dc___creator as $author) {
        if( $author != "Hearst Magazines" ) {  // Catch common google bad authors
           $this->add_if_new("author" . ++$i, formatAuthor(str_replace("___", ":", $author)));
        }
      }

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:17, 7 September 2017 (UTC)

Erroneously reports DOI as broken

Status: new bug
Reported by: AManWithNoPlan (talk) 00:42, 18 November 2015 (UTC)
Type of bug: Improvement:
What happens: marks a DOI as invalid even if it works if there is no crossref entry
We can't proceed until: Agreement on the best solution
Requested action from maintainer: Only mark DOI invalid if dx.doi.org also fails

I thought this was fixed and marked it as so. Currently, doi is flagged as invalid if crossref fails, which is reasonable, but need to also check is dx.doi.org also failed AManWithNoPlan (talk) 00:42, 18 November 2015 (UTC)

I encounter this bug quite often and find it annoying, because in my naive thinking it should be easy to make the bot check the dx.doi.org/xxx link for a "broken" doi. A fresh example: run doi bot on Africanized bee, it will mark doi:10.3265/Nefrologia.pre2010.May.10269 as inactive. Materialscientist (talk) 03:34, 5 February 2016 (UTC)

Maybe the solution is change this code. I think this code only adds broken date if there is no re-direct information in dx.doi.org headers (lack of redirect implies dead doi):

        $this->add_if_new('doi_brokendate', date('Y-m-d'));

to:

        $url_test = "http://dx.doi.org/".$doi ;
        $headers_test = get_headers($url_test, 1);
        if(empty($headers_test['Location']))
                $this->add_if_new('doi_brokendate', date('Y-m-d'));

and change this code:

      $this->set("doi_brokendate", date("Y-m-d"));

to:

        $url_test = "http://dx.doi.org/".$doi ;
        $headers_test = get_headers($url_test, 1);
        if(empty($headers_test['Location']))
              $this->set("doi_brokendate", date("Y-m-d"));

AManWithNoPlan (talk) 16:28, 9 August 2016 (UTC)

Is this the same bug? Another editor reverted before I could act, but I checked and the doi is not broken at all. Hawkeye7 (talk) 22:25, 4 October 2016 (UTC)

Hard to tell. It works now. Probably a transient cross-ref failure. AManWithNoPlan (talk) 23:49, 4 October 2016 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Bot created arXiv= parameter error

Status: new bug
Reported by: – Jonesey95 (talk) 03:56, 7 December 2015 (UTC)
Type of bug: Inconvenience
What happens: Bot changed a valid |eprint= parameter into an invalid one by removing the class
What should happen: Bot should leave valid parameters alone
Relevant diffs/links: Search for 0508091 in this diff
We can't proceed until: Bot operator's feedback on what is feasible
Requested action from maintainer: Modify code to match {{cite arxiv}}

The bot removed the class portion of the arXiv parameter value in {{cite arxiv}}. It should not have done so. There are two kinds of arXiv parameters, explained in the documentation as follows:

arxiv or eprint (Mandatory): arXiv/Eprint identifier, without any "arXiv:" prefix. Prior to April 2007, the identifiers included a classification, an optional two-letter subdivision, and a 7-digit YYMMNNN year, month, and sequence number of submission in that category. E.g. gr-qc/0610068 or math.GT/0309136. After April 2007, the format was changed to a simple YYMM.NNNN. Starting in January 2015, the identifier was changed to be 5 digits: YYMM.NNNNN.
class: arXiv classification, e.g. hep-th. Optional. To be used only with new-style (2007 and later) eprint identifiers that do not include the classification.

The bot should not modify valid |arxiv= or |eprint= parameters. – Jonesey95 (talk) 03:56, 7 December 2015 (UTC)

Here's a minimal diff showing this problem. Lithopsian (talk) 00:02, 29 December 2015 (UTC)

This is still happening. – Jonesey95 (talk) 13:30, 27 July 2016 (UTC)

Here is an example of one that gets broken. {{cite arXiv|eprint=astro-ph/0409583 | title = Exploring the Divisions and Overlap between AGB and Super-AGB Stars and Supernovae | last1 = Eldridge | first1 = J. J. | last2 = Tout | first2 = C. A.|class=astro-ph|date=2004 }} AManWithNoPlan (talk) 15:49, 9 August 2016 (UTC)

Here is the offending source code from objects.php:

    $eprint = str_ireplace("arXiv:", "", $this->get('eprint') . $this->get('arxiv'));
    if ($class && substr($eprint, 0, strlen($class) + 1) == $class . '/')
      $eprint = substr($eprint, strlen($class) + 1);
    $this->set($arxiv_param, $eprint);

that should be:

    $eprint = str_ireplace("arXiv:", "", $this->get('eprint') . $this->get('arxiv'));
    //if ($class && substr($eprint, 0, strlen($class) + 1) == $class . '/')
    //  $eprint = substr($eprint, strlen($class) + 1);
    $this->set($arxiv_param, $eprint);

AManWithNoPlan (talk) 15:56, 9 August 2016 (UTC)

This only occurs if class is set AManWithNoPlan (talk) 00:26, 14 October 2016 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 03:19, 7 September 2017 (UTC)

Link at top of results page leads to error

Status: new bug
Reported by: Lithopsian (talk) 13:27, 26 December 2015 (UTC)
Type of bug: Cosmetic
What happens: After expanding citations for a page containing spaces in the title, the results page shows a link to the article at the top and bottom of the page. The link at the top does not lead to the article, but to an error page.
We can't proceed until: Agreement on the best solution

This code in objects.php :

    quiet_echo ("\n<hr>[" . date("H:i:s") . "] Processing page '<a href='http://wiki.riteme.site/wiki/" . addslashes($this->title) . "' style='text-weight:bold;'>{$this->title}</a>' &mdash; <a href='http://wiki.riteme.site/?title=". addslashes(urlencode($this->title))."&action=edit' style='text-weight:bold;'>edit</a>&mdash;<a href='http://wiki.riteme.site/?title=" . addslashes(urlencode($this->title)) . "&action=history' style='text-weight:bold;'>history</a> <script type='text/javascript'>document.title=\"Citation bot: '" . str_replace("+", " ", urlencode($this->title)) ."'\";</script>");

needs changed to

    quiet_echo ("\n<hr>[" . date("H:i:s") . "] Processing page '<a href='http://wiki.riteme.site/?title=" . addslashes($this->title) . "' style='text-weight:bold;'>{$this->title}</a>' &mdash; <a href='http://wiki.riteme.site/?title=". addslashes(urlencode($this->title))."&action=edit' style='text-weight:bold;'>edit</a>&mdash;<a href='http://wiki.riteme.site/?title=" . addslashes(urlencode($this->title)) . "&action=history' style='text-weight:bold;'>history</a> <script type='text/javascript'>document.title=\"Citation bot: '" . str_replace("+", " ", urlencode($this->title)) ."'\";</script>");

AManWithNoPlan (talk) 21:10, 6 August 2016 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Error converting url to arxiv parameter

Status: new bug
Reported by: Hawkeye7 (talk) 21:48, 27 December 2015 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: A Bot inserted an arxiv= into a template on Metallurgical Laboratory creating a red "Check |arxiv= value" error message. Corrected by removing the ".pdf" from the end of the arxiv. see https://wiki.riteme.site/w/index.php?title=Metallurgical_Laboratory&type=revision&diff=697034978&oldid=697034297
We can't proceed until: A specific edit to the bot's code is requested below.

Just need to strip the .pdf off of url when converting url to eprint. Super easy code change. AManWithNoPlan (talk) 19:19, 9 January 2016 (UTC)

Change in objects.php

        $this->add_if_new("arxiv", $match[1]);
        if (strpos($this->name, 'web')) $this->name = 'Cite arxiv';

to

        $match[1] = str_replace ( ".pdf" , "" , $match[1] )
        $this->add_if_new("arxiv", $match[1]);
        if (strpos($this->name, 'web')) $this->name = 'Cite arxiv';

and change this:

    return "{{Cite arxiv | eprint={$match[1]} }}";

to:

    $match[1] = str_replace ( ".pdf" , "" , $match[1] )
    return "{{Cite arxiv | eprint={$match[1]} }}";

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

JSTOR plant link mistaken for journal

Status: new bug
Reported by: Josh Milburn (talk) 15:10, 7 February 2016 (UTC)
Type of bug: Deleterious
What happens: The bot is changing a JSTOR link to the JSTOR Global Plants project to an unrelated link to a JSTOR journal article. It falsely believes that the "JSTOR=" link on {{cite journal}} (admittedly, this is probably not the template which should have been used in the article) can be used in this case, when it cannot, as the citation is to a different part of the JSTOR website.
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Persoonia_terminalis&type=revision&diff=703656019&oldid=703655944
We can't proceed until: Agreement on the best solution
Requested action from maintainer: detect plant jstor urls and ignore

That's annoying that JSTOR has chosen to add a new type of stable link (although it does start with plant) AManWithNoPlan (talk) 19:21, 7 February 2016 (UTC)

The fix needs put in objects.php the third through fifth lines

      if (strpos($url, "sici")) {
        #Skip.  We can't do anything more with the SICI, unfortunately.
      elseif (strpos($url, "plants")) {
        #Skip.  We can't do anything more with the plants, unfortunately.
      }  else

AManWithNoPlan (talk) 21:00, 6 August 2016 (UTC)

new github pull that changes plants to plants.jstor.com AManWithNoPlan (talk) 22:33, 4 September 2017 (UTC)

That pull is accepted, but #116 opened 12 minutes ago by kaldari has now been added that fixes the missing bracket before the elseif. AManWithNoPlan (talk) 16:42, 5 September 2017 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

When bibcodes ends with a dot, it leaves the dot out

Status: new bug
Reported by: Headbomb {talk / contribs / physics / books} 17:53, 19 June 2016 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: When bibcodes ends with a dot, it leaves the dot out (2010Natur.464...59)
What should happen: The bot should retrieve the full 19-character bibcode (2010Natur.464...59.)
Relevant diffs/links: search for the string "| bibcode = 2010Natur.464...59" in the diff
We can't proceed until: Bot operator's feedback on what is feasible

I think the solution is to modify objects.php to add a special case for bibcodes, to sit above the catch all code:

      default:
        if ($this->blank($param)) {        
          return $this->add($param, sanitize_string($value));
        }

such as:

      case 'bibcode':
        if ($this->blank($param)) { 
          $bibcode_pad =  strlen($value) - 19;
          if($bibcode_pad > 0 ) {  // Paranoid, don't want a negative value, if bibcodes get longer
              value = $value . str_repeat( ".", $bibcode_pad);  // Add back on trailing periods
          }
          return $this->add($param, $value);
        } 
      return false;

AManWithNoPlan (talk) 21:34, 6 August 2016 (UTC)

Here's another diff showing this bug. – Jonesey95 (talk) 16:17, 10 August 2016 (UTC)

And another diff showing this bug. GoingBatty (talk) 13:38, 19 August 2016 (UTC)

new github pull fixes this better by changing V-9 to 9-V. Which is correct fix. AManWithNoPlan (talk) 22:35, 4 September 2017 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Comments cause trouble

Status: new bug
Reported by: – Jonesey95 (talk) 02:54, 9 November 2014 (UTC) & 2 years later, Wikid77 (talk) 14:29, 30 September 2016 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: Bot changed |publisher= to |DUPLICATE_publisher= in the absence of a duplicate publisher parameter
What should happen: Bot should not do that.
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Fathima_Beevi&diff=629715024&oldid=610463414
Replication instructions: Two years later, on 29 September 2016, Citation_bot still confused by comment "" and put DUPLICATE_title & DUPLICATE_url when only one title/url, in page "Mary Babnik Brown" (dif135). -Wikid77 (talk) 14:29, 30 September 2016 (UTC)
We can't proceed until: Bot operator's feedback on what is feasible

As far as I can tell, there were no duplicated parameters when the bot did its edit. – Jonesey95 (talk) 02:54, 9 November 2014 (UTC)

How did you get this? The bot is not currently working.--Auric talk 13:49, 9 November 2014 (UTC)

The edit is date-stamped 15 October 2014. I just discovered it yesterday while going through Category:Pages with citations using unsupported parameters. – Jonesey95 (talk) 15:48, 9 November 2014 (UTC)

Here's another similar one, adding DUPLICATE to |archiveurl= and |archivedate=. – Jonesey95 (talk) 19:53, 10 November 2014 (UTC)

This looks like it related to comments in the references in all cases. This appears to be a common thread in bot bugs on this page. AManWithNoPlan (talk) 04:45, 1 February 2015 (UTC)

Adding bogus |year= https://wiki.riteme.site/w/index.php?title=Wealden_Line&diff=629805699&oldid=629545497

DUPLICATE_ added: https://wiki.riteme.site/w/index.php?title=509th_Composite_Group&diff=636859536&oldid=636220208

DUPLICATE_ added: https://wiki.riteme.site/w/index.php?title=Shapley%E2%80%93Folkman_lemma&diff=655089982&oldid=651991293

This bug appears to still be present in the current version, as of this date stamp. Pinging Fhocutt (WMF). – Jonesey95 (talk) 03:46, 22 September 2015 (UTC)

Give it another try? I tested the dev version (now the actual version) on testwiki and it didn't add DUPLICATE: https://test.wikipedia.org/w/index.php?title=User%3AFhocutt_%28WMF%29%2FCitation_bot_test&type=revision&diff=243602&oldid=243601 . --Fhocutt (WMF) (talk) 23:04, 9 October 2015 (UTC)

It's still doing it here on en.WP. – Jonesey95 (talk) 23:15, 9 October 2015 (UTC)

Here is a very simple reproducer

Here are a variety of lines from the bot source code (i might have missed one)

  const regexp = '~<!--.*-->~us';
  $comment_regexp = "~(<!--.*?)\|(.*?-->)~";
  while(preg_match("~<!--.*?-->~", $c, $match)) {
  if (preg_match_all("~<!--[\s\S]*?-->~", $page_code, $match)) {

I think the problem is the first one. It is greedy. The .* needs to be .*? like number three. AManWithNoPlan (talk) 20:41, 7 August 2016 (UTC)

Still happening Hawkeye7 (talk) 02:36, 14 February 2017 (UTC)

https://wiki.riteme.site/w/index.php?title=2010_New_York_Yankees_season&type=revision&diff=797318586&oldid=796799252 Plastikspork

https://wiki.riteme.site/w/index.php?title=Alpha_particle&diff=795641460&oldid=795641155 Headbomb

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Google data is not always right, and the bot is not telepathic

Status: new bug
Reported by: Stevie is the man! ^{Talk • Work} 15:57, 22 January 2017 (UTC)
Type of bug: Inconvenience
What happens: 1) the first cite change sets params to "|author1=Inc |first1=Time"; 2) the third cite change sets params to "|author1=Friedwald|first1=Will|date=2010-11-02"
What should happen: 1) should be something like "|author1=Time Inc." or perhaps don't have an author; 2) should be "|last1=Friedwald|first1=Will|date=November 2, 2010" (the date part didn't respect {{Use mdy dates}}
Relevant diffs/links: diff
We can't proceed until: Consensus<

The date is grabbed from Google and not massaged at all. AManWithNoPlan (talk) 00:40, 23 January 2017 (UTC)

Pull added to github that detects Time Inc AManWithNoPlan (talk) 00:14, 6 September 2017 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Bot generated invalid cite data "# # # comment"

Status: still bug
Reported by: Wikid77 (talk) 22:27, 26 March 2017 (UTC)
Type of bug: Bad, invalid cite parameter
What happens: While bot changes Google Books links in "A. C. Benson" (dif276), a commented  archive url became "# # # citation bot : comment # # #" or such.
We can't proceed until: Agreement on the best solution

This is because the search and replace is case sensitive, which is fine an dandy 99.9% of the time. Obviously, 0.1% of the time it fails. AManWithNoPlan (talk) 15:16, 5 April 2017 (UTC)

{{resolved}} in development branch. Live soon. AManWithNoPlan (talk) 02:33, 7 September 2017 (UTC)

Incorrect DOI removal

Status: new bug
Reported by: TheDragonFire (talk) 06:17, 22 July 2017 (UTC)
Type of bug: Deleterious
What happens: The bot incorrectly removes a DOI from a citation, and inexplicably renames a blank url parameter to DUPLICATE_url.
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Referred_itch&diff=791742279&oldid=774741740
We can't proceed until: Agreement on the best solution

This is the comments bug. The bot uses a greedy search for comments. AManWithNoPlan (talk) 13:13, 22 July 2017 (UTC)

I just proved it by undoing the previous edit, then removing the comments, and finally running the bot again. https://wiki.riteme.site/w/index.php?title=Referred_itch&diff=prev&oldid=791790626 AManWithNoPlan (talk) 14:21, 22 July 2017 (UTC)

{{resolved}} in development branch. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

Authors must be people, not companies

Status: new bug
Reported by: Stepho talk 09:29, 16 August 2017 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: Bot is adding company names in author fields, eg '|author1=Magazines |first1=Hearst'
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Internal_combustion_engine&type=revision&diff=795735634&oldid=795700442
We can't proceed until: Bot operator's feedback on what is feasible

Perhaps the bot could look for keywords like 'magazine', 'journal', 'newspaper', etc and common variations (eg upper/lowercase, plurals). Stepho talk 09:29, 16 August 2017 (UTC)

{{resolved}} in development branch for a few select authors. Soon to be live. AManWithNoPlan (talk) 02:18, 7 September 2017 (UTC)

issue vs. volume confusion for journals with no volumes

Status: feature request
Reported by: All the best: Rich Farmbrough, 01:38, 11 November 2014 (UTC).
Type of bug: Inconvenience
What happens: for the journal ZooKeys changes the issue number to a volume number.
What should happen: Should understand that this number is an issue number with this particular journal
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Aegista_diversifamilia&diff=630393100&oldid=629974617 - see discussion here
Replication instructions: A similar ZooKeys doi template
We can't proceed until: Bot operator's feedback on what is feasible
Requested action from maintainer: Build in specific knowledge of this journal's numbering scheme. Possibly a list of one, unless and until other similar items are found.

http://search.crossref.org/?q=10.3897/zookeys.445.7778 The cross-ref data is wrong. So, it is not a bot bug, but the bot could easily fix it. AManWithNoPlan (talk) 19:15, 2 October 2015 (UTC)

The bot need to add special code for journals like this. And then internally store a list of of such journals. AManWithNoPlan (talk) 00:13, 3 January 2016 (UTC)

The solution is to add code to objects.php in the public function add_if_new($param, $value) AManWithNoPlan (talk) 02:10, 7 August 2016 (UTC)

      case 'volume':
        if ($this->blank($param)) {
          if (  $this->get('journal') == "ZooKeys" ) add_if_new('issue',$value) ; // This journal has no volume
          return $this->add($param, $value);
        }
      return false;

And change this code:

        if ($this->blank("journal") && $this->blank("periodical") && $this->blank("work")) {
          return $this->add($param, sanitize_string($value));
        }

to

        if ($this->blank("journal") && $this->blank("periodical") && $this->blank("work")) {
          if ( sanitize_string($value) == "ZooKeys" ) $this->blank("volume") ; // No volumes, just issues.
          return $this->add($param, sanitize_string($value));
        }

Might be best long term to have a global array of such journals rather than having to keep adding them one by one.

New github pull request with zookeys spelled correct added. AManWithNoPlan (talk) 16:56, 7 September 2017 (UTC)

{{resolved}} AManWithNoPlan (talk) 17:42, 7 September 2017 (UTC)

`Unknown` is not a journal name

Status: feature request
Reported by: (t) Josve05a (c) 06:51, 24 September 2015 (UTC)
Type of bug: Inconvenience
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Digital_object_identifier&diff=prev&oldid=682510640
We can't proceed until: Bot operator's feedback on what is feasible

In this case it looks like bad data at ADS rather than the bot's fault. —David Eppstein (talk) 06:56, 24 September 2015 (UTC)

Yes, but I think that the bot can have one line of code that refuses to add a journal name that is unknown. AManWithNoPlan (talk) 15:22, 1 October 2015 (UTC)

I think this fix is needed in objects.php is second line and fourth line AManWithNoPlan (talk) 20:59, 6 August 2016 (UTC)

        $this->add_if_new("bibcode", (string) $xml->record->bibcode);
        if ( strcasecmp( (string) $xml->record->bibcode ), "unknown") )  {  // Returns zero if the same
        $this->add_if_new("title", (string) $xml->record->title);
        }

A new git pull has been submitted by someone to add the == 0 part to it that I missed. I guess the fact that I do not know php is showing. AManWithNoPlan (talk) 16:56, 5 September 2017 (UTC)

New pull added that checks in more places. AManWithNoPlan (talk) 16:57, 7 September 2017 (UTC)

{{resolved}} AManWithNoPlan (talk) 17:41, 7 September 2017 (UTC)

Special characters in data need escaped

Status: feature request
Reported by: – Jonesey95 (talk) 03:42, 22 September 2015 (UTC)
Type of bug: Inconvenience
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Latamoxef&type=revision&diff=682190504&oldid=682190396
We can't proceed until: Bot operator's feedback on what is feasible

This is a pretty obscure bug, but if someone wanted to fix it, they could run the title through a regex to look for "[[" and replace it with "[[" (as was done on that article). Kaldari (talk) 20:56, 22 September 2015 (UTC)

And pipes too: https://wiki.riteme.site/w/index.php?title=User%3AJonesey95%2Fsandbox2&diff=prev&oldid=694077824

The problem is that the source of the metadata, http://adsabs.harvard.edu/abs/1991bsc..book.....H, has a vbar within an author's name, I think erroneously as the author in question doesn't use a middle name or initial, and the bot doesn't recognize it and quote it to prevent it becoming a parameter delimiter. So I think there are really two issues here: (1) bad data elsewhere that we can't do much about, and (2) better bot handing of special characters in external data. —David Eppstein (talk) 21:39, 6 December 2015 (UTC)

I have added a diff in the bug description above. When vertical bars occur in URLs, replace each vertical bar with %7c. When vertical bars occur in parameter values that are not URLs, replace each vertical bar with |. – Jonesey95 (talk) 23:46, 6 December 2015 (UTC)

Yes that's it. Sounds like a sensible solution. I've not seen one of these where the vertical bar is anything other than a mistake, but I suppose it is possible in some cases. Even for a mistake, it is perhaps best for the bot to keep the character, without breaking the formatting, and someone to take it out by hand if it is really obnoxious. Lithopsian (talk) 12:25, 7 December 2015 (UTC)

Sometimes for news site or web site sources, the pipe character or spaced dash may come up in |title= values, where it should really be treated as a field delimiter between title and publisher. I'm not sure if citationbot checks for that, but certainly there are some other tools that are getting it wrong. It would be good if citationbot caught and corrected those errors, rather than just converting the character to have a less-obvious error. LeadSongDog come howl! 17:06, 7 December 2015 (UTC)

Need to add the second line here in expandFns.php AManWithNoPlan (talk) 15:22, 9 August 2016 (UTC)

function format_title_text($title) {
   $title = sanitize_string($title)

also in object.php need to do a lot of changing this:

          return $this->add($param, $value);

to this:

          return $this->add($param, sanitize_string($value));

within these areas:

      case "editor": case "editor-last": case "editor-first":
 .............
      case "first90": case "first91": case "first92": case "first93": case "first94": case "first95": case "first96": case "first97": case "first98": case "first99":

the top bug fix is missing the semicolon at the end of the line. I had GlazerMann submit a new pull request to github. AManWithNoPlan (talk) 16:04, 31 August 2017 (UTC)

New github pull submitted that does this for more types of data sources (DOI, PMID, etc.) AManWithNoPlan (talk) 16:56, 7 September 2017 (UTC)

{{resolved}} in development branch. AManWithNoPlan (talk) 15:20, 11 September 2017 (UTC)

Inline "Citations" button does not work as well as calling the bot through link

Status: new bug
Reported by: Martin (Smith609 – Talk) 08:52, 15 September 2017 (UTC)
Type of bug: Inconvenience
What happens: Bot does not expand citation when called through Citations button (see prior link for output of that); it does when called directly through wmflabs link on edited page
What should happen: Output should be same however bot is called
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Jianshanopodia&diff=prev&oldid=800726211
We can't proceed until: A specific edit to the bot's code is requested below.
Requested action from maintainer: Update script called from Citations button, or establish that it works as expected

Button on the left sets slow=1, inline editing does not. Maybe slow should be removed from bot, made default, or added to button. AManWithNoPlan (talk) 13:48, 15 September 2017 (UTC)

I have whined at https://wiki.riteme.site/wiki/MediaWiki_talk:Gadget-citations.js AManWithNoPlan (talk) 15:03, 21 September 2017 (UTC)

you know it’s a big deal when the bot writer reports a bug. AManWithNoPlan (talk) 03:41, 23 September 2017 (UTC)

{{resolved}} The page is edited. AManWithNoPlan (talk) 15:02, 25 September 2017 (UTC)

Adding invalid field (|DUPLICATE_work)

Status: new bug
Reported by: OhanaUnited^{Talk page} 15:34, 27 September 2017 (UTC)
Type of bug: Inconvenience
What happens: Bot added an invalid field within {{cite web}}
What should happen: It should do nothing
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Bombardier_CSeries&curid=1567474&diff=802642343&oldid=802639630
We can't proceed until: Bot operator's feedback on what is feasible

This is not a bug. Check archive discussion to see why this is a good thing. AManWithNoPlan (talk) 16:07, 27 September 2017 (UTC)

https://wiki.riteme.site/wiki/User_talk:Citation_bot/Archive_5#DUPLICATE_parameters AManWithNoPlan (talk) 16:24, 27 September 2017 (UTC)

Standardize and Customize Journal Capitalization

Status: feature request
Reported by: Saimondo (talk) 16:21, 3 August 2014 (UTC)
Type of bug: Improvement
What happens: Bot writes for example "Molecular and cellular biology" instead of "Molecular and Cellular Biology" by autofilling with PMID 9858585
Replication instructions: autocomplete with PMID 9858585
We can't proceed until: Agreement on the best solution

Extended content

Data on NCBI seems to be ok: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC83919/ where the Journal is written as "Mol Cell Biol." on the webpage and as "MOLECULAR AND CELLULAR BIOLOGY" in the full text pdf.

What to do in those cases? Include "Molecular and Cellular Biology" in: https://wiki.riteme.site/wiki/User:Citation_bot/capitalisation_exclusions in sush cases?

The same with

-"The Journal of biological chemistry" e.g. PMID 9858585

-"The Journal of cell biology" e.g. PMID 9763423

an other cases seen in https://wiki.riteme.site/wiki/Special:RecentChangesLinked/Category:Cite_doi_templates ? Thanks--Saimondo (talk) 16:21, 3 August 2014 (UTC)

Actually PubMed lists the journal as "Molecular and cellular biology" in the webpage meta data. A very minor case of GIGO. AManWithNoPlan (talk) 02:31, 4 August 2014 (UTC)

Perhaps its worth quoting the University of Chicago Manual of Style (14th ed.) on this matter:

"In regular title capitalization, also known as headline style, the first and last words and all nouns, pronouns, adjectives, verbs, adverbs, and subordinating conjunctions (if, because, as, that, etc.) are capitalized. Articles (a, an, the), coordinating conjunctions (and, but, or, for, nor), and prepositions, regardless of length are lowercased unless they are the first or last word of the title or subtitle. The to in infinitives is also lowercased."

On the other hand, it is common in library cataloging following MARC format to capitalize only the initial word, proper nouns, and, if the title begins with an article, that article and the following noun.

Wikipedia citations should follow citation style, rather than library cataloging style. In this case, the appropriate form would be "Molecular and Cellular Biology". The Wikipedia Manual of Style provides much the same advice on the capitalization of titles. SteveMcCluskey (talk) 18:40, 4 August 2014 (UTC)

I am not very familiar with PHP (the language that Citation Bot is coded in), but it would appear that there is a mb_convert_case function:

 $str = mb_convert_case($str, MB_CASE_TITLE, "UTF-8");

that can transform a string into title case (i.e., capitalize the first and last words of the title and all nouns, pronouns, adjectives, verbs, adverbs, and subordinating conjunctions). This function would probably work well for most journal names. Boghog (talk) 19:15, 4 August 2014 (UTC)

This should be easy to implement, but I anticipate that some time down the line it will upset someone. Before I implement it, could we establish consensus and file a bot approval request if necessary? Thanks. Martin (Smith609 – Talk) 08:49, 25 August 2014 (UTC)

How about your implement it for adding journal titles, but don't implement it for changing existing entries. Eventually, the list of titles that violate the rules will be built up, and then you can make it is a fix for existing journal titles. AManWithNoPlan (talk) 01:48, 4 September 2014 (UTC)

You are of course right, it´s no error it´s the catalog style NCBI is using. I don´t have the complete overview what capitalization format is obtained by the doi or issn vs pmid queries. But if you use the cite-> templates-> cite journal option here in the edit window and use autofill with the doi:10.1128/MCB.00698-14 you get "Molecular and Cellular Biology" if you use the same publications PMID 25022755 with autofill you get "Molecular and cellular biology". If capitalization means also harmonization I think few wikipedians would be against it.

Furthermore, as far as I understand https://wiki.riteme.site/wiki/Wikipedia:Manual_of_Style#Titles_of_works the capitalization format like above should be ok (I have the impression that most journals use capitalization for their own names on their homepages/pdfs). Should we ask on the Manual of style talk page to see if there´s a consensus for capitalization? In case someone is interested, here is a recent reply of an email I (re-)sent to NCBI some time ago:

"...Standard cataloging requires that the first word in the full journal title begins with an upper case letter and remaining words (except for proper nouns) begin with lower case. Journal title abbreviations begin with all upper-case letters. I checked the XML data for several journals and found that each of the title listed in this manner. You can see several examples at the bottom of this document:

Fact Sheet: Construction of the National Library of Medicine Title Abbreviations http://www.nlm.nih.gov/pubs/factsheets/constructitle.html Sincerely, Ellen M. L. ...

-Original Message-

Dear NCBI Team, in the xml data of a specific article https://www.ncbi.nlm.nih.gov/pubmed/9858585?dopt=Abstract&report=xml&format=text the journal name is written "Molecular and cellular biology" and the abbreviation is "Mol Cell Biol.". I think the correct journal name should be "Molecular and Cellular Biology" as written on the journal homepage http://mcb.asm.org/content/19/1/612.long ." Saimondo (talk) 17:29, 10 September 2014 (UTC)

https://wiki.riteme.site/wiki/User:Citation_bot/capitalisation_exclusions seems to be being ignored by the latest bot also. AManWithNoPlan (talk) 16:12, 27 September 2015 (UTC)

So, the conclusion is

covert journal names to title case when adding them
Add back in exclusions list support https://wiki.riteme.site/wiki/User:Citation_bot/capitalisation_exclusions

AManWithNoPlan (talk) 20:43, 2 January 2016 (UTC)

I think the solution is to change add_if_new in objects.php like this:

changing

      case "periodical": case "journal":
        if ($this->blank("journal") && $this->blank("periodical") && $this->blank("work")) {
          return $this->add($param, sanitize_string($value));
        }
        return false;

into

      case "periodical": case "journal":
        if ($this->blank("journal") && $this->blank("periodical") && $this->blank("work")) {
          return $this->add($param, format_title_text(sanitize_string($value)));
        }
        return false;

AManWithNoPlan (talk) 20:58, 6 August 2016 (UTC)

New github pull submitted that applies title case in more locations. AManWithNoPlan (talk) 16:55, 7 September 2017 (UTC)

Need to add option $title = mb_convert_case($title, MB_CASE_TITLE, "UTF-8") AManWithNoPlan (talk) 13:22, 10 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:25, 2 October 2017 (UTC)

citing using pmid creates author1 instead of last1

Status: improvement
Reported by: Ihaveacatonmydesk (talk) 21:33, 30 May 2016 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: {{cite journal|pmid=12858711 |year=2003 |author1=Lovallo |first1=D |title=Delusions of success. How optimism undermines executives' decisions |journal=Harvard business review |volume=81 |issue=7 |pages=56–63, 117 |last2=Kahneman |first2=D }}
What should happen: {{cite journal|pmid=12858711 |year=2003 |last1=Lovallo |first1=D |title=Delusions of success. How optimism undermines executives' decisions |journal=Harvard business review |volume=81 |issue=7 |pages=56–63, 117 |last2=Kahneman |first2=D }}
Replication instructions: use a pmid an click the button to autocomplete - also does the same thing when inputting a url into cite book, like {{cite book|url=https://books.google.com/?id=FI7l8O1tlkkC}}
We can't proceed until: Bot operator's feedback on what is feasible

|author1= is an alias of |last1=. This would be a cosmetic fix (in the code) only. – Jonesey95 (talk) 22:55, 31 May 2016 (UTC)

Agreed, but since it's such a simple fix it would be a shame not to do it. Also I actively search for "author" when most of the refs are |lastn=/|firstn= to edit them for consistency, and that creates false positives. Ihaveacatonmydesk (talk) 08:28, 1 June 2016 (UTC)

When splitting an author into last and first, it keeps the original type when setting the last name. Pull request done to switch to last. https://github.com/ms609/citation-bot/pull/169 AManWithNoPlan (talk) 15:14, 25 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:42, 2 October 2017 (UTC)

URL in the website field instead of the URL field (common newbie error)

Status: feature request
Reported by: Kerry (talk) 06:48, 1 March 2017 (UTC)
Type of bug: Potentially Deleterious: Invisible Human-input data is deleted
What happens: the bot is removing the accessdate from citations saying "Removed accessdate with no specified URL"

when the citation does contain a URL but it is in the website field (a common mistake made by newbies, especially those who don't understand the jargon "URL" -- in my experience of doing training in public libraries, many people call these "web addresses" and not "URL")

What should happen: Ideally. If a citation has a URL in the website field and the URL field is empty, move the URL into the correct field and empty the website field. If that's not possible for the bot to do, then don't delete the accessdate, but try and warn in some way. (In a super-ideal world, the editor software would not use the term URL but say "address of web page", but I assume this is out of scope here).
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=George_Christensen_%28politician%29&type=revision&diff=768005628&oldid=767963006
Replication instructions: undo it and run the bot again
We can't proceed until: Agreement on the best solution

The access date that is deleted is not actually shown to humans. Attempt to have bot do this: https://github.com/ms609/citation-bot/pull/172 AManWithNoPlan (talk) 21:37, 25 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:26, 2 October 2017 (UTC)

lowercasing "the" as the first word in a subtitle?

Is it correct for this bot to remove capitalization from the word "the" when it's immediately following a colon as the first word in a subtitle? That's a wordy sentence, and might be confusing, so I'll also ask: is it correct for this bot to do this: https://wiki.riteme.site/w/index.php?title=Initiations_%28Star_Trek%3A_Voyager%29&type=revision&diff=795130102&oldid=795049756 ? — fourthords | =Λ= | 15:11, 12 August 2017 (UTC)

That is a good question. I edited https://wiki.riteme.site/wiki/User:Citation_bot/capitalisation_exclusions to make this Star Trek magazine have a capital The. Generally, a the is not capitalized in the middle of a sentence, but this is a weird case where a colon really is being used more like a period than a colon. AManWithNoPlan (talk) 13:44, 13 August 2017 (UTC)

This is in general true of all words following colons and dashes, not just 'The'. 'A' and "An" are very common, as are many others. The bot should leave the capitalization of all follow-up words alone. Headbomb {t · c · p · b} 14:40, 13 August 2017 (UTC)

The convention I've usually seen is that the word following a colon in a complete English sentence is not capitalized (although I think in earlier styles it might have been) but the word following a colon in the title of a publication is capitalized. For instance the mathematics publication database MathSciNet, which aggressively lowercases even words after the first in titles of books (unlike most other bibliographic sources), nevertheless follows this convention. —David Eppstein (talk) 18:23, 13 August 2017 (UTC)

There is a style out there which will capitalize the first word after a colon even in a full sentence, but that's a rare one; most of my experience has been the same as David's. --Izno (talk) 19:58, 25 August 2017 (UTC)

This might be working in the development version on github. Not yet deployed to wiki land. AManWithNoPlan (talk) 21:37, 12 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:33, 2 October 2017 (UTC)

Creates invalid ISO date

Status: new bug
Reported by: Keith D (talk) 21:06, 18 August 2017 (UTC)
Type of bug: Deleterious: Human-input data is deleted or articles are otherwise significantly affected. Many bot edits require undoing.
What happens: Changes hyphens to em-dashes in ISO dates (I had just corrected the date earlier today)
Relevant diffs/links: https://wiki.riteme.site/w/index.php?title=Ye_Wenling&diff=796142445&oldid=796141424
We can't proceed until: Bot operator's feedback on what is feasible
Requested action from maintainer: Not change two dashed dates

This looks like a GIGO error. "2007-08-01" should not be in |year=. A format like that should be in |date=. The bot could perhaps ignore this incorrect format, leaving it for a human editor to fix. In this case, the bot did human editors a favor by highlighting an erroneous parameter value. – Jonesey95 (talk) 22:12, 18 August 2017 (UTC)

I guess we agree on this AManWithNoPlan (talk) 19:24, 5 September 2017 (UTC)

Have to disagree with this conclusion, something should be done in the code to stop this happening even when there is incorrect usage of fields. Keith D (talk) 21:05, 5 September 2017 (UTC)

Garbage in; Garbage out. I will write a patch to detect more than done dash. That why the original garbage satay put AManWithNoPlan (talk) 00:46, 6 September 2017 (UTC)

Need to add this && (substr_count($text, '-') < 2 || substr_count($text, '--') != 0 ) (this means that if more than one dash is found, then do not change, unless there are dashes next to each other). Probably change |year= to |date=. AManWithNoPlan (talk) 16:20, 13 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:36, 2 October 2017 (UTC)

Bot broke a URL

This edit altered an dash to an ndash in a URL within a page= parameter. You need to check that if the page or pages parameter includes an open square bracket nothing is changed before a space or a close square bracket. -- PBS (talk) 16:29, 27 August 2017 (UTC)

Extended content

GIGO. That is a misuse of the template. I will fix it. There is no way for the bot to deal with all the ways that templates can be used wrong AManWithNoPlan (talk) 16:37, 27 August 2017 (UTC)

GIGO "garbage in garbage out" do you meant "Rubbish in rubbish out?" It is no rubbish in to use a url link for a page number.

It is not a misuse of the template is is a misuse of the bot. fix please the bot. I have only had a limited time to sample the bots output. Here are some other problems:

14:07, 27 August 2017‎ broke url
Revision as of 13:07, 27 August 2017 broke url

This is something generated by the goggle book tool. While it is not a bug to change dash to ndash the correct thing to do if the parameter is page= is to remove the trailing dash not change it to mdash

16:13, 27 August 2017

These should probably not have been touched:

16:03, 27 August 2017 questionable
14:32, 27 August 2017 questionable

--PBS (talk) 22:17, 27 August 2017 (UTC)

"There is no way for the bot to deal with all the ways that templates can be used wrong" The template is no being used "wrong" do you need help fixeing the bot? -- PBS (talk) 22:20, 27 August 2017 (UTC)

BTW I am very consented with the string of edits you made to Murder Act 1751 after I raised problem with the bot. Please explain -- PBS (talk) 22:40, 27 August 2017 (UTC)

The documentation for the parallel series of templates {{sfn}} etc explicitly recommends using a url in its page parameter: see Template:Sfnp#Adding a URL for the page or location. So characterizing this usage as "garbage" seems overly harsh. And Citation bot should clearly detect page parameter formats that it doesn't understand and not break them. I think this is indeed a bug. —David Eppstein (talk) 22:52, 27 August 2017 (UTC)

This is definitely a bug. The bot is altering a URL that it shouldn't be touching. – Jonesey95 (talk) 22:57, 27 August 2017 (UTC)

{{citation}} do not want url's in page numbers. They have an explicit URL parameter for that. {{sfn}} does not have that. I do not see how the bot could deal with people putting stuff in the wrong places. AManWithNoPlan (talk) 00:32, 28 August 2017 (UTC)

^{[citation needed]}.(edit conflict)I know that {{citation}} is cs2, but cs1|2 share Module:Citation/CS1. A lot of the documentation at Help:Citation Style 1 applies to cs2. Particularly, and pertinent to this discussion: this. There we have an example that shows |page= externally linked with a url.

—Trappist the monk (talk) 01:07, 28 August 2017 (UTC)

Interesting. That documentation is poorly organized, but clear. It also says that you should use a template for dashes that you do not wan changed. AManWithNoPlan (talk) 01:20, 28 August 2017 (UTC)

of course unless some one is willing to test out change by change new code, there is no reason for anyone to fix this "bug" AManWithNoPlan (talk) 01:22, 28 August 2017 (UTC)

it seems to be discouraged https://wiki.riteme.site/wiki/Help_talk:Citation_Style_1/Archive_2 AManWithNoPlan (talk) 01:30, 28 August 2017 (UTC)

https://wiki.riteme.site/w/index.php?title=Help:Citation_Style_1&diff=next&oldid=774956610

A lot has happened since that discussion from May 2013. Editor Redrose64's point about corrupted COinS metadata for the &rft.pages keyword has been addressed long since. The original GoingBatty template implementation now produces:

'"`UNIQ--templatestyles-0000005A-QINU`"'<cite id="CITEREFde_Lint2007" class="citation book cs1">[[Charles de Lint|de Lint, Charles]] (2007). ''[[Widdershins (novel)|Widdershins]]''. Macmillan. [http://books.google.com/books?id=Lze6oI8YnJ8C&pg=PA287&lpg=PA287&ots=GD39FFwqva&sig=UX21aqwJXsVpwJR4muJjRaU_sq8&hl=en&sa=X&ei=2IymUYm8FKiAiwL70IHYDw&ved=0CDAQ6AEwBA p. 287]. [[ISBN (identifier)|ISBN]]&nbsp;[[Special:BookSources/0765312859|<bdi>0765312859</bdi>]].</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Widdershins&rft.pages=p.+287&rft.pub=Macmillan&rft.date=2007&rft.isbn=0765312859&rft.aulast=de+Lint&rft.aufirst=Charles&rfr_id=info%3Asid%2Fwiki.riteme.site%3AUser+talk%3ACitation+bot%2FArchive+6" class="Z3988"></span>

in which you will find:

&rft.pages=p.+287

which is slightly off because page numbers should be using |page= or |pages=, whichever is appropriate. Use of the correct parameter will render the metadata as:

&rft.pages=287

And, please don't remove content from other editor's posts. You made a claim that {{citation}} do not want url's in page numbers. I wanted to know then, and still want to know now, what it is that you believe supports that claim.

—Trappist the monk (talk) 09:56, 28 August 2017 (UTC)

Added in these two edits in 2011. It would be hard to suggest that's not supported by at least a few people simply due to its age in the documentation. I would guess that phab:T151301 can/will put an end to the practice, since if you're only citing the work once on one page, you can link the page directly in the URL field; and if you're citing it multiple times, you'd rather use the official extension mechanism. --Izno (talk) 03:41, 28 August 2017 (UTC)

AManWithNoPlan, your claim that the |url= parameter makes links in pages unnecessary is, simply, wrong. A link in the url parameter will show the link on the title of the work, as a link to the whole work. A link in the page parameter will put the link on the page number, making clear that it is a link to that specific page. There is no way to achieve that effect with any of the url parameters. —David Eppstein (talk) 08:59, 28 August 2017 (UTC)

It looks like standard for the citation templates has changed (again -- the documentation has only suggested this for less than half a year). I will concede that now it is okay to have url's in the page number area. The templates really should have a page-url option for that, but until they do, this seems okay. This discussion is moot until we get the latest bot git source debugged and amended. Fixing this in the source should be be easy: If page_number contains either "[" or "http" then do not change. AManWithNoPlan (talk) 15:06, 28 August 2017 (UTC)

Adding urls to page parameters has been done for years, whether or not it has been documented. -- PBS (talk) 19:59, 29 August 2017 (UTC)

Enough discussion of this good/evil practice. The end result is that the bot needs updated. The existing code in Template.php is:


         if (!preg_match("~^[A-Za-z ]+\-~", $p->val) && mb_ereg(to_en_dash, $p->val)) {
           $this->mod_dashes = TRUE;
           echo ( "\n   ~ Upgrading to en-dash in" . htmlspecialchars($p->param) . tag());
           $p->val = mb_ereg_replace(to_en_dash, en_dash, $p->val);
         }

Should be:


         if (!preg_match("~^[A-Za-z ]+\-~", $p->val) && mb_ereg(to_en_dash, $p->val)  && !preg_match("http", $p->val)) {
           $this->mod_dashes = TRUE;
           echo ( "\n   ~ Upgrading to en-dash in" . htmlspecialchars($p->param) . tag());
           $p->val = mb_ereg_replace(to_en_dash, en_dash, $p->val);
         }

I will have a git pull submitted. AManWithNoPlan (talk) 20:38, 5 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:40, 2 October 2017 (UTC)

Linefeeds

Arxiv often has linefeeds in titles and journal names. Need to strip them out and probably replace with a space. AManWithNoPlan (talk) 04:03, 10 September 2017 (UTC)

Something like find '\s+' replace ' ' should do the trick. Headbomb {t · c · p · b} 14:53, 12 September 2017 (UTC)

I have added code to github to replace "\n\r","\r\n","\r","\n" each with a single space (all four are valid depending upon your OS). Once the dev version is updated, I will test it out. AManWithNoPlan (talk) 15:12, 12 September 2017 (UTC)

@AManWithNoPlan: it should strip tabs too. Headbomb {t · c · p · b} 15:38, 12 September 2017 (UTC)

@Headbomb: $v = preg_replace('/(\s\s+|\t|\n)/', ' ', $v); I think this grabs all of them and all spaces and cuts them down to one space. AManWithNoPlan (talk) 16:10, 12 September 2017 (UTC)

Wouldn't \s+ cover all of that though? Headbomb {t · c · p · b} 16:43, 12 September 2017 (UTC)

There you go being right. AManWithNoPlan (talk) 16:52, 12 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:39, 2 October 2017 (UTC)

First parameter gets deleted

Status: new bug
Reported by: Martin (Smith609 – Talk) 12:49, 15 September 2017 (UTC)
Type of bug: Deleterious
What happens: Unnamed parameter code deletes first element of citation templates
Relevant diffs/links: Triggered using Citationm buttoin: https://wiki.riteme.site/w/index.php?title=Xiaoheiqingella&type=revision&diff=800750038&oldid=800749961

Triggered using wmftools link: https://wiki.riteme.site/w/index.php?title=Xiaoheiqingella&type=revision&diff=800750114&oldid=800750078

Replication instructions: See edits
We can't proceed until: Agreement on the best solution

{{Cite journal |STUFF | pp. 1–5}} lead to this: {{Cite journal|pages=1–5}}

protected function correct_param_spelling() or more likely use_unnamed_params() in Template.php is to blame.

This {{Cite journal|pp. 1–5}} becomes {{Cite journa}} because the bot deletes the first entry. AManWithNoPlan (talk) 19:30, 19 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:39, 2 October 2017 (UTC)

bot adds |year= when |date= already holds valid date

Status: new bug
Reported by: Trappist the monk (talk) 10:32, 27 September 2017 (UTC)
Type of bug: Inconvenience: Humans must occasionally make immediate edits to clean up after the bot
What happens: bot added |year=2002 even though |date=2002 already present in the citation; this adds the page to Category:CS1 maint: Date and year
What should happen: nothing; the citation was fine without |year=2002
Relevant diffs/links: look for bonehead mistakes
Replication instructions: don't know, I wasn't the bot driver; history claims that the bot made this edit autonomously
We can't proceed until: Code to be fixed

The article title is funny (I thought you were being funny).. {{cite journal|date=2002|doi=10.1635/0097-3157(2002)152[0215:HPOVBM]2.0.CO;2}} is enough to get the bug. AManWithNoPlan (talk) 13:57, 27 September 2017 (UTC)

It is the SICI data that was used. https://github.com/ms609/citation-bot/pull/176 AManWithNoPlan (talk) 01:53, 29 September 2017 (UTC)

{{resolved}} in Dev AManWithNoPlan (talk) 18:37, 2 October 2017 (UTC)

Update jstor links

Old links include SICI, they redirect to stable jstor https://www.jstor.org/sici?sici=0003-0279(196101%2F03)81%3A1%3C43%3AWLIMP%3E2.0.CO%3B2-9 Should figure that out and update. AManWithNoPlan (talk) 04:08, 30 September 2017 (UTC) https://github.com/ms609/citation-bot/pull/201 and test later with this:

   public function testJstorSICI() {
       $text = '{{Cite journal|url=https://www.jstor.org/sici?sici=0003-0279(196101%2F03)81%3A1%3C43%3AWLIMP%3E2.0.CO%3B2-9}}';
       $expanded = $this->process_citation($text);
       $this-assertEquals('594900',$expanded->get('jstor'));
   }

AManWithNoPlan (talk) 04:19, 2 October 2017 (UTC)

{{resolved}} in GitHub. AManWithNoPlan (talk) 02:14, 3 October 2017 (UTC)

Bot does not handle aliases

Edits citations inside of nowiki tags

Duplicating jstor

Google books data is sometimes rubbish

Erroneously reports DOI as broken

Bot created arXiv= parameter error

Link at top of results page leads to error

Error converting url to arxiv parameter

JSTOR plant link mistaken for journal

When bibcodes ends with a dot, it leaves the dot out

Comments cause trouble

Google data is not always right, and the bot is not telepathic

Bot generated invalid cite data "# # # comment"

Incorrect DOI removal

Authors must be people, not companies

issue vs. volume confusion for journals with no volumes

Unknown is not a journal name

Special characters in data need escaped

Inline "Citations" button does not work as well as calling the bot through link

Adding invalid field (|DUPLICATE_work)

Standardize and Customize Journal Capitalization

citing using pmid creates author1 instead of last1

URL in the website field instead of the URL field (common newbie error)

lowercasing "the" as the first word in a subtitle?

Creates invalid ISO date

Bot broke a URL

Linefeeds

First parameter gets deleted

bot adds |year= when |date= already holds valid date

Update jstor links

`Unknown` is not a journal name