DB Viewer UX and layout issues

[E3V3A]

For the DB Viewer to be of any informative value, it should better reflect the important contents of the DB tables. Especially important to us is the key info in the DBi_bts and DBe_import tables.

I propose the following improvements:

• [x] 1. In DB Viewer, use ~~the same two-color text-coloring-scheme as in the Map Viewer pin-info.~~
• [x] 2. In DB Viewer, try to left-align all the text columns.
• [x] 3. In DB Viewer, use 2 columns to fit additional data for measurements and OCID data.

Specifically, for the BTS Measurements and in map view details, we'd like something like this:

----------------------------------------------------
CID(hex): HHHHH         Sector:  nn
----------------------------------------------------
PC:  NNN-NN             Lat:     51.9898
LAC: nnnnn              Lon:     176.58705
CID: nnnnn?             first:   2014-12-01 21:00:00
PSC: nnn                last:    2014-12-19 21:00:01
RAT: HDSP               XXX:     
RSS: -NN                samples: 3
----------------------------------------------------

H : variable length HEX [0-9a-z] (depending on RAT)
n : variable length integer (depending on RAT)
N : Fixed length integer

RSS = AvgSignal for OCID data, and RSSI for measured data. XXX = isGPS_exact for OCID data and for measured data:

        LTE:  *TA*
        UMTS: -
        GSM:  /

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[E3V3A]

Could someone please try to provide some help on how to setup the XML + code card to show different font colors and aligning the text?

[E3V3A]

This is now a high priority item, since after the major DB overhaul, we've had to loose some of the original cad items, that correctly formats the DB viewer.

[E3V3A]

New list of things to fix:

• [x] Add DB item count on bottom right of each DB item: 12/123

Sorting:

• [ ] Sort Unique BTS Data (on time_last) to show latest used cell first
• [ ] Sort BTS Masurements (on time_last) to show latest used cell first
• [ ] Sort Imported OCID Data on:
  • [ ] 1. MCC and MNC (if not already unique from import specification)
  • [ ] 2. LAC and then CID .

Text and Fonts:

• [x] In all X tables, use the same small size font as currently used in Silent SMS table
• [x] In all X tables, left-justify all the text (as currently used in Silent SMS table)
• [x] In all X tables, use same green color for item names as is now, but for the item data, use same gray as is used in the Silent SMS table.

Items to be displayed:

• [ ] In all X tables, truncate or round GPS Lat/Lon coordinates to 5 decimal digits.)
• [ ] In all X tables, for CID item, also show its Hexadecimal equivalent as shown above and in Measured Signal Strengths table.
• [ ] In all X tables, and for all timestamps, make sure to show them in human form as in EventLog table

Table specific:

• [x] In the BTS Measurements table, use the SQL DB names as itemn names. (I.e. instead of showing BB POWER, use bb_power etc.)
• [x] In the Imported OCID Data table, put the source at the bottom right, left to item count like this: OCID 12/123

X = are the Unique BTS Data, BTS Measurements and Imported OCID Data tables.

[SecUpwN]

@larsgrefer, are you tackling this as well whilst working on #827?

[SecUpwN]

@larsgrefer, would you please tell us if this is fixed now with the move to the new realm database?