Bug 10198 - Add the ability to import and export authorized values
Summary: Add the ability to import and export authorized values
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on: 10363
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-06 10:35 UTC by Mathieu Saby
Modified: 2025-10-27 23:12 UTC (History)
13 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Saby 2013-05-06 10:35:46 UTC
We can not import and export easily from staff interface a list of authorized values (in CSV or SQL).
It would be useful.

M. Saby
Comment 1 Narcis Garcia 2018-07-18 06:24:20 UTC
It would be useful to allow easy backups, same as it can be done with "MARC frameworks"
Comment 2 David Cook 2025-10-24 00:01:27 UTC
After responding to a listserv query today, I thought that this would actually be a really useful feature to allow libraries to manage their authorized value lists in more manageable ways.

Doing adds/updates/deletes one-by-one in the web UI isn't really sustainable once you get past a certain list size. 

This means that people have to turn to someone with backend access to write a script or do a direct SQL import. This is fine if you have vendor support, but if you don't... you'd be in a rough spot.
Comment 3 David Cook 2025-10-24 00:03:55 UTC
Of course, this is easier said than done, as different libraries might want different things in different situations.

For instance, you might want to export an existing list, and then only include the entries in the import (ie delete existing list and then import fresh values), or maybe you only want add/update with the imports and not to delete any existing entries. There might be other options that aren't coming to mind right now as well.
Comment 4 Mathieu Saby 2025-10-24 10:35:48 UTC
What would have been useful in 2013 is still useful today ;-)
Of course, we could ask our service provider, but I'm not sure if it would be free, and anything that gives end users more autonomy on staff interface seems welcome.
Comment 5 David Cook 2025-10-26 22:37:38 UTC
(In reply to Mathieu Saby from comment #4)
> What would have been useful in 2013 is still useful today ;-)

100%

> Of course, we could ask our service provider, but I'm not sure if it would
> be free, and anything that gives end users more autonomy on staff interface
> seems welcome.

Yeah, I don't think I can prioritize this one either. If it was sponsored, yes, but otherwise... it's one of those things where the status quo seems "good enough" for now :/.
Comment 6 Mathieu Saby 2025-10-27 08:24:01 UTC
In my opinion, even though it would be useful in absolute terms, there are undoubtedly many more important and urgent improvements or corrections to be made.
Comment 7 David Cook 2025-10-27 23:12:42 UTC
(In reply to Mathieu Saby from comment #6)
> In my opinion, even though it would be useful in absolute terms, there are
> undoubtedly many more important and urgent improvements or corrections to be
> made.

I'm currently looking through my emails and thinking that same thing haha. Unfortunately, there are only a limited number of hours in a day...