Actually, I misunderstood the browse search pages.  I thought that the author browse search wasn’t working, until I realized that the search box at the top of the page is always a keyword search.  I had suspected that I’d accidentally messed up something with the author_browse copyfield settings, but I just misread the screen. 

 

But, to put this to rest in my head, is the author_browse field not supposed to show up in a record’s XML after it’s been indexed?  Or should I be seeing that field now that I’ve changed the “stored” value to “true” in the author_browse field, reimported the records and reindexed them?

 

Maura Byrne

Integrated Library Systems

University of Chicago Library

 

From: Demian Katz [mailto:demian.katz@villanova.edu]
Sent: Friday, October 12, 2012 6:07 AM
To: Maura Byrne; VuFind Tech Mailinglist
Subject: RE: Copyfield not working so well

 

As David said, the symptom you are seeing is due to the field being indexed but not stored.

Is there some behavior you want that you are not getting, or was this just a matter of curiosity?

- Demian


From: Maura Byrne [byrne@uchicago.edu]
Sent: Thursday, October 11, 2012 5:29 PM
To: VuFind Tech Mailinglist
Subject: [VuFind-Tech] Copyfield not working so well

We’ve been trying to use the author browse in our VuFind implementation, and we’ve been running into some problems that seem to be related to the copyfield tag in schema.xml.

 

For instance, the schema.xml has this field:

 

<field name="author_browse" type="string" indexed="true" stored="false" multiValued="true"/>

 

And these copyfields:

 

<copyField source=”author” dest=”author_browse”/>

<copyField source=”author2” dest=”author_browse”/>

 

However, when I look at a particular record in the Solr admin interface, the author_browse field doesn’t show up in the record’s XML.  My colleagues and I think that the author_browse field is just not being brought into solr.  But from what I understand about the copyfield tag, our code ought to be bringing everything from the author and author2 fields into the author_browse field.

 

Has anyone else encountered this problem?  Does anybody have an idea where we can look to fix this problem?

 

 

Maura Byrne

Integrated Library Systems

University of Chicago Library