This post is a recent, non-confidential internal memo I wrote to a co-worker as a sort of post-mortem on a long-term digital preservation project. Although its in very rough form, and alludes to some things that won’t make sense to those outside of Cornell University Library, (and I tend to be pretty loose in how I deal with topics, such as the relationship between performance and scalability for example, and I assume some familiarity with certain technologies), I thought there might be enough meat hear to interest others working in the area of digital preservation.
A Possible Way Forward For Developing Cornell’s OAIS Infrastructure
Categories:
Related Post
Blog Comments Considered Harmful?Blog Comments Considered Harmful?
Like many software developers, Joel Spolsky's blog "Joel on Software" has been in my RSS aggregator for several years now. I don't always agree with what he says, but I
A Potential Confusion When Converting HABTM Relationships to has_many :through.A Potential Confusion When Converting HABTM Relationships to has_many :through.
As someone relatively new to Ruby on Rails, I managed to confuse myself on one of my Rails projects recently when I decided to follow some very logical advice in
EXPLORING TERNARY ASSOCIATIONS IN RUBY ON RAILSEXPLORING TERNARY ASSOCIATIONS IN RUBY ON RAILS
Consider the following problem domain. We have users, projects as well as roles and rights. Often, users are assigned roles and roles are assigned rights in straightforward binary associations: [rights]