{"id":1396,"date":"2018-06-13T13:17:47","date_gmt":"2018-06-13T17:17:47","guid":{"rendered":"http:\/\/libapps.libraries.uc.edu\/source\/?p=1396"},"modified":"2018-06-14T11:26:09","modified_gmt":"2018-06-14T15:26:09","slug":"managing-university-archives-in-a-digital-world","status":"publish","type":"post","link":"https:\/\/libapps.libraries.uc.edu\/source\/managing-university-archives-in-a-digital-world\/","title":{"rendered":"Managing University Archives in a Digital World"},"content":{"rendered":"

By Eira Tansey, Digital Archivist\/Records Manager, Archives and Rare Books Library<\/em><\/p>\n

\u201cWhat College-Conservatory of Music musicals were staged in 1986?\u201d<\/p>\n

\u201cWhen did the university begin offering a dental insurance plan?\u201d<\/p>\n

\u201cWhat dorms have served as polling places?\u201d<\/p><\/blockquote>\n

These are just a handful of the university-history related questions I\u2019ve encountered since starting work at the Archives and Rare Books (ARB) Library nearly five years ago. The questions we receive concern events at all times in campus history \u2013 from the earliest days of UC\u2019s predecessor colleges to events that took place just a couple years ago.<\/p>\n

ARB is the official home for University Archives, making us the obvious place to go for answers about university history. But our archives do not instantly materialize \u2013 they require diligence and work to ensure records are not lost. Anyone who has ever tried to research their family genealogy knows the woes of promising clues leading to a trail that quickly turns cold. Maybe the records in question were lost in a fire, or were simply never maintained because someone didn\u2019t understand their value for future users.<\/p>\n

Thanks to diligent faculty, staff and students who have done much work over the years to send us records, photographs and other documents, University Archives can answer most questions we receive about the last two centuries of the university\u2019s history. But today we run the risk of losing our university\u2019s third century of history.<\/p>\n

\"arb<\/a>
ARB Stacks<\/figcaption><\/figure>\n

Since ARB was created, the main way in which University Archives receives content has been departments dropping off boxes of paper records. We then organize the contents of each box (what archivists call \u201cprocessing\u201d) and inventory them (creating a \u201cfinding aid\u201d). The processed boxes then go into our secure archival stacks, where they are ready to be retrieved when needed by a user.<\/p>\n

The vast majority of today\u2019s content that will be tomorrow\u2019s archives is created in diverse technologies. Most photographs are no longer developed in darkrooms; rather, they are manipulated in Photoshop. Reports are no longer printed and bound, they are distributed via PDF. And when was the last time you wrote a formal memo? E-mails are the new memos.<\/p>\n

Per the university\u2019s official records management policy, departments are required to periodically send specific records to University Archives to ensure continuity in preserving university history. The reality is that in the past, it was often easier to comply with those guidelines than it is today. In a paper-based environment, at some point transferring files was inevitable thanks to a move to a new building or the filling up of filing cabinets. Today, there is no equivalent digital \u201ctrigger event\u201d of a physical move or full storage that forces departments to think, \u201cHey, it\u2019s time to send these files to University Archives.\u201d There are many different file storage systems across campus, and unfortunately there are almost no options to automate collecting relevant archival records from the university\u2019s various colleges and administrative units.<\/p>\n

As the University of Cincinnati Libraries\u2019 digital archivist\/records manager, I am responsible for issuing both guidance for records while they are still in the custody of departments around the university and managing the processing of \u201cborn digital\u201d records that are transferred to University Archives. As a result, I often see how even though departments are advised to transfer records to us, they struggle to do this as regularly as we would like to see happen.<\/p>\n

I\u2019m pleased to report, however, that this is not an insurmountable challenge. One of the creative ways that university staff and I have found to be the easiest way to transfer records is through UC Box, the file sharing system the University of Cincinnati adopted recently. Within Box, UC affiliates can easily send their records to me. Here is an example from the College of Arts and Sciences administrative office:<\/p>\n

\"box<\/a><\/p>\n

After I receive the files through Box, I still have to process the files. What does it mean to process born-digital files? It depends. The first thing I do is to make a local \u201cpreservation copy\u201d of all the files that are transferred, and place them into secure digital storage outside of Box, on the Libraries\u2019 digital collections server. I then create a \u201cprocessed copy\u201d of all the files that are intended for public use \u2013 similar to the boxes of paper files we keep on the shelves of University Archives that we pull upon request. This is a bit like putting your original birth certificate into a bank safe deposit box, while you keep a photocopy at home in your personal records.<\/p>\n

If it\u2019s a potentially sensitive set of records, I might do a close review of the files to ensure no confidential information is being disseminated that needs to be kept private. The processed files are usually very similar to preservation files, with some minor changes to enable public use.<\/p>\n

During processing, there is a lot of waiting while running various tasks on large groups of files. This is a pretty common sight in my working life:<\/p>\n

\"box<\/a><\/p>\n

At the end of the process (and often, much earlier) I will run what is known as hashing or checksumming of the files. A hash, or checksum, is an algorithmic process run on a file to generate a unique alphanumeric number for that file. If anything changes within the \u201cguts\u201d of the file – whether the deletion of a period at the end of a sentence, a changed pixel in a photo, or snipping of a half-second of audio –\u00a0 then the entire checksum will change for the file. \u00a0Digital archivists will generate a checksum for files when they are received, and will generate them again on a periodic basis. If they match, this is how archivists can demonstrate that the file has not suffered from any corruption or change.<\/p>\n

\"digital<\/a><\/p>\n

Finally, I publish a finding aid for all processed born-digital collections. Many archives with born-digital collections are exploring unique ways to enable user access to these records. Some have set up \u201cvirtual reading rooms\u201d while others simply deliver the files through a file sharing system or email. We are still figuring this part out at the University of Cincinnati Libraries.<\/p>\n

Digital archivists deal with a paradox of living in a digital deluge (where it is far easier to create new documents than 40 years ago), but also battling a digital dark age (where without early intervention in archiving files, they can risk being lost or corrupted). It may seem like the digital transition has changed everything about archivists\u2019 work, but the recipe for success remains the same \u2013 building relationships across the university, investment in infrastructure and always looking for creative ways to solve problems.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Eira Tansey, Digital Archivist\/Records Manager, Archives and Rare Books Library \u201cWhat College-Conservatory of Music musicals were staged in 1986?\u201d \u201cWhen did the university begin offering a dental insurance plan?\u201d \u201cWhat dorms have served as polling places?\u201d These are just a handful of the university-history related questions I\u2019ve encountered since starting work at the Archives and Rare Books (ARB) Library nearly five years ago. The questions we receive concern events at all times in campus history \u2013 from the earliest days of UC\u2019s predecessor colleges to events that took place just a couple years ago. ARB is the official home for University Archives, making us the obvious place to go for answers about university history. But our archives do not instantly materialize \u2013 they require diligence and work to ensure records are not lost. Anyone who has ever tried to research their family genealogy knows the woes of promising clues leading to a trail that quickly turns cold. Maybe the records in question were lost in a fire, or were simply never maintained because someone didn\u2019t understand their value for future users. Thanks to diligent faculty, staff and students who have done much work over the years to send us records, photographs and other documents, University Archives can answer most questions we receive about the last two centuries of the university\u2019s history. But today we run the risk of losing our university\u2019s third century of history. Since ARB was created, the main way in which University Archives receives content has been departments dropping off boxes of paper records. We then organize the contents of each box (what archivists call \u201cprocessing\u201d) and inventory them (creating a \u201cfinding aid\u201d). The processed boxes then go into our secure archival stacks, where they are ready to be retrieved when needed by a user. The vast majority of today\u2019s content that will be tomorrow\u2019s archives is created in diverse technologies. Most photographs are no longer developed in darkrooms; rather, they are manipulated in Photoshop. Reports are no longer printed and bound, they are distributed via PDF. And when was the last time you wrote a formal memo? E-mails are the new memos. Per the university\u2019s official records management policy, departments are required to periodically send specific records to University Archives to ensure continuity in preserving university history. The reality is that in the past, it was often easier to comply with those guidelines than it is today. In a paper-based environment, at some point transferring files was inevitable thanks to a move to a new building or the filling up of filing cabinets. Today, there is no equivalent digital \u201ctrigger event\u201d of a physical move or full storage that forces departments to think, \u201cHey, it\u2019s time to send these files to University Archives.\u201d There are many different file storage systems across campus, and unfortunately there are almost no options to automate collecting relevant archival records from the university\u2019s various colleges and administrative units. As the University of Cincinnati Libraries\u2019 digital archivist\/records manager, I am responsible for issuing both guidance for records while they are still in the custody of departments around the university and managing the processing of \u201cborn digital\u201d records that are transferred to University Archives. As a result, I often see how even though departments are advised to transfer records to us, they struggle to do this as regularly as we would like to see happen. I\u2019m pleased to report, however, that this is not an insurmountable challenge. One of the creative ways that university staff and I have found to be the easiest way to transfer records is through UC Box, the file sharing system the University of Cincinnati adopted recently. Within Box, UC affiliates can easily send their records to me. Here is an example from the College of Arts and Sciences administrative office: After I receive the files through Box, I still have to process the files. What does it mean to process born-digital files? It depends. The first thing I do is to make a local \u201cpreservation copy\u201d of all the files that are transferred, and place them into secure digital storage outside of Box, on the Libraries\u2019 digital collections server. I then create a \u201cprocessed copy\u201d of all the files that are intended for public use \u2013 similar to the boxes of paper files we keep on the shelves of University Archives that we pull upon request. This is a bit like putting your original birth certificate into a bank safe deposit box, while you keep a photocopy at home in your personal records. If it\u2019s a potentially sensitive set of records, I might do a close review of the files to ensure no confidential information is being disseminated that needs to be kept private. The processed files are usually very similar to preservation files, with some minor changes to enable public use. During processing, there is a lot of waiting while running various tasks on large groups of files. This is a pretty common sight in my working life: At the end of the process (and often, much earlier) I will run what is known as hashing or checksumming of the files. A hash, or checksum, is an algorithmic process run on a file to generate a unique alphanumeric number for that file. If anything changes within the \u201cguts\u201d of the file – whether the deletion of a period at the end of a sentence, a changed pixel in a photo, or snipping of a half-second of audio –\u00a0 then the entire checksum will change for the file. \u00a0Digital archivists will generate a checksum for files when they are received, and will generate them again on a periodic basis. If they match, this is how archivists can demonstrate that the file has not suffered from any corruption or change. Finally, I publish a finding aid for all processed born-digital collections. Many archives with born-digital collections are exploring unique ways to enable user access to these records. Some have set up \u201cvirtual reading rooms\u201d while others simply deliver the files through a file sharing system or email. We are still figuring this part out at the University of Cincinnati Libraries. Digital archivists deal with a paradox of living in a digital deluge (where it is far easier to create new documents than 40 years ago), but also battling a digital dark age (where without early intervention in archiving files, they can risk being lost or corrupted). It may seem like the digital transition has changed everything about archivists\u2019 work, but the recipe for success remains the same \u2013 building relationships across the university, investment in infrastructure and always looking for creative ways to solve problems.<\/p>\n","protected":false},"author":2,"featured_media":1383,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[75,79],"tags":[17,54,16,29],"class_list":["post-1396","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-volume-16","category-volume-16-issue-3","tag-archives-and-rare-books-library","tag-collections","tag-digital-collections","tag-uc"],"_links":{"self":[{"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/posts\/1396","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/comments?post=1396"}],"version-history":[{"count":5,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/posts\/1396\/revisions"}],"predecessor-version":[{"id":1438,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/posts\/1396\/revisions\/1438"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/media\/1383"}],"wp:attachment":[{"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/media?parent=1396"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/categories?post=1396"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/libapps.libraries.uc.edu\/source\/wp-json\/wp\/v2\/tags?post=1396"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}