Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
indexing:tracking_record_changes [2015/12/14 18:13] – ↷ Links adapted because of a move operation demiankatz | indexing:tracking_record_changes [2016/08/30 15:36] – [Enabling Change Tracking] demiankatz |
---|
===== Enabling Change Tracking ====== | ===== Enabling Change Tracking ====== |
| |
The most important thing that you need to do in order to enable VuFind's change tracking is to edit the [[indexing:solrmarc:local_marc_mappings|local MARC mappings]] file and uncomment the lines that fill in the "first_indexed" and "last_indexed" fields of your Solr index. | The most important thing that you need to do in order to enable VuFind's change tracking is to edit the [[indexing:solrmarc:local_marc_mappings|local MARC mappings]] file and uncomment the lines that fill in the "first_indexed" and "last_indexed" fields of your Solr index. If you are using VuFind 2.x or higher, this usually consists of: |
| |
If you are indexing non-MARC records, some change tracking facilities also exist in the [[indexing:xml|XSLT index tool]]. For example, the VuDL importer supports change tracking if you edit [[https://vufind.svn.sourceforge.net/svnroot/vufind/trunk/import/vudl.properties|import/vudl.properties]]. | 1. Copy import/marc_local.properties into the import subdirectory of your [[configuration:local_settings_directory]] (usually $VUFIND_HOME/local/import). |
| |
| 2. Uncomment the *_indexed lines. |
| |
| 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. 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 ==== |
| |
[[indexing:solrmarc|SolrMarc]] may require more memory in order to update the database and the Solr index at the same time. If you get error messages about running out of heap space during the index process, try editing import-marc.sh or import-marc.bat (depending on your platform) to change the Java memory settings. See the [[:performance]] page for more details on Java memory tuning. | [[indexing:solrmarc|SolrMarc]] may require more memory in order to update the database and the Solr index at the same time. If you get error messages about running out of heap space during the index process, try editing import-marc.sh or import-marc.bat (depending on your platform) to change the Java memory settings. See the [[administration:performance]] page for more details on Java memory tuning. |
| |
| |
==== Configuration ==== | ==== Configuration ==== |
| |
Several aspects of the server (including ID prefixes, administrative email addresses and set behavior) can be configured through the [OAI] section of [[:config.ini]]. See the comments in that file for details on how the settings work. | Several aspects of the server (including ID prefixes, administrative email addresses and set behavior) can be configured through the [OAI] section of [[configuration:files:config.ini]]. See the comments in that file for details on how the settings work. |
| |
==== Metadata Formats ==== | ==== Metadata Formats ==== |
When record change tracking is enabled, RSS feeds will be more effective. Without tracking, RSS dates are based on publication dates, which may or may not correspond with the dates that items were added to your collection. With change tracking turned on, RSS feeds will be sorted by index date and will display index dates within the feed. This means that patrons can truly track searches in order to be notified of new additions within their chosen areas of interest. | When record change tracking is enabled, RSS feeds will be more effective. Without tracking, RSS dates are based on publication dates, which may or may not correspond with the dates that items were added to your collection. With change tracking turned on, RSS feeds will be sorted by index date and will display index dates within the feed. This means that patrons can truly track searches in order to be notified of new additions within their chosen areas of interest. |
| |
Note that you can customize some of the RSS behavior in VuFind -- see the [RSS] section of [[:searches.ini]]. | Note that you can customize some of the RSS behavior in VuFind -- see the [RSS] section of [[configuration:files:searches.ini]]. |
---- struct data ---- | ---- struct data ---- |
---- | ---- |
| |