Perform the following steps:
2. Table of Contents and Index
3. Bibliography Entry
4. From document content
6. Compete info in the Define Bibliography Entry form
This creates a reference to the just created Bibliography entry.
When the reference is deleted, all information in the form and the Short name are also deleted.
It would be much better to be able to do the following:
1. Select the Short name on the Insert Bibliography Entry form
2. Have a Delete button to delete the Short name plus form information.
In that case:
1. Bibliography information can easily be re-used between templates (assuming that templates created from a document retain this)
2. Mistakes made by deleting references to Bibliography entries do not delete all information
3. One does not need to track in the document how many times a reference to a particular Bibliography entry is made. For example, if two references are made, then deleting one reference will not delete the form info, but if one reference is made and deleting that info will cause the situation mentioned under item 2.
Although in its current implementation the Bibliography Entry creation "From document content' seems to be far more robust than "from bibliography database" (see https://bugs.documentfoundation.org/show_bug.cgi?id=108641 ), I'm still reluctant to use it because of items 2 and 3 and will probably end up putting bibliography entries (citations) straight into the document without using the entry form and use cross references to numbered paragraphs indicating the entries.
Without a clear perspective for the bibliography it's hard to make a good proposal. Quickly reading over the request it sounds a bit out of scope.
If we automatically/on confirmation add the new BE to the database it's not possible to have multiple bibliography databases. That's not possible yet but might be needed in future.
Since the option exists to store the BE in the document and the database you have all the freedom to save it => WFM.
We could alternatively remove the option to store BE in the document but there might be use cases where it's needed.
And last but not least there was not much interest in this topic for years. So let's resolve it.