anyone using collectiveaccess for their collections?
legalize at xmission.com
Wed Mar 9 11:47:57 CST 2011
In article <4D76C27D.803 at bitsavers.org>,
Al Kossow <aek at bitsavers.org> writes:
> On 3/8/11 3:09 PM, Richard wrote:
> > knows about physical pathnames in the
> >> 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.
> We ran into a problem where image paths were hardcoded with windows pathnames,
> which causes the OSX version of the client to fail.
Was this encountered while using CollectiveAccess?
> > Does that cover digital asset management as you see it?
> No, it is the issue of maintaining the integrity of the contents of a digital
> when it is stored in a normal database.
> When something is put into a repository, it should (in theory) be impossible
> or delete it. Working with real storage media makes this an impossibility.
> It should also be replicated, and all of the copies periodically verified tha
t haven't changed.
> This is VERY different from the model that a normal database works under, tha
> are constantly created, deleted, and modified.
OK, so if I understand you correctly, you're talking about maintaining
an audit trail for every digital media item entered into the
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?
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
More information about the cctalk