28:
266:; you should not attempt it unless you feel confident that you know what you're doing. Also note that it may misrepresent an editor's intention at the boundaries between article histories, and thus should only be used in a situation in which two articles are essentially identical, such as a cut-and-paste move in which both articles have continued to develop since the move.
107:
160:, however, and unless the article title is confusing or objectionable, it may be preferable just to leave it as a redirect to the merge target, in which case the usual interpretation of the licensing requirements requires only that the edit summary about the merge states the name of the article from which the merged information is derived.
154:". The objection is then frequently made that such an action is not possible under the licensing requirements. This may not be strictly true since attribution of authorship can be maintained in other ways, but it is troublesome and so a merge and delete is not usually done unless there is a specific and pressing problem with the redirect.
251:
An administrator merges the article history into the merge target along with the content. This action is done by moving the merged article over the target article, which automatically causes the target to be deleted, and then undeleting the history of the target article. Another edit usually needs
221:
from the main talk page. If the merged article is moved, the history can be accessed in the same way as any other page. This may be necessary if the title of the merged article is confusing or objectionable enough to make it an exceptionally poor redirect, although in such cases deletion often
293:
link exists to the previous edit, even if the link is broken, deleted, or directed to a non-static page. If there are only a few authors, their linked usernames can be included in the edit summary documenting the merge. If there are more authors, a list on the talk page or a subpage may be
277:
Under GFDL section 4, you are obligated to include the five "principal authors" when moving or merging a page, plus any authors in the page history dating back four years, as well as the "network location" of the required history pages. Older edit histories can be excluded or deleted.
229:
be maintained so that attribution is not lost. It is questionable if attribution is ever properly achieved since there is no link from either the article or its history to the attribution history. Therefore, this approach is almost never used on
Knowledge at present.
171:" A new editor may make such a vote without understanding the licensing requirements; this can be safely read as a merge vote. An advanced editor who wishes to argue for a merge and delete should make clear why the redirect would be unacceptable.
297:
Though this method is legally acceptable, it is not preferred, since, in addition to potentially voiding the GFDL part of the dual-license, history erasure complicates tracking editor contributions in addition to attribution.
122:
142:... you must ... Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page.
242:
of the merged article history can be copied onto a subpage, and linked. The list that results must often be edited for coherence. This approach does not have favor among
Knowledge administrators at this time.
133:
You must... retain... identification of the creator(s) of the
Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if
282:
146:
These licensing terms require that when one article is merged into another, either the history of the merged text must be preserved, or the authors' names must be recorded for attribution. At
356:
129:(GFDL), which Knowledge uses to license all of its content, both have provisions requiring that the attribution history of an article be preserved. CC BY-SA, section 3(a), states that:
310:
is unrelated, and presents no problems under the licensing requirements. As long as no content is merged, the old article can be safely deleted and a redirect created in its place.
205:
The best option is to simply rename the page with the unsuitable title. If the to-be-merged article's title is not suitable as a redirect, it could be renamed to another title that
150:, when an editor wishes for an article to be merged to another article but does not regard the article's title as a useful redirect, the editor sometimes suggests something like, "
259:
This technique is normally only used on
Knowledge for repairing cut-and-paste moves where the history of an article has become accidentally fragmented across several titles.
209:
suitable for a redirect. In this way the article's history is maintained just like a normal merge and the old redirect will be left with no history and can be deleted.
272:
182:
126:
233:
212:
256:
for more information. Ensure that deletion log and edit summaries make clear what you are doing, as there should be a record of the merge itself.
269:
Nevertheless, it is not normally necessary to leave the source of the merge deleted. It is more usual simply to redirect it to the merge target.
115:
Pages that have been merged to other articles should almost never be deleted, since our copyright requires all authors to be publicly credited
36:
253:
285:. One significant difference with the CC-BY-SA license is that history preservation is no longer strictly requgired, so long as
174:
371:
339:
324:
246:
44:
57:
334:
147:
56:
This page provides additional information about concepts in the page(s) it supplements. This page is not one of
217:
The merged article is moved into, for example, a subpage of the target article's talk page, and then linked to
157:
61:
376:
381:
179:
On the rare occasion that the article title is not suitable as a redirect, there are several options:
344:
319:
40:
163:
Unless there is a particular reason to delete a redirect, admins should feel free to interpret "
86:
196:
8:
294:
appropriate, with that list clearly marked to indicate that it must remain permanently.
357:
Knowledge:Administrators' noticeboard/Archive133#A case of merge and delete and the GFDL
329:
188:
79:
71:
48:
17:
301:
365:
16:"WP:MAD" redirects here. For essay about how to deal with being mad, see
123:
Creative
Commons Attribution-ShareAlike 4.0 International License
252:
to be made to make sure the correct version is displayed. See
281:
In 2009, Knowledge changed from the GFDL license to GFDL +
313:
225:
When the talk page gets archived, a link to the subpage
363:
283:Creative Commons Attribution-ShareAlike License
289:of the article authors are included, and
254:Knowledge:How to fix cut-and-paste moves
364:
175:What can 'merge and delete' look like?
273:Record authorship and delete history
183:Rename to another title and redirect
101:
22:
138:The GFDL, section 4-I, states that:
13:
340:Knowledge:Redirects for discussion
325:Knowledge:Copying within Knowledge
264:this procedure can get complicated
62:thoroughly vetted by the community
58:Knowledge's policies or guidelines
45:Knowledge:Copying within Knowledge
14:
393:
105:
26:
335:Knowledge:Articles for deletion
308:delete and recreate as redirect
148:Knowledge:Articles for deletion
127:GNU Free Documentation License
1:
234:Paste history to talk subpage
372:Knowledge supplemental pages
213:Move to subpage of talk page
7:
10:
398:
186:
69:
15:
345:Knowledge:Delete or merge
320:Knowledge:Deletion policy
41:Knowledge:Deletion policy
113:This page in a nutshell:
144:
136:
140:
131:
302:Delete and redirect
158:Redirects are cheap
125:(CC BY-SA) and the
60:as it has not been
377:Knowledge deletion
330:Knowledge:Redirect
49:Knowledge:Redirect
382:Knowledge merging
119:
118:
99:Explanatory essay
97:
96:
37:explanatory essay
18:Knowledge:Explode
389:
199:
165:Merge and delete
152:Merge and delete
109:
108:
102:
89:
82:
30:
29:
23:
397:
396:
392:
391:
390:
388:
387:
386:
362:
361:
316:
304:
275:
249:
236:
215:
203:
202:
195:
191:
185:
177:
106:
100:
93:
92:
85:
78:
74:
66:
65:
27:
21:
12:
11:
5:
395:
385:
384:
379:
374:
360:
359:
353:
352:
348:
347:
342:
337:
332:
327:
322:
315:
312:
303:
300:
274:
271:
248:
247:History fixing
245:
235:
232:
214:
211:
201:
200:
192:
187:
184:
181:
176:
173:
117:
116:
110:
98:
95:
94:
91:
90:
87:WP:MERGEDELETE
83:
75:
70:
67:
55:
54:
33:
31:
9:
6:
4:
3:
2:
394:
383:
380:
378:
375:
373:
370:
369:
367:
358:
355:
354:
350:
349:
346:
343:
341:
338:
336:
333:
331:
328:
326:
323:
321:
318:
317:
311:
309:
299:
295:
292:
288:
284:
279:
270:
267:
265:
260:
257:
255:
244:
241:
231:
228:
223:
220:
210:
208:
198:
194:
193:
190:
180:
172:
170:
166:
161:
159:
155:
153:
149:
143:
139:
135:
130:
128:
124:
114:
111:
104:
103:
88:
84:
81:
77:
76:
73:
68:
63:
59:
52:
50:
46:
42:
38:
32:
25:
24:
19:
307:
305:
296:
290:
286:
280:
276:
268:
263:
261:
258:
250:
239:
237:
226:
224:
218:
216:
206:
204:
197:WP:MADRENAME
178:
168:
167:" votes as "
164:
162:
156:
151:
145:
141:
137:
132:
120:
112:
34:
306:A vote for
219:permanently
134:designated)
35:This is an
366:Categories
351:Case study
262:Note that
39:about the
222:results.
72:Shortcuts
314:See also
189:Shortcut
169:Merge.
80:WP:MAD
51:pages
240:text
238:The
227:must
121:The
47:and
287:all
368::
207:is
53:.
43:,
291:a
64:.
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.