Requirements

Provide for Browser app table a paged resolution.

• Source: Table name with col columns und row rows. 
• Header and content provided per server
• • Entity with unique name
  • contains properties
  • filterable, pagable(size:
  Pagination with configurable row number (e.g.
  • 10, 20, 50, 100)
• Filter, configurable per column
• Column type: Date, String, Long, Float
• Multiple column filter: As specified ... link
• One column can be used to sort table:
  • , sortable (multiple properties,ascending, descending, default

Further points&questions:

• Language
• How to export Table data?
• yang spec ?
• JSON
• Attribute: table name
• get table size
• get page n
• get/set page size
• set filter for each column

Interfaces to be considered (At the moment provided by ElasticSearch)

• Tables (Fault, Logs, PM Data) (ES)
• Maintenace (ES)
• Inventory (ES)
• Status bar (ES)
• Required Network Elements / Unknown network elements (MDSAL)
• MediatorApp (ES) (??)

Not to support

• • )
  • properties have unique names per entity (not translated - will be translated through seperate service if neccessary)
  • CRUD (Create, Read, Update, Delete)-functionalities
  • auth required, token based (has to be optimized - maybe independent from odl)
  • export function
  • additional result information:
    • result size
    • page number
    • page size
  • payload: JSON (no '-' for properties, entities)
  • yang spec !
  • Language 
  • Localization
  • change events via websocket (needs subscription for this entity)

Further points&questions:

Entities:

• NetworkElementConnection (filter: isRequired:boolean, connectionState: enum<string>)
• NetworkElementConfiguration (only proxy for restconf) → implemented in APIGateway
• Fault
• Log
• PMData
• MediatorServer
• Inventory
• Maintenance
• StatusConfigurationApp (RESTCONF)

Table Screenshot Examples

...