From: P. S. M. <psm...@gm...> - 2016-10-17 19:09:32
|
I have observed a few facts related to new SolrMarc in our recent upgradation from 3.0.3. 1. It is remarkably faster that the previous SolrMarc in version 3.0.3; 2. It's rejecting indexing of those records (harvested in marcxml format from Koha) where tag 001 is missing (previous SolrMarc was using biblio number - a master record number automatically generated by Koha for each record and available as 9xx (precisely 999c); 3. It is using content of 001 as unique identifier (for example http://localhost/vufind/Record/18235147 for the record where value of 001 is 18235147 and 999 *is |c* 41 *|d* 41) but in the previous SolrMarc version it was 999c. My questions against the above observations are: 1. In some of our records 001 tags are missing; Can we direct new SolrMarc to use 999c as record identifier in place of 001? If no, is there any way to avoid manual entry of 001 in those records where the contents of the tags 001 are missing? 2. If in a union catalogue environment, we use a compound 001 like MARC org code and biblio number e.g. INWBKUC0001 then can it be handled by new SolrMarc? Thanks and regards -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |