1. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
Uniform Access to Raw Mementos
Herbert Van de Sompel1, Michael L. Nelson2, Lyudmila Balakireva1,
Martin Klein1, Shawn M. Jones1, Harihar Shankar1
{@hvdsomp, @phonedude_mln, N/A, @mart1nkle1n,
@shawnmjones, @hariharshankar}
1Research Library
Los Alamos National Laboratory
2Computer Science Department
Old Dominion University

2. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
2
• Most web archives augment their Mementos with
• Custom banners
• Rewritten links
Status Quo

3. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
3

4. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
4
 Such Mementos do not represent the resource’s state at
the time of capture.
 “Rawness” is needed for
 Research evaluating original content
 Replay systems e.g., Memento Reconstruct
 Approaches to guarantee veracity of archived content
Problem

5. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
5
• Clients have to be aware of archive-specific implementation
• URI patterns used to convey levels of rawness:
• http://somearchive.org/{datetime}im_/URI-R
• http://somearchive.org/{datetime}id_/URI-R
• Supported by OpenWayback and pywb instances
Current Workaround

6. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
6

7. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
7
Option #1
Request header sent against TimeGate
Proposal: Use of Prefer Header in HTTP Request

8. Uniform Access to Raw Mementos
@mart1nkle1n
IIPC WAC, 06/16/2017, London, UK
8
Option #2
Request header sent against Memento
Proposal: Use of Prefer Header in HTTP Request