3 ms·

I think the path to take would be to add this feature into the library CMS systems out there. Sell it to libraries as an add-on plugin as a way to drive engagem

• gricardo99 9y ago
  That's an interesting idea. Some quick googling and I found there seem to be a number of CMS systems for libraries, some open source, some vendor/closed. That got me thinking that another angle on this would be to write the curator part (e.g. some ML model trained on reader preferences), and provide that as a SaaS to end-users. But I see that something similar already exists[1]... of course. 1 - http://www.whatshouldireadnext.com/ http://www.whatshouldireadnext.com/
• jogjayr 9y ago
  The problem with that is there is a large variety of CMSes out there. It may not be cost-effective to write plugins for every CMS. Some of them may not not have documented plugin APIs or may not have the ability to have plugins at all. Libraries may not necessarily have the budget to buy plugins or, depending on their CMS licensing agreement, might not be allowed to install 3rd party plugins. It might still be a cool little system to build though. I might try pitching it as a new (volunteer) project to my local library and see what they say.