sustainability, storage, and presentation

[deborah]

YES YES YES. An excellent post by Dorothea at Book of Trogool, inspired by Dan Cohen, about sustainability and chasing the shiny.

As I've had occasion to mention, scholars generally and humanists in particular have a terrible habit of chasing the shiny. [...]

The answer to this conundrum is not, however, "avoid the shiny at all costs!" It can't be. That will only turn scholars away from archiving and archivists. To my mind, this means that our systems have to take in the data and make it as easy as possible for scholars to build shiny on top of it. When the shiny tarnishes, as it inevitably will, the data will still be there, for someone else to build something perhaps even shinier.

Mark me well, incidentally: it is unreasonable and unsustainable to expect data archivists to build a whole lot of project-specific shiny stuff. You don't want your data archivists spending their precious development cycles doing that! You want your archivists bothering about machine replacement cycles, geographically-dispersed backups, standards, metadata, access rights, file formats, auditing and repair, and all that good work.

---

YES. We need to be working well with the people responsible for interfaces -- but we need not to be building those interfaces ourselves. (Hopefully, I will soon have exciting news about a project that follows these guidelines. I'm not going to make an announcement until we have it right, though. *g*)

Comments

[libskrat]

*blush*

Also, PROJECT!

We have a Drupal-Fedora collaboration thing going at my shop based on half-written code from another uni. (Use Islandora? Which is heavily-tested production code? Nooooooooooo, we can't do that -- cavlec suggested it, so it's clearly out of the question! Don't get me started...)

Something's wrong on their end. Our dev came to see me and said "I really don't think we need to be mucking around in PHP. They need to fix whatever their deal is." I said "Right behind you, man."

[deborah]

I have to say, more and more I keep thinking "Wow, I wish we hadn't been on the bleeding edge, because then I would love to use Islandora." Now we have functionality which is too far beyond it, but it also has functionality we need. I kind of want to take it apart and glue parts of it into our infrastructure.