Revision as of 16:43, 9 July 2006 edit"D" (talk | contribs)676 edits →See also← Previous edit | Revision as of 02:34, 12 July 2006 edit undo130.76.32.16 (talk) →Performing the merger: clarifyingNext edit → | ||
Line 46: | Line 46: | ||
====Performing the merger==== | ====Performing the merger==== | ||
# Open the source and destination pages in two separate windows/tabs. | # Open the source and destination pages in two separate windows/tabs. | ||
# Cut/paste the source page into the destination page. | # Cut/paste the non-redundant content from the source page into the destination page. | ||
# Add <code><nowiki>#REDIRECT ]</nowiki></code> to the source page. | # Add <code><nowiki>#REDIRECT ]</nowiki></code> to the source page. | ||
# Be sure to remove the 'mergefrom' tag from the destination page before previewing | # Be sure to remove the 'mergefrom' tag from the destination page before previewing |
Revision as of 02:34, 12 July 2006
This page documents an English Misplaced Pages content. Editors should generally follow it, though exceptions may apply. Substantive edits to this page should reflect consensus. When in doubt, discuss first on this guideline's talk page. | Shortcut
|
Merging and moving are two fundamental aspects of how articles are developed and reformed on Misplaced Pages. A "merger" is a manual (non-automated) process by which two existing but similar (or redundant) pages are united under the same name. 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. Misplaced Pages is not a dictionary; 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 Flammability.
- 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 redirect or, in some cases, a disambiguation page 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 bold and do so. If the merge is controversial however, you may find your merge reverted, and as with all other edits, edit wars 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 {{merge|OTHER PAGE}} at the top of each page. It should appear like this:
It has been suggested that this article or section be merged with OTHER PAGE. (Discuss)If you know which page should remain, use {{mergefrom|SOURCE PAGE}} on that page, and {{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:
It has been suggested that SOURCE PAGE be merged into this article or section. (Discuss)and
It has been suggested that this article or section be merged into DESTINATION PAGE. (Discuss)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 {{multiplemergefrom|], ], ], etc}} to generate the following:
It has been suggested that SOURCE PAGE ONE, SOURCE PAGE TWO, SOURCE PAGE THREE, etc be merged into this article or section. (Discuss)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 Misplaced Pages:Proposed mergers.
- 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 template substitution and editing.
- Do not use the above tags to propose a category merger. This should be requested at Misplaced Pages:Categories for discussion, which uses a separate {{cfm}} template.
Performing the merger
- Open the source and destination pages in two separate windows/tabs.
- Cut/paste the non-redundant content from the source page into the destination page.
- Add
#REDIRECT ]
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 "What links here" on the destination page for double-redirects.
- 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 Misplaced Pages:Cleanup resources, such as {{cleanup-date|December 2024}} (using the current month and year as the parameter).
Renaming / Moving
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 Misplaced Pages:Redirects for deletion. 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.
- NPOV – 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 Marie de Rabutin-Chantal, marquise de Sévigné, but rather for Mme de Sevigne.
Cross-namespace moves
The move feature is capable of moving pages in any namespace, 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 Talk/Abraham Lincoln to Talk:Abraham Lincoln, or moving Articles for deletion/Some article to Misplaced Pages:Articles for deletion/Some article. In some cases, new users may create articles on themselves that they intend to serve as their user page, in which case such an article may be userfied.
Generally speaking, other types of cross-namespace moves will be controversial and worth discussing with other editors. Misplaced Pages:Requested moves 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 Misplaced Pages:Deletion process should be used, preferably Misplaced Pages:Articles for deletion, as Misplaced Pages:Proposed deletion and Misplaced Pages:Speedy deletion 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 logged in 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 edit history. (The GFDL 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 here to have an administrator repair it.
If you cannot rename a page, or you think that the renaming may be controversial, please go to Misplaced Pages:Requested moves 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 WP:RM.
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
- Misplaced Pages:How to fix cut and paste moves
- Misplaced Pages:How to break up a page
- Help:Moving a page
- Misplaced Pages:Article size