Tuesday, August 4, 2009
discovery services
Been trying to get my head around these, and articulate why intuitively they make me very uncomfortable.
I think it is down to two reasons:
1) they think they are clever; they attempt to generate search results based on a variety of data, not just what the searcher may have entered into the search box, including such unhelpful things as a user profile, and what you were searching for the last time. At one level it is unnerving as hell; at another its like holding a conversation with somebody who keeps finishing your sentences, but long before they could possibly know what you're going to say. It is a flaw based on the assumption that you couldn't possibly be researching two completely different topics. Consider that during the week, I'm researching the native role in the French Indian wars, and on the weekend I'm shopping for a used car. So in both cases I may search for Pontiac, and will get gibberish in both cases.
2) Pedagogically, they're asking for trouble. In the tradition of google, they will give answers. In the tradition of google, there is no way of knowing if they are useful answers. Moreover, if for example I'm researching a particular topic as a geographer, I expect my results, the articles I find on the Industrial Revolution, to use a geographical approach, and discuss in some detail the Geography of that event. These are important nuances that a first year student might not get, but a prof could / should challenge the students on. They should have been looking through the geographical literature, a known subset of the whole of global knowledge that the discovery layer would give them. This is actually likely to make the work more difficult than it needs to be for the student at this stage. Like google, it seems to me that such searches should be carried out as a last resort, but with the false ease that they offer, almost certainly they will be used a first resort, produce some results that the researcher can live with, and preclude the more in depth and specialised searching we should encourage at the University level.
I think it is down to two reasons:
1) they think they are clever; they attempt to generate search results based on a variety of data, not just what the searcher may have entered into the search box, including such unhelpful things as a user profile, and what you were searching for the last time. At one level it is unnerving as hell; at another its like holding a conversation with somebody who keeps finishing your sentences, but long before they could possibly know what you're going to say. It is a flaw based on the assumption that you couldn't possibly be researching two completely different topics. Consider that during the week, I'm researching the native role in the French Indian wars, and on the weekend I'm shopping for a used car. So in both cases I may search for Pontiac, and will get gibberish in both cases.
2) Pedagogically, they're asking for trouble. In the tradition of google, they will give answers. In the tradition of google, there is no way of knowing if they are useful answers. Moreover, if for example I'm researching a particular topic as a geographer, I expect my results, the articles I find on the Industrial Revolution, to use a geographical approach, and discuss in some detail the Geography of that event. These are important nuances that a first year student might not get, but a prof could / should challenge the students on. They should have been looking through the geographical literature, a known subset of the whole of global knowledge that the discovery layer would give them. This is actually likely to make the work more difficult than it needs to be for the student at this stage. Like google, it seems to me that such searches should be carried out as a last resort, but with the false ease that they offer, almost certainly they will be used a first resort, produce some results that the researcher can live with, and preclude the more in depth and specialised searching we should encourage at the University level.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment