STYLEMAP
in package
Define style mapping
There are dynamic properties like $custom_1, custom_2, ... for styles
Table of Contents
Methods
- loadMap() : mixed
- loadMap: Load the map into arrays based on resource type.
Methods
loadMap()
loadMap: Load the map into arrays based on resource type.
private
loadMap() : mixed
The basic() array contains database fields that are common to all types of resources. The key is the database field and the value is displayed to the user to be part of the style definition. e.g. if the user enters: author. |title. |publisherName|: publisherLocation|. for a style definition for a book, we know that 'author' is the database field 'creator1', 'title' is the database field 'title' etc. There are some exceptions as defined by WIKINDX (other systems may have different methods). Because these may be represented in different ways in different systems, you will need to explicitly define these. See BIBCITEGATEWAY.php for examples of how WIKINDX does this. The comments below relate to how WIKINDX stores such values in its database: 1/ 'originalPublicationYear doesn't exist in the database but is used to re-order publicationYear and reprintYear for book and book_article resource types. 2/ 'pages' doesn't exist in the database but is created on the fly in BIBCITEGATEWAY.php as an amalgamation of the database fields pageStart and pageEnd. 3/ 'date' doesn't exist in the database but is created on the fly in BIBCITEGATEWAY.php as an amalgamation of the database fields miscField2 (day) and miscField3 (month). 4/ 'runningTime' doesn't exist in the database but is created on the fly in BIBCITEGATEWAY.php as an amalgamation of the database fields miscField1 (minute) and miscField4 (hour) for film/broadcast. 5/ 'transTitle' doesn't exist in the database but is created on the fly in BIBCITEGATEWAY.php as an amalgamation of the database fields transTitle, transSubtitle and transNoSort.