Galleria.io is great because it is Free/Libre Software (MIT-licensed), simply does what it is supposed to do, and requires not yet another plugin for WordPress nor a database backend. It also supports mobile devices and its typical touch gestures. Furthermore it enables self-hosted galleries and does not require to rely on any cloud services where you might loose control on your data.
The only thing that I was missing was a straight forward way to automatically generate a gallery. Creating it by hand – as for example described in Galleria.io’s “Beginners Guide” – is time-consuming, cumbersome, and error-prone. So the overall idea was to create a ready-to-run Galleria.io gallery based on a given folder that contains just the image files by using a shell script.
In detail I wanted to have the following functionality:
A gallery based on Galleria.io should be generated out of a given source folder that contains the image files as JPEGs. The folder corresponds to one gallery (collection of image files).
Multiple folders should be supported so to be able to generate multiple galleries at once.
Required thumbnails with naturally much lower resolution should be automatically generated based on the original image files.
Title and description of gallery should be customisable. The intended text should be provided during gallery creation.
In case an image has a title and caption given within the JPEG file it should be extracted. As I use Adobe Lightroom the title and caption are provided within the XMP tags “Xmp.dc.title” and “Xmp.dc.description”.
Images, thumbnails and provided metadata should be automatically integrated within the gallery definition file.
Actual files (images, thumbnails and gallery definition file) should be added to the resulting destination folder that could then be easily uploaded to the hosting web server.
As solution I have created a shell (Bash) script that could be run on any GNU/Linux-like environment. For thumbnail creation ImageMagick was used, for extraction of EXIF/XMP metadata Exiv2 was used. The script works also on a Macintosh as it actually was developed and tested on it. Required tools are available via MacPorts.
You are welcome to download, use, and modify it from here:
Prerequisites (as stated):Bash, ImageMagick, Exiv2 and ideally some knowledge in scripting, HTML and Galleria.io to adjust it to your needs.
Please note: You need to place the Galleria.io core files somewhere on your server and set the (relative) links to these files correctly within the provided script. In other words the script just works fine with my settings and needs to be adjusted to your setup. Error handling is currently very basic and addresses only some common mistakes.
Move any customisations like imports and the links to the Galleria.io core files into a separate config file or alternatively to a configuration part within the script.
Offer a persistent storage of already processed galleries in order to remember at least the already provided title and description per gallery. Use case: It might happen that you need to recreate a gallery as you forgot to include or remove certain images.
Improved error handling and overall guidance to also support non-expert users.
The article about my previous research has finally been published in the IMIA Yearbook 2013. It is meant to provide a practitioner’s perspective on the use of medical free/libre and open source software (FLOSS) in clinical routine. In this context I examined and presented the opinions and experiences of chief information officers (CIO) working at larger hospitals. The abstract reads like this:
Objectives: To assess and analyze the attitude of health IT executives towards the utilization of specialized medical Open Source software (OSS) in Germany’s and other European countries’ health care delivery.
Methods: After an initial literature review a field study was carried out based on semi-structured expert interviews. Eight German and 11 other European health IT executives were surveyed. The results were qualitatively analyzed using the grounded theory approach. Identified concepts were reviewed using SWOT analysis.
Results: In total, 13 strengths, 11 weaknesses, 3 opportunities, and 8 threats of the utilization of OSS in a clinical setting could be identified. Additionally, closely related aspects like general software procurement criteria, the overall attitude of health IT executives, users, and management towards OSS and its current and future use could as well be assessed.
Conclusions: Medical OSS is rarely used in health care delivery. In order to capitalize the unique advantages of OSS in a clinical setting, complex requirements need to be addressed. Short-comings of OSS describe an attractive breeding ground for new commercial offerings and services that need yet to be seen.
Schmuhl, H., Heinze, O., & Bergh, B. (2013). Use of Open Source Software in Health Care Delivery – Results of a Qualitative Field Study. Contribution of the EFMI LIFOSS Working Group. Yearbook of medical informatics, 8(1), 107–13.
As you might know Medfloss.org (formerly medfoss.apfelkraut.org) tries to provide a comprehensive and structured overview of Free/Libre and Open Source Software (FLOSS) projects for the health care domain.
After the initial launch 6 months ago it recently welcomed the 200th project in its repository: the GPL-licensed iDART software – iDART is the abbreviation of “Intelligent Dispensing of Antiretroviral Treatment” and according to its authors addresses many of the challenges faced by public ART dispensing pharmacies in developing countries.
Starting with originally just 120 projects, the medfloss.org database currently holds:
My cordial thanks goes to all the contributors that already made and hopefully will continue to make use of the open content concept by revising/extending existing information or adding new content!
For more information about the site and its objectives please refer to the mission statement or these slides. Beside amendments to the actual content I also highly appreciate any general feedback about the site, offered functionality and shortcomings of it.
Are you a practice, clinic or any other health care institution that is using medical open source software in daily routine? And wasn’t it quite hard for you to find the right software, to get it up and running and to finally customize it to your needs without having any experienced users or reference sites at hand?
Even a high number of downloads or a strong ‘activity percentile’ of an open source software project doesn’t tell you anything about the suitability for your purposes and in general about the stability and efficiency that are required for successful clinical practice.
But what if you could see on a per-project basis at which site it is already deployed and even whom you could contact and ask for advice and personal experiences?
Medfloss.org (formerly medfoss.apfelkraut.org) should provide a comprehensive and structured overview of Free/Libre and Open Source Software (FLOSS) projects for the health care domain. Moreover it should offer a platform to foster the exchange of ideas, knowledge and experiences about these projects.
For details about the offered features and services please refer to the Mission Statement.