Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:record_data_formatter
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
development:architecture:record_data_formatter [2020/09/22 14:19] – demiankatz | development:architecture:record_data_formatter [2022/12/20 13:03] – [Basic Concept] demiankatz | ||
---|---|---|---|
Line 12: | Line 12: | ||
* A [[development: | * A [[development: | ||
- | As output, getData() returns different formats depending on your VuFind version. In 4.x, it is an associative array of field name < | + | As output, getData() returns different formats depending on your VuFind version. In 4.x, it is an associative array of field name < |
+ | |||
+ | :!: Starting with 5.0, the return format changes to a non-associative array of arrays, with each sub-array containing a ' | ||
+ | |||
+ | :!: Starting with 9.0, the record driver parameter to getData is optional; you can instead pass it directly to the view helper when the helper is invoked -- e.g. < | ||
Field names are raw and should be translated/ | Field names are raw and should be translated/ | ||
Line 65: | Line 69: | ||
If you want to change behavior for a specific record driver, or if you prefer to keep your code changes at a higher level, you can also customize the appropriate record driver template(s), | If you want to change behavior for a specific record driver, or if you prefer to keep your code changes at a higher level, you can also customize the appropriate record driver template(s), | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
development/architecture/record_data_formatter.txt · Last modified: 2023/12/11 16:11 by dltj