About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

VuFind Documentation

Site Tools

You are here: start » indexing » tracking_record_changes
Trace:
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.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
indexing:tracking_record_changes [2021/07/28 10:51] – demiankatzindexing:tracking_record_changes [2021/08/03 13:59] (current) – [More on OAI-PMH] demiankatz
Line 61: Line 61:
 For a general introduction to the OAI-PMH protocol, see [[http://www.oaforum.org/tutorial/|this tutorial]]. For a general introduction to the OAI-PMH protocol, see [[http://www.oaforum.org/tutorial/|this tutorial]].
  
 +==== Related Video ====
  
 +For more on OAI-PMH, see the [[videos:oai-pmh_server_and_harvest_functionality|OAI-PMH Server and Harvest Functionality]] video.
 ===== Enhanced RSS Functionality ===== ===== Enhanced RSS Functionality =====
  
Line 83: Line 85:
  
 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. 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/deletes [[administration:command_line_utilities|command line utility]] for this purpose.
 +
 +For systems that have no easy way of reporting deleted records, a common solution is to simply delete VuFind's index, and then reindex from a fresh full export. If you do this, the deleted records will be removed from VuFind's index correctly, so normal search behavior will work as expected. However, the change tracking system will not be aware that records have been removed, and the now-missing records will not be reported as deleted through OAI-PMH (or any other feature that might rely on delete tracking functionality). This may or may not be a problem for you, depending on your use case.
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
indexing/tracking_record_changes.1627469482.txt.gz · Last modified: 2021/07/28 10:51 by demiankatz