So we'll start today's meetup and first up will be Sayani. Yep. Hi, everyone. As Mike mentioned, my name is Sayani. So you can go to this website, sayn.ee, as a top-level domain, and I'm a web developer. And today I want to talk about one of my site projects that Mike said, but it is a site project about developer community, about developers like all of you here. And the site is called data.webuild.sg. So I'm going to show you some graphs and charts collected about Singapore developer community over the course of 2020 to show you PHP data. And hopefully some of you with open source repositories names will be called out, and of course Mike as well for the organization. But let me talk a little bit about how this project got started. So about four years ago when I was kind of getting into web development, I was like, where are the meetups in Singapore? So in December 28, 2012, I did my first commit. And it was a static page. Xeon will know very well what is a static page. And all I did was to list down chronologically the developer meetups in Singapore and the open source above 50 stars in GitHub. And that was pretty possible, because you know what? Per week we would have what? Like two or three meetups per month, 10 meetups. That was in 2012, 2013. It wasn't possible anymore. So although the website design looks exactly the same, the architecture behind it has changed. So I want to explain to you what goes on. On the left-hand side is open events. And there we query Facebook API, meetup.com API, events-bright API, and ICS URLs. Every hour it runs a cron job or a scheduler. And it lists down the upcoming developer events in Singapore. As you can see right now, maybe if you refresh the page, it won't be there anymore, because we have passed 7 o'clock. PHP Meetup is there. And all the meetups here are about developer meetups in Singapore. On the right-hand side, on the other hand, we list open source repositories from GitHub that has at least 50 stars. The contributor or the owner of the repository has Singapore as part of the string of location. And also it has been updated in the last three months. So this is what it is. So this website was going on fine since 2012, 13, and 14 until one of our friend, Mike Cheng, his name is V, he was like, he's like a math dude.  Are the events preserved somewhere? The events were never preserved, and neither were the open source. Like, who cares about the past events, right? I only want to know about the future ones. So the data was always in memory, never backed up by a database. All right, so this is a site project. And then there was a lot of bike shading. And we were like, OK, how do we kind of capture the data so that we can do some math? So this is what the data.webuild is all about. And I want to explain to you, once again, the architecture. So what happens every day? There are two API endpoints, which is written in JSON, not in XML, not in like a season or whatever. So this is the repositories JSON API. It is, by the way, found in webuildsg api slash v1 slash repose. And if you go here, you'll find the entire list of repositories. Similarly, there's also the events API endpoint, which I highly encourage all of you to go and consume it in your client-side application, iOS, iWatch, Android, whatever. So what this bot does is that every day at 3 AM, it will commit two snapshots, one for the events and one for the repositories. And this was being done for the entire 2015. All of us got busy and we were like, oh, whatever, we can't be bothered. But until in December, I was like, you know what, let's do some data manipulation. And that's what we did. We created 10 graphs out of these JSON snapshots taken for 365 days last year. Are you all curious to see the data? All right, here you will see a young but a growing developer community. And it invests in more of us, or rather it should encourage more of us to come and join in into this growing story. And that's what my point is here for all of you today. So let me show you the very first one. This is repositories updated per week, per week. As you can see, this was in 29 December 2014. It was barely six repositories. You can clearly see that the number of repositories is growing until last week. You know, people were still coming back from the holidays, but who cares? Developers were still chucking away code. There were like 27 repositories, which were above 50 stars, that were updated last week. And obviously, this is a growing trend. 27 repositories is a very small number. I think all of us can get together and make it even bigger this year. And I'm so happy that I'm speaking for a January meetup because this is basically call for action for the rest of the year. All right, so let's look at the next one, which is, maybe I should also look at events per week just for this. Yeah, obviously you can see that this is very low, the holiday period. This is like the Chinese New Year. The next one I want to show you is update events per programming language. All right, so PHP, I think you have been very, very active. There has been 127 Git pushes for the entire of last year for PHP for repositories with stars more than 50. I think we should clap ourselves for contributing. Like it's one of the highest. So JavaScript is, of course, one of the highest. But then this is where we also tracked the active user groups with at least five events last year. So all of you, if you want to be looking for more developer events in Singapore, these are the groups. And because we query API, these are not stale data. This is taken from groups that had at least five events last year. So all of them are active groups. I don't think we could have imagined this number of groups like two or three years ago. Could we, Mike? Not really. And by the way, these are developer groups. I'm not even counting startups and design and all those because those will be even more if you get them together. So please find a group and get involved in other groups as well. Next is the interesting stuff. Are you all curious about PHP? So these are the repositories with at least 50 stars updated last year. And let's click this little guy called PHP. I do want to call out if the authors of the open source repository is here. Dispatch by Noodle Haas. Noody Haas. Are you here? Come on. That's you. OK. Thank you. So please go and check out. It has 340 stars. Dispatch. Go and look at the issues. Go and give some pull requests love to him. Bones for Genesis 2-0. C. Dukes. Are you here? All right, if not, go and check this out. Config by Noody Haas again. Selects off by Gigabline. I know Chris is here, right? Where is Chris? Chris is there. Chris even has Go programming language. So go and check out. Yes. Chris. That's a 2XL. One for one repository. No, I'm kidding. Thank you, Chris. All right. Next is State Machine by Winto. Are you here? And Grap to it by Kai Henry. Kai is too busy with his kid. Eno Earp, ERP, INO ERP. Are you here?  I know Lester is here. Lester. One more t-shirt for Lester. I don't need that to the phone. OK. Save the environment. Save the t-shirts. Yes. It should be so really printable. Give it to somebody who doesn't have that. And Coel by Fennan. Are you here? This project is awesome. Which project? The program. Coel is awesome. Exactly. So please, 5,000 stars. You know, because we query API once again, it even makes us discover new things. Because as a programmer, these are not static. So when I go and look, I'm like, oh my gosh, I didn't even know this programmer actually lives in Singapore, or actually rather puts Singapore as their location. So please go ahead and check out other programming languages and get inspired. And maybe as a meetup organizer, you can invite these creator of open source to talk about it. Maybe Chris Hink can talk about it. Or you can talk about it at the next. I promise not all of them published their emails. Yeah, I know, right? Maybe tag in a Git issue. Hey, you know. Because they're active on GitHub, right? This is a creating issue. Can you talk on PHP Meetup? All right, so once again, we also create maps out of the location data. So if you are a new meetup user group, please go ahead and check out this map. And a big thanks to PayPal, really. Because PayPal, it's both the locations, the old one and the new one is here. So thanks to that. And finally, data.webuild.sg, the one with the graphs, is fully open source. Everything is open source, by the way. So I highly encourage you to go there. Make some pull requests. If not, give us suggestions for the graphs we can plot. That's the inspiring thing I need. Where can I get more inspiration or rather insight about the developer community here? And finally, I wanted to point out to you these few numbers. So the one at the bottom is the numbers of 2015. And I restarted that for 2016. And let's see whether we can beat that number. I mean, we are still a young community. But to beat that number, I don't think it's the job of only Mike Cheng or the job of only the few open source repositories. It's for all of us to come in and join it. So really, I will say for sure that all the meetup organizers here are very, very open to newcomers. People out of industry, people new to PHP programming, please come and talk to Mike Cheng. Come and talk to the organizers. They will take you up with open arm, with help, and stuff like that. So please contribute. These numbers will be done by all of us. And finally, I have just three requests from all of you. So what can we do about the developer community stats here? So firstly, please raise an issue about what are the graphs we can plot. Secondly, if you know an existing programmer who is not aware of this open community here that is free and open for programming, for open source, please bring the person to a meetup. And if the person can speak, please encourage him or her to speak as well. Next one is add links to nodes. So this is something I just coded up just this afternoon. We are trying to collect a group of links to help meetup organizers to help first time contributors to open source, first time conference proposal. I would love your pull request to this repository. It's right here. Send some pull request. It's written in HTML, not a markdown, not JSON. It's plain old HTML. So I believe all of us will be able to contribute to it. So contribute to it. And let's see what the magic numbers will be for 2016. But it's all up to us and all the best to PHP. And I hope to see more meetups and more activities in PHP programming language. Thank you so much. I would love your questions. Do you have questions for Sairani? Do you have questions for her? No, yes. What is written in? All right. So different projects are written in different things. This rebuild is written in node. It's hosted in OpenShift by Red Hat. You know our site projects, we tend to find free stuff to use. I don't want to pay money. And yeah, it runs a scheduler. The data.webuild.sg is a complete static site. But it uses a jade, and then it compiles into HTML. And I just run a build task every other day. I kind of get pulled. But feel free to look at the thing. And yeah, we actually do have a podcast website as well. I need to restart it, where we also interview. It's called live.webuild.sg. We interview developers visiting or living in Singapore. So feel free to listen to all of them. The very first one is by Mike Cheng, first episode. All right, if not, please go ahead and subscribe to the calendar. Attend more meetups. Yes. Would there be any integration with the job board? No, the job board? Oh my god, I don't have time. To read the job. Yeah, a lot of work. Oh yeah, I don't have time, man. Job board will require time, right? I'm trying to learn iOS. Sorry, I'm trying to learn PGA. Yeah. But I mean, I think job board is probably better than by Tech in Asia, right? Yeah, or just kind of. Do you have a job board? Don't you guys have a job board or something? Oops, I'm sorry. Tech in Asia? That's E27, OK? Like one of the startup. Embed the feed. Or maybe just, like I do have links here. Maybe I'll just point to the link there, you know, like Hacker Space, job board, yeah. All right, if not, talk to me. I shall not take much more time. Let's talk after the meetup. Thank you. Thank you.


