LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  March 2007

ZNG March 2007

Subject:

Re: Profiles and context sets

From:

Tor Arne Dahl <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Mon, 26 Mar 2007 15:11:49 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (72 lines)

Thanks for all the answers to my questions about profiles and context set.

On 22.03.2007 15:39, Mike Taylor wrote:
> Tor Arne Dahl writes:
>  > 1. The profile is based on the NorZIG Z39.50 profile, and we design the 
>  > SRU profile to support for the same kind of queries as the Z39.50 
>  > profile. Many of the necessary indexes are defined in the Bath, CQL, 
>  > Dublin Core and Record Metadata context sets, but we had to create a 
>  > NorZIG context set to define all required indexes (series title and 
>  > corporate and conference name, for example). Since our first draft, the 
>  > CQL Bibliographic Searching Proposal has been published on the SRU 
>  > website. Many of the indexes from the NorZIG context set are defined in 
>  > the bib context set described in this document, so we would rather use 
>  > them than create our own.
> 
> I am very pleased to hear it!  If you have any remaining indexes in
> the NorZIG context set, perhaps you would propose them here for
> inclusion in one of the other existing sets?

OK, here are the 11 indexes in the draft version of a NorZIG context 
set, followed by a description in brackets:

creatorConference (A conference name identified as the author)
creatorCorporate (An organization or a group of people that is 
identified as the author)
creatorNormalized (A personal or corporate author, or a conference or 
meeting name, in normalized form)
creatorPersonalNameNormalized (An author's personal name in normalized form)
dewey (A classification number from the Dewey Decimal Classification)
docid (An identifier or Doc-ID, assigned by a server, that uniquely 
identifies a document on that server)
nationalBibliographyNumber (Character string that uniquely identifies a 
record in a national bibliography)
personalNameNormalized	(A person's name in normalized form)
remoteSystemClassificationNumber (A local classification number from a 
system not specified elsewhere in the Bib-1 attribute set)
titleSeries (Collective title applying to a group of separate, but 
related, items)
udc (A classification number from the Universal Decimal Classification)

Some of the indexes seem to be included in the proposed bib context set:

norzig.creatorConference -> bib.nameConference
norzig.creatorCorporate -> bib.nameCorporate
norzig.titleSeries -> bib.titleSeries

norzig.docid and norzig.nationalBiographyNumber can probably be replaced 
by dc.identifier with the bib.identifierAuthority relation modifier. 
Which values could be used for the modifier in these cases?

norzig.dewey, norzig.remoteSystemClassificationNumber and norzig.udc can 
probably be replaced by bib.classification and some kind of 
bib.classAuthority relation modifier. Are there any suggestions about 
how this can be done?

The last three indexes specify normalized forms of personal names (i.e. 
last name, first name(s)). This isn't mentioned in the CQL bibliographic 
searching proposal. Do you think it's a bad idea to create these indexes?

I'm also wondering about the dc.creator index in CQL bibliographic 
searching. With the different name indexes and relation modifiers 
defined in the bib context set, does it mean that dc.creator never 
should be used?


Tor Arne Dahl

-- 
Tor Arne Dahl
Oslo University College
Faculty of Journalism, Library and Information Science

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager