Wikipedia:Contributor copyright investigations/Aldebaran69

This page has been removed from search engines' indexes.

Instructions

edit

All contributors with no history of copyright problems are welcome to contribute to clean up. Contributors who are the subject of a contributor copyright investigation are among contributors with a history of copyright problems and so are not welcome to directly evaluate their own or others' copyright violations in CCIs. They are welcome to assist with rewriting any problems identified.

If contributors have been shown to have a history of extensive copyright violation, it may be assumed without further evidence that all of their major contributions are copyright violations, and they may be removed indiscriminately in accordance with Wikipedia:Copyright violations. Contributors who are the subject of a contributor copyright investigation are among contributors who have been shown to have a history of extensive copyright violation and so all of the below listed contributions may be removed indiscriminately. However, to avoid collateral damage, efforts should be made when possible to verify infringement before removal.

When every section is completed, please alter the listing for this CCI at Wikipedia:CCI#Open_investigations to include the tag "completed=yes". This will alert a clerk that the listing needs to be archived.

  • {{CCI-open|Contributor name|Day Month Year|completed=yes}}

Text

edit
  • Examine the article or the diffs linked below.
  • If the contributor has added creative content, either evaluate it carefully for copyright concerns or remove it.
  • Evaluating for copyright concerns may include checking the listed sources, spot-checking using google, google books and other search engines and looking for major differences in writing style. The background may give some indication of the kinds of copyright concerns that have been previously detected. For older text, mirrors of Wikipedia content may make determining which came first difficult. It may be helpful to look for significant changes to the text after it was entered. Searching for the earlier form of text can help eliminate later mirrors. If you cannot determine which came first, text should be removed presumptively, since there is an established history of copying with the editor in question.
  • If you remove text presumptively, place {{subst:CCI|name=Contributor name}} on the article's talk page.
  • If you specifically locate infringement and remove it (or revert to a previous clean version), place {{subst:cclean}} on the article's talk page. The url parameter may be optionally used to indicate source.
  • If there is insufficient creative content on the page for it to survive the removal of the text or it is impossible to extricate from subsequent improvements, replace it with {{subst:copyvio}}, linking to the investigation subpage in the url parameter. List the article as instructed at the copyright problems board, but you do not need to notify the contributor. Your note on the CCI investigation page serves that purpose.
  • To tag an article created by the contributor for presumptive deletion, place {{subst:copyvio|url=see talk}} on the article's face and {{subst:CCId|name=Contributor name}} on the article's talk page. List the article as instructed at the copyright problems board, but you do not need to notify the contributor.
  • After examining an article:
  • replace the diffs after the colon on the listing with indication of whether a problem was found (add {{y}}) or not (add {{n}}). If the article is blanked and may be deleted, please indicate as much after the {{y}}. The {{?}} template may be used for articles where you were unable to determine whether or not a violation occurred, but are prepared to remove the article from consideration – either because the material is no longer present in the article, or it is adequately paraphrased so as to no longer be a violation (please specify which).
  • Follow with your username and the time to indicate to others that the article has been evaluated and appropriately addressed. This is automatically generated by four tildes (~~~~)
  • If a section is complete, consider collapsing it by placing {{collapse top}} and {{collapse bottom}} beneath the section header and after the final listing.

Background

edit

user:Aldebaran69 complained on another user's page that they were being harassed. They stated

Hi Callanecc, I have a questions: who are the steps to made a complain about some users who believed that translation from featured articles from other language Wikipedia articles to English Wikipedia was always wrong?? (diff at 02:33, 2 November 2016)

This refers to edits to Maria Anna of Spain which was copied from ru:Мария Анна Испанская which at the time had no comments added to the history of the article by user:Aldebaran69. This has retrospectively been fixed with proper attribution.

From Aldebaran69's talk page:

I translated from the Russian article who seems to be a good article according to Wikipedia standards. If you think that I'm doing a bad job or I'm not qualified to continue to do it, please be free to reverese the editions I made, or, in the case you don't wanted, I'm gladly do it. Aldebaran69 (talk) 01:07, 31 October 2016 (UTC) (diff)[reply]

This referred to the page Margaret Theresa of Spain which was translated and copied from ru:Маргарита Тереза Испанская without any edit history comments. Although after the chat on the talk page this has been fixed with a retrospective proper attribution.

Aldebaran69 has since stated:

I didn't known that the translation from another wikipedia article to English needs an atribution: I made for the last 8 years without any complain until now (for example, from Polish to English wikipedia); concerning about your thread to take administrative action don't worry, i won't translated any other article for the sake of copyright violation -- you can be in peace now. Thanks Aldebaran69 (talk) 00:27, 3 November 2016 (UTC)(diff)[reply]

The evidence of these two pages and the editor's edit history over the last few days since the copyright violations were explained to the editor, suggests that this is an editor who would be willing to help fix the copyright violation. But as this is a systemic problem stretching over about 8 years, a "contributor copyright investigation" of the scale of the problem would help bring a formality and ginger to the clean-up of past mistakes. -- PBS (talk) 21:57, 4 November 2016 (UTC) PBS (talk) 21:57, 4 November 2016 (UTC)[reply]

This appears to have been an innocent misunderstanding of policy, but should be cleaned up nonetheless. I will contact the user involved to see if he can assist here. Calliopejen1 (talk) 00:03, 23 May 2017 (UTC)[reply]

Contribution survey

edit

Articles 1 through 20

edit

Articles 21 through 40

edit

Articles 41 through 60

edit

Articles 61 through 80

edit

Articles 81 through 100

edit

Articles 101 through 120

edit

Articles 121 through 140

edit

Articles 141 through 160

edit

Articles 161 through 180

edit

Articles 181 through 200

edit

Articles 201 through 220

edit

Articles 221 through 240

edit

Articles 241 through 260

edit

Articles 261 through 280

edit

Articles 281 through 300

edit

Articles 301 through 320

edit

Articles 321 through 340

edit

Articles 341 through 360

edit

Articles 361 through 380

edit

Articles 381 through 400

edit

Articles 401 through 420

edit

Articles 421 through 440

edit

Articles 441 through 460

edit

Articles 461 through 480

edit

Articles 481 through 500

edit

Articles 501 through 520

edit

Articles 521 through 540

edit

Articles 541 through 560

edit

Articles 561 through 580

edit

Articles 581 through 600

edit

Articles 601 through 620

edit

Articles 621 through 640

edit

Articles 641 through 660

edit

Articles 661 through 680

edit

Articles 681 through 700

edit

Articles 701 through 720

edit

Articles 721 through 740

edit

Articles 741 through 760

edit

Articles 761 through 780

edit

Articles 781 through 800

edit

Articles 801 through 811

edit

This report generated by Contribution Surveyor at 2017-05-23T00:00:32+00:00 in 1.54 sec.