Diary

[sashafirsov]

Notes on project design and plans

[sashafirsov]

headers for table extraction

Entities which could be shown as tabular data need the ordered list of record fields/attributes along with assigned sorting order.

headers

• have to be computed for each table
• table should have associated xPath which would be used as a key for tables definition
• during transformation the pipeline would

1. Preprocess XML to inject display parameters, TableParams.xslt output is XML with xv:display display data for each table. This XML is reused for run-time sorting so display data extraction and injection done only once.
   • extract from XML headers from all rows as not all records would have all fields.
   • mix-in the order, sorting, visibility from URL/xPath
2. After preprocess in step 1 and on each sort order change, AsTable.xsl transform
   • on tabular data entry looks for display data ( identified by xPath as key in xv:display list)
   • sort rows
   • render HTML &filter columns

[sashafirsov]

XML display preprocessing placement

xv:display data could be saved as

independent XML

how to refer from XSLT which transform original XML?

independent sub-tree embedded into source XML

after initial preprocessing step, xv:display is appended to original XML.
CONS: original data changed.

embedded into XML clone used for further processing

PROS: easiest processing as display data injected in place of use.
CONS: injection requires re-creation of XML(memory) or inline injection by xPath(CPU);

embedded into XSLT as template path - best

PROS: dynamic code could be more efficient than metadata processing from XML
CONS: ?

[sashafirsov]

Display params as XSLT rules

sort and order ( -1 to hide ), filter are the parameters passed from display param state to transformation rules.

sort

is ordered sequence of fields with associated sorting XSLT template

• none by default, i.e. in order of data or by XSLT transformation
• inv - inverse order
• asc - alphanumerical ascending
• des - alphanumerical desc
• inc - numeric incremental
• dec - numeric decremental
• future date order with past-first
• past date order with future-first
• other TBD
• custom order via xPath or function TBD
  sort:[ ['dob',future'], ['lastname','asc'], ['firstname','asc'] ] lists older-first folks by year with last/first name inside of year sorting.

[sashafirsov]

order

Propagated in same fashion as sort except of values are numerical with negative to hide.

Same value could serve to combine data fields into single table cell.

[sashafirsov]

filter

Display only data defined in xPath as comma separated list.

When filter is defined, by default all data except of listed are hidden.

[sashafirsov]

Table render

<xsl:template mode="DisplayAs" match="/SearchResult/BookSet/Book" >

is the entry for particular tabular data generated by TableParams.xsl.

<xsl:apply-templates select="." mode="DisplayAsTable" >
    <xsl:with-param name="headers">... sorted by order header titles
    <xsl:with-param name="rows">... sorted by order/direction rows with sorted by header order cells

[sashafirsov]

table TH click/trigger handle

Primary Click/tap or SPACE key is triggering the sort button. Parameters passed from DOM:

• xPath to table
• field id ( name() or @Attribute )
  Handler would find DisplayAs template with xPath and
• change order by rotating in ['ascending','descending','']. If blank, remove the sort rule
• set selected sort number to 1 and shift others in previous order

Account

User settings to be kept

• on browser instance
• on account associated with email, authorized by git/npm/gmail/twitter... OAuth2?
• saved on GDrive, etc.

[sashafirsov]

Context menu

Triggered by keyboard/right click. Actions candidates

• sort column as string/number/date...
• copy selected
• select
• copy table
• table props ( visibility, theme, account ), copy & paste props
• export to eXcel CSV