Remember a hallmark card when you carry enough to send the very best. His greatest stars in outstanding stories and presents as your host one of the most distinguished actors of the American theater, Mr. Lionel Barrymore. Ladies and gentlemen, this is Lionel Barrymore. You know there's one pleasant memory which I think most all of us have in common. You know what I mean if you think back to the first time you began to read a book by Sir Walter Scott. Remember the tingling excitement which went through you as you followed the magic of his words? Well, I hope you'll feel the same thrill again tonight as we dramatize Sir Walter Scott's great narrative poem, The Lady of the Lake. It's a love story of the Scottish Highlands in the days when Henry VIII ruled England and his nephew was king of the restless land to the north. When clan fuelled with clan and scot with scot. And to play the role of the Lady of the Lake we've invited as our guest the talented and very lovely Joan Fontaine. And now here's Frank Goss from Makers of Hallmark Cards. When you want to remember your friends there is one way to be sure the card you send receives an extra welcome. Look for that identifying hallmark on the back when you select it. For words to express your feelings and designs to express your good taste let the hallmark on the back be your guide. For that hallmark tells your friends you cared enough to send the very best. Lionel Barrymore appears by arrangement with Metro-Goldwyn-Mayer producers of the Technicolor musical Because You're Mine starring Mario Lanza, Doretta Morrow and James Whitmore. And now here's the first act of The Lady of the Lake starring Joan Fontaine. Go through the rooted clan and stony past. Onward through the Scottish Highland horse and rider plunged and still the antler stag led on. Past the brig of turk over creek and crag past the hills of Benletty and beyond. Horse of bravest heart then the hunter went on alone. Until at last he stood upon an unfamiliar shore. Once more the hunter raised his arm. The hunter turned to sea. Maiden's boat came swiftly to the shore. The hunter bowed low and swept off the cap of Aaron's plume. Neither father nor friend, my lass, but a stranger to these shores. Sir, forgive me, but are you hurt? The stag escaped me and now I am without horse or harms or friends. Friends? They are near. No, lass, many leagues away faint hearts who failed me in the chase. Still you blew their horn. It was to summon them. This thought frightens you? Ah, you tremble. No, it was for aid that I called out for I have heard that Highland law will not let the wanderer to go unfed or to sleep upon the ground. That is Highland law and we are subject to it. We? My father and I. And perhaps another? The name which you called out, Malcolm Graham? Which is but a name. I and which brings color to your cheeks even now. But one name must lead to another and so I hope to yours. There is another Highland law, sir, that strangest shall be strangest to each other until bread is broken. For if there are no names, they must eat his friends and part his friends. May we be there always. And now take me where you will, my lady of the lake. You look about the hall. I to seek an answer to this riddle. A dwelling so large, so strongly built so far from all others. An island refuge in an unknown lake. My father planned it so. Your father? Is he Rudrick do? No. And yet on this wall hangs Rudrick's broadsword. I saw it flash in many a battle, a sword so great that none other can wield it. Lass, what have you to do with Rudrick, the outlaw? First, sir, I must have your name. I, since I have eaten and Highland law is satisfied, James fits James, Knight of Snowden, a wanderer without castle or lady to grace it. And you? Ellen, daughter to James, Lord Douglas. So the riddle is ended. This dwelling is Rudrick's and within me a father seeks refuge. He is uncle to that Douglas who sought to do King James harm. Now the King would have sworn vengeance on all our clan. Ellen. Father. Hold not back, your lordship, I am but a wayfarer and unarmed. Then I bid you welcome, sir, the courtesy of this house. The broadsword. The sign, the sign. Why do you stand back? It is the Highland warning, my child. Rudrick Dew's blade falls between us. There must be bloodshed. I, and even now, Rudrick comes. Farewell, sweet Ellen. Sir James, serve him. She was our guest. Ellen. Oh, hear me, father. He has done no harm. As he will, Rudrick Dew's blade promises it. Quickly, child, what name did he give? James Fitz-James, a poor knight who lost his way. Oh, found it to our hiding place and goes now to King James. A spy? No. I will not believe it. Believe as you will. But speak to no one of this. Rudrick comes. Listen, great booty. All Glen Lass is burnt to ashes, and the men of Loch Lomond lie as dead as the stones upon their shores. Then the raid is ended. Victory. My men fell on them while they slept, and those who escaped will carry the news to King James. Beware of coward cringes and sterling castles and leave the halons to those who are men. Rudrick. Ah, Ellen. Even in victory, there must be losses, with a few or many. Oh, look yonder lass, the men seem few. I cannot find Malcolm Graham. Malcolm Graham. Oh, he is new with your band. Tall with golden hair and wide blue eyes. It seems you know him too well. Lad Douglas there, Rudrick. You mis-take her meaning. Malcolm is a lad who befriended me once. We owe him much. And so, Ellen's question. It is well that this all. And now, fair Ellen, what shall I tell you? That Malcolm is alive, and that he is unhurt. He is, and now stands guard with my boats in the cove. Oh, thank you, Rudrick. I think, have you so soon forgotten the sound of my voice? Ellen. Every hour away from you, I heard it again in the call of the Delph. I, and saw once more the deepness of your eyes in the blue of Loch Lomond. And now the blue of Loch Lomond is stained red with the blood of the dying. I, Rudrick, you waters a heather of Scotland with the blood of his enemies. When must it end? Highland against Lowland, clan against clan. Chieftain against chieftain. When will there be peace in Scotland united? Ellen, this is strange, though. Oh, I thought much, my dear. In the night sometimes my mind turned straighter to our clan. I've even wished that King James might bring us peace. Ellen. Oh, can you not see, Malcolm? Each time I bid you farewell, it may be forever. It's both love in my heart and fear. Then let me make it love alone, my darling. We waited long, too long. I'll go to your father and ask for your hand. And what dowry would I bring you? Save the curse of the Douglas, the outlawed clan. With me you would strife in the wrath of the King. Ellen, Ellen of Douglas. Frederick, come here. Bye, until later. God, have you seen all of the Douglas lies?  Oh, Ellen, all my sentries were so fair. They truly sentry are to my heart. Frederick. Come, lass, there's no time for shyness. I've won a victory. And now I wish another. Still it's custom to speak to a maid's father. Aye, Lord Douglas is her name. And she's answer? Is that you must answer it, your name. Sir, you make it hard. By father, Fred King James, save Haven. Aye, and with the word, his Haven ends. By your answer, I'll know your gratitude. No more, please. Love comes not by threat. If you refuse me. Aye, for my heart is already given. And I know where. You fled the camp and victory feast. You wander the shore to be with him that I set guard. Sentry, welcome, Graham. Aye, sir, welcome. Yes, sir, nun, your death. Frederick. What comes from your friends? What comes and speaking, man? King James and his army. They march from Sterling Castle. And not even now in the mountain pass. At last. Then to our welcome. Light the war fires and solve the master. Oh, your life I feared for because of war. And now there is added victory. Frederick's wrath will come again. And in battle he may find a way. Oh, my beloved, quickly escape while there's time. And in my life I'll find a way. Oh, my beloved, quickly escape while there's time. And in my prayers I'll ask for this Scotlanded peace and Malcolm mine. Turn to the second act of the Lady of the Lake, starring Joan Fontaine. Colors, artistic designs, a style of printing that's smart and easy to read. All of these things are important, of course. For together they express your personality just as much as the books you read or the plays and concerts you attend. Now, one sure way to find a card that's a tribute to your own good taste is to choose your Christmas card from the new Hallmark albums. You'll find that this year the collection is bigger and more beautiful than ever before. If you prefer the works of famous painters, the cards in the Hallmark Gallery Artists series will be ideal for you. And before you decide, you'll want to browse through the modern and traditional and religious Christmas cards too, all carefully crafted in the fine manner of Hallmark cards. So why delay? By ordering your cards from the Hallmark albums tomorrow, you can have them in plenty of time for addressing at your leisure. And remember, that Hallmark on the back of every card you mail tells your friends you cared enough to send the very best. Now back to Lionel Barrymore on the second act of the Lady of the Lake, starring Joan Fontaine. He's done every peek for Roderick Dumas with bagpipe screaming. But still, there was peace in one highland retreat. Ellen of Douglas wandered the island and sat down with her thoughts by a wooden shore. Then in the sound she rose in fright. Who goes there? Father? Be quiet, lass. He's out of hearing. Oh, such insidious, James. Aye. And if there's danger, it's mine, not yours. Sir, what brings you here again? Is it to spy once more and then back to King James? You'll be glad for the news that my father is unguarded. A helpless Douglas before a vengeful king. If he be helpless, then no more than I. Helpless before a highland maid. Well, believe me, Farrell, and I come again with no wish to spy nor intent to harm, but to give you my heart and bear you away. Then I am sorry. I wait for another. You know his name. You heard me call it. Aye, Malcolm Grimm. Aye, Malcolm Grimm. I feared it might be so, and yet I had to prove it. But if you're Malcolm in battle or by some misfortune... No, I'm prepared for it. Even now he stands between two enemies. King James Army and Roderick's Envy. If he dies, my heart dies with him. Then such a love must surely triumph. I wish you well and Malcolm's safety. Wait! Roderick's men fill these mountains. Your escape must be through a secret path. I came that way and will find it again. But since you wish me kindness, take this in payment. Wear this always on your finger. Whose ring is this? Once in battle I saved the king and ingratitude James gave it to me. He vowed to grant whatever I asked in the name of this golden token. Keep it, Ellen, or it may be that you will have need of it. And now farewell. The king's own ring on his beltless hand. It is in a dream. Aye, my only happiness is no in dreams. Aye, my only happiness is no in dreams. Aye, my only happiness is no in dreams. To sleep and dream is with me still. If it be the future, then his blood is on my head, not Roderick. Oh, it's not true. And I say it is. Roderick need not kill Malcolm. The fortunes of battle may accomplish that. The battle whose cause is myself. I am the prize that King James seeks. The hunted lord of a hated clan. But if I surrender... No! That's the clod's way. The brave man's. One captive just sterling castle and the island's free of strife. One life and ransom for a thousand. No, no! It was but a thought. Dream in sleep and I awake. There come no more fears. Back to your pillow while I stand guard. Goes by the secret valley, friend or foe. Let him pass. Answer I say. Castle! Then you go as a ghost. My hope to drag me but... I'll bind you up and you'll still live. But who came here? Did you pass another? My father saw him I. But she, not me. In the secret pass, he cannot do a place of his death. Answer from the night and wind. Made Douglas to sterling castle. And the king. All coming is no surprise, Made Ellen. And now command me as you with. Then this ring. Your gift to me. I would present it to the king. This command. Send your prisoners to the appointed place. I saw you and I worried you.  It was no dream. Then the battle has ended. Fight on Highland losers. But you once fed and would not wed. It was between one who gave me life and one who is now my life. Tell you must. Douglas, who now swears allegiance to my name or Malcolm, who swears allegiance to yours. Which shall live? Oh, Malcolm. Now, forgive me and stand my choice. If my father dies, the Highlands rise again and rather than there is war, but now he lives and Scotland is invited. For that night, dearest, I gladly die. Oh, and be brave, Malcolm. Grief death happily. For I meet it with you. Scotland greater than the kings. And your sacrifice of this lad shames my generosity. He is free. But when in some near day I'm Malcolm's bride, perhaps to the Highlands again you'll come. Not as a hunter without horse, not as a gallant-seeking love, but as Lord of all peaceful Scotland and throughout our glens. 97, a puzzled little girl named Virginia O'Henlon wrote a letter to the editor of the New York Sun. In it she asked, please tell me the truth, is there a Santa Claus? The editor's reply has become a classic. He said, in essence, yes, Virginia, there is a Santa Claus. He exists as certainly as love and generosity and devotion exist. And you know that they have bound and give to your life its highest beauty and joy. Today, as we approach the Christmas season, those words again take on their full meaning. The wonderful spirit of Santa Claus returns to the hearts of each of us and we are eager to honor our friends and loved ones wherever they may be. And this is such an easy and pleasant gesture thanks to hallmark cards. They are the symbols of friendship and they carry your greetings the length and breadth of the land. And here's something you might like to know, while the quality of hallmark cards is being constantly improved, you'll find the prices remain the same. This year, as always, that hallmark on the back of every card you mail tells your friends you cared enough to send the very best. Here again is Lionel Barrymore.   Thank you. Thank you. And thank you, Mr. Barrymore, for that pretty compliment. And of course I always enjoy a visit to hallmark playhouse. Tell me now, are you going to be able to stay with us a while? Or will you be off on another traveling joint right away? Well, not right away, until after a certain date next week. A certain date next week? Oh, that sounds to me like it could be a birthday. Who's is it? Yours or your daughter's? As a matter of fact, it's mine. But their birthdays are pretty soon too. They're early in November. Well, now, it sounds like your family will be getting lots of hallmark birthday cards very soon. And I'm sure each one will make you happy. You know, Mr. Barrymore, that's the truth. It's something I've noticed about hallmark cards. You may get many different kinds, some sweet, some humorous, but each one seems to make you happy in its own way. It's like seeing a lot of your friends all at once. But tell me, Mr. Barrymore, what are your plans for next week on hallmark playhouse? Well, next week we'll present the story of some famous American naval heroes and of the man under whom they served, Commodore Pribble. When we dramatize Pribble's Boys by Fletcher Pratt and to start in it we'll have McDonald's Carry. Our hallmark playhouse is every Sunday. Our producer and director is William Gay. Our music is composed and conducted by David Rose and our story tonight was adapted by Leonard Sinclair. Until the next Sunday then, this is Lionel Barrymore saying goodnight. Hallmark cards present two great programs for the whole family's enjoyment. On radio the hallmark playhouse with host Lionel Barrymore and on television outstanding dramatic entertainment on the hallmark television theater. Consult your paper for time and station. If you find a symbol of the Liberty Bell hanging on your front door one day soon you'll know it was put there by a good American reminding you to be a good American. It's the Boy Scouts of America reminding all America to vote as you think and to think when you vote on November 4th. This is Frank Goss saying goodnight to you all until next week at the same time. When Hallmark Playhouse returns to present McDonald's Carry in Fletcher Platt's Pebbles Boys and the week following Daniel Webster starring Lionel Barrymore and the week after that Herman Peterson's The Covered Bridge on the Hallmark Playhouse. This is the CBS Radio Network. This is KMVC, Kansas City, Missouri.


