Archival HTTP Redirection Retrieval Policies - TemporalWeb 2013
Upcoming SlideShare
Loading in...5
×
 

Archival HTTP Redirection Retrieval Policies - TemporalWeb 2013

on

  • 1,627 views

This is my presentation in TemporalWeb 2013 workshop collocated with WWW 2013

This is my presentation in TemporalWeb 2013 workshop collocated with WWW 2013

Statistics

Views

Total Views
1,627
Views on SlideShare
481
Embed Views
1,146

Actions

Likes
0
Downloads
4
Comments
0

34 Embeds 1,146

http://eventifier.co 541
http://ws-dl.blogspot.com 407
http://ws-dl.blogspot.de 31
http://ws-dl.blogspot.ch 18
http://ws-dl.blogspot.co.uk 18
http://ws-dl.blogspot.in 15
http://ws-dl.blogspot.ca 13
https://twitter.com 12
http://ws-dl.blogspot.nl 9
http://ws-dl.blogspot.fr 9
http://192.168.1.2 6
http://ws-dl.blogspot.com.br 5
http://ws-dl.blogspot.it 5
http://ws-dl.blogspot.kr 5
http://ws-dl.blogspot.pt 5
http://ws-dl.blogspot.no 4
http://ws-dl.blogspot.gr 4
http://ws-dl.blogspot.com.au 4
http://ws-dl.blogspot.jp 4
http://ws-dl.blogspot.com.es 3
http://ws-dl.blogspot.co.il 3
http://ws-dl.blogspot.tw 3
http://eventifier.com 3
http://ws-dl.blogspot.hk 3
http://ws-dl.blogspot.dk 3
http://ws-dl.blogspot.co.nz 2
http://translate.googleusercontent.com 2
http://ws-dl.blogspot.se 2
http://ws-dl.blogspot.co.at 2
http://ws-dl.blogspot.ro 1
http://www.ws-dl.blogspot.co.uk 1
http://ws-dl.blogspot.ru 1
http://localhost 1
http://newsblur.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Archival HTTP Redirection Retrieval Policies - TemporalWeb 2013 Archival HTTP Redirection Retrieval Policies - TemporalWeb 2013 Presentation Transcript

  • Archival HTTP RedirectionRetrieval PoliciesTemporal Web Analytics Workshop 2013, Rio De JaniroAhmed AlSum,Michael L. NelsonOld Dominion UniversityNorfolk VA, USA{aalsum,mln}@cs.odu.eduRobert Sanderson,Herbert Van de SompelLos Alamos National LaboratoryLos Alamos NM, USA{rsanderson,herbertv}@lanl.gov1
  • Agenda• Introduction• Abstract Model• Experiment And Results• Retrieval Policies2
  • Memento TerminologyURI-R, RURI-M, MURI-T, TMhttp://www.amazon.comhttp://web.archive.org/web/20110411070244/http://amazon.comOriginal ResourceMementoTimeMap3
  • Live Redirecthttp://bit.ly/r9kIfC redirects to http://www.cs.odu.edu% curl -I http://bit.ly/r9kIfCHTTP/1.1 301 Moved….Location: http://www.cs.odu.edu/…4
  • Live Redirecthttp://bit.ly/r9kIfC redirects to http://www.cs.odu.edu5
  • Archived Redirectwww.draculathemusical.co.ukredirectswww.dracula-uk.com/index.htmlhttp://api.wayback.archive.org/memento/20020212194020/http://www.draculathemusical.co.uk/Archived redirectshttp://api.wayback.archive.org/memento/20020212194020/http://www.geocities.com/draculathemusicalhttp://api.wayback.archive.org/memento/20020212194020/http://www.geocities.com/draculathemusical6
  • Abstract Model7
  • Abstract ModelM1 M2 M38
  • URI Stability• URI’s stability is a count of the change in HTTPresponses across time (200, 3xx, or 4xx) and thenumber of different URIs in the “Location” for 3xxstatus code.High Stability = 1 No Stability = 09
  • Timemap Redirection Categories• Category 1All Mementos have 200 HTTP status code10
  • Timemap Redirection Categories• Category 2All Mementos have redirection to the same URI.11
  • Timemap Redirection Categories• Category 3All Mementos have redirection to different URIs.12
  • Timemap Redirection Categories• Category 4Mementos have different HTTP status code.13
  • Timemap Redirection CategoriesAll Mementos have 200 HTTP status code All Mementos have redirection to the same URI.All Mementos have redirection to different URIs. Mementos have different HTTP status code.14
  • URI ReliabilityM13xxM23xxM33xxrel=originalR`Mrel=originalR`Mrel=originalR`M? ? ?200 404 3xx15
  • HTTP Redirection Relationshipbetween URI-R & URI-MLive Web URI − ROK RedirectionWeb ArchiveURI-MOK Case 1 5Redirection 2 3,4Case 1Case 2 Case 3 Case 4 Case 516
  • Experiment & Results17
  • Experiment• Dataset: 10,000 sample URIs from• Dataset doesn’t have bit.ly nor doi.• Experiment foucsed on the root page (no embeddedresources)HTTP Status/Code (10,000 URI-R)OK (200) 82.83%Redirection (3xx) 14.71%Redirection (301) 8.4%Redirection (302) 6.1%Redirection (others) 0.2%Not-Found (4xx) 1.18%Others 1.28%HTTP Status/Code (894,717 URI-M)OK (200) 93.46%Redirection (3xx) 5.69%Not-Found (4xx) 0.26%Others 0.59%URIs Live HTTP status code Memento HTTP status code18
  • Time span Number of Mementos19
  • URI StabilityTimeMap Category Percentage StabilityAll Mementos have OK 52% 1Mementos have mix status code 36% 0.91All Mementos have Redirection 0.92% 0.85Redirection to the same URI 0.62%Redirection to different URIs 0.30%URI has no Mementos at all 10.97% 0Stability in semi-log scale Stability for |TM(R)| < 300 20
  • URI Reliability• 23% of the mementos did not lead to a successfulmemento at the end.Reliabilityin semi-log scale Reliabilityfor |TM(R)| < 30021
  • HTTP Redirection Relationshipbetween URI-R & URI-MLive Web URI − ROK RedirectionWeb ArchiveURI-MOK Case 1 5Redirection 2 3,4Case 1Case 2 Case 3 Case 4 Case 580.8%2.74% 1.34%1.33%13.7%22
  • RETRIEVAL POLICIESARCHIVED HTTP REDIRECTION RETRIEVAL POLICIES23
  • Current WaybackMachine Policy24
  • Policy one:URI-R with HTTP redirectionRetrieve the memento M for R.Status(M) =200Status(M) =3xxStopGo to Policy 2StopYesYesYes NoNoNo25
  • Policy one:URI-R with HTTP redirection• Evaluation:o Policy scope has: 1471 URIs (that have live redirection)o 77 out of 1471 have no mementos at allo 17 out of 77 have been retrieved mementos based on live redirection• Implementation26Tool CommentMementoFox v 9.6+mcurl v 1.0IA Wayback Machine For bit.ly URIs only
  • Policy two:URI-M with HTTP redirectionhttp://www.cnn.com/Accept-Datetime: Sun, 13 May 2006http://www.cnn.com/27
  • Policy two:URI-M with HTTP redirection• Evaluation:o Policy scope: 2980 TimeMap (that showed HTTP redirection status code in at least one memento)o Success criteria: Using policy two contributed to the original TimeMapo Success percentage: 58% of the cases28
  • Conclusion• Quantitative study with 10,000 URIs.• 48% were not fully stable through time.• 27% were not perfectly reliable through time.• New archival retrieval policy:o Policy one: successfully retreived mementos for17 out of 77o Policy two: Expanded the timemap for 58% of cases.• aalsum@cs.odu.edu• @aalsum29