Development changelog

On the asset history page, editing a label window now shows the preview's field, current and new columns side by side. Before, a long note or source link stretched the preview wider than its card and the column of new values was cut off, so a correct change looked as if nothing had changed.

Cells in tables nested inside the record card were picking up the history table's no-wrap rule, so they never wrapped. Nested cells now wrap, and the preview table keeps its three columns within the card's width. A styling change only: what is validated and saved is unchanged.

Adding an asset name now offers two choices, Paste JSON or Enter by hand, and shows only the one chosen. A pasted block opens the form already filled in and checked, so the empty form no longer sits under the paste box.

Pasting opens by default, since moving records between systems is the common case. A paste that cannot be read stays on the paste box with its errors; one that loads becomes the editable record, with a link back to paste a different block. Validation and the write are unchanged.

The asset history page took the shared layout, and a label window can now be corrected by form or by JSON with a preview of the differences before saving.

The assets page follows the same layout, with its entity shown as a one-line linked record, and gained the same form-or-JSON editing with a preview of the differences.

An entity can now be corrected after it is created, by form or by pasting JSON. Both routes pass the same checks, show the differences before saving, and ask for explicit confirmation before an identifying field is overwritten.

The first click into the JSON box selects everything in it, so a paste replaces the old text. A second click places the cursor as usual; dragging, typing or an empty box are left alone.

A researched name record can be adopted onto an existing name record instead of being added beside it, replacing the name, dates and source while keeping the ticker and the asset link. Every change any mode makes to an existing name record is now logged with its previous values, and nothing is saved if the log cannot be written.

Until this version no page could change the name text of a record. Adoption is meant for the many imported names that each new asset already has a record for.

A name record's start date can be corrected after it has been set, when a better source turns up. It is the only filled-in field that can be changed this way.

The JSON box on the add-entity page starts empty, with the sample shown as grey placeholder text, so a pasted record no longer has to replace the sample first.

When no exchange is chosen, the exchange code in the pasted JSON now picks it, if it matches exactly one known exchange. A chosen exchange still wins and is still checked against the code, an unknown code is still refused, and the preview asks for the venue to be confirmed.

The entity is still always chosen by hand, because a CIK can match more than one record or none.

The JSON box on the add-asset page starts empty, with the sample as grey placeholder text, unless the page arrived with an entity already chosen, in which case the filled-in sample is kept.

Three corrections to the asset history checks: the identifier types offered now match the ones the database accepts; one asset may carry two different tickers at once, as a security listed on two exchanges does, while the same ticker still cannot overlap itself; and marking a closed window as primary is now refused before saving, since the database would refuse it anyway.

An entity's notes can be corrected in place: a pencil opens the notes, and Save writes them without reloading the page. Notes are the only field that can be changed here, since they hold the record's sources.

The save goes through a new shared identity library, so the asset page can use the same rules. Saving unchanged notes writes nothing.

Editing an asset's notes now happens in place, without reloading the page, and the save uses the same shared code as the entity page, so both follow one set of rules.

The old bookmarkable address for opening the notes editor still works. The editor now needs JavaScript.

A shared identity library with one job: saving a single field edited in place on the entity and asset pages. Only the notes fields are open to it; every other column is closed until there is a decision to open it, and the reason for each is written beside the list.

The list of editable tables and columns is fixed in the library, so a page cannot widen it. The save normalises line endings, writes nothing when the value is unchanged, and stamps the record's last-updated time.

An edit mode fills in the empty fields of an existing name record, its dates and source, and changes nothing that already holds a value. Fields with a value are shown locked.

Pasting JSON on the add-name page no longer throws away an asset that was already chosen. The paste form had not carried the asset choice with it, so the record reverted to unlinked.

A name record can be pasted as JSON, which fills in the form for checking rather than saving directly. The JSON never sets the asset; it can state the ticker and entity CIK it expects, and a mismatch with the chosen asset is refused.

When an asset has no name but unlinked name records with its exact symbol exist, its row offers "choose name (N)" first, with adding a new name second, so the existing record gets linked instead of a duplicate being created. An unlinked name row also gets a "link" action.

The count is an exact symbol match on purpose; looser matches belong to the link page's own search. The search page still writes nothing: the linking happens on a separate page with its own preview and confirm.

A link mode attaches an existing unlinked name record to its asset, so the record is kept rather than duplicated. It checks for clashes the link would create, and re-pointing a record already linked to another asset needs a separate acknowledgment.

An entity can be entered as form fields or pasted as JSON. Both tabs feed the same checks, the same preview and the same single save, and the tabs keep each other up to date. Unknown keys in the JSON are refused by name, and only one entity is accepted per paste.

Confirm saves what the preview showed, never the JSON text again.

An asset can be entered as form fields or pasted as JSON, but the entity and exchange are always chosen from the lists, never taken from the JSON. Instead the JSON can state the entity's name or CIK and the exchange code it expects, and the preview refuses a choice that does not match.

Internal row ids mean nothing outside one database, and a wrong one would save quietly under the wrong issuer; a stated name or code is checked instead.

The JSON entry tab on the asset history page now spells out its format: every key, which are required, the limits, both lists of allowed values and a second worked example. The value lists are printed from the same lists the validator checks.

Help text only; no change to what is accepted.

A page for asset history, the label windows that say which ticker or other identifier each asset carried between which dates. It lists every window with filters and an integrity summary, and adds windows, or renames a label by closing one window and opening the next, through a form or pasted JSON with a preview before anything is saved.

A rename is one transaction. The integrity summary is counted across the whole table, never just the filtered view.

Arriving from an entity's "+ add asset" link now opens the form with that entity already chosen, and the JSON sample already names it. The link's setting had been ignored, so the form opened blank; an id that matches no entity now shows a warning.

Arriving from a blank name on the search or asset page now opens the form with that asset already chosen, and each asset in the picker shows its entity's name and CIK. The asset had been dropped, so the new name was saved unlinked and the blank stayed blank.

An asset's notes can be edited on its page. It is the first thing the page writes to the asset record, and saving unchanged notes writes nothing.

A new name can now be tied to a specific asset, picked from the assets using that ticker, or left unlinked on purpose. Clashes are graded into blocking, advisory and context, and the form stays live, offering Confirm only once the save is allowed and any advisory is acknowledged for that exact record.

An acknowledgment goes stale if the advisories change between checking and confirming.

A page for adding an asset name: the name a ticker carried from a given date, with the names already on file for that ticker shown alongside and a clash with an existing record blocked.

A page for adding an entity by hand: a form, a preview, then a confirm that writes one record. It pads a CIK to ten digits, checks an LEI's format, limits the entity type to the allowed list, and warns about possible duplicates by name, CIK or LEI.

A page for adding an asset by hand: a form, a preview, then a confirm that writes one record. The entity and exchange are required and chosen from lists of existing records, the class, role and status come from the allowed lists, and a symbol already in use triggers a warning.