Bug 146884 - Export Paths should be saved in the Document
Summary: Export Paths should be saved in the Document
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Save
  Show dependency treegraph
 
Reported: 2022-01-20 17:28 UTC by Ian Eales
Modified: 2022-01-28 11:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Eales 2022-01-20 17:28:52 UTC
Description:
Export is to the last used LO path. When a user has hundreds of LO documents and is likely working on several tens at any one time, the last document path is invariably wrong.

If the export path is saved in the document, it would save a great deal of repeated tree navigation to correctly locate the file.

The feature should be implemented for objects like charts and whole documents as PDFs as these are often exported to web servers.

Steps to Reproduce:
1.Export object from a document
2.Export another object from a document in a different path
3.

Actual Results:
Export Path is the last used file path

Expected Results:
Export path should persist with the document.


Reproducible: Always


User Profile Reset: No



Additional Info:
LO should retain the export path internally. If the path does not exist, use doc path.
Comment 1 V Stuart Foote 2022-01-20 19:27:09 UTC
Isn't this the opposite of internal path setting for current "context" for bug 129886

This seems much more invasive and would nneed to extend ODF to store the working path within the document.

I'm neutral on merit, but seems like a lot of effort.

=-ref-=

https://gerrit.libreoffice.org/c/core/+/118597
Comment 2 V Stuart Foote 2022-01-20 19:32:45 UTC
sorry, wrong ref BZ a dupe -- the patch was for bug 126665
Comment 3 Heiko Tietze 2022-01-21 06:44:05 UTC
My bug 126665 comment 2 is still valid: different scenarios require different solutions. Samuel's patch solves it. Do you agree, Ian?
Comment 4 Ian Eales 2022-01-21 18:43:04 UTC
It's not the same.
I'm not creating new files.

I have files I work on almost every day, some of which are close to a decade old.

I export several graphs from one workbook related to daily precipitation to //webserver/assets/wX/.

When I export a graph from a workbook related to tube amplifier distortion, I have to navigate to //NAS/Share/Ian/!!_Manuals/product/KitManual/images/

If the precipitation file saved //webserver/assets/wX/ and the tube amplifier file saved //NAS/Share/Ian/!!_Manuals/product/KitManual/images/ export path, it would make things much easier.

Ideally, LibO would save a specific graph name, but I could wait until 8.x for that ;)
Comment 5 QA Administrators 2022-01-22 03:57:10 UTC Comment hidden (obsolete)
Comment 6 Heiko Tietze 2022-01-24 09:48:08 UTC
We had many requests to remember the last used path instead using the default (bug 126665) that resulted in the current implementation. If we change something it has to be an option.
Comment 7 Samuel Mehrbrodt (allotropia) 2022-01-24 13:42:53 UTC
Agree that "Export" is probably special here.
Usually when you export a document, you are not interested in the path where you exported the last document, but either the place you saved your document, or the place you last exported the current document too.
So having the last Export-To location saved in the document might make sense. Of course it adds personal information to the document, which we need to consider (at least make this optional).

@Ian: Note that for your use case, and as long as this is not implemented, you can also write a small macro which exports the document to the desired location.
Comment 8 Jean-Baptiste Faure 2022-01-27 16:20:05 UTC
(In reply to Ian Eales from comment #4)
> 
> I export several graphs from one workbook related to daily precipitation to
> //webserver/assets/wX/.
> 
> When I export a graph from a workbook related to tube amplifier distortion,
> I have to navigate to //NAS/Share/Ian/!!_Manuals/product/KitManual/images/
> 
> If the precipitation file saved //webserver/assets/wX/ and the tube
> amplifier file saved //NAS/Share/Ian/!!_Manuals/product/KitManual/images/
> export path, it would make things much easier.

For such a use-case, I would prefer to use the functionalities of the file manager of my OS. For example, with Nautilus (Ubuntu 20.04) it is easy to define preferred locations which are available in one click in the left panel of the filepicker.

Saving an export path with the document is adding a personal data in a file that will be difficult to remove if you need to provide a document without any personal data.
Additionally, that will not solve the case where you need several different export paths for the same document. For example, one for PDF export, one for ePub export, one for OOXML export, etc.  

Best regards. JBF
Comment 9 Ian Eales 2022-01-27 16:40:17 UTC
More than about 20 folders in the quick pick becomes unwieldy.

I probably have 200 folders to which I export images.

They are my files and not going anywhere. An option to save export path would give the user control. Don't handicap the capable.

Separate paths for PDF and images is not a problem. To date, never exported a doc as a PDF, typically from Writer, to the same location as an image, typically graphs from Calc.
Comment 10 Heiko Tietze 2022-01-28 11:11:31 UTC
(In reply to Ian Eales from comment #9)
> They are my files and not going anywhere.

But we have to consider other scenarios too. And I tend to resolve WONTFIX, but leaving open for Samuel.

If we add an option it seems best to have it at  Tools > Options > Load/Save > General (or as expert option). The export path could be shown with File > Properties. And cleaning the document needs to consider this information too.