This user has administrator privileges on the English Wikipedia.


From Wikipedia, the free encyclopedia
Jump to: navigation, search
If you want to leave me a message, please use my talk page. Remember to sign your message with ~~~~. I will respond to all civil comments there, unless you specify that you would rather I respond on yours.
Basic info
Admin mop.PNG This user is an administrator on the English Wikipedia. (verify)
Edge-evolution.png This user is a member of the Wikimedia OTRS team.
Noia 64 apps xclock.png This user's time zone is EDT.
Noia 64 apps karm.svg This user has been on Wikipedia for 9 years, 6 months and 13 days.
W This user has started at least 406 English Wikipedia articles as of
November 26 2015 – the last article was
Copyright in compilation.

What I do here[edit]

Activities & Notes
CCI badge multi.png This user regularly helps conduct Multiple copyright infringement Investigations.
Checked copyright icon.svg This user is a member of WikiProject Copyright Cleanup.
Question book magnify2.svg This user is a member of
Wikipedia's Help Project.
Question mark.svg This user is a member of the Missing article WikiProject.
Police man Twinkle Head.svg This user performs administrator tasks in the blink of an eye with Twinkle!
I'm an awesome Wikipedian!
This user has been identified as an Awesome Wikipedian and was awarded her own day.
Featured article star.svg Moonriddengirl's Awesome Wikipedian day is 7 June 2009.
Featured article star.svg Moonriddengirl's Awesome Wikipedian day is 20 January 2011.
3DTomo.jpg This user has migraines.

My current primary focus on Wikipedia is addressing copyright concerns. I really enjoy article work, but don't get to write much. There's just so much mopping up to do.

I emphasize collaboration and courtesy. Working on an encyclopedia can be very stressful; Assuming good faith sometimes requires active effort, but it's worth it. Misanthropy does not make a happy Moonriddengirl. Like many people, I sometimes get tunnel vision while working. While I hope I am never rude as a result, I know that sometimes I am more businesslike than others. While occasionally adminship may also require a businesslike approach, I generally prefer to be amiable. If I have seemed unduly brusque with you, please excuse me.

I am not available in volunteer mode as often as I used to be, but am still willing to help where I can. Please feel free to drop me a note, although it may not be your quickest avenue of getting help if you catch me in a busy time. I welcome helpful talk page stalkers.

I suffer occasional migraines which may limit my participation for hours or even days at a time. Fortunately, these don't happen often, and as long as I'm able to function, I'm likely to check in, though I won't be undertaking anything complicated at those times.

I possess one other sometimes active account on Wikipedia, User:Moonriddengirl2, created for use while traveling so as not to risk compromising the log-in information of my primary account. I have also created two doppelgänger accounts, User:Moonriddengir! and User:MRG, by which abbreviated name I am often called.

Text based copyright concerns[edit]

I spend quite a bit of my Wikipedia time evaluating text-based copyright problems. I am not a lawyer, and this is not legal advice. This is based on my understanding of the intersection of US copyright law and Wikipedia's copyright policy. If you'd like to discuss text-based copyright concerns with me or if you have a question about text copyright that is not answered here, please feel free to leave your civil message on my talk page. If I can help you, I will. If I can't, I will try to help you locate a more appropriate resource.

On copyright and my handling of copyright

Basic copyright policy overview[edit]

Wikipedia's servers are located in the United States, and so we are bound by US copyright law, although in an effort to keep our content free wherever possible we also attempt to respect copyright laws of other countries. (See Wikipedia:Non-U.S. copyrights.) If material is not automatically excluded from copyright (see Stanford's summary of some of the exclusions), public domain for age or other reasons, or released under a license compatible with ours (that would be CC-BY-SA for all text, with most text co-licensed under WP:GFDL), we can only use it if it meets our non-free content guidelines. In order to keep our content as freely distributable as possible, this is a deliberately more narrow range than fair use. For text, this means we can utilize limited quotations of copyrighted material—so long as that material is clearly marked, cited and used verbatim—when appropriate to illustrate a point, establish context, or attribute a point of view or idea. (Some contributors are under the mistaken belief that if the source is cited, exact duplication of text is not a copyright infringement. This is not the case. United States copyright law does permit limited use of copyrighted text under fair use, but makes very clear that "acknowledging the source of the copyrighted material does not substitute for obtaining permission."[1]) Since copyright covers the creative expression of ideas, not facts, we can paraphrase external sources (though we should still acknowledge them to avoid plagiarism and meet verifiability policies). But we do have to be careful when paraphrasing that we do not too closely follow the original in structure and language.

