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.
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 add_name.php. Show everything
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.
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.
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.
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.
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.
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.
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 older shared-key check on the add-name page was retired. The page now relies on the site's sign-in and permissions, which cover viewing it as well as saving, and it refuses to load if the sign-in system is not running.
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.
The add-name 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.