8 Mar
2011
8 Mar
'11
2:15 p.m.
<http://collectiveaccess.org/>
Its open source (GPLv2) software for cataloging collections. Does
anyone have any experience with it?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
8 Mar
8 Mar
2:59 p.m.
On 3/8/11 2:15 PM, Richard wrote:
Its open source (GPLv2) software for cataloging
collections.
From a quick look at it, it's php/mySQL based, and seems to cover all the basics of
collections management and catalog exporting.
Seems like a good place to start, though it appears to deal mostly with physical objects,
and knows about physical pathnames in
the catalog records, so that's a little dangerous. It has minimal support for digital
asset management.
3:09 p.m.
In article <4D76B4CC.3050004 at bitsavers.org>,
Al Kossow <aek at bitsavers.org> writes:
Seems like a good place to start, though it appears to
deal mostly
with physical objects, and 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.
It has minimal support for digital asset management.
They seem to provide a mechanism for customizing the base
functionality with installation profiles. They list a bunch of
installation profiles that are already created that provide metadata
for digital media and other applications here:
<http://www.collectiveaccess.org/support/library>
Does that cover digital asset management as you see it?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
3:57 p.m.
On 3/8/11 3:09 PM, Richard wrote:
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.
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 archive
when it is stored in a normal database.
When something is put into a repository, it should (in theory) be impossible to change
or delete it. Working with real storage media makes this an impossibility.
It should also be replicated, and all of the copies periodically verified that haven't
changed.
This is VERY different from the model that a normal database works under, that records
are constantly created, deleted, and modified.
9 Mar
9 Mar
9:47 a.m.
In article <4D76C27D.803 at bitsavers.org>,
Al Kossow <aek at bitsavers.org> writes:
archive
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.
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
to
change
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
t
records
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
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?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
10:22 a.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.
10:41 a.m.
In article <4D77C55F.5040008 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
>> We ran into a problem where image paths were
hardcoded with windows pathna
mes,
which causes the OSX version of the client to fail.
Was this encountered while using CollectiveAccess?
clients deal with pathnames the same way and it might
be a problem if someone
would use
this in a heterogeneous environment.
OK, I'll keep an eye out for this with CA. I'm going to start
experimenting with CollectiveAccess. When I was at the Living
Computer Museum, Rich Alderson mentioned a program called PastPerfect.
I looked at it and the vendor lock-in feel to it put me off. Plus it
costs money and only ran on Windows. CA is a web application, so I
can leverage data backup plans from a web hosting service instead of
having to maintain my own backups. Also, being an open source PHP
application I can host it on classiccmp.org for minimal expense. With
an open source PHP application I have the option of contributing
extnesions that address problems in the vintage computing domain and
share them with others.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
10:52 a.m.
On 3/9/11 10:41 AM, Richard wrote:
Also, being an open source PHP
application I can host it on classiccmp.org for minimal expense. With
an open source PHP application I have the option of contributing
extnesions that address problems in the vintage computing domain and
share them with others.
Seems like a good starting point for classiccmp hosted collections databases
in the future.
I assume they already deal with public/private visibility of collection assets.
You should check with Jay, though on the backup policies on classiccmp before
starting any major projects there, though.
11:05 a.m.
In article <4D77CC68.7000309 at bitsavers.org>,
Al Kossow <aek at bitsavers.org> writes:
I assume they already deal with public/private
visibility of collection assets.
I believe I read in their documentation that they have some support
for this.
You should check with Jay, though on the backup
policies on classiccmp before
starting any major projects there, though.
Yep, that thought occurred to me as well.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
11:17 a.m.
Also, the CollectiveAccess folks have a good wiki that goes into
detail on a lot of these issues:
<http://wiki.collectiveaccess.org/index.php?title=Main_Page>
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
10:23 a.m.
At 11:47 AM 3/9/2011, Richard wrote:
Al Kossow <aek at bitsavers.org> writes:
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
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? 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
10:45 a.m.
In article <201103091828.p29ISdff090465 at billY.EZWIND.NET>,
John Foust <jfoust at threedee.com> writes:
I'd like to see how [CollectiveAccess] handles the
intranet and
Internet sides of its interface.
From what I've read so far, it appears that both
sides use the same
database and are different web applications. There also appears
to be
a user/role facility so that you can manage who can do what with the
database. They also use this in some extensions to integrate into
social networking sites, i.e. once logged in a user can 'like'
something into a social network like facebook, or can create their own
personal collections from stuff in your catalog, possibly even
extending the catalog with their own items. I think I'm going to
build out a cheap linux box at home for experimenting with all this
stuff in an environment where I have total control. Then once I'm
confident in what I'd like, I'm going to deploy to classiccmp.org.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
5037
days inactive
5038
days old
11 comments
3 participants
participants (3)
-
aek＠bitsavers.org -
jfoust＠threedee.com -
legalize＠xmission.com