We just tried to track a master and derivatives. Tools like documentum can automate some types of versions. If I ever get the chance, I'm going to see what I can do with a standard version control system like git and standardized branching. But until then, as far as I know this is untested (and VCS systems are not at their best maintaining info about binary files).
ari > On Jul 21, 2015, at 7:47 PM, Emma Jones <[email protected]> wrote: > > I would like to get an idea of who out there has found a way to manage > multiple versions of a single object in their collections. No so much > multiple examples of the same object, rather versions of the same one. As > our photographs collection has built up over the last 100 odd years, a > variety of versions have been created of the one object for preservation, > access and other reasons. However we tend to have the "one catalogue record > to rule them all", which sadly does not truly reflect our holdings. There are > a number of ideas being put forward, but it would be great to hear how other > institutions have/haven't tackled this issue, especially in regard to how you > represent these versions in your CMS (we have XG). > Thanks > Emma > > Emma Jones > Manager, Collection Information and Access team | Collection Services > [email protected]<mailto:[email protected]> | t 02 62434476 > Australian War Memorial | GPO Box 345 Canberra ACT 2601 | www.awm.gov.au > > [AWM Logo not displayed in text email] > > ________________________________________________________________________________________________________________ > > This message may contain confidential information and is intended only for > its recipient(s). If you have received this email by error, please delete > this e-mail from your system and notify the sender immediately. E-mail > transmission cannot be guaranteed to be secure. E-mail information could be > intercepted, corrupted, lost, destroyed, arrive late, be incomplete, or > contain viruses. The sender therefore does not accept liability for any > errors or omissions in the contents of this message. > > ________________________________________________________________________________________________________________ > _______________________________________________ > You are currently subscribed to mcn-l, the listserv of the Museum Computer > Network (http://www.mcn.edu) > > To post to this list, send messages to: [email protected] > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/[email protected]/ _______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: [email protected] To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/[email protected]/