I'm really excited about how we're set up and how it's going to work in this draft process. I'll let anybody in here, huh? They really will. Look at you. Wait, are you the coach? Coach? I'm the Tennessee Titans. I'm in the stadium groundbreaking Thursday afternoon. You've got a lot of events to be at. A lot of events.  It's the tour. It is. It is. AB Wells and I are now pleased to be joined at the 2024 NFL Combine by Titans head Coach Brian Callahan. I think you always operate with the, we're trying to put the best team on the field each year. Your staff and the scouting staff on the same page, looking for the same players. Now you really feel like you have a good vision for what's to come. Thank you so much. Thank you for your time. You got it. Yeah, of course. Appreciate it. You got it. I'll see you guys soon.


Are you passing out with the door locked? It's locked, it's locked, it's locked. Right, you okay? Babe, are you actually okay? Did you fall or did you just make a loud noise? Did you unlock this thing? Mariah! Let me just say, why is Tako sitting by the bill right now? He needs to be upstairs with me, getting ready for this freaking prank. I don't know what he's doing. Oh my gosh, the door, so he doesn't hear me. Good morning, Marvel Squad, and welcome back to our channel. If you guys are new, make sure you go hit that subscribe button. Turn your post notifications on, you guys can notify every single time post. Guys, today we're gonna be announcing the winners for the $300 giveaway. We're giving $100 to three of you guys. I'm really excited to announce the winners, so make sure you guys are staying tuned for the end of the video. To hear the winners of today's giveaway, I'm so excited, we're so happy to be doing this, and don't worry guys, if you didn't win, we're gonna have many giveaways in the future. I think we're gonna probably just once a month. So if you don't win, make sure you guys keep on showing love. The more we see you, the more you'll have a chance to win, and we wanna be able to get back to as many of you guys as we can. We just wanna do this, I feel like it's a good way to lift somebody's mood up and just make you smile. As you guys see, Bill is downstairs right now making us food. I was gonna start a conversation with him, but I decided not to, because I did not even want him to think anything's up, so I just snuck down there and saw him is cooking. It looks like he's cooking mac and cheese or rice or something. As you guys are about to taste, I'm gonna be do passing out with the door locked prank. If you guys saw the crime with the door locked prank, it's basically the same thing, but I wanted to be original. I looked up this prank on YouTube, and I did not see it anywhere. I wanted to try to create a trend that has not been done before, and I know how much you guys loved the crime door lock, and I know how much he goes along our pass out pranks. You guys think it's so funny, so I'm gonna be doing that. I think what I'm gonna do is I'm gonna do like a loud, because the kitchen is right below here. It's right below us, so any thump or loud noise that I do, he will hear it.  He's gonna be so confused. I'm hoping he runs up the stairs. I am gonna have a second camera set up outside of the room. I'm gonna have to figure out how to hide that because the camera is bigger, so I need to make sure I put it in the perfect spot anywhere you know. Team Ryan, he's not gonna even be expecting anything that's going on. I'm really excited. I wanna see how he reacts. I feel bad because he's gonna be freaking out of the door lock. Like when I did the crime, the door lock, he was so concerned and he just wanted to be there for me, so the fact that I'm gonna be thumping to the ground and just not responding or not doing anything, he's gonna be like, what the heck is going on? You know? Oh my God, he's so epic and so funny. I'm so excited to get a little bleed, but I think team Ryan in the comments, I'm a little salty with you, Taco, that you're sitting downstairs with Team Bill. You should be up here with mommy, you should be sitting right here seeing go team Ryan.  I'll try to get this video to, I wanna say 30,000 likes. We keep shooting for 25,000. You guys have been crushing it. I think we should shoot for 30,000. 30,000 for creativity, you know? So make sure you give this video a big thumbs up. If you guys are comment down below and staying tuned for the end of the video questions and staying tuned for when we announce the giveaway of winners, I'm super excited to be doing this. Let's give it. All right guys, so the second camera is placed and it's time to get this prank on a roll. I'm really nervous, but I gotta just frickin' do it. I got it. I don't know how I'm gonna make this thump, like I had to make it dramatic so he comes upstairs and he hears it. So I don't know how to do it, I'm nervous. All right, can you just? Ryan, you okay? Babe, are you actually okay? Did you fall, babe? All right, this is not funny. Actually, are you okay? Babe, are you okay? Babe, wake up, babe. Did you fall or did you just make a loud noise? Come on, this is not funny. Are you okay? Babe, are you actually, like, messing around right now? I don't even know how to open this door. Babe, come on, open the door. Ryan, wake up. Come on, this is not funny. Oh my gosh, come here, Ryan. Babe, wake up, wake up. Ryan, are you okay? Babe, wake up, wake up, open your head, babe. Please, wake up. Oh my gosh. Wake up. What was what? What was that? What do you mean?  I'm already talking about it. You literally were smacked on the, what? You literally were smacked on the ground, babe. Who are you?  You're not serious. Babe. Don't touch me. Stop. Don't touch me. Ryan, stop, I'm your boyfriend. Okay, don't touch me. Ryan, you literally were on the floor. I heard a loud bang. I did not fall, what are you talking about? You did, your head's cold because you were by the vet right here. I did not.  Why do you think there's water on your face? Guys, just spray water over your face to wake you up. Pass the ball. Are you okay? Yes, babe. Oh my God. Did you bump your head or anything? Are you fine? I don't know. Come on, you're okay, right? I don't want to throw up. Well, let's go lay down. I don't know who you are. Just stop touching me. You know who I am. No, I don't. I don't want to. Okay, well, just, you're probably just confused of what happened. You were in the bathroom and then I guess you fell and hit your head on the floor or something. Stop. Oh my God. Babe, babe, are you okay? Over heating or something, babe? I'm sorry. What? What? Are you delusional right now? What's going on? Why are you laughing? Okay, just stop. You're not, you're not, stop. Are you okay? It's not funny.  It's not funny. And the door was locked so I couldn't even get to you right away. What? Why are you laughing? Because I'm having a cold. Your slap. I didn't go to the salon. You're slap heavy, bro. We gotta, we gotta, we gotta give you the shower. Give me the shower. Oh my God. This is a joke. Y'all think he was climbing up the gate. It was a bad butt. So the reason we have this gate up in his bag.    Mariah. Guys, I am so. I thought that Bobby pinned it on the door. I didn't even know how to, like I thought you had a door lock on top of here somewhere. Oh my God. That was so funny. I was nice when he sprayed water on me. I tried passing out again and you just really drenched me. What am I supposed to do? Literally, it worked the first time I did it again.   That was, I know. That wouldn't have been good. I'm sorry, Mariah. It's okay. How did you not laugh when I was yelling at you, babe? I don't know. I was really hung up. Oh my God. You're so annoying. And it was a good prank. Look at him. He's just chilling, enjoying his time. What are you doing, dude? I can't even move. He, I bet you, you made him so concerned.  Sure, yeah. He was really concerned for mom. I know, babe. You didn't even stop with this stuff. He's not with the pranks. No, you know I got you good. Cause that was an original prank that I didn't knew.  Oh my God. We had me on Instagram some prank ideas because I need to get this girl back. I need to smack her with her own medicine. Just wait, I'm gonna get you back so much better. People come to the channel for Team Bill but they just watch your videos. If you sent me, you know. I'm just kidding. That was a pretty good prank.  I also told the local squad we're announcing the giveaway winners today. Oh, we are today. I totally forgot, guys. We're giving away $300 right now. So we're going to pick. I know we've been doing this for I think a little over a month but we're picking the three people that are winning. We really had a hard decision picking. It was really hard to pick. But don't worry if you do not win. We will do way more giveaways and we have a lot more to come in the future so get ready for that. You wanna start with the first one? The first one that won $100 is Mariah underscore dot bill. It's a fan page but her name is G. G, she's such a huge supporter all the time. And we have a lot of fan pages. Don't think that even if you have a fan page and you did not win that we don't support you or anything. We literally love you guys so much and it is so hard to pick only three people. I wish we could do 1,000 people, 100,000 people. But G, we're giving you $100 for this giveaway. Who's the second person, babe? The second person is Iris Lynn Weber. Iris Lynn Weber, thank you so much for being so supportive on our channel. We're gonna put their at names here so you guys know, make sure it's the right person so we're gonna put like your Instagram. And we'll DM you guys after this. But Iris, you got $100. Thank you so much for being so supportive. We love you. And the final, I always see her. She's always on our page. She's literally always on our page too. Morgan Underhill. Morgan Underhill, thank you so much for being so supportive as well. We love you guys. We really love you, you got $100. And that concludes this giveaway. Oh my God, I wish, I literally wish. We have so many more people in mind, trust me, in our heads that we want to do giveaways and just, you know, compete and all this stuff. But it'll happen in the future. So don't worry if you do not win. We literally love you and appreciate all of your support every day. For those of you that do have also fan pages along with them, thank you so much for being supportive and like doing edits, videos. We literally love seeing all the pictures and stuff that you guys create. They're literally insane.  So thank you so much for giving back. Also, for the question of the day, I want you guys to comment down below more giveaway ideas on what you guys want to see for our next giveaway. Comment down below some ideas and that'll be for today's question of the day. I want to see what you guys are thinking and what you would want to see in a giveaway. Anyways, Waffle Squad, thank you guys for tuning in today's video. I hope you guys liked me pranking his little booty butt. You saw it, babe. Yeah, literally. That was so bad. Pranked with no idea what was coming for. I know, I know. It was like his little bathroom was locked and you were making, I don't know how you didn't laugh. That's just, that's going through my head. I know, it is hard. It is always really hard not to laugh. Were you smiling in there? Like how? Yeah, I was laughing. That was banging on the door. I was like, babe, unlock the door. Yeah, you were going crazy. If you are not subscribed to our channel, go hit that subscribe button and turn on your post notifications so you get notified every time we post. But I think that is it for this video. Is it it, baby? Are you done pranking me? It's done pranking you. Thank God. I can't handle any more Team Mariah today. Anyways, guys, see you guys in the next video. But until then, peace, bye.


