So far for the theory, but as we’ll see below, things got slightly more complicated and messy along the way! Iromlab to IpmlabĪs a first step I forked the existing Iromlab code. It also implied that Windows (10) would be the target platform. This would allow us to re-use most of the software components of the existing optical media workflow with only minor modifications. Since we already have a workflow in place for optical media, it seemed to make sense to use Iromlab (which uses IsoBuster as the main imaging application) as a starting point. In this post I’ll explain how this tool came about, and highlight some of the challenges I encountered during its development. Using the existing Iromlab-based workflow as a starting point, I created a preliminary workflow tool that can be used for imaging our 3.5” floppies (and various other types portable media). Out of these, 3.5 inch floppy disks are the most common data carriers (after optical media), so it made sense to focus on these as a next step. This project is expected to reach its completion later this year, but as demonstrated by this earlier inventory, our deposit collection also contains various other types of legacy media that are under threat of becoming inaccessible. The KB has been using Iromlab since 2019 as part of an ongoing effort to preserve the information contained in its vast collection of legacy optical media.
In 2017 I wrote a blog post on Iromlab (an acronym for “Image and Rip Optical Media Like A Boss”), a custom-built software tool that streamlines imaging and ripping of optical media using an Acronova Nimbie disc robot.
0 kommentar(er)
