Description: LO 7.5.1.2 Win 7/10/11-64 [1] The bibliographic database is separate from Writer. Renaming, moving, and copying both a Writer document and the Bibliographic DB is not supported. They have to be treated separately. [2] Can not copy the Bibliographic DB between users because the address to the DB in $System%username/appdata/remote/libreoffice is hardcoded. Steps to Reproduce: 1.Change the test Bibliographic DB while in Writer. 2.Perform a copy, move, rename, ... of the Writer document. 3. _OR_ Create a new Bibliographic DB (undefined how to do this) 4. Repeat step 2. Actual Results: Copying and pasting the DB to a another Username account is not possible. Expected Results: Copy the DB is possible. Rename, copy, paste, ... should be integrated into Wrtier. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes All, embedded and non-embedded DB, should be integrated with Writer. Any operation on Writer should have an equal effect on the DB and it should be able to copy and paste Writer and the Bibliographic DB to another user account on the same machine or another.
Lostbits, thank you for reporting the bug. I've tried the following steps. Do they describe your problem? If not, please desribe correct steps in detail. Thank you. 1. Open a document in writer or create new document 2. Tools -> Bibliography Database 3. Change an entry in DB (for example change Type in first entry from "Book" to "Journal") 4. Close DB (change is saved) 5. Save writer document 6. Open folder with saved document and change name of document 7. Open document in Writer 8. Tools -> Bibiography Actual result: BD empty and error message: "The following column names could not be assigned" Expected result: BD opens without error message Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded I'm not an expert for this topic, but there might be some reports, that are at least related to this bug.
If you want to copy the default data source "Bibliography", copy the directory <user_profile>/database/biblio/
I thought that I'd put this in as a request for an enhancement, not as a bug. Sorry about the confusion. What is requested is that the DB used within the document be moved with the document when necessary. In this regard there are two cases: [1] A move on the same computer within the same user account, and {2] A move to a source external to the originating computer and user account. In [1] there is no change needed. That is, going from the same user to the same user allows access to the DB (if absolute paths are used). If absolute paths are not used, then the DB must be moved also or a path the the DB generated. In [2] a change is needed. Both absolute and relative paths are no longer valid. If on the same machine then there are security issues. If on different machinges (or the cloud), the DB is unavailable. The suggested solution, eg, manually moving the DB, will work providing the Data Source is changed appropriately. But, as an enhancement, it would be desirable for LO to do the suggested operations on the users behalf. If elected, this requires an augmented interface to include copy, move, rename of a given document, or the conversion of an external DB to an internal DB. The conversion is stated to be possible, so the issue disappears, but there does not seem to any mechanism to do this within (at least) Writer. The existing Bibliographic documentation provides no guidance on any of these matters, to wit, moving, copying, renaming the LO Writer document or changing an external DB to an internal one, nor is there any description of any of these. And to the point, my volunteering of documentation services has been silently rejected, hence, I have no means to contribute to this effort.
Lostbits, thank you for clarification. I think your request is coverd by bug 135450, so I mark it as duplicate. Feel free to change it back to UNCONFIRMED with a short reasonng, if you disagree. *** This bug has been marked as a duplicate of bug 135450 ***