Alexander Johannesen wrote:
>
> I'm not impressed. My rant isn't designed to tick people off, nor to
> say that you are all worthless and are going to die. Why haven't
> anyone picked up the challenges and explained to me in no uncertain
> terms why we need catalogers in the future? It's such a simple
> question, you shouldn't be avoiding it, and there should be plenty of
> easy answers.
>
Easy answers? Obviously not.
This exchange is getting us nowhere, and don't we have to hammer it out
what an NGC will have to be and to do before we should think about
whether or not it will require catalogers to build it, and why and
what for? Who knows, it may require a very different bunch of people,
if any.
So let's finally put the horse before the cart and try to say what
an NGC will have to be and to do. Then, what data model it will
therefore need, and then how to implement it, and finally, what
intellectual input it will then need.
Why not start from a very broad list of the functions of
a catalog. Here is one, for you to pick apart or modify:
Produce reliable results
Clearly display differences
Bring together what belongs together
Present meaningful choices
Locate what users want
B.Eversberg
Received on Fri Apr 23 2010 - 02:57:35 EDT