Git is a great tool for tracking software code, and versions of various
projects. It's critical to keeping various versions of our media resources
as we move forward. However, git doesn't handle large files like video,
graphics, and binary code very well. So I've been doing some initial
experiments
Great questions! We're wondering about storing and archiving older
interactives that have older dependencies. Many of our interactives were
built in old versions of Adobe Director exclusively compatible with Windows
XP and older QuickTime binaries, and some run inside old Apache/Tomcat
installation
n, 14 Jul 2013 10:51:16 -0700
From: Perian mailto:per...@emphatic.org>>
To: Museum Computer Network Listserv mailto:mcn-l at mcn.edu>>
Subject: [MCN-L] Managing retention of digital projects
Message-ID: <51E2E514.5080401 at emphatic.org<mailto:51E2E514.5080401 at
empha
he at hotmail.com
> From: BarbaraP at PHM.GOV.AU
> To: mcn-l at mcn.edu
> Date: Sun, 14 Jul 2013 23:42:19 +
> Subject: Re: [MCN-L] Managing retention of digital projects
>
> I'd like to put in a 'me too' for this one. I know we can archive most things
> i
hibited. If you receive this email in
error, please delete it and any attachments.
-Original Message-
From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of
Perian
Sent: Monday, 15 July 2013 3:51 AM
To: Museum Computer Network Listserv
Subject: [MCN-L] Managing reten
Something I've been trying to wrap my head around lately is what happens
with all of the mobile tours, old exhibition websites, PSD and InDesign
projects, Final Cut Project files, gallery kiosk displays, touchtable,
etc. once we're done with them. It seems to me that we're the one
industry, wit
