About Features Downloads Getting Started Documentation Events Support GitHub

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

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:data_model_key_concepts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
development:architecture:data_model_key_concepts [2015/12/11 18:59] – ↷ Links adapted because of a move operation demiankatzdevelopment:architecture:data_model_key_concepts [2015/12/11 19:01] – ↷ Links adapted because of a move operation demiankatz
Line 22: Line 22:
 ==== Record Drivers ==== ==== Record Drivers ====
  
-Regardless of where it comes from, every record in VuFind is represented by a [[development:plugins:record_drivers|record driver object]].  Like the search objects, all record drivers inherit from a common base class that implements basic record-related behavior (saving to favorites, adding tags, etc.).  However, subclasses have a great deal of flexibility in how they represent records.  Each record driver gets its own set of templates for rendering within the VuFind interface, so displays can be completely customized.  However, by implementing a [[vufind2:record_driver_method_master_list|standard set of get methods]] for retrieving common sorts of data elements (title, author, subject, etc.) it is possible to share templates between similar record drivers for less complex code and a more consistent user experience.+Regardless of where it comes from, every record in VuFind is represented by a [[development:plugins:record_drivers|record driver object]].  Like the search objects, all record drivers inherit from a common base class that implements basic record-related behavior (saving to favorites, adding tags, etc.).  However, subclasses have a great deal of flexibility in how they represent records.  Each record driver gets its own set of templates for rendering within the VuFind interface, so displays can be completely customized.  However, by implementing a [[development:architecture:record_driver_method_master_list|standard set of get methods]] for retrieving common sorts of data elements (title, author, subject, etc.) it is possible to share templates between similar record drivers for less complex code and a more consistent user experience.
 ---- struct data ---- ---- struct data ----
 ---- ----
  
development/architecture/data_model_key_concepts.txt · Last modified: 2023/03/27 19:49 by demiankatz