2

We have a sister site, ELL, as far as I understand. (So, to some extent, do other sites, such as Theoretical Computer Science (Computational Science) or MathOverflow (Mathematics).

I wonder whether we would consider a question "duplicate" at all if the criteria we normally apply to "duplicate" were met by a question on our sister site. Because of the considerable overlap in scope, that can easily happen.

This may pertain to a site policy -- how strong the family bond is between EL&U and the rest of the StackExchange family, and namely, whether we want to be comprehensive by ourselves in terms of covering individual topics, or whether we feel it is sufficient that StackExchange is so. I would like to learn about the policy. (As far as I know, ELL was born out at least partly out of the needs of this site.) Also, there might be technical issues, of course. I'd be interested in those, too.

  • 5
    Ironically, this question is answered on another site! See meta.stackexchange.com/questions/4708/… – Andrew Leach Nov 13 '15 at 12:28
  • @AndrewLeach Thank you. Of course, one can always link the other question, that's for sure (although it won't show in the LINKED tab, will it, if it is on another site?) Personally, I do not much care for the solution of letting the question live in both cultures, as they will provide different answers. I do not think this applies to EL&U and ELL, in particular. However, I really liked the idea of crossover feature (meta.stackexchange.com/questions/199989/…). Is it anywhere near being available? – anemone Nov 13 '15 at 12:46
2

Since the question is answered on another site, I shall take the advice in that answer and its comments.

TL;DR: Take the relevant parts of the answer from the other site and summarise/quote in an answer exactly as you would for any other internet reference.

For questions that are on-topic on both stacks, not asked by the same person, and already have a good answer on the other stack:

Link to the other question with a community wiki answer.

Also, it could be good to include the full text of the post in block quotes (using >) in case it gets deleted, and linking to the other author's profile on the other stack.

This:

  1. Allows the question asker to get the information they are looking for
  2. Has no risk of receiving reputation for another's work
    • Prevents any worries of plagiarism

This is the best compromise solution.

durron597


Well, as long as you quote and reference properly, I don't really see a problem with not making this community wiki. Afterall you usually get reputation for quoting and summarizing other sources from the internet anyway, so why not another SE answer. If the answer's good give that guy his rep, CW is IMHO counter to the workings of SE in those case. – Christian Rau

Personally, I don't have a problem with extending the "Duplicate" closure reason to other Stack Exchange sites, but as that isn't likely to happen, this seems to be a good solution which follows existing practice for information on non-SE sites.

This answer only applies to a question which, while answered elsewhere, is still on-topic on ELU. Where a question is answered elsewhere because the answer is where the question is on-topic, then the question should be migrated and treated as a normal duplicate. That may even happen between ELU and ELL [in either direction], as well as a question being on-topic in both places.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .