On 2007/11/20, at 6:12 AM, Ignacio wrote:
I made the rebuild but there are still some rows that contain
__RAW__ value
and same for new catalog entries, they are stablishing a default
value for
indexname to the value '__RAW__' each time I add a a new entry to the
catalog.
The basic search makes a 'value' column matching of this table, but
advanced
search filters make a more granular selection using parameters (title,
subject, ISBN, etc...) that are matching against a __RAW__ value
that seems
being generated (instead title, subject, etc...) in nozebra table
each time
a new entry is catalogued.
The script seems to add some indexname = title, author, etc...
entries, but
does not fix raw entries added before.
It seems to be a problem inherited caused by misconfiguration. Some
ideas?
Hiya Ignacio,
Easy questions first :)
What marc flavour are you using, UNIMARC or MARC21. ?
I have been working on some MARC21 imports this week, and have found
some little tricks, for MARC21 nozebra at least
how does your nozebra table look if you run this sql??
heres mine.
mysql> select distinct(indexname) from nozebra;
+--------------+
| indexname |
+--------------+
| author |
| bc |
| biblionumber |
| date |
| host-item |
| isbn |
| note |
| subject |
| title |
| __RAW__ |
+--------------+
10 rows in set (0.03 sec)
_______________________________________________
Koha-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/koha-devel
