Archival HTTP Archival HTTP Redirection Retrieval Redirection Retrieval Policies Policies Temporal Web Analytics Workshop 2013, Rio De Janiro Ahmed AlSum , Michael L. Nelson Old Dominion University Norfolk VA, USA {aalsum,mln}@cs.odu.edu Robert Sanderson, Herbert Van de Sompel Los Alamos National Laboratory Los Alamos NM, USA {rsanderson,herbertv}@lan l.gov
25
Embed
Archival HTTP Redirection Retrieval Policies Temporal Web Analytics Workshop 2013, Rio De Janiro Ahmed AlSum, Michael L. Nelson Old Dominion University.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Current Wayback Current Wayback Machine PolicyMachine Policy
Policy one: Policy one: URI-R with HTTP URI-R with HTTP
redirectionredirection
Retrieve the memento M for R.
Status(M) =200
Status(M) =3xx
Stop
Go to Policy 2
Stop
Yes
Yes
Yes No
No
No
Policy one: Policy one: URI-R with HTTP URI-R with HTTP
redirectionredirection• 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
Policy two: Policy two: URI-M with HTTP URI-M with HTTP
redirectionredirection
http://www.cnn.com/
Accept-Datetime: Sun, 13 May 2006 http://www.cnn.com/
Policy two: Policy two: URI-M with HTTP URI-M with HTTP
redirectionredirection• 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 cases
ConclusionConclusion• 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.