# Wikipedia talk:WikiProject National Register of Historic Places

WikiProject National Register of Historic Places (Rated Project-class)
This page is within the scope of WikiProject National Register of Historic Places, a collaborative effort to improve the coverage of U.S. historic sites listed on the National Register of Historic Places on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Project  This page does not require a rating on the project's quality scale.
 To-do: Development Help provide 100% coverage of at least one county in every U.S. state by creating NRHP articles in DE, ME, VT (see Progress) Help meet 20% coverage in every U.S. state and territory by creating NRHP articles in SD (see Progress) Expand articles sourced only to NRIS by adding additional information from reliable sources Create new articles or develop existing ones, especially in states where all NRHP nomination forms are available online Run peer reviews/collaborations to improve higher importance NRHP articles to good or featured status Upload new photos to Commons and link from NRHP list-articles Place uploaded, unused images into list-articles and NRHP place articles Find and add HABS, Flickr, or other images where allowable Maintenance Assess 20 article(s) having no quality rating assigned Assess 779 article(s) having no importance rating assigned Add an infobox to 3 article(s) without one Verify information in 4 article(s) without a valid NRIS version date Fix 14 infobox(es) needing cleanup Cleanup these articles tagged as needing cleanup Pay attention to 15 article(s) tagged and these listed as needing attention Address a state's NRIS info issues with National Register staff and state historic preservation offices

## Virginia ostensibly done

Pub's tracks now go from Virginia to Pennsylvania. Not sure about New York Smallbones(smalltalk) 20:05, 2 February 2014 (UTC)

Hi all: I've worked through all counties and independent city listing for the Commonwealth of Virginia. Most unstubbed articles are for archaeological sites for which the Virginia Department of Historic Resources does not include the NRHP nomination forms. I'll go back and look at the gaps or any other additions made since I started in May 2013. For each listing, I include the Virginia Landmarks Register reference and added them to existing articles, as well as links to the nomination forms available at the Virginia Department of Historic Resources website. Maybe on to South Carolina? Cheers--Pubdog (talk) 17:28, 2 February 2014 (UTC)

Excellent. I've been trolling Flickr and a couple of other sites looking for images, too - I've managed to add about twenty to the lists that weren't there before. --Ser Amantio di NicolaoChe dicono a Signa?Lo dicono a Signa. 18:19, 2 February 2014 (UTC)
Absolutely outstanding! I put the map up to show how important Pub's contributions are to the project. If you're going to do South Carolina, note that the SC Dept Archives and History has a summary of the NRHP nomination for each site (eg), and a link to their copy of the nom. Delaware and NJ fit in with your Mid-Atlantic concentration. Maybe California or Texas if you are looking for a really big challenge. Smallbones(smalltalk) 20:05, 2 February 2014 (UTC)
Excellent work! If you're looking at the Carolinas, you should note that North Carolina also has all of its nominations online (except for address-restricted sites). They can all be accessed from this PDF on the North Carolina SHPO website. TheCatalyst31 ReactionCreation 21:39, 2 February 2014 (UTC)
Cool --- since I started with Prince George's County, Maryland in October 2008, I've managed to work my way through Maryland, New York, Pennsylvania, West Virginia, Delaware, and now Virginia. Keeps me out of trouble ... thanks and cheers.--Pubdog (talk) 23:00, 2 February 2014 (UTC)
Help would also be appreciated for Kentucky: it has fewer articles, a larger percentage are substubs, and like California (but unlike Texas) pretty much everything is on Focus. Nyttend (talk) 05:16, 3 February 2014 (UTC)
I've mentioned this before, but does anybody want to get more images of sites in Emporia, Virginia? The list for that city has two images now, one of which is mine, and I passed up the chance to snap a picture of one site, when I drove through there back in November 2013, and I've been kicking myself for it ever since. ---------User:DanTD (talk) 17:40, 27 February 2014 (UTC)
I'd like to, but it's a bit much of a drive for me. Nyttend (talk) 02:38, 28 February 2014 (UTC)

## Incorrect refnums in county lists

I've just run my bot to produce output for duplications based on refnums rather than titles. While the job queue still hasn't completely caught up (and thus the giant 11k member list showing missing refnums; consider yourself warned), I did get some kind of reasonable result. I'll run through once more now that it appears (by spot checking) that all the counties that hadn't caught up when I started the bot are caught up now.. or at least a good portion of them. Just looking through the results, I found a few odd circumstances:

