Bug 18239 - Add Open Document export option to items search
Summary: Add Open Document export option to items search
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-09 14:16 UTC by Katrin Fischer
Modified: 2024-08-09 18:40 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2017-03-09 14:16:34 UTC 
For libraries using Excel the CSV export often shows some problems: Umlauts/diacritics are broken, because UTF-8 is not detected automatically and the separators are not recognized with all data appearing in one line.

What works really will, also with Excel, is the Open Document format that was added for exporting reports. It would be nice if this option could also be added to the items search in the staff interface.
Comment 1 Chanel Wheeler 2024-08-02 15:20:23 UTC 
Something needs to be done so that the search results open in Excel well. Parsing semicolon-separated fields is harder than lots of our library staff can handle (not to mention how tedious it is). If Open Document is the solution, I'm 100% behind that.
Comment 2 Angela Berrett 2024-08-09 18:40:54 UTC 
+1  We often lose a lot of information when doing a CSV export - the data just doesn't export.  And as stated in the original comment, the diacritics are broken.