Posts tonen met het label KEEP. Alle posts tonen
Posts tonen met het label KEEP. Alle posts tonen

donderdag 27 oktober 2011

Emulation is becoming a viable option (#KEEP) (1)

aa_DSC8958Just about everybody in our community has heard of emulation as an alternative preservation strategy to migration. But emulation is mostly talked about -- and in terms that are not very encouraging: emulation is rumoured to be very difficult to do, to require lots of expert knowledge and to be really expensive. On 26-27 October the road show of the European KEEP project came to the KB in The Hague and some 45 attendees were given the opportunity to learn more about emulation and test the tools developed by KEEP.

The resulting workshop (led by Jeffrey van der Hoeven, KB, at right) was very much worthwhile and enjoyable, with almost the entire KEEP project team sharing its knowledge. For all those interested in the deep technical details, I refer you to the KEEP website where all the slides will appear soon. For those of you who would like a broader overview, here are my experiences from the last few days (with a selection of slides from the presenters; thanks, KEEP team, for allowing me to use those).

aa_DSC9040

The audience included representatives from libraries, archives, a technical university, two The Hague-based criminal courts, a criminal information service, a film museum and a museum for media art.

What emulation is

In my general introduction to the workshop (what is the problem, etc.), I gave a definition for dummies that was not contested by the experts in the room, so I dare repeat it here. Our problem is that digital objects really only work on the hardware/software combination on which they were made. But these platforms change quickly. Migration is a strategy whereby you change the digital object to make it run on a newer platform. In the long term this is risky, because migrations are never 100%. There are always little changes. Until one day the object no longer is what it is supposed to be. Plus: it only works for a limited number of relatively simple file formats (text, images).

An alternative is emulation. You leave the digital object as it is, but you build software to make the new hardware/software combination pretend it is the old combination.

keep1

One can imagine this requires a lot of technical expertise about the old platform and the new platform and this for every possible file format around, of which there are thousands, plus all the dependencies within more complex objects such as websites.

keep2

Hence, it does not seem very practical. But when it works, you get a more authentic look and feel than with migration. Two participants in the project come from the computer game industry (Computer Spielemuseum and the European Games Developer Federation, EGDF), where look and feel is everything. Quite a few single emulator programmes have been developed already and new ones are developed all the time. But these are just pieces of the puzzle.

Emulation according to KEEP in four basic steps

Bram Lohman of Tessella summed up emulation according to KEEP in four basic steps, and I will let his slides speak for themselves:

keep6

keep7

EF_slide3

EF_slide4

 

The KEEP approach

The KEEP project wants to make emulation more practical by building a number of black boxes that take care of the most technical aspects of emulation; in this slide they are the green boxes.

keep3 

  • The Transfer Tools Framework is your assistant during the ingest phase. It helps you get content from different media (floppy disk, cd-rom, cassette, etc.) and store it into your digital archive.
  • At the access stage, there is the Emulation Framework, that analyses the digital object, finds the proper emulator software and delivers everything you need to run the object in a new computer environment.
  • The last building block is the KEEP Virtual Machine. This is the most daring goal of the project, and you can see in the slide that it is only pencilled in for now. Emulators themselves are pieces of software which become obsolete as hardware platforms change. The KEEP Virtual Machine is a piece of software that  is so basic and universal that it will ‘port’ into many hardware platforms and thus make emulator software much less prone to technology changes. This is the ‘portability’ part of the KEEP acronym.

A special component of the Emulation Framework is TOTEM, which helps users find technical information about the digital object to be emulated in various available databases such as PRONOM (see earlier post):

keep4

What emerged from the workshop

The attendees at the workshop were impressed by the work of the KEEP project. Jacob Taekema of the Amsterdam Municipal Archives (previously Rotterdam) concluded at the end of the two-day event that he could now see emulation developing into a really viable option. Aminata Kpewa and her colleagues of the Special Court of Sierra Leone were really happy to discover a network of people and a tool framework that could finally help them sort out the mess of obsolete databases in their archives.

The important accomplishment of the KEEP approach is that it takes care of a lot of the most technical, expert work (finding the best emulator, configuring the original environment), thus making emulation more accessible for less technically expert staff. The good news is also that the framework can be included into any existing preservation solution – Safety Deposit Box producer Tessella is one of the partners in the project. In addition, all of the work of KEEP is available in open source.

aa_DSC9252

Representatives of the KEEP team discussing archival problems with representatives of the Special Court for Sierra Leone – and making plans for on-site help.

But the KEEP team itself readily admits that much, much work still needs to be done:

  • keep5The framework now works for a limited number of platforms and file formats (slide at right), and, obviously, many more should be added to really make the framework practicable. As yet the framework cannot yet handle complex objects, although the emulation strategy is considered the most promising for those. It is a matter of finding the resources to put in lots of more R&D work.
  • At the ingest point (the tool transfer framework), the approach still depends on the availability of all sorts of old hardware to read obsolescent media carriers (floppy disks, tapes, etc.). Such devices are being collected by private individuals and sometimes by computer museums, but it was suggested that perhaps we need a more structured approach to safeguarding these essential machines and the knowledge about how to use them (nationally, perhaps, such as within the Dutch Digital Preservation Coalition?)
  • Whoever wants to work with an emulated object will have to know how that programme worked, what the commands were, etc. Thus we need to collect and keep as many manuals and specifications as possible. KEEP is building a knowledge base.
  • The KEEP project itself will end in February 2012. But much work still needs to be done. The KEEP team are doing everything they can to transfer the project to an organization such as the Open Planets Foundation (OPF), which can continue to develop the approach. Let us hope that this transfer is successful and more resources will become available to develop emulation as a strategy, e.g. from the European Community.

Digital preservation stumbling block: copyright law

A major stumbling block for KEEP project, for emulation, and, indeed, for all of digital preservation, is copyright legislation. David Anderson of the University of Portsmouth took upon himself the ungrateful task of finding out about possible legal constraints, and, unfortunately, he found (too) many. In fact, the deliverables of the KEEP project itself will be handed over to the European Commission in loose components because of copyright restrictions. Which is, when you come to think of it, pretty ridiculous. I will write a separate blog post about this important subject and David’s work soon.

More KEEP workshops planned

If this post has wetted your appetite for emulation, you are most welcome to attend one of the forthcoming KEEP national workshops: 10 November Zagreb, 29 November Rome, 24 January Cardiff. Details on the website.

aa_DSC9026

Alexander Fernandez on behalf of the European Games Developer Federation EGDF: ‘Involve game developers in preserving their work and building the emulation knowledge base.’

(For those who question the need to preserve games: they are part of our cultural heritage and they play a growing role in education. Plus: there is a keen and creative community out there developing those games, and they may well help projects such as KEEP to develop means to preserve other complex objects.)

PS: Not to complicate matters too much, and also because it was not mentioned during the workshop, I did not speak, in this blog post, of a third preservation strategy emerging from the CASPAR project, the ‘representation information network’; everything about that in an earlier post.

zaterdag 15 oktober 2011

Is emulation something for you (2)

If you tried to register for the The Hague Keep workshop (26-27 October, see last post) but were told the workshop was sold out, you may want to try again. Twenty more seats have been made available.

zaterdag 8 oktober 2011

Is emulation something for you?

KEEP-Keeping-Emulation-Environments-PortableIn their efforts to come up with catchy acronyms, project managers sometimes think of  wonderfully sounding names that, however, tell you too little about what is really going on. The European KEEP project is a case in point to me: KEEP stands for ‘Keeping Emulation Environments Portable’. Perhaps it is just my slow brain and/or the often fuzzy official project language, but for some reason I kept getting visions of shopping bags and briefcases …

jeffrey2On the occasion of the KEEP road show, which is coming to The Hague on 26-27 October (and to Zagreb, 9-11 November, Rome: 29-30 November), I asked KB colleague and KEEP participant Jeffrey van der Hoeven (at left, emulating KEEP user satisfaction) to explain it to me. Here is my version of what he told me:

The most well-known method to deal with software and hardware obsolescence is migration: you change the bits and the bytes of a digital object to make them work on a new platform. However, migration turns out to be not at all as risk-free as we would hope. Plus: it does not work for complex objects such as video games, websites, etc.. An alternative is emulation: you do not change the bits, but write software to make a new computer function as if it were an (old) computer. This means writing emulators for every possible combination (which is a lot of expensive R&D work), but if it works, there are fewer risks involved than with migration.

However, working with emulators is not for dummies. It is technically challenging work for specialists. The KEEP project developed an ‘emulation framework’ that takes care of that. It automatically selects the right emulator and configures the software required to render the object. That sounds quite handy.

Now, what about the ‘portability’? Emulators themselves are pieces of software that become obsolete over time. Therefore, KEEP is developing a KEEP ‘virtual machine’ – that will allow for execution of any software on any platform at any time.

Does this sound too good to be true? Come to The Hague (or Zagreb or Rome) and find out for yourself. Be sure to bring some old obsolete floppies with you to test the systems hands-on.

woensdag 7 oktober 2009

IIPC (2): technische strategieën webarchivering

'Making more informed "guesses" about what works, David Pearson, National Library of Australia. Zo'n titel vermoedt een echt pragmatische aanpak, en bij de Australiërs ben je dan meestal in goede handen. In Australië wordt het hele .au domein vier keer per jaar geharvest in het Pandora webarchief. Van de 2.3 miljard files die daaruit zijn voortgekomen, is een klein deel nu al niet meer toegankelijk, omdat de file formats al weer verdwenen zijn. Wat kun je daaraan doen? Een beroep doen op file format registers (Pronom, UDFR, etc.)? Een beDSC_0514roep doen op Wikipedia? Documenteren wat de webarchieven hebben gebruikt/nu gebruiken? Daar komen hele lijsten met gebruikte software uit. Door die te vergelijken kun je beter inschatten wat er gebruikt zou kunnen zijn. Pearson vraagt leden van de IIPC of ze mee willen helpen om zulke lijsten te maken. Het blijft wel een beetje stil in de zaal ....

'Here be dragons', strategies for dealing with virusees in the web archive, Matt Holden, Institut National de l'Audiovisuel). Holden wil de virussen niet helemaal uit het webarchief houden, want ze zijn een stuk historie, maar je wilt natuurlijk niet dat ze het hele archief infecteren. Hij acht het risico bij het oogsten van websites klein, want dan wordt er van alles gecheckt. Bij het opvragen is het risico veel groter. Dan moet je niet alleen het archief beschermen, maar ook de PC van de gebruiker. Beschikbare tools zijn ClamAV, Dazuko en HAVP. De strategie van INA bestaat uit: regelmatige viruschecks in het archief en regelmatige checks van het dataverkeer tussen het archief en de gebruiker. - Bij tests bleek het archief 2458 virussen te bevatten (28 unieke), 1 virus per 50,000 files. Exploit & Iframe zijn de meest voorkomende virustypes. Als de lezer weet wat dit betekent, weet hij meer dan ik ;-). De conclusie is dat de virussen een relatief laag risico zijn voor het webarchief. Maar ja, eentje kan te veel zijn ....

Duurzaamheidsstrategieën: emulatie of migratie?

DSC_0528 'I say emulate; he says migrate', David Pearson, National Library of Australia (rechts) en Jeffrey van der Hoeven van de KB namens het KEEP project. Hoe gaan we duurzaamheid waarborgen? Dat is een tak van sport die nog in de kinderschoenen staat. Want er zit van alles in websites, tekst, databases, beelden, video, etc. etc. Wat je gaat bewaren en welke eigenschappen je belangrijk vindt, hangt af van de doelstelling van de de bewarende organisatie.

Mogelijke duurzaamheidsstrategieën zijn migratie (omzetten van bestanden naar steeds nieuwe software) en emulatie (een nieuwe computer door middel van software laten functioneren als een oude computer). Je kunt natuurlijk ook proberen de oude computers te bewaren (computermuseum), maar dat spoor zal snel doodlopen als die computers niet meer onderhouden kunnen worden. En wie weet 50 jaar later nog hoe die computers werkten?

De National Library of Australië deed een serie tests met zowel emulatie (Dioscuri) als migratie. Bij emulatie kreeg men vooral problemen met: a) allerhande licenties op software; b) de vele onderlinge afhankelijkheden tussen de gebruikte programma's. Maar aan het eind kwamen de meeste objecten er goed genoeg uit. Migratie vereiste zeer snelle dataverbindingen, en de beschikbare tools zijn niet perfect en nogal langzaam. En het is moeilijk om goede beslissingen te nemen als je niet weet wat het exacte doel van de beschikbaarstelling is. Al met al concludeerde Australië dat de belangrijkste vraag nog niet is beantwoord: wat willen we precies bewaren? Waavoor bewaren we precies? Er zijn verder te weinig tools, en de tools die er zijn, moeten nog verder ontwikkeld worden. Vooral bij grote hoeveelheden data werken ze slecht.

