https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37675 --- Comment #18 from David Cook <dcook@prosentient.com.au> --- (In reply to Alexander Wagner from comment #16)
I just added this comment to give an idea how far one would need to scale up the number of authors to be done with (for a while). Besides getting the ids right there might even be some issues rendering the display of whatever editor you use, btw.
Mmm I understand you now. Could also cause issues rendering on the detail page and search results. Could be a good reason to build in some "length handling" for some of the interfaces.
We were pondering on using Koha as the successor system for our current repository, that is also based on Marc21 and we have this several k author lists use a lot of normalizations etc. Koha would fit a lot of bills. It would however require Koha to get a decent OA repository component. (join² was pondering if we could pull this off, but it was finally decided otherwise for other reasons.)
Still, I think it would be worthwhile to add a decent OA repository component to Koha, but that's another story and also quite a task to get it right. It is actually quite convenient if your repo is your catalogue. I'll miss that.
I hope some day that Koha is more modular so that it would be easier to add in these components. Although part of the problem is maintenance. It's not easy for a small number of volunteers to maintain such a large and growing codebase. Tough to be all things to all people... But I'd be interested to hear more.
It's probably not a matter of size of the library, but on the research area of your institution. I would definitely call us pretty small, while Atlas and CMS papers are regulars in our systems. (More on the repository end / article cataloguing of course.)
What I mean is larger institutions usually have more money which means they can pay for more systems. But that's a good point. I do support some library systems for small low budget parts of large wealthy organisations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.