I promised to jot down a few notes on how we publish images in our Project Blacklight based catalog with IIIF. The International Image Interoperability Framework is a set of API’s that enable flexible publishing, sharing and (re)use of images over the Web. It’s specifically tailored towards the digital cultural heritage domain. In this post, I’ll outline how you can easily integrate IIIF support in your own projects.
So, December has kicked off. It’s a nice opportunity to do a reboot as we approach the end of the year. I’m active in the field of GLAM institutions. Galleries, libraries, archives and Museums. As a digital specialist, I’m involved in the ongoing digitisation or automatisation of processes within these organisations. Coming from the private sector, I apply my experience of realising digital projects of various scale and size for a wide variety of clients, on a daily basis on an operational level. Doing a blog series about the experience of these past few years has been on a my wish list for a while now.
Publishing structured data on the Web is a hot topic these days. XML and JSON are go-to formats for HTTP endpoints, because they can be easily consumed by machines. However, these formats are less wieldable for humans though. So, how can we extract data from an XML or JSON document without heavy duty coding?
Breadcrumbs are one of those components on a website that don’t always get the attention they deserve. If done right, they can become a valuable asset. But if thrown in as an afterthought, they can turn into another nail of a projects’ coffin.
Is it easy to expose data stored in Drupal and use it in a web application? Of course it is! But how do you make Drupal and AngularJS play nice together? I decided to record an introductory screencast that answers this question.
I’ve been joining the AngularJS bandwagon lately. Why? Because modern browsers and devices can do so much more besides merely rendering static HTML. And client side frameworks are excellent companions for processig raw server side API output. Here’s what I’ve come to learn.
A few weeks ago, I ran into an issue with the Entity Reference module and the Internationalization suite. A client with a project featuring content in multiple languages, wanted the autocomplete widget only to show suggestions in the active language. On the surface, this didn’t look like an exceptional request, but the process to devise a good solution became quite interesting.