Some tables do not have Schema Config records, making them unhideable

[grantfitzsimmons]

Describe the bug
There are a number of tables that do not have a schema config records associated with them, which presents a problem as the "Hide Table" option is not available. This option controls whether or not users can see and add a table to the data entry menu.

Known tables:

• DNASequencingRunAttachment
• LocalityUpdate
• LocalityUpdateRowResult

This was reported by Museum für Naturkunde Berlin when going through and modifying the visibility of tables in the Schema Config.

Comparing the splocalecontainer name field against the tables in the schema config list (on the sp7demofish database) yielded the following results:

• The splocalecontainer recordstaxononly and dnasequencerunattachment do not exist in the data model

• The splocalecontainer records are missing for localityupdate and localityupdaterowresult

  splocalecontainer_2025_11_24.csv
  all_schema_tables_2025_11_24.csv

To Reproduce
Steps to reproduce the behavior (can be done on any database, but links are for sp7demofish):

1. Go to User Tools
2. Go to Schema Config
3. Select English and then choose the following tables (see the crash):
   • DNASequencingRunAttachment (https://sp7demofish.specifycloud.org/specify/schema-config/en/DNASequencingRunAttachment)
   • LocalityUpdate (https://sp7demofish.specifycloud.org/specify/schema-config/en/localityupdate)
   • LocalityUpdateRowResult (https://sp7demofish.specifycloud.org/specify/schema-config/en/LocalityUpdateRowResult)

Error: Unable to find SpLocaleContainer for LocalityUpdateRowResult

Specify 7 Crash Report - 2025-11-24T21_01_56.920Z.txt

When reporting an issue on the production branch or any development version of Specify, please try to recreate the issue on the latest tagged release (v7) and indicate if it does not occur there, indicating a regression.

Expected behavior
These tables should have corresponding schema records, or at the very least, they should be hideable even if the field captions are non-editable.

Screenshots

Here an exemple with "DNASequencingRunAttachment"

If I click on this table, I will be taken directly to a blank page with an error message.

It is therefore not possible to click on this tickbox.

Reported By
Marion at MFNB on BoldDesk

[grantfitzsimmons]

I did some more digging while solving an issue for MHNG and found that as of v7.11.4, when comparing present schema config fields to the fields present in the model, there are a large number of missing schema records. We need to restore these and add a utility or Django command to restore them if they are missing (part of a larger 'self-healing' installation).

Discipline: Vertebrate Zoology (id=3)

Missing containers:
- DNASequencingRunAttachment
- LocalityUpdate
- LocalityUpdateRowResult

Missing fields:
- Attachment: spDataSetAttachments
- CollectionObject: collectionObjectType
- DNASequencingRunAttachment: ordinal, remarks, timestampCreated, timestampModified, version, attachment, createdByAgent, dnaSequencingRun, modifiedByAgent
- Discipline: tectonicUnitTreeDef
- Locality: collectingEvents
- LocalityUpdate: status, timestampcreated, timestampmodified, recordset, collection, specifyuser, createdbyagent, modifiedbyagent
- LocalityUpdateRowResult: rownumber, result, localityupdate
- SpQueryField: isStrict