October 2023 | 2 |
November 2023 | 53 |
December 2023 | 92 |
January 2024 | 50 |
February 2024 | 89 |
March 2024 | 253 |
April 2024 | 217 |
May 2024 | 269 |
June 2024 | 217 |
July 2024 | 314 |
August 2024 | 362 |
September 2024 | 6 |
Undated articles | 0 |
![]() | This is a WikiProject, a collaboration area and open group of editors dedicated to organizing an internal process on Wikipedia. New participants are welcome; please feel free to participate!
|
October 2023 | 2 |
November 2023 | 53 |
December 2023 | 92 |
January 2024 | 50 |
February 2024 | 89 |
March 2024 | 253 |
April 2024 | 217 |
May 2024 | 269 |
June 2024 | 217 |
July 2024 | 314 |
August 2024 | 362 |
September 2024 | 6 |
Undated articles | 0 |
Articles to be merged after an Articles for deletion discussion | |
---|---|
All articles | 211 |
Several Wikipedians have formed this collaboration resource and group dedicated to improving the merging process. This page and its subpages contain their suggestions and various resources; it is hoped that this project will help to focus the efforts of other Wikipedians interested in the merge process. If you would like to help, please join the project, inquire on the talk page and see the to-do list below.
The main project focus at this time is reducing the articles to be merged backlog!
|
A merge is a process by which the content of two pages are united on one page for one or more of the following reasons:
A copy paste merge creates "attribution dependency". To license the content from the originating article you must, at minimum, provide a direct link to the original article in the edit summary of the page where content is being placed. You should also place the {{Copied}} tag on the originating article as well as the target article.
Merging should be avoided if the articles are sufficiently distinct to stand on their own and the resulting article will be too long or "clunky"; the separate topics could be expanded into longer standalone (but cross-linked) articles; the topics are discrete subjects and deserve their own articles even though they may be short.
If you need direction for making a new merge proposal see Wikipedia:Proposed mergers. On Wikipedia, articles may be boldly merged without any proposal taking place, though it is recommended where the merge is expected to be controversial. If you boldly merge an article and it is reverted, this should be considered part of the BOLD, revert, discuss cycle and not undone until discussion takes place—do not edit war.
A merge is listed once a tag is placed on the article, such as {{Merge}} or {{Merge to}}. Removing the tag delists the article. Never remove a proposed merge tag unless you are intending to delist the article and only do so when all issues have been addressed. If the proposer of the merge did not start a discussion for the merge, and it is not obvious why the articles should be merged, it is acceptable to remove the tags. If the reason for the merge is obvious, you can either merge the articles boldly, or start a new discussion.
Editors should always close a proposal uncontroversially. Complex cases can be referred to the project's talk page. Merging an article where there was a consensus-based decision to do so at an AfD discussion that has been closed by an administrator is not controversial, and may be undertaken with no further discussion or closing procedure.
If there has been no discussion generated after a reasonable amount of time then the merge proposal is stale. If there are no active AfD, ANI, or other dispute resolution discussions involving any of the affected pages (see below), stale merge proposals with no discussion after six months should be immediately delisted if any of the following apply:
If the articles listed for merge meet the above standards then you may simply remove the tags as a stale merge/old proposal with no consensus. No merging takes place. Otherwise, you may participate in the discussion if you have an opinion on the merits of the proposed merge, or consider closing the discussion according to merge discussion closing procedures.
To carry out the merge, be sure and follow the steps as laid out by Wikipedia:Merging#How to merge.
Editors should not merge content during an AFD. AfD participants should not work "around" consensus by beginning a merge process on their own, before discussion. While preservation of content is a good consideration, copying may be contentious and may create additional steps and administrative work if undoing any copying is necessary. Such a merge also causes an attribution dependency breakage between articles that may require the merging of article history that would be lost if the source page is deleted. AFD participants may offer proposals and negotiate with the other participants during the discussion. If needed, editors may ask the closing admin how to rescue the content or what additional steps that need to be taken.
Any editor may add contents and references if the prose used is completely original. In this manner the merged content is not merely copied and pasted but all original content makes use of the available references (see Wikipedia:EDITATAFD). Rather than merging, the content can be rewritten. In this case, there is no attribution problems as the content is new. However, one should exercise extreme caution BEFORE undertaking such a controversial merge. While it is not strictly prohibited, Wikipedia:WikiProject Merge recommends that all editors refrain from such tasks in the spirit of collaboration. Unless there is a strong case for the merge specified by deletion policy it is preferred that editors wait until the discussion period is complete.
From Help:Merging
If there is clear agreement with the proposal by consensus, or if there is silence, after the debate has been open for at least two weeks, proceed with the merge. Before merging, it is recommended that you refer to this, which applies to merge targets as well as redirect targets.
To provide clarity that the merge discussion is over and that a consensus has been reached, it may be important to close and then archive the proposal discussion. To close a merge proposal discussion, indicate the outcome at the top. If the merge is particularly controversial, one may take the optional step of requesting closure by an uninvolved administrator at Wikipedia:Administrators' noticeboard/Requests for closure.
To archive a merge proposal discussion, a {{Discussion top}} template is generally placed between the header and the top of the discussion and a {{Discussion bottom}} template will need to be placed at the bottom of the discussion.
Here is an example of how to archive a merge proposal discussion:
== Header == {{Discussion top|1=The result was '''merge''' into DESTINATION PAGE. -- ~~~~}} Hi, I would like to discuss... {{Discussion bottom}}
You can also place the {{oldmergefull}} template at the top of the talk pages of the articles proposed to be merged.
AFD consensus to merge/redirects have been Admin closed and do not reguire further closing procedure. These may be merged and redirected with no further tasks required or associated with the merge.
From Help:Merging
There are two basic types of merge; which to use depends on how much content of the source page you want to keep:
Also remember that almost all article pages have a talk page. To avoid losing quick access to that historical discussion, a link to the source article's talk-page should be placed at the top of the destination article's talk-page, such as:
Article merged: See old talk-page [[talk:PAGENAME|here]]
or use Template:Copied:
{{Copied|from=source|from_oldid=source|to=destination|diff=|date=}}
merge content from [[SOURCEPAGE]]
(This step is required in order to conform with Wikipedia's licensing requirements. Do not omit it nor omit the page name.)#REDIRECT [[DESTINATIONPAGE]] {{R from merge}}
, save the source page with an edit summary noting merge content to [[DESTINATIONPAGE]]
From Help:Merging
![]() | Full content merge in a nutshell: A full merge copies all the text from the source page. |
#REDIRECT [[PAGENAME]] {{R from merge}}
, note the merge (including the page name) in the edit summary, and save the page.{{Copied|from=source|to=destination|diff=permanent diff}}
onto the talk pages of both articles. This not only helps clarify attribution at the destination, but helps prevent inadvertent later deletion of the source history. This step is optional but recommended.Performing a merge in this manner is beneficial when you want to include all the content from both articles in the article history of the final article.
From Help:Merging
![]() | Selective merge in a nutshell: A selective merge transfers only some of the text from the source page into the target article. |
#REDIRECT [[PAGENAME]] {{R from merge}}
.
{{Copied|from=source|to=destination|diff=permanent diff}}
onto the talk pages of both articles. This not only helps clarify attribution at the destination, but helps prevent inadvertent later deletion of the source history. This step is optional but recommended.Performing a merge in this manner is beneficial when the source document includes a great deal of material that is not needed in the final article.
Once the content is merged do not forget to blank the originating page and add:
#REDIRECT [[PAGENAME]] {{R from merge}}
At minimum, attribution must be provided in the edit summary of the page into which content is placed. This step is required in order to conform with Wikipedia's licensing requirements. Do not omit it nor omit the page name. It is important to remember, once a merge has been made and the redirect set or even when a redirect is not set in place, to add this template on both the target and originating article talkpage and fill out completely:
{{Copied |from= |from_oldid= |to= |diff= }}
See the Template:Copied documentation for instructions.
© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search