Bug 38865 - API functionality needed in lists to allow future connectivity with discovery systems
Summary: API functionality needed in lists to allow future connectivity with discovery...
Status: RESOLVED DUPLICATE of bug 27603
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-10 18:11 UTC by Christopher Brannon
Modified: 2025-01-14 15:41 UTC (History)
2 users (show)

See Also:
GIT URL:
Change sponsored?: ---
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 Christopher Brannon 2025-01-10 18:11:20 UTC
Lists can currently be read by outside discovery systems (I am assuming this is how Aspen can import current lists from Koha), but there is no current API path to allow lists to be managed centrally through Koha.  Once Aspen imports the lists, they are two separate lists.

I would like to see API enhanced to allow discovery systems to work in tandem with discovery systems, so those systems can work together and the lists can be maintained in one place.
Comment 1 Katrin Fischer 2025-01-10 18:40:30 UTC

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