Talk:Knowledge Corridor

Is this needed?
Wikivoyage has a pretty well-defined region structure for New England, and per Project:Geographical hierarchy we generally try to avoid overlapping regions except in cases where they are already well-known and useful for travelers, such as Lake Tahoe (which spans both California and Nevada). I'm not familiar with the "Knowledge Corridor" and so can't comment on whether it's a similar example, but as someone who has traveled fairly extensively in the US, the fact that I haven't heard of this region would seem to be an argument against making an exception for it.

Perhaps the author could explain the goal of this article? Alternately, I'd suggest that this article might be better handled as a redirect to the appropriate existing Wikivoyage region, with the content merged as appropriate. -- (WT-en) Ryan &bull; (talk) &bull; 23:21, 16 April 2011 (EDT)


 * Agreed. I blanked all the listings because they don't belong in a region article, but I don't think we need a interstate region article that basically consists of two cities. I vfd'd this. 01:43, 17 April 2011 (EDT)

Absolutely oppose deletion; please do some research before proposing such things

 * I oppose the deletion. I put a lot of work into the article. I think it's preposterous that someone's ignorance of the region would be a "cause for deletion." A cursory google search will tell you the story behind the interstate partnership between the two cities and the surrounding area. I'm not aware of any other formalized interstate partnerships like this. Is it the uniqueness that objected to? Regardless, it's certainly an entity and most certainly should not be deleted. Search the web for a greater frame of reference on The Knowledge Corridor -- or even Wikipedia.

From that cursory Google search:
 * http://www.hartfordspringfield.com/
 * http://www.hartfordspringfieldnews.com/
 * http://www.valleyadvocate.com/article.cfm?aid=9825
 * http://www.westernmassedc.com/Data__Demographics/knowledgecorridor/
 * http://www.masslive.com/business-news/index.ssf/2010/09/hartford-springfield_partnership_celebra.html -- Knowledge Corridor partnership celebrates 10 years.

