Jump to content

Wikipedia:Featured article candidates/Wade's Causeway/archive1

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by PocklingtonDan (talk | contribs) at 19:41, 12 December 2013 (→‎Comments from [unregistered user]). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Wade's Causeway (edit | talk | history | links | watch | logs)

Nominator(s): PocklingtonDan (talk) 21:57, 11 December 2013 (UTC)[reply]

I nominate this article for FA consideration as its primary editor to date. I am happy to work with reviewers to make any improvements that are felt necessary. This is the first nomination for FA of this article. It has had a GA nomination (successful) and a peer review. PocklingtonDan

The article is about a stone structure of ambiguous origin, located in Yorkshire, United Kingdom. FA review of areas such as copy-editing are welcome, but specific value can be added by reviews additionally by those with domain knowledge in areas such as archaeology, history, and etymology. (talk) 21:57, 11 December 2013 (UTC)[reply]

Feedback from Curly Turkey

I haven't really read the article; maybe I will, maybe I won't. I just wanted to know what was going on with the mountains of "Explanatory notes", like "See Grimm[169] and Davidson.[135]", that just point to "Citations" without "explaining" anything? Is this a convoluted bundling method? Have you seen sfnm?

 Doing... Thank you for taking the time to give the article a brief scan. I hope you will take the time to read and review it fully. I am looking at this particular item now, thanks for the helpful javascript tool - PocklingtonDan (talk) 19:12, 12 December 2013 (UTC)[reply]

Also, there are a ton of harv errors in the references. You can see them easily if you use User:Ucucha/HarvErrors. Curly Turkey (gobble) 22:09, 11 December 2013 (UTC)[reply]

 Doing... I have sorted the reference errors. However, the same javascript tool shows several refs that are not cited. This may be works that were added as refs but then the cites removed, or may be where refs are typoed or duplicated etc. I will investigate each one and revise accordingly and am doing this now - PocklingtonDan (talk) 19:12, 12 December 2013 (UTC)[reply]

Comments from Chris857

I'm noticing there seems to still be a ref issue, note ϸ, I see "See Knight (2011),[260]Powell (2012)CITEREFPowell2012 and NYNPA Minerals Technical Paper (2013).[261]" -- note the CITEREFPowell2012.Chris857 (talk) 16:10, 12 December 2013 (UTC)[reply]

 Done Thanks for the heads up. This is now resolved - PocklingtonDan (talk) 18:54, 12 December 2013 (UTC)[reply]

There are also two refs with "|url= missing title (help)" errors. Chris857 (talk) 16:10, 12 December 2013 (UTC)[reply]

 Done Thanks for the heads up. This is now resolved - PocklingtonDan (talk) 19:08, 12 December 2013 (UTC)[reply]

Oppose from [unregistered user]

Oppose reference system is weird. For example, do a ctrl+F for "[79]". There are two hits. One goes to the citation "Hayes 1964, p. 11.", but the other goes to the explanatory note "Ϗ.^ See Lang[146] and Geake.[210]". This seems to be the case for all the citations. 122.172.27.199 (talk) 16:50, 12 December 2013 (UTC)[reply]

Oppose rather than pointing out some problems that you can see and giving me an opporunity to fix? Why? The FAC guidelines suggest that reviewers and editors work together to improve articles, this unsightly brief comment stating oppose is hardly conducive to that end. I see that you are an unregistered user with 3 edits from 2009 and a dozen more in the last 24 hours. You may want to withdraw your oppose, which as an unregistered user is highly unusual, and familiarise yourself more closely with the FA review process. PocklingtonDan (talk) 18:54, 12 December 2013 (UTC)[reply]

Comments from Squeamish Ossifrage

Oppose, urge withdrawal.. FAC doesn't prescribe a specific referencing standard, but this isn't really acceptable. Numbered citations point to "explanatory notes" which aren't numbered, but are instead indexed with a (very) extended Greek alphabet? Then those notes in turn point to sfn-formatted citations with corresponding references? That's very confusing, and it's nonstandard to the point of uniqueness. Additionally, you've got unformatted external links (like in the lead). There are books missing ISBN numbers (I believe the Barker book is 978-0-7134-3189-6, for example), and books without issued ISBN numbers should ideally have OCLC numbers instead. The division of books into printed and electronic sections based, presumably, on how you accessed them, is very confusing to the reader and not at all a standard practice. Google Books is not a publisher per se; you're also very inconsistent how you refer to Google Books and whether it's italicized. Most of the printed journal entries lack page numbers, and I'm highly dubious of the way you've formatted the title of the Austen reference (if it doesn't have a title, don't make one up). Malformed templating abounds (Chadwick, Andrews, Strahan, Witcher, likely others). Several of the website references are insufficiently formatted ("North York Moors" is little more than a bare link), and several are not reliable sources (including MyHeritage, Wiktionary pages, and a Wikipedia image file!). Squeamish Ossifrage (talk) 17:29, 12 December 2013 (UTC)[reply]

Oppose rather than pointing out some issues that you can see and giving me an opporunity to fix? Why? The FAC guidelines suggest that reviewers and editors work together to improve articles, this unsightly brief comment stating oppose is hardly conducive to that end. Additionally, offering a wall of text rather than cogent and well ordered points makes your comments difficult to respond to: nevertheless, I will attempt to do so. Most of your points were covered and explained at GA review, but I will revisit them here. I would urge you to change your oppose to a comment and allow us to work on addressing these minor issues that have raised. PocklingtonDan (talk) 18:54, 12 December 2013 (UTC)[reply]