More than European leaders posed for family photo in Moldova on June 1 at a European Political Community Summit in a show of support for the former Soviet Republic that applied to join the European Union after Russia invaded Ukraine in February 2022. The gathering of the EU's 27 member states and 20 other European countries at a castle deep in Moldovan wine country just 20 kilometers from Ukrainian territory poses a security and organizational challenge for a country of 2.5 million people wedged between Ukraine and NATO member state Romania. Ukrainian President Volodymyr Zelensky was seen speaking on the sidelines to Kosovo President Josa Osmani and Serbian President Aleksandar Vuchic as Pristina and Belgrade accuse each other of fueling tensions in Kosovo.


Hi and welcome to the session. Let us discuss the following question which says, find the degree measure of the angle subtended at the center of a circle of radius 100 centimeter by an arc of length 22 centimeter. Start with the solution and we are given a circle of radius 100 centimeter and length of the arc is equal to 22 centimeter and we are required to find the degree measure of the angle subtended at the center. So we are given a circle with radius 100 centimeter and arc of the circle is 22 centimeter and we are required to find the angle. Let this angle be denoted by theta. Now length of the arc is equal to 2 pi r into theta upon 360 where r is the radius of the circle. Now length of the arc is equal to 22 centimeter and we have 2 into pi radius of the circle is 100 into theta we have to find out upon 360. So theta is equal to on cross multiplying 22 into 360. Upon 2 pi into 100 now pi is equal to 22 upon 7 so we have 22 into 360 upon 2 into 22 into 100 into 7. Now 2 into 180 is a 360 0 cancels out with 0 22 by 22 then we have 18 into 7 upon 10. Now again 2 is the common factor in the numerator and denominator so 2 pi is the 10, 2 nines are 18. So we have 63 upon 5 degrees. So this is 12 10 3 upon 5 degree and next form which is equal to 12 plus 3 upon 5 into 60 minutes and this is a degree since 1 degree is equal to 60 minutes and in solving we have 12 degrees plus 5 12s is 60 and 12 into 3 is 36 minutes which is equal to 12 degrees and 36 minutes and therefore it is subtended at the same term is equal to 12 degrees and 36 minutes. So this completes the solution hope you enjoyed it take care and have a good day.


