I don't know this-- I'm just wondering if we can't put URLs in various parts of
the record, not just the 856. It seems like the 856 should reflect the item
described in 245, and that we could put URLs elsewhere for subparts, related
items and names, etc. I haven't really had occasion to do this, but somehow
using 856 for every kind of URL that relates indirectly to a record is odd.
Any thoughts?
Thanks,
Joanna Fountain
Joanna F. Fountain, Ph.D.
Adjunct Faculty, GSLIS, The University of Texas at Austin
and Database Administrator, Texas Library Connection
*********************************************
Patricia Scott wrote:
> Hello,
>
> The answer Randall supplied below is a good answer for the traditional
> catalogue.
>
> However for a web catalogue, with the advent of article level URLs there
> is a possibility that an 856 tag could be added to the catalogue record
> at the local level to "hotlink" to book reviews in full text.
>
> We should bear this in mind and investigate the electronic resources
> that are being made available to our clientele, usually through the
> endeavours of other staff in our libraries. Many full text databases and
> electronic journals include book reviews, though not all provide article
> level URLs that will make them useful in this way.
>
> Now time to do this would be something !
>
> Patricia Scott
>
> "Randall K. Barry" wrote:
> >
> > I have not seen links made between books and/or literary works in
> > periodicals to their reviews in other publications, but one of the Linking
> > Entry Fields (76X-78X) could be used. I don't think any of fields 760-786
> > is appropriate, so that leaves field 787 (Nonspecific Relationship
> > Entry). The relationship could be established as follows in the record
> > for the work being reviewed:
>
> --
> **********************************************************
>
> Patricia Scott
> Bibliographic Services Librarian
> Barr Smith Library fax: +61 8 8303 4369
> University of Adelaide telephone: +61 8 8303 5373
> Adelaide
> South Australia 5005
>
> ***********************************************************
|