Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `src/app/shared/modules/scientific-metadata/metadata-view/metadata-view.component.ts:180-181` </location>
<code_context>
     public prettyUnit: PrettyUnitPipe,
   ) {}

-  getHumanReadableName(name: string): string {
-    return this.titleCase.transform(this.replaceUnderscore.transform(name));
-  }
-
</code_context>

<issue_to_address>
**issue:** Removal of fallback for human readable name may reduce robustness.

Please verify that all metadata objects consistently provide 'human_name' to avoid missing display names.
</issue_to_address>

### Comment 2
<location> `src/app/shared/modules/dynamic-material-table/table/dynamic-mat-table.component.html:167-162` </location>
<code_context>
-              [innerHTML]="columnName(row, column)"
             >
+              <ng-container *ngIf="column.hoverOnCell; else noHoverCell">
+                <span
+                  #hoverOriginSpan="cdkOverlayOrigin"
+                  cdkOverlayOrigin
+                  (mouseenter)="hoverKey = makeKey(row, column)"
+                  (mouseleave)="hoverKey = null"
+                  [innerHTML]="columnName(row, column)"
+                ></span>
+                <ng-template
</code_context>

<issue_to_address>
**🚨 issue (security):** Using [innerHTML] for cell content may introduce XSS risk if content is not sanitized.

If columnName returns untrusted data, sanitize it before assigning to [innerHTML] to prevent XSS.
</issue_to_address>

### Comment 3
<location> `src/app/shared/modules/dynamic-material-table/table/dynamic-mat-table.component.ts:260` </location>
<code_context>
       offsetX: 4,
     },
   ];
+  /** Overlay positions for metadata hover */
+  metadataOverlayPositions: ConnectedPosition[] = [
+    {
</code_context>

<issue_to_address>
**issue (complexity):** Consider moving overlay position configuration and hover content formatting into shared constants and a pipe to separate presentation logic from component behavior.

Consider extracting the “presentation” bits out of your component and re-using them via a constant and a pipe (or template). This keeps your component’s TS focused on behavior and makes both the overlay positions and hover-content easy to share and test. For example:

1) Extract your overlay positions to a shared constant:

```ts
// src/app/shared/constants/overlay-positions.ts
import { ConnectedPosition } from '@angular/cdk/overlay';

export const METADATA_OVERLAY_POSITIONS: ConnectedPosition[] = [
  {
    originX: 'end',
    originY: 'center',
    overlayX: 'start',
    overlayY: 'center',
    offsetX: 8,
  },
  {
    originX: 'start',
    originY: 'center',
    overlayX: 'end',
    overlayY: 'center',
    offsetX: -8,
  },
];
```

```ts
// in your component
import { METADATA_OVERLAY_POSITIONS } from 'app/shared/constants/overlay-positions';

@Component({ … })
export class MyTableComponent<T> {
  metadataOverlayPositions = METADATA_OVERLAY_POSITIONS;
  …
}
```

2) Create a small pipe for your hover HTML:

```ts
// src/app/shared/pipes/metadata-hover.pipe.ts
import { Pipe, PipeTransform } from '@angular/core';

@Pipe({ name: 'metadataHover' })
export class MetadataHoverPipe implements PipeTransform {
  transform(row: any): string {
    const raw = `<strong>Raw name:</strong> ${row.name}`;
    if (!row.human_name) {
      return raw;
    }
    return `<strong>Human readable name:</strong> ${row.human_name}<br>${raw}`;
  }
}
```

3) In your template bind via `innerHTML` (or use it inside a `<ng-template>`):

```html
<ng-template #metadataTooltip let-row="row">
  <div [innerHTML]="row | metadataHover"></div>
</ng-template>

<button
  [cdkOverlayOrigin]="trigger"
  [cdkConnectedOverlayPositions]="metadataOverlayPositions"
  [cdkConnectedOverlayHasBackdrop]="false"
  [cdkConnectedOverlayTemplate]="metadataTooltip"
  [cdkConnectedOverlayContext]="{ row: row }">
  {{ row.name }}
</button>
```

This removes manual string builds from your component class, centralizes the overlay config, and reuses logic consistently.
</issue_to_address>