Posts

Showing posts with the label SiteStory

2016-05-31: Can I find this story? API: Yes, Google: Maybe, Native Search: No

Image
A story on Storify titled: "Lecture on Academic Freedom"  (capture date: 2016-05-31) The story on Storify titled: "Lecture on Academic Freedom" could not be found on Google   (capture date: 2016-05-31) The story on Storify titled: "Lecture on Academic Freedom" could not be found on Storify native search  (capture date: 2016-05-31) A part of our research ( funded by IMLS ) to build collections for stories or events involves exploring content curation sites like Storify  in order to determine if they hold quality (news worthy, timely, etc.) content. Storify is a social network service used to create stories which consists of text and multimedia content, as well as content from other social media sites like Twitter , Facebook and Instagram . Our exploration involved collecting stories from Storify over a period in other to manually inspect the stories to determine their newsworthiness. This exploration was dual natured: we col...

2012-08-31: Benchmarking LANL's SiteStory

Image
On August 17th, 2012, Los Alamos National Laboratory's Herbert Van de Sompel announced the release of the anticipated transactional web archiver called SiteStory . Very excited to announce the release of our SiteStory transactional archive solution # memento mementoweb.github.com/SiteStory/ — Herbert (@hvdsomp) August 17, 2012 The ODU WS-DL research group (in conjunction with The MITRE Corporation ) performed a series of studies to measure the effect of the SiteStory on web server performance. We found that SiteStory does not significantly affect content server performance when it is performing transactional archiving. Content server performance slows from 0.076 seconds to 0.086 seconds per Web page access when the content server is under load, and from 0.15 seconds to 0.21 seconds when the resource has many embedded and changing resources. A sneak-peek at how SiteStory affects server performance is provided below. Please see the technical report for a full descri...