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.
What has changed on this site, in its database and in the scripts behind it, newest first. Older history is being filled in as it is reconstructed, and each entry says whether it was recorded at the time or rebuilt later.
Showing entries for file assets.php. Show everything
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 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.
Stories moved off the assets page to a page of their own in a new assertions area, because a story is an observation about an asset, not part of its identity.
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.
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.
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.
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.
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.
The asset page lists the asset's label windows: which ticker or other identifier it carried between which dates, which one is primary, and where each came from. These windows decide whether ledger rows can be matched to the asset.
The asset page lists every name the asset has carried, oldest first, and checks where one name ends and the next begins, marking each join as ok, a gap, an overlap or unknown. Unlinked name records that mention one of the asset's tickers are listed as a worklist, each with a link to review and link it.
The check reports and never changes a date. The worklist is a prompt for a person to decide, not a claim that those names belong to this asset.
The asset page now shows the asset's own name. Names had been looked up by ticker, so an old delisted company showed the name of the newer company that reused its ticker. A blank name now offers "+ add name" for this asset.
An older shared-key check on adding stories and editing notes was retired. The page now relies on the site's sign-in and permissions, which cover viewing it as well as writing, and it refuses to load if the sign-in system is not running.
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.
The asset page shows the asset's stories, newest first, and has a form to add one: a dated event with a title, body and tags, entered as fields or as JSON, previewed and then saved.
A follow-up the next day (1.1.1) keeps the page scrolled to the stories section while the form is open, previewed or re-shown.
An asset record page: one security with all of its fields, its entity and exchange shown by name, its status, and counts of related records such as prices and ledger rows.
The asset page moved into the site's admin tools area, where access is checked by role, and now uses the site's shared page header, footer and navigation. Every link and form on it, including the ones that save notes and stories, was updated to the new address.