Preservation and institutional repositories for the digital arts and humanities

  • Published on
    21-Oct-2014

  • View
    960

  • Download
    2

DESCRIPTION

For the Digital Humanities Data Curation Institute

Transcript

<p>Dorothea SaloUniversity of Wisconsin</p> <p>salo@wisc.edu</p> <p>Institutional repositories for the digital arts and </p> <p>humanities</p> <p>Dorothea SaloUniversity of Wisconsin</p> <p>salo@wisc.edu</p> <p>Preservation for the digital arts and </p> <p>humanities</p> <p>Dorothea SaloUniversity of Wisconsin</p> <p>salo@wisc.edu</p> <p>Dorothea SaloUniversity of Wisconsin</p> <p>salo@wisc.edu</p> <p>Preservation andinstitutional repositories for the digital arts and </p> <p>humanities</p> <p>And I said...</p> <p>... youre giving me how much time for this?</p> <p>Environment</p> <p>As several of you are intimately aware, higher ed is trying to figure out What To Do About Data.</p> <p>This spells opportunity... IF you can get a seat at the table, and IF you know what to ask for!</p> <p> Humanists will not be the first people they think of, sadly.</p> <p>Serious (insoluble?) problem: data diversity Expect compromise solutions.</p> <p>Do not let IT pros intimidate you. They do not know everything they think they know.</p> <p>PICK SOFTWARELAST.</p> <p>Friendly wordof advice:</p> <p>Photo: Briana Calderon; future educator of america. http://www.flickr.com/photos/46132085@N03/4703617843/</p> <p>Arielle Calderon / CC-BY 2.0</p> <p>ITS WHATTHE SOFTWAREWONT DO.</p> <p>Its not what the software doesthatll kill you.</p> <p>Photo: Briana Calderon; future educator of america. http://www.flickr.com/photos/46132085@N03/4703617843/</p> <p>Arielle Calderon / CC-BY 2.0</p> <p>DONT CHASE THE SHINY.</p> <p>Another friendly word of advice:</p> <p>Photo: Sparkle Texture http://www.flickr.com/photos/abbylanes/3214921616/Abby Lane / CC-BY 2.0</p> <p>its much lessshiny.</p> <p>In five years...</p> <p>Photo: Sparkle Texture http://www.flickr.com/photos/abbylanes/3214921616/Abby Lane / CC-BY 2.0</p> <p>its not shinyat all.</p> <p>In ten years...</p> <p>Photo: Sparkle Texture http://www.flickr.com/photos/abbylanes/3214921616/Abby Lane / CC-BY 2.0</p> <p>In twenty years...</p> <p>its probablyuseless.</p> <p>NOT A SOLUTION:your graduate students</p> <p>You have a bright, tech-savvy grad student.She builds an Awesome Tech Thing.You have no idea how it works.She graduates. Youre hosed.</p> <p> Because she didnt (know how to) build it sustainably... Because you dont have any documentation... Because nobody made contingency plans for it...</p> <p> I have seen this pattern over and over again. Its killed more digital culture and research materials than </p> <p>anything I can think of in academe.</p> <p>Am I saying dont experiment?</p> <p>Nah, of course not. Im saying know what an experiment means. Im saying dont mistake an experiment for an </p> <p>archive. Im saying dont experiment and then expect </p> <p>everybody else to pick up your pieces because you didnt plan for metadata or preservation.</p> <p>That said?</p> <p>You gotta do what you gotta do.Some friendly advice:</p> <p> Know where the exits are. (Can you export your data? In a reusable format?)</p> <p> When you finish a project, USE that export. Triply true if youre relying on the cloud!</p> <p>Your overriding goal, while a project is in progress: keep your eventual options open!</p> <p>Long-term... is a totally other kettle of fish.</p> <p>Your best strategyThe single best strategy for a digital humanist </p> <p>concerned about long-term preservation... ... is to figure out how to make it Somebody </p> <p>Elses Problem. Right now, this is hard. I do believe it will get easier.</p> <p> Its a lot easier to figure this out from the start than at the end.</p> <p> Dierent Somebody Elses will have dierent things that they want. If you know that from the get-go, youre much better o.</p> <p>Institution-internal solutions</p> <p>Institution-internal solutions</p> <p>Rolling your own</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software e.g. Omeka, Dataverse, ArchivesSpace...</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software e.g. Omeka, Dataverse, ArchivesSpace... Better, but not foolproof. Upgrades? Security? Backups?</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software e.g. Omeka, Dataverse, ArchivesSpace... Better, but not foolproof. Upgrades? Security? Backups? Writing plugins/mods = rolling your own. Avoid if possible.</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software e.g. Omeka, Dataverse, ArchivesSpace... Better, but not foolproof. Upgrades? Security? Backups? Writing plugins/mods = rolling your own. Avoid if possible.</p> <p>Adopting institutional infrastructure</p> <p>Institution-internal solutions</p> <p>Rolling your own Please dont, if you can possibly avoid it.</p> <p>Adopting open-source software e.g. Omeka, Dataverse, ArchivesSpace... Better, but not foolproof. Upgrades? Security? Backups? Writing plugins/mods = rolling your own. Avoid if possible.</p> <p>Adopting institutional infrastructure Make sure itll survive your departure from the institution!</p> <p>Outside the institution</p> <p>Outside the institution</p> <p>Lists of data repositories</p> <p>Outside the institution</p> <p>Lists of data repositories Databib: http://databib.org/</p> <p>Outside the institution</p> <p>Lists of data repositories Databib: http://databib.org/ re3data: http://re3data.org/</p> <p>Outside the institution</p> <p>Lists of data repositories Databib: http://databib.org/ re3data: http://re3data.org/ N.b. you will find less here on the humanities than you </p> <p>would probably prefer. Long story.</p> <p>Outside the institution</p> <p>Lists of data repositories Databib: http://databib.org/ re3data: http://re3data.org/ N.b. you will find less here on the humanities than you </p> <p>would probably prefer. Long story.</p> <p>Figshare</p> <p>Outside the institution</p> <p>Lists of data repositories Databib: http://databib.org/ re3data: http://re3data.org/ N.b. you will find less here on the humanities than you </p> <p>would probably prefer. Long story.</p> <p>Figshare ... and other web services springing up, e.g. omeka.net</p> <p>You will be limited by... Infrastructure your library/IT has already </p> <p>committed to this is why you want to be in on ground-floor discussions!</p> <p>Their willingness and ability to tweak, rewrite, or replace it with something suiting your needs</p> <p>Your willingness and ability to evaluate, install, and maintain a software stack that suits you</p> <p> ... perhaps indefinitely!</p> <p>The availability of hosted solutions, and your ability to pay for them (perhaps indefinitely!)</p> <p>You need to know what the options are like.</p> <p>Your library and IT folks may well need guidance. At minimum, they need clearly-expressed requirements.</p> <p>The requirements you give them need to go beyond end-user access, use, and UI.</p> <p> Back end: getting material in as eciently as possible, allowing for additions/changes/deletions</p> <p> Preservation requirements Data and metadata purity, clarity, preservability, </p> <p>reusability, mashuppability, migratability, standards</p> <p>Institutional repositories</p> <p>Whats an IR?[A]ttics (and often fairly empty ones), with </p> <p>random assortments of content of questionable importance</p> <p> Brown, Griths, Rasco, University publishing in a digital age. Ithaka 2007. http://www.sr.ithaka.org/research-publications/university-publishing-digital-age</p> <p>A basic digital preservation-and-access platform designed to allow faculty to deposit and describe single PDFs.</p> <p>Quite commonly available in research libraries or through library consortia.</p> <p> You probably have one available to you!</p> <p>IR softwareOpen source</p> <p> Fedora Commons: http://fedora-commons.info/ (youll need a layer on top of this)</p> <p> DSpace: http://dspace.org/ EPrints: http://eprints.org/</p> <p>Commercial ContentDM: http://contentdm.com/ DigiTool: http://www.exlibrisgroup.com/category/</p> <p>DigiToolOverview</p> <p>Hosted ContentDM: http://contentdm.com/ BePress: http://bepress.com/</p> <p>Two minutes!</p> <p>Find an IR available to you for depositing content.</p> <p>You can typically expect...To get in touch with someone in the library to </p> <p>get an account set up, and a space for you to deposit into</p> <p> Have a collection name and description ready. Default descriptors, if you have any, also a good idea. Need access controls? To delegate deposit? Talk about this.</p> <p>To be able to put materials in on your own, through web forms</p> <p> To find the deposit process fiddly and annoying</p> <p>To have material appear on the web right after deposit.</p> <p>IRs work for...</p> <p>Small(ish), discrete files that never change So an Excel-using researcher is just fine with an IR.</p> <p>Documentation for data held elsewhereSome IRs can handle static website captures.Files with uncomplicated IP lives</p> <p> ... which complicates the static website question.</p> <p>Access restriction may be possible, as may dark archiving; it depends on the IR platform. Expect it to be annoying to implement, though.</p> <p>IRs dont work forReally Big Data</p> <p> including, sometimes, audio and video This is less a reflection on IR software than of most IRs being </p> <p>horribly underprovisioned with storage and bandwidth.</p> <p>Work in progress; files that may change or be updated</p> <p>Complex digital objects (except static websites)Digital objects that need interactivity</p> <p> Even something as simple as video streaming. IRs cant.</p> <p>Anything that needs a DOI. (Youll get a permanent identifier, but it wont be a DOI.)</p> <p>Datasets where the researcher wants to vet any potential reusers</p> <p>Digital libraries</p> <p>Digital-library software Omeka, Greenstone (aging), ContentDM... Again, chances are your library already has some kind </p> <p>of digital-collections software. Go ask a librarian what it is, and whether you can add material to it! Also ask if its attached to any kind of digitization or metadata-help </p> <p>service. It may not be, but you never know.</p> <p> If not, there are hosted options if youre prepared to pay for them indefinitely.</p> <p> Designed for image exhibitions May extend to audio and video, but UI wont be ideal. May extend to page-scanned books, but may not. (Omeka is terrible </p> <p>at these.)</p> <p>Be aware</p> <p>The digital-preservation underpinnings of this class of software are weak to nonexistent.</p> <p> Its designed for exhibiting, not for archiving! It may also entice you into poor sustainability decisions, </p> <p>such as using web-friendly but lossy JPG as your master image format. Or not making backups.</p> <p>On the plus side, though, if its a library service, the library feels an institutional commitment to the materials in it.</p> <p> Thats a lot of the preservation battle won, right there.</p> <p>Emerging solutions</p> <p>Often involve combining software to attack dierent parts of the problem</p> <p> Preservation underlayers: Fedora Commons, microservices Deposit and management UI: Hydra, Islandora End-user UI: Hydra, Islandora, Omeka, plugins, mods, etc.</p> <p>Are still pretty DIY at this point If your library is doing active development, youre one of </p> <p>the lucky ones. The rest of you may have to wait. And lobby.</p> <p>Archives platforms</p> <p>Designed for coping with an undierentiated mess of random digital stu.</p> <p> I know, right? Nobody has that problem...</p> <p>Not usually designed to help other people use or interact with that stu.</p> <p> Also, designed for archivists ways of thinking. Archivists are humanists, but not all humanists are archivists.</p> <p> Worth getting a software tour from an archivist!</p> <p>Archivematica, ArchivesSpace (in beta), Duke Data Accessioner, CollectiveAccess, BitCurator</p> <p>Data-management platformsUsually designed for the sciences, not the </p> <p>humanities! But that doesnt necessarily mean they wont work for what </p> <p>you have in mind. (E-lab notebooks will probably feel pretty foreign, though.)</p> <p>Look at Dataverse Network, http://thedata.org/Gigantor lists of everything ever:</p> <p> http://www.dcc.ac.uk/resources/external/tools-services/archiving-and-preserving-information</p> <p> http://dirt.projectbamboo.org/categories/publishing http://foss4lib.org/packages Less helpful than you might think; theres rarely any decision </p> <p>apparatus alongside.</p> <p>Dorotheas cantankerous, crabby, cynical, crude, choleric, churlish, other-words-beginning-with-C </p> <p>take on digital humanists working with librarians and IT pros</p> <p>Neil Gaiman on George R.R. Martin and his eager fans</p> <p>CENSORED</p> <p>CENSORED</p> <p>From: http://journal.neilgaiman.com/2009/05/entitlement-issues.html</p> <p>Digital humanists:</p> <p>Librarians and IT professionals are </p> <p>not your bitch.CENSORED</p> <p>Not entirely your fault!</p> <p>$$$ is a consideration, unfortunately The sciences have it. Unfortunately.</p> <p>Your colleagues may have poisoned the well by being prima donnas, even though youre not!</p> <p>Dierent professional-advancement infrastructure</p> <p>We may just. not. be. ready. Or the infrastructure we rely on may not be.</p> <p>DH and libraries should be friends Involve the library from the outset.</p> <p> Please do NOT ask us to pick up your messes at the end! Expect us to have work for you to do, and quality expectations. Yes, I know thats how it used to work with analog materials </p> <p>and archivists. Digital is dierent.</p> <p>Come to us in groups. We serve all of campus. We cannot aord to move heaven and </p> <p>earth for any one person. Please dont be a prima donna! At minimum, have an idea how what youre asking will </p> <p>concretely benefit other campus constituencies.</p> <p>Oer quid pro quo. Whats in it for us? (Library advocacy in high places is always a good trade.)</p> <p>Be patient, please. We dont turn on a dime.</p> <p>Will this always work?Sadly, no.A good many libraries are just not ready to </p> <p>take digital preservation and DH support seriously.</p> <p> The presence of a DH center in the library is not always proof of serious intent.</p> <p>Others have been burned before.Still others are skeptics. I cant promise youll find help in the library, or </p> <p>with campus IT. I can promise you wont if you dont seriously approach them.</p> <p> (Miriam Posners article is a must-read!)</p> <p>Thanks!Questions?</p>

Recommended

View more >