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.
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 topic record export. Show everything
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 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.
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.
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.