When summary isn't acceptable[edit]

The US government utilizes a "substantial similarity" test intended to determine if infringement exists. Melville Nimmer produced subcategories of "substantial similarity" for which the courts search. In the first, they look for "fragmented literal similarity", checking for phrases and passages copied or closely paraphrased from the original text. Unless such phrases are defensible as fair use, their presence is a strong indicator of infringement. (Note that on Wikipedia, such phrases must always conform to our non-free content guideline.) This is a definition of copyright with which most contributors are familiar.

But in the second, courts look for "comprehensive non-literal similarity." Even if there is no verbatim duplication of the copyrighted original, infringement can be found if the new version follows so closely on the structure of the original that copying is clear. As the US Court of Appeals noted in discussing Artica v. Palmer, et al. (970 F.2d 106, 1992): "A plaintiff succeeds under this doctrine when it shows that the pattern or sequence of the two works is similar."[2] Wikipedia's contributors are cautioned here against utilizing great detail in summarizing or analyzing, to avoid creating a derivative work, as only the original copyright holder has the legal right to license derivative works.

This can be a challenge in practice, but we do need to be careful to comply, since word-for-word duplication is not the limit of copyright infringement. Basically, what this means is that you can't read an article in The Fabulous Encyclopedia of Everything and reproduce it here, not even if you tweak the language a bit so that there is no "literal similarity." A close paraphrase of another source (whether comprehensive or fragmented) may be a derivative work, which is actionable unless it meets the fair use doctrine. If substantial similarity exists, you (yes, you, if you added it here) could be in trouble. Wikipedia could potentially be in trouble along with you. The best way to avoid this is to not only substantially restructure the article, but also to incorporate additional sources. If you're drawing on multiple sources, you're less likely to be taking too much from one.

To read more about summary, I heartily recommend the following:

Handling copyright concerns[edit]

With regards to addressing copyright problems, I am guided by Wikipedia:Copyright problems/Advice for admins. In terms of articles what this means (briefly) is that if copyright infringement is substantial and there is no non-infringing version in history, the article is likely to be deleted. It may be deleted immediately under criterion WP:CSD#G12 of the speedy deletion criteria if it meets certain conditions. It may be deleted after a seven day process if it does not. This deletion is necessary for copyright protection.

Sometimes, copyright problems are not extensive or have not been present through the entire history of the article. In that case, I may delete the "history" of the violation, leaving an earlier version of the article where the problem did not exist. Alternatively, I may remove the material or revise it, leaving a warning in edit summary and at the article's talk page against the restoration of that text. In all of these cases, content can be restored to the article (or a new article written) as long as the material is sufficiently revised. You also may restore the material if you can verify that the material is free for Wikipedia to use.

Importing PD or "Free" license[edit]

Sometimes, material may be already free for use, and it can be a simple matter of providing evidence of that (for one example, by providing a link to show where on the site the material is already placed in public domain). If it is released under free license, it may come down to a question of whether the licenses are compatible with CC-By-SA. (Source: [3])

License Compatibility
Creative Commons Licenses
License/Compatible License/Compatible
CC-By-NC Red XN CC-By 2.0 Green tickY
CC-By-NC-ND Red XN CC-By 2.5 Green tickY
CC-By-ND Red XN CC-By 3.0 Green tickY
CC-By-NC-SA Red XN CC-By-SA 1.0, 2.0, 2.5, 3.0 Green tickY
CC-By-NC-SA Red XN CC-By-US 3.0 Green tickY
Other Licenses
Any GNU only license Red XN GFDL & CC-By or CC-By-SA Green tickY

If there is no indication of free license at the source page, you will need to verify permission. See the next section.

Verifying copyright permission[edit]

