>> Yes, it might be *nice* to have this sort of information in the
>> catalog--it would
>> be nice to be able to tell someone where they can buy a copy of a
>> certain book,
>> for instance--but the system is not made for that.
>
>...
>
>That very much depends upon what 'the system' is... We're not necessarily
>building a library catalogue here, or a museum collection management
system,
>or a database of news feeds. We're creating a framework that can be used
for
>the *discovery* (and retrieval) of resources.
>
Forgive me if I am slightly off the point, but once the *discovery* has been
made, the person wishing to view the resource/book/webpage will *retrieve*
a copy from the library/institute which holds it. Any further information
about the resource/book/webpage, i.e. how to contact the author, how to buy
a copy would be contained in the actual resource/book.
Surely their is no need to record any further information about the authors
email/address etc.
Anthony Cranfield
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|