Improve readability in the admin view for Read and HiFi Yield

[RasmusBurge-CG]

Description

Closes: https://github.com/Clinical-Genomics/ProdBioInfo/issues/246

Added

• Comma separation for large numbers on Reads in Sample table in the Admin view:

100,000,000
100,000
100
1

• SI prefix on Hifi Yield in the Sample table in the Admin view :

1.00 Tb
1.00 Gb
1.00 Mb
1.00 kb
1b

(b-base pairs)

How to prepare for test

• Ssh to relevant server (depending on type of change)
• Use stage: us
• Paxa the environment: paxa
• Install on stage (example for Hasta):

  bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_cg -t cg -b improved-yield-view -a

How to test

• Do ...

Expected test outcome

• Check that ...
• Take a screenshot and attach or copy/paste the output.

Review

• Tests executed by
• "Merge and deploy" approved by
  Thanks for filling in who performed the code review and the test!

This version is a

• MAJOR - when you make incompatible API changes
• MINOR - when you add functionality in a backwards compatible manner
• PATCH - when you make backwards compatible bug fixes or documentation/instructions

Implementation Plan

• Document in ...
• Deploy this branch on ...
• Inform to ...

[RasmusBurge-CG]

[StellaPaulina]

Very nice! I would second that suggestion to try spaced for the same reason as Alfred unless it will take too much space on the row

[RasmusBurge-CG]

Very nice! I would second that suggestion to try spaced for the same reason as Alfred unless it will take too much space on the row

Hi!
I tried that, and with the current implementation, it would occasionally produce a line break.
It would render like this:
100
000
000
Instead of like this:
100 000 000

@StellaPaulina How would you like to proceed? Is it okay with a comma or is it a dealbreaker?

[dnil]

We had a similar discussion with Scout, and ended up with thinsp thin spaces for spacing plus a copy button to make it smooth to copy and use the numbers as such. Since there are all kinds of local national standards for making numbers readable, adding commas, points and apostrophes is bound to backfire at some point. 😊 I take the Indian numbering system as a case in point "3,00,00,000" (https://en.wikipedia.org/wiki/Indian_numbering_system)

[RasmusBurge-CG]

@dnil I see, good point. I will leave some options to prod.

Option 1

Option 2

Option 3

Option 4
Leave it as it is

[RasmusBurge-CG]

Option 1 was selected, discussion open office 2026-02-10

[dnil]

Ajajaj. Oh well, too late, you can't argue with office democracy. Next time, just silently follow the SI / NIST, and consider text-nowrap or white-space:nowrap. 😁

[RasmusBurge-CG]

Ajajaj. Oh well, too late, you can't argue with office democracy. Next time, just silently follow the SI / NIST, and consider text-nowrap or white-space:nowrap. 😁

Thanks, Daniel, very helpful.
Could I ask the reviewer to consider this and help me navigate the tricky waters.

[Vince-janv]

👌

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Vince-janv]

⭐