3 ms·
Easy: get a bunch of DVD drives and a ~1 Gbps uplink. 2000 4.7GB single layer DVDs in three working days is about 870Mbps. Upload them as you rip to S3 and th
by amluto 8y ago
Easy: get a bunch of DVD drives and a ~1 Gbps uplink. 2000 4.7GB single layer DVDs in three working days is about 870Mbps. Upload them as you rip to S3 and then send a pull request!
https://github.com/awslabs/open-data-registry/ https://github.com/awslabs/open-data-registry/
- rconti 8y agoSo the 3 days is for figuring out how to use git, then?
- halis 8y agolmao
- briffle 8y agoobligatory xkcd: https://xkcd.com/1597/ https://xkcd.com/1597/ If anything is out of your few commands, just save work elsewhere, delete the project, and download a fresh copy.
- tracker1 8y agoI've, frankly, done that many times at this point... when your merge request gets too wonky, it's just easier. I do try to remember to squash, then rebase generally, though there are times I just forget or mess up.
- rconti 8y agoWhen in doubt, "how does the team here handle these conflicts? At my old job we just did <made up thing> to solve it, I've forgotten the process here."
- reaperducer 8y agoEasy: get a bunch of DVD drives and a ~1 Gbps uplink. Can you detail how one easily gets a 1 gigabit uplink installed temporarily in the National Archives? I've had telcos drop fiber into the middle of fields in the middle of nowhere, so it's probably possible. But it feels like there's a lot of complicated bureaucracy to navigate, and the researcher OP is time-restricted.
- nathancahill 8y agoSneaker shuttle the SSDs from the National Archives to your friends apartment with the uplink.
- amluto 8y agosigh No one got the joke. I’m suggesting that the DVD’s should be submitted as an AWS public dataset, because Amazon is the company that digitized them in the first place, and the content is apparently public domain.