Download Firefox: WindowsMac OS X
logo       
Google Custom Search
    AddThis Social Bookmark Button

Re: 1.2.3 qa whilst going production: msg#00024

Subject: Re: 1.2.3 qa whilst going production
On 8/15/05, Wolfgang Pichler <wolfgang.pichler@xxxxxxxxxxxxxxxx> wrote:
> 2) MARC.inc
> 
> at the first attempt i tried to "customize" native by specifying
> 
>     $YAZ_attributes = Array(
>          //standard things for all databases
>          ...
>          //specials for native databases
>          $REMOTE_DATABASE[_("Native")] => (
>             "970" => "u=5000 t=l t=r t=n t=b s=al",
>             ...
>             );
>          //specials for foreign databases
>         ...
>     );
> 
> such coding did not work but maybe i missed something ...

The question here is what do these map to?  For instance, if 970 is
yet another place to look for "Title" then I would not make the
distinction known to the user, but instead map it to the normal use
attribute within Zebra only.

If you still need to have 970 distinctly and individually searchable,
be certain that bib1.att,  usmarc.abs,  usmarc.tag,  Emilda MARC
configuration (database), and your CCL_names array (MARC.inc) is
appropriately harmonized.

In either case, if you want it to display, you still have to manage
the Emilda MARC Configuration.


<Prev in Thread] Current Thread [Next in Thread>