Barry Kline, a member of my ProGen cohort (l to r, Theresa, ProGen Coordinator, me, Barry at SLIG), commented on my ProGen paper in which I used long URLs and disagreed with my use of them. I thanked him for his comments and referred him to my blog posting about URLs. After reading it, he responded. I thought it was a thoughtful response and it changed my mind about how I will approach long vs. short URLs–at least for a while. At the end of Barry’s response (unedited) is where I stand now on this issue. For ease of differentiation, I have placed Barry’s response in italics. Thanks, Barry!
I read your blog post on URL’s, well done and I think you covered the topic thoroughly and you got a lot of great responses. Consisten[cy] is important but so is good judgment and in my opinion that is where this topic falls. So we might just have to agree to disagree on this point! :-)
TinyURL’s are not acceptable – I think we both agree on that.
For me, Ancestry’s full links fall in the same category. They are too long, they completely disrupt the citation and like I said in my comment, unless you have an electronic form of your article, they are useless. Would you sit there and try to retype all of that information into the URL bar of your browser – one space or character error and the person would have to start all over. Not to mention that after the first “/” a URL becomes case sensitive, not everyone realizes that fact. A properly crafted citation should be able to take a reader to the point in a database website. For example a census citation gives you county, ED, page number, family number, etc. nothing more is needed. (And in the case of the Ancestry.com links you are using, if I were “officially” reviewing your article, I would have to go to a library that has Ancestry.com because your links are using Ancestry.com Library Edition. The links produce an error page if I try from home. Which is not a good use of my time as an editor. So I would be relying on the rest of the citation anyway to guide me to the correct location).
On the other hand, your use of the FindAGrave full citation was appropriate. It is a smaller database that has simpler URL naming scheme. For me I try to include the full URL as long as it is not too long – or if trying to explain how I got there would be too difficult.
This is one of those sticky widget type of areas. This is totally just my opinion, and I don’t own a copy of CMOS, but I would find it hard to believe that even they would recommend using full URL’s that are as long as Ancestry’s, which tend to be among the longest I run across. I have made a note for when I am at NGS to look at the portfolio examples and see how they handled URLs.
One of the points that is standing out for me through this discussion is does a full URL add anything to my citation? If the rest of the citation contains enough identifying information that will lead a reader to my exact location, i.e. an EE crafted census record, then I would say No. If my citation does not have enough information either in the main body or in an additional comment, then yes a full citation would be needed. Even though this way of thinking would result in the use of two different types of URLs, the consistency lies in the use of the initial question; does the full URL add anything to my citation?
I think I am rambling so I will stop now and finish my other reviews!! ;-) Again … good job Jill!
Barry raises some good points and let me discuss where my head is at on this issue now…until it changes! :-)
- TinyURLs are out! I agree.
- I think the most persuasive part of Barry’s argument was not the issue of error introduction if the reader had to type the long URL. I was much more persuaded by the argument of whether you get more information about of a long URL or just the homepage URL. In the case of Ancestry, I agree, you do not get any more information out of a long URL than the short one, especially if you include the search terms you used to find the document.
- I disagree with him about the library edition. I believe I should cite what I am looking at and I was looking at the library edition. This is a moot point if you use the homepage URL.
- CMOS clearly states the full URL or the DOI is what you cite. The typical user of the CMOS style manual is an humanities writer who would cite journals and other writings. I suspect they have not run into a URL the length of an image on Ancestry.com.
- I, and others, will have to decide what is too long and what is short. I feel comfortable saying that Ancestry.com’s image URL’s are too long, but I am not sure if half that length would qualify or if 25% of that length would qualify. I would tend to say, for now…Ancestry.com– yes; all the others– I will use a full URL.
One of the things we agreed to do was to review the portfolios at the NGS conference in Richmond and then get together and discuss one more time. So stay tuned for a reprise of that conversation!
Happy Hunting & thanks, Barry!
Since my last posting: put the finishing touches on the draft of the paper for ProGen but will now go back and change the ancestry URLs to a shortened form; turned in my SGS Board materials and report; put the finishing touches on the GPS #2 PowerPoint presentation that I am recording on Wednesday to comply with the application procedures for NGS Conference 2015 Call for Papers, put the finishing touches on the GPS #3 presentation for SGS on the 30 March; drafted another blog; explored the free websites this weekend to see what they had. The Swedish site was interesting but didn’t have the document range of SVAR. Mocavo was unimpressive and I don’t have any direct need for the pre-1758 Irish wills, but I bet there were some folks doing the genealogical happy dance!