Jeffrey van der Hoeven van KB presenteert het KEEP project: Keeping Emulation Environments Portable. Jeffrey laat zien hoe snel het gaat met de veranderingen in de software die we gebruiken. De laatste browser is Google Chrome 2009, dat op de markt wordt gebracht onder het motto 'not your mother's JavaScript'. Complex, dus. Ook de functionaliteit van websites is in vijftien jaar tijd enorm vooruitgegaan. Om de websites te gebruiken hebben we steeds meer software nodig (plug-ins, fonts, video). En waar websites nog wel compatibel kunnen zijn, zijn de browsers dat vaak niet.

DSC_0522 Van der Hoeven zegt direct: emulatie is niet DE oplossing, maar voor complexe websites zou het weleens de enige oplossing kunnen zijn. De KB en het NA hebben er veel onderzoek naar gedaan en o.a. Dioscuri ontwikkeld. Maar, geeft Jeffrey toe, we zijn er nog niet. Een emulator is een complex systeem dat alleen door 'techies' kan worden gebruikt. Ook heb je de oude software nodig (licenties!). En wie weet nog precies hoe die oude programma's werkten?

KEEP is een Europees project dat erop is gericht het makkelijker te maken data over te zetten van oude dragers op nieuwe; duurzaamheid te bevorderen; en de emulatie onafhankelijk te maken van een sDSC_0519pecifiek computerplatform. Het project loopt van 2009 tot 2012. Jeffrey vraagt het publiek om mee te helpen ontwikkelen aan een goed emulatieplatform. Daar kan ik weinig aan bijdragen. Maar ik heb wel een advies voor komende projecten: het is aardig als een acronyiem lekker klinkt (KEEP), maar als het vervolgens volstrekt onduidelijk wordt waar het om gaat, dan ben je je doel toch wel een beetje voorbijgeschoten.

DSC_0531 David Rosenthal van LOCKSS vindt KEEP een interessant project, maar hij denkt dat het makkelijker kan. Als je de meest gebruikte browsers inbouwt in de pijplijn tussen het archief en de gebruiker, dan zou je al veel oplossen. LOCKSS kiest voor het bewaren van de bitstream; eventuele migratie geschiedt op het moment van opvragen, 'on the fly'. Ook denkt David dat het wel zal meevallen met het in onbruik raken van file formats. Zijns inziens zal dat veel langzamer gaan dan soms gesuggereerd. Hier schiet mijn technische kennis tekort ...

Iemand uit het publiek vraagt waar Australië nu voor zou kiezen, migratie of emulatie. David's antwoord: 'personally I think migration ... or emulation.' Men is er nog niet uit. Anderen vragen hoe lang het zal duren voordat we emulatie of migratie echt moeten gaan inzetten. Jeffrey geeft aan dat er nu al content verloren gaat. Maar misschien kunnen we dat ook accepteren, voegt David toe.

Ten slotte vragen Jeffrey van der Hoeven en Hilde van Wijngaarden van de KB andere organisaties om mee te helpen ontwikkelen aan emulatietechnieken.