Sometimes the material is not already free for use, but copyright owners are willing to release their material in a form we can use. In that case, we will need external verification of permission to duplicate previously published material on Wikipedia or even to very closely summarize it. We need this even if you have claimed to be the copyright owner of the external source, because we do not require verification of identity at account creation.

You can verify permission in one of two ways, though licensing requirements depend in part on who authored the material. The licensing requirement is as follows:

  • If you are the sole copyright holder of previously published material that you, yourself, are placing on Wikipedia, it must be co-licensed for use under CC-BY-SA and GFDL (both of which licenses allow commercial and non-commercial reproduction and modification so long as the material is properly attributed and as long as subsequent versions are licensed the same).
  • If you have coauthored the material with somebody else, or if somebody else owns the copyright, it may be co-licensed as above or released under any single license compatible with CC-BY-SA (including CC-BY-SA itself).

When transitioned to Wikipedia, it will be released under CC-BY-SA and, if co-licensed, GFDL.

The two methods of verifying permission are:

  • Note on the original source of publication: If you (as the copyright owner) choose to do the former, it is sufficient to place at the site "The contents of this website (or page, if you are specifically releasing one section) are available for modification and reuse under the terms of the Creative Commons Attribution/Share-Alike License 3.0 and GNU Free Documentation License unversioned, with no invariant sections, front-cover texts, or back-cover texts)." Make a note at the article's talk page linking to that release, and the administrator who evaluates the article at the end of the 7-day listing period will restore the contents. Note, please, that the release must remain displayed, or the material may be challenged later and removed. (If you are not the sole copyright holder, reference to GFDL can be omitted.)
  • Communication directly to the Wikimedia Foundation verifying the release, via e-mail, postal letter or FAX: If you choose to send a letter to the Wikimedia Foundation, it is easiest by far to do so via e-mail. The address that sends the e-mail must be associated with the original publication. There is a boilerplate release form at Wikipedia:Declaration of consent for all enquiries which can be helpful. For text, the release must either put the text into public domain or license it under CC-BY-SA 3.0 and (if you are the sole copyright holder) GFDL. Please provide a clear link to the website in your e-mail and specify by name the article on Wikipedia in which the material is being used. Once your e-mail is received and processed by a member of the Communications Committee, the article's contents will be restored if your release is legally sufficient. Please make a note that you've done this on the talk page of the article to help guard against premature deletion of the page. You can compose a note or very simply paste the following on the talk page, brackets and all: {{OTRS pending}} (For more information, including the address to which the release should be sent, please see Wikipedia:Requesting copyright permission or Wikipedia:Donating copyrighted materials.)

Occasionally a contributor sends a letter, but forgets to note that at the article talk page, or the Communications Committee becomes backlogged and the letter is not addressed in a timely fashion. Sometimes the letter did not address all concerns, and correspondence does not complete in time. The article may be deleted. When the verification is received by the Communications Committee, it should be restored. If this has happened to you, I would recommend waiting a few days to see if the process completes. If it does not, it may be that your permission letter did not reach the Committee, as e-mail is sometimes lost. I would recommend resending it if no action has been taken 10 days after you originally sent your note. My observation suggests all requests should have been processed by then.

Image-based copyright concerns[edit]

Wikipedia:Image use policy offers some guidance on image copyright and public domain. If the image is not public domain—or if you are not the original author of it—it still may be usable. Again, our non-free content guideline can help you, as it explains when we can sometimes use images that do not have a compatible license. There are a number of Category:Non-free image copyright tags that can be used in conjunction with a properly filled-out Template:Non-free use rationale to assert when an image is so usable. Please keep in mind through all of this that you cannot claim authorship of a derivative work. For example, you can't photograph a copyrighted painting and release the photograph into public domain. You can't take a screen capture of a television show and release the screencap into public domain. You can't crop a copyrighted image and release the crop into public domain. Only the copyright holder has the legal right to make and release derivative works.

I may sometimes delete images or tag them for speedy deletion under one of the processes set out at our guide to image deletion, but only if I find the concerns clear-cut. Typically, I will list them for evaluation at our possibly unfree image forum or the forum for non-free content review.

