[MCN-L] Can a CIS be a DAMS too?

2006-07-07 Thread Trudy Levy
I don't entirely disagree with Nick, especially on a practical level. I did
not intend to support one system for all. Though I see the different needs
impacting more in terms of how the information is used rather than the
structure of the data "buckets." I find it interesting that this topic is
being discussed on the list servs  - imagelib, vra and mcn in different ways
at this time.  I guess because of that I would like to think there is a way
to get Dublin Core to stretch to fit all,  so all would have a common
starting pointing. 

That would make for easier integration of the various programs that retrieve
and present the information.

Trudy
-- 

Trudy Levy
Consultant for Digital Imaging Projects

Image Integration 415 750 1274http://www.DIG-Mar.com
Membership Chair, Visual Resources Association  http://vraweb.org
Images are information - Manage them


On 7/7/06 12:22 PM, "Nik Honeysett"  wrote:

> IMHO, I think it is a mistake to expect a single system to do both the job of
> a CIS and DAM well, for the good reasons that are discussed in this thread. I
> would look long and hard at any vendor who claimed a system that did, or
> claimed to be able to build a system that did. These systems do very different
> things, but there are crucial points of intersection and the principle of
> best-of-breed is one that should be applied here. Meet your institution's
> needs separately for each system with the additional requirement of the
> ability to integrate at the appropriate points for each. I would rather be in
> the position of going to a software developer to develop the integration of
> two applications, than the ground-up development of a complex application like
> this. Consider too, that both vendors may partner in the development of some
> integration software that would enhance their product.
> 
> Modularity and interoperability are key componants to a sustainable
> infrastructure for the management of digital resources in all their forms, and
> don't be swaid by the perceived cost-saving of a single system.
> 
> My 2 cents.
> 
> -nik
> 
> Nik Honeysett
> Manager, Web Group
> J. Paul Getty Trust
> tel: 310-440-7346
> fax: 310-440-7704
> nhoneysett at getty.edu
> 
> 
 Trudy at dig-mar.com 07/06/06 1:50 PM >>>
> I have been loving this discussion, especially as I , along with Maureen
> Burns, are moderating a Panel at the Pasadena Conference on Taming the Many
> Headed DAM.  This panel is the result of questions raised at my workshop on
> Managing a DAM in Boston, regarding just this issue.
> One thing I think is important to consider as far as one stop solutions go
> is that the managing of the data ( images and metadata) may be one solution,
> but you still might want for different inputs and output solutions if only
> in terms of user interfaces.
> The problem in the single solution for data managing seems to be data
> structuring.  I wonder if we could take a fresh look at Dublin Core for more
> specialized uses, such as how the VRA Core and CCO are tweaking it to work
> with cultural objects.  Might there not also be a cross walkable Core for
> Publishing, exhibits, archives. Etc?
> Maybe the RLG's   Museum Collections Sharing Working
> Group, could add to their list?
> Guenter? *,-)
> 
> Trudy Levy





[MCN-L] Can a CIS be a DAMS too?

2006-07-07 Thread Nik Honeysett
IMHO, I think it is a mistake to expect a single system to do both the job of a 
CIS and DAM well, for the good reasons that are discussed in this thread. I 
would look long and hard at any vendor who claimed a system that did, or 
claimed to be able to build a system that did. These systems do very different 
things, but there are crucial points of intersection and the principle of 
best-of-breed is one that should be applied here. Meet your institution's needs 
separately for each system with the additional requirement of the ability to 
integrate at the appropriate points for each. I would rather be in the position 
of going to a software developer to develop the integration of two 
applications, than the ground-up development of a complex application like 
this. Consider too, that both vendors may partner in the development of some 
integration software that would enhance their product.

Modularity and interoperability are key componants to a sustainable 
infrastructure for the management of digital resources in all their forms, and 
don't be swaid by the perceived cost-saving of a single system.

