2015
DOI: 10.1007/s00799-015-0140-8
|View full text |Cite
|
Sign up to set email alerts
|

The impact of JavaScript on archivability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
18
1

Year Published

2015
2015
2021
2021

Publication Types

Select...
3
3
2

Relationship

4
4

Authors

Journals

citations
Cited by 21 publications
(20 citation statements)
references
References 33 publications
1
18
1
Order By: Relevance
“…As measured in our prior work [12], the resources in the Archive-It set receive an HTTP 200 response for 93.5 % of all requests for embedded resources and the resources in the Twitter set receive an HTTP 200 response for 87.1 % of all requests for embedded resources.…”
Section: Dataset Selectionmentioning
confidence: 87%
See 2 more Smart Citations
“…As measured in our prior work [12], the resources in the Archive-It set receive an HTTP 200 response for 93.5 % of all requests for embedded resources and the resources in the Twitter set receive an HTTP 200 response for 87.1 % of all requests for embedded resources.…”
Section: Dataset Selectionmentioning
confidence: 87%
“…This experiment uses the same set of 2,000 URI-Rs as in our previous work [12], which was sampled from Twitter and Archive-It. The first dataset, the Twitter set, consists of 1,000 Bitly URIs shared over Twitter and represents a more random selection of URI-Rs not explicitly selected for curation by human archivists.…”
Section: Dataset Selectionmentioning
confidence: 99%
See 1 more Smart Citation
“…Because the turkers identified m0 in the m0 vs m1 in 81% of the comparisons, we used turkers to evaluate our mea- This experiment uses the same set of 2,000 URI-Rs as in our previous work [6], which was sampled from Twitter and Archive-It. The first dataset, the Twitter set, consists of Bitly URIs shared over Twitter.…”
Section: Evaluating Organic Damagementioning
confidence: 99%
“…Archive.is, Mummify, Perma.cc and WebCitation (see Table 1), all provide URI submission and archive browsing services with obfuscated URIs, though none make accessible a resultant WARC file. Brunelle et al [6] highlighted the difficulties that current archival crawlers have with capturing content on the live web that relies on JavaScript, and Kelly et al [7] showed the ramifications this has had on preserving web pages over time. Brunelle pointed out that sometimes what archives show as preserved actually "reaches out" into the live web on replay, causing false positives [8].…”
Section: Related Workmentioning
confidence: 99%