# `Mpan`

A UK electricity supply's MPAN core (Elexon), 13 digits, its check digit passing: `1200012345679`.

[Other with a published standard](types.md#other-with-a-published-standard); not ordered; personal data (contact); since Jadpo 0.1.0.

## Make one

Build one from its text, `Mpan("1200012345679")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: Mpan)` reads one from its text; text that isn't one at all fails `malformed`, such as `1200012345678`, `120001234567` or `S 1200012345679`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `1200012345679` | `"1200012345679"` |
| `2300004567890` | `"2300004567890"` |

It is stored in one column named for the field, of type `text`. `2300004567890` is stored as `'2300004567890'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `1200012345679` | `1200012345679` |
| `2300004567890` | `2300004567890` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.