Leslie Johnston Keynote, Best Practices Exchange 2011


Published on

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Leslie Johnston Keynote, Best Practices Exchange 2011

  1. 1. From Records to Data:It’s Not Just AboutCollections Any More Leslie Johnston, Library of Congress Best Practices Exchange 2011
  2. 2. What are the Biggest Insights that we have Learned in Fifteen Years ofBuilding Digital Collections?
  3. 3. Researchers do not use digitalcollections the same way that they use analog collections
  4. 4. We Can Never Guess EveryWay that Our Collections Will Be Used
  5. 5. Stewardship organizationshave, until recently, spoken of“collections” or “content” or“records” or even “files,” butnot data.
  6. 6. We Have Data in our Libraries, Archives and Museums? Yes.Data is not just generated by satellites, identified during experiments, or collected during surveys.
  7. 7. Datasets are not just scientific and businesstables and spreadsheets: our collections arenow considered data.They are the building blocks for interpretationand discovery that transform and combinethem into entities that we may not recognize.
  8. 8. More and more researchers want to usecollections as a whole, mining and organizingthe information in novel ways.Researchers use algorithms to mine the richinformation and tools to create pictures thattranslate that information into knowledge.Researchers may want to interact with acollection of artifacts, or they may want towork with a data corpus.
  9. 9. Consider the Digging Into DataChallengeThe repositories available for research include not onlyscientific information—astronomy, geology, physics, biology,social science surveys—but images, film, sound,newspapers, maps, art, archaeology, architecture andgovernment records. http://www.diggingintodata.org/
  10. 10. What Constitutes “Big Data?”The definition of Big Data is very fluid, as it is a movingtarget — what cannot be easily manipulated with commontools — and specific to the organization: what can bemanaged and stewarded by any one institution in itsinfrastructure. One researcher or organization’s concept ofa large data set is small to another.Not too long ago, an organization would be surprised toneed 10 TB of storage for a large digital collection. Now acollection can increase by 10 TB in a single week.
  11. 11. We still have collections. But what we alsohave is Big Data, which requires us to rethinkthe infrastructure that is needed to supportBig Data services. Our community used toexpect researchers to come to us, ask usquestions about our collections, and use ourdigital collections in our environment.Now our collections are, more often than not,self-serve.
  12. 12. Case Study: Web Archives • Web Archives, such as the one at the Library of Congress, may be comprised of billions of files. • When we began archiving election web sites, we imagined users browsing through the web pages, studying the graphics or use of phrases or links. But when our first researchers came to the Library, they wanted to know about all those topics, but they used scripts to query for them and sort them into categories. They were not very much interested in reading web pages. http://www.loc.gov/webarchiving/
  13. 13. Case Study: Historic Newspapers • The Chronicling America collection has over 4 million page images from historic newspapers with OCR from organizations in 25 states. • The site gets approximately 4 million views per day. • Some researchers want to search for stories in historic newspapers. • Some researchers want to mine newspaper OCR for trends across time periods and geographic areas. • Requests have come in to analyze all 4 million page images. http://chroniclingamerica.loc.gov/
  14. 14. Case Study: Twitter • The Twitter archive has 10s of billions of tweets in it. • Research requests have included users looking for their own Twitter history, the study of the geographic spread of news, the study of the spread of epidemics, and the study of the transmission of new uses of language. social science visualization social media status events personal privacy commercial
  15. 15. Can each of our organizations support real-time querying of billions of full-textitems? Can we provide tools for collectionanalysis and visualization? Can we supportthe frequent downloading by researchers ofcollections that may be over 200 TB each?These are among the questions that all of ourinstitutions are grappling with as we buildlarge digital collections and discover newways in which they can be used.
  16. 16. So what are ourinstitutions doingabout preservationand access to ourBig Collections andBig Data?
  17. 17. Collaboration www.digitalpreservation.gov/ndsaThe National Digital Stewardship Alliance is aninitiative of the National Digital InformationInfrastructure and Preservation Program at theLibrary of Congress, with almost 100 memberorganizations that share a sense of dedication todigital preservation, and want to workcollaboratively across the community.The NDSA operates through five working groups:Content; Standards and Practices; Infrastructure;Innovation; and Outreach.
  18. 18. Tool DevelopmentAll stewardship organizations can and shouldparticipate in the development and use of openaccess tools for use across the community.NDIIPP is revising its Tools and ServicesDirectory to include a broader range of projects,some of which are always looking for otherorganizations to contribute to!http://www.digitalpreservation.gov/partners/resources/tools
  19. 19. As an Example…Seeing and Sharing Digital CulturalHeritage Collections Differentlywith ViewShare/Recollection
  20. 20. bigish ideas› heterogeneous data› one big distributed collection› open distributed infrastructure› mindset: records -> data
  21. 21. Beyond thinkinglike records
  22. 22. to thinkinglike data
  23. 23. the ViewShare ideadigital cultural heritage collectionsinclude temporal, locative, andcategorical data that, could betapped to better dynamicallyinteract with and understand thosecollections.
  24. 24. the challenges› we all have different kinds ofmetadata› that data is in different kinds ofsystems› much of that data is messy› much of that data is not in theformat we might wish it was
  25. 25. whatViewSharedoes
  26. 26. take this
  27. 27. or this
  28. 28. and make…
  29. 29. ingest collectiondescriptions fromspreadsheets, MODSrecords, or ATOM andRSS
  30. 30. Augment: deriveISO dates,latitude andlongitudecoordinates, andbreak apartdata
  31. 31. design views:graphical interfacefor assemblingviews
  32. 32. publish views on the site or embedviews with one line of javascript intoany HTML document.
  33. 33. visually review data
  34. 34. share data and viewsshare not only the end results, butalso the raw data for other others tocreate their own views.data use and re-use
  35. 35. recent work› support for public/private views and data› beta support for OAI and ContentDM dataloading› full open source release on SourceForge:http://sourceforge.net/projects/loc-recollect/
  36. 36. what’s next?› viewshare.org public launch onNovember 1, 2011› big data sets: in a while› remix across data sets: long view
  37. 37. contact us› Let us know if you are interested inparticipation in the NDSA through the website› Let us know if there is a tool or service thatis missing from our directory› visit http://recollection.zepheira.com/ to geta sneak peek at ViewShare› email NDIIPPaccess@loc.gov if you areinterested in a ViewShare account
  38. 38. Questions? Leslie Johnston lesliej@loc.gov