 So, my name is Mustafa Don, I'm the Deputy Head of Digital Library Department here, and also leading the team where we have 15 software engineers and working with agile methods and triple IF. And most of the things I'll be presenting today are the results of their work. So, from a librarian perspective, it's hard to talk about anything digital without talking about digital transformation. Digital transformation changes libraries with or create petabytes of digital data, try to find ways to manage them, and our library services are becoming more and more IT services. Our funders ask for digital standards, digital sustainability in their calls, so our organization also changes. And over time, our customers change as well. First of all, they get younger. They want to use mobile devices, they care for user experience, and they want to see more than just the catalog. They want to see the content, the image, the full takes, and searching it and access it whenever they want. So, standards like triple IF cannot solve all these problems coming from the digital transformation, but it can help libraries to become more digital without reinventing the wheel. In the next few slides, I will talk about our experience with triple IF and our journey up to that mountain. So, a little bit history. This is how our digital library for printed books look like a few years ago. GDZ stands for Getting in Digitalization Center. I think you might be able to visit that too. It's also a department where we scan our historical books. But this is also the name of our service. And the service had performance issues because of the increase of the index objects, more than tenfold, compared with the start of the service 10 years ago. And it was, and still, one of the best visited online services of our library. It was originally designed for approximately 100,000 pages 10 years ago, but was trying to cope with 10 million pages as we decided to redesign it. Our initial goal was to renew the indexer and to provide a responsive design. But we decided to keep the architecture for the beginning. But after three months of agile development, we realized that we need a complete redesign of the architecture in order to be able to provide a scalable product. That was the point where we decided to give TripLIF a go. And we partially ditched what we had done and partially refactored what we had done and created a modular IT architecture supporting presentation image APIs of TripLIF. And developed a software bundle, a viewer with AGPL license, which you can also find on GitHub. I'll talk about that later. And after a project, we launched two years ago this new service with a new responsive design and better performance, takes to also TripLIF, giving online access to 63,000 books and manuscripts in 20 collections and 50 million pages. Presentation storage is about 40 terabytes, including permanent cache for tiles. And we also need about 200 terabytes for the raw data with an ascending trend because of ongoing digitization projects. But how did TripLIF helped us here? It helped us build a scalable product and provided a uniform access to image-based content as we also heard today from other speakers. So we didn't have to wait long for the next project. We were asked to build a similar service for different material coming from publishing houses which were licensed by the library, sponsored by the German Research Foundation. The numbers got even larger this time. Until 2021, the service is expected to provide access to one and a half million records and about one million pages. 100 million pages, sorry. And at the moment, we got about a third of it, half a million records and 28 million pages online using pretty much the same software based on TripLIF with little adjustments. I put also the links on the left-hand side if you want to visit them, you can have a look at it. And with TripLIF, we could reuse the software and invest it less in re-menting the wheel. That was the gain of TripLIF here. A similar digital library project with a service provider for scientific periodicals has also been started lately. And we plan to relaunch the DigitSciShift website in the next few weeks. And this is comparable to JSTAR. This will be giving access to 700 periodicals with eight million pages. And this is again an example of re-use of tools and less re-menting to build. We, the University of Gettengen has additional collections with 3D objects which has been scanned for the time being with 3,000, 30,000 objects. And we act as consultants for this project looking back at our experience with TripLIF. We encourage the project team to implement TripLIF here so that we can link to 3D objects with printed and written handwritten material. Here you can see one of the early examples where we use Mirador viewer. At the left-hand side, you see a coin of the Empress Elizabeth of Russia from 1742. And at the right-hand side, you see a letter of Georg Thomas von Asch Heine, the library director at that time, how he mentions these coins. So this is a good example of how we can support provenance research. And TripLIF helped us here to reuse the data and it value to existing services. The software suit I talked about earlier, during these projects we got a lot of help from the TripLIF community and we learned a lot about TripLIF and we decided to give the software we created back to the community as part of our policy which is now accessible over GitHub, as I said with AGPL. And this TripLIF bundle contains the backhand written in symphony, a PHP framework for TripLIF support. If you are using other getting products like Gobi or Ketodo, you'll also hear about them during the conference, I assume. This bundle might come quite handy to build a presentation layer up on that. And Tiffy is a lightweight TripLIF viewer which can process even long documents up to 10,000 pages. It's implemented with JavaScript. For image rendering, we use existing libraries like OpenSea Directing. And it can be used standalone in a web page or a Type-O3 extension, support for WordPress or other content management systems envisaged. It has features like panels. You can see the scan, stop nails, table of contents metadata. I mean, you know these already from other viewers. What is interesting about Tiffy is it supports responsive design. It's mobile-friendly. And in this example, you can see that at the right-hand side there is the full text of the document, also presented. And at the left-hand side, you can see the image with additional functions like image manipulation. We sometimes come across some Tiffy implementations on different websites. Here's an example from a square finally university. Unfortunately, we don't have the opportunity always to follow who's using what. But if you want to give us feedback, if you are using Tiffy or if you want to use Tiffy or if you don't want to use Tiffy after you related it, please give us a feedback. And last but not least, TripLIF helps libraries to preserve their textures better. Here you can see the digitized version of the infamous Gutenberg Bible, which is worldwide accessible and reusable over TripLIF now. Our head of special collections is very happy now that he doesn't need to take it out of the safe every time we have a VIP guest. So he's sleeping better now. So in a nutshell, TripLIF provides uniform access to image-based data and it helps building scalable services, prevents reinventing the build by software reuse, adds value to existing services by data reuse, fosters interaction with the community, facing similar challenges and contributes to preservation of cultural heritage. So Outlook, we hope to provide better support for scholarly digital editions and digital amenities since our virtual research environment takes good, also supports TripLIF. Regina will be talking about this in a couple of minutes. And we are collaborating with other libraries in a national project to digitize an index printed materials published in the 17th and 18th century in the German speaking areas. This is a huge project where we digitize millions of pages and we are planning to use TripLIF to combine content from across repositories. Text delivery is an important requirement. In this regard, we are looking forward to discussions about the new beta 3.1 APIs of Image and Presentation API, also during this conference. About T3, we have plans for a plugin approach to provide easy enhancements for project-specific requirements. Netation support is also one of the demanded features we are working on. So I think the time is up and I'm done. I'll see you in a minute.