- The document discusses how the author spends their summer vacations studying the archivability of web resources by capturing 1,000 URIs each from Twitter and Archive-It. - The author analyzes the captured data to measure how perfectly the resources were archived, finding only 4.2% of Twitter and 34.2% of Archive-It were perfectly archived, with missing embedded resources, stylesheets, and functionality impacting the archivability. - The author plans future work evaluating the importance of missing elements, measuring damage to archives, and developing methods to predict and potentially improve archivability.

1. How I spend my summer
vacations
Justin F. Brunelle
WS-DL Research Group
Department of Computer Science
Old Dominion University
WADL 2013

2. Justin in a nutshell
• PhD Student at ODU
• Dynamic representations
–in the archives
–Improved quality from
–archived data
–Alter-ego: Application Developer
• at The MITRE Corporation
–Big data & cloud computing

3. How much can we archive?

4. The setup
• 1,000 URIs from Twitter
• 1,000 URIs from Archive-it
• Capture with tools
• Study the archivability

5. Good

6. Good

7. Good

8. Meh…
Zombies in the Archives

9. Bad

10. Bad

11. Bad

12. Bad

13. Bad

14. Why?

15. Losing the Moment
• What we share != What we curate
• 4.2% of Twitter is perfectly archived
–Losing My Revolution: 11% gone in 2 years
• 34.2% of Archive-it is perfectly archived
• Accessibility? Gov vs. non-Gov?

16. Measuring memento damage

17. VS.

18. Not all embedded resources are
created equal

19. Not all embedded resources are
created equal

20. Planned Work
• Evaluate importance of missing stuff
–Size, position
–# CSS Classes
–Not all stylesheets created equal
– Missing border vs missing functionality
– “Whitespace”
–Provide Web service
• Mechanical Turk evaluation of “damage”
• Evaluate collections of mementos

21. What does it all mean?
• Archivability is measurable
• Damage is measurable
• If we can predict archivability….
–We can try new methods of archiving on “hard to
capture” mementos
–Attempt repairs on existing mementos
–Gauge our successes in real-time
• Next step: capturing dynamic content