Bug 24115 - patron import tool should have option to not overwrite specific fields
Summary: patron import tool should have option to not overwrite specific fields
Status: RESOLVED DUPLICATE of bug 27883
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-26 10:14 UTC by Jeremy Evans
Modified: 2022-01-02 15:22 UTC (History)
1 user (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 Jeremy Evans 2019-11-26 10:14:04 UTC
Following a test load of users exported from our active directory using the import users tool (Koha 18.11) we have encountered a few issues.
The default settings specified for the load are being applied to also overwrite existing users. For example, all users now have the same profile and home library. 

We would wish to have the option for the default settings to only apply for new users created and for example retain the current user profile and home library for existing users.  These 2 fields would not be included in the file loaded to Koha from the Active directory.
There are other fields such as the email address, expiry date, address, etc where we do want the load to overwrite the existing records to keep these up to date in Koha.

Probably another tick box next to each of the fields listed for the default settings to only apply to new records would make it flexible to retain specific fields whilst allowing others to be updated  

As a minimum this should apply to user profile and home library.
Comment 1 AspenCat Team 2021-12-27 20:10:52 UTC
This would be very helpful for us when we want to update certain aspects of patron export automatically, but reserve some fields for changing.  Anything we can do to get this moving, we would be happy to. - Bob Bennhoff
Comment 2 Katrin Fischer 2022-01-02 15:22:32 UTC
Hi, I believe this is a duplicate to bug 27883 which implemented this in 21.11.

*** This bug has been marked as a duplicate of bug 27883 ***