I think this is an important point - the way lcsh.info is structured
opens up some interesting possibilities (e.g. substituting all LCSH
terms in your catalogue with URIs; building a search engine that
'crawls' LCSH and presents a search interface based on this, etc.)
Are there any examples of people using lcsh.info out there to look at?
Owen
Owen Stephens
Assistant Director: e-Strategy and Information Resources
Imperial College London Library
Imperial College London
South Kensington
London SW7 2AZ
Tel: 020 7594 8829
Email: o.stephens_at_imperial.ac.uk
> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_LISTSERV.ND.EDU] On Behalf Of Ross Singer
> Sent: 23 September 2008 14:18
> To: NGC4LIB_at_LISTSERV.ND.EDU
> Subject: Re: [NGC4LIB] Library Technologies and Library
> School (was Commercial Vendors and Open Source Software)
>
> On Mon, Sep 22, 2008 at 5:04 PM, Weinheimer Jim
> <j.weinheimer_at_aur.edu> wrote:
> > and while I personally don't care for the version at the
> lcsh.info site (that's just my opinion), that is irrelevant.
>
> Well, lcsh.info's purpose isn't for making the LC Subjects
> Headings available in a web browseable interface. It was
> designed as a project to model LCSH in SKOS and make it
> available as Linked Data. So instead of using:
>
> 650 _0 |a Semantic Web.
>
> You'd use:
>
> http://lcsh.info/sh2002000569#concept
>
> The former is useless in a web context. Using the latter
> (whether or not you believe SKOS is suitable for LCSH is
> beside the point for
> this) ensures that two disparate resources are referring to
> the same thing.
>
> Bernhard Eversberg's interface is made for information
> consumers to use, while Ed Summer's application exists for
> information creators.
>
> I think this offhand critique of design misses the point of
> their completely different purposes.
>
> -Ross.
>
Received on Wed Sep 24 2008 - 04:14:16 EDT