WIKINDX API 6.9.1

ENDNOTEMAP
in package

Endnote Map class.

Provides mappings for Endnote export/import

Table of Contents

Methods

loadMap()  : mixed
Create arrays based on database table and resource type.

Methods

loadMap()

Create arrays based on database table and resource type.

private loadMap() : mixed

The arrays are named for WIKINDX resource types. The key of the resource_xxx arrays is the database resourceField within the resource_xxx database table. For exporting Endnote tabbed files this is not needed but will prove useful should there be an eventual Endnote import. The key of the resource_xxx array is the WIKINDX resourceField in that table while the value is the Endnote equivalent resourceField (Generic). For an export, these keys can be found as the resourceFields in the SQL $row assoc. array.

The database matrix can be found in docs/resourceDatabaseMatrix.html

Some things must be sorted out on the fly in the import/export code: 1/ Endnote only has a resourceField 'Pages' whereas WIKINDX uses pageStart and pageEnd resourceFields. 2/ Endnote has a separate type for an 'Edited Book' - WIKINDX makes no such distinction but, if a WIKINDX book has editors but no author, then it is an Endnote 'Edited Book'. 3/ WIKINDX book and book_article types can have a reprintYear in resourceyearYear2. If a book has this in addition to a publicationYear in resourceyearYear1 then we need to switch the two resourceFields so that resourceyearYear1 is Endnote's 'Original Publication' resourceField and resourceyearYear2 is Endnote's 'Year'. They are defined here as if there were no reprintYear. 4/ Most dates (newspaper, magazine, hearing etc.) have to be created on the fly from database resourceFields resourcemiscField2 (day) and resourcemiscField3 (month). 5/ A WIKINDX 'title' is comprised of subtitle, title and noSort resourceFields.


        
On this page

Search results