What is the benefit of having a marc context set, rather than a profile
which maps marc fields to semantically named and defined indexes?
eg 245 -> dc.title
999 -> yourPrivateContextSet.yourPrivateField
Otherwise I'm going to have to set an alias of marc.245a on all my
dc.title indexes, and no one wants to do that.
On Wed, 2005-11-23 at 20:23 +0000, Matthew J. Dovey wrote:
> > > I think a delimier *is* needed between the MARC tag and the
> > subfield
> > > though just to avoid confusion over say numeric subfield names e.g.
> > >
> > > marc.2451
> > >
> > > Say marc.245$1 marc245$a for instance?
> > We could do that; but isn't it the case that MARC fields are
> > all three-digit numbers anyway? In which case 2451 is
> > perfectly unambiguous.
> Yes, MARC field tags are all three characters - although checking that
> in ISO2709 I discovered that a MARC field tag can be alphanumeric which
> I'd never realised before! So you might have marc.aaaa for instance (or
> even marc.marc!)
> I wasn't saying that marc.2451 or marc.aaaa was unambiguous just that it
> might be confusing (e.g. for any human reading or entering the CQL by
> hand), and marc.245$1 or marc.245.1 or whatever might be easier on the
Dr Robert Sanderson
Dept of Computer Science, University of Liverpool