| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| indexing:tracking_record_changes [2016/08/30 16:26] – demiankatz | indexing:tracking_record_changes [2021/07/28 10:44] – [Enabling Change Tracking] demiankatz |
|---|
| 1. Copy import/marc_local.properties into the import subdirectory of your [[configuration:local_settings_directory]] (usually $VUFIND_HOME/local/import), if you don't already have a local copy of marc_local.properties. | 1. Copy import/marc_local.properties into the import subdirectory of your [[configuration:local_settings_directory]] (usually $VUFIND_HOME/local/import), if you don't already have a local copy of marc_local.properties. |
| |
| 2. Uncomment the *_indexed lines in the local copy of marc_local.properties. | 2. Uncomment the *_indexed lines in the local copy of marc_local.properties. The example lines assume that your record IDs come from the 001 field; if you use IDs in a different place, change 001 to an appropriate pattern (e.g. 999c for Koha). |
| |
| If you are indexing non-MARC records, some change tracking facilities also exist in the [[indexing:xml|XSLT index tool]]. Depending on your data source, you may need to customize your XSLT and/or properties file to implement support. | If you are indexing non-MARC records, some change tracking facilities also exist in the [[indexing:xml|XSLT index tool]]. Depending on your data source, you may need to customize your XSLT and/or properties file to implement support. |
| |
| After making the necessary configuration changes, you will need to reindex all of your records. This will take a long time, as it will be generating a database so that VuFind can correctly populate these fields in the future. "first_indexed" contains the time that the record was first indexed by VuFind, while "last_indexed" contains the time that the record was most recently changed. VuFind stores information in its database so that even if you upgrade Solr and destroy your entire index, it will still be able to rebuild the correct "first_indexed" and "last_indexed" values. In the future, when you reindex existing records, the process should be faster than the first time around, since for records that have not actually changed, VuFind will not have to do much extra database work. | After making the necessary configuration changes, you will need to reindex all of your records. This will take a long time, as it will be generating a database so that VuFind can correctly populate these fields in the future. "first_indexed" contains the time that the record was first indexed by VuFind, while "last_indexed" contains the time that the record was most recently changed. For consistency and appropriate OAI-PMH behavior, it is STRONGLY RECOMMENDED that all times be stored in UTC; VuFind's provided tools will already do this, but if you build your own custom indexer, you should conform to this standard. VuFind stores information in its database so that even if you upgrade Solr and destroy your entire index, it will still be able to rebuild the correct "first_indexed" and "last_indexed" values. In the future, when you reindex existing records, the process should be faster than the first time around, since for records that have not actually changed, VuFind will not have to do much extra database work. |
| |
| ==== A Note on Memory Usage ==== | ==== A Note on Memory Usage ==== |