1. My code showed Augusta Electrical Generating Plant as duplicated in Woodruff County, Arkansas. This is because the row for McCrory Commercial Historic District mistakenly had the same refnum as the electrical plant. I fixed the error, so next time this should not show up.
2. There is also the case of Druid Hills Historic District (Atlanta, Georgia). This listing shows up as duplicated in DeKalb County, Georgia, which is kind of weird. That list shows a "Druid Hills Historic District" and a "Druid Hills Parks and Parkways". They are both technically different listings, but the article itself says the former is a boundary increase/renaming of the latter. As such, should there really be two separate rows in the county list? I think usually we handle boundary increases by merging them to one row.
3. Sunken barges of Bridgeport, which covers three shipwrecks in Bridgeport, Connecticut, shows up as duplicated three times on the county list. All three shipwrecks, though different listings, have the same refnum in the county list.
4. The Avery Homestead and Avery House are listed under the same refnum on New London County, Connecticut.
$\vdots$

The list may go on (I'm pressed for time now), and these are quick fixes, but I just wanted to bring them to everyone's attention. Now that the refnums have taken on a more visible role in the county lists, it may make sense to do a once-over of all of them to find any errors. For sites with more than one refnum like boundary increases/decreases (which unfortunately currently output URL text), I will soon edit the NRHP row template to only pick out the first refnum listed, so a list of refnums in a single parameter is fine; don't worry about fixing those.. the main thing to check is if the refnum attached to a site is legitimately attached to that site in NRIS. Anyone want to volunteer to help me go through the lists? Although the bot has been helpful in finding these erroneous duplications, it can only go so far, meaning it won't be able to find flat-out wrong refnums. This is something that needs to be manually checked. Thanks for the patience with me as I work toward automating this process!--Dudemanfellabra (talk) 00:33, 9 February 2014 (UTC)

I've been looking through the list, and it looks like there are a whole lot of issues with mistakenly repeated refnums. I'm seeing a lot of duplicates within single counties, and that's almost never a legitimate duplication. I'm also seeing a bunch of different (and hopefully unusual) problems in the usable bits of the "missing refnum" section. I had to fix a hardcoded listing in Laramie County, Wyoming, and I thought we had gotten rid of those a while ago. There are also a number of flat-out missing refnums and typos in refnums (at least one of which was my fault, embarrassingly enough). Once the job queue catches up, it's probably going to take a group effort to straighten this mess out. As for the listing in Georgia, it probably shouldn't be two separate rows, but regardless of what we do the boundary increase should have a different refnum anyway.
On a related note, what's going on with the lists that are subsections of large cities? Some of them are showing up as additional "Illinois" sections under whatever state they're supposed to be in, some of them are in the multi-state section, and some (including Chicago, ironically) aren't showing up as having any duplicates when they should be. TheCatalyst31 ReactionCreation 01:55, 9 February 2014 (UTC)
I re-ran the bot overnight, and I am now mostly satisfied with the output. Just spot checking the missing refnums list, it seems that a majority of the articles listed there now legitimately have something wrong with the refnums--i.e. they're either missing or not the standard 8 number format. I also was able to fix the multiple "Illinois" sections, which was due to a dumb coding mistake on my part. I'll begin working on trying to clean refnums up later today and am thankful for any help volunteered.--Dudemanfellabra (talk) 17:16, 9 February 2014 (UTC)
Also, with regards to the boundary increases being in a second row, I found Moraine Park Museum and Amphitheater in Larimer County, Colorado. Can we get a general rule for these cases? According to WP:NRHPMOS#Naming conventions:

Though the boundary increase receives its own official name and reference number and Elkman's tool outputs two separate infoboxes, it is common practice to [...] simply combine the boundary increase listing in the state, county, or other list with the original listing.

So IMO these two rows should be combined. Agree or disagree?--Dudemanfellabra (talk) 18:01, 9 February 2014 (UTC)
Combined the two Moraine Park listings. The problem is that it didn't look like a boundary increase from the name alone; unless I missed something, the only way to notice this was a careful check of the nomination form or other documentation, and it's not something that we would have caught easily. Nyttend (talk) 20:32, 9 February 2014 (UTC)

This may (or may not) be a good time to review how we deal with NRHP inconsistencies in general. Most of us run into NRHP classifications that just don't seem to make sense, or are done in 2 or 3 different ways, e.g.

• names for the same site that are different for the NRHP and NHL
• HDs that contain other HDs, or other sites sometimes, but other HDs have different HDs inside them
• A new HD formed out of 2 other HDs (all 3 listed)
• Buildings on the list 20 years after they were destroyed (and variations)

Maybe it's time to review our general response to the NRHPs inconsistencies.

Smallbones(smalltalk) 19:47, 9 February 2014 (UTC)

Differing NR/NHL names aren't a problem: we can use the NR name in the NR lists and the NHL name in the NHL lists, and in the infobox, we use the NHL name because it's a higher designation. When an HD is contained in another HD, or when it's formed out of other designations, or when it contains one or more individually-listed sites, we shouldn't have a problem: unless it's specifically marked as being a boundary increase (whether in the name, or the documentation says so), we shouldn't assume that it is. After all, properties inside HDs sometimes get listed individually later; for example, the Crawford-Whitehead-Ross House is a CP to the Madison Historic District (NHLD), but it got individually listed 19 years after the district was declared, because the nominators and the Indiana SHPO decided that it warranted additional designation by itself. And as far as destroyed-and-still-listed, it's not a problem for our listings, as they've just not caught up. Nothing wrong with saying that a property is still listed on the Register 40 years after its destruction if we can verify that it was destroyed and that it's still in NRIS. Nyttend (talk) 20:32, 9 February 2014 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── In going through the duplicates, I've come across a few that I'd like to get some more eyes on:

1. Unnamed Battery #2 in Charleston Co., SC: I think this may not actually be listed. The site not in Focus/Elkman, only Unnamed Battery No. 1 appears in the 1982 listings, and the MPS form shows "Substantive Review" but no signature like the other SRs.
2. Lehigh Canal in various counties in Pennsylvania: there's at least 5 refnums for this site, and not being familiar with the area, I'm not sure what corresponds to what. Also, should each listing have all of the refnums, or only the one for its section?
3. Martha's Vineyard Campground / Wesleyan Grove in Dukes Co., MA: These are noted on the list as duplicates and point to the same article, so it may just be a renaming and NHL-designating, but since I'm not sure, I didn't combine them.
4. Boston Common and Public Garden in northern Boston, MA: these were listed together, and then separately designated NHLs; should the original listing be deleted?
5. Also, the aforementioned Druid Hills Historic District in Atlanta.

Spyder_Monkey (Talk) 05:11, 12 February 2014 (UTC)

I looked into the Unnamed Battery #2 listing, and it gets even more confusing. The South Carolina SHPO lists all three as being on the NR, though, which complicates things. My guess would be that Unnamed Battery #2 isn't actually listed, but got put in the state database along with the rest of the MPS by mistake, in which case it should probably be removed from the list. I know Illinois' state database says that a few properties with owner objections are listed, so I wouldn't be surprised if it happens in other states too. (It doesn't help that "Unnamed Battery" is distinct from "Unnamed Battery #1" and "Unnamed Battery #2"; there had to have been a better way to name those.) TheCatalyst31 ReactionCreation 05:32, 12 February 2014 (UTC)
As far as Boston, no: the HD was listed on the Register, and it's not been removed, so we shouldn't say that it has been. Perhaps NPS should remove it, but that's not our job. Probably best just to redirect it to Boston Common, since that's the first name in the title. Nyttend (talk) 07:11, 12 February 2014 (UTC)
The Martha's Vineyard Campground/Wesleyan Grove pair highlight a question I posed a while back here: are the lists we create of listings, or of listed entities, since these are not quite the same thing? There's probably a small argument to be made that what we actually provide are lists of listed entities, since we routinely fold things like boundary increases out of the lists. Under that idea, duplicated listings should also be folded together. On the other hand, boundary changes are arguably administrative entries (we don't record documentation changes and other administrivia from the weekly lists), and aren't really "listings". (I think what happened with this specific pair is that it was first NRHP-listed under one name; then when the NHL listing was processed, a second NRHP listing and the NHL listing were added. There are three entries in Focus for this place, two NRIS, one NHL.) Magic♪piano 08:32, 13 February 2014 (UTC)
We're providing cleaned-up lists of listings. This is why we retain entries for sites that have been destroyed but haven't been delisted, and why we use the sometimes-funky NRIS names in the lists, even when we'd never use those names for article titles. I say "cleaned-up" because we're implementing changes that have been made after listing (the boundary increases), since the nature of the listing has changed, and because we're fixing errors that we find: places listed in the wrong town (e.g. a recent new listing in Dayton, Ohio isn't on the Dayton list, because it's in the adjacent city of Oakwood), typos or outright errors in addresses, and duplications. We've started with NRIS, modified it with changes that announced by NPS, and fixed all sorts of errors that we've found. Resolving duplications is just another kind of error-fixing. Nyttend (talk) 04:19, 14 February 2014 (UTC)

I just found another repeated listing while trying to fix the refnums in image tags. In the list for Albany County, New York, there are separate entries for Verdoy School and Verdoy Schoolhouse; however, the article says these are the same building, which was apparently delisted and relisted after a move. I'm assuming those two entries should be combined, but what listing date (and refnum) should we use in the list? TheCatalyst31 ReactionCreation 09:18, 17 February 2014 (UTC)

I've seen this in three other places: see the Gramelspacher-Gutzweiler House (Dubois County, Indiana), the Kent Jail (Portage County, Ohio), and the John Marshall House Site (Gallatin County, Illinois). All three lists provide the refnum and date for the second listing; further notes:
• The Portage County list gives details about listing/delisting/listing, based on stuff that's in the Kent Jail article.
• The Dubois County list doesn't mention a thing about delisting, perhaps because we don't have an article on the G-G House. NRIS doesn't mention the delisting, probably because it happened before they started assigning refnums, and there really wouldn't be a point to giving a first-listing refnum to a delisted property after it got relisted. I wouldn't know about the delisting if it weren't mentioned on the third page of its nomination.
• The Gallatin County list doesn't mention delisting, although the Marshall House article does. Basically, they listed the house, it got destroyed, and the site was relisted as a site. Again, there's no refnum for the original listing, probably since it's pointless.
Since the Verdoy listings are seemingly both the same building, I'd suggest merging them and using the current name, refnum, and date. Nyttend (talk) 23:15, 17 February 2014 (UTC)

## Baltimore City College

I have nominated Baltimore City College for a featured article review here. Please join the discussion on whether this article meets featured article criteria. Articles are typically reviewed for two weeks. If substantial concerns are not addressed during the review period, the article will be moved to the Featured Article Removal Candidates list for a further period, where editors may declare "Keep" or "Delist" the article's featured status. The instructions for the review process are here. DrKiernan (talk) 19:27, 14 February 2014 (UTC)

## NRHP in Connecticut categories

When I was trying to move an article about an NRHP site in Middlesex County, Connecticut to a specific NRHP category, I found out there was no such category. Instead I looked up the Category:National Register of Historic Places in Connecticut by county, and found the only items in that category are county lists! Why hasn't anybody made county-specific categories, and will any be made in the future? ---------User:DanTD (talk) 16:46, 15 February 2014 (UTC)

Probably because nobody got around to it, so you can be BOLD. There were only scattershot county categories for Massachusetts before I got going there. Magic♪piano 17:21, 15 February 2014 (UTC)
For most states, we do not have county-specific categories, but it is certainly a good idea to create and populate them.--Ymblanter (talk) 20:51, 15 February 2014 (UTC)
Well, I just created seven county categories, and moved one to the CT-by county category. Whoever can move sites to the proper category, go and do it. ---------User:DanTD (talk) 02:34, 16 February 2014 (UTC)
Ohio, for example, is very spotty; Franklin County, with the third-highest number of sites statewide, has none, but Meigs County with nine has a category. This is basically the result of my article-writing styles and preferences: when I'm writing a bunch of articles on places in the same county, I'll create a category for them, but I won't do it otherwise. Nyttend (talk) 07:04, 16 February 2014 (UTC)

## Refnum search links in list articles

I've just added a photo of a recent listing to its list article. While there, I noticed that each refnum in the lists is EL'd to the Focus search result for the number. Unfortunately, recent listings don't appear to be in Focus, so the link leads to a no-results-found message. The EL seems to be an automatic feature of the template, with no way to turn it off for individual properties in the list; moreover, when I tried to add a citation to a source that gave the refnum for this particular property, it apparently wasn't compatible with the template syntax. Any way that this can be fixed? Assuming that NPS doesn't plan to add recent listings to Focus, the situation's only going to get worse as more properties are listed. Ammodramus (talk) 14:04, 22 February 2014 (UTC)

Why would you assume NPS doesn't plan to add recent listings to Focus? The record will eventually be in NRIS, so the link will eventually point to the right place. Would it suffice to modify the note for the listing date/refnum column to include something along the lines of

"If the link returns a 'no results found' screen, that does not necessarily mean the property is not listed on the National Register. The NRIS database only includes a skeletal record of properties listed through August 2012. To verify that a property was listed after this date, check the weekly listings posted by the National Park Service."?

It may also be desirable to use {{NRHP Weekly List}} to link the date to the weekly list instead of the refnum to the database in listings after August 2012. For example in your Farmers State Bank case, we could drop the link to the refnum and include instead December 31, 2013. This link is not always accurate, especially since the NRHP gets lazy on Fridays and sometimes includes that day's listings on the next week's list. It's pretty accurate for most listings, though.
I've also just found a page to search through the 2013 weekly lists, and this link seems to bring up a record for Farmers State Bank. Unfortunately, it appears that still leaves a gap for properties listed between August and December 2012.
I personally would be fine with just adding the note to keep it less complicated, but any of the above can be done if consensus sways that way.--Dudemanfellabra (talk) 17:30, 22 February 2014 (UTC)
Agree with Dudeman. NPS is getting more and more behind with recent stuff as they scan old stuff in more and more states (the newest KY nominations on Focus are several years old), but presumably once they get done with all the states, they'll be able to go back and catch up, getting everything into Focus. Mentioning the newest listings in Focus is a matter of updating the database, which happens irregularly, but they've still done it year after year; we should expect it to get updated. And finally, they occasionally have holes for far-older properties; for example, location 80001629, a fire station in Louisville, has just the generic "The PDF file for this National Register record has not yet been digitized" page. Nyttend (talk) 00:50, 23 February 2014 (UTC)
I've considered raising this question before, since a new editor thought a new listing I added wasn't listed since it didn't have a working Focus link. I think the footnote is fine, since linking to an incorrect weekly listings page might be even more confusing than linking to a "no results" page. My other thought is to disable the link entirely for any listings after August 2012, assuming that's technically possible, and only add it back once Focus is updated; the footnote would probably still be a good idea in this case. As an aside, it seems like NPS is getting more behind about things in general, not just for recent stuff; they haven't updated the status page since last spring. TheCatalyst31 ReactionCreation 01:09, 23 February 2014 (UTC)
I'd be inclined to support TheCatalyst's suggestion of disabling the link for post-Aug2012 listings; I assume that this would allow us to insert citations manually, which we can't seem to do right now. (I was planning to cite this page rather than the weekly listing in support of the refnum for this property.) Assuming, of course, that this wouldn't cause too many headaches for DMFB, who's been doing valuable work for this project. Ammodramus (talk) 02:22, 23 February 2014 (UTC)
Is everyone happy with this? The relevant test cases are the second and third ones on the list. Anything listed after August 31, 2012 will not have a link. When Focus is updated, we can simply change the cutoff date in the template. To add a citation to the refnum, use the `|refnum_extra=` paramter, akin to the `|date_extra=` that already exists. Also I added an option to remove the link on any property by setting `|nolink=yes`. If that's ok with everyone, I'll make the change go live soon.--Dudemanfellabra (talk) 03:01, 23 February 2014 (UTC)
This looks great to me. Many thanks to DMFB for his work on this. Ammodramus (talk) 12:07, 23 February 2014 (UTC)
Can the Focus linking please be disabled for the states (such as Tennessee) for which there are no files in Focus? It is profoundly unhelpful to send people to thousands of URLs that we know have no useful content. I'm hoping for coding that would allow these links to be disabled now, then enabled if and when the records get digitized. --Orlady (talk) 14:46, 23 February 2014 (UTC)
The point of the Focus links is to send readers to the database to verify that the number we claim is in fact the reference number of the property, not to send them to the digitized nomination forms. The links to the nomination forms (be they in Focus or some state source) should be found in the articles themselves, not the lists. If you really think the Focus link is unhelpful for states such as Tennessee (I disagree with you), then you could make use of the `|nolink=` parameter that is in the works now.--Dudemanfellabra (talk) 19:54, 23 February 2014 (UTC)
OK. I concur that the links to Focus aren't totally useless, so I guess it's OK to keep them. --Orlady (talk) 17:55, 24 February 2014 (UTC)

So... No objections? I'll give this another day.--Dudemanfellabra (talk) 17:25, 24 February 2014 (UTC)

It looks good to me. I say go for it. TheCatalyst31 ReactionCreation 20:05, 24 February 2014 (UTC)
Changes implemented. If you still see a link for a site listed after August 2012, WP:PURGE the page and everything should work. Thanks!--Dudemanfellabra (talk) 20:22, 25 February 2014 (UTC)

### Former listings

Apparently my edit caused some errors with former listings that included more than one date (i.e. listing date and removed date) in the date parameter. While I've taken care of that now, it begs the question, why do we include two dates in one column? Shouldn't we just have two separate columns, one for listing and one for delisting? Also, I'm pretty sure no delisted sites have records in Focus, so we should probably disable the Focus link if type=NRHP-delisted.--Dudemanfellabra (talk) 02:05, 26 February 2014 (UTC)

Would that even work with our current coding? If you want to produce new code to add an extra column, I would have no objection — it takes additional horizontal space, but we don't generally have extensive notes in the Summary field for delisted properties, so the space shouldn't be a problem. Nyttend (talk) 02:33, 26 February 2014 (UTC)
If we moved to two columns, we would have to add a second parameter, e.g. `|delisted_date=` and move the delisting dates to this parameter in all the existing former listings templates. It would be quite a task, but there aren't that many delisted properties... definitely not as many as there are listed.--Dudemanfellabra (talk) 07:21, 26 February 2014 (UTC)
I thought it would be a lot more work than that; I'd be willing to help with the grunt work. Could you have the bot produce a complete list of lists in which {{NRHP row}} appears with `|type=NRHP-delisted`? It would seem like an easy starting spot, since we wouldn't have to check all 3000+ lists before working on it. Nyttend (talk) 13:22, 26 February 2014 (UTC)
From the database:
```mysql> SELECT type, COUNT(type) FROM `monuments_us_(en)` GROUP BY type LIMIT 100;
+---------------+-------------+
| type          | COUNT(type) |
+---------------+-------------+
| HD            |       13671 |
| NB            |           8 |
| NBP           |           2 |
| NHL           |        1958 |
| NHLD          |         406 |
| NHP           |          19 |
| NHS           |          67 |
| NMEM          |           9 |
| NMON          |          29 |
| NMP           |           8 |
| NRHP          |       72340 |
| NRHP-delisted |        1386 |
+---------------+-------------+
12 rows in set (2.20 sec)
```
The list of delisted items is available here (here). Multichill (talk) 17:17, 27 February 2014 (UTC)
Awesome! Thanks for that list, Multichill. I'll work on coding a change to the template which shows the extra column if `|delisted_date=` is set. Then we can go around and move all the dates to that parameter and there will be no breaking in the interim. I'll let you know when I get that working in the sandbox.--Dudemanfellabra (talk) 19:03, 27 February 2014 (UTC)
Took less time than I thought. I put code in the sandbox that you can see in action on the test cases page. The relevant case is the second delisted property at the bottom of the section, which you can compare to the case above it. I've taken the delisting date and put it in `|delisted_date=`, which caused a new column to appear (and also turned off the Focus link). To handle the new column, I've added `|splitdate=yes` to the {{NRHP former header}} template (which is strangely unprotected btw), making it split as well. This is the procedure to follow for updating all the county lists. When all have been converted, I'll simply remove the splitdate parameter and default to being split... that is, unless some tables want to remain unsplit for some reason. As an aside, I also added `|delisted_date_extra=` so that we can put any references for delisting there. If there are no objections I'll make the code go live in the next day or so.--Dudemanfellabra (talk) 19:45, 27 February 2014 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I've made the change to {{NRHP row}}. Now we can start going through the counties in the above lists. I won't have much time for the next few days/weeks (and most of that will be spent working on another project I have in the works). I'm more than willing to help, but I just won't be able to do so until I get some more free time.--Dudemanfellabra (talk) 00:57, 1 March 2014 (UTC)

### Implementation

Dudemanfellabra, I decided to start implementing these fixes in Ohio, so I made this edit and this edit. Look at the mess that resulted. What did I do wrongly, and what should I have done? Nyttend (talk) 02:03, 1 March 2014 (UTC)

I edited the first list to have the correct format. The `|date=` parameter cannot be left blank, but since the original listing date for these properties was unknown, I just added the year based on the reference number along with a {{cn}} tag in the `|date_extra=` parameter since we need a source for those dates. The general procedure to fix a table is to add `|splitdate=yes` to {{NRHP former header}} and then move the delisted date to `|delisted_date=` in each row. The `|date=` parameter cannot be empty, so something needs to go there, thus my addition of the listing year. It has been my experience, though, that most delisted properties have original listing dates already in the tables.--Dudemanfellabra (talk) 17:04, 1 March 2014 (UTC)
Can we get the delisted date column centered like the listed date column? 25or6to4 (talk) 14:59, 2 March 2014 (UTC)
I've added the extra column to everything in Indiana, Ohio, and Pennsylvania. The issue of listing date in tables varies from state to state: most Indiana locations had the original date, while most Ohio lacked it. I've put in "Unavailable" instead of a facttagged year: it doesn't presume anything, whether a specific year or the idea that the date has been lost, and it does nothing except for telling the reader "We haven't found it yet". 25or6to4, I tried, but I can't figure out where the <center> tags should go. Would you mind doing it? If you dump the code into a sandbox and notify me, I'll be happy to copy it over to the template. Nyttend (talk) 18:21, 2 March 2014 (UTC)
Done--Dudemanfellabra (talk)

## Popular pages tool update

As of January, the popular pages tool has moved from the Toolserver to Wikimedia Tool Labs. The code has changed significantly from the Toolserver version, but users should notice few differences. Please take a moment to look over your project's list for any anomalies, such as pages that you expect to see that are missing or pages that seem to have more views than expected. Note that unlike other tools, this tool aggregates all views from redirects, which means it will typically have higher numbers. (For January 2014 specifically, 35 hours of data is missing from the WMF data, which was approximated from other dates. For most articles, this should yield a more accurate number. However, a few articles, like ones featured on the Main Page, may be off).

Web tools, to replace the ones at tools:~alexz/pop, will become available over the next few weeks at toollabs:popularpages. All of the historical data (back to July 2009 for some projects) has been copied over. The tool to view historical data is currently partially available (assessment data and a few projects may not be available at the moment). The tool to add new projects to the bot's list is also available now (editing the configuration of current projects coming soon). Unlike the previous tool, all changes will be effective immediately. OAuth is used to authenticate users, allowing only regular users to make changes to prevent abuse. A visible history of configuration additions and changes is coming soon. Once tools become fully available, their toolserver versions will redirect to Labs.

If you have any questions, want to report any bugs, or there are any features you would like to see that aren't currently available on the Toolserver tools, see the updated FAQ or contact me on my talk page. Mr.Z-bot (talk) (for ) 05:18, 23 February 2014 (UTC)

## Collaboration? Kenton Commercial Historic District (or East Skinner Butte Historic District)

Would any project members be interested in contributing to this project? WikiProject Oregon hosts monthly photography campaigns. For February, the subject of focus is Portland's Kenton Commercial Historic District. As you can see, many of the contributing sites have been photographed, and new categories have been created at Wikimedia Commons. There are just a few days left for the campaign, but any assistance with creating an article for the district would be much appreciated. Consider my request one WikiProject member attempting to leverage collaboration with another WikiProject. :) Content creators/writers are especially welcome; help with district maps is also great. Please feel free to use newly-uploaded images from this district, and to add your name to the list of participants on the project page.

If it is too late for this particular project, please consider doing the same for our March project, which focuses on Eugene's East Skinner Butte Historic District. Similarly, we hope to create a new Wikipedia article and photograph contributing properties to the district.

Again, any assistance would be much appreciated! --Another Believer (Talk) 23:36, 24 February 2014 (UTC)

I made this map of the Kenton district if it's of any use. I included the boundaries of the larger Kenton Conservation District as well.--Dudemanfellabra (talk) 22:46, 27 February 2014 (UTC)
Thank you so much, Dudemanfellabra! Your assistance is much appreciated. I added your contribution to the project page as well. --Another Believer (Talk) 22:57, 27 February 2014 (UTC)

For those who may be interested you can view photos uploaded so far at this link. Thanks! --Another Believer (Talk) 16:34, 12 March 2014 (UTC)

## NYSHPO site problems (again)

Can someone explain to me in simple terms how to get the ji.jar file to work? I've downloaded it, but I cannot get the PDF files to render. Thanks in advance (see Archives p. 58 for background on same topic)--Pubdog (talk) 01:34, 5 March 2014 (UTC)

## Automatic duplicate stats on Progress page

The WP:NRHPPROGRESS page has slowly become more and more automated in its gathering of statistics about the state of things related to articles under the scope of this project. Via scripts, we can now find information about each and every county list in the country in about two hours total, and we can generate the maps automatically as well. In fact, up until this point, the only thing that wasn't automated was the tallying of duplicates; we still had to gather information about them and input it by hand. Because of this, much of the duplicate information on the Progress page is woefully out of date. Well I've been working on getting that last little thing taken care of, and I think I can finally say it's working. Using my bot which scans for NRIS-only pages, I have compiled a list of all duplications across county and state lines here, which I then use to create the tables found here (that page will be moved eventually, but I wanted to make sure it worked before moving out to a permanent location). The information in these tables is encoded in a hidden table at the top of the page (viewable if you click to edit the page) and can be transcluded directly into the tables on the Progress page. As an example of this transclusion, I have put the national table and the Alabama table here and used the automated duplicate information in the relevant rows.

What I'm asking is for people to go over the information in the tables and see if it is indeed correct. If there are any duplicates included that shouldn't be, that is probably due to an error in the reference number included on one or more of the relevant county lists. I have already found one incorrect duplication in Colorado that I have fixed, and I expect there to be more in other states. It is also possible, comparing to the manually entered duplications on the Progress page, that my code has missed some duplicates. If this is the case, could you let me know here? I will try to see what is wrong.

After we verify that the information is correct, I will edit the Progress page to transclude the information in these tables, and the entire thing will be automated.. finally. Thank you for your patience with this project. I will probably still tinker around with it, but as far as I can tell, it is as automated as it is going to get!--Dudemanfellabra (talk) 19:09, 15 March 2014 (UTC)

In Michigan, one of the dupes (Copper Peak) is not really a dupe, but was assigned the wrong refnum in the Gogegic County list. I fixed the county list, and presumably it will fall off the dupe list. Andrew Jameson (talk) 19:31, 15 March 2014 (UTC)
I corrected the following Massachusetts, Virginia, and New Hampshire entries after seeing this data in your sandbox:
To the best of my knowledge, all of the other duplications in Maine, Massachusetts, and Rhode Island are legit, including all uses of Blackstone Canal. Magic♪piano 20:29, 15 March 2014 (UTC)
The dups in Wisconsin are both correct. Royalbroil 21:08, 15 March 2014 (UTC)
The Nebraska dupes are all correct, but there's one missing: Site No. JF00-072, which is located at the four-way intersection of Thayer and Jefferson counties in Nebraska and Republic and Washington counties in Kansas. Ammodramus (talk) 21:19, 15 March 2014 (UTC)
Cocke-Martin-Jackson House (#97000799), listed as being in both Rankin County, Mississippi and Rhea County, Tennessee, is invalid. Neither of those counties is anywhere near a state line. Elkman shows that property as being located in Rankin County. The other Tennessee items on that list appear to be correct. However, I haven't yet checked for omissions. --Orlady (talk) 22:56, 15 March 2014 (UTC)
The in-state Texas listings are correct. One listing between Texas and Louisiana, the Burr's Ferry Bridge #98000563, is missing from the multistate listing. 25or6to4 (talk) 22:58, 15 March 2014 (UTC)
I found a Tennessee-related omission. Jesse Whitesell House (#06001199 or possibly #77000619) is missing from this list. It is listed on the Progress page as crossing the Kentucky-Tennessee line. Apparently the initial listing was for the building, which is in Kentucky, and a boundary increase called "Jesse Whitesell Farm" added surrounding land located in both Obion County, Tennessee, and Fulton County, Kentucky. --Orlady (talk) 23:20, 15 March 2014 (UTC)

Thank you for fixing/verifying those duplicates. The ones you fixed were removed after the latest bot run.

Site No. JF00-072 is included on the list. It is included in the multistate section (halfway down the table; one of the only redlinks), the Kansas section (last in the table), and the Nebraska section (also last in the table). It was even there before the last update. Maybe you just missed it?

@Orlady: Thanks for fixing the MS-TN incorrect duplicate. As for the Whitesell house, the reason it is not included is that the site is listed with two different refnums in the two counties. My guess is this is because only the boundary increase is actually in Kentucky, not the "original" listing. This is a kind of peculiar case because, while it is technically the same property in both counties, the listings are not really duplicated.... so should we count it as one? My opinion is yes, we should count it as a duplicate, and the Kentucky list should be changed to have the old 1977 refnum. Either that or change the Tennessee list to have the 2009 refnum (which strangely starts with 06.. must have been a delay in the listing process). Regardless, if two sites on different lists don't share a refnum, my code won't count them as a duplicate.

@25or6to4: Burr's Ferry Bridge is another peculiar case. It seems the bridge was listed twice in two different states on the same day with two different reference numbers. Using Elkman's tool as the source, the refnum 98000563 shows up as in Louisiana and 98000562 in Texas. Those are the two reference numbers used on their respective lists here as well, and just like Orlady's case, because they don't have the same reference number, my code won't county the as a duplicate. This is a little more tricky to deal with, though. I don't like the idea of using one of the two reference numbers as the primary because it's technically two different listings.. but then again it's obviously the same bridge listed twice. I'll defer to others' opinions on this one. I'll just say the folks at the NRHP never cease to amaze me with their illogical antics.

I'll continue to look over these for the next few days and refine the code if necessary, but all the errors so far seem to be human rather than coding. Keep them coming if you find anything else, though; especially if what's already on the Progress page doesn't match my output. Thanks for all the help!--Dudemanfellabra (talk) 08:31, 16 March 2014 (UTC)

I'm with Ammodramus on this one. Site No. JF00-072 isn't showing up in the Kansas and Nebraska sections for me, though it is showing up in the multi-state section. If I try to edit the Kansas and Nebraska sections, nothing for that site shows up in the wikitext, so it's not some kind of weird formatting issue; I'm really curious as to how you're seeing that listing. I suspect this is an overall issue with multi-state duplicates that span multiple counties in a state, as neither of the two listings for the George Washington Memorial Parkway is showing up in the Virginia section either. TheCatalyst31 ReactionCreation 08:48, 16 March 2014 (UTC)
Let me be clear. Site JF00-072 doesn't show up in the state sections of the list of duplications at User:NationalRegisterBot/AllNRHPPages/Duplications. It does, however, show up correctly in the tables at User:Dudemanfellabra/Sandbox. Is this true for everyone? Because if it isn't, something really weird is going on here. The tables are what we should be checking, not the raw list. Hope that clears up any confusion.--Dudemanfellabra (talk) 09:18, 16 March 2014 (UTC)
Ah, I was looking at the list. The site shows up fine in the table. TheCatalyst31 ReactionCreation 11:06, 16 March 2014 (UTC)