Well, it's everybody Jason here for jasper's case breaks.com. We're giving away five free spots away with this select pack filler here to give away Six Bowman spots, so we're gonna give away five free spots in this break We only sold 25 out of the 30 and then we're gonna give away six Bowman filler spots away at the end We do this 2021 select poof baseball one pack copy break number 11 So here we go guys so the dice roller here will be for the customer names to give away the five free spots And then we're gonna give away the spots at the end. So here we go dice roller three and three six times top five get free spots in here guys one two three four five and six So six times top five Zach Bennett Josh Jeff and Jeff Congratulations, you guys got five free extra spots to give you a better opportunity to win a team random spots so we go So we use this list for later and now Let's do six times on the names and teams in the break one two three four five six Josh down to Zach six times here one two three four five six Rocky's down to the Texas Rangers. All right, there you go Stick to what you got of course.  Good luck One two three four five six and seven Josh Zach Ryan Zach Kevin and Josh Congratulations, boom top six get a spot in the team random filler And again the next pack filler is on the website guys Sells out the break Well, what's going on here? So they go appreciate it guys. Jasper's case breaks calm


I'm going to be introducing the first two speakers who are going to tell us a little bit about handwritten text recognition. So we're going to have Jacqueline Somburg and Caroline Picoski from the McGill Library. Jacqueline is the outreach librarian at Roar, the Rare and Special Collections Oslo Art and Archives, and Caroline is the metadata and electronic resources librarian. They will talk about how they have applied handwritten text recognition on a couple of McGill's archival collections using the core text platform and the kind of practical applications they've encountered, the technology, the sort of the challenges and the best practice in terms of using this technology to access archival collections. So I'm going to now hand over to Jacqueline and Caroline and I believe we have a video from that. So good morning or afternoon wherever you're joining from today. Jacqueline and I are delighted to be here with you to share our work on enhancing the discoverability and accessibility of handwritten text, applying handwritten text recognition or HDR to McGill University Library collections. This presentation will describe our process for applying HDR to two of our archival collections using the core text platform. So our next slide now is going to show that first and foremost, the fundamental goal that has driven our work has been to make our collections more accessible. We're keeping all of our stakeholders and users in mind from faculty and students to researchers both at and external to McGill, as well as members of the public. The value of these unique collections is tied to their use and discoverability. So ensuring that this collection is as findable and accessible as possible has been the why behind everything that we've done. And this is why we were committed to trying to apply HDR to our collections as one additional access point to these materials along with cataloging metadata and the digitized images of the materials themselves. So with that in mind, I will now turn things over to Jacqueline to speak about the context and the specific collections we've been working with. So thanks, Carolyn. Here at McGill, we do have four rare collections under the umbrella of a war. That's very special collections. The Ulster Library of the History of Medicine, the Visual Arts Collection and the McGill University Archives. The library's been collecting materials for a long time. We started in the 1850s and now through purchases and donations, the holdings are rich research collections, including a great many manuscript materials in over 250,000 items unique to the world. So we invite the curious everywhere to discover our collections, but we have found that handwritten materials do present unique challenges and unique barriers to access. To this point, handwritten materials have really only been searchable by human eyes, requiring time consuming transcription and double checks or crowdsourcing and double checks to generate searchable transcripts. So for this pilot, we were excited about the potential of AI driven handwritten text recognition and we chose to explore the options because really handwriting can be a very major barrier. Our librarians have had experience working with students in the classroom setting and it's been eye-opening to see that even history students who received the most training and working with primary materials can be put off by the time and effort needed to make handwritten effective use of handwritten documents. So we're excited about the potential with HDR that would enable new search techniques. So we chose two collections. The first one is actually this one, the Doncaster Collection. It's 12 manuscript recipe books and over 1300 culinary and medical manuscript recipes. It's dates from the 1790s through 1840s and mostly from the Doncaster area of South Yorkshire centered on Hootman Pagnell Hall. Why this one? Well, it's entirely manuscript and it's fairly small in size. So the scope was appropriate as well as the content. It was also the subject of an active research interest at the time and as such, it was a good test case for transcription functionality because that project was generating the transcripts of their own that we could use as a comparison for the AI generated transcripts. So we ran with this and we published it in April of 2020 at a time, unfortunately, when all of us were focused on the growing COVID-19 pandemic. The second collection that we worked with is a collection of fur trade materials here at McGill and this collection includes records that document the finance accounting and administration of the Northwest Company. And the Northwest Company was active from the 1770s through about 1821, at which point it becomes more recognizable worldwide. It merged with the Hudson's Bay Company, which has more name cache, I believe internationally. In many ways, the histories of those two companies are the history of European colonization in the landmass referred to as North America. Now users can take a detailed look at the impact of the fur trade across the country through the lens of the documentary evidence, account books, ledgers, estate documents and correspondence. You can see James McGill's signature here. Although headquartered in Montreal, the Northwest Company extended its reach as far as the Pacific Ocean and the Arctic Ocean. In these records as well, Indigenous knowledge and Indigenous peoples were really a principal part of that fur trade and they were also, or sorry, they are also therefore present in these records, albeit indirectly. You can see on screen here that some different Indigenous groups are named in these documents. They are named by exonyms, to be sure, but they are noted in the account books and the material also attests to the critical role of Indigenous peoples in the fur trade. They were the primary providers of furs, as also the crucial sources of knowledge for the European fur traders as they established their networks in North America. Letters of several of the company partners expressed the complicated nature of the relationship between the peoples. I want to take a moment to acknowledge that McGill University is located on land that has long served as a place of meeting and exchange amongst peoples, including the Haudenosaunee and the Nation Bay Nations. Roar honors, respects and recognizes these nations as the traditional stewards of the lands and waters on which McGill University stands today. Here we meet to study and exchange ideas, but the legacy of those Indigenous peoples is here in this place as well as in this collection and records of their knowledge and influence are listed here on screen in tidy black and white. As the archivist Tom Nespitz writes, Indigenous peoples provided technological, agricultural, military, cartographic, economic, medicinal, weather and wildlife information. They are named, described and extensively quoted, sometimes in their own languages, in the records. They were sketched and photographed and filmed, and the archives of their knowledge helped to create the archives of the Europeans that they encountered. This collection in particular is one of those in which we see the influence of Indigenous peoples. It also represents commercial, political and social interactions between Anglophones and Francophones, and you can see that in some of employee contracts, which you see here in French edited and redacted and take a form contract and annotated by hand. So this was one of the challenges actually for HDR recognition, but with that context, those are the two collections that we chose. I'll pass it back to Carolyn for a dive into metadata. Thanks, Jacqueline. So our goal was to take the Doncaster and Furtrade collections and import them into the Cortex platform, and I'm going to take some time now to review the metadata considerations that were involved in the import and how we tried to make decisions that would allow the metadata to function as additional access points to the materials once they were within Cortex. The question, I think, a good starting place is to ask, where were these collections to begin with? And if we go to the next slide, you can see a representation that the collections do exist physically, of course, at McGill. In terms of this work, I was mostly concerned with how they're represented online in our archival catalog, which is built with E to M. On this next slide, we're going to take a closer look at the James McGill phone, which is part of our Furtrade collection, as Jacqueline has described. And as you can see, there was already a lot of detailed metadata in that online catalog associated with the font and the individual items in these collections. And luckily this meant that the groundwork was really there. There wasn't a lot that I had to do to prepare this metadata for ingestion to Cortex. Now we're going to take a look at where things ended up and where all this metadata is now. You're going to see a snapshot of the mapping exercise that we did, which was primarily set up by my colleague, Megan Chellew, which was to help us get ready to perform the important to Cortex. So at this point, we were trying to pick and choose the most important or most used fields from E to M or Adam to carry over into Cortex, keeping in mind the user's experience and looking for ways to enhance their options for discovering the content via whatever different pathway they chose. You'll see sort of the final product of that mapping exercise, which was the final field mapping that was built up in Cortex. And it includes all the fields that we opted to include on each item's display in Cortex. We had two different field mappings, so one for Doncaster and a separate one for Furtrade. And while building the field mapping, we also spent time deciding which fields should be controlled vocabularies and which would be text fields. So the controlled vocabularies in Cortex allowed us to do things like create font-level landing pages and allows for greater browsing opportunities overall for users. And later on, you're going to see the controlled vocabularies. They sort of show up as little grayed out terms that are affiliated with each item in Cortex. If we go to the next slide, you'll see a representation of the work that I was doing to prepare some of the exported metadata. So essentially, I worked with metadata exported out of the archival catalog. And then I edited that using a combo of Excel, Python, and as you see here, open refine. And if we go to the next slide, you'll see an example of an Excel file that's ready for upload directly into Cortex. I dealt with just one font at a time in my case, so I only ever did about a maximum of 50 items at a time, but it would be possible to do more. And I made some changes after this initial file upload within Cortex because that's an option using batch editing and some of their other features. So I would say as a final note on metadata, the workflow we have is fairly well established now for future metadata transfers of the sort. And we would have a standard in mind for doing transfers at least into Cortex. Tools like Excel and open refine, as well as Python, and as well as the batch editing that's available in Cortex, I'll ensure that this metadata is easy to work with and rework as needed. So at this point, we're going to actually take a step out into the Cortex site and take a bit of a site tour through our online platform and the online exhibits that we have. So we're starting on the home page of the Miguel Cortex site. Cortex simplifies and automates our workflows for transcription, but we also use their tools to build exhibitions to accompany this material and to make the material available online. So the search box that you see on the home page will search across all of our collections. But as we've mentioned, we started with one collection in particular, which was Don Caster. So we'll take a look now at the Don Caster specific landing page. Now that we have two collections in our Cortex system, we're making use of things called list pages, which is a website template that will build pages based on your controlled vocabularies or collections. This function makes generating pages simple, and it still allows you to customize the raw search options and appearance. And now we'll actually take a step over into our second collection page, which is the fur trade landing page. And it's possible for users to also do more of a browsing using the find function if they would prefer to do that. So we're going to take a look within fur trade at how you could browse through our different phone pages. And we're going to jump in directly into our James McGill phone, which is one we've been discussing throughout so far. And finally, we also want to take a look at our fur trade exhibition site, just so you can see what that looks like to bring these collections to life all the more. So if you click into the exhibition site, we're going to jump over to the second slide just so that you can see an example of how you can toggle to the full screen to get a better look at an image. And you'll see that there's also a nice image caption that's associated with the image so that you can get a bit of a description about it. The interface does let you embed other external links. So what we did here was embed a contemporary map showing the location that this fire plan corresponds to today, which is quite interesting if you want to walk down to Old Port, you can see where these buildings stood. One of the other functionalities of the exhibition is that it is powered and linked to all of your assets in Cortex. So if you click on this related page, it takes you out to the actual contract of Jacques Ratel of L'Assomption of Voyager and who signed his name there as I zoom in and out a little bit too quickly. His contract is there marked X at the bottom, but that's what the interface looks like when you look at an individual item. You have the summary here. You have the metadata listed below with those controlled vocabularies that Carolyn pointed out in her comments. You can click through any of those and it'll take you into the list of related assets. And then the other thing that is important is, of course, you can look at the transcript right here. And the other difficulty that our collection posed was, of course, it's multilingual. It's in French and English. And it is manuscript, but also tabular manuscript data. So I worked with Cortex to select samples for testing their HDR accuracy. I'm going to flip back to our slide deck now. And what we did was try to hit all of the major categories of material and to have a clean and messy example of each category. So clean correspondence, clean ledger, a clean map, a clean daybook, etc. And then what we did was create a clean and corrected transcript based on the transcript generated by the AI. Testing showed us that the generated transcript online, as if your sees it here, doesn't actually show the line breaks that are in existence if you download the transcript. So that's one mismatch between the viewer experience and the downloaded transcript. And we found that the accuracy of detecting column breaks was actually quite high and character recognition is very high. But with the tabular format, the breakdown is in generating a transcript that makes sense in order because the line breaks do tend to really confuse the AI. Another thing on this one that causes issues for the AI recognition of the handwritten scripts is actually the page curve at the binding. So we newly discovered the importance of very flat and very clear digitized images. We use the historic handwritten scripts and HDR provided by Cortex does have different scripts that are better for different time periods. This is the corrected transcript in process that we provided to Cortex so that they could test the accuracy character by character word by word and line by line. And they did a lot of work and have all of the documented accuracy ratings for the test samples that we gave. This is an example of correspondence in a mediocre personal hand which actually belongs to James McGill and the generated transcript is there. The accuracy ratings were variable depending on the legibility of the script, but overall impressive. And it opens up a keyword search across the entirety of the collection. So the one thing that breaks down of course is tabular data, especially with non-text characters. So things like ampersands or apostrophes or this sort of thing, they really did confuse and break down the legibility of the generated transcript. So for us, the project showed us that the hard work put in to make our archival collections available even through A to M is well worth it because that prepared the way for transcription workflows in this new software in Cortex. We've gained knowledge of the strengths and weaknesses of this particular AI-driven HDR throughout the pilot and it gives us a new lens to look at our collections. We know what type of material, return the greatest character and word recognition, and we know also the inverse. What materials are better lasted to manual and human transcription at this point. I'll close now with some words from my colleague Ellis Ng who curated the fur trade exhibition along with us. As librarians and archivists, we can't possibly know all the potential uses of the material we care for, which is another reason why HDR and other developments can help overcome barriers to research are so valuable. We want to empower people to make use of the material in whatever way they want rather than dictate the ways in which it can be used. Thanks for listening. Thanks. Thank you very much, Jacqueline and Caroline. Really, really interesting presentation. I'm sure we'll come back to some of the issues about transcriptions and the challenges. Some of this actually came up in this morning's session with a programming historian and some of these approaches. Our next speaker is Jenny Ban from the National Archives and Jenny is a Head of Archives Research. She has over 25 years experience as an archival practitioner, educator and researcher and has been interested in the intersection and interplay between archives and technology throughout her career. She's going to talk to us about AI and the glam sector and what it might mean, the latest craze for the glam sector. So thank you, Jenny, and I'm going to hand over to you. Thank you, Paolo. The title of this presentation was in... Oh, I must introduce myself. Sorry, I am a white woman. I'm quite short. I have brown hair. It's tied back. I'm wearing a blue and white, blue and blue pattern top, which is the same top I wore on Tuesday if anybody was here on Tuesday. So that's me. And the title of this presentation was inspired by an article by Terry Eastwood, which was called Nailing a Little Jelly to the Wall of Archival Studies. And in that article, Terry Eastwood set out to dismantle an edifice of ideas to see of what it is really made and whether it will stand up to close scrutiny. And in this presentation, the edifice of ideas under scrutiny is that of artificial intelligence, because in my opinion, this is something that badly needs pinning down. These days, it is all AI this and AI that. And I, for one, am increasingly put in mind of the emperor's new clothes. So what follows is a personal reflection on the way I currently make sense of AI in the game. And I will be asserting a kind of definite view, but I do so not because I want to persuade you to the same view, only because I want to encourage you to take steps to inform one of your own. When I'm asked kind of what is AI and I'm asked to define it, I choose to sort of do so in the terms on this slide. And as you can see, those terms are informed by looking back into the history of AI and to a summer workshop held at the Dartmouth College in New Hampshire, which is commonly regarded and by commonly regarded, I mean, IE by Wikipedia as the founding event of artificial intelligence as a kind of academic field. Now, the exploration that started at that workshop is still very much ongoing, and this hypothesis is still far from proven one way or another. But what is certain, however, is that as is the case with quite a lot of academic exercises, the knowledge and techniques developed as a result have found fruitful and profitable application in any number of real world contexts. And in this respect, another quote I particularly like is from Ralph Cornis, who wrote in the pages of the Records Management Journal way back in 1989 that artificial intelligence, which many saw as the wave of the future, will arrive by osmosis. Other branches of IT will steal its clothes. It is already starting to happen. Osmosis can be defined as the process of gradual or unconscious assimilation of ideas or knowledge. And it is this unconsciousness that I see as the problem, given what we are starting to realize about the potential applications of AI to remain unconscious of that assimilation seems to me to be asking for trouble. One of the first sort of new areas to spin off from the quest for AI was that of robotics. Now, this field has achieved considerable success in proving the hypothesis that one feature of intelligence that can be described in such detail that a machine can simulate it is the ability to follow a clearly set out procedure to get that is with the program. Indeed, machines can do so quite literally such that they are able to do so arguably more slavishly and consistently than any human ever would be able to. And because they can simulate this feature, they can and do perform routine and repetitive manual tasks, albeit under very carefully controlled conditions, because they are still not good at simulating that feature of intelligence that allows us to react to something unexpected happening, like a bike suddenly veering in front of our self-driving car. More recently, another spin off from the exploration of artificial intelligence has been the field of machine learning. And the feature of intelligence that machine learning simulates is our ability to process data to iterate models that allow us to make judgments or predictions on the base of similar data in the future. So to some extent, then, this could be seen as learning by experience, but in the case of machine learning, that experience is exceedingly limited in range. But even so, the machine simulation of this feature has advanced to the extent that it already mimics the almost unconscious internalization of the arrived at model, which leaves many experts unable to explain fully why and how they have come to those conclusions or by those insights. Then again, the simulation also mimics the well-known problems of reaching any conclusion on the basis of data that is inaccurate, incomplete, and or unrepresentative in some important respect. Training and refining these machine mental models takes a lot of time, a lot of energy, and a lot of data. But models have now been created that do allow machines to simulate perhaps more advanced features of intelligence, such as the ability to parse natural language or to recognize an object appearing in an image. So as the phrase goes, fake it until you can make it. But while the machines may now be able to fake it, actually what we make of it is still up to us. Well, what then should we make of it, I guess, is the next question. And to start to answer this question, I feel it's instructive to think about what others are making at it and what many people are making at it. In particular, perhaps the big players in technology is another service that can be sold to us. So as to why we might want to avail ourselves of this service down the right, you can see a list of the sort of things we are being told we can achieve if we choose to employ power of these new services. So in the glam sector, we may be less interested in fraud detection or combating financial crime, but achieving the last two in bold, I would say fall very much kind of within our sights. So knowledge mining, according to the sales pitch involves uncovering latent insights. This is absolutely one of the things we want to facilitate. As glam organizations, we know that our collections are crammed full of latent insights. That's partly why we put so much effort into preserving them such that this latency can be realized. Document process automation on the other hand involves turning documents into usable data at a fraction of the time and cost by automating information extraction, particularly perhaps in the more archival parts of the glam domain. We have more documents than we can possibly process using manual methods, but it's also kind of generally true, I think, that the holdings of glam organizations quite often are not usable data in that sort of digital data science way of things. So that's big technology players. What about Glam's? So here we have the results of a project which show that knowledge extraction and metadata quality are two of the main reasons why Glam's are interested in AI and they're also of course the areas where its application has been found to be most useful. Now these two are of course related because knowledge extraction or mining, whether it is AI assisted or not, is always ultimately dependent on data quality. And this connection may also explain why the potential of AI is seen perhaps most as pertaining to the application areas of collections management and discovery and search. So this is where Glam is currently focusing its attention in relation to AI with possible applications such as audience analysis and machine translation still of interest, but not as much. So nailing a little jelly to the wall then, let us narrow our focus accordingly and to look at what we are currently making of AI in respect of one, turning our collections into usable data, and two, uncovering latent insights. First then, turning our collections into usable data. One thing that all Glam institutions are very aware of is that spinning straw into gold is quite a resource intensive enterprise. The added value of our material curation and care ensures and allows others to realise all sorts of values from that material, be that cultural, aesthetic, emotional, informational or evidential. Ensuring and allowing this outcome has always involved material preservation, along with the collection and curation of lots of additional intelligence, information or metadata that allows the relevant material to be found, understood and sourced when required. With the arrival of new digital ways of processing, however, to be considered usable, all this material and information is now expected to be accessible in a new form, which is amenable to that type of processing. We are entering the world of, so to speak, collections as data. So spinning collections into data is a sort of constant background task and reality for Glam institutions and we are starting to make something of AI in this regard. For example, it is through the application of machine learning that projects such as transcribers have allowed for leap forwards in handwritten text recognition such as we've just been hearing about. This handwritten text recognition allows for the spinning of such text into a digital form. Once so spun, this text in a digital form becomes amenable to another application of AI that of natural language processing. One project to try to make something of this was the cybernetics thought collective project at the University of Illinois. Working on the digitised papers of leading cyberneticians, they use these techniques to automatically generate metadata such as percent sentiment scores and you'll see some of these in a minute. I've introduced this metaphor of spinning straw into gold because it also allows me to talk in terms of a gold standard. All Glam institutions want their collections to be both usable and used and yet the gold standard of what is needed resource-wide to achieve the levels of usability that are needed to attract the levels of use that are needed to justify the level of resource expended in the first place just keeps expanded and I often find myself sort of asking where will it end? So this then is me on a bad day. I want to be helpful. I want to make my collection usable but at what point does this become too big an ask or too impossible an ask? At what point do all those who are gaining the use of and value from all of this usability I'm generating need to sit down together and renegotiate where the work of and resource for usable ends and that of and for use begins. On a good day though I do recognise that this renegotiation is already happening so it's happening for example in the way that academic funders and institutions are starting to acknowledge the need to cost in the work of so-called research technicians and by maintaining their own research data repositories to take on some of the cost of ensuring that value once gained is not lost again by sort of but remains usable it's maintaining its usability it's available for reuse. So returning to the original question of what we are making of AI in respect of turning our collections into usable data I think it is clear that we are making some progress with applying it to accomplish some sort of specific tasks in service of that goal such as handwritten text recognition but that in others such as perhaps generation of metadata our efforts remain at a much more experimental stage. So we turn then to what we are making of AI in respect of uncovering latent insights as I mentioned previously uncovering latent insights is to some extent what the glam sector is all about certainly perhaps in terms of why it is seen to have public value so what then are we making of AI in this respect one answer that question has already been hinted at that we are only doing this indirectly that what we in glam are making of AI are the means to automate the turning of our collections into data that is usable digitally because we anticipate that this will lead in turn to the uncovering of latent insights and numerous digital humanities such as the one featured on this slide would seem to suggest that our anticipation is justified but perhaps a better question to be asking is what latent insights could AI help glam to uncover that are of more direct use to its practice rather than to that of research my answer to this is that in its simulation of internal mental models on which the few base future judgments or inference and its blunt surfacing of the uncertainty or if you prefer the subjectivity of that process in statistical and numerical terms certain applications of AI force us to confront the fact the same is true whether these models are held by a machine or a human being we've long been aware of the biases uncertainty and absences within our collections but perhaps we might now be able to develop tools to help us become more specifically aware of them to quantify and communicate them more effectively to allow more informed use of our collections possible perhaps in raw informational terms the machine generated sentiment score presented here is is not that useful but its presence and the questions that generates about the degree to which we can be confident in any judgments drawn from the material being described is nonetheless to my mind still helpful so to conclude then my view is that AI is an ongoing academic exercise to explore the hypothesis that every aspect of learning or any other feature of intelligence can in principle be so precisely described that a machine can be made to simulate it in exploring this hypothesis techniques and technologies have been developed that do simulate certain features of intelligence which once simulated allow for the application and development of machines to perform tasks which could previously only be undertaken by human beings and in the glam context the main task we are currently looking for machines to perform is the automatic datification of our collections be this conversion into a digital form or where material already exists in a digital form the conversion of it into more structured and refined digital forms and once in these forms the material undoubtedly becomes more usable that is to say usable in more ways e.g. over greater distances or at greater scale but whether automated or not such conversions do not come cost or risk free and we may all want to play with the shiny new toys but we must not let this distract us from these costs and these risks thank you thank you very much Jenny very well made points I had a number of questions triggering in my mind about the expectations also that we have when engaging in these the outputs of these technologies but again we'll leave that for later so our next speaker is Stephanie Decker who I think will be speaking on behalf of a number of colleagues on the projects that they have worked on Stephanie is a professor of history and strategy at the University of Bristol and a visiting professor at the University of Gothenburg in Sweden and she'll be talking about a piece of research that with her team they have carried out with funding from the HRC on contextualizing email archives and I have to say that a part of the team members who have put together the presentation but I don't think are speaking with Stephanie today are Adam Nix from the Birmingham Business School, David Kirch, University of Maryland and St. Thileta, Kupili Venkata from the National Archives or I believe ex-National Archives. Anyway, Stephanie over to you. Thank you Paola. Just to say I don't normally sound like this I'm on my third day of COVID so my apologies for that. Maybe starting with the visual description you asked for so I'm a white woman in my 40s I've got brown hair chin lengths you see me in my office with books in the background a wear a black jacket and a brown turtleneck. So as Paola already said I'm presenting here on behalf of our research team so two of my team have joined us today that is David Kirch and Shanti Kupili Venkata. Adam unfortunately couldn't make it because he would have only been able to join later. So we've been working on a series of projects the first one been contextualizing email archives together with the National Archives the second one a project led by David in the US on the MCODIS tool which is the one we developed in the first project so they're largely our projects dealing with the same issue the same problem which is what we'll be talking about today. So for DCDC we've called this digitally curious context beyond the search window really what we're interested in is how will people actually interact with born digital resources when they come to collections and they seek to actually find material for research you might also be for example um other users in in the glam context maybe trying to understand what is in a digital resource and the project and its questions really come from our own problems its research is trying to to figure out how will we make use of digital resources in the future okay so our project takes a user perspective so this is somewhat different perhaps from from some of the presentations earlier for us the questions really how born digital sources are going to be vital for future researcher draws on on historical ideas so so looking backwards in time that might not only be historians we all work in a business management school context might also be cultural studies literature lots of people want to go back to material in digital or non-digital um collections and our main problem at the moment is that a lot of these born digital collections remain inaccessible so so as a team we've written a paper on this about the dark archives and what will happen if some of these archives actually become accessible but at the moment for legal reasons um researchers have very little opportunity to actually understand how they might want to research these resources that maybe some archivists and and owners of collections already have but may not be able to put in the public domain that means they may not quite understand the ethical implications but also the practical implications of how we would be using those resources because most of us have just been trained on the use of physical and pre-digital sources so other than people who work in a particular computing science of big data context for many of the rest of us how will we actually make use of digital sources is not at all clear and people have a lot of preconceptions but not necessarily a lot of knowledge opportunity to test it so our research project tries to look beyond the current issues with preservation which we understand are very significant um arguments we make how they are shaking up traditional archival processes just because of the size and and some of the privacy concerns with digital resources our privacy in particular for us here in the UK and Europe GDPR as a particular issue means that simply a lot of it can't be made accessible or can't be quite worked on in the way that maybe in the future we'll be able to. East Cheyenne has made the the point that really to to address this problem of access might require collaboration between um those that manage the collections and those that ultimately want to use the collections and this is sort of the spirit in which we've tried to address some of the questions and then our work um and looking at access issues um existing work for example from the Wellcome Trust to sort of argued users want optionality but they still expect some curation from archivists because they're still inexperienced in the use so that doesn't necessarily answer the question of how archivists will be able to provide that curation keeping the size of some of these born digital resources so our key question in our project in both projects really has been around how users will actually engage with born digital material once these access issues have been navigated because from our understanding working with these sources that the problems don't end with the moment that we actually get access to the digital resources and at the moment we don't know that because so many of them are not yet accessible so our first research project contextualizing email archives was very much focused on exploring this gap between the current efforts to preserve and then the means by which researchers might actually want to engage with them so so what happens after they've been preserved so for this we collaborated with the National Archives however we actually used data that isn't in the National Archives because these are emails of a failed us.com company that David Kirsch is our collaborator has already worked with in a research context made these available for the research via the Linguistic Data Consortium so linguistic data already tells you this is large-scale what's called non-consumptive use so it's very much about modeling interactions and it's a large-scale data analytic use so we collaborated with the TNA with a digital archives specialist especially Jean-Tillatou Coupilli-Vancasse and our aim was really to look at how we can make email archives available for search and study whilst drawn on these relational network properties of the format that have been well researched but actually also making use of them for people who might want to actually read the emails and know what people were saying to each other and we're particularly interested in emails because we think there's specific issues here the network resource so you could say emails replace correspondence that's not really true it's more like almost a telephone conversation perhaps because it's the back and fools so an individual email outside the context of its thread can be hard to interpret so email is emails also are in the plural and also who's writing to whom who's in the cc and who's in the bcc is it's not just content it's not just information it is actually also context to understanding the meaning of a conversation so when we see non-historians or non-qualitative researchers look at emails they often look at aspects such as frequency networks timing and sequencing language or content all of them in isolation we see all of these as context we actually need to you know to interpret a historical source obviously now we particularly look at organizational email because we believe that they're going to be very useful historical sources and for those in particular you need the individual in the network aspects a couple of other assumptions we made is really that you know how we approach something is not how everybody else will approach it so we need to accommodate really diverse research questions users will probably work iteratively and might have to sort of tacit and somewhat messy approach that many historical researchers have you go in with a general question what we find determines how you rephrase the question people will come with different levels of experience and ideally you want to offer them a relatively complete access to a whole quarter so they understand what's not there as well as what's there and we try to sort of think about how does what we are proposing differ from how you might have previously accessed these sort of resources so previously you may have relied heavily on the archivist you might have come in and say okay i want to know what's in here on e-business trends in the early millennium it's definitely something that there's this source we looked at covers you might look at finding aids or a catalog structure probably ask the archivist if they know the resource you might read closely go back to targeted search so you iterate backwards and forwards between a structure and what you find and how you begin to understand how the structure works for you now in a digital resource these structures are unlikely to be there or are not likely there in quite the same way so say you come in with a search query you know your classic way looking at a text resource might be to look at keyword search so you look at e-business trends in the years that doesn't necessarily give you the intersection of all of these themes so the prototype we developed in the first project which we call M-Codist is trying to be a search tool that sort of closes this gap from from like the simpler search approaches first option within that tool would be to use phrase matching which allows you to draw all these terms together but you know there's also the problem of what if people didn't refer to it as e-business trends in that particular collection or that particular time so the M-Codist plus version which uses attention-based content encoding is trying to also bring up the synonyms and all these terms that were used maybe relatedly and which the tool should help us identify so not knowing what terms to look for the tool supposed to fill that gap though this this is something that we're currently in the process of testing how well that actually works and in order for this to work better we are trying to bring context in so to really think about what do we know about a source and how can we use that to actually help such a tool to work but this we need some external sources of context in addition to the emails we talked about something like an organizational chart if we're looking at a business context or an organizational context known relationships between individuals you know are they all the same managerial levels as the CEO and the PA are they market or geographic events you know an outside I might not know but this this and that happen in the source and this is likely to generate a lot of emails that might be interesting but they might not know the precise terms how can we make sure a new user can find that and that's what we're trying to do with the M-Codist tool so M-Codist stands for email contextualization discovery tool and the idea is really that we can draw on different sources of context to help people find better results in emails in our experience the results you find when you search emails not always that great not always quite what you're looking for as a researcher in the second phase of our project so we're on to the second project at the moment we're really interested in how research would actually use this tool because you know it's all nice that we designed it but A does it do how we designed it and is that actually what other researchers want so we are currently working on a web-based version of the tool for early august to then have an opportunity to review user behavior so we're making it clear we're logging the activity to see how user friendly how well can we navigate the tool we're requesting user evaluation through a short survey and in particular we're interested how users navigate the empty search box because what we're assuming is there's a googleification of search right you ask google anything you put it in the box and it throws out an answer because it's got the totality of the internet now obviously where the digital resource for the search box you know these resources are limited and if you use the wrong terms it's not necessarily going to give you any results so this is one of the problems we anticipate but we also want to see how will people phrase a query when they do not actually know what's in the results because that's the fundamental problem of coming to a new research area coming to a new archive you never quite know what's in then without the traditional finding aids potentially for digital sources it'll be even harder so for this MCODIS test version we're using the Enron email corpus largely because obviously Enron is in the public domain we don't have any of the privacy issues because all of this was made available and has been online for well over 10 years the Enron data set is also interesting in a different way because Enron obviously if you know what Enron is you know Enron because of the accountancy fraud and if you come to an email data set and you want to read the emails about fraud how do you type your query I mean you put in fraud and you expect to get all the emails about fraud I mean realistically you know people don't say they're committing fraud while they're committing fraud so how do you find these emails so that's a good sort of idea around how do you how do you phrase any conceptual query that isn't a keyword per se how do people do that and what does the tool need to do to actually help them do that secondly the Enron data set is interesting because it's a little bit misleading it was actually collected as part of the investigation into Enron's involvement in the California energy crisis and that predated the accountancy scandal so while some of the emails relating to the accountancy scandal are in there actually the collection was before that scandal broke so this data set doesn't quite contain what people think it contains and you actually need to know pretty well how this data set came to be in a public domain to to know this and most people weren't so again and how far can a tool help people navigate a resource that they think they know something about but probably don't know that much about and that is not as a result going to throw out quite the results they're expecting so this is sort of our ongoing projects M-Codist in particular is something that I think we have on github so that's the link you have on the bottom of the page here but that's not currently the the usable version so we're working on on a sort of web hosted version to to use from from august onwards but if you're interested in the coding underneath I said it's under github contextualizing email archives and you can have a look there so this is our presentation I said this is on behalf of my team I'm Stephanie David and Shanti are here and Adam can't make it but Shanti is our technical lead can also answer any questions you might have on the more computing end of things all right thank you very much thank you thank you very much Stephanie again another really interesting presentation that has a lot of links to the ones that we've heard before if I can just invite all the speakers to come back on video please and again as we've been saying throughout the presentations if you have questions please pop them into the q&a through the q&a function and we'll just go through them are we all back okay thank you just before we go into individual questions I I just had a question for all of you thinking in different ways at the user side of things so I was wondering if you had any thoughts or any reflections so for example the first presentation in terms of the you talked about the challenges of the HDR so applying that technique and I was curious to know about what users have thought about it what kind of feedback you've got in terms of the the the results and how people have been able to discover the text but equally Jenny from your point of view I think you made a really good point about striking the balance between the amount of resources and what can then be expected as outputs again what what's your understanding of the sort of the approach and the reactions of of patients who might want to then use those data sets and equally for the email projects I'm not sure if others are now able to use the data sets that you have put together and analyzed but so that kind of user perspective first and then we'll go into something specific for each of the projects Caroline and Jacqueline do you want to go first sure I'll I'll take a stab at that one of the things with this collection is that tracking usage we can have quantitative numbers generated by google analytics tracking on the data the website itself to see how many people have viewed but we don't really have a mechanism in place for a qualitative feedback on the user experience it's not something that we have actively tested so we don't necessarily have that subjective user experience apart from our own internal testing with our team on using the platform and that sort of thing and I know that Adam Matthew and Cortex have a booth and we could probably all go and sit them in the exhibition hall and ask more about other collections too and and what sort of testing other collections have done for Adam or Cortex hosted collections because we are not the only people who have signed on and piloted and tried out Cortex tools but for our point from our point of view we focused in this presentation and generally more on the construction side and less on the user perspective so all we have at the moment is the quantitative numbers which we'd have to report back on but I think Caroline do you have anything to add to that no yeah I think I think that's right I think the focus of our project was a bit more like kicking the tire so to speak of just testing out this software and how it would apply to our collections from a very tech like sort of the more tech point of view but we haven't done as much of an analysis of the user the user experience I would agree thank you um Jenny do you have any comments yeah and I think it's interesting in terms of um I see myself as a user quite often and and actually what I want to use AI for is to kind of you know before the user before the end users do search and discovery there's the archivist search and discovery and that's about kind of trying to get a grip with you know moving these records from live business I'm thinking more of an archivist here that's my background from the live business systems into the something that is the archive system and I think that's quite interesting because email is quite an interesting example from this because what we're actually doing is we're kind of moving the entire live business system with it so that all of the kind of contextual information that Stephanie was talking about is kind of built into that system and we can port it through but how can we perhaps use that um you know it if if a user is interested in the same sort of thing that an archivist is interested in which is kind of understanding the workings of a company understanding how the kind of functioning of that organization has led to those records or is documented in those records then we have a kind of common purpose and we can probably use the same tools to do that so I think it's quite it's quite useful to have that kind of um renegotiation I was talking about renegotiation of boundaries and I think one of those is actually about kind of recognizing that quite often we're doing the same sort of we're interested in the same sort of thing um and we want to kind of get the same intelligence and the same insights from this data um and so I think that's quite an interesting development and it will you know it it's it's easy when it's kind of maybe well it's easy Stephanie it's not easy sorry but it's easy when it's like in an email sort of system but when you're trying to bring that sort of coherence and and that context between an email system what's going on in you know other formats in in SharePoint in whatever it becomes harder and how do you kind of gain that insight and that coherence over over the whole of it so I think it's really exciting I mean I'm really excited by some of these what's happening in some of the live business systems and the sort of things that are being created that could actually be ported through so that the user has access to them for research purposes at a later date but how what we port and how we port it that's the question for me thank you that's absolutely right Stephanie do you have anything to add yeah you asked about the availability of the data set so um I mean we're basically working here with two email data sets the first one from the first project is um a company we cannot name and is under pseudonym so we're calling it Aurora Tech and obviously all the individuals have to be anonymized I mean this data set is available on the Linguistic Data Consortium um but that's really available as a data set and I think the problem that we found is well that's great that you have a data set available if you don't know what to do with that data set as a person curious about what's in there that's very problematic plus you're not actually allowed to use it in quite the same way so um as part of the first project we created a website that's a little bit of an exhibition of these emails so that's what I posted in in the chat.com archive and we used the first prototype of the tool to kind of find our way around the emails and tell a couple of stories about the business and what they were doing and what were the things that generated all these emails but bear in mind all of this is anonymized so we anonymized all the names and we anonymized the company and we're trying to give as much context as we can and we use narrative to give the whole thing a context which is the dot-com boom and bust and use the story as as a sort of as a way of showing the organizational side of being maybe not one of the winners of the dot-com boom which is where we see the historical significance of some of these resources because all that information is in email. The second one is the Enron email data set now that's been available for years and again I mean many a researcher has downloaded it and if you don't do large-scale computational analysis it's not super user-friendly so we're really trying to design the the tool to make it more findable and we know a couple of people so Adam on our project has worked with the Enron corpus and we know other people really struggled making use in qualitative sense of those emails so I think David posted earlier that once we actually have the test environment ready which we hope to have ready in August we're happy to share that with people because we really want to see whether that makes it easier for people to use and whether it works the way we're hoping it does so data sets yeah sometimes they're there but even when they're there they're not terribly useful to researchers and that's really the problem we want to look at that's right thank you so people will be looking forward to the tool becoming available on a larger scale. Going back to the HDR project we've got the question about the sociability and how do you approach sociability with regards to archaic language or spellings is it something that you've come up against? I'll take a stab at that one as well and then perhaps throw it back to Stephanie's team because their tool actually is solving a lot of those questions in that or it seems to be addressing that when you're looking for something but you don't necessarily know the language of vocabulary used in the corpus in which you're searching. For our part our colleague that I quoted at the end of our talk Ellis we also work together to create a search guide that's at the beginning of our fur trade collection and then and we didn't do the same level of work with the Doncaster project but for the fur trade collection in particular we focused that tool on the exonyms versus the names that indigenous groups called themselves as a self-identified so that was in some ways the closest stab that we have towards archaic language because for the moment all of the indigenous groups in this collection are identified as the names that the francophone or anglophone european fur traders and merchants as they were identified by those people groups not by the language specific names that those groups use to identify themselves. So if you're searching for something you may not be using the right vocabulary as they was used in the collection. So what we did was create a search guide and pointed to other resources where you could find appropriate search terms. We also pointed out to the pretty well documented search while the search documentation provided by Cortex itself because they wrote the best manual and using their own tool so rather than pointing creating new things we used the extensive documentation that they provided as well but as this question I saw it come up in the Q&A and I was like oh as I was listening to Stephanie's talk I was like they're addressing part of this in of course a different corpus but that tool and the way that it functions is something that probably would be worth looking into for the archaic language question as well. Thank you. Thank you Jacqueline and from this I just wanted to go back to something that in a way you all spoke about but Jenny I think you powerfully made the point about the level of effort of resources of time that goes into these things and obviously it's a lot of labor that also went into the HDR project and in the email archives so I was just wondering whether people can comment a little bit about it whether there is a sweet spot of you know a good balance I suppose that the short answer is probably not but yes when is it that we feel we have perhaps reached the point in which previous efforts are feeding into future efforts and becoming a bit more effective and efficient and when is it worth doing and when not and what kind of expectations also we are setting up for ourselves our organizations and our users eventually so perhaps Janish can I start with you? Yes no that's fine yeah I mean I think it's this kind of usability arms race you know everything everything I've got in my collection is usable most well that's not true most things in my collection are usable but it may be that you have to come to queue to use them right everything is usable so it's kind of what level you're the usability so I don't know that there's a sweet spot I don't know where it is where you put your resources always a choice those choices you know exclude some include others it's tough so I think we're going to just you know that's a constant negotiation and that constant negotiation is going to be have to be ongoing I think where I kind of try to see more optimism perhaps and this is possible in this archival space is that things are now being born digital and it may be that I can you know if I can get upstream and I can solve the problem upstream so that we don't have to then expend all of this resource when they're coming through so that we don't have to do all of this conversion again and again and again we can bring things in in the right way that means that we can use them in the right way if you see what I mean so I think in some ways that's where I kind of see the hope that I mean I do think that you know there's a lot of a lot of money involved in sort of big tech and there's a lot of money involved in sort of current business systems and that's where the money is and that's where people perhaps have the resources to develop some of these techniques and to develop these kind of sense making kind of AI that allows people to kind of get a sense of their material and insights over there and if I can kind of use some of that artifact and bring them across so that I don't have to do that then they'll be available for others longer term so I think that's perhaps where I see a hope so is there a sweet spot no is there a possibility perhaps in some some kind of aspects of GLAM particularly where we're kind of moving into that you know when the stuff that we're dealing with is born digital is now born digital maybe we might be able to leverage some of that thank you Stephanie as well as your team your other colleagues have now come on video David and Shanti please chip in if you would like to share your views yeah I mean I'm sure David and Shanti have something to say on that as well but I thought the for us the key question is not just a sweet spot but also where's the responsibility right is that with the people who curate the resource is that with the people who are going to search for resource and at the moment the people who are actually going to be using the resource as in not the people managing the resource who also use it obviously they're very very different in terms of technical ability and this is really why we went with a digital curious you know people may have some idea but they're not really computing scientists and maybe in the future this is not going to be a problem because the classic training for everybody will be that they're an information management specialist in like 30 40 years from now I don't know but in the meantime it's also a question of should an archive give us these tools or should we as researchers come with that tool and I think that's this this thing about both sides of the search room we're not clear who's supposed to be doing what for whom and as Jenny said who's going to be included and excluded by these choices so I'm just seeing if David or Shanti would like to come in on that probably I could go sorry go ahead Shanti probably I could answer that to Jenny a bit this is already all these type genes they are doing this because they have got huge amounts of processing power and huge amounts of capabilities to do the kind of with the latest technologies and research kind of thing we are having we are getting these open source packages and open source resources to use for us so one of the one one such resource that is the bird timidings we have used for our search facility in order to work with so it is happening but again it depends on what the end user requires and also like it is how have you processed the how we ingest our archives in what way that depends on the what the end user wants so like I mean on this understand until we know the end user like we have to get a feedback from the end user to really do the processing at this source so probably it is a loop and it would take some time to stabilize thank you David you were about to comment yeah I just I think to underscore both this the digitally curious piece right that this is where I think it is not just a sweet spot it is a big kind of mass of opportunity and challenge in the middle here and I think it is why both were kind of excited but also a little daunted about what lies ahead and just underscore Santi's point you know when you know there is now all the all these variations on the BERT embeddings so when we started a couple years ago BERT was the state of the art and Santi was the state of the artist and now of course it is you know Robert Robert and Bertha and Roberta and all that you know so the that that kind of the if you will the kind of forefront of the technology keeps moving and and then you know does that change our capability how important is that our focus has really been on the user trying to center the user and user experience the kinds of questions that users want to ask so hopefully that by focusing on that we don't you know kind of lose the the the lead dog if you will in the technology game definitely and the issue around skills that has kept on coming up a number of sessions literally all the sessions have attended at the DC DC conference and keeping up to that Jacqueline and Caroline did you have any other comments okay the only thing that I thought of in terms of the yeah sorry the only thing I thought of in terms of going back to the question of the sweet spot of balance between the effort that you put in and the reward for the the work and where that balance is I think the only thing that comes to mind with our particular project is actually the point that Caroline made about the archival groundwork and the descriptive groundwork that was done and how that made this particular application forward compatible much less work than the initial description so we give an enormous shout out to the people who originally created the finding aid and descriptions for all that collection but that's it's a lot of work but now that collection is usable in a way that is future compatible as well so that was my only other point that there is a sweet spot the effort pays off when you take that as a clean sort of usable data set to use for future projects