Version: 22.214.171.124 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: default; VCL: win;
Locale: en-GB (en_GB); UI-Language: en-GB
This may have been reported before in some form, but I am filing it as an enhancement. Perhaps I've misunderstood something, but this feature seems very user-unfriendly.
The default BIBLIOGRAPHY DATABASE, which is conveniently formatted for use with Writer, IS NOT SAVED WITH THE WRITER FILE as a document exclusively for the use of, and only accessible from, THAT Writer file. In fact, the Bibliography database is shared between ALL files.
If you change it in another Writer file, the Bibliography database in ALL dependent Writer files changes, although, AFAICS, the visible Bibliography remains the same and there is a safeguard to prevent the user updating the display with the changed database.
This is unintuitive, and confounding for the user. S/he finds that not only has the database been mysteriously changed, but the former entries are not available to enter in the text, if any additions need to be made.
Allow the user the option of duplicating the shared bibliography database and have it save with the currently active Writer file. The database can now only be accessed and changed from THIS linked Writer file. Naturally, the database will still be available to link to any other file if required.
Also, saves of the Bibliography database need to be under the control of the user, just like Writer document saves.
Although I like LO, I must admit that bibliography tool in LO is a mess and there has been a (short) discussion to remove it completely and use an extension by default, for example Zotero.
Not sure, if your enhancement request is something for design-team, I add them in cc
Users want to keep at least a minimum viable bibliography [1,2]. An advantage over 3rd party tools would be indeed if the database is integrated into the document. Wouldn't _duplicate_ however - or ask whether to move or copy the DB.