Bug 24425 - Remove utf8 as an export option
Summary: Remove utf8 as an export option
Status: RESOLVED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: David Roberts
QA Contact: Testopia
URL:
Keywords: Academy
Depends on:
Blocks:
 
Reported: 2020-01-14 23:57 UTC by Aleisha Amohia
Modified: 2023-12-10 10: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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aleisha Amohia 2020-01-14 23:57:53 UTC
it's a character encoding, not a file type. Doesn't really makes sense.

Option exists for both bibliographic records and authority records.
Comment 1 David Roberts 2020-04-17 22:16:06 UTC
There are three MARC options:

MARC (non-Unicode/MARC-8)
MARC (Unicode/UTF-8)
MARC (Unicode/UTF-8, Standard)

I'm not sure what the difference between Unicode and Unicode Standard are, but it seems sensible to keep at least one of these. In order for compatibility with other systems, it seems most practical to keep a non-unicode and a unicode export, but I'm happy to take advice on this.
Comment 2 Katrin Fischer 2020-04-18 02:26:25 UTC
Hm, I am not sure if Aleisha meant the download/export options for records or not. Aleisha, can you clarify?


> MARC (non-Unicode/MARC-8)
> MARC (Unicode/UTF-8)
> MARC (Unicode/UTF-8, Standard)
> 
> I'm not sure what the difference between Unicode and Unicode Standard are,
> but it seems sensible to keep at least one of these. 

Standard doesn't include the non-standard 9xx $9 x9x, xx9 custom fields :)
Comment 3 Katrin Fischer 2023-12-10 10:40:09 UTC
I believe all available options produce different formats/output, so this might be invalid. The internal naming could probably be improved.