 Okay. Thank you for the technicality help. I'm about to share about our project here in Indonesia. We have a pilot project called Wikisource Loves Manuscript that handle some works on Manuscript, including digitization and working on Wikisource. And it's not quite a simple presentation because we have our equipment for digitization in the field. So I will make it on two sessions. One is a short session for the introduction for the program itself and one other is for the practical technique to digitize the manuscript. We brought also the manuscript from Indonesia. Okay. This is the condition of the manuscript we found in the field in many regions in Indonesia, mostly abandoned by the owner or other private collection, not institutional collection. We are not talking about the governmental institution, but this is only we focus on private collection or private institution like museums or self-owned library. And this is a pilot project from Wikimedia Foundation involving our institution in Jakarta, PPIM, and we have a media partner. It's one of the major media in Indonesia, which is Tempo. And we do the digitization in three regions, which is three different islands in Indonesia. One is Bali, two Java, and the three is Sumatra. So it's quite far away from Jakarta, especially the Sumatra in Bali. So it's challenging when we do the field missions. The program itself has two main activities. First is digitization of the manuscript, taking pictures, uploading to the media comments, and then inputting metadata to Wikidata and transcribing the manuscript. Getting the information about the manuscript. Then we have another activity, which is community engagement. We do workshop of Wikisource to the newbies, and then we will have a competition on transcribing the manuscript. And also we have a cover by some local news. This is the big workflow for the project. You can imagine that images from the manuscript can be uploaded to Wikimedia Commons. Then the information about the manuscript itself, the codicological aspect, the size of the script, or the text information, like what the story is inside, who is the author, and etc. Then we also retrieve the data from Wikimedia Commons. Wikisource and we do the transcription for the manuscript with the same script that we got from the field. And then this almost end until this September. We are still working to gathering a whole of the information and a whole of the picture from the regions. So in September, we are going to publish the full report of the progress. So this is the situation of the manuscript digitization. So this is from the fields. We have Balinese manuscript, palm leaf manuscripts. This is musical notation manuscript from Yogyakarta, from Java. There's an ancient Japanese course who can make this unique manuscript. Then this is another region. This is the workshop for the newbies for the Wikisource that involve the manuscript to be transcribed by the participants. This is the situation from the workshop activity in three regions. As you can see, there is a picture of manuscript that transcribed into Arabic script but in Malay language in Sumatra. And the proofreader tone is about to start by the end of this month. This is the sample of the metadata that we input into the Wikidata. This is the transcribed manuscript, Balinese manuscript, palm leaf. This is the Arabic Malay and Minakabao manuscript. As far as we have done, the digitization has resulting... It's quite significant result. We have almost 20,000 pages of the manuscript being digitized. In short time, we will upload it to the Wikimedia Commons. We have also cooperation with the British Library. We have re-applauded the 76 Japanese manuscript from the collection of the British Library to Wikimedia Commons to be able to work on the Wikisource. Thank you so much for... This is the end of this presentation, I think. So we do practice and you can... Sure? Okay. Thank you. Just two questions. In what Wikisources were these transcriptions uploaded? In how many Wikisources? We used three Wikisources. The Balinese using the Balinese Wikisource, and the Multilingual Wikisource for the Multilingual manuscript and languages. So for Multilingual manuscripts, you used the Multilingual Wikisource? Yes. And the second question, which is quite interesting. When you used the competition for the transcription, how steep was the learning curve? Because when I think of transcribing manuscripts, I think about something quite difficult, because manuscript texts are often difficult to understand with abbreviations or string styles or instant languages and so on. How did you manage to get many people to transcribe this? Okay. The first, we approached to have the workshop before. Yes. To make more candidates to be able to be a participant on the competition. And also we invite the community of the Indonesian Wikisource. So there are several communities in Indonesia that focus on Wikisource, like the Indonesian Wikisource, the Balinese Wikisource community, and also the Balinese Wikisource community. So we invite them and invite them to join this competition, as well as the newbies from maybe students from the universities. There are several guidance from the communities from Indonesia that can be used as help for the newbies, like tutorials, something like that. We have also in our community. Yes, we involve many communities here. I think we need more people to collaborate with this project. Okay. Please. So I'm Nicolas Vigneron from the Wikisource community as a group. Okay. Thank you. I'm not sure if you know it or not, but the place of Wikidata and relationship with Wikisource has always been a question. And I see that you put Wikidata after comments. Some people prefer to do the other way around, starting with Wikidata. Why, how, if you have an idea about, be interested. Okay. That's always challenging, which will be first you put the data, first to Wikidata or the comment. I think I put the image first, then make an item in Wikidata and then connect it. Yeah, just, but it's not handy, not really handy, but it works as long as the data still have connection. Yeah, we can put all together. And yeah, the question also maybe how to represent the Wikidata items to more convenient way for the user. Yesterday I met a friend from Uruguay Jorge. He offered a new project that can represent the Wikidata items simpler than the appearance on Wikidata itself. So it could be another option to develop another landing page to search the manuscript or to query the result of the Wikidata. So yeah, we need to collaborate more, I think. So any question? Okay. I think we can share the digitization process. I have my friend here, Alan, who is ready with the rig. I don't know how to, if you can share the screen. I'm using Zoom to connect that laptop to the screen. So we choose to use the camera with a high resolution ability to get a high resolution image. So there are always options whether you use scanner, cell phone, mobile phone or camera to use. It's optional, not as should. But for our standard, we use the camera. We use camera to take the picture with the exact color from the manuscript. We use the QP card or the color checker to check the RGB standard of the image. So we do not prefer using the black and white or grayscale image type. We use the full color with the standard. And then we manage to make coding for the manuscript item and also etc. Many things happen at the back end of the process. This is a technical thing. While we're waiting, what is happening on the laptop? There is a sample of the Japanese manuscript with Japanese script and Japanese language from 19th century made of 3-bar paper. We use the application from the camera itself, the Canon EOS utility. And we need to measure the frame. This is the artistic part. You not only take the picture as what it is, but we have to make it more beautiful to appear. That is the color checker. As you can see, there's a white and gray, white, black tag at the side. We can check that the color is matched to the RGB standard, red, green, blue standard. So the manuscript color will match digitally with the physical manuscript. Are we ready? We have another setting standard for the other specifications like ISO setting and also the calfin setting. The image result itself produces two types of images. The one is JPG or DPEG. The other one is RAW or uncompressed file. We can put some music. That's also challenging when we do it in the field. Sometimes we have to do it outside or inside the room. That's why we choose using the strong flash to make it consistent. It doesn't matter if you do that outside of the room or inside of the room. The flash light can handle the standard. We have to make some adjustments in the first time to match the standard. What is called calibration. We need calibration. Sometimes one hour calibration to match the standard. Because we have the measurement of the lightness, the RGB and so on. That's challenging. One day we have to readjust or synchronize again after four or five manuscripts. That's another thing. Challenging but we have experience to do that. We can do that. This is the result of the manuscript. We put some different folders for the identity. The recto is the front and the verso is the backside of the page. We also tend to have one page in one shot. Sometimes the manuscript size is small. We can do one shot, two pages. For the palm leaf manuscript, we use one shot, two pages. That's different alignment and different layout of the text. We have to make some adjustments. The challenge in the field also, if we have a big manuscript. This copy stand for the camera is not really good for a big manuscript. Therefore we use a tripod to handle the bigger manuscripts. Hi. Sorry to interrupt. There's a question from the chat box which is from Lucy. How do you introduce coding to the manuscript? Coding. Do you mean coding for the naming or coding for the programming? That's a different thing. I'm not very sure just reading out the question as it was stated as well. This was a question at around about five minutes ago. I'm guessing it's encoding. Okay. Maybe I can answer both of coding or encoding. The naming and coding, we use several, what is called the term minor. The first, can we have the folder name? That one. We have a folder. The name is WM ID 0001 and 001. The first two letters reflect the WM Wikimedia project. And ID is for the ISO code for country Indonesia. And also 00, the first four digits reflect the number of the owner. And the last three digits reflect the number of the manuscript. So we can trace where country, which owner or which collection and manuscript number what. So because this is a pilot project, we hope our guidelines, we have also arranged a guideline for digitization with this style. We hope this kind of encoding or naming for the file can be used abroad based on country code and collection and the manuscript number itself. And in the metadata, we have also this code. But for the title to be used in Wikimedia Commons or Wikisource, we use the title from the text. For example, Ramayana Story, we use the title Ramayana for the Balinese text, for example. So not only the code we put on the title. So let's hopefully answer the question. We will check with her right now. Okay. Yeah, and we'll get back to you. Okay, thank you so much. Okay, is there any comment for this program? Yeah, one that I, one thing that I noticed from the project, especially from the friends or communities in the regions was difficulties on communication with the owner of the collection. How we can approach the owner to be to believe that their collection is can be usable for many people and can be opened freely access the access, I mean, and we have to make sure that the owner one to be part of the open access activity. Some of the owner reject to collaborate because the collection is like sacred to them. Not every single day can be opened, can be read, can be touch. They, yeah, most of the manuscript still like a cultural taboo. Yeah, so, yeah, that's part of the culture and we have to respect that. We don't force the owner to be part of the project, but yeah, we have to communicate with them in a kind manner, following their culture, following their habit. If there were a ritual, we joined the ritual, like in Bali Balinese, very strong in the traditional and cultural ritual. So we also joined the ritual to get blessed from the ancestor. So that's very interesting. This is not only about the technicality on digitization and technicality on how to put it on the internet, but how to approach the owner. Yeah, of course, license is another thing to discuss whether this manuscript should be open, what is it called? Open domain? What domain? Public domain? Yes. The license should be public domain or something else. That's also always be a question. The ownership of the photograph, the image is this owned by the photographer or the project itself and the text. The text is the text owned by the author or the owner of the manuscript. It's always challenging. Then we put all of the description of the ownership, the authorship, the other things. So everybody can get the credits, the owner, the author, the project, the photographer itself. So yeah, that's maybe not the best practice for the licensing, but at least we can appreciate everyone who involved in the project. So I was several times asking to the Creative Commons community in Indonesia which license should be fit to the manuscript, should be public domain or something else. Yes, please. Did you get from your sponsors any condition about copyright? No, particularly not, maybe Masakti can comment something about the license from a sponsor from the Wikimedia Foundation. Is there any demand for the licensing? I think the question is more related than the licensing from the owners of the manuscripts. But with regards to the licensing itself, all the collections that we have for Wilma is already provided by the owners of the manuscripts during the field missions. And apart from that, there is an in-kind donation of already digitized manuscripts from British Library which we already resolved about the licensing issue. I hope that answered your question. Yes, you clearly answered my question. Just to talk to the audience. You know there is nothing like a free coffee or a free beer. So I thought about institutions giving sponsorships or giving funds to Wikimedia related initiatives or projects. Sometimes they are quite loath about the free licenses. And so as long as we talk with libraries or state institutions, we do not have real problems. But when we talk with private institutions or banks or other firms, they want to know if they have any income, any gain from these projects. This is a very interesting question and thank you so much Eduardo. Well, maybe for your context, the funding for the Wikimedia project actually coming from the Wikimedia foundations. At that time, we have initiatives fund and I totally agree with you. Sometimes when we are engaging with private institutions, it might be quite challenging. It might be quite challenging. It's literally everywhere. But according to my experience, it's based on the mutual understanding and whether there is a line that we need to cross or not. In this case, we would prefer to collaborate with institutions that has good attention for heritage preservation. So it's like an option, whether we are moving forward from sponsorship from private enterprises or we can collaborate with maybe government related institutions or other nonprofit foundation that have the same mission alignment with us. So yeah, that's my opinion. Thank you so much. Okay, thank you so much for the additional information about this. And maybe I have another comment about the consent to the owner. We have a constant shit that signed by the owner that the owner willing to collaborate with this program and to upload to be to upload the collection into internet as specifically into Wikimedia platforms. Yes, my question is what kind of software you're using for the image manipulation. Is it a proprietary software or a false software? It's, yeah, it's proprietary. Yes, this is from what's called a CDC or image something like a CDC software. This for managing the folders as well as to check the color standard, the RGB standard. We don't actually manipulate the color or the image. Yeah, it is what it is from the field. So we have to manage a synchronization or calibration in the first time we set the equipment. So we don't need to manipulate the image. There's no no change on the color, for example, or format. At the end we have to convert the images into one PDF file to be uploaded to the Wikimedia Commons, but not changing the size of the image, size of the, you know, widen width and height, and also the resolution. It's converting to PDF also challenging. Sometimes the PDF software engine, yeah, did something weird that the output of the PDF format is not matched to the original image. For example, or the resolution is decreased. But we always we can always find solution for that. Mostly for converting we use the open source program from I'm using Linux actually. So there are several software can be used open source for converting PDF. Yeah, that's always option optional, whether we use open source software or proper property software. It depends on how we manage the workflow and the maybe the budget. We still have time. I'm still open if you have another thing to discuss. Yeah, maybe I can say something again about the script or the letter or this writing system. Since the writing system in Indonesia is various, not only using the Roman or Latin script Roman or Latin script is used for Bahasa Indonesia or the national language. But for the manuscript, most of them not using Latin or Roman script, but using the traditional scripts like Balinese, Japanese. The question is how the user can use to type can use the indigenous scripts to type on the wiki source. Fortunately, several of the manuscript has been accepted by international organization like ISO or a unique code. So we can use the script, the indigenous script by the international standard that used by the wiki media wiki platform, for example. That's very important to represent the text, the literature, like the original source. When the script of the manuscript is not available in the unique code, for example, it's another challenge to be worked in the wiki source. So everything has to be have standard on the unique code for script codification. So we can work on the digital ecology ecosystem. That's also challenging because not many people in Indonesia can type on the indigenous script. Even though the indigenous script are taught in the schools, but only for educational purpose, not for daily activity. We still can see if we go to Java, everything is written in Latin or Roman script. But maybe since past five years, the revival of the indigenous script in several regions like Bali, we can see the signs, several signs in airports or governmental office, no reuse of the indigenous script. I don't know if they can bring the indigenous script to be able to be daily used, but fortunately the digital environment like wiki source can be a good documentation platform for the indigenous script in the digital platform. That's all I think. We still have time, but I'm finished. Thank you so much for the attention. And if you have any questions, please let me know maybe after the session or on the free session. Thank you so much and bye.