Summary: | REST API should include a patron import function | ||
---|---|---|---|
Product: | Koha | Reporter: | Justin Rittenhouse <jrittenh> |
Component: | REST API | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Justin Rittenhouse
2022-09-21 13:26:05 UTC
We have implemented a batch update with the current API using look-ups and also deciding on which fields in a patron we want to update. I think you have more control of the process the current way, but what you describe has it's own merits. Maybe instead of using the patron API using the patron import CLI script could be an option for you? It's very close to the how the tool works. |