At 11:47 AM 3/9/2011, Richard wrote:
Al Kossow <aek at bitsavers.org> writes:
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?
Yes, this puzzled me, too. You'd think this would've been a primary
consideration of any design.
I've added CA to my get-around-to-it list, as it looks interesting enough
to solve my own organization problems as well as that of the local
historical society. I'd like to see how it handles the intranet and
Internet sides of its interface. I'd like to see how it handles
storage - are all files expected to be under a particular folder
from the perspective of which server? Can objects be
distributed?
Offline?
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?
I'd be happy with verification and an audit trail.
- John