#17 Bell/Howell modelling title lists

[Kimberly Parker]

On Fri, 19 Nov 1999, Kimberly Parker wrote:

All Bell & Howell Info lists for ProQuest seem to be at:
http://www.proquest.com/hp/Support/Titles/

Unfortunately, one seems to have to go to several different pages from
there due to their structure.

Many of the links from that page will be easy enough to pull down... the
bigger question is how to we model the provider/database relationships?

Usually, what we do is something like this:

Ovid=provider
journals@ovid=database, is provided by ovid
annals of internal medicine=serial, is provided by journals@ovid

For proquest/b&h it seems more complicated for some of these. For
instance, ProQuestŽ DiscoveryTM and ProQuestŽ Research LibraryTM have two
separate products, each of which have separate modules (see
http://www.proquest.com/cgi-bin/TitleForm?cfg=ModTitles.cf\).

For the sake of discussion (and since we'd like to get these in there),
here's one way to do it. Please dispute with a better way if you can
suggest it.

Bell&Howell=provider
ProQuest=database, provided by Bell&Howell
Discovery=database, provided by ProQuest
Multicultural=database, provided by Discovery

The simpler products won't need so many levels as this. If we go this
route, we'll have to rewrite the stylesheets a bit to account for the
possibility of having to go this deep. But that shouldn't be too hard,
and the relationships should be clear. One thing to keep in mind, too, is
that our semantics are very simple (there are providers, databases,
serials, and soon to be textbooks but not yet) and we want to keep it
simple. If one of these things is genuinely a new kind of resource, we
need to add a 'type'. If not, we shouldn't.

What do you think?

&&&&& I think it could work as you specify Dan, or you could simply not map the intermediary trees.
As in:
Bell&Howell=provider
ProQuest Discovery Multicultural, provided by Bell&Howell

By the way, if you do your original treed structure suggestion, don't include Proquest as a database. ProQuest is simply the name of the interface, not the name of any particular database.