With that, I'm going to delete the request for deletion.


 * You can't delete the request for deletion. Please state your opinion at Votes for deletion. The issue is not whether the Knowledge Corridor is a recognized region, but rather the fact that it cannot possibly jive with our established Geographical hierarchy. (WT-en) texugo 02:42, 17 April 2011 (EDT)


 * well then perhaps the geographical hierarchy needs some re-structuring--right? Furthermore, if you can arbitrarily put up a request for deletion, then why can't I just as arbitrarily remove it? If you're arguing for a hierarchy that won't accomodate the designation "Knowledge Corridor," a legitimate designation as noted above, then I suggest that we find a way to accomodate the designation rather than delete the entire article. The latter seems ridiculous in light of the facts.


 * Four points:


 * If you look at the nomination on the Project:Votes for deletion, I think (WT-en) texugo is actually proposing that it be merged or redirected rather than deleted. The VFD page is generally used for such discussions.
 * The concerns that have been raised aren't that it's not a valid region, but that it doesn't fit into the existing Project:Geographical hierarchy for New England. See specifically Project:Geographical hierarchy, which spells out why we try very hard to avoid overlapping regions.
 * Please don't try to end a VFD by fiat - while it can seem cumbersome, the Project:Votes for deletion page has a well-established procedure for coming to some consensus about what to do with nominated articles.
 * If you'd like to propose changes to the hierarchy please do so, but as noted on the Project:Geographical hierarchy we really do try to encourage people to discuss such changes before making them to avoid confusion.


 * -- (WT-en) Ryan &bull; (talk) &bull; 02:50, 17 April 2011 (EDT)
 * Fair enough. I am new to Wikivoyage, and created this page after I searched for "Knowledge Corridor" (I'm currently staying with family in the region) and was surprised to find that it didn't exist on here. I don't think that a redirect to New England would do, because New England is vast. Perhaps if it was drawn on a map of New England and appropriately described then it could be redicted, or perhaps if it were redirected to "Connecticut River Valley" (which currently describes only northern and central Connecticut,) that would work; however, that article would have to be expanded to accomodate the entire Connecticut River Valley, which (unfortunately for all the classification hierarchies here) stretches from from the Canadian border south to the Long Island Sound. Perhaps needless to say, it encompasses several distinct regions. The Knowledge Corridor itself is distinct within the Connecticut River Valley. From what I understand, it does not extend past Middletown in the south, nor Northampton-Amherst in the north. It is a region about fifty miles in length and twenty miles wide within the CT River Valley, which includes parts (but not all) of the Pioneer Valley, (which itself includes the Five College Area, from which I'm currently writing to you,) and part (but not all) of Connecticut's section of the Connecticut River Valley. How to you ferret out all of these overlapping regions--it's a great question. That said, I don't think that deleting the region-a dynamic and revitalizing one at that--or consigning it to a obscure one-line reference on the New England page is appropriate.


 * In my opinion, if you want to redirect "Knowledge Corridor," then at least it ought to be mentioned on the pages of Hartford, Springfield, their respective states, and their respective regions (e.g. New England, CT River Valley, Pioneer Valley, Five College Area.) These are the areas involved.


 * What about turning this page into a disambiguation page (example: West Coast) that essentially says "The Knowledge Corridor is a region of New England that encompasses the following"? In that way we wouldn't end up with a multi-state region as part of the hierarchy, but there would be an article for people such as yourself who search for one? -- (WT-en) Ryan &bull; (talk) &bull; 12:20, 17 April 2011 (EDT)
 * Incidentally, this sort of situation is exactly why I proposed a extended disambiguation or "meta-region" template a while back, but it seems that that idea was shot down. (WT-en) texugo 12:39, 17 April 2011 (EDT)


 * Possibly this article could be worked into Pioneer Valley, however I think this corridor extends beyond P.V. in both directions (see following section). In general the consensus regional structure can be [Procrustean for some articles that should be written and posted without necessarily conforming.  I think it should be left to authors to decide whether a disambiguation format is suitable. [[User:(WT-en) LADave|(WT-en) LADave]] 17:13, 18 May 2011 (EDT)

Synonymous with "College Highway"?
This is a series of state highways all numbered Route 10, however extending further south to New Haven, Connecticut (Yale University) and north to Hanover, New Hampshire (Dartmouth College) in New Hampshire. The concept is somewhat dated, reflecting the situation decades ago when men from the Ivy League and women from Seven Sister colleges tended to date each other to the exclusion of others. Nevertheless Yale and Dartmouth remain notable parts of the education/knowledge industry and should be included. (WT-en) LADave 16:45, 18 May 2011 (EDT)

VFD Discussion
Overlapping interstate region article for the Hartford CT-Springfield, MA urban area, created mostly by copying things from those two articles and slapping them together. I think a redirect to New England along with a short note there would suffice.
 * Redirect - (WT-en) texugo 01:49, 17 April 2011 (EDT)
 * Keep (for the moment). The anonymous user who created this region did so in good faith, and will (hopefully) either make the case for integrating it into the existing hierarchy or redirecting it.  However, if that clarification isn't forthcoming then I'd be in favor of a redirect to New England since multi-state regions break the geographic hierarchy quite badly without offering much benefit. -- (WT-en) Ryan &bull; (talk) &bull; 02:53, 17 April 2011 (EDT)
 * The fact that it crosses state lines rather precludes integration, don't you think? (WT-en) texugo 02:56, 17 April 2011 (EDT)
 * Having let this bake for a while, I think the right solution is to turn the page into a disambiguation-like page that simply points to the citys/towns/regions that this extra-hierarchical region encompasses ("The Knowledge Corridor is a region of New England that includes the following towns and cities"). This would keep the article around to catch anyone searching for "Knowledge Corridor", but then point those users to the proper Wikivoyage articles for information about what is contained in that region without adding confusion to Wikivoyage's regional structure. -- (WT-en) Ryan &bull; (talk) &bull; 11:49, 29 April 2011 (EDT)


 * Keep - The Knowledge Corridor is an official designation for the region surrounding the cities of Springfield, Mass, and Hartford, Conn. Just as there's a "Research Triangle" in North Carolina, there's the "Knowledge Corridor" along the Connecticut River Valley. It just so happens to straddle two states. From what I read on the discussion page, the reason why the article (which I worked hard on) would be deleted is because it doesn't jive with wikivoyage's current classification hierarchy. Rather than delete a page dedicated to a whole region, I suggest fixing the unaccomodating hierarchy... Otherwise wikivoyage will keep on deleting legitimate articles for the sake of preserving a hierarchy that might not be worth preserving (from the sounds of it.) Is the problem here that it's an interstate region? I don't get it. What of Kansas City, which straddles state lines? Or St. Louis? —The preceding comment was added by (WT-en) 71.192.97.169 (talk • contribs)
 * The Research Triangle fits neatly into our hierarchy, Kansas City has two separate articles, and the parts of St. Louis in other states have separate articles as well. (WT-en) texugo 04:30, 17 April 2011 (EDT)
 * If an official regional designation and travel destination isn't fitting neatly in the hierarchies of WikiTravel, then in my opinion, the hierarchy is not working correctly to accomodate material it should be able to accomodate.
 * Here are references for those who do not know about the Knowledge Corridor, from a cursory Google search:
 * http://www.hartfordspringfield.com/
 * http://www.hartfordspringfieldnews.com/
 * http://www.valleyadvocate.com/article.cfm?aid=9825
 * http://www.westernmassedc.com/Data__Demographics/knowledgecorridor/
 * http://www.masslive.com/business-news/index.ssf/2010/09/hartford-springfield_partnership_celebra.html -- Knowledge Corridor partnership celebrates 10 years.


 * Here's my reasoning to Keep. I wrote this on the Knowledge Corridor's discussion page and I'll reprint it here so that people who don't visit the former can read the rationale.


 * I am new to Wikivoyage, and created this page after I searched for "Knowledge Corridor" (I'm currently staying with family in the region) and was surprised to find that it didn't exist on here. I don't think that a redirect to New England would do, because New England is vast. Perhaps if the Knowledge Corridor was drawn on a map of New England, appropriately described then its attractions fleshed out, it could be redirected. Alternately, perhaps if Knowledge Corridor was redirected to "Connecticut River Valley" (which currently describes only northern and central Connecticut,) that would work; however, that article would have to be expanded to accomodate the entire Connecticut River Valley, which (unfortunately for the classification hierarchies here) stretches from from the Canadian border south to Long Island Sound. Perhaps needless to say, the CT River Valley encompasses several distinct regions in different states. Perhaps that article as currently constituted is incomplete, describing only Connecticut's 'Connecticut River Valley.' I don't know.


 * Regardless, the Knowledge Corridor itself is a distinct region within the Connecticut River Valley. From what I understand, it does not extend past Middletown in the south, nor Northampton-Amherst in the north. It is a region about fifty miles in length and twenty miles wide (at its widest) within the CT River Valley, which includes parts (but not all) of the Pioneer Valley, (which itself includes the Five College Area, from which I'm currently writing to you,) and parts (but not all) of Connecticut's section of the Connecticut River Valley. How to you ferret out all of these overlapping regions?--it's a great question. That said, I don't think that deleting the Knowledge Corridor region-a dynamic, revitalizing region, with many points of interest--or consigning it to an obscure one or two-line reference on the "New England" page is appropriate. That would barely scratch the surface.


 * In my opinion, if you want to redirect "Knowledge Corridor," then at least it ought to be mentioned on the pages of Hartford, Springfield, their respective states, and their respective regions (e.g. New England, CT River Valley, Pioneer Valley, Five College Area, etc.) My ultimate point is that 1.9 million people live in a relatively small geographical swath beside the Connecticut River. If the region views itself as a region, why shouldn't Wikivoyage? Ideally, I'd be able to come here and receive travel tips for the region. —The preceding comment was added by (WT-en) 71.192.97.169 (talk • contribs)


 * For what it's worth, the Wikipedia article says that the "Knowledge Corridor" is "an economic, civic, and cultural partnership between the Connecticut River cities of Springfield, Massachusetts and Hartford, Connecticut; and the cities' surrounding metropolitan areas" that was created by regional boosters in 2000, a trademarked moniker designed to attract investment in the region. I find it hard to believe that any traveller when asked "What are you doing this weekend" would answer with "I'm going to the Knowledge Corridor". That said, we do of course want this area to be thoroughly covered in our guides but, like Kansas City and other places, I'm not sure it will be possible to group these under a regional article. Keeping in mind that we don't want to duplicate listings or information that is already found in the city guide articles, what information do you hope to put here? (WT-en) texugo 04:14, 17 April 2011 (EDT)


 * Keep as an overview with links to the towns for most of the information.
 * On one hand, we don't recommend Procrustes as an innkeeper, and our region hierarchy should not work that way either. This has come up before, for example Project:Votes_for_deletion/November_2009.
 * On the other hand, we do have a hierarchy so we should use it. Most information should go in the town articles.
 * On the third hand (great for holding the flashlight while you work), this is a new user who is actively writing. Don't discourage him or her. (WT-en) Pashley 07:36, 17 April 2011 (EDT)


 * Keep. When reality does not comply with policy, policy is easier to change. &bull; &bull; &bull; (WT-en) Peter (Southwood) Talk 07:17, 28 April 2011 (EDT)
 * Wait a minute... are you suggesting that we abandon our Project:Geographical hierarchy policy? (WT-en) LtPowers 09:49, 28 April 2011 (EDT)
 * Not at all. Merely that where it doesn't work properly, it should be adjusted. The Knowledge Corridor seems to be a regional destination by all criteria that I have seen so far except that it crosses a state line, which makes breadcrumb navigation problematic. The hierarchy policy is useful in almost all cases, but there will be a few where it is not ideal. I can't think of concrete examples, but can easily imagine things like national parks and the like crossing state/province boundaries too. How else can they be accommodated? (two articles is a bit over the top). Breadcrumbing does present a slight difficulty. the simplest solution would be to breadcrumb the region to the same level as the regions it is located in, and exclude the conflicting regions from the path. Cities etc. within the region get breadcrumbed by the most useful region they are part of (usually the state or equivalent). Otherwise a new system allowing for parallel breadcrumb paths and branching would be necessary, and I have no idea if that is even possible. &bull; &bull; &bull; (WT-en) Peter (Southwood) Talk 02:38, 29 April 2011 (EDT)
 * I am still completely, absolutely 100% unconvinced that this is anything but a recently-created moniker useful only for local municipalities trying to attract investment. (WT-en) texugo 03:09, 29 April 2011 (EDT)
 * I agree; it's primarily an economic designation, not a tourism one. No one says "Oh, I'm vacationing in the Knowledge Corridor this summer!"  They're trying to make it a cultural region, and certainly there are similarities, but I don't think it's strong enough to override the state borders.
 * Peter, we do currently have a number of extra-hierarchical regions, like Navajo Nation, as well as regions that are actually (sort of) in the hierarchy but overlap more than one state, like Metro New York. I think Metro New York is awkward and causes all sorts of navigation problems, but Peter F. was a strong proponent of doing it that way (as was done with Chicagoland.  Anyway, that's just an example of the confusion caused when we try to insert these sorts of regions into our hierarchy.  That's not to say it's never possible, but I think such things work best as a redirect or as a brief stub that just covers the basics.  (WT-en) LtPowers 11:40, 29 April 2011 (EDT)
 * There is no prohibition of economic designations for destinations in the listing of non-goals, nor anything else that I know of to specify that articles are aimed exclusively at the non-business traveller. If that is to be the case, it should be spelled out in the policies, preferably somewhere easy to find. &bull; &bull; &bull; (WT-en) Peter (Southwood) Talk 01:08, 1 May 2011 (EDT)
 * Given that we have to pick one or the other, it makes no sense to favor an invented, purely economic region that crosses state lines over more natural travel regions that have come together more organically. (WT-en) LtPowers 12:02, 1 May 2011 (EDT)
 * If that is the choice, I would agree with you, But is it? &bull; &bull; &bull; (WT-en) Peter (Southwood) Talk 13:46, 1 May 2011 (EDT)
 * No, it quite obviously isn't. We do not "have to pick one or the other". This article can act as a supplement to existing articles. It should not grow large; it should be just an overview and most of the information should be in the city articles. However, it does not break the hierarchy, merely adds to it. (WT-en) Pashley 11:55, 24 May 2011 (EDT)
 * This kind of thinking is causing us to slip further and further down the slope away from our directive to resist overlap. We do have to "pick one or the other" as to whether we continue to put stock in our policy of discouraging overlap, or we discard it in favor of letting this kind of thing proliferate. Exceptions made thus far such as Navajo Nation are special cases which were discussed at length before being allowed, but this is no such special case, just a chamber of commerce's recent notion of how best to attract business, and if we allow this, there are all kinds of other extra-hierarchical regions waiting to follow.(WT-en) texugo 12:49, 24 May 2011 (EDT)
 * (WT-en) texugo's argument matches current site policy - except in rare cases the benefits of having a clear regional structure outweigh the benefits of having an article for every named region - see Project:Geographical hierarchy which states "If we have overlapping guides, readers don't know where to go to get travel information, and contributors don't know where to put travel information". That said, I think that the correct solution is to convert this article (and other extra-hierarchical region articles) into a disambiguation-like page containing a list of cities/regions that have related information, which allows us to keep an article for the region in case someone searches for the term in the future. -- (WT-en) Ryan &bull; (talk) &bull; 13:05, 24 May 2011 (EDT)
 * I agree, and I've been thinking maybe we need to formalize a policy for pages that are valid tourism destinations (like Navajo Nation, Erie Canal, bodies of water, mountain ranges, and the like) but don't fit into our geographic hierarchy. We could just lump them under travel topics or disambiguation pages, but as evidenced by continuing discussion, that seems inadequate to many of us.  (WT-en) LtPowers 13:30, 25 May 2011 (EDT)
 * This is why I proposed standardizing a meta-region template as a sort of "expanded disambiguation" category of articles. Discussion on that kind of fizzled, but I still think it's a good idea, because I really think we need a predictable way to handle these situations. Certainly wouldn't mind opening that discussion back up... (WT-en) texugo 21:42, 25 May 2011 (EDT)
 * I rather liked that proposal, though re-reading the discussion now, I see you never answered the questions I had. =)  (WT-en) LtPowers 09:02, 26 May 2011 (EDT)
 * OK. I have now answered that here and hope to re-open some discussion there. (WT-en) texugo 11:13, 26 May 2011 (EDT)

Knowledge Corridor has now been rewritten per this discussion. I think that means we can close this as keep. Does anyone object? (WT-en) Pashley 00:39, 8 June 2011 (EDT)
 * Honestly, I'm still not convinced it's a useful travel region, but I suppose there's little harm in keeping it. (WT-en) LtPowers 09:49, 8 June 2011 (EDT)


 * Leaning delete. Sorry to hold this up further, but... If it's not a useful travel region, then why keep it? The whole concept has to do with marketing and branding for non-travel related purposes, so to me it doesn't seem a good fit for our website. (Furthermore, it's not the only section of the U.S. to call itself a knowledge corridor either, which raises other problems.) --(WT-en) Peter Talk 16:34, 14 June 2011 (EDT)

Result: Kept. This has been open for months, and there is enough sentiment for to "keep" that a deletion does not seem the appropriate resolution. -- (WT-en) Ryan &bull; (talk) &bull; 23:41, 27 July 2011 (EDT)