I'm trying to see if I can lump my response to some of the responses above.
Glad to see so much conversation around this.
We've considered setting up VMs, but even that can be quite costly,
especially if a project is or becomes dormant. Developing a sustainable
container is certainly necessary.
I agree with both Tom and Stuart. It is an easy problem to solve from a
technology standpoint. It is, or least can be, a difficult one from a
management standpoint. If institutional support is there figuring out the
technology is easy. In this case, I'd start investigating the technology part
On 18/05/13 01:51, Tim McGeary wrote:
There is no easy answer for this, so I'm looking for discussion.
- Should we begin considering a cooperative project that focuses on
emulation, where we could archive projects that emulate the system
environment they were built?
- Do we set
That doesn't sound like an easy answer at all! Given that we all try to
play nice with institutional funding, all you've said is that in an ideal
world some other group will have a similar mandate. It doesn't get us (in
all seriousness) anywhere. Hopefully our institutions have higher
preservation
Hi all,
It would also be great to discuss earlier non-internet DH projects (e.g.,
works designed as interactive CDs). At UF, I'm co-chair of the campus-wide
Data Management/Curation Task Force (Libraries, Research Computing, and
Office of Research) and we're data gathering on the range of
I'm interested in starting or joining discussions about best practices for
on-going support for digital library projects. In particular, I'm looking
at non-repository projects, such as projects built on applications like
Omeka. In the repository context, there are initiatives like APTrust and
Good questions.
I'm a programmer for a project lasting 4 years which will create quite a
few web applications with uncertain future once the project ends.
So what I have in mind is something like graceful degradation of these
services. E.g. most of these apps make use of a javascript mapping
On May 17, 2013, at 9:51 AM, Tim McGeary wrote:
I'm interested in starting or joining discussions about best practices for
on-going support for digital library projects. In particular, I'm looking
at non-repository projects, such as projects built on applications like
Omeka. In the
These are good questions. Digital humanities centers have been dealing
with these questions as they've accumulated projects, and sometimes they
have dumped them on libraries to try to preserve. Leslie Johnston has
experience with this, which she summarized recently:
Kevin Hawkins writes
Digital humanities centers have been dealing with these questions as
they've accumulated projects, and sometimes they have dumped them on
libraries to try to preserve.
dumped maybe but I would still try to see this as an opportunity
for libraries to move into a
On Fri, May 17, 2013 at 7:14 AM, Robert Forkel xrotw...@googlemail.com wrote:
Good questions.
Or
once the web framework is no longer supported, there should be an export
mechanism to create a set of static resources which can be hosted with just
a webserver.
Completely agree. This should be
11 matches
Mail list logo