My 2 cents.

-nik

Nik Honeysett
Manager, Web Group
J. Paul Getty Trust
tel: 310-440-7346
fax: 310-440-7704
nhoneysett at getty.edu


>>> Trudy at dig-mar.com 07/06/06 1:50 PM >>>
I have been loving this discussion, especially as I , along with Maureen
Burns, are moderating a Panel at the Pasadena Conference on Taming the Many
Headed DAM.  This panel is the result of questions raised at my workshop on
Managing a DAM in Boston, regarding just this issue.
One thing I think is important to consider as far as one stop solutions go
is that the managing of the data ( images and metadata) may be one solution,
but you still might want for different inputs and output solutions if only
in terms of user interfaces.
The problem in the single solution for data managing seems to be data
structuring.  I wonder if we could take a fresh look at Dublin Core for more
specialized uses, such as how the VRA Core and CCO are tweaking it to work
with cultural objects.  Might there not also be a cross walkable Core for
Publishing, exhibits, archives. Etc?
Maybe the RLG's   Museum Collections Sharing Working
Group, could add to their list?
Guenter? *,-)

Trudy Levy
-- 

Trudy Levy
Consultant for Digital Imaging Projects

Image Integration 415 750 1274http://www.DIG-Mar.com 
Membership Chair, Visual Resources Association  http://vraweb.org 
Images are information - Manage them





On 7/3/06 9:19 AM, "Quigley"  wrote:

> ooops try this instead for Fedora...  very interesting... Suzanne
> Quigley
> 
>   www.fedora.info 
> 
> Suzanne Quigley
> 
> 
> On Jul 3, 2006, at 12:02 PM, Morgan, Matt wrote:
> 
>> On 6/30/06 10:01 AM, "" <> wrote:
>> 
>>> Hi Matt,
>>> 
>>> I'm curious about where the drive is coming from to have a "one stop
>>> solution" mean there's one system under it all.   I often feel sorry
>>> for the folks at Past Perfect when I see comments elsewhere about why
>>> doesn't it also do accounting, POS,  and your taxes on top of already
>>> managing museum collections, archives, libraries, and membership.  I
>>> think it juliennes potatoes too.
>> 
>> I didn't mean to argue that CIS's /should/ offer DAMS-type
>> services. I just
>> think it's a common hope.
>> 
>> I was surprised to realize this when it came to DAMS, but museums
>> are the
>> DAMS vendors' most demanding customers. For example, the number of
>> them that
>> can satisfy Deborah's hierarchy demands even partially (or with
>> difficult
>> workarounds) is pretty few. You would think that big real estate
>> companies
>> (region, city, neighborhood, street, house, room--just guessing but
>> you get
>> the idea), for example, might have similar needs. But I guess
>> they're not
>> using DAMS yet, or they're not being very demanding.
>> 
>> So given the unlikelihood that a top-notch CIS vendor, really
>> specialized in
>> that field, could also become a first-rate DAMS vendor, I think the
>> one-stop
>> solution is not going to happen.
>> 
>>> 
>>> Colleges and universities are working to build institutional
>>> repositories (IR) to capture "grey literature' on campuses, and some
>>> of these solutions may be adaptable to building digital repositories
>>> of non-collection materials in a museum, as you suggest - CAD
>>> drawings, exhibit scripts, PR copy, etc.
>> 
>> I have seen some custom software vendors looking at Fedora
>> (http://fedora.us) as a back-end for a combined (physical and
>> digital) asset
>> management solution. It certainly meets all the storage & organization
>> requirements, and with an easier-to-use UI layer it could work.
>> 
>>> 
>>> The challenge of course, is that sometimes these materials are
>>> related to objects in a CIS, or images in DAM.   As I suggested to
>>> Dianne, the question may be, how do we build more open systems that
>>> allow interaction between different functions.
>> 
>> That is definitely the right approach!
>> 
>> Tha