I don’t usually post just pointers to other blogs, but I’m making an exception here. In the interesting new “Federated Search Blog” (Which I think is from someone who works for a vendor looking to get into the library federated search market?), is a great post that explains what goes into the quality of a federated search product’s search, and what might make one work better than another—in a really accessible and understandable way to the non-tech-geek. This is a topic I’ve had to try to explain to non-technologists before, and one which it’s really good for non-technologist library workers who are using and training users in this technology every day to understand. From now on, I’ll point them to this essay.
- jrochkind on Rails5 (and earlier?) ActiveRecord::Enum supports strings in db
- Mike Owens on Rails5 (and earlier?) ActiveRecord::Enum supports strings in db
- Reinier de Lange on Non-digested asset names in Rails 4: Your Options
- Jerome on Non-digested asset names in Rails 4: Your Options
- Ross on Catching HTTP OPTIONS /* request in a Rails app
- Elliot Oh on A Proquest platform API