9 Mar
2011
9 Mar
'11
1:22 p.m.
On 3/9/11 9:47 AM, Richard wrote:
In article<4D76C27D.803 at bitsavers.org>,
Al Kossow<aek at bitsavers.org> writes:
No, this was with Mimsy, the system CHM uses. I just pointed this out to note that not
all
clients deal with pathnames the same way and it might be a problem if someone would use
this in a heterogeneous environment.
On 3/8/11 3:09 PM, Richard wrote:
Was this encountered while using CollectiveAccess?
knows about physical pathnames in the
We ran into a problem where image paths were hardcoded with windows pathnames,
which causes the OSX version of the client to fail. catalog records, so that's a little
dangerous.
Can you elaborate on this? I'm not sure I understand what you mean by
this comment.
OK, so if I understand you correctly, you're
talking about maintaining
an audit trail for every digital media item entered into the
collection?
Sort of like a source code control system where code is never really
"deleted" because you can go back in the history and recover it?
Not quite. Once entered into a digital repository, the contents of the 'blob'
never
changes, so you can use this fact to verify what it contains is invariant by recomputing
the check mechanism (MD5, etc.) and making sure they match on all known copies.
For more details, see my last message.