Warning: This page has not been updated in over over a year and may be outdated or deprecated.
indexing:tracking_record_changes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tracking_record_changes [2015/12/11 17:37] – ↷ Links adapted because of a move operation demiankatz | indexing:tracking_record_changes [2021/08/03 13:59] (current) – [More on OAI-PMH] demiankatz | ||
---|---|---|---|
Line 13: | Line 13: | ||
===== Enabling Change Tracking ====== | ===== Enabling Change Tracking ====== | ||
- | The most important thing that you need to do in order to enable VuFind' | + | The most important thing that you need to do in order to enable VuFind' |
- | If you are indexing non-MARC records, some change tracking facilities also exist in the [[importing_records# | + | 1. Copy import/ |
- | After making the necessary configuration changes, you will need to reindex all of your records. | + | 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: | ||
+ | |||
+ | After making the necessary configuration changes, you will need to reindex all of your records. | ||
==== A Note on Memory Usage ==== | ==== A Note on Memory Usage ==== | ||
- | [[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. | + | [[indexing: |
Line 37: | Line 41: | ||
==== 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]]. | + | Several aspects of the server (including ID prefixes, administrative email addresses and set behavior) can be configured through the [OAI] section of [[configuration: |
==== Metadata Formats ==== | ==== Metadata Formats ==== | ||
Line 43: | Line 47: | ||
Out of the box, VuFind' | Out of the box, VuFind' | ||
- | To add additional metadata formats, simply make changes to the getXML() method of the [[legacy:vufind_1.x_developer_manual:supporting_a_new_metadata_format|record driver(s)]] you are using. | + | To add additional metadata formats, simply make changes to the getXML() method of the [[development:plugins:record_drivers|record driver(s)]] you are using. |
Important: The server is currently coded to assume that all supported metadata formats are supported by all records in the index. | Important: The server is currently coded to assume that all supported metadata formats are supported by all records in the index. | ||
Line 57: | Line 61: | ||
For a general introduction to the OAI-PMH protocol, see [[http:// | For a general introduction to the OAI-PMH protocol, see [[http:// | ||
+ | ==== Related Video ==== | ||
+ | For more on OAI-PMH, see the [[videos: | ||
===== Enhanced RSS Functionality ===== | ===== Enhanced RSS Functionality ===== | ||
When record change tracking is enabled, RSS feeds will be more effective. | When record change tracking is enabled, RSS feeds will be more effective. | ||
- | 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: |
+ | |||
+ | ===== Solr-driven New Items ===== | ||
+ | |||
+ | :!: This feature was added in VuFind 2.3. | ||
+ | |||
+ | By default, VuFind tries to use the ILS driver to power the "new items" search. However, not all ILS drivers support this functionality. If you turn on record change tracking, you can modify the method setting to " | ||
+ | |||
+ | ===== Frequently Asked Questions ===== | ||
+ | |||
+ | This section contains answers to frequently asked questions about the technical details of the change-tracking implementation. | ||
+ | |||
+ | ==== If I reindex my existing records, will VuFind think that they are new? ==== | ||
+ | |||
+ | No, the change tracking system will only update dates in its internal database if it encounters a record ID it has never seen before, or if the record itself has changed. If you index the same MARC file over and over again, that record will only be recorded in the database once. However, if you edit the MARC record and export a new version, when you index the changed record, VuFind will update the "last indexed" | ||
+ | |||
+ | This behavior is dependent on records containing last-changed dates. In the case of MARC records, VuFind checks the 005 and 008 fields for modification dates. Note that if no dates are found, VuFind will always assume that the record has changed as a precaution; thus, it is important to ensure that your ILS is including one of these fields in exported records if you want reliable change tracking. In the case of XSLT records, the custom PHP methods used by the XSLT expect a modification date parameter, and you should be sure to extract it from an appropriate place in your XML to ensure consistent behavior. | ||
+ | |||
+ | ==== What happens when records are deleted? ==== | ||
+ | |||
+ | If you remove records from your ILS, you should inform VuFind about the deleted records so it can update its change tracking database. This enables the system to correctly report deleted records through OAI-PMH, and it also allows the system to treat records as new if they later are added again after being previously deleted. You can use the util/ | ||
+ | |||
+ | For systems that have no easy way of reporting deleted records, a common solution is to simply delete VuFind' | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
indexing/tracking_record_changes.1449855445.txt.gz · Last modified: 2015/12/11 17:37 by demiankatz