We had a masters student (Amine) working on Brass for quite some time, and over the last few months I've been overhauling the interface and tightening up the security. (I'm sure there's still some holes in it, but it's much better than it used to be!)
Below is a screen shot of the opening interface.
After submitting the requested info, the user is sent a confirmation email (to avoid recovering websites for bots). Once the user confirms the request, the job is queued and later dispatched to a free machine. The user is emailed when the job completes, and then the user can download the recovered set of files from the lost website.
Go ahead and give it a spin, and let me know if you have any problems.
*By the way, the really cool Warrick logo was created by two graphic design majors at Harding: Andrew Murray and Luke Jones.
Interesting. I can see a cached copy containing scripts, html files, and images, but a database? That's the key for any sites I make (and most made today).
ReplyDeleteAn interesting application of caching sites.
Allan- The problem with web archives and search engine caches (the Web Infrastructure, as I call it), is that it can't store the server components (scripts, databases, etc.) of a website. But I've developed a method where the server components are actually injected into the WI so they can be recovered, and I'm currently running an experiment as a proof-of-concept. I'll probably write about in the next few months.
ReplyDelete