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  July 2004

ZNG July 2004

Subject:

Re: diagnostic examples - revisited

From:

Peter Noerr <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Thu, 15 Jul 2004 12:03:47 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (70 lines)

Hi All,

This is a relatively cool thread by now, but blame various "xLA" conferences
and having to clean up email for weeks afterwards.

As a producer of a metasearch engine (and hence a client to all "real"
servers and also a server to our clients - all at once) I would like to put
in 2c worth for more machine readable (parseable) diagnostics.

We have to understand the diagnostics from a variety of servers (not all
Z39.50) and represent what happened to the end user in a consistent fashion.
This means that we need machine readable diagnostics so our engine can
"interpret" them and correlate with similar problems occurring in other
environments. The problems get reported individually to the user, but need
to be consistent. (So the example that started this: "fo* vs *oo" cannot be
reported variously as "unrecognized masking character", "left truncation not
allowed", "unrecognized term", etc. (Imagination may now run wild with
alternatives.)) We need to convert all into one diagnostic and present that
to the user. Thus the more specificity in machine readable form the better.

There is one other aspect of this which seems to have been missed entirely
(or is handled in some clever way I'm missing) and that is multi-lingual
forms of the user friendly text message. All the diagnostic user messages
were quoted in English, not entirely surprisingly. But we certainly, and
almost all library systems probably, have to allow for interfaces in
different languages. That includes translating the
error/diagnostic/informative messages that systems further away from the
user pass back. Language here also means "level of" language. So end users
may get a different message to staff users for the same problem. This
multi-lingualism is obviously a function of the system 'nearest' to the
user, and that is almost certainly not the Z39.50 server. So, in these
circumstance, the 'user friendly text message' becomes a bit moot. Except
that it is very necessary for the person creating the translations in the
first place and debugging their attempts.

Peter

p.s. I agree that the problem term should be returned as part of the
message.

Dr Peter Noerr
Chief Technical Officer
Museglobal, Inc.

tel: +1 801 208 1880
fax: +1 801 208 1889
cell:+1 801 910 4912

[log in to unmask]
www.museglobal.com




> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]]On Behalf Of
> Ray Denenberg, Library of Congress
> Sent: Thursday, July 01, 2004 1:06 PM
> To: [log in to unmask]
> Subject: Re: diagnostic examples
>
>
> >  In this case, I think the
> > best we can do is to show the rejected term.
>
> Lacking any other suggestion, let's go with this one.
>
> --Ray
>

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