So, I'm going to go ahead and slowly get started. Number one, I want to welcome everyone to this webinar. Welcome to our NHR members and the AFR colleagues. Before we begin, I would like to acknowledge that this webinar is being moderated on the traditional lands of the Mikasuki and Seminole people and their ancestors and I pay my respects to elders both past and present. I will start again by saying welcome my name is Robin Bauer Kilgo and I'm the co-chair of the NHR working group. I want to welcome both our NHR members and our AFR colleagues and today's webinar is part of a quarterly meetup that we have started scheduling with NHR members and when this topic was introduced to us. We wanted to make sure to extend the invitation over to the AFR folks as well, just because we thought it was going to be useful. So we obviously work with Elena that you can see hopefully on the screen, who is our contact up at AIC and FAIC. She's going to be running the Q&A portion at the conclusion of this webinar. And this webinar today is going to be all about Georgia's natural cultural and historical organizations disaster planning process and how a directory was created on how to reuse for people to basically contact each other when it comes to emergencies and disaster response. Our speakers today are Christine Wiseman she is head of digital services at the Atlanta University Center Robert W. Woodruff Library. She's a founding member of the Atlanta Area Heritage Emergency Response Network and a member of NHR. And Cliff Landis is the digital initiatives librarian at the Atlanta University Center Robert W. Woodruff Library. His research interests include linked open data, arrival technologies, digitization, metadata, and the co-evolution of humanity and technology. This webinar is going to be about 45 minutes long and then we will have a Q&A period at the end. So I'm going to go ahead and turn off my camera and my mic and hand controls over to Cliff and Christine. And if anyone has any issues with the tech, please go ahead and put it in the chat box. And if you have a question during the presentation, please put it in the Q&A box and we will keep track of both as we go along. So we'll see you at the end of the presentation and thanks. Thanks Robin and Elena. We really appreciate the invitation to come and talk to you today. Good afternoon everyone. I'm Cliff Landis. Hey everyone, it's great to be here. Thanks to AIC and AFR and I am Christine Wiseman. Together we're going to be presenting on a project we've been working on for the past couple of years called GANCH. Rhymes with Ranch. So to briefly introduce the project design, the goal of this one-year project was to create a publicly editable directory of Georgia's natural, cultural, and historical organizations in WikiData, allowing for quick retrieval of location and contact information for disaster response available via a website. And as Robin said, Cliff and I are both with the Atlanta University Center, Robert W. Woodruff Library that we're both working respectively from our homes at the moment. I am Assistant Director of Digital Services and we are the lead organization for this project. Our library is a consortium library so we like consortial projects. We serve four institutions, HBCUs all located in Atlanta, Clark Atlanta University, the Interdenominational Theological Center, Morehouse College, and Spelling College. And I'd like to say a huge thank you to Lyrasys for funding this project through a Lyrasys Catalyst Grant. The Lyrasys grant funded several positions or a position for our graduates as Assistant Allison Smith pictured here on the slide, and also our web developer Matthew Stevens. Additional team members Jessica Lemming and Alex Dade from our Digital Services Department chipped in on the project as well. We couldn't have done this without our partners, we had partner organizations throughout Georgia and the Southeast both both professional organizations and governmental. Some of our partners provided assistance to provide assistance to NCH organizations impacted by disasters, including Hera and Cher. We also provided membership lists, help without reach, and are helping with sustainability of the project. So before Cliff presents on the technical aspects of the project and the workflow I'd like to provide some context about cultural heritage disaster planning in our state. In Georgia we are modeled after the federal planning structure, and we are organized into 14 emergency support functions or ESFs. National or natural excuse me natural cultural and historic organizations or NCH organizations are located under ESF 11, which is coordinated by the Department of Agriculture and the Department of Natural Resources. Under these primary agencies, there are support agencies and you can see in the tiny script there that provides support functions under the state plan. And you can see that the Georgia Archives, the Georgia Historical Society, the Heritage Emergency Response Alliance, and Savannah Heritage Emergency Response are all included in the plan. This was added as of 2015, which at the time was a huge accomplishment that we got introduced into the plan. Since then we've worked really hard to cultivate relationships within the primary and the support agencies within the ESF 11 because of course in a disaster they have many other responsibilities to deal with. We have a particularly good relationship with the lead planner from the Department of Agriculture, Vanessa Sims. She has really taken a strong interest in NCH organizations has really helped to raise our profile within the state planning ecosystem. So now I'm going to talk a little bit about our AFR networks in Georgia. HERA is the Heritage Emergency Response Alliance we were established in 2007 after the AFR forum that was held in Atlanta, right after Katrina. I happen to be one of the founding members of HERA and the current co-chair along with Tina Situ who may be on this I'm not sure. And our members are, we have individuals, we have conservators, preservation professionals, librarians, curators, archivists, and first responders. Generally we have a little over 100 members on our listserv and our network has really grown from an Atlanta area network to really having members from around the state. We have a steering committee and a directory of members that we call on and we can deploy when needed to aid other institutions. Of course our primary purpose is to help other cultural organizations if they're impacted by disaster and to that end we have participated in statewide drills and exercises along with GMA Homeland Security. We have educational programs, webinars like this. We try to do a webinar at least every once a year, usually around May and the spring. Or and we've had you know course in person training as well. Over the past few years we've really evolved into working with the state to coordinate response and recovery statewide through ESF 11. Share is our sister organization in Savannah. Share was formed in 2010 after another AFR forum. Share has institutional members. They cover just one county. HERA is like, depending on how you count it, we have like 15 counties in Metro Atlanta. Share's members include museums, archives, libraries, cultural historic sites, art galleries, parks, houses of worship and first responders and emergency managers. One of Share's great accomplishments recently was they actually worked with Chatham County Emergency Management to map 80 cultural heritage institutions into their web EOC as critical facilities. And that kind of in a way led to this project that we're talking about today. So two other initiatives I wanted to bring up that many of you probably have already heard about, but we have two other initiatives underway of course the GANCH project, which is what we're going to talk about today. And also we're working with AIC to the Georgia Heritage Responders Training Program. So that's been coordinated by AIC and Elena as part of an NEH grant. The goal is to train a statewide response team similar to the, you know, NHR teams. This project is in the process of training 40 people from around the state with a combination of online instruction, culminated by a two-day hands-on training session in Savannah. That was supposed to be in April, but of course it had to be postponed due to the pandemic. We're hoping to have that in fall. In the meantime, we've held meet and greets, and we are planning some virtual tabletop exercises next month. So why do we need this tool? So, and all of these projects and initiatives around the state would really benefit by having some sort of statewide database of all of the universe of cultural heritage organizations. Natural disasters are impacting our state in an alarming rate. In the past few years, we've dealt with flooding, rainfall, tornadoes, multiple hurricanes and tropical storms. And of course, as all of you know, 2020 was the most active hurricane season on record with 30 named storms. Georgia is one of the, is the largest geographic state, east of the Mississippi with 159 counties. We have extensive and diverse natural and cultural historic sites that preserve and document the unique history of our state. So it'd be a great benefit to have a comprehensive list of institutions for disaster purposes. Now we have that. So we started out this project in 2019 and at that point we were contacted by FEMA. As they were preparing for Hurricane Dorian and they asked us to share what coordinates that we had at that time for institutions and we really mainly, as you can see from this map, we mainly had the coordinates of institutions from Savannah. So even before the project right in the beginning of the project, before we really got started there was already a need for this and some of the data was already being used. So in the past, how would we find these organizations well we would basically look for directory information and it's out there but it's scattered into different data sets, none of which are publicly editable. So we did a video coded or particularly up to date. So we started with the Georgia historic historical records advisory councils, historic and cultural organizations directly which would have been around for at least a decade, but really was had become fairly out of date. And the Georgia historical societies directory of affiliate organizations, and the Georgia Association of museums and galleries directory. And the list of Georgia public libraries, and several other directories which we eventually estimated at over 1500 organizational records combined. So there'd be some overlap among these directories but we really didn't know how much until we got more into the into the project. So as Christine was saying we had all these data sets, but we really needed a place to combine them all and to deduplicate them because we knew that there would be some duplicates across the databases. So we've mentioned a little bit about linked open data and wiki data several times so in case you're not already familiar with these terms. Let me give you a brief explanation of what linked open data and wiki data actually are. So linked open data is a way of publishing machine readable facts online, linking them together, and then giving them an open license for all of the data, allowing for access and reuse, hence the term open in linked open data. You'll also sometimes hear linked data, and without that open in the middle of it, it can often refer to closed and proprietary databases, like something at Google or Facebook. So wiki data is a free and open knowledge graph that acts as a central storage place for the structured data of wikimedia sister projects like Wikipedia. So basically it's a big database of facts with the ability to link those facts together. And this was actually a perfect fit for the in CH organizations directory and location information that we wanted to gather and map for Georgia. So when designing the project and writing the grant proposal, we focused on several principles. So wiki data provides a flexible structure to represent many relationships and repeatable fields, so that records are easily enhanced with additional data. Facts in wiki data can be done manually by anyone, allowing for decentralized updates. So there's no need for an institution or individual owner to grant access to the data for regular updates, thus removing bottlenecks to keeping the information up to date. The data represented in wiki data are provided with an open license, as I said, so to honor this we didn't reuse any copy writeable content from any of our source data sets, things like collection descriptions. Reference links were included for each statement providing sourced information for verification, and this also helps to provide a direction for future updates. So we completed using free software guaranteeing broad access and free implementation. And we made an effort to provide a model for other states by documenting and presenting on all the processes that we used. We also wanted to design the project to provide a graduate assistant paid internship to give an up and coming information professional practical experience working with link open data, and we're very lucky to have Allison join the team. So now I'll go over how we went from the design principles to the actual workflow for collecting verifying and uploading the data. And to give you a little backstory, the idea for this project actually started in 2018 when I attended the Georgia Archives Institute. GAI is an annual two week crash course and archival practice. And since I was trained as librarian, I had lots of gaps in my knowledge of archives so I really wanted to attend. So after I was able to attend and meeting so many cool archivists there. I wanted to see a map of all of the archives in Georgia, but after looking around I realized that there wasn't anything available out there. So I started looking for directories of cultural heritage organizations in Georgia, and I came across that crack historical and cultural organizations directory that Christine had mentioned before. And I had the latest web scrape of that data in that directory and I cleaned it up and then enhanced it with geocoordinates and county information. And then I uploaded it to wiki data. So when I mentioned this test upload to Christine she explained that she had already worked on that same directory, while she worked at the Georgia Archives, and that the data set really needed to be brought up to date and so she suggested that we apply for a grant and here we are. We had the in place we had to choose what kind of metadata elements we wanted to include and how to rank them in terms of priority. So required metadata elements included the organization's name and any aliases that it had a brief description of the organization and what type of organization it was like a library archive State Park Historical Society etc. We also required the street address city counties state country and geographic coordinate location information. If the organization no longer existed we also required the record of the date the organization dissolve so that we could exclude it from our search results and that way, you know, even though we're putting it into wiki data we're saying that's closed so that we can say you don't need to look for this organization in a disaster. We tried to capture contact information like phone number website and some sort of generic organizational email address. And when we had time we also gathered the start and end dates for the organization, any organizational relationships like if it's an academic library that houses a distinct archives we tried to describe those separately and then describe the relationship between them. We also gathered Facebook ID and Twitter username when they were available is these are often used during disasters to describe the status of an organization and its collections, and to be perfectly clear. Not all of the organizations had all of these fields available. So for example, many historical societies that are smaller and little counties like my home county of Lowndes County. And they don't necessarily have a physical location because in a lot of times, they're run by volunteer organizations with maybe only a PO box and a phone number. So we did the best that we could with the information that we had. Also during our focus group sessions with heritage emergency responders. There were requests for some meta metadata elements that we just couldn't accommodate. We ended up out of scope for this project, and they're out of scope either because the information doesn't fit into wiki data like collection descriptions, or because the information is private like cell phone numbers for organization administrators, or because it was a security risk like hazardous materials or formats. When we first started planning the project, we searched for all of the glam organizations in Georgia that had coordinate location information recorded in wiki data, which only pulled up 40 organizations. Now look at that map of Georgia very closely and look at the next slide in comparison. At that time if you search by glance in the United States you got even more results in Georgia. And this has to do with a little bit of the messiness around how information was tagged in wiki data. And that was the type of data that we were planning on updating and cleaning up to make uniform across the state. So we also did this project to find smaller hidden institutions, such as the Georgia rural telephone museum located in Leslie Georgia. Even though there is an entry for this museum in Wikipedia, we didn't have the information in any of our partners data sets. So one of the more rewarding parts of this project was discovering and including these lesser known institutions, and adding them to the data set for disaster relief. So as you can see from this map, we made quite a lot of progress over the course of the grant. So we widen our search out beyond just glam institutions to try and get as many relevant NCH organizations as possible. So as of November 11 in 2020, our big search for the entire state returns over 1900 institutions, and I checked it this morning and I think it now returns over 2100 institutions, as well as individual things like statues, you know famous public statues and stuff. The search includes things like historic districts that don't necessarily have contact information so that emergency responders can cast as wide a net as possible when doing helicopter flyovers following following a disaster. And beyond the maps we also make the data available in table format, as will show being able to export the contact information and table format helps emergency responders reach out to these NCH organizations to see if they need the data before and after disaster strikes. So the free software that we used for the project includes open refine GitHub and Visual Studio code. We chose to use Visual Studio code to save and manage the data and CSV spreadsheet tables. Since Microsoft Excel tends to force formatting particularly around dates, which VS code does not so it made things a little bit easier. So we started the process by scraping websites, gathering lists from our partners and creating spreadsheets of these NCH organizations. We then used free website tools like geo code and things like that, in order to enrich the organizational data with additional metadata like coordinate location and county. We loaded each spreadsheet into open refine and began matching up the organizations to their records in wiki data if those records already existed. Then we reconciled our fields against wiki data schema inside of open refine. So we have our data dictionary available on our GitHub site if you're curious about how we mapped the spreadsheets to wiki data schema. And next we created references for each link data triple. So for every single fact, which is sometimes called a triple, since it's a subject object and predicate. So for every single fact that we uploaded to wiki data we supplied three values the fact itself, the reference URL and the retrieval date. So by citing our sources with snapshots and timestamps, we're giving folks in the future the ability to trace and update each fact as things change over time. So this allows us to track organizations that have dissolved like I mentioned before which allows us to exclude them from our search results. We captured the reference link using Internet archives way back machine to unique fact to unique things happened when we captured this information over the course of a year. The sites went down after we captured the information. And then we also captured a lot of COVID-19 information while we were processing through these sites. So by using Internet archives way back machine to take snapshots of web pages where we found each fact, we're able to basically show evidence of our claims in wiki data. And then the last part is that we uploaded the information to wiki data, and we did so using open refine. So this slide shows the Aragon Historical Society, which we added as part of our testing phase. So after the data is uploaded to wiki data we perform quality control on each entry to verify that things are correct, and especially the coordinate location information which can be a little bit tricky. Sometimes getting that coordinate location data is hard because, you know, sometimes listed as being like at a crossroads or it might just be in the center of a property rather listing the actual location of the cultural heritage materials. So we did our best to try and put the marker right on top of the building, because after disaster street signs and other way finding markers are often damaged and destroyed so we tried to get as close to the actual object itself as we could. So a little bit about the website outreach and sustainability. So we knocked up our website for testing and feedback to ensure that it met with emergency responders needs. Here you can see our initial homepage wireframe and mock flow. Now wiki data can occasionally run slowly or be temporarily unavailable. So to prevent any outages during a disaster, our web developer Matthew Stevens designed the site to actually store the query results locally in the website. So the queries are refreshed nightly to keep the information on the website up to date with any changes that happened in Wikipedia overnight. So we have three main query types, Georgia as a whole individual Georgia counties and the eight GEMA regions that the Georgia emergency management and Homeland Security Agency uses to divide the state. The result page displays both a map and a table of the directory information for the NCH organizations in that area. Here you can see the results for GEMA region one, which combined several counties. So we recognize that the website may be used on mobile devices after disaster as cultural heritage first responders will probably be on the field. So I tried to make sure to give the website a responsive design with my particularly favorite feature a table that converts from single cell format on that converts over to single cell format on mobile devices to prevent users from having to scroll left and right on the table if they're not on a desktop device. We also provide users with instructions on how to export the tabular data directly from wiki data to a CSV file, and that way it can be imported into other systems like web EOC the emergency operation command software. So we're getting a lot of help from our partner organizations to get the word out about the project, not only the member institutions but not only to their member institutions but also more broadly to similar organizations and other states. So we emphasize that the partner organizations are the foundation of this entire project. They're the ones who will both be doing the disaster response and getting the help to their member institutions so that they're. So they are both the partners and the stakeholders in the making in making sure that this project is functional and sustainable without them, this project just would not exist. Now that we're at the end of the grant. We've worked with our state level partner organizations to begin the handoff for long term maintenance and sustainability. Sarah, Sharon Jima have integrated the final project into their disaster response workflows Galileo our statewide virtual library is graciously hosting the actual website and Galileo and the Georgia Public Library Services Archival Services and digital initiatives office, which is our statewide digital initiative will perform the annual updates and so we built an e-mailer into the website so that folks at Galileo and GPLS can send out reminder emails once a year to any NCH organizations whose emails we have. And this way we can request any updates to their contact information. If information has changed the edits can be can be made directly in wiki data, but if we send out these annual reminder notices and the email bounces back. That allows us to look at the organization to see if it's already dissolves. We created a self submission form on the website so that organizations can let us know if their directory information has changed. This is also very helpful to identify new NCH organizations that arise over time. So if you're from Georgia and you see the organization is missing from any of our source data sets. Just let us know via the form and we'll make sure to make, we'll make sure that your organization is included in wiki data. I think we got everybody but you never know. And also to make sure that everything associated with the project is free transparent, adaptable and reproducible. We created to GitHub repositories, which include everything associated with the project. An example of this is our workflow manual shown here, which basically walks you step by step through the entire process that we developed. And with that I'll pass it back over to Christine. Oh, thanks, Cliff. I was reading the questions. Shouldn't do that. Thank you, Cliff. I'm going to talk now about things to consider if you decide to undertake a similar project in your state, and also some things that we learned and some additional uses for the data set and the impact of the project. So things to consider. We came up we discovered that there's a lot of duplicates and name variations probably not too surprising. Some organizations change their names or have aliases that create duplicates. So pay close attention to the names and sometimes do a deeper dive into the history of an organization. As we discovered name variations we recorded them in the key data. We also found that due to the sum of the data sets being outdated many organizations were no longer in existence. The process to verify dissolved organizations to determine the dates included reaching out to the context looking at newspaper articles looking at trip advisor and the Georgia registry. These are some of the most aware of organizations that might have been started in your state so the organizations that began in Georgia that have since relocated, and then there's national organizations whose main offices might be in your state. We still captured these records. So let's look out for expired domains. These are domains that may have expired and been purchased by another organization. Be careful because we found that in some cases these domains were purchased by organizations designed for explicit adult content. That we don't want in our database. What we discovered was the challenge of trying to map real world messiness to the much cleaner data model of wiki data. This challenge this challenge was not only trying to map map it but also trying to reach consensus with the wiki data community on how this should be handled. So what we mean by this is municipalities include towns villages and cities. The P 131 field in wiki data is the field for administrative territorial entities. This field is broad and can cover municipalities counties and states. Remember wiki data is an international tool. So in the documentation for P 131 it recommends that you only list the single most local administrative entity since the field is supposed to be both transitive and hierarchical and cascade upwards like you see on the left of the slide. In Georgia, the borders of municipalities and counties were drawn independently and about 10% of municipalities in Georgia are in more than one county. So they aren't transitive. This means that for our project we can't rely on wiki data is cascading hierarchy to be correct when it comes to searching for organizations by county. We reached out to the community or cliff did I should say to try to find a solution to this challenge but after several proposals and lots of discussion no consensus was reached. So for this project we explicitly decided that municipality county and state we're all in the P 131 field with the hopes that consensus on a solution can be reached in the future. And we figured it's better to have too much information than too little. Another thing we came across as we were reminded in the course of this project that Georgia has a rich but sometimes uncomfortable history. Georgia was the 13th colony and was also part of the Confederacy. The most challenging history is reflected in organizations and their records about the Confederacy slavery Jim Crow civil rights, sacred lands, etc. They're all part of our state's history. These, their organizations in Georgia that celebrate those that defended the practice of slavery, and there are also organizations who celebrate those that sought to abolish it. The project was completed at the same time that the protests were taking place against systemic police violence and racism. Yet no matter how we personally feel about parts of our history, we endeavor to record it all fairly and equally. No record should be erased because we're uncomfortable. And in fact our discomfort should push us into further discourse about what this, what these records and organizations mean to the state then and now. If you're interested in learning more about Georgia's history. This database has can be used for tourism. So you can run a query for places to visit based on city county or region. This image here shows glam institutions in to cap county where where I live in clip lives. The use we stumbled upon was related to visitor counts to public libraries in the state. Since the annual visitor counts from 2015 through 2017 for all of the library systems were already in wiki data we are able to get a little help from the community to graph those counts in another query. Here they are displayed as a line graph. It's a little hard to see because it's small. Type in this URL to see it in action for yourself. And to us it's interesting to have this information out there and readily accessible with no barriers to update enhance and enrich the data. So really any publicly available and verifiable fact can be added to wiki data so feel free to explore. So looking back at this project we feel like we accomplished a lot. We have over like 1900 cliff said what 2100 organizations now in the database and a single location. The website for emergency responders to identify organizations in affected areas. We developed this project to be open source and reusable, and we have a plan for sustainability so the data and the website continue to be useful over time. So we had our first in the field test this year in September with the landfall of hurricane Sally. In anticipation of heavy rainfall and flooding members of Harris sent out emails to 330 organizations that we pulled from the database from Gima regions 1347. Unfortunately, none of the emailed organizations requested assistance or had damage following the storms, but here I did receive thanks for reaching out. We didn't get a 9% bounce rate where emails cannot be delivered which actually isn't is pretty good considering we didn't test the emails before the project. We did discover though that not all organizations have email addresses on their website. So now we know that we're not reaching everyone in these areas, but it is a good way to at least get the word out and quickly that emergency assistance is available. We're also through outreach efforts. We're hoping that institutions at least give us one emergency email. But we found that a lot of institutions have taken emails off their website and they have those forms instead. And for more cute disasters like a tornado emergency responders can reach out to organizations on a county by county basis, using the table of all available contact methods and this includes email the phone number Facebook, Twitter handles and website forms. So we are following up with the organizations whose emails bounce to see if they're still active, and to see if they can provide an up to date email address for emergency purposes. The timing around when to send these emails can be tricky due to how quickly and dramatically weather forecasts can change. This is a timeline that Tina see to and I developed as part of our documentation. So it turned out hurricane Sally ended up not to be as damaging to Georgia as predicted, then a few weeks later another storm and I think it was delta was initially predicted to just be have minor impacts in Georgia but then it quickly increased in severity and we actually had widespread power outages in North Georgia tornadoes and lots of trees down. We ended up not sending emails out in advance of that storm. And then we developed this we updated this timeline so it really is a judgment call to balance between when you're sending out too many emails to where folks stop paying attention versus not enough. So we do have this timeline and generally, we start monitoring the storms very closely when it's five days from landfall, and then we begin to send. We usually send the email blast out to targeted areas about three days before the storm hits. We have we have developed canned email templates. So it's pretty quick to pull the information out of the database. You have to do a little bit of massaging of the data. And then we can update the emails and send them out from we send them out from the Hera Gmail account. So it's a work in progress but having the databases a critical part of this response. So I know that we covered a lot today, but I'm very happy to say that in the end, I got my wish that the initial idea was created from so here you can see a map of all of the archives in Georgia. And a link to this map available at the bottom of the slide. As I said before, you know, if you know of any organizations in Georgia that we missed. You can either fill out the self submission form on the Gantt website, or even go to wiki data and add it in yourself. And with that, I think we moved a little quickly. And so we'd like to thank you all for your time and attention today and we are happy to start taking questions. I'm going to pull up the questions here. Okay, so our first question is from Tara Kennedy, and it is how much cooperation did you need to get from the SF 11 slash female leadership in order to accomplish this project. I can take that one clip. Thanks Tara. Well, we had really great cooperation, both from the state. Jima ESF 11 folks and from Lori Foley and FEMA I mean Lori's been a great cheerleader for this project she was on our advisor committee she attended a lot of the meetings, and she's done a lot to help get the word out about this project. And same with our state level folks I mentioned that in one of my slides we've just really been lucky to develop such a good relationship with our ESF 11 coordinator. In the state and she is also an amazing cheerleader for the project and has made a lot of connections with us and is going to help us get the data imported into the state. That's that's the next step. And I think that was really just building relation while having Lori is great, you know we've worked with Lori for years so that was a huge advantage and then just the years it took to build relationships in the state. And eventually you find that person that really is aligned with us and it just takes time to find those people but they're out there for sure. And then Carl Stewart asked, how did you select partners. Yes, anyone and everyone. Christine you can take this one. Yeah, we were not selective but we really wanted to. You know reach all the institutions so we just reached out to all of the umbrella organizations that we could think of that we knew about in turn that. You know involve cultural heritage organizations so we see them organizations archives libraries. We want to get one area that we, we didn't really have time for is all of the local governments and that is a whole nother realm in itself. We got some of those folks included but we did start to look at the clerk of courts list I believe Cliff but I think we just had to table that so we could maybe do a phase two at some point there's always more to add. Do emergency managers access this data through the public facing website or do they have a different method of accessing the data. They access it through the public facing website. The way that we have it set up is that the publicly facing website gives you sort of a brief view, sort of slicing and dicing based on whether you want to see an emergency response region or individual counties or state as a whole. But that's actually the reason that we built that export instructions into the website so that folks could export the data for their own use in any way that they want. There really isn't any sort of back end to the website other than to edit and adjust the queries themselves that end up in the different sorts of displays. Okay. Could you talk more about getting state library to host website. Yeah, they actually volunteered, which was great, like Christine and I were really blessed through this whole project because when we pulled everyone together for the first few meetings ever, you know, we were met with like 99% enthusiasm from everybody. And so when we said hey, is there any sort of organization at a state level who'd be willing and Galileo, you know, volunteer, we were very happy with that because that way, you know, we work at an individual library and we're working with all of these partners but we didn't want to necessarily place the onus on our library we were looking for something state level to do the hosting, and we were very lucky that Galileo volunteered. Thank you. Looks like we have few more here. Is there a way to hide levels of data behind some sort of password protection. There is not. There is not that's the the wiki data platform is specific to publicly available information. And so for example, you know, a lot of organizations have individual folks email addresses. So we made a point that we would only include publicly visible email addresses if they were publicly visible on that organization's website so somebody's name. You know, like john dot dough at organization.org is published on that organization's website, we'd be willing to include it but we didn't include anything that was private or had personally identifiable information otherwise, just because we're basically reusing publicly visible material. So in the case of you know when I was talking about the metadata fields in the case of those things like cell phone numbers for administrators formats and those sorts of things. We've been trying to encourage folks as we go around to get in touch with their EOC emergency operations folks locally, as well as at the state level to say hey, these types of materials. The information like cell phone numbers and formats would be very helpful for the actual emergency responders, but there's just not room for it and wiki data because it's not built for that sort of secure information. Thank you. So is it possible to find quote closed glam closed glam. I don't know what that means. Is it a closed institution, maybe, or something with like closed stacks like, or private organization. Carl, if you're able to clarify your question in the chat box, you can go about it that way but I'll move on to as he has another question right below. I have two other states planning to follow you. He is with Colorado cultural and historical resources CHR and is running a proposal around for money with Colorado Boulder to do preliminary information collection research. Nice. We haven't heard anyone tell us yet that they're following our model we've had we've had interest but we haven't heard anyone say hey, we're following the ganch model in our state or our region. But we hope somebody will. Yeah, feel free to raise your hand now and volunteer to follow the model. And he was referring to discovered. Oh sorry. This disobey. Oh, thank you. Yeah, so because the data sets that were that we received were all, you know, out of date nothing can stay up to date except for something you produce today. That's why we did that quality control check and when we ran across dissolved organizations, we did include them in the data set so they're in wiki data now. But we also included the date that they dissolved, along with information about when that date was like you know if it was 2016 we tried to find some sort of newspaper article or, you know, a tweet or something else that indicated this was when it dissolved. And that way we have some sort of record that the organization had dissolved. What we did is we wrote into our scripts for great for our ganch website, all those queries. If you look at the code itself you'll actually see that it, it excludes any dissolved organizations. And so that way if, if Hera like looks on our ganch website, they will not see any organizations that are already closed in order to save time when it comes to responding after disaster. And so that's how we sort of navigated that is that yes we recorded that the organization existed yes we recorded the date that it was open and closed, but we're excluding it from our disaster response website to just save time. Okay. Many organizations have more than one location for the holdings. How did you manage that in the database. Excellent question. I'm very curious to hear about this because I know I've run into that problem to have multiple addresses and all sorts of craziness. Yeah, so the best example I can think of is the Georgia technical college system TCSOG and technical college system of Georgia. Where any, you know, they did a lot of mergers over the last decade and so like, I think in South Georgia it's like wire grass community or wire grass technical college has like five different campuses. And so this is actually a funny story is that we had the data set and so we're like, okay, here, all of these technical colleges that each have anywhere from two to, you know, seven different branches. So what we did is we actually looked at every single branch and tried to find where the location of the library was for those technical college campuses, even if it was like in one building. We tried to find some sort of record somewhere that the library was in that building. And so as you look at like the technical colleges. In the data set you'll see that like the the Vavasta campus and the Eccles campus and the Brooks campus will each have their own record for those libraries because we're trying to pin down each and every one of them so we listed them as separate institutions.  So, you know, each of these different campus libraries will all be under the parent organization of wire grass technical college. I hope that makes sense. Yes, okay. Any possibility of a guide for the rest of us to follow for other states. Yes. So, if you actually I will go back. So if you just search for the word ganch on Google, if you do like ganch linked data or something like that, you will find links to the project GitHub repositories which are down at the bottom of this slide. And the one that says ganch data actually has this workflow manual that we show here on the slide. And so that'll actually walk you through the whole process of how we took, you know, gathered the data, cleaned it up, ingested into open refine reconciled it and uploaded it. So, we also have a GitHub repository at the bottom for the website so if you want to show that to your web developers that'll show them how our website is built. We kept them separate because they're basically two separate things one is the actual source data set, and the other is the website. Thank you. Is ESF 11 involved with both response and recovery. I guess I could take that one clip. Yes, they are in that. The idea was to make the Hera and share the other cultural heritage organization sort of independent and be available as resources so the ideas if emergency responders happen upon a cultural organization that has damaged and they can refer them to us and if we do our own outreach before and after disaster then we can coordinate with them if they if those institutions need resources beyond what we can provide so we work very collaboratively with them in both response and recovery. I would say Hera and share more involved in in pre disaster actions sending out the emails which is the purpose of this database before disaster occurs, and then we work through ESF 11 to coordinate calls and we have done pre landfall calls to make sure that we have the resources they need before the disaster and then we also coordinate calls afterwards to assess damage for situational awareness and those sorts of things so I guess you know they are involved in really all aspects. Okay. And then we are not thinking so this is I think referring back to Colorado again we are not thinking of including natural resources. Can you discuss, you can you discuss your choosing to include those. I can, I can answer that one too. Because of the way ESF 11 is structured in Georgia. The lead organization is our Department of Natural Resources, which is over parks, and also over historic preservation so I don't know how if it's structured and differently. It's in states, but parks have a lot of historic sites in Georgia and they also have collections and exhibits of a lot of the park so we did include natural resources and of course historic structures and buildings which are all also under natural resources in terms of the state planning structure and the organization of how of the state. That makes sense. So I'll chime in that you know the question is often raised about archaeological resources, and that's actually something that we didn't include on purpose, because a lot of times, you know you have to protect the coordinate location data for archaeological resources to prevent poaching, or anybody coming in and messing with the site or doing any sort of damage, and there are separate archaeological resources databases in the state of Georgia run by I think also parks. But we chose not to include those because a they're not exactly organizations which this generally focused around organizations, although the breadth did, you know, sort of expand over time. So we considered that to be secure data and we didn't want to pose any additional risk by including those in wiki data. Glenda Anderson asked, we have been building relationships with our federal state and local emergency management entities for more than 10 years in Georgia. So we're going to be building relationships with our federal state and local emergency management entities for more than 10 years in Georgia. So we're going to be building relationships with our federal state and local emergency management entities for more than 10 years in Georgia. We have our number one cheerleaders on the GANCH project so she's she's very involved with Sharon we've been very lucky that she's done a lot of that face to face relationship building. I think that's a lot of it from all levels like building those relationships and trying to get like, so people know about you because I know whenever I go to places and I'm a contract registrar so I'll go to places and help people with emergency services and they'll sometimes say like well the fire department doesn't talk to us and I'm like well you gotta get on your agenda and like go and like meet them and be like hey fire department what's going on and like building those relationships will help everyone as they build all these types of projects for sure. Olivia Permanis, she's from Texas Sierra asked, what size was your grant and did it cover all the costs of this project. Yeah, I can answer that. Hey Olivia. Our grant was actually quite small. And what was it $16,000. Yeah it was less than $20,000. It was a very bare boned grant but we are grateful to have it. Cliff, all of his time was pretty much free. He did it as part of work. So I think if we actually would have costed this out and done an actual grant to cover all the costs it would have been quite a bit more, but the grant primarily covered our graduate student program of the travel and a computer so we made it we wanted to make it small because we knew we'd have a better chance of getting it funded and our institution was supporting cliffs time on it. I don't know if they ended up knowing how much time he spent on it. Oops but no but it was a great project and we got great support but we ended up actually devoting to other department members, a little bit to the project so definitely it did take longer than we thought so it did take more staff time than we had planned so I would say if you're going to write a grant definitely we could talk to you about budgeting for time. I think now that we've done it we have a better sense of how long it took it was going to take because at that point it was all just a pilot, and we really didn't know. I will tell you that the contract developer time for Matthew Stevens was not nearly enough. We contracted for I think like 20 you know 40 hours or something like just not enough time like assume that the web development piece of things is going to take a lot more time and also plan in money for presentations and travel and speaking and stuff. We were kind of in the silverest of linings and and I don't want to be dismissive, but COVID-19 actually was a good thing for us because all of a sudden everything went online and so we didn't have to worry about getting the word out because we could just sit in front of our computers and get the word out so as grim and unfortunate as the last year has been the timing actually worked out for us to be able to get the word out more than if we you know just didn't have any travel budget written into the grant. Right and thank you for mentioning that because Matthew Stevens did donate quite a bit of time to the project which was very kind of him. It looks like California is also working on a similar data compilation and seeking funding. They proposed data would be hosted on state site with password and grant funding requests in process with Cal OES and FEMA. There are more questions here. We encourage anybody who's interested and has more questions for Cliff and Christine to reach out to them with, you know, more inquiries, but we don't want to take up any more of their precious time that they've gifted us with today. So thank you so much, Cliff and Christine. We really appreciate you sharing this project with us. And I think this is super interesting and beneficial. Thank you. Thanks everyone.


