copyField is pretty straightforward. Before any field processing, it copies the data destined for one field to another field. The copyField element/directive doesn’t take any attributes. It copies, period. The destination field has stored, indexed, etc. The source field and destination field are completely independent and don’t “know” that the text came from a copy.
The most common use for this is to send the same text to one field processed as text for searching and another as a string field for faceting. Another use is a catch-all field that collects all the text. Did the name change from IUPUI? I went to North Central High School. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Feb 18, 2025, at 9:19 AM, mw...@iu.edu wrote: > > So *how* does copyField work? Do I wind up with two identical copies > of the data stored in the index (if stored='true')? Does the > copyField element accept a 'stored' attribute, and can it have a > different value than the source field declares? What *are* the > defined attributes for copyField, and do they interact with the source > field's attributes? Where should I have found answers to these > questions? > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > library.indianapolis.iu.edu
