Development changelog

The label-window section on the asset name page now links directly to the add form on the asset history page, with the asset already picked and the identifier type set to ticker, saving a click per record. A plain link to view the asset's windows sits beside it.

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.

The version histories that sat at the top of the five identity pages and their shared library have moved to this changelog. Each file now carries a link to its own changelog page instead.

The five identity pages now take their styling from the site's shared stylesheet. Each page's own styles were cut down to what is particular to it, and every removal was checked so that each element keeps the same look.

A few rules that several identity pages used, and no other page did, moved into the shared stylesheet.

The five identity pages now draw their shared parts from one library: the search bar, the entity and asset lines, the name and label-window lists, the name-join check, the edit comparison and the record update. Each page lost its own copy, so a fix to one of these parts now reaches every page at once.

Nothing a visitor sees changed. Each page refuses to load, and says why, if the library is missing or too old. An edit preview opened before this update is refused once as out of date and must be rebuilt. Name records keep their own audited save path and are not written by the library.

On the asset history page, a long source link no longer stretches the opened record past the edge of the screen. The link now shows the site and file name, with the full address still behind it, and long values wrap inside the record.

On the asset history page, the selected label window is no longer shown twice. Its one-line row is replaced by the opened record, which names the window in its header and lists every field once, with the JSON and Edit controls beside it.

Other windows in the timeline keep their one-line rows and stay clickable. The edit form opens in the same place. Display only.

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.

After adding or renaming a label window, the asset history page now opens the record of the new window in its timeline, with the confirmation and ledger links above it, instead of redrawing the whole table page.

The old screen stacked the confirmation, the whole-table integrity checks, the add form again and a filtered table, and refreshing it could resubmit the form. The page now redirects to the new window's record, so a refresh is safe. The write and its validation are unchanged.

On the asset history page, the record and the label timeline are now one table. Every label window the asset has carried is listed by type, oldest first, and the selected window opens beneath its own row with its fields, its portable JSON and an Edit button, matching the asset name page.

Previously the selected window appeared in its own block and again as a row in the timeline below it. Other windows in the timeline are now links that open that window in the same place, so the separate previous/next links were removed. Editing a window opens the same form, JSON entry and preview in that place. Display only: no validation or write behaviour changed.

On the asset name page, the record and the name timeline are now one table. Every name the asset has carried is listed oldest first, and the selected name opens beneath its own row with its fields, its portable JSON, its change history and an Edit button.

Previously the selected record appeared in its own block and again as a row in the timeline below it. Now other names in the timeline are links that open that name in the same place, so the separate previous/next links were removed. The change log moved from its own section into a Changes tab on the opened row, shown only when that record has been edited; the timeline's changes column still shows at a glance which records have history. A name not yet linked to an asset opens as a table of one, with other records sharing its ticker string listed separately because they may belong to different assets. Display only: no data entry, validation or write behaviour changed.

On the assets page, the ledger and price counts under Related records now find rows by the asset's id rather than its current ticker, so rows recorded under an earlier ticker are included and a ticker later reused by another company is not.

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.

On the research workflow board, the name column now opens the name record itself.

The asset name page took the shared layout: search bar, entity and asset as one-line records, the name with fields, JSON and edit, then the history below it.

Links to the three older single-purpose add pages were removed. Creating a record now happens on the page that shows that kind of record.

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.

The entities page was rebuilt around one record: a compact search bar with the four add buttons, the entity with its fields and its portable JSON form, then only the assets, names and history that belong to it.

Search gained a history block and an add-history button, so all four record types can be found and started from one page.

Search results now appear in a fixed order: entities, then assets, then names, then history. Each block shows its first ten rows with an option to show all, and entity matches are ranked by exact match first.

The "Add entity" links now open the new combined entities page in create mode instead of the separate add-entity page.

Viewing, creating and editing an entity now happen on one page. The separate add-entity page was folded in behind a "new" address, unchanged, and the view gained a "+ New entity" link.

Both halves were moved, not rewritten, and the combined page was checked by comparing its output with the two pages it replaced.

Each related-record count above zero on the asset page is now a link to the rows it counted. The corporate actions count was removed.

A zero or failed count stays plain, so a link always lands on rows.

Names and label windows on the asset page now open their own record pages, and adding or linking a name goes to the new asset name page instead of the retired add-name page.

Names first (2.0.1), label windows next (2.0.2).

Viewing, creating and editing an asset now happen on one page. The separate add-asset page was folded in behind a "new" address, unchanged, and the view gained a "+ New asset" link.

Both halves were moved, not rewritten. The same pattern as the entity page a step earlier.

Label window links on the asset name page open that window's own record instead of a filtered table scrolled to its JSON.

On a name record, the asset field now shows a short link, the asset's id and ticker. It had shown the asset's whole description, notes included, as one long link.

A page for asset names replaces the add-name page and adds what that page never had: a record view. Opening a name shows its fields and JSON, the asset it names, every other name on that asset in order with the joins between them checked, and the record's change log.

Adding, linking and correcting names moved over from the add-name page unchanged, with their validation and audit trail. A name id clicked anywhere else now opens the record, with the actions one click away.

After saving a window, the link to the ledger assets page opens it filtered to the asset just worked on, with a second link for an older ticker when one was entered, instead of the whole ledger.

Each label window can be opened as a record: its fields and JSON, with the windows before and after it on the same asset and the asset's names. A Rename from a record opens the form already pointed at that window.

The add-name page was superseded by the asset name page, which carries its add, link and edit modes unchanged and adds a record view.

Any name record in play on the add-name page can be shown as JSON in the site's standard format, with a Copy button, ready to paste on another copy of the site.

The add-entity page was superseded by the combined entities page, where creating an entity is the "new" mode. Its code moved there unchanged; the old page kept working until every link to it had been repointed.

The add-asset page was superseded by the combined assets page, where creating an asset is the "new" mode. Its code moved there unchanged; the old page kept working until every link to it had been repointed.

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.

"+ add asset" now appears on every entity, beside its asset count, not only on an entity with none. An issuer with several securities could only ever get its first one from this page.

The link is still withheld when the asset list could not be read, and the count then reads "unknown" instead of zero.

The asset history page can show a single window by its id, and whenever the view is narrowed to one asset it shows that asset's windows as one block of JSON with a Copy button, ready to paste on another copy of the site.

The exported asset id is deliberately 0, so an unedited paste is refused instead of filing the windows under the wrong asset on the receiving system. A closed window still marked primary is named before it is copied.

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.

Now that the entity page can write, it checks the editing permission itself and refuses to load at all if the sign-in system is not running, instead of opening to anyone.

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.

The entity record has a JSON tab beside its fields: the record in the site's standard format, with a Copy button, ready to paste into the add page on another copy of the site. It carries no row id, so the receiving system assigns its own.

First shown as a separate card under the fields (1.6.0), then moved into a tab (1.6.1). If the notes are edited after the page loads, the JSON is withdrawn with a prompt to reload rather than offering stale text.

Each label window on the asset page links to that window's record, and the add or edit windows button now opens the history page filtered to this asset. It had sent a setting the history page never read, so it always opened the whole table.

The asset record has a JSON tab beside its fields: the record in the site's standard format, with a Copy button, ready to paste into the add page on another copy of the site. Instead of internal ids it carries the entity's name and CIK and the exchange code, which the receiving page checks.

First shown as a card under the fields (1.10.0), then moved into a tab (1.10.2). A line above the JSON says when a record is missing something the add page requires. If the notes change after the page loads, the JSON is withdrawn with a prompt to reload.

Each name in the asset's name list links straight to the screen that fills in that name record's missing fields.