Hacker News new | past | comments | ask | show | jobs | submit login

One problem with digital databases: What if the electricity goes out for a very long time? Or a nefarious hacker manages to destroy the database? (Or all librarians' terminals are locked by NotPetya...)

Library without catalog is, while not totally worthless, much more difficult to use.

The physical card catalog, like other paper-based archives, is more resistant to attacks. For it to be destroyed, you need to cause physical damage, like a giant flood or tornado or hit it with explosives.

See: https://www.raphkoster.com/2017/06/27/the-internet-as-existe...

I hope that at least the national libraries and archives will maintain physical backups for the worst-case scenarios.




If the electricity is out for a very long time I imagine that's not isolated to the library and people will have much larger problems to worry about.

If a hacker manages to destroy the database, well it's a good thing backups are cheap these days and it doesn't take a trained IT person to implement them. Even Crashplan or Carbonite, or just periodically copying files to an external drive and then disconnecting it would probably do the job. If libraries have the money for hundreds of pounds of paper cards and the cabinets to store them in, plus labor to maintain all of that, they surely have the money for functional-if-basic backup infrastructure.

I'm all for securing critical infrastructure with analog systems/subsystems, but the only argument I could see for doing so with libraries is if said library is in the developing world where electricity is intermittent.


>If the electricity is out for a very long time I imagine that's not isolated to the library and people will have much larger problems to worry about.

Well, yes. But a library rendered unusable is also a major problem, in the long run. And especially if it's not just the local library, but all of them in the country?

I would probably need to read the book in question to be able to do Fermi estimates on what kind of amounts of paper and space the old system would need. But if one already has the "this is a backup system for very rare, very worst-case events, not for active use" viewpoint, one is free to do changes and optimizations. For example, miniaturized analogue backup from which the full-blown card system can be reproduced if the need arises.


What do you mean by "in the long run"? Because a library being rendered unusable for a definite length of time wouldn't be a problem in the long run unless we're talking about a system with path dependence. And even if there is some path dependence, it's not quite obvious whether or not that's a major problem. For example, not being able to lend a book during a few hours could be only thing preventing some terminally-ill genius from solving some elusive mathematical problem before he dies, while everyone else can just try to check their books some other day when the power is back on. But so long as the problem can be solved, the solution might be found out later on by someone else.

On the other hand, if libraries are rendered unusable for an indefinite amount of time, or if they become so unreliable that they aren't even worth the effort, those would always be an issue regardless of whether there's path-dependence.

But it sounds somewhat far-fetched to create system to ensure the reliability of libraries in the event of say, a massive solar flare. Plus, it misses the point: in the event of something able to take out something crucial to the entire US library system for any appreciable length of time, the librarians themselves would most likely have far more pressing concerns in their hands. And that would be our new single point of failure.

I pretty much agree with scottLobster. Unless we're talking about developing countries, where electric power is not so much intermitent as unreliable - whereas it might take a hurricane to cause power outages in other countries, a gush of wind here will do - it makes sense to have a system like this in place.


>Plus, it misses the point: in the event of something able to take out something crucial to the entire US library system for any appreciable length of time, the librarians themselves would most likely have far more pressing concerns in their hands. And that would be our new single point of failure.

I'm not exactly sure if I'm following you, but the general idea of this kind of "resilience" is to introduce enough safety / backup measures at all points in the society so that there is less things that hinge on "single point of failure".

The scenario I had in mind was a national grid of a much smaller country going down. (Apparently bringing up all the power plants back online is not as straightforward operation as flipping some switches 'on'.) For example, in conjunction with other crisis (say, conventional war with cyberattack component) that would turn out to taking much longer than anticipated (because aren't they all "over by Christmas"), so there might be an adversary interested in keeping it down.

And the libraries are not the only institutions handling critical data that used to be stored on paper but now exist on computers. The particular solution of retaining backup paper card system might be silly or otherwise prove infeasible at closer inspection, but what kind of backup systems the current institutions have?

edit. Looking at the rest of the comments, smkellat might have provided a splendidly simple answer upthread. At least, concerning libraries.


Frankly you get the cataloger(s) out of their office/cubicle/holding pen, sit the cataloger(s) down at the reference desk, and have them work from memory guiding people through the classification system. You won't have the same level of granularity in searching but by general subject you'll be able to get to where you're looking to go. Been there, done that, wrote the plan while I was Cataloger for a community college in an area at risk for tsunamis. Those call numbers are there for a reason and have very important meanings.


Samr can happen to physical cards too. Wear and tear, flood, fire, theft, vandalism. Also, its difficult to create copies of physical as compared to digital. The upside of digital is also that you can and should have multiple backups, same as any other digital data.


>For it to be destroyed, you need to cause physical damage

However, I'd like to have redundancy. Backups. Library catalogs are quite critical when it comes to using the combined amount of information the humankind has amassed: It's critical infrastructure. We maintain also backups for things like seeds [1].

You would need just an automated machinery to create printout backups once in a while. It does not necessarily have to be exactly the same system as the old catalogs, just enough that something exists and is ready to use after the rare catastrophic failure.

[1] https://en.wikipedia.org/wiki/Svalbard_Global_Seed_Vault


So, you are saying the library should store some solar panels and spare computers somewhere?

Creating electricity to run a computer is not really that difficult.


I do a feel a bit silly about not considering this. (Okay, the feasibility of solar depends on the local climate. But alternative local methods to generate electricity exist.)

It even also provides some form of resilience that I was calling for: assuming there is a backup system, less-electricity dependent functionality could be recreated if it's considered a worthwhile option.


> Or a nefarious hacker manages to destroy the database

offsite backups?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: