<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Allow option for Bibliography database to be duplicated and saved with the current Writer file"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135450">135450</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Allow option for Bibliography database to be duplicated and saved with the current Writer file
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Documentation
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>greenandpleasant2000-support@yahoo.co.uk
</td>
</tr>
<tr>
<th>CC</th>
<td>olivier.hallot@libreoffice.org
</td>
</tr></table>
<p>
<div>
<pre>Version: 6.4.4.2 (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
Calc: threaded
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.
SUGGESTION
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>