For questions about image copyright not explained above, please visit the helpful folks at Wikipedia:Media copyright questions.


For specifics, see User:Moonriddengirl/Deletions.

I am not currently heavily involved in deletions aside from those related to copyright, but considering that I dedicated almost the first full year of my adminship to tool use in the speedy deletion queue, contributors might be interested in knowing more about my work there. For specifics on copyright deletions, please see above.


I am completely open to civil, good faith discussions about my admin actions. If I'm doing something wrong, I really want you to tell me, so that I can start doing it correctly. If I see you making a mistake, I'm going to point it out to you as diplomatically as I can and consider that I'm doing you a favor. So, please, do me the favor, too. Admins, if you see that I've made a mistake, please fix it. If you reverse my admin actions, I would be grateful if you'd leave me a nice note telling me what you've done and why and if you would be open to discussion with me should I disagree. (See "Grievances by users" for other steps & options for dealing with tool misuse.)

I think adminship is a job that needs to be taken seriously and used with responsibility. Admins are in a unique position to alienate other editors, if they misuse the tools. Certainly, I can't think of much that would have more discouraged me as a newcomer than being unjustly blocked or having an article unfairly deleted. This is one of the reasons why I support process. As experienced editors, we may be able to look at that article on that piece of software and just know that it cannot possibly survive AfD because it simply is not notable, but deleting it out of process can only undermine the creator's sense of trust in the community. We want them to follow procedure; we should be willing to demonstrate that we will, too.

When I evaluate adminship requests (which I don't do often, unless I see a situation where I believe my input may have value, because it can take me hours), I am looking particularly for what I perceive to be a risk of misuse of the tools in a way that might seriously harm the project. Since admins are often perceived as authorities (correctly in ways involving the tools, incorrectly in matters of ordinary content disputes), I believe that incivility is likely to cause serious harm to the project. Civility is not a suggestion; it's policy, #4 of the five pillars. (You'll remember that note above: if we want other users to follow procedure, we certainly should demonstrate that we will.) I am also highly concerned when I fear a tendency to misapply speedy deletion criteria. Speedy deletions are often unevaluated. Since content is hidden from ordinary editors, it is one of the least transparent uses of the admin tools. There is always deletion review, but new contributors in particular are unlikely to pursue that avenue. Wikipedia relies on admins to use good judgment here and to know and follow community consensus as set out at WP:CSD. I look meticulously for evidence that admin candidates do not, as this is one area where mistakes may go undiscovered and damage the project for a very long time.

What I do elsewhere[edit]

I have a wide variety of interests—including videogames, music, movies, and books. I have an advanced degree in a liberal arts field and have spent many, many hours studying languages that nobody living speaks. (In other words, I have what some describe as a high tolerance for pointless activity.) My work off wiki is nowhere near as diverse and varied as what I do here. I have loved being exposed to so many different subjects. I write fiction in my spare time and sometimes argue with my husband over control of the remote. You may occasionally find me playing Rock Band with my teenage son.

My username comes from a poem by Denise Levertov, "In Mind", but the name is significant to me on a number of metaphoric levels.

I am, in my own opinion, the queen of malapropisms and unintended puns. On Wikipedia, preview sometimes helps me catch these; often it does not. I generally notice them seconds after I've hit "save page." I suspect there are many I've never noticed. No mistake I've ever made on Wikipedia, though, has amused me more than this one. (No, not even including this. But I note that I am not only now rewarding copyvios, but evidently preparing them. I need to be stopped. Face-confused.svg)


Barnstars are a way of saying "Good work" to another editor. Appreciation can also be conveyed more informally (but just as meaningfully!) with a note. A lot of solitary hours go into building the project, and community support = a good thing. I appreciate those people who've taken the time to offer encouragement in any way. And since Barnstars are pretty, I'm displaying mine proudly here. Thanks. It's nice working with you.

See also[edit]

Committed identity: 03316b9685c5637fdef2bd6ea62b9171656185fb32131d72a6dc2e3eb957673d1b3404953812022ac64fca474e5d58c0b873b77503ed59df30a19c4bfa42c602 is a SHA-512 commitment to this user's real-life identity.