GDC: Purpose of GDC Reindexing job?
- Product: Voyager
- Product Version: 8.2.0
- Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care
Can you describe a scenario where one might use the reindexing job in Global Data Change (GDC) module? Is it the same as a keyword regen?
GDC's Index Job essentially allows an operator to selectively regen/index a set of records. If you need to reindex a set of records, but don't want to reindex your entire database, you can create a record set & reindex just those records.
The index job exports & reimports the records so it's fully indexing the record with that action (i.e., it fully indexes the record, not just keyword indexing). Re-saving records in the client would have the same end result, but this option does not change the record's update date (may be desirable if you run a Primo extract and don't wish to re-extract the records in the daily Publishing extract).
Examples where this job may be used
- an occupational/genre term in a subject's $2 subfield that was previously not included the HEADING_TYPE table is added in a later release & want to reindex records with that $2 value
- keyword indexing was not enabled for a BulkImport but should have been, and is locally determined that an Index Job makes more sense than a keyword regen at that point in time
- Article last edited: 03-Aug-2015