This is on behalf of the New Members Round Table group on Footnotes.
I’ve been interning for six months now at a library/archive in a museum. Since this was on the side, I haven’t felt right about publicizing it much until some of my contributions showed up online. However, this particular project was intriguing and got me digging through a 1915 directory.
My task is to match 1915 newspaper clippings about historic houses “in Bridgeport and the surrounding vicinity” to actual addresses. It’s surprising how many houses don’t even have a town mentioned. Instead you’d get vague descriptions like “down the street from Honeysuckle and up on Sunspot Hill.” My supervisor pulled the directory for me and showed me how to cross-reference streets to people’s names.
First, I’d skim the article to see if they laid it out: city or address. If not, I’d then jump to the end of the article where the author usually placed the name of the current owner. Then I’d leaf through the directory (always starting with Bridgeport then Stratford) to see if I could find that person’s name. If I’m lucky, there they are and the address vaguely relates in some way to the article.
Then there is the tricky one. This house belonged to Mr. Hatchback for 30 years, but he died last year. His estate sold the house to Mrs. Owens. I can find Mrs. Owens in the directory but does she live there? The directory is actually for 1914, so maybe not. Another one: the house was moved from place A to place B. Then another building was moved to the original location. Where is the house located now? Oh, right. It’s down by the river. Which river? No name.
Am I still stuck? Time to break out my smartphone. If I’m in luck, I’ll find it right away. Otherwise, I’m downloading PDFs of articles related to that area to scan for information. The State Librarian had a nice census done on buildings around that time period, so that’s somewhat helpful. Unfortunately, the addresses are not included so it’s just “Hudson House.” If I’m at this point, I then go to Google Maps and see if I can tell from the article photo if the contemporary building is the same one. Often times it is not, but a few times I’ve struck gold. Most of the houses are from around 1800, but some are rumored to be from closer to the 1600s.
Once I had an answer or my best guess, I’d write it on a piece of paper and lay it on top of the photocopy. If I felt unconfident, I’d mark that address with a question mark.
From the screenshot above, you probably can’t tell much about changes from the finished product to the previous one I wrote about. Oh, you’d be mistaken. Let me show you a little bit about what happened behind the curtain:
The site took around 25 hours to complete. This is despite the fact that I was working on top of a framework that I established three years ago. The issues are numerous such as there not really being a CMS to work with. Any style change I make on the front page will show up on the logged-in homepage. The logged-in version has additional content. This content climbs on top of the content that was already there. So you have to figure out a way to assign classes to the logged in vs. logged out versions of the same tables (yes, tables).
The backend of the site is not divided into one master stylesheet but into many stylesheets per page. Yes, page level. So if I set the background to be X, Y, and Z on the homepage, I had to visit every other page and set up that new background code. It made the process very long and drawn-out.
My favorite part
My coworker sent me the image from the front of their summer reading brochure. I took it apart in Photoshop and added shadows, removed the spotlights, and created a semi-repeating pattern to use as the background. When I added that to the site, I realized I wasn’t happy with it. So I then pulled apart the curtain into multiple layers (with the courtesy of a transparent background and an eraser). I then ran drop shadows over the new individual rows. I then ‘shopped them back together.
What I didn’t incorporate
My colleague’s original design included spotlights. I wanted to add spotlights which would sway gently or slowly warm up. Something cool with CSS3. However, by the time I got to the end of getting it structurally working, I was done. So done.
The above is a work in progress. This is our third year of using Evanced’s Summer Reading software. What I’ve done so far is clone last year’s site and then made adjustments for this one. You can view last year’s theme below. I was in the process of starting to dismantle its interior when I remembered to take the screenshot. So forgive the out of alignment aspects.
Regarding this year’s theater design, I wanted to have a curtain that could be lifted with a click of a button. Alas, it was not meant to be. I could probably have done it if I had full control over the site. Unfortunately, it’s table-based and all I can do is some CSS manipulation. Below is what I believe is this year’s default theme.
I’m having trouble with our design because it’s breaking in Firefox. I’ve tested it in multiple other browsers (including IE) and it looks on fleek. Firefox has been my nemesis for years in this regards. However, I am using Firefox’s 3D model of the divs to help me pinpoint the different parts of the page are on the site. I’ve completely swapped the original two columns so it can get confusing. Also there isn’t a master stylesheet but approximately 50 tiny ones.
Hopefully by this time tomorrow I’ll be able to share the completely redesigned site!