This presentation explores the choices digital programs face as they add functionality to an expanding corpus of content and services. It focuses on archives and academic library special collections with metadata as the particular lens for this analysis. The scope, though, includes all aspects of digital programs and the concept of interoperability frames the discussion. We will look at several ways to conceive of it. Perfecting interoperability is a bit of a holy grail for digital and special collections since the content and culture of archives gravitate toward bespoke solutions. Unique content, the purpose of archives, can seem at odds with uniformity. But uniformity is what can bring multiple elements of digital programs for special collections into harmony. My name is Michael Herrick and I'm a cataloging and metadata librarian at San Francisco State University. I started here in September 2022 about a month before we began a three month process to migrate from content DM to Cortex, the Dams and Content Management System marketed by Adam Matthew, now AM Digital. Adam Matthew developed Cortex to produce and deliver curated digital collections of primary source content. AM Digital now offers the software as a service to enable individual institutions both to manage their digital assets and to arrange content into multiple types of collections. This front end content management part of Cortex is fairly customizable and thus speaks to an archivist's affinity for unique. Before coming to San Francisco State, I worked as a manager focusing on metadata and description at the Hoover Institution Library and Archives on Stanford's campus. My time at Hoover was dominated by participation in the planning for and launching of its next phase and a progression toward delivery of its fast and varied archival collections over the web. The front end of their Digital Collections 2 beta site, first put on the web in rough form in 2021, is truly but the skin of a major effort to rethink digital delivery for archival researchers. As the beta website currently states, Hoover is developing an ambitious new digitization program with an emphasis on digitizing whole collections to uniform standards. Hoover's collections serve an international body of advanced researchers. The library and archives are 100% privately funded with support coming from a relatively small body of donors. San Francisco State is a publicly funded university with a commitment to quality teaching and broad access to undergraduate and graduate education. The archival and unique collection materials of both institutions sit within larger networks of ownership and digital opportunity. Situated on Stanford's campus, Hoover has access to its digital repository built within the San Vera framework. San Francisco State is part of the 23 campus California State University, the largest public university system in the United States. The CSU has also adopted San Vera tools recently and San Francisco State is building its institutional repository for master's theses and other content in this direction. For digital archives though, neither Hoover nor San Francisco State chose to deposit assets to their respective broader institutional repositories during their most recent rounds of decision making about digital. A final note about the obvious serrations I'm making. While I was intensely involved in discussions about strategic decisions for digital collections too at Hoover between 2018 and 2021, I ended my involvement with that program in 2022. Conversely, I came to San Francisco State to help clean, wrangle, and ingest metadata in the recent migration to Cortex, but I had no involvement with the strategic decisions made here in the period 2019 to 2022. My reflections therefore are based on internal observations of process, the weighting of factors for decisions, and the consequences of these decisions, but I'm not really overwetted to either process at this point. These observations are mine and do not necessarily reflect programmatic statements of either institution. I've created this dual project briefing to help all special collections librarians and archivists to consider the challenges and factors at their home institutions as we all move ever more content online in creative and impactful ways. Anyone who has worked with digital migrations, implementations, or really digital content in any form in the back end knows that the glossy skins with which researchers interact on the web belie the complexity of decision making and trade-offs that go into a full digitization workflow and a digital publishing program. Many hard decisions must be made about interrelated components and resource allocation. When drilling down into the details of each component or node of a total program, one can spawn telescoping or metastasizing pathways of opportunity or need. The work simply to scope everything can absorb vast amounts of time and energy. In the next 10 to 15 minutes I will not cover everything about these two projects or implementations, but in migrations and implementations one needs to consider the fact that long term everything must interrelate or become interoperable on some level. Therefore, I'll spend a few minutes talking about interoperability generally before moving on to a brief description of the two projects in a contrast to compare format. Finally, I'll provide some reflections on metadata and long term strategies we should be considering as we balance two things. First, the established needs and examples of metadata surfacing in single aggregator websites like the Digital Public Library of America and Europe. Second, the emerging needs of linked data applications which offer the promise to build niche aggregators on the fly and via machine-based methods. When we think about interoperability in digital archives, both the International Image Interoperability Framework, TIPLIF, and the Open Archives Initiative Protocol for Metadata Harvesting, OAIPMH spring to mind. These are two enormously successful contributions to interoperability for finding and using digital content on the web. I strongly endorse their use, but the way we'll talk about interoperability here aims both smaller and bigger. Locally, I am talking about the interoperability of all the components of digital workflows. No one implementation of a system, software tool, adoption of a schema or workflow exists in isolation. Declaring adherence to principles like FAIR or implementing a TIPLIF viewer are important, but without a lot of effort devoted to the interoperability of local processes, digital production and dissemination quickly grind to a crawl or total halt. Every digital program aspires on some level to balancing all seven elements on the screen. Almost no program can make progress with all seven simultaneously at an even pace. Therefore, an implementation of a new system or element can be thought of as part of a dance over time. Less successful programs are the ones which just keep trading in one-to-one dance partners to keep up surface level confidence and an image of competence. It is important that they keep dancing and they will never be left without a partner or at least one individual connection to the total dance. Programs aimed at long-term capacity building and success see the full dance floor as an opportunity for growth. This approach includes all elements or all dancers. Long-term successful programs move forward roughly in sync, keeping all parts dancing to the same rhythm. This is interoperability over time for realistic digital production. At the end of this briefing, I'll reflect on the bigger aspect of interoperability, which I see as more of a metadata-specific topic. Catherine Ruddick gave a presentation in this pre-recorded project briefing series in April 2022 that provides an excellent example of implementing an all-in-one solution. The image on the right side of the slide is from her presentation, which I recommend you watch in conjunction with this one. The data or digital curation lifecycle derives from images on the vendor's website, Orange Logic. This type of dam's implementation approximates, as much as possible, all-in-one interoperability. Neither San Francisco State nor Hoover elected to take an all-in-one approach. Each local decision-making process follows its own logic based on its stakeholders and needs. But the processes at these two institutions shared a common factor in that that desire to solve one of the seven elements on the preceding slide weighed much more heavily than the other six. So an all-in-one dam's implementation was never really considered. That is not necessarily negative. All-in-one solutions have their strengths but also drawbacks by limiting versatility over time in doing the dance. In a couple of minutes, I will show a slide that captures the total weighted picture of the prioritization process at these two institutions. In terms of local interoperability, I will note that the AM Digital Cortex Solution is, in a sense, an all-in-one dam's directly linked to content management and publishing. But when born digital collection, collecting, digital preservation, and other elements of the total digital life cycle are considered, it is clear that Cortex, in its current form, is heavily skewed toward publishing and curating collections of materials for front-end defectiveness. Interestingly, Ruddock notes that the Cortex dam's, that's C-O-R-T-E-X at the University of Calgary, is linked to LibNova's LibSafe product for long-term digital preservation needs. The LibSafe digital preservation platform forms the core of Hoover's solution in that it is sandwiched between Archive Space and LibNova's discovery layer called Open Access. Hoover and the University of Calgary share the choice of LibSafe for digital preservation. The similarity of roots taken ends there. The methodology for decision-making at Hoover shared a lot, though, with that at San Francisco State. Even though the dominant priorities for each fill in opposite ends of the preservation and access continuum, each institution followed a similar path in how they researched and deliberated about a new implementation. Waiting priorities is not the same thing as prioritized waiting. Waiting priorities assumes a sequential process in which all priorities are scoped and established. Then research and a decision-making process occurs to prioritize and to allocate resources within a given time frame. Prioritized waiting, which I think is relatively common and pretty much happened at Hoover and San Francisco State, means that one or two elements on the total dance floor of digital interoperability receive preferential consideration at the start of a new phase of planning and implementation. Phasing the upgrading of elements on the total dance floor of digital interoperability is inevitable. Almost no institution is starting from scratch. Complete digital programs, which almost all archives will aim for given their mandate both to preserve and provide access, are thus required to phase change to the various elements. This is the only way to evolve ever more complex and effective digital services. Over the past decade, Hoover and San Francisco State have done exactly that. Nearly a decade ago, both had already brought digital asset projects, begun in the idiosyncratic manner, which all programs developed in the 1990s and early 2000s, into a small number of management systems. At San Francisco State, this was content DM for everything but the Bay Area Television Archive, which was providing access to digitized content through a locally developed platform called DIVA. Almost 10 years ago, Hoover also brought all but a few key groups of assets into gallery systems TMS. A main common driver for both institutions to seek replacement solutions in the past years involved the workflows for and eventual surfacing of OCR and audio transcriptions to enhance discovery and access. But their motivations for this derive from their differing priorities. The Bay Area Television Archives established a relationship with Cortex in 2020, two years prior to the general migration, largely for accessibility issues. Getting content fully transcribed, a feature which Cortex was building directly into their dams, assists San Francisco State's mission to provide equal access to all communities and to foreground accessibility to the content which treats the history of the whole Bay Area in the 60s, 70s, and 80s. At Hoover, full text searchability, whenever feasible, has become a key element in their ambitious goal to digitize entire archival collections in a uniform way. With human-produced metadata being a prohibitive cost element to mass digitization efforts, Hoover developed a strategy by which digitization could happen based on the slim metadata contained in the EAD of finding aids. This allows entire collections to be made available to researchers soon after digitization. The API-based Archive Space LibSafe connections will give researchers access through the finding aids almost immediately. With a focus on first getting things preserved and then getting as much full text access as possible built out as part of ingest, future stages of Hoover's original plan envisioned providing large textual datasets to researchers. It was also envisioned that machine-based entity enhancement in the total-meditated corpus could eventually build more and more discovery pathways. Both Hoover and San Francisco State have long-term visions while accepting short-term trade-offs. That San Francisco did not solve digital preservation up front does not mean that they are not as equally committed to this goal long-term as Hoover. That Hoover, in the beginning, sacrificed content management functionality beyond basic research or needs in order to build a fundamentally solid core system for digital preservation does not mean that they aren't equally committed to building strong content management solutions for niche publishing and teaching in order to highlight small areas of their total digitized corpus. In the last part of this briefing I will share a few reflections about interoperability as it relates specifically to metadata. The smaller focus of interoperability, which I've already presented, helps to keep all pieces of a local program dancing roughly to the same rhythm over time. Metadata is but one piece of this dance. As libraries, archives, and museums, or LAMS, edge ever closer to an environment in which linked data tools and platforms drive interoperability, I think a shift in perspective about metadata for digital objects within archives could happen. Near the start of the Digital Collections 2 planning phase, a couple members of Hoover's very small planning team were invited to participate in a two-day session at Stanford, which brought together people from libraries, archives, and museums to brainstorm further growth of already highly successful IIIF development. Within this two-day LAM melting pot, there was a strong drive to force consensus around uniformity of metadata elements in IIIF manifests. The museum community seemed convinced that it should be possible to agree on title and a few other elements to achieve metadata interoperability across communities. Librarians seemed convinced that linked data development and IIIF development would and should proceed with awareness of each other's domain without rigid forced integration. Archivists seemed somewhat perplexed by the whole conversation. Build out of extensive descriptive metadata for archival objects taken out of the archival context does happen in digital archives, but the original order of creation, storage, and presentation provides the fundamental framework of archival description. Traditional archival description in aggregators is both not effective and can become astronomically expensive. To make a description of archival objects aggregator friendly is like completing all the work which a creator and a publishing house need to do when they prepare a book or article for publication. Once all the descriptive elements have been created, they then need to be formatted into a structured form with multiple access points like cataloging and publication or CIP statements. When the original creator of an object does or oversees this, the resulting description tends to be accurate. An archival processor or digital program metadata producer works at a certain number of degrees of separation from the original context of creation. Changes in cultural, historical, and linguistic context result in blurred accuracy. By assigning an archival resource key or arc to every object and building a metadata application profile at Hoover which is focused on the eventual generation of RDF triples, an underlying framework has been established to make the atomization of interoperability for metadata creation and use possible. OAIPMH and the main digital object aggregators of the past several decades necessitate a level of description which is simply unrealistic when working with mass digitization of archival content. People are successfully doing it, but scaling it for mass digitization of archives is not economically feasible. The emerging potential to provide a wiki-based type environment for creating collaborative knowledge bases could greatly expand the discovery potential for digitized archival content. For Hoover, this is basically essential since its collection mission has been focused on bringing in content from all over the world in a huge number of languages. Quality discovery pathways to individual items will need to be aided by both machine applications and worldwide collaborative effort. The same approach would work equally well at San Francisco State. This would marshal the collective knowledge and participation of the entire San Francisco Bay Area instead of relying on a small number of staff on the San Francisco State campus. Both San Francisco State and Hoover are still very much in the soft launches or beta phases of their current implementations. I encourage you to check back at these sites in the coming months and years to see how they each build functionality and at what pace. The main tensions they experienced in planning for this phase involved how to balance resource expenditure along the preservation and access continuum. My discussion of the linked data potential for digital projects and archives has been brief, but I encourage you to think about the possibilities for deep linking and discovery across archival collections and repositories. Content can continue to be represented in major aggregators, but some of the most fruitful connections which will lead to the powerful interoperability will I think happen when RDF statements begin to create direct connections between related content to positive archives throughout the world. Thank you for listening.