# `Orcid`

A researcher's ORCID iD, its ISO 7064 check character passing: `0000-0002-1825-0097`.

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

## Make one

Build one from its text, `Orcid("0000-0002-1825-0097")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: Orcid)` reads one from its text; text that isn't one at all fails `malformed`, such as `0000-0002-1825-0098`, `0000000218250097` or `https://orcid.org/0000-0002-1825-0097`.

## 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 |
|---|---|
| `0000-0002-1825-0097` | `"0000-0002-1825-0097"` |
| `0000-0001-5109-3700` | `"0000-0001-5109-3700"` |
| `0000-0002-1694-233X` | `"0000-0002-1694-233X"` |

It is stored in one column named for the field, of type `text`. `0000-0001-5109-3700` is stored as `'0000-0001-5109-3700'`.

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `0000-0002-1825-0097` | `0000-0002-1825-0097` |
| `0000-0001-5109-3700` | `0000-0001-5109-3700` |
| `0000-0002-1694-233X` | `0000-0002-1694-233X` |

## 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.