Summary: | Add Donors to Acquisitions | ||
---|---|---|---|
Product: | Koha | Reporter: | Esther Melander <esther.melander> |
Component: | Acquisitions | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | angela.berrett, michaela.sieber |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Esther Melander
2024-08-23 20:25:04 UTC
Hi Esther, some ideas about this for a possible workaround or starting a solution: * Create a vendor type of Donor to assign to these vendors. This will help to distinguish them in reporting and maybe later other functionality will be added to allow for filtering. * Use a "Donor" vendor for all of them and a "Donor fund". The statistics fields linked to the fund could then be used to track more information about the individual donor either as pull downs or free text. I guess it depends on how much information about the Donor is needed and how structured it needs to be. + 1 We would love to see this differentiation. We have thousands of individual donors all mixed in with purchasing vendors. We have created different authorized values to distinguish them, but we can't sort them or isolate them that way - it's just a label for us. Have a different page would save a lot of time and help our vendors load faster. Katrin, The workaround is to do as you suggest. However, if a library tracks individual donors rather than a generic vendor of Donor, it becomes problematic because they can create thousands of donor vendors. Thus the need to separate vendors from donors. There are few library examples with 8,000 vendors and 99.9% of them are actually donors. This number of vendors can cause slow page loading and searching, which I think has been addressed in other bugs. (In reply to Esther Melander from comment #3) > Katrin, > > The workaround is to do as you suggest. However, if a library tracks > individual donors rather than a generic vendor of Donor, it becomes > problematic because they can create thousands of donor vendors. Thus the > need to separate vendors from donors. There are few library examples with > 8,000 vendors and 99.9% of them are actually donors. This number of vendors > can cause slow page loading and searching, which I think has been addressed > in other bugs. Hi Esther, thanks for explaining! I think some of these problems will be improved by the work on moving vendors to vue and making things all API driven. I hesitate to move them to a separate table in the database, I think a lot of the issues could be solved by filtering and having different "types". |