| Revision as of 16:45, 8 July 2006 edit147.226.157.243 (talk)No edit summary← Previous edit |
Latest revision as of 17:08, 1 May 2017 edit undoRich Farmbrough (talk | contribs)Edit filter managers, Autopatrolled, Extended confirmed users, File movers, Pending changes reviewers, Rollbackers, Template editors1,725,269 edits Update deprecated redirect template. |
| (403 intermediate revisions by more than 100 users not shown) |
| Line 1: |
Line 1: |
|
|
#Redirect ] |
|
{{Misplaced Pages subcat guideline|content|{{PAGENAME}}|]}} |
|
|
|
|
|
|
|
{{Redirect category shell|1= |
|
'''Merging and moving''' are two fundamental aspects of how articles are developed and reformed on Misplaced Pages. |
|
|
|
{{Redirect from merge}} |
|
A "merger" is a manual (non-automated) process by which two existing but similar (or redundant) pages are united under the same name. |
|
|
|
{{Redirect to project namespace}} |
|
A "move" is equivalent to "renaming" a page — i.e. giving it a new title. |
|
|
|
}} |
|
|
|
|
==Merging== |
|
|
There are several good reasons to merge a page: |
|
|
*There are two or more pages on exactly the same subject. |
|
|
*There are two or more pages on related subjects that have a large overlap. ]; there does not need to be a separate entry for every concept in the universe. For example, "Flammable" and "Non-flammable" can both be explained in an article on ]. |
|
|
*If a page is very short and cannot or should not be expanded terribly much, it often makes sense to merge it with a page on a broader topic. |
|
|
*If a short article requires the background material or context from a broader article in order for readers to understand it. |
|
|
|
|
|
Merging should always leave a ] or, in some cases, a ] in place. This is often needed to allow proper attribution through the edit history for the page the merged text came from. Even if it seems rather pointless or obscure, leave it in place. Superfluous redirects do not harm anything, and are sometimes helpful. Other websites may have made links to the old page title, so we will want to redirect incoming visitors to the merged page. We do not want people accidentally creating a new page under the old title, not knowing that the merged page exists. Redirects also show up in search results, helping people who might be looking under the "wrong" title to find the page that they are looking for. |
|
|
|
|
|
You may find that some or all of the information to be merged is already in the destination page. That is fine; you can feel free to delete the redundant information and only add the new stuff. If there is no information to be added to the destination page, you can note in your edit summary on the source page (as you are turning it into a redirect) that there was nothing to be merged (or that the source page was entirely redundant with the destination). |
|
|
|
|
|
===How to merge pages=== |
|
|
Merging is something any editor can do, and if you are sure that something should be merged, you can be ''']''' and do so. If the merge is controversial however, you may find your merge reverted, and as with all other edits, ] should be avoided. |
|
|
|
|
|
If you are uncertain of the merger's appropriateness, you should '''propose''' it on the affected pages. After sufficient time has elapsed to generate consensus or silence (at least 5 days), you may '''perform''' the merger or request that someone else do so. |
|
|
|
|
|
====Proposing a merger==== |
|
|
To propose a merger of two or more pages, place the tag {{tlp|merge|OTHER PAGE}} at the top of each page. It should appear like this: |
|
|
|
|
|
<div class="messagebox merge"><!--PNG images containing transparencies do not display properly for some users. Please consider this fact before replacing the already tiny GIF file.-->] It has been suggested that this article or section be ] with '']''. (])</div> |
|
|
|
|
|
If you know which page should remain, use {{tlp|mergefrom|SOURCE PAGE}} on that page, and {{tlp|mergeto|DESTINATION PAGE}} on each of the pages that should be merged into and redirected to the destination page. Applying these templates relieves the merging editor from having to decide which way to merge, and causes both/all "Discuss" links to lead to the talk page of the destination page (instead of each page linking to its own talk page). These templates will appear as: |
|
|
|
|
|
<div class="messagebox merge">] It has been suggested that '']'' be ] into this article or section. (])</div> |
|
|
|
|
|
and |
|
|
|
|
|
<div class="messagebox merge">] It has been suggested that this article or section be ] into '']''. (])</div> |
|
|
|
|
|
If you are proposing that many pages be merged into one page, it is better to use a single template on the destination page rather than one for each source page. The above template will not work correctly unless modified, so use {{tlp|multiplemergefrom|<nowiki>], ], ], etc</nowiki>}} to generate the following: |
|
|
|
|
|
<div class="messagebox merge"><!--PNG images containing transparencies do not display properly for some users. Please consider this fact before replacing the already tiny GIF file.-->] It has been suggested that ''], ], ], etc'' be ] into this article or section. (])</div> |
|
|
|
|
|
=====Caveats===== |
|
|
*If you are unable to merge the pages, or you believe that the merger may be controversial, you might want to add a listing to ]. |
|
|
*When proposing a merger of pages within "Misplaced Pages" namespace (any pages that begin with the "Misplaced Pages:" prefix), do '''not''' include this prefix in the parameter. |
|
|
*Due to technical limitations, the above tags are incompatible with cross-namespace mergers (mergers between pages from both the article and Misplaced Pages namespaces). Such instances are rare, and should be handled via manual ] and editing. |
|
|
*Do '''not''' use the above tags to propose a ''category'' merger. This should be requested at ], which uses a separate {{tl|cfm}} template. |
|
|
|
|
|
====Performing the merger==== |
|
|
# Open the source and destination pages in two separate windows/tabs. |
|
|
# Cut/paste the source page into the destination page. |
|
|
# Add <code><nowiki>#REDIRECT ]</nowiki></code> to the source page. |
|
|
# Be sure to remove the 'mergefrom' tag from the destination page before previewing |
|
|
# Preview and edit the destination page until it looks good and consistent. |
|
|
# Save both, and note the merger (including the page names) in the edit summaries. |
|
|
# Check ] on the destination page for ]. |
|
|
#* Double-redirects will fail to link, and must be renamed to redirect to the current page name. |
|
|
|
|
|
=====Alternative version===== |
|
|
Simply dumping the text from one page onto another ''is'' progress, because it puts all of the information on the same topic on the same page. This, however, seldom results in a smooth-flowing article. Fixing that may require a great deal of time and rewriting. If you can do that, terrific! Future readers will greatly benefit from your contribution. If you do not have the time or expertise to do so, please tag the article for attention; select a template from ], such as {{tlp|cleanup-date|{{CURRENTMONTHNAME}} {{CURRENTYEAR}}}} (using the current month and year as the parameter). |
|
|
|
|
|
==Renaming / Moving== |
|
|
:''See ] and ]. |
|
|
On Misplaced Pages, usually anyone logged in can rename a page from its current name to a new one. This is also called "moving" because the effect is as if the page has been moved. A redirect is automatically created at its old name so that links still work. After a move to correct a spelling mistake, you may want to list the resultant redirect for deletion at ]. This, however, isn't necessary, and ideally should be done only for redirects which meet the deletion criteria as outlined at Redirects for deletion. If a redirect is a plausible or common misspelling, it is very likely to be kept. |
|
|
*'''Misspelled''' – The most common reason is that a page name is misspelled or incorrectly capitalized. Please fix any and all of these as you see them. |
|
|
*''']''' – Terms used in a title express a bias or POV. NPOV policy requires that titles be given "neutral" titles — using the most general and objective terms. |
|
|
|
|
|
Sometimes, you may feel that a page is wrongly named for another reason. For example, "Napoleon" is more properly known as "Napoleon I of France." However, this is a situation in which a redirect would be appropriate. Most people would not search for ], but rather for ]. |
|
|
|
|
|
===Cross-namespace moves=== |
|
|
The move feature is capable of moving pages in any ], and even of moving pages from one namespace to another. Cross-namespace moving is useful when a page is accidentally created in the wrong namespace; for instance, moving ] to ], or moving ] to ]. In some cases, new users may create articles on themselves that they intend to serve as their ], in which case such an article may be ]. |
|
|
|
|
|
Generally speaking, other types of cross-namespace moves will be controversial and worth discussing with other editors. ] is the proper place for this. However, when proposing to move what appears to be an article out of the main namespace, it is strongly recommended that some form of ] should be used, preferably ], as ] and ] don't build consensus. This is because the redirect that is created by such a move is subject to speedy deletion, which would effectively cause the article to be deleted from the main encyclopedia. |
|
|
|
|
|
===How to rename a page=== |
|
|
''Note, you must be ] to do this'' |
|
|
# Go to the page that you wish to rename. |
|
|
# Click the tab labeled "move." |
|
|
# Type the new desired title, add a reason, and click "Move page." |
|
|
#* The old title will redirect to the new title. |
|
|
#* The old edit history will be moved to the new title. |
|
|
# Check for redirects. |
|
|
#* Double-redirects will fail to link, and must be renamed to redirect to the current page name. |
|
|
*'''''Do not move or rename a page by copying/pasting its content,''''' because doing so destroys the ]. (The ] requires acknowledgement of all contributors, and editors continue to hold copyright on their contributions unless they specifically give up this right. Hence it is required that edit histories be preserved for all major contributions until the normal copyright expires.) If you come across a cut-and-paste move that should be fixed by merging the page histories, please follow the instructions ] to have an administrator repair it. |
|
|
|
|
|
If you cannot rename a page, or you think that the renaming may be controversial, please go to ] and list it there. |
|
|
|
|
|
The most common reason for failure is that there is already an article at the location to which you're trying to move the article. This is especially likely to happen if there is a history of moves from one name to another. This can be dealt with by an administrator after discussion at ]. |
|
|
|
|
|
If the destination does exist, but it only contains a redirect without any history, the move will still work — the designers of the MediaWiki software recognised this as a special case in which no information will be lost if a move is performed. |
|
|
|
|
|
== See also == |
|
|
* ] |
|
|
* ] |
|
|
* ] |
|
|
* ] |
|
|
|
|
|
] |
|
|
] |
|
|
] |
|
|
] |
|
|
] |
|
|
] |
|
|
] |
|
|
] |
|