talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

CAP 5.5 + CS

AS
Angela Spinazze
Wed, Feb 22, 2012 4:47 PM

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow afternoon
to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace development
schedule set through September 2012 http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0
and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would be
involved in this process. It seems like it could be really close if
it is just a matter of exposing the CS doc types in the DM
interface. What are the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org, <talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not entirely sure
what to recommend bumping. For us, and I suspect most of the current
implementers, the multi-tenant service isn't as big an issue, but I
know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and Movement
rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet <richard.millet@berkeley.edu

wrote:
Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo’s DM and DAM
applications.  Unfortunately, this work is not currently scheduled
to happen anytime soon.  However, we understand the value of
CollectionSpace being able to co-exist with Nuxeo’s applications.
If you feel we need to make this work a higher priority, please
review the current release roadmaps and see how this work compares
to what we have planned.  If you decide this work is more
important, let us know and we can try to raise its priority.

-Richard

From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] On Behalf Of Charlie Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing CS
+DM+DAM all on the same postgres database. I am attaching two
screenshots of the results. There are only a few errors during the
DM+DAM startup, but things seem to run well enough. There appears
to be promise. Two glaring things are that the "default-domain"
that is normally part of the top-level of DM is missing. Looking
inside each CS domain shows a workspace for each type, but they are
empty. I would hope that it is only a matter of adding the proper
Nuxeo extensions to expose these types to the DM interface. Any
insight the development team has would be interesting. In the mean
time I believe we are going to relate our DM documents to
placeholders documents. The prospect of creating relationship
between DM documents and CS ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman <chris.hoffman@berkeley.edu

Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we’re also in the process of defining our requirements
for a DAM solution and as a part of this process have also tested
an earlier Nuxeo DAM version. It was basic, but seemed fast and
stable in the short period we tested it. Relating texts and
documents to artworks is also a pressing use case for us – although
Ihope we can integrate this into CollectionSpace either through the
Media Handling procedure by supporting some new document types
(pdf, doc, html etc.) or possibly even by creating a new procedure
for handling related texts. In any case I look forward to following
your investigations.

Regards,
(another) Chris

Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] På vegne af Charlie Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select group of
staff members for several months now with decent success. We found
the previous versions of DAM lacking some very basic needs and many
of those have been addressed in the latest release. We even paid
for the development of some of those enhancements. In general Nuxeo
DAM is fairly simple, but that's all that we (and I suspect many
museums) need. We need it to be able to handle and preview media
files and relate them to our institution. I'm not entirely sure
what the effort would be and if much additional work would be
required. That's why I reached out. I'll continue to investigate
this and come back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org" talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the way you
describe.  The Nuxeo DAM has seemed like a good way to go, but we
haven't really experimented with it here.  What's your experience
been like?  Anyway, we'll happily endorsethis too.  And if it's
something that looks like it needs another grant-funded project to
do right, maybe we could get our institutions to partner on
something.  Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but
it would be pretty powerful to have a single repository for the
sole purpose of relating documents to collection objects,
exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org, <talk@lists.collectionspace.org

Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as many
folks have expressed at least some interest in this. We have also
been assured by the Nuxeo folks that this should be possible. At
this point, it is mostly a matter of resources and priorities. If
the community rallies support for this as an essential integration,
we should be able to find time in the Phase 3 project to
investigate it.

Note that we are otherwise interested in getting the DM working as
a diagnostic and support tool, and to aid with import/export
workflows. As such, there may be some basic investigation (not
necessarily including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on a
related thread.

Thanks for the question -

Patrick

From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] On Behalf Of Charlie Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository running
the new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace
2.0 in a single repository? I would like to be able to relate
documents to works in our collection. Any guidance would be greatly
appreciated.

Thanks,
Charlie
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Charlie, Patrick, Megan and I will be discussing this work tomorrow afternoon to determine just what is required and we will follow up on this thread once we've had a chance to explore this in more detail. As Richard pointed out, we have our core CollectionSpace development schedule set through September 2012 http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule We do however, realize how important this functionality is to many community members. Thanks very much for keeping this conversation alive! Angela On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > It would help to know if someone could express what would be > involved in this process. It seems like it could be really close if > it is just a matter of exposing the CS doc types in the DM > interface. What are the complicating factors beyond that? > > - Charlie > > From: Nate Solas <nate.solas@walkerart.org> > Date: Tue, 21 Feb 2012 11:52:38 -0600 > To: Richard Millet <richard.millet@berkeley.edu> > Cc: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org > > > Subject: Re: [Talk] CAP 5.5 + CS > > I'd like to +1 a raised priority for this, but I'm not entirely sure > what to recommend bumping. For us, and I suspect most of the current > implementers, the multi-tenant service isn't as big an issue, but I > know it's core to the long-term sustainability of the software. > > It seems like there might be some room for this work in the 2.3 > roadmap? I don't know how big a chunk the Location and Movement > rewrite is. > > Thanks for considering it. This would be huge for us, and it sounds > like there is a lot of support out there. > Nate > > > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet <richard.millet@berkeley.edu > > wrote: >> Charlie, >> >> Thanks for experimenting with this. One of our known tasks is to >> ensure that CollectionSpace can co-exist with Nuxeo’s DM and DAM >> applications. Unfortunately, this work is not currently scheduled >> to happen anytime soon. However, we understand the value of >> CollectionSpace being able to co-exist with Nuxeo’s applications. >> If you feel we need to make this work a higher priority, please >> review the current release roadmaps and see how this work compares >> to what we have planned. If you decide this work is more >> important, let us know and we can try to raise its priority. >> >> -Richard >> >> >> From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >> ] On Behalf Of Charlie Moad >> Sent: Thursday, February 16, 2012 7:14 PM >> To: Christopher Pott; Chris Hoffman >> Cc: talk@lists.collectionspace.org >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> I haven't had much time, but I took a naïve attempt at installing CS >> +DM+DAM all on the same postgres database. I am attaching two >> screenshots of the results. There are only a few errors during the >> DM+DAM startup, but things seem to run well enough. There appears >> to be promise. Two glaring things are that the "default-domain" >> that is normally part of the top-level of DM is missing. Looking >> inside each CS domain shows a workspace for each type, but they are >> empty. I would hope that it is only a matter of adding the proper >> Nuxeo extensions to expose these types to the DM interface. Any >> insight the development team has would be interesting. In the mean >> time I believe we are going to relate our DM documents to >> placeholders documents. The prospect of creating relationship >> between DM documents and CS ones feels close though. >> >> - Charlie >> >> From: Christopher Pott <Christopher.Pott@smk.dk> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman <chris.hoffman@berkeley.edu >> > >> Cc: <talk@lists.collectionspace.org> >> Subject: SV: [Talk] CAP 5.5 + CS >> >> Hi Charlie, >> >> Here at SMK we’re also in the process of defining our requirements >> for a DAM solution and as a part of this process have also tested >> an earlier Nuxeo DAM version. It was basic, but seemed fast and >> stable in the short period we tested it. Relating texts and >> documents to artworks is also a pressing use case for us – although >> Ihope we can integrate this into CollectionSpace either through the >> Media Handling procedure by supporting some new document types >> (pdf, doc, html etc.) or possibly even by creating a new procedure >> for handling related texts. In any case I look forward to following >> your investigations. >> >> Regards, >> (another) Chris >> >> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >> ] På vegne af Charlie Moad >> Sendt: 4. januar 2012 22:48 >> Til: Chris Hoffman >> Cc: talk@lists.collectionspace.org >> Emne: Re: [Talk] CAP 5.5 + CS >> >> At the IMA we are just in the process of rolling out the new DAM >> software based on 5.5. We have been using DM with a select group of >> staff members for several months now with decent success. We found >> the previous versions of DAM lacking some very basic needs and many >> of those have been addressed in the latest release. We even paid >> for the development of some of those enhancements. In general Nuxeo >> DAM is fairly simple, but that's all that we (and I suspect many >> museums) need. We need it to be able to handle and preview media >> files and relate them to our institution. I'm not entirely sure >> what the effort would be and if much additional work would be >> required. That's why I reached out. I'll continue to investigate >> this and come back with progress I might have. >> >> - Charlie >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 >> To: Charles Moad <cmoad@imamuseum.org> >> Cc: "talk@lists.collectionspace.org" <talk@lists.collectionspace.org> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> Hi Charlie, >> >> At UC Berkeley, we have a very strong need to connect collections >> management and digital assetmanagement functions in the way you >> describe. The Nuxeo DAM has seemed like a good way to go, but we >> haven't really experimented with it here. What's your experience >> been like? Anyway, we'll happily endorsethis too. And if it's >> something that looks like it needs another grant-funded project to >> do right, maybe we could get our institutions to partner on >> something. Just thinking out loud... >> >> Thanks, >> Chris >> >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >> >> >> Thanks for following up Patrick. I'll rally my friends. I wouldn't >> expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but >> it would be pretty powerful to have a single repository for the >> sole purpose of relating documents to collection objects, >> exhibitions, etc. >> >> Keep up the good work, >> Charlie >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 >> To: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org >> > >> Subject: RE: [Talk] CAP 5.5 + CS >> >> Hi Charlie - >> >> This is something we would really like to investigate, as many >> folks have expressed at least some interest in this. We have also >> been assured by the Nuxeo folks that this should be possible. At >> this point, it is mostly a matter of resources and priorities. If >> the community rallies support for this as an essential integration, >> we should be able to find time in the Phase 3 project to >> investigate it. >> >> Note that we are otherwise interested in getting the DM working as >> a diagnostic and support tool, and to aid with import/export >> workflows. As such, there may be some basic investigation (not >> necessarily including DAM/CSpace coordination) in the near term. >> >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI >> any time soon, as this is not ause-case that anyone (else) has yet >> requested. Am not ruling it out, just giving my impression of the >> current project priorities, in response to yourquestion on a >> related thread. >> >> Thanks for the question - >> >> Patrick >> >> >> From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >> ] On Behalf Of Charlie Moad >> Sent: Wednesday, January 04, 2012 6:18 AM >> To: talk@lists.collectionspace.org >> Subject: [Talk] CAP 5.5 + CS >> >> What is the feasibility of setting up a single repository running >> the new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace >> 2.0 in a single repository? I would like to be able to relate >> documents to works in our collection. Any guidance would be greatly >> appreciated. >> >> Thanks, >> Charlie >> This email message is for the sole use of the intended recipient(s) >> and may contain confidential and privileged information. Any >> unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact Charlie Moad >> by reply email and destroy all copies of the original message. >> >> This email message is for the sole use of the intended recipient(s) >> and may contain confidential and privileged information. Any >> unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact Charlie Moad >> by reply email and destroy all copies of the original message. >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> This email message is for the sole use of the intended recipient(s) >> and may contain confidential and privileged information. Any >> unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact Charlie Moad >> by reply email and destroy all copies of the original message. >> >> This email message is for the sole use of the intended recipient(s) >> and may contain confidential and privileged information. Any >> unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact Charlie Moad >> by reply email and destroy all copies of the original message. >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact Charlie Moad > by reply email and destroy all copies of the original message. > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AS
Angela Spinazze
Fri, Feb 24, 2012 9:31 PM

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread (January 4th)
"Note that we are otherwise interested in getting the DM working as a
diagnostic and support tool, and to aid with import/export workflows.
As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we will include
investigation into the effort required to do so in the scope of work
for the release 2.3 (scheduled to begin on March 5th).  Based on what
we discover in the research phase, we will determine if/when the work
might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow afternoon
to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace development
schedule set through September 2012 http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0
and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this conversation
alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would be
involved in this process. It seems like it could be really close if
it is just a matter of exposing the CS doc types in the DM
interface. What are the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org, <talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not entirely
sure what to recommend bumping. For us, and I suspect most of the
current implementers, the multi-tenant service isn't as big an
issue, but I know it's core to the long-term sustainability of the
software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and Movement
rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet <richard.millet@berkeley.edu

wrote:
Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo’s DM and DAM
applications.  Unfortunately, this work is not currently scheduled
to happen anytime soon.  However, we understand the value of
CollectionSpace being able to co-exist with Nuxeo’s applications.
If you feel we need to make this work a higher priority, please
review the current release roadmaps and see how this work compares
to what we have planned.  If you decide this work is more
important, let us know and we can try to raise its priority.

-Richard

From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] On Behalf Of Charlie Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two
screenshots of the results. There are only a few errors during the
DM+DAM startup, but things seem to run well enough. There appears
to be promise. Two glaring things are that the "default-domain"
that is normally part of the top-level of DM is missing. Looking
inside each CS domain shows a workspace for each type, but they
are empty. I would hope that it is only a matter of adding the
proper Nuxeo extensions to expose these types to the DM interface.
Any insight the development team has would be interesting. In the
mean time I believe we are going to relate our DM documents to
placeholders documents. The prospect of creating relationship
between DM documents and CS ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman <chris.hoffman@berkeley.edu

Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we’re also in the process of defining our requirements
for a DAM solution and as a part of this process have also tested
an earlier Nuxeo DAM version. It was basic, but seemed fast and
stable in the short period we tested it. Relating texts and
documents to artworks is also a pressing use case for us –
although Ihope we can integrate this into CollectionSpace either
through the Media Handling procedure by supporting some new
document types (pdf, doc, html etc.) or possibly even by creating
a new procedure for handling related texts. In any case I look
forward to following your investigations.

Regards,
(another) Chris

Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] På vegne af Charlie Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select group
of staff members for several months now with decent success. We
found the previous versions of DAM lacking some very basic needs
and many of those have been addressed in the latest release. We
even paid for the development of some of those enhancements. In
general Nuxeo DAM is fairly simple, but that's all that we (and I
suspect many museums) need. We need it to be able to handle and
preview media files and relate them to our institution. I'm not
entirely sure what the effort would be and if much additional work
would be required. That's why I reached out. I'll continue to
investigate this and come back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the way you
describe.  The Nuxeo DAM has seemed like a good way to go, but we
haven't really experimented with it here.  What's your experience
been like?  Anyway, we'll happily endorsethis too.  And if it's
something that looks like it needs another grant-funded project to
do right, maybe we could get our institutions to partner on
something.  Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but
it would be pretty powerful to have a single repository for the
sole purpose of relating documents to collection objects,
exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org, <talk@lists.collectionspace.org

Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as many
folks have expressed at least some interest in this. We have also
been assured by the Nuxeo folks that this should be possible. At
this point, it is mostly a matter of resources and priorities. If
the community rallies support for this as an essential
integration, we should be able to find time in the Phase 3 project
to investigate it.

Note that we are otherwise interested in getting the DM working as
a diagnostic and support tool, and to aid with import/export
workflows. As such, there may be some basic investigation (not
necessarily including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on a
related thread.

Thanks for the question -

Patrick

From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org
] On Behalf Of Charlie Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository running
the new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace
2.0 in a single repository? I would like to be able to relate
documents to works in our collection. Any guidance would be
greatly appreciated.

Thanks,
Charlie
This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please contact Charlie Moad by reply email and destroy all copies
of the original message.

This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please contact Charlie Moad by reply email and destroy all copies
of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please contact Charlie Moad by reply email and destroy all copies
of the original message.

This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please contact Charlie Moad by reply email and destroy all copies
of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact Charlie Moad
by reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi all, A brief update for you on this Nuxeo DM question. As Patrick mentioned in an earlier post to this thread (January 4th) "Note that we are otherwise interested in getting the DM working as a diagnostic and support tool, and to aid with import/export workflows. As such, there may be some basic investigation (not necessarily including DAM/CSpace coordination) in the near term." Given the level of interest in and the potential positive impact of getting the DM working as a diagnostic support tool, we will include investigation into the effort required to do so in the scope of work for the release 2.3 (scheduled to begin on March 5th). Based on what we discover in the research phase, we will determine if/when the work might be scheduled to take place within the current schedule. We'll be creating a new Jira for this investigation effort so that everyone who is interested can keep an eye on our progress. Cheers, Angela On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: > Hi Charlie, > > Patrick, Megan and I will be discussing this work tomorrow afternoon > to determine just what is required and we will follow up on this > thread once we've had a chance to explore this in more detail. > > As Richard pointed out, we have our core CollectionSpace development > schedule set through September 2012 http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 > and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule > > We do however, realize how important this functionality is to many > community members. Thanks very much for keeping this conversation > alive! > > Angela > > > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > >> It would help to know if someone could express what would be >> involved in this process. It seems like it could be really close if >> it is just a matter of exposing the CS doc types in the DM >> interface. What are the complicating factors beyond that? >> >> - Charlie >> >> From: Nate Solas <nate.solas@walkerart.org> >> Date: Tue, 21 Feb 2012 11:52:38 -0600 >> To: Richard Millet <richard.millet@berkeley.edu> >> Cc: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org >> > >> Subject: Re: [Talk] CAP 5.5 + CS >> >> I'd like to +1 a raised priority for this, but I'm not entirely >> sure what to recommend bumping. For us, and I suspect most of the >> current implementers, the multi-tenant service isn't as big an >> issue, but I know it's core to the long-term sustainability of the >> software. >> >> It seems like there might be some room for this work in the 2.3 >> roadmap? I don't know how big a chunk the Location and Movement >> rewrite is. >> >> Thanks for considering it. This would be huge for us, and it sounds >> like there is a lot of support out there. >> Nate >> >> >> On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet <richard.millet@berkeley.edu >> > wrote: >>> Charlie, >>> >>> Thanks for experimenting with this. One of our known tasks is to >>> ensure that CollectionSpace can co-exist with Nuxeo’s DM and DAM >>> applications. Unfortunately, this work is not currently scheduled >>> to happen anytime soon. However, we understand the value of >>> CollectionSpace being able to co-exist with Nuxeo’s applications. >>> If you feel we need to make this work a higher priority, please >>> review the current release roadmaps and see how this work compares >>> to what we have planned. If you decide this work is more >>> important, let us know and we can try to raise its priority. >>> >>> -Richard >>> >>> >>> From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >>> ] On Behalf Of Charlie Moad >>> Sent: Thursday, February 16, 2012 7:14 PM >>> To: Christopher Pott; Chris Hoffman >>> Cc: talk@lists.collectionspace.org >>> >>> Subject: Re: [Talk] CAP 5.5 + CS >>> >>> >>> I haven't had much time, but I took a naïve attempt at installing >>> CS+DM+DAM all on the same postgres database. I am attaching two >>> screenshots of the results. There are only a few errors during the >>> DM+DAM startup, but things seem to run well enough. There appears >>> to be promise. Two glaring things are that the "default-domain" >>> that is normally part of the top-level of DM is missing. Looking >>> inside each CS domain shows a workspace for each type, but they >>> are empty. I would hope that it is only a matter of adding the >>> proper Nuxeo extensions to expose these types to the DM interface. >>> Any insight the development team has would be interesting. In the >>> mean time I believe we are going to relate our DM documents to >>> placeholders documents. The prospect of creating relationship >>> between DM documents and CS ones feels close though. >>> >>> - Charlie >>> >>> From: Christopher Pott <Christopher.Pott@smk.dk> >>> Date: Wed, 11 Jan 2012 14:35:34 +0100 >>> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman <chris.hoffman@berkeley.edu >>> > >>> Cc: <talk@lists.collectionspace.org> >>> Subject: SV: [Talk] CAP 5.5 + CS >>> >>> Hi Charlie, >>> >>> Here at SMK we’re also in the process of defining our requirements >>> for a DAM solution and as a part of this process have also tested >>> an earlier Nuxeo DAM version. It was basic, but seemed fast and >>> stable in the short period we tested it. Relating texts and >>> documents to artworks is also a pressing use case for us – >>> although Ihope we can integrate this into CollectionSpace either >>> through the Media Handling procedure by supporting some new >>> document types (pdf, doc, html etc.) or possibly even by creating >>> a new procedure for handling related texts. In any case I look >>> forward to following your investigations. >>> >>> Regards, >>> (another) Chris >>> >>> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >>> ] På vegne af Charlie Moad >>> Sendt: 4. januar 2012 22:48 >>> Til: Chris Hoffman >>> Cc: talk@lists.collectionspace.org >>> Emne: Re: [Talk] CAP 5.5 + CS >>> >>> At the IMA we are just in the process of rolling out the new DAM >>> software based on 5.5. We have been using DM with a select group >>> of staff members for several months now with decent success. We >>> found the previous versions of DAM lacking some very basic needs >>> and many of those have been addressed in the latest release. We >>> even paid for the development of some of those enhancements. In >>> general Nuxeo DAM is fairly simple, but that's all that we (and I >>> suspect many museums) need. We need it to be able to handle and >>> preview media files and relate them to our institution. I'm not >>> entirely sure what the effort would be and if much additional work >>> would be required. That's why I reached out. I'll continue to >>> investigate this and come back with progress I might have. >>> >>> - Charlie >>> >>> From: Chris Hoffman <chris.hoffman@berkeley.edu> >>> Date: Wed, 4 Jan 2012 13:39:36 -0800 >>> To: Charles Moad <cmoad@imamuseum.org> >>> Cc: "talk@lists.collectionspace.org" >>> <talk@lists.collectionspace.org> >>> Subject: Re: [Talk] CAP 5.5 + CS >>> >>> Hi Charlie, >>> >>> At UC Berkeley, we have a very strong need to connect collections >>> management and digital assetmanagement functions in the way you >>> describe. The Nuxeo DAM has seemed like a good way to go, but we >>> haven't really experimented with it here. What's your experience >>> been like? Anyway, we'll happily endorsethis too. And if it's >>> something that looks like it needs another grant-funded project to >>> do right, maybe we could get our institutions to partner on >>> something. Just thinking out loud... >>> >>> Thanks, >>> Chris >>> >>> >>> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >>> >>> >>> Thanks for following up Patrick. I'll rally my friends. I wouldn't >>> expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but >>> it would be pretty powerful to have a single repository for the >>> sole purpose of relating documents to collection objects, >>> exhibitions, etc. >>> >>> Keep up the good work, >>> Charlie >>> >>> From: Patrick Schmitz <pschmitz@berkeley.edu> >>> Date: Wed, 4 Jan 2012 10:33:48 -0800 >>> To: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org >>> > >>> Subject: RE: [Talk] CAP 5.5 + CS >>> >>> Hi Charlie - >>> >>> This is something we would really like to investigate, as many >>> folks have expressed at least some interest in this. We have also >>> been assured by the Nuxeo folks that this should be possible. At >>> this point, it is mostly a matter of resources and priorities. If >>> the community rallies support for this as an essential >>> integration, we should be able to find time in the Phase 3 project >>> to investigate it. >>> >>> Note that we are otherwise interested in getting the DM working as >>> a diagnostic and support tool, and to aid with import/export >>> workflows. As such, there may be some basic investigation (not >>> necessarily including DAM/CSpace coordination) in the near term. >>> >>> I doubt very much that CSpace will appear as a tab in the Nuxeo UI >>> any time soon, as this is not ause-case that anyone (else) has yet >>> requested. Am not ruling it out, just giving my impression of the >>> current project priorities, in response to yourquestion on a >>> related thread. >>> >>> Thanks for the question - >>> >>> Patrick >>> >>> >>> From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org >>> ] On Behalf Of Charlie Moad >>> Sent: Wednesday, January 04, 2012 6:18 AM >>> To: talk@lists.collectionspace.org >>> Subject: [Talk] CAP 5.5 + CS >>> >>> What is the feasibility of setting up a single repository running >>> the new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace >>> 2.0 in a single repository? I would like to be able to relate >>> documents to works in our collection. Any guidance would be >>> greatly appreciated. >>> >>> Thanks, >>> Charlie >>> This email message is for the sole use of the intended >>> recipient(s) and may contain confidential and privileged >>> information. Any unauthorized review, use, disclosure or >>> distribution is prohibited. If you are not the intended recipient, >>> please contact Charlie Moad by reply email and destroy all copies >>> of the original message. >>> >>> This email message is for the sole use of the intended >>> recipient(s) and may contain confidential and privileged >>> information. Any unauthorized review, use, disclosure or >>> distribution is prohibited. If you are not the intended recipient, >>> please contact Charlie Moad by reply email and destroy all copies >>> of the original message. >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> This email message is for the sole use of the intended >>> recipient(s) and may contain confidential and privileged >>> information. Any unauthorized review, use, disclosure or >>> distribution is prohibited. If you are not the intended recipient, >>> please contact Charlie Moad by reply email and destroy all copies >>> of the original message. >>> >>> This email message is for the sole use of the intended >>> recipient(s) and may contain confidential and privileged >>> information. Any unauthorized review, use, disclosure or >>> distribution is prohibited. If you are not the intended recipient, >>> please contact Charlie Moad by reply email and destroy all copies >>> of the original message. >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >> This email message is for the sole use of the intended recipient(s) >> and may contain confidential and privileged information. Any >> unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact Charlie Moad >> by reply email and destroy all copies of the original message. >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Fri, Feb 24, 2012 9:41 PM

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread (January 4th) "Note
that we are otherwise interested in getting the DM working as a diagnostic
and support tool, and to aid with import/export workflows. As such, there
may be some basic investigation (not necessarily including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of getting
the DM working as a diagnostic support tool, we will include investigation
into the effort required to do so in the scope of work for the release 2.3
(scheduled to begin on March 5th).  Based on what we discover in the
research phase, we will determine if/when the work might be scheduled to
take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that everyone
who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow afternoon to
determine just what is required and we will follow up on this thread once
we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace development
schedule set through September 2012
http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0
 and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule

We do however, realize how important this functionality is to many community
members. Thanks very much for keeping this conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would be involved in
this process. It seems like it could be really close if it is just a matter
of exposing the CS doc types in the DM interface. What are the complicating
factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org, talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not entirely sure what to
recommend bumping. For us, and I suspect most of the current implementers,
the multi-tenant service isn't as big an issue, but I know it's core to the
long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3 roadmap? I
don't know how big a chunk the Location and Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds like
there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known tasks is to ensure
that CollectionSpace can co-exist with Nuxeo’s DM and DAM applications.
Unfortunately, this work is not currently scheduled to happen anytime soon.
However, we understand the value of CollectionSpace being able to co-exist
with Nuxeo’s applications.  If you feel we need to make this work a higher
priority, please review the current release roadmaps and see how this work
compares to what we have planned.  If you decide this work is more
important, let us know and we can try to raise its priority.

-Richard

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Charlie Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two screenshots
of the results. There are only a few errors during the DM+DAM startup, but
things seem to run well enough. There appears to be promise. Two glaring
things are that the "default-domain" that is normally part of the top-level
of DM is missing. Looking inside each CS domain shows a workspace for each
type, but they are empty. I would hope that it is only a matter of adding
the proper Nuxeo extensions to expose these types to the DM interface. Any
insight the development team has would be interesting. In the mean time I
believe we are going to relate our DM documents to placeholders documents.
The prospect of creating relationship between DM documents and CS ones feels
close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we’re also in the process of defining our requirements for a
DAM solution and as a part of this process have also tested an earlier Nuxeo
DAM version. It was basic, but seemed fast and stable in the short period we
tested it. Relating texts and documents to artworks is also a pressing use
case for us – although Ihope we can integrate this into CollectionSpace
either through the Media Handling procedure by supporting some new document
types (pdf, doc, html etc.) or possibly even by creating a new procedure for
handling related texts. In any case I look forward to following your
investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne af Charlie Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM software
based on 5.5. We have been using DM with a select group of staff members for
several months now with decent success. We found the previous versions of
DAM lacking some very basic needs and many of those have been addressed in
the latest release. We even paid for the development of some of those
enhancements. In general Nuxeo DAM is fairly simple, but that's all that we
(and I suspect many museums) need. We need it to be able to handle and
preview media files and relate them to our institution. I'm not entirely
sure what the effort would be and if much additional work would be required.
That's why I reached out. I'll continue to investigate this and come back
with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org" talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the way you describe.
 The Nuxeo DAM has seemed like a good way to go, but we haven't really
experimented with it here.  What's your experience been like?  Anyway, we'll
happily endorsethis too.  And if it's something that looks like it needs
another grant-funded project to do right, maybe we could get our
institutions to partner on something.  Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't expect
a CollectionSpace tab in Nuxeo CAP anytime soon either, but it would be
pretty powerful to have a single repository for the sole purpose of relating
documents to collection objects, exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org, talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as many folks have
expressed at least some interest in this. We have also been assured by the
Nuxeo folks that this should be possible. At this point, it is mostly a
matter of resources and priorities. If the community rallies support for
this as an essential integration, we should be able to find time in the
Phase 3 project to investigate it.

Note that we are otherwise interested in getting the DM working as a
diagnostic and support tool, and to aid with import/export workflows. As
such, there may be some basic investigation (not necessarily including
DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI any
time soon, as this is not ause-case that anyone (else) has yet requested. Am
not ruling it out, just giving my impression of the current project
priorities, in response to yourquestion on a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Charlie Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository running the new
Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace 2.0 in a single
repository? I would like to be able to relate documents to works in our
collection. Any guidance would be greatly appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message.


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message.


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact Charlie Moad by reply email and destroy all copies
of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

DAM the torpedoes, and full speed ahead? Aron (With due apologies ... it's Friday afternoon) http://en.wiktionary.org/wiki/damn_the_torpedoes On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze <ats@atspin.com> wrote: > Hi all, > > A brief update for you on this Nuxeo DM question. > > As Patrick mentioned in an earlier post to this thread (January 4th) "Note > that we are otherwise interested in getting the DM working as a diagnostic > and support tool, and to aid with import/export workflows. As such, there > may be some basic investigation (not necessarily including DAM/CSpace > coordination) in the near term." > > Given the level of interest in and the potential positive impact of getting > the DM working as a diagnostic support tool, we will include investigation > into the effort required to do so in the scope of work for the release 2.3 > (scheduled to begin on March 5th).  Based on what we discover in the > research phase, we will determine if/when the work might be scheduled to > take place within the current schedule. > > We'll be creating a new Jira for this investigation effort so that everyone > who is interested can keep an eye on our progress. > > Cheers, > > Angela > > > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: > > Hi Charlie, > > Patrick, Megan and I will be discussing this work tomorrow afternoon to > determine just what is required and we will follow up on this thread once > we've had a chance to explore this in more detail. > > As Richard pointed out, we have our core CollectionSpace development > schedule set through September 2012 > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >  and http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule > > We do however, realize how important this functionality is to many community > members. Thanks very much for keeping this conversation alive! > > Angela > > > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > > It would help to know if someone could express what would be involved in > this process. It seems like it could be really close if it is just a matter > of exposing the CS doc types in the DM interface. What are the complicating > factors beyond that? > > - Charlie > > From: Nate Solas <nate.solas@walkerart.org> > Date: Tue, 21 Feb 2012 11:52:38 -0600 > To: Richard Millet <richard.millet@berkeley.edu> > Cc: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org> > Subject: Re: [Talk] CAP 5.5 + CS > > I'd like to +1 a raised priority for this, but I'm not entirely sure what to > recommend bumping. For us, and I suspect most of the current implementers, > the multi-tenant service isn't as big an issue, but I know it's core to the > long-term sustainability of the software. > > It seems like there might be some room for this work in the 2.3 roadmap? I > don't know how big a chunk the Location and Movement rewrite is. > > Thanks for considering it. This would be huge for us, and it sounds like > there is a lot of support out there. > Nate > > > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet > <richard.millet@berkeley.edu> wrote: >> >> Charlie, >> >> Thanks for experimenting with this.  One of our known tasks is to ensure >> that CollectionSpace can co-exist with Nuxeo’s DM and DAM applications. >> Unfortunately, this work is not currently scheduled to happen anytime soon. >> However, we understand the value of CollectionSpace being able to co-exist >> with Nuxeo’s applications.  If you feel we need to make this work a higher >> priority, please review the current release roadmaps and see how this work >> compares to what we have planned.  If you decide this work is more >> important, let us know and we can try to raise its priority. >> >> -Richard >> >> >> From: talk-bounces@lists.collectionspace.org >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Charlie Moad >> Sent: Thursday, February 16, 2012 7:14 PM >> To: Christopher Pott; Chris Hoffman >> Cc: talk@lists.collectionspace.org >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> I haven't had much time, but I took a naïve attempt at installing >> CS+DM+DAM all on the same postgres database. I am attaching two screenshots >> of the results. There are only a few errors during the DM+DAM startup, but >> things seem to run well enough. There appears to be promise. Two glaring >> things are that the "default-domain" that is normally part of the top-level >> of DM is missing. Looking inside each CS domain shows a workspace for each >> type, but they are empty. I would hope that it is only a matter of adding >> the proper Nuxeo extensions to expose these types to the DM interface. Any >> insight the development team has would be interesting. In the mean time I >> believe we are going to relate our DM documents to placeholders documents. >> The prospect of creating relationship between DM documents and CS ones feels >> close though. >> >> - Charlie >> >> From: Christopher Pott <Christopher.Pott@smk.dk> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman >> <chris.hoffman@berkeley.edu> >> Cc: <talk@lists.collectionspace.org> >> Subject: SV: [Talk] CAP 5.5 + CS >> >> Hi Charlie, >> >> Here at SMK we’re also in the process of defining our requirements for a >> DAM solution and as a part of this process have also tested an earlier Nuxeo >> DAM version. It was basic, but seemed fast and stable in the short period we >> tested it. Relating texts and documents to artworks is also a pressing use >> case for us – although Ihope we can integrate this into CollectionSpace >> either through the Media Handling procedure by supporting some new document >> types (pdf, doc, html etc.) or possibly even by creating a new procedure for >> handling related texts. In any case I look forward to following your >> investigations. >> >> Regards, >> (another) Chris >> >> ________________________________ >> Fra: talk-bounces@lists.collectionspace.org >> [mailto:talk-bounces@lists.collectionspace.org] På vegne af Charlie Moad >> Sendt: 4. januar 2012 22:48 >> Til: Chris Hoffman >> Cc: talk@lists.collectionspace.org >> Emne: Re: [Talk] CAP 5.5 + CS >> >> At the IMA we are just in the process of rolling out the new DAM software >> based on 5.5. We have been using DM with a select group of staff members for >> several months now with decent success. We found the previous versions of >> DAM lacking some very basic needs and many of those have been addressed in >> the latest release. We even paid for the development of some of those >> enhancements. In general Nuxeo DAM is fairly simple, but that's all that we >> (and I suspect many museums) need. We need it to be able to handle and >> preview media files and relate them to our institution. I'm not entirely >> sure what the effort would be and if much additional work would be required. >> That's why I reached out. I'll continue to investigate this and come back >> with progress I might have. >> >> - Charlie >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 >> To: Charles Moad <cmoad@imamuseum.org> >> Cc: "talk@lists.collectionspace.org" <talk@lists.collectionspace.org> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> Hi Charlie, >> >> At UC Berkeley, we have a very strong need to connect collections >> management and digital assetmanagement functions in the way you describe. >>  The Nuxeo DAM has seemed like a good way to go, but we haven't really >> experimented with it here.  What's your experience been like?  Anyway, we'll >> happily endorsethis too.  And if it's something that looks like it needs >> another grant-funded project to do right, maybe we could get our >> institutions to partner on something.  Just thinking out loud... >> >> Thanks, >> Chris >> >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >> >> >> >> Thanks for following up Patrick. I'll rally my friends. I wouldn't expect >> a CollectionSpace tab in Nuxeo CAP anytime soon either, but it would be >> pretty powerful to have a single repository for the sole purpose of relating >> documents to collection objects, exhibitions, etc. >> >> Keep up the good work, >> Charlie >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 >> To: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org> >> Subject: RE: [Talk] CAP 5.5 + CS >> >> Hi Charlie - >> >> This is something we would really like to investigate, as many folks have >> expressed at least some interest in this. We have also been assured by the >> Nuxeo folks that this should be possible. At this point, it is mostly a >> matter of resources and priorities. If the community rallies support for >> this as an essential integration, we should be able to find time in the >> Phase 3 project to investigate it. >> >> Note that we are otherwise interested in getting the DM working as a >> diagnostic and support tool, and to aid with import/export workflows. As >> such, there may be some basic investigation (not necessarily including >> DAM/CSpace coordination) in the near term. >> >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI any >> time soon, as this is not ause-case that anyone (else) has yet requested. Am >> not ruling it out, just giving my impression of the current project >> priorities, in response to yourquestion on a related thread. >> >> Thanks for the question - >> >> Patrick >> >> >> >> ________________________________ >> >> From: talk-bounces@lists.collectionspace.org >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Charlie Moad >> Sent: Wednesday, January 04, 2012 6:18 AM >> To: talk@lists.collectionspace.org >> Subject: [Talk] CAP 5.5 + CS >> >> What is the feasibility of setting up a single repository running the new >> Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace 2.0 in a single >> repository? I would like to be able to relate documents to works in our >> collection. Any guidance would be greatly appreciated. >> >> Thanks, >> Charlie >> ________________________________ >> >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. >> >> ________________________________ >> >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> ________________________________ >> >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. >> >> ________________________________ >> >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > ________________________________ > > This email message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. Any unauthorized review, > use, disclosure or distribution is prohibited. If you are not the intended > recipient, please contact Charlie Moad by reply email and destroy all copies > of the original message. > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >
PS
Patrick Schmitz
Fri, Feb 24, 2012 10:58 PM

Sorry to undermine your joke, but I should note that Nuxeo DM is not the
same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we used when we
had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same repo as
CSpace.

However, the scope of work in 2.3 is only to look at DM, so that support for
export and diagnostics is restored to what we had previous to 2.0. It may
well be that once we figure out how to support DM and CSpace, adding the DAM
app to the mix will be straightforward. However, integrating DAM is not a
goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of
Aron Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze
ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).  

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

 and 

+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM interface. What are
the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an issue, but I
know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo’s DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace being able to
co-exist with Nuxeo’s applications.  If you feel we need

to make this

work a higher priority, please review the current release roadmaps
and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There appears to be
promise. Two glaring things are that the "default-domain" that is
normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are empty. I
would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM documents and CS
ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we’re also in the process of defining our requirements
for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and documents to
artworks is also a pressing use case for us – although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for handling related
texts. In any case I look forward to following your investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent success. We found
the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media files and
relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the

way you describe.

 The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?  

Anyway, we'll happily endorsethis too.  And if it's something that
looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.  

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository for the sole
purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have also been
assured by the Nuxeo folks that this should be possible. At this
point, it is mostly a matter of resources and priorities. If the
community rallies support for this as an essential integration, we
should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact Charlie Moad by
reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org

Sorry to undermine your joke, but I should note that Nuxeo DM is not the same as Nuxeo DAM. Nuxeo DM is the traditional Nuxeo doc management app that we used when we had the dual-server (JBoss) setup. Nuxeo DAM is the Digital Asset Management application. We would like (eventually) to support both, integrated with the same repo as CSpace. However, the scope of work in 2.3 is only to look at DM, so that support for export and diagnostics is restored to what we had previous to 2.0. It may well be that once we figure out how to support DM and CSpace, adding the DAM app to the mix will be straightforward. However, integrating DAM is not a goal in the 2.3 release. Patrick > -----Original Message----- > From: talk-bounces@lists.collectionspace.org > [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of > Aron Roberts > Sent: Friday, February 24, 2012 1:41 PM > To: Angela Spinazze > Cc: CollectionSpace Talk List > Subject: Re: [Talk] CAP 5.5 + CS > > DAM the torpedoes, and full speed ahead? > > Aron > > (With due apologies ... it's Friday afternoon) > http://en.wiktionary.org/wiki/damn_the_torpedoes > > On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze > <ats@atspin.com> wrote: > > Hi all, > > > > A brief update for you on this Nuxeo DM question. > > > > As Patrick mentioned in an earlier post to this thread > (January 4th) > > "Note that we are otherwise interested in getting the DM > working as a > > diagnostic and support tool, and to aid with import/export > workflows. > > As such, there may be some basic investigation (not necessarily > > including DAM/CSpace > > coordination) in the near term." > > > > Given the level of interest in and the potential positive impact of > > getting the DM working as a diagnostic support tool, we > will include > > investigation into the effort required to do so in the > scope of work > > for the release 2.3 (scheduled to begin on March 5th).   Based on what > > we discover in the research phase, we will determine > if/when the work > > might be scheduled to take place within the current schedule. > > > > We'll be creating a new Jira for this investigation effort so that > > everyone who is interested can keep an eye on our progress. > > > > Cheers, > > > > Angela > > > > > > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: > > > > Hi Charlie, > > > > Patrick, Megan and I will be discussing this work tomorrow > afternoon > > to determine just what is required and we will follow up on this > > thread once we've had a chance to explore this in more detail. > > > > As Richard pointed out, we have our core CollectionSpace > development > > schedule set through September 2012 > > > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 > >  and  > > > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 > > +Proposed+Schedule > > > > We do however, realize how important this functionality is to many > > community members. Thanks very much for keeping this > conversation alive! > > > > Angela > > > > > > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > > > > It would help to know if someone could express what would > be involved > > in this process. It seems like it could be really close if > it is just > > a matter of exposing the CS doc types in the DM interface. What are > > the complicating factors beyond that? > > > > - Charlie > > > > From: Nate Solas <nate.solas@walkerart.org> > > Date: Tue, 21 Feb 2012 11:52:38 -0600 > > To: Richard Millet <richard.millet@berkeley.edu> > > Cc: Charles Moad <cmoad@imamuseum.org>, > > <talk@lists.collectionspace.org> > > Subject: Re: [Talk] CAP 5.5 + CS > > > > I'd like to +1 a raised priority for this, but I'm not > entirely sure > > what to recommend bumping. For us, and I suspect most of > the current > > implementers, the multi-tenant service isn't as big an issue, but I > > know it's core to the long-term sustainability of the software. > > > > It seems like there might be some room for this work in the 2.3 > > roadmap? I don't know how big a chunk the Location and > Movement rewrite is. > > > > Thanks for considering it. This would be huge for us, and it sounds > > like there is a lot of support out there. > > Nate > > > > > > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet > > <richard.millet@berkeley.edu> wrote: > >> > >> Charlie, > >> > >> Thanks for experimenting with this.  One of our known tasks is to > >> ensure that CollectionSpace can co-exist with Nuxeo’s DM > and DAM applications. > >> Unfortunately, this work is not currently scheduled to > happen anytime soon. > >> However, we understand the value of CollectionSpace being able to > >> co-exist with Nuxeo’s applications.  If you feel we need > to make this > >> work a higher priority, please review the current release roadmaps > >> and see how this work compares to what we have planned.  If you > >> decide this work is more important, let us know and we can > try to raise its priority. > >> > >> -Richard > >> > >> > >> From: talk-bounces@lists.collectionspace.org > >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf > Of Charlie > >> Moad > >> Sent: Thursday, February 16, 2012 7:14 PM > >> To: Christopher Pott; Chris Hoffman > >> Cc: talk@lists.collectionspace.org > >> > >> Subject: Re: [Talk] CAP 5.5 + CS > >> > >> > >> I haven't had much time, but I took a naïve attempt at installing > >> CS+DM+DAM all on the same postgres database. I am attaching two > >> CS+DM+screenshots > >> of the results. There are only a few errors during the DM+DAM > >> startup, but things seem to run well enough. There appears to be > >> promise. Two glaring things are that the "default-domain" that is > >> normally part of the top-level of DM is missing. Looking > inside each > >> CS domain shows a workspace for each type, but they are empty. I > >> would hope that it is only a matter of adding the proper Nuxeo > >> extensions to expose these types to the DM interface. Any > insight the > >> development team has would be interesting. In the mean > time I believe we are going to relate our DM documents to > placeholders documents. > >> The prospect of creating relationship between DM documents and CS > >> ones feels close though. > >> > >> - Charlie > >> > >> From: Christopher Pott <Christopher.Pott@smk.dk> > >> Date: Wed, 11 Jan 2012 14:35:34 +0100 > >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman > >> <chris.hoffman@berkeley.edu> > >> Cc: <talk@lists.collectionspace.org> > >> Subject: SV: [Talk] CAP 5.5 + CS > >> > >> Hi Charlie, > >> > >> Here at SMK we’re also in the process of defining our requirements > >> for a DAM solution and as a part of this process have also > tested an > >> earlier Nuxeo DAM version. It was basic, but seemed fast > and stable > >> in the short period we tested it. Relating texts and documents to > >> artworks is also a pressing use case for us – although > Ihope we can > >> integrate this into CollectionSpace either through the > Media Handling > >> procedure by supporting some new document types (pdf, doc, > html etc.) > >> or possibly even by creating a new procedure for handling related > >> texts. In any case I look forward to following your investigations. > >> > >> Regards, > >> (another) Chris > >> > >> ________________________________ > >> Fra: talk-bounces@lists.collectionspace.org > >> [mailto:talk-bounces@lists.collectionspace.org] På vegne > af Charlie > >> Moad > >> Sendt: 4. januar 2012 22:48 > >> Til: Chris Hoffman > >> Cc: talk@lists.collectionspace.org > >> Emne: Re: [Talk] CAP 5.5 + CS > >> > >> At the IMA we are just in the process of rolling out the new DAM > >> software based on 5.5. We have been using DM with a select > group of > >> staff members for several months now with decent success. We found > >> the previous versions of DAM lacking some very basic needs > and many > >> of those have been addressed in the latest release. We > even paid for > >> the development of some of those enhancements. In general > Nuxeo DAM > >> is fairly simple, but that's all that we (and I suspect > many museums) > >> need. We need it to be able to handle and preview media files and > >> relate them to our institution. I'm not entirely sure what > the effort would be and if much additional work would be required. > >> That's why I reached out. I'll continue to investigate > this and come > >> back with progress I might have. > >> > >> - Charlie > >> > >> From: Chris Hoffman <chris.hoffman@berkeley.edu> > >> Date: Wed, 4 Jan 2012 13:39:36 -0800 > >> To: Charles Moad <cmoad@imamuseum.org> > >> Cc: "talk@lists.collectionspace.org" > <talk@lists.collectionspace.org> > >> Subject: Re: [Talk] CAP 5.5 + CS > >> > >> Hi Charlie, > >> > >> At UC Berkeley, we have a very strong need to connect collections > >> management and digital assetmanagement functions in the > way you describe. > >>  The Nuxeo DAM has seemed like a good way to go, but we haven't > >> really experimented with it here.  What's your experience > been like?   > >> Anyway, we'll happily endorsethis too.  And if it's something that > >> looks like it needs another grant-funded project to do > right, maybe > >> we could get our institutions to partner on something.   Just thinking out loud... > >> > >> Thanks, > >> Chris > >> > >> > >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: > >> > >> > >> > >> Thanks for following up Patrick. I'll rally my friends. I wouldn't > >> expect a CollectionSpace tab in Nuxeo CAP anytime soon > either, but it > >> would be pretty powerful to have a single repository for the sole > >> purpose of relating documents to collection objects, > exhibitions, etc. > >> > >> Keep up the good work, > >> Charlie > >> > >> From: Patrick Schmitz <pschmitz@berkeley.edu> > >> Date: Wed, 4 Jan 2012 10:33:48 -0800 > >> To: Charles Moad <cmoad@imamuseum.org>, > >> <talk@lists.collectionspace.org> > >> Subject: RE: [Talk] CAP 5.5 + CS > >> > >> Hi Charlie - > >> > >> This is something we would really like to investigate, as > many folks > >> have expressed at least some interest in this. We have also been > >> assured by the Nuxeo folks that this should be possible. At this > >> point, it is mostly a matter of resources and priorities. If the > >> community rallies support for this as an essential integration, we > >> should be able to find time in the Phase 3 project to > investigate it. > >> > >> Note that we are otherwise interested in getting the DM > working as a > >> diagnostic and support tool, and to aid with import/export > workflows. > >> As such, there may be some basic investigation (not necessarily > >> including DAM/CSpace coordination) in the near term. > >> > >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI > >> any time soon, as this is not ause-case that anyone (else) has yet > >> requested. Am not ruling it out, just giving my impression of the > >> current project priorities, in response to yourquestion on > a related thread. > >> > >> Thanks for the question - > >> > >> Patrick > >> > >> > >> > >> ________________________________ > >> > >> From: talk-bounces@lists.collectionspace.org > >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf > Of Charlie > >> Moad > >> Sent: Wednesday, January 04, 2012 6:18 AM > >> To: talk@lists.collectionspace.org > >> Subject: [Talk] CAP 5.5 + CS > >> > >> What is the feasibility of setting up a single repository > running the > >> new Nuxeo CAP 5.5 (DM + DAM specifically) and > CollectionSpace 2.0 in > >> a single repository? I would like to be able to relate > documents to > >> works in our collection. Any guidance would be greatly appreciated. > >> > >> Thanks, > >> Charlie > >> ________________________________ > >> > >> This email message is for the sole use of the intended > recipient(s) > >> and may contain confidential and privileged information. Any > >> unauthorized review, use, disclosure or distribution is > prohibited. > >> If you are not the intended recipient, please contact > Charlie Moad by > >> reply email and destroy all copies of the original message. > >> > >> ________________________________ > >> > >> This email message is for the sole use of the intended > recipient(s) > >> and may contain confidential and privileged information. Any > >> unauthorized review, use, disclosure or distribution is > prohibited. > >> If you are not the intended recipient, please contact > Charlie Moad by > >> reply email and destroy all copies of the original message. > >> > >> _______________________________________________ > >> Talk mailing list > >> Talk@lists.collectionspace.org > >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> onspace.org > >> > >> ________________________________ > >> > >> This email message is for the sole use of the intended > recipient(s) > >> and may contain confidential and privileged information. Any > >> unauthorized review, use, disclosure or distribution is > prohibited. > >> If you are not the intended recipient, please contact > Charlie Moad by > >> reply email and destroy all copies of the original message. > >> > >> ________________________________ > >> > >> This email message is for the sole use of the intended > recipient(s) > >> and may contain confidential and privileged information. Any > >> unauthorized review, use, disclosure or distribution is > prohibited. > >> If you are not the intended recipient, please contact > Charlie Moad by > >> reply email and destroy all copies of the original message. > >> > >> > >> _______________________________________________ > >> Talk mailing list > >> Talk@lists.collectionspace.org > >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> onspace.org > >> > > > > ________________________________ > > > > This email message is for the sole use of the intended recipient(s) > > and may contain confidential and privileged information. Any > > unauthorized review, use, disclosure or distribution is > prohibited. If > > you are not the intended recipient, please contact Charlie Moad by > > reply email and destroy all copies of the original message. > > > > _______________________________________________ > > Talk mailing list > > Talk@lists.collectionspace.org > > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio > > nspace.org > > > > > > _______________________________________________ > > Talk mailing list > > Talk@lists.collectionspace.org > > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio > > nspace.org > > > > > > > > _______________________________________________ > > Talk mailing list > > Talk@lists.collectionspace.org > > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio > > nspace.org > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.c > ollectionspace.org >
AR
Aron Roberts
Fri, Feb 24, 2012 11:16 PM

That was creative license, alas.  "DM the torpedoes" just didn't seem
to have the same impact (pun intended).

Thanks for the as-always important clarification, Patrick!

Aron

P.S. Two key reasons that getting the DM back is useful, and that, as
Patrick mentioned, we're focusing on that initially:
http://issues.collectionspace.org/browse/CSPACE-4790

In addition to the two reasons mentioned, two more: the DM's web
console gave us one more useful diagnostic tool for looking at Nuxeo's
view of things, and a quick way to both view and hard-delete records
via a web-based UI.

On Fri, Feb 24, 2012 at 2:58 PM, Patrick Schmitz pschmitz@berkeley.edu wrote:

Sorry to undermine your joke, but I should note that Nuxeo DM is not the
same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we used when we
had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same repo as
CSpace.

However, the scope of work in 2.3 is only to look at DM, so that support for
export and diagnostics is restored to what we had previous to 2.0. It may
well be that once we figure out how to support DM and CSpace, adding the DAM
app to the mix will be straightforward. However, integrating DAM is not a
goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of
Aron Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze
ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

 and

+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM interface. What are
the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an issue, but I
know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo’s DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace being able to
co-exist with Nuxeo’s applications.  If you feel we need

to make this

work a higher priority, please review the current release roadmaps
and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There appears to be
promise. Two glaring things are that the "default-domain" that is
normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are empty. I
would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM documents and CS
ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we’re also in the process of defining our requirements
for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and documents to
artworks is also a pressing use case for us – although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for handling related
texts. In any case I look forward to following your investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent success. We found
the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media files and
relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the

way you describe.

 The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?

Anyway, we'll happily endorsethis too.  And if it's something that
looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository for the sole
purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have also been
assured by the Nuxeo folks that this should be possible. At this
point, it is mostly a matter of resources and priorities. If the
community rallies support for this as an essential integration, we
should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact Charlie Moad by
reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org

That was creative license, alas. "DM the torpedoes" just didn't seem to have the same impact (pun intended). Thanks for the as-always important clarification, Patrick! Aron P.S. Two key reasons that getting the DM back is useful, and that, as Patrick mentioned, we're focusing on that initially: http://issues.collectionspace.org/browse/CSPACE-4790 In addition to the two reasons mentioned, two more: the DM's web console gave us one more useful diagnostic tool for looking at Nuxeo's view of things, and a quick way to both view and hard-delete records via a web-based UI. On Fri, Feb 24, 2012 at 2:58 PM, Patrick Schmitz <pschmitz@berkeley.edu> wrote: > Sorry to undermine your joke, but I should note that Nuxeo DM is not the > same as Nuxeo DAM. > > Nuxeo DM is the traditional Nuxeo doc management app that we used when we > had the dual-server (JBoss) setup. > > Nuxeo DAM is the Digital Asset Management application. > > We would like (eventually) to support both, integrated with the same repo as > CSpace. > > However, the scope of work in 2.3 is only to look at DM, so that support for > export and diagnostics is restored to what we had previous to 2.0. It may > well be that once we figure out how to support DM and CSpace, adding the DAM > app to the mix will be straightforward. However, integrating DAM is not a > goal in the 2.3 release. > > Patrick > >> -----Original Message----- >> From: talk-bounces@lists.collectionspace.org >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of >> Aron Roberts >> Sent: Friday, February 24, 2012 1:41 PM >> To: Angela Spinazze >> Cc: CollectionSpace Talk List >> Subject: Re: [Talk] CAP 5.5 + CS >> >> DAM the torpedoes, and full speed ahead? >> >> Aron >> >> (With due apologies ... it's Friday afternoon) >> http://en.wiktionary.org/wiki/damn_the_torpedoes >> >> On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze >> <ats@atspin.com> wrote: >> > Hi all, >> > >> > A brief update for you on this Nuxeo DM question. >> > >> > As Patrick mentioned in an earlier post to this thread >> (January 4th) >> > "Note that we are otherwise interested in getting the DM >> working as a >> > diagnostic and support tool, and to aid with import/export >> workflows. >> > As such, there may be some basic investigation (not necessarily >> > including DAM/CSpace >> > coordination) in the near term." >> > >> > Given the level of interest in and the potential positive impact of >> > getting the DM working as a diagnostic support tool, we >> will include >> > investigation into the effort required to do so in the >> scope of work >> > for the release 2.3 (scheduled to begin on March 5th). > Based on what >> > we discover in the research phase, we will determine >> if/when the work >> > might be scheduled to take place within the current schedule. >> > >> > We'll be creating a new Jira for this investigation effort so that >> > everyone who is interested can keep an eye on our progress. >> > >> > Cheers, >> > >> > Angela >> > >> > >> > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: >> > >> > Hi Charlie, >> > >> > Patrick, Megan and I will be discussing this work tomorrow >> afternoon >> > to determine just what is required and we will follow up on this >> > thread once we've had a chance to explore this in more detail. >> > >> > As Richard pointed out, we have our core CollectionSpace >> development >> > schedule set through September 2012 >> > >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >> >  and >> > >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >> > +Proposed+Schedule >> > >> > We do however, realize how important this functionality is to many >> > community members. Thanks very much for keeping this >> conversation alive! >> > >> > Angela >> > >> > >> > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: >> > >> > It would help to know if someone could express what would >> be involved >> > in this process. It seems like it could be really close if >> it is just >> > a matter of exposing the CS doc types in the DM interface. What are >> > the complicating factors beyond that? >> > >> > - Charlie >> > >> > From: Nate Solas <nate.solas@walkerart.org> >> > Date: Tue, 21 Feb 2012 11:52:38 -0600 >> > To: Richard Millet <richard.millet@berkeley.edu> >> > Cc: Charles Moad <cmoad@imamuseum.org>, >> > <talk@lists.collectionspace.org> >> > Subject: Re: [Talk] CAP 5.5 + CS >> > >> > I'd like to +1 a raised priority for this, but I'm not >> entirely sure >> > what to recommend bumping. For us, and I suspect most of >> the current >> > implementers, the multi-tenant service isn't as big an issue, but I >> > know it's core to the long-term sustainability of the software. >> > >> > It seems like there might be some room for this work in the 2.3 >> > roadmap? I don't know how big a chunk the Location and >> Movement rewrite is. >> > >> > Thanks for considering it. This would be huge for us, and it sounds >> > like there is a lot of support out there. >> > Nate >> > >> > >> > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet >> > <richard.millet@berkeley.edu> wrote: >> >> >> >> Charlie, >> >> >> >> Thanks for experimenting with this.  One of our known tasks is to >> >> ensure that CollectionSpace can co-exist with Nuxeo’s DM >> and DAM applications. >> >> Unfortunately, this work is not currently scheduled to >> happen anytime soon. >> >> However, we understand the value of CollectionSpace being able to >> >> co-exist with Nuxeo’s applications.  If you feel we need >> to make this >> >> work a higher priority, please review the current release roadmaps >> >> and see how this work compares to what we have planned.  If you >> >> decide this work is more important, let us know and we can >> try to raise its priority. >> >> >> >> -Richard >> >> >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> Of Charlie >> >> Moad >> >> Sent: Thursday, February 16, 2012 7:14 PM >> >> To: Christopher Pott; Chris Hoffman >> >> Cc: talk@lists.collectionspace.org >> >> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> >> >> I haven't had much time, but I took a naïve attempt at installing >> >> CS+DM+DAM all on the same postgres database. I am attaching two >> >> CS+DM+screenshots >> >> of the results. There are only a few errors during the DM+DAM >> >> startup, but things seem to run well enough. There appears to be >> >> promise. Two glaring things are that the "default-domain" that is >> >> normally part of the top-level of DM is missing. Looking >> inside each >> >> CS domain shows a workspace for each type, but they are empty. I >> >> would hope that it is only a matter of adding the proper Nuxeo >> >> extensions to expose these types to the DM interface. Any >> insight the >> >> development team has would be interesting. In the mean >> time I believe we are going to relate our DM documents to >> placeholders documents. >> >> The prospect of creating relationship between DM documents and CS >> >> ones feels close though. >> >> >> >> - Charlie >> >> >> >> From: Christopher Pott <Christopher.Pott@smk.dk> >> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 >> >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman >> >> <chris.hoffman@berkeley.edu> >> >> Cc: <talk@lists.collectionspace.org> >> >> Subject: SV: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie, >> >> >> >> Here at SMK we’re also in the process of defining our requirements >> >> for a DAM solution and as a part of this process have also >> tested an >> >> earlier Nuxeo DAM version. It was basic, but seemed fast >> and stable >> >> in the short period we tested it. Relating texts and documents to >> >> artworks is also a pressing use case for us – although >> Ihope we can >> >> integrate this into CollectionSpace either through the >> Media Handling >> >> procedure by supporting some new document types (pdf, doc, >> html etc.) >> >> or possibly even by creating a new procedure for handling related >> >> texts. In any case I look forward to following your investigations. >> >> >> >> Regards, >> >> (another) Chris >> >> >> >> ________________________________ >> >> Fra: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] På vegne >> af Charlie >> >> Moad >> >> Sendt: 4. januar 2012 22:48 >> >> Til: Chris Hoffman >> >> Cc: talk@lists.collectionspace.org >> >> Emne: Re: [Talk] CAP 5.5 + CS >> >> >> >> At the IMA we are just in the process of rolling out the new DAM >> >> software based on 5.5. We have been using DM with a select >> group of >> >> staff members for several months now with decent success. We found >> >> the previous versions of DAM lacking some very basic needs >> and many >> >> of those have been addressed in the latest release. We >> even paid for >> >> the development of some of those enhancements. In general >> Nuxeo DAM >> >> is fairly simple, but that's all that we (and I suspect >> many museums) >> >> need. We need it to be able to handle and preview media files and >> >> relate them to our institution. I'm not entirely sure what >> the effort would be and if much additional work would be required. >> >> That's why I reached out. I'll continue to investigate >> this and come >> >> back with progress I might have. >> >> >> >> - Charlie >> >> >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> >> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 >> >> To: Charles Moad <cmoad@imamuseum.org> >> >> Cc: "talk@lists.collectionspace.org" >> <talk@lists.collectionspace.org> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie, >> >> >> >> At UC Berkeley, we have a very strong need to connect collections >> >> management and digital assetmanagement functions in the >> way you describe. >> >>  The Nuxeo DAM has seemed like a good way to go, but we haven't >> >> really experimented with it here.  What's your experience >> been like? >> >> Anyway, we'll happily endorsethis too.  And if it's something that >> >> looks like it needs another grant-funded project to do >> right, maybe >> >> we could get our institutions to partner on something. > Just thinking out loud... >> >> >> >> Thanks, >> >> Chris >> >> >> >> >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >> >> >> >> >> >> >> >> Thanks for following up Patrick. I'll rally my friends. I wouldn't >> >> expect a CollectionSpace tab in Nuxeo CAP anytime soon >> either, but it >> >> would be pretty powerful to have a single repository for the sole >> >> purpose of relating documents to collection objects, >> exhibitions, etc. >> >> >> >> Keep up the good work, >> >> Charlie >> >> >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> >> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 >> >> To: Charles Moad <cmoad@imamuseum.org>, >> >> <talk@lists.collectionspace.org> >> >> Subject: RE: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie - >> >> >> >> This is something we would really like to investigate, as >> many folks >> >> have expressed at least some interest in this. We have also been >> >> assured by the Nuxeo folks that this should be possible. At this >> >> point, it is mostly a matter of resources and priorities. If the >> >> community rallies support for this as an essential integration, we >> >> should be able to find time in the Phase 3 project to >> investigate it. >> >> >> >> Note that we are otherwise interested in getting the DM >> working as a >> >> diagnostic and support tool, and to aid with import/export >> workflows. >> >> As such, there may be some basic investigation (not necessarily >> >> including DAM/CSpace coordination) in the near term. >> >> >> >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI >> >> any time soon, as this is not ause-case that anyone (else) has yet >> >> requested. Am not ruling it out, just giving my impression of the >> >> current project priorities, in response to yourquestion on >> a related thread. >> >> >> >> Thanks for the question - >> >> >> >> Patrick >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> Of Charlie >> >> Moad >> >> Sent: Wednesday, January 04, 2012 6:18 AM >> >> To: talk@lists.collectionspace.org >> >> Subject: [Talk] CAP 5.5 + CS >> >> >> >> What is the feasibility of setting up a single repository >> running the >> >> new Nuxeo CAP 5.5 (DM + DAM specifically) and >> CollectionSpace 2.0 in >> >> a single repository? I would like to be able to relate >> documents to >> >> works in our collection. Any guidance would be greatly appreciated. >> >> >> >> Thanks, >> >> Charlie >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> onspace.org >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> onspace.org >> >> >> > >> > ________________________________ >> > >> > This email message is for the sole use of the intended recipient(s) >> > and may contain confidential and privileged information. Any >> > unauthorized review, use, disclosure or distribution is >> prohibited. If >> > you are not the intended recipient, please contact Charlie Moad by >> > reply email and destroy all copies of the original message. >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> > >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c >> ollectionspace.org >> >
CM
Charlie Moad
Mon, Feb 27, 2012 2:54 PM

I'd like to throw a few thoughts on top of this. Nuxeo DAM and its
features are becoming more and more integrated with the DM interface,
which is far more robust. DAM is not much more than an advanced/visual
search of the DM repository. Any attempt to integrate with DAM at this
point would most likely lead to headaches and lost code down the road as
DAM looks more and more like part of DM. DM is where the real power and
focus of the Nuxeo team lies. Also, aligning CS with the DM product would
most likely give you DAM integration for free as the products merge. The
CS team is probably aware of this, but I am imagine others who are not
familiar with the DM/DAM products are not.

  • Charlie

On 2/24/12 5:58 PM, "Patrick Schmitz" pschmitz@berkeley.edu wrote:

Sorry to undermine your joke, but I should note that Nuxeo DM is not the
same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we used when we
had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same repo
as
CSpace.

However, the scope of work in 2.3 is only to look at DM, so that support
for
export and diagnostics is restored to what we had previous to 2.0. It may
well be that once we figure out how to support DM and CSpace, adding the
DAM
app to the mix will be straightforward. However, integrating DAM is not a
goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of
Aron Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze
ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

and

+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM interface. What are
the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an issue, but I
know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo's DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace being able to
co-exist with Nuxeo's applications.  If you feel we need

to make this

work a higher priority, please review the current release roadmaps
and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There appears to be
promise. Two glaring things are that the "default-domain" that is
normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are empty. I
would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM documents and CS
ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we're also in the process of defining our requirements
for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and documents to
artworks is also a pressing use case for us - although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for handling related
texts. In any case I look forward to following your investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent success. We found
the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media files and
relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the

way you describe.

The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?

Anyway, we'll happily endorsethis too.  And if it's something that
looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository for the sole
purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have also been
assured by the Nuxeo folks that this should be possible. At this
point, it is mostly a matter of resources and priorities. If the
community rallies support for this as an essential integration, we
should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact Charlie Moad by
reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message.

I'd like to throw a few thoughts on top of this. Nuxeo DAM and its features are becoming more and more integrated with the DM interface, which is far more robust. DAM is not much more than an advanced/visual search of the DM repository. Any attempt to integrate with DAM at this point would most likely lead to headaches and lost code down the road as DAM looks more and more like part of DM. DM is where the real power and focus of the Nuxeo team lies. Also, aligning CS with the DM product would most likely give you DAM integration for free as the products merge. The CS team is probably aware of this, but I am imagine others who are not familiar with the DM/DAM products are not. - Charlie On 2/24/12 5:58 PM, "Patrick Schmitz" <pschmitz@berkeley.edu> wrote: >Sorry to undermine your joke, but I should note that Nuxeo DM is not the >same as Nuxeo DAM. > >Nuxeo DM is the traditional Nuxeo doc management app that we used when we >had the dual-server (JBoss) setup. > >Nuxeo DAM is the Digital Asset Management application. > >We would like (eventually) to support both, integrated with the same repo >as >CSpace. > >However, the scope of work in 2.3 is only to look at DM, so that support >for >export and diagnostics is restored to what we had previous to 2.0. It may >well be that once we figure out how to support DM and CSpace, adding the >DAM >app to the mix will be straightforward. However, integrating DAM is not a >goal in the 2.3 release. > >Patrick > >> -----Original Message----- >> From: talk-bounces@lists.collectionspace.org >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of >> Aron Roberts >> Sent: Friday, February 24, 2012 1:41 PM >> To: Angela Spinazze >> Cc: CollectionSpace Talk List >> Subject: Re: [Talk] CAP 5.5 + CS >> >> DAM the torpedoes, and full speed ahead? >> >> Aron >> >> (With due apologies ... it's Friday afternoon) >> http://en.wiktionary.org/wiki/damn_the_torpedoes >> >> On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze >> <ats@atspin.com> wrote: >> > Hi all, >> > >> > A brief update for you on this Nuxeo DM question. >> > >> > As Patrick mentioned in an earlier post to this thread >> (January 4th) >> > "Note that we are otherwise interested in getting the DM >> working as a >> > diagnostic and support tool, and to aid with import/export >> workflows. >> > As such, there may be some basic investigation (not necessarily >> > including DAM/CSpace >> > coordination) in the near term." >> > >> > Given the level of interest in and the potential positive impact of >> > getting the DM working as a diagnostic support tool, we >> will include >> > investigation into the effort required to do so in the >> scope of work >> > for the release 2.3 (scheduled to begin on March 5th). >Based on what >> > we discover in the research phase, we will determine >> if/when the work >> > might be scheduled to take place within the current schedule. >> > >> > We'll be creating a new Jira for this investigation effort so that >> > everyone who is interested can keep an eye on our progress. >> > >> > Cheers, >> > >> > Angela >> > >> > >> > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: >> > >> > Hi Charlie, >> > >> > Patrick, Megan and I will be discussing this work tomorrow >> afternoon >> > to determine just what is required and we will follow up on this >> > thread once we've had a chance to explore this in more detail. >> > >> > As Richard pointed out, we have our core CollectionSpace >> development >> > schedule set through September 2012 >> > >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >> > and >> > >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >> > +Proposed+Schedule >> > >> > We do however, realize how important this functionality is to many >> > community members. Thanks very much for keeping this >> conversation alive! >> > >> > Angela >> > >> > >> > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: >> > >> > It would help to know if someone could express what would >> be involved >> > in this process. It seems like it could be really close if >> it is just >> > a matter of exposing the CS doc types in the DM interface. What are >> > the complicating factors beyond that? >> > >> > - Charlie >> > >> > From: Nate Solas <nate.solas@walkerart.org> >> > Date: Tue, 21 Feb 2012 11:52:38 -0600 >> > To: Richard Millet <richard.millet@berkeley.edu> >> > Cc: Charles Moad <cmoad@imamuseum.org>, >> > <talk@lists.collectionspace.org> >> > Subject: Re: [Talk] CAP 5.5 + CS >> > >> > I'd like to +1 a raised priority for this, but I'm not >> entirely sure >> > what to recommend bumping. For us, and I suspect most of >> the current >> > implementers, the multi-tenant service isn't as big an issue, but I >> > know it's core to the long-term sustainability of the software. >> > >> > It seems like there might be some room for this work in the 2.3 >> > roadmap? I don't know how big a chunk the Location and >> Movement rewrite is. >> > >> > Thanks for considering it. This would be huge for us, and it sounds >> > like there is a lot of support out there. >> > Nate >> > >> > >> > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet >> > <richard.millet@berkeley.edu> wrote: >> >> >> >> Charlie, >> >> >> >> Thanks for experimenting with this. One of our known tasks is to >> >> ensure that CollectionSpace can co-exist with Nuxeo's DM >> and DAM applications. >> >> Unfortunately, this work is not currently scheduled to >> happen anytime soon. >> >> However, we understand the value of CollectionSpace being able to >> >> co-exist with Nuxeo's applications. If you feel we need >> to make this >> >> work a higher priority, please review the current release roadmaps >> >> and see how this work compares to what we have planned. If you >> >> decide this work is more important, let us know and we can >> try to raise its priority. >> >> >> >> -Richard >> >> >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> Of Charlie >> >> Moad >> >> Sent: Thursday, February 16, 2012 7:14 PM >> >> To: Christopher Pott; Chris Hoffman >> >> Cc: talk@lists.collectionspace.org >> >> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> >> >> I haven't had much time, but I took a naïve attempt at installing >> >> CS+DM+DAM all on the same postgres database. I am attaching two >> >> CS+DM+screenshots >> >> of the results. There are only a few errors during the DM+DAM >> >> startup, but things seem to run well enough. There appears to be >> >> promise. Two glaring things are that the "default-domain" that is >> >> normally part of the top-level of DM is missing. Looking >> inside each >> >> CS domain shows a workspace for each type, but they are empty. I >> >> would hope that it is only a matter of adding the proper Nuxeo >> >> extensions to expose these types to the DM interface. Any >> insight the >> >> development team has would be interesting. In the mean >> time I believe we are going to relate our DM documents to >> placeholders documents. >> >> The prospect of creating relationship between DM documents and CS >> >> ones feels close though. >> >> >> >> - Charlie >> >> >> >> From: Christopher Pott <Christopher.Pott@smk.dk> >> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 >> >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman >> >> <chris.hoffman@berkeley.edu> >> >> Cc: <talk@lists.collectionspace.org> >> >> Subject: SV: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie, >> >> >> >> Here at SMK we're also in the process of defining our requirements >> >> for a DAM solution and as a part of this process have also >> tested an >> >> earlier Nuxeo DAM version. It was basic, but seemed fast >> and stable >> >> in the short period we tested it. Relating texts and documents to >> >> artworks is also a pressing use case for us - although >> Ihope we can >> >> integrate this into CollectionSpace either through the >> Media Handling >> >> procedure by supporting some new document types (pdf, doc, >> html etc.) >> >> or possibly even by creating a new procedure for handling related >> >> texts. In any case I look forward to following your investigations. >> >> >> >> Regards, >> >> (another) Chris >> >> >> >> ________________________________ >> >> Fra: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] På vegne >> af Charlie >> >> Moad >> >> Sendt: 4. januar 2012 22:48 >> >> Til: Chris Hoffman >> >> Cc: talk@lists.collectionspace.org >> >> Emne: Re: [Talk] CAP 5.5 + CS >> >> >> >> At the IMA we are just in the process of rolling out the new DAM >> >> software based on 5.5. We have been using DM with a select >> group of >> >> staff members for several months now with decent success. We found >> >> the previous versions of DAM lacking some very basic needs >> and many >> >> of those have been addressed in the latest release. We >> even paid for >> >> the development of some of those enhancements. In general >> Nuxeo DAM >> >> is fairly simple, but that's all that we (and I suspect >> many museums) >> >> need. We need it to be able to handle and preview media files and >> >> relate them to our institution. I'm not entirely sure what >> the effort would be and if much additional work would be required. >> >> That's why I reached out. I'll continue to investigate >> this and come >> >> back with progress I might have. >> >> >> >> - Charlie >> >> >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> >> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 >> >> To: Charles Moad <cmoad@imamuseum.org> >> >> Cc: "talk@lists.collectionspace.org" >> <talk@lists.collectionspace.org> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie, >> >> >> >> At UC Berkeley, we have a very strong need to connect collections >> >> management and digital assetmanagement functions in the >> way you describe. >> >> The Nuxeo DAM has seemed like a good way to go, but we haven't >> >> really experimented with it here. What's your experience >> been like? >> >> Anyway, we'll happily endorsethis too. And if it's something that >> >> looks like it needs another grant-funded project to do >> right, maybe >> >> we could get our institutions to partner on something. >Just thinking out loud... >> >> >> >> Thanks, >> >> Chris >> >> >> >> >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >> >> >> >> >> >> >> >> Thanks for following up Patrick. I'll rally my friends. I wouldn't >> >> expect a CollectionSpace tab in Nuxeo CAP anytime soon >> either, but it >> >> would be pretty powerful to have a single repository for the sole >> >> purpose of relating documents to collection objects, >> exhibitions, etc. >> >> >> >> Keep up the good work, >> >> Charlie >> >> >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> >> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 >> >> To: Charles Moad <cmoad@imamuseum.org>, >> >> <talk@lists.collectionspace.org> >> >> Subject: RE: [Talk] CAP 5.5 + CS >> >> >> >> Hi Charlie - >> >> >> >> This is something we would really like to investigate, as >> many folks >> >> have expressed at least some interest in this. We have also been >> >> assured by the Nuxeo folks that this should be possible. At this >> >> point, it is mostly a matter of resources and priorities. If the >> >> community rallies support for this as an essential integration, we >> >> should be able to find time in the Phase 3 project to >> investigate it. >> >> >> >> Note that we are otherwise interested in getting the DM >> working as a >> >> diagnostic and support tool, and to aid with import/export >> workflows. >> >> As such, there may be some basic investigation (not necessarily >> >> including DAM/CSpace coordination) in the near term. >> >> >> >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI >> >> any time soon, as this is not ause-case that anyone (else) has yet >> >> requested. Am not ruling it out, just giving my impression of the >> >> current project priorities, in response to yourquestion on >> a related thread. >> >> >> >> Thanks for the question - >> >> >> >> Patrick >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> Of Charlie >> >> Moad >> >> Sent: Wednesday, January 04, 2012 6:18 AM >> >> To: talk@lists.collectionspace.org >> >> Subject: [Talk] CAP 5.5 + CS >> >> >> >> What is the feasibility of setting up a single repository >> running the >> >> new Nuxeo CAP 5.5 (DM + DAM specifically) and >> CollectionSpace 2.0 in >> >> a single repository? I would like to be able to relate >> documents to >> >> works in our collection. Any guidance would be greatly appreciated. >> >> >> >> Thanks, >> >> Charlie >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> onspace.org >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> ________________________________ >> >> >> >> This email message is for the sole use of the intended >> recipient(s) >> >> and may contain confidential and privileged information. Any >> >> unauthorized review, use, disclosure or distribution is >> prohibited. >> >> If you are not the intended recipient, please contact >> Charlie Moad by >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> onspace.org >> >> >> > >> > ________________________________ >> > >> > This email message is for the sole use of the intended recipient(s) >> > and may contain confidential and privileged information. Any >> > unauthorized review, use, disclosure or distribution is >> prohibited. If >> > you are not the intended recipient, please contact Charlie Moad by >> > reply email and destroy all copies of the original message. >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> > >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >> > nspace.org >> > >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c >> ollectionspace.org >> > > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspa >ce.org ________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message.
CH
Chris Hoffman
Mon, Feb 27, 2012 4:16 PM

Thanks, Charlie.  I had not learned about this DM-DAM convergence.  That is definitely good news for a bunch of us!
Chris

On Feb 27, 2012, at 6:54 AM, Charlie Moad wrote:

I'd like to throw a few thoughts on top of this. Nuxeo DAM and its
features are becoming more and more integrated with the DM interface,
which is far more robust. DAM is not much more than an advanced/visual
search of the DM repository. Any attempt to integrate with DAM at this
point would most likely lead to headaches and lost code down the road as
DAM looks more and more like part of DM. DM is where the real power and
focus of the Nuxeo team lies. Also, aligning CS with the DM product would
most likely give you DAM integration for free as the products merge. The
CS team is probably aware of this, but I am imagine others who are not
familiar with the DM/DAM products are not.

  • Charlie

On 2/24/12 5:58 PM, "Patrick Schmitz" pschmitz@berkeley.edu wrote:

Sorry to undermine your joke, but I should note that Nuxeo DM is not the
same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we used when we
had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same repo
as
CSpace.

However, the scope of work in 2.3 is only to look at DM, so that support
for
export and diagnostics is restored to what we had previous to 2.0. It may
well be that once we figure out how to support DM and CSpace, adding the
DAM
app to the mix will be straightforward. However, integrating DAM is not a
goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of
Aron Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze
ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

and

+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM interface. What are
the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an issue, but I
know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds
like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known tasks is to
ensure that CollectionSpace can co-exist with Nuxeo's DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace being able to
co-exist with Nuxeo's applications.  If you feel we need

to make this

work a higher priority, please review the current release roadmaps
and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There appears to be
promise. Two glaring things are that the "default-domain" that is
normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are empty. I
would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM documents and CS
ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we're also in the process of defining our requirements
for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and documents to
artworks is also a pressing use case for us - although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for handling related
texts. In any case I look forward to following your investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent success. We found
the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media files and
relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the

way you describe.

The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?

Anyway, we'll happily endorsethis too.  And if it's something that
looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository for the sole
purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have also been
assured by the Nuxeo folks that this should be possible. At this
point, it is mostly a matter of resources and priorities. If the
community rallies support for this as an essential integration, we
should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in the Nuxeo UI
any time soon, as this is not ause-case that anyone (else) has yet
requested. Am not ruling it out, just giving my impression of the
current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact Charlie Moad by
reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

nspace.org


This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Thanks, Charlie. I had not learned about this DM-DAM convergence. That is definitely good news for a bunch of us! Chris On Feb 27, 2012, at 6:54 AM, Charlie Moad wrote: > I'd like to throw a few thoughts on top of this. Nuxeo DAM and its > features are becoming more and more integrated with the DM interface, > which is far more robust. DAM is not much more than an advanced/visual > search of the DM repository. Any attempt to integrate with DAM at this > point would most likely lead to headaches and lost code down the road as > DAM looks more and more like part of DM. DM is where the real power and > focus of the Nuxeo team lies. Also, aligning CS with the DM product would > most likely give you DAM integration for free as the products merge. The > CS team is probably aware of this, but I am imagine others who are not > familiar with the DM/DAM products are not. > > > - Charlie > > On 2/24/12 5:58 PM, "Patrick Schmitz" <pschmitz@berkeley.edu> wrote: > >> Sorry to undermine your joke, but I should note that Nuxeo DM is not the >> same as Nuxeo DAM. >> >> Nuxeo DM is the traditional Nuxeo doc management app that we used when we >> had the dual-server (JBoss) setup. >> >> Nuxeo DAM is the Digital Asset Management application. >> >> We would like (eventually) to support both, integrated with the same repo >> as >> CSpace. >> >> However, the scope of work in 2.3 is only to look at DM, so that support >> for >> export and diagnostics is restored to what we had previous to 2.0. It may >> well be that once we figure out how to support DM and CSpace, adding the >> DAM >> app to the mix will be straightforward. However, integrating DAM is not a >> goal in the 2.3 release. >> >> Patrick >> >>> -----Original Message----- >>> From: talk-bounces@lists.collectionspace.org >>> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of >>> Aron Roberts >>> Sent: Friday, February 24, 2012 1:41 PM >>> To: Angela Spinazze >>> Cc: CollectionSpace Talk List >>> Subject: Re: [Talk] CAP 5.5 + CS >>> >>> DAM the torpedoes, and full speed ahead? >>> >>> Aron >>> >>> (With due apologies ... it's Friday afternoon) >>> http://en.wiktionary.org/wiki/damn_the_torpedoes >>> >>> On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze >>> <ats@atspin.com> wrote: >>>> Hi all, >>>> >>>> A brief update for you on this Nuxeo DM question. >>>> >>>> As Patrick mentioned in an earlier post to this thread >>> (January 4th) >>>> "Note that we are otherwise interested in getting the DM >>> working as a >>>> diagnostic and support tool, and to aid with import/export >>> workflows. >>>> As such, there may be some basic investigation (not necessarily >>>> including DAM/CSpace >>>> coordination) in the near term." >>>> >>>> Given the level of interest in and the potential positive impact of >>>> getting the DM working as a diagnostic support tool, we >>> will include >>>> investigation into the effort required to do so in the >>> scope of work >>>> for the release 2.3 (scheduled to begin on March 5th). >> Based on what >>>> we discover in the research phase, we will determine >>> if/when the work >>>> might be scheduled to take place within the current schedule. >>>> >>>> We'll be creating a new Jira for this investigation effort so that >>>> everyone who is interested can keep an eye on our progress. >>>> >>>> Cheers, >>>> >>>> Angela >>>> >>>> >>>> On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: >>>> >>>> Hi Charlie, >>>> >>>> Patrick, Megan and I will be discussing this work tomorrow >>> afternoon >>>> to determine just what is required and we will follow up on this >>>> thread once we've had a chance to explore this in more detail. >>>> >>>> As Richard pointed out, we have our core CollectionSpace >>> development >>>> schedule set through September 2012 >>>> >>> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >>>> and >>>> >>> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 >>>> +Proposed+Schedule >>>> >>>> We do however, realize how important this functionality is to many >>>> community members. Thanks very much for keeping this >>> conversation alive! >>>> >>>> Angela >>>> >>>> >>>> On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: >>>> >>>> It would help to know if someone could express what would >>> be involved >>>> in this process. It seems like it could be really close if >>> it is just >>>> a matter of exposing the CS doc types in the DM interface. What are >>>> the complicating factors beyond that? >>>> >>>> - Charlie >>>> >>>> From: Nate Solas <nate.solas@walkerart.org> >>>> Date: Tue, 21 Feb 2012 11:52:38 -0600 >>>> To: Richard Millet <richard.millet@berkeley.edu> >>>> Cc: Charles Moad <cmoad@imamuseum.org>, >>>> <talk@lists.collectionspace.org> >>>> Subject: Re: [Talk] CAP 5.5 + CS >>>> >>>> I'd like to +1 a raised priority for this, but I'm not >>> entirely sure >>>> what to recommend bumping. For us, and I suspect most of >>> the current >>>> implementers, the multi-tenant service isn't as big an issue, but I >>>> know it's core to the long-term sustainability of the software. >>>> >>>> It seems like there might be some room for this work in the 2.3 >>>> roadmap? I don't know how big a chunk the Location and >>> Movement rewrite is. >>>> >>>> Thanks for considering it. This would be huge for us, and it sounds >>>> like there is a lot of support out there. >>>> Nate >>>> >>>> >>>> On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet >>>> <richard.millet@berkeley.edu> wrote: >>>>> >>>>> Charlie, >>>>> >>>>> Thanks for experimenting with this. One of our known tasks is to >>>>> ensure that CollectionSpace can co-exist with Nuxeo's DM >>> and DAM applications. >>>>> Unfortunately, this work is not currently scheduled to >>> happen anytime soon. >>>>> However, we understand the value of CollectionSpace being able to >>>>> co-exist with Nuxeo's applications. If you feel we need >>> to make this >>>>> work a higher priority, please review the current release roadmaps >>>>> and see how this work compares to what we have planned. If you >>>>> decide this work is more important, let us know and we can >>> try to raise its priority. >>>>> >>>>> -Richard >>>>> >>>>> >>>>> From: talk-bounces@lists.collectionspace.org >>>>> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >>> Of Charlie >>>>> Moad >>>>> Sent: Thursday, February 16, 2012 7:14 PM >>>>> To: Christopher Pott; Chris Hoffman >>>>> Cc: talk@lists.collectionspace.org >>>>> >>>>> Subject: Re: [Talk] CAP 5.5 + CS >>>>> >>>>> >>>>> I haven't had much time, but I took a naïve attempt at installing >>>>> CS+DM+DAM all on the same postgres database. I am attaching two >>>>> CS+DM+screenshots >>>>> of the results. There are only a few errors during the DM+DAM >>>>> startup, but things seem to run well enough. There appears to be >>>>> promise. Two glaring things are that the "default-domain" that is >>>>> normally part of the top-level of DM is missing. Looking >>> inside each >>>>> CS domain shows a workspace for each type, but they are empty. I >>>>> would hope that it is only a matter of adding the proper Nuxeo >>>>> extensions to expose these types to the DM interface. Any >>> insight the >>>>> development team has would be interesting. In the mean >>> time I believe we are going to relate our DM documents to >>> placeholders documents. >>>>> The prospect of creating relationship between DM documents and CS >>>>> ones feels close though. >>>>> >>>>> - Charlie >>>>> >>>>> From: Christopher Pott <Christopher.Pott@smk.dk> >>>>> Date: Wed, 11 Jan 2012 14:35:34 +0100 >>>>> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman >>>>> <chris.hoffman@berkeley.edu> >>>>> Cc: <talk@lists.collectionspace.org> >>>>> Subject: SV: [Talk] CAP 5.5 + CS >>>>> >>>>> Hi Charlie, >>>>> >>>>> Here at SMK we're also in the process of defining our requirements >>>>> for a DAM solution and as a part of this process have also >>> tested an >>>>> earlier Nuxeo DAM version. It was basic, but seemed fast >>> and stable >>>>> in the short period we tested it. Relating texts and documents to >>>>> artworks is also a pressing use case for us - although >>> Ihope we can >>>>> integrate this into CollectionSpace either through the >>> Media Handling >>>>> procedure by supporting some new document types (pdf, doc, >>> html etc.) >>>>> or possibly even by creating a new procedure for handling related >>>>> texts. In any case I look forward to following your investigations. >>>>> >>>>> Regards, >>>>> (another) Chris >>>>> >>>>> ________________________________ >>>>> Fra: talk-bounces@lists.collectionspace.org >>>>> [mailto:talk-bounces@lists.collectionspace.org] På vegne >>> af Charlie >>>>> Moad >>>>> Sendt: 4. januar 2012 22:48 >>>>> Til: Chris Hoffman >>>>> Cc: talk@lists.collectionspace.org >>>>> Emne: Re: [Talk] CAP 5.5 + CS >>>>> >>>>> At the IMA we are just in the process of rolling out the new DAM >>>>> software based on 5.5. We have been using DM with a select >>> group of >>>>> staff members for several months now with decent success. We found >>>>> the previous versions of DAM lacking some very basic needs >>> and many >>>>> of those have been addressed in the latest release. We >>> even paid for >>>>> the development of some of those enhancements. In general >>> Nuxeo DAM >>>>> is fairly simple, but that's all that we (and I suspect >>> many museums) >>>>> need. We need it to be able to handle and preview media files and >>>>> relate them to our institution. I'm not entirely sure what >>> the effort would be and if much additional work would be required. >>>>> That's why I reached out. I'll continue to investigate >>> this and come >>>>> back with progress I might have. >>>>> >>>>> - Charlie >>>>> >>>>> From: Chris Hoffman <chris.hoffman@berkeley.edu> >>>>> Date: Wed, 4 Jan 2012 13:39:36 -0800 >>>>> To: Charles Moad <cmoad@imamuseum.org> >>>>> Cc: "talk@lists.collectionspace.org" >>> <talk@lists.collectionspace.org> >>>>> Subject: Re: [Talk] CAP 5.5 + CS >>>>> >>>>> Hi Charlie, >>>>> >>>>> At UC Berkeley, we have a very strong need to connect collections >>>>> management and digital assetmanagement functions in the >>> way you describe. >>>>> The Nuxeo DAM has seemed like a good way to go, but we haven't >>>>> really experimented with it here. What's your experience >>> been like? >>>>> Anyway, we'll happily endorsethis too. And if it's something that >>>>> looks like it needs another grant-funded project to do >>> right, maybe >>>>> we could get our institutions to partner on something. >> Just thinking out loud... >>>>> >>>>> Thanks, >>>>> Chris >>>>> >>>>> >>>>> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >>>>> >>>>> >>>>> >>>>> Thanks for following up Patrick. I'll rally my friends. I wouldn't >>>>> expect a CollectionSpace tab in Nuxeo CAP anytime soon >>> either, but it >>>>> would be pretty powerful to have a single repository for the sole >>>>> purpose of relating documents to collection objects, >>> exhibitions, etc. >>>>> >>>>> Keep up the good work, >>>>> Charlie >>>>> >>>>> From: Patrick Schmitz <pschmitz@berkeley.edu> >>>>> Date: Wed, 4 Jan 2012 10:33:48 -0800 >>>>> To: Charles Moad <cmoad@imamuseum.org>, >>>>> <talk@lists.collectionspace.org> >>>>> Subject: RE: [Talk] CAP 5.5 + CS >>>>> >>>>> Hi Charlie - >>>>> >>>>> This is something we would really like to investigate, as >>> many folks >>>>> have expressed at least some interest in this. We have also been >>>>> assured by the Nuxeo folks that this should be possible. At this >>>>> point, it is mostly a matter of resources and priorities. If the >>>>> community rallies support for this as an essential integration, we >>>>> should be able to find time in the Phase 3 project to >>> investigate it. >>>>> >>>>> Note that we are otherwise interested in getting the DM >>> working as a >>>>> diagnostic and support tool, and to aid with import/export >>> workflows. >>>>> As such, there may be some basic investigation (not necessarily >>>>> including DAM/CSpace coordination) in the near term. >>>>> >>>>> I doubt very much that CSpace will appear as a tab in the Nuxeo UI >>>>> any time soon, as this is not ause-case that anyone (else) has yet >>>>> requested. Am not ruling it out, just giving my impression of the >>>>> current project priorities, in response to yourquestion on >>> a related thread. >>>>> >>>>> Thanks for the question - >>>>> >>>>> Patrick >>>>> >>>>> >>>>> >>>>> ________________________________ >>>>> >>>>> From: talk-bounces@lists.collectionspace.org >>>>> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >>> Of Charlie >>>>> Moad >>>>> Sent: Wednesday, January 04, 2012 6:18 AM >>>>> To: talk@lists.collectionspace.org >>>>> Subject: [Talk] CAP 5.5 + CS >>>>> >>>>> What is the feasibility of setting up a single repository >>> running the >>>>> new Nuxeo CAP 5.5 (DM + DAM specifically) and >>> CollectionSpace 2.0 in >>>>> a single repository? I would like to be able to relate >>> documents to >>>>> works in our collection. Any guidance would be greatly appreciated. >>>>> >>>>> Thanks, >>>>> Charlie >>>>> ________________________________ >>>>> >>>>> This email message is for the sole use of the intended >>> recipient(s) >>>>> and may contain confidential and privileged information. Any >>>>> unauthorized review, use, disclosure or distribution is >>> prohibited. >>>>> If you are not the intended recipient, please contact >>> Charlie Moad by >>>>> reply email and destroy all copies of the original message. >>>>> >>>>> ________________________________ >>>>> >>>>> This email message is for the sole use of the intended >>> recipient(s) >>>>> and may contain confidential and privileged information. Any >>>>> unauthorized review, use, disclosure or distribution is >>> prohibited. >>>>> If you are not the intended recipient, please contact >>> Charlie Moad by >>>>> reply email and destroy all copies of the original message. >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> >>>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >>>>> onspace.org >>>>> >>>>> ________________________________ >>>>> >>>>> This email message is for the sole use of the intended >>> recipient(s) >>>>> and may contain confidential and privileged information. Any >>>>> unauthorized review, use, disclosure or distribution is >>> prohibited. >>>>> If you are not the intended recipient, please contact >>> Charlie Moad by >>>>> reply email and destroy all copies of the original message. >>>>> >>>>> ________________________________ >>>>> >>>>> This email message is for the sole use of the intended >>> recipient(s) >>>>> and may contain confidential and privileged information. Any >>>>> unauthorized review, use, disclosure or distribution is >>> prohibited. >>>>> If you are not the intended recipient, please contact >>> Charlie Moad by >>>>> reply email and destroy all copies of the original message. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> >>>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >>>>> onspace.org >>>>> >>>> >>>> ________________________________ >>>> >>>> This email message is for the sole use of the intended recipient(s) >>>> and may contain confidential and privileged information. Any >>>> unauthorized review, use, disclosure or distribution is >>> prohibited. If >>>> you are not the intended recipient, please contact Charlie Moad by >>>> reply email and destroy all copies of the original message. >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >>>> nspace.org >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >>>> nspace.org >>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio >>>> nspace.org >>>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c >>> ollectionspace.org >>> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspa >> ce.org > > ________________________________ > > This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message. > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
PS
Patrick Schmitz
Mon, Feb 27, 2012 4:50 PM

Thanks Charlie.

I agree with your comments, but hesitated to go there. Not because I take an
issue with the substance of your argument, but because I am trying to set
expectations for functionality in this upcoming sprint.

Our goal is to get access to the admin interfaces of the DM app, and not to
provide a seamless integration of the applications. The latter is a longer
term goal, and we've been working with the Nuxeo team to ensure this will be
possible. But for now, we have to be careful about the scope of our sprint.

Of course, we would welcome any contributions you can make in this area, and
appreciate your investigations so far. If you've got time to be involved,
perhaps we can work together on this. I suspect you have more experience
with the DAM that any of us, and as you note, the DAM is closely integrated
with the DM product (more so with the latest releases). Your experience and
your ideas on what an integration would constitute would be very useful.

Thanks - Patrick

-----Original Message-----
From: Charlie Moad [mailto:CMoad@imamuseum.org]
Sent: Monday, February 27, 2012 6:54 AM
To: Patrick Schmitz; 'Aron Roberts'; 'Angela Spinazze'
Cc: 'CollectionSpace Talk List'
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to throw a few thoughts on top of this. Nuxeo DAM
and its features are becoming more and more integrated with
the DM interface, which is far more robust. DAM is not much
more than an advanced/visual search of the DM repository. Any
attempt to integrate with DAM at this point would most likely
lead to headaches and lost code down the road as DAM looks
more and more like part of DM. DM is where the real power and
focus of the Nuxeo team lies. Also, aligning CS with the DM
product would most likely give you DAM integration for free
as the products merge. The CS team is probably aware of this,
but I am imagine others who are not familiar with the DM/DAM
products are not.

  • Charlie

On 2/24/12 5:58 PM, "Patrick Schmitz" pschmitz@berkeley.edu wrote:

Sorry to undermine your joke, but I should note that Nuxeo DM is not
the same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we

used when

we had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same
repo as CSpace.

However, the scope of work in 2.3 is only to look at DM, so that
support for export and diagnostics is restored to what we

had previous

to 2.0. It may well be that once we figure out how to support DM and
CSpace, adding the DAM app to the mix will be

straightforward. However,

integrating DAM is not a goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Aron
Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze ats@atspin.com
wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential

positive impact of

getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation

effort so that

everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

0

and

0

+Proposed+Schedule

We do however, realize how important this functionality

is to many

community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM

interface. What are

the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an

issue, but I

know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us,

and it sounds

like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known

tasks is to

ensure that CollectionSpace can co-exist with Nuxeo's DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace

being able to

co-exist with Nuxeo's applications.  If you feel we need

to make this

work a higher priority, please review the current

release roadmaps

and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at

installing

CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There

appears to be

promise. Two glaring things are that the

"default-domain" that is

normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are

empty. I

would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM

documents and CS

ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we're also in the process of defining our

requirements

for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and

documents to

artworks is also a pressing use case for us - although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for

handling related

texts. In any case I look forward to following your

investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out

the new DAM

software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent

success. We found

the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media

files and

relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect

collections

management and digital assetmanagement functions in the

way you describe.

The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?

Anyway, we'll happily endorsethis too.  And if it's

something that

looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends.

I wouldn't

expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository

for the sole

purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have

also been

assured by the Nuxeo folks that this should be

possible. At this

point, it is mostly a matter of resources and

priorities. If the

community rallies support for this as an essential

integration, we

should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in

the Nuxeo UI

any time soon, as this is not ause-case that anyone

(else) has yet

requested. Am not ruling it out, just giving my

impression of the

current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly

appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

o

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

o

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

collection

spa
ce.org


This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended
recipient, please contact Charlie Moad by reply email and
destroy all copies of the original message.

Thanks Charlie. I agree with your comments, but hesitated to go there. Not because I take an issue with the substance of your argument, but because I am trying to set expectations for functionality in this upcoming sprint. Our goal is to get access to the admin interfaces of the DM app, and not to provide a seamless integration of the applications. The latter is a longer term goal, and we've been working with the Nuxeo team to ensure this will be possible. But for now, we have to be careful about the scope of our sprint. Of course, we would welcome any contributions you can make in this area, and appreciate your investigations so far. If you've got time to be involved, perhaps we can work together on this. I suspect you have more experience with the DAM that any of us, and as you note, the DAM is closely integrated with the DM product (more so with the latest releases). Your experience and your ideas on what an integration would constitute would be very useful. Thanks - Patrick > -----Original Message----- > From: Charlie Moad [mailto:CMoad@imamuseum.org] > Sent: Monday, February 27, 2012 6:54 AM > To: Patrick Schmitz; 'Aron Roberts'; 'Angela Spinazze' > Cc: 'CollectionSpace Talk List' > Subject: Re: [Talk] CAP 5.5 + CS > > I'd like to throw a few thoughts on top of this. Nuxeo DAM > and its features are becoming more and more integrated with > the DM interface, which is far more robust. DAM is not much > more than an advanced/visual search of the DM repository. Any > attempt to integrate with DAM at this point would most likely > lead to headaches and lost code down the road as DAM looks > more and more like part of DM. DM is where the real power and > focus of the Nuxeo team lies. Also, aligning CS with the DM > product would most likely give you DAM integration for free > as the products merge. The CS team is probably aware of this, > but I am imagine others who are not familiar with the DM/DAM > products are not. > > > - Charlie > > On 2/24/12 5:58 PM, "Patrick Schmitz" <pschmitz@berkeley.edu> wrote: > > >Sorry to undermine your joke, but I should note that Nuxeo DM is not > >the same as Nuxeo DAM. > > > >Nuxeo DM is the traditional Nuxeo doc management app that we > used when > >we had the dual-server (JBoss) setup. > > > >Nuxeo DAM is the Digital Asset Management application. > > > >We would like (eventually) to support both, integrated with the same > >repo as CSpace. > > > >However, the scope of work in 2.3 is only to look at DM, so that > >support for export and diagnostics is restored to what we > had previous > >to 2.0. It may well be that once we figure out how to support DM and > >CSpace, adding the DAM app to the mix will be > straightforward. However, > >integrating DAM is not a goal in the 2.3 release. > > > >Patrick > > > >> -----Original Message----- > >> From: talk-bounces@lists.collectionspace.org > >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Aron > >> Roberts > >> Sent: Friday, February 24, 2012 1:41 PM > >> To: Angela Spinazze > >> Cc: CollectionSpace Talk List > >> Subject: Re: [Talk] CAP 5.5 + CS > >> > >> DAM the torpedoes, and full speed ahead? > >> > >> Aron > >> > >> (With due apologies ... it's Friday afternoon) > >> http://en.wiktionary.org/wiki/damn_the_torpedoes > >> > >> On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze <ats@atspin.com> > >> wrote: > >> > Hi all, > >> > > >> > A brief update for you on this Nuxeo DM question. > >> > > >> > As Patrick mentioned in an earlier post to this thread > >> (January 4th) > >> > "Note that we are otherwise interested in getting the DM > >> working as a > >> > diagnostic and support tool, and to aid with import/export > >> workflows. > >> > As such, there may be some basic investigation (not necessarily > >> > including DAM/CSpace > >> > coordination) in the near term." > >> > > >> > Given the level of interest in and the potential > positive impact of > >> > getting the DM working as a diagnostic support tool, we > >> will include > >> > investigation into the effort required to do so in the > >> scope of work > >> > for the release 2.3 (scheduled to begin on March 5th). > >Based on what > >> > we discover in the research phase, we will determine > >> if/when the work > >> > might be scheduled to take place within the current schedule. > >> > > >> > We'll be creating a new Jira for this investigation > effort so that > >> > everyone who is interested can keep an eye on our progress. > >> > > >> > Cheers, > >> > > >> > Angela > >> > > >> > > >> > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: > >> > > >> > Hi Charlie, > >> > > >> > Patrick, Megan and I will be discussing this work tomorrow > >> afternoon > >> > to determine just what is required and we will follow up on this > >> > thread once we've had a chance to explore this in more detail. > >> > > >> > As Richard pointed out, we have our core CollectionSpace > >> development > >> > schedule set through September 2012 > >> > > >> > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3. > >> 0 > >> > and > >> > > >> > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3. > >> 0 > >> > +Proposed+Schedule > >> > > >> > We do however, realize how important this functionality > is to many > >> > community members. Thanks very much for keeping this > >> conversation alive! > >> > > >> > Angela > >> > > >> > > >> > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > >> > > >> > It would help to know if someone could express what would > >> be involved > >> > in this process. It seems like it could be really close if > >> it is just > >> > a matter of exposing the CS doc types in the DM > interface. What are > >> > the complicating factors beyond that? > >> > > >> > - Charlie > >> > > >> > From: Nate Solas <nate.solas@walkerart.org> > >> > Date: Tue, 21 Feb 2012 11:52:38 -0600 > >> > To: Richard Millet <richard.millet@berkeley.edu> > >> > Cc: Charles Moad <cmoad@imamuseum.org>, > >> > <talk@lists.collectionspace.org> > >> > Subject: Re: [Talk] CAP 5.5 + CS > >> > > >> > I'd like to +1 a raised priority for this, but I'm not > >> entirely sure > >> > what to recommend bumping. For us, and I suspect most of > >> the current > >> > implementers, the multi-tenant service isn't as big an > issue, but I > >> > know it's core to the long-term sustainability of the software. > >> > > >> > It seems like there might be some room for this work in the 2.3 > >> > roadmap? I don't know how big a chunk the Location and > >> Movement rewrite is. > >> > > >> > Thanks for considering it. This would be huge for us, > and it sounds > >> > like there is a lot of support out there. > >> > Nate > >> > > >> > > >> > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet > >> > <richard.millet@berkeley.edu> wrote: > >> >> > >> >> Charlie, > >> >> > >> >> Thanks for experimenting with this. One of our known > tasks is to > >> >> ensure that CollectionSpace can co-exist with Nuxeo's DM > >> and DAM applications. > >> >> Unfortunately, this work is not currently scheduled to > >> happen anytime soon. > >> >> However, we understand the value of CollectionSpace > being able to > >> >> co-exist with Nuxeo's applications. If you feel we need > >> to make this > >> >> work a higher priority, please review the current > release roadmaps > >> >> and see how this work compares to what we have planned. If you > >> >> decide this work is more important, let us know and we can > >> try to raise its priority. > >> >> > >> >> -Richard > >> >> > >> >> > >> >> From: talk-bounces@lists.collectionspace.org > >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf > >> Of Charlie > >> >> Moad > >> >> Sent: Thursday, February 16, 2012 7:14 PM > >> >> To: Christopher Pott; Chris Hoffman > >> >> Cc: talk@lists.collectionspace.org > >> >> > >> >> Subject: Re: [Talk] CAP 5.5 + CS > >> >> > >> >> > >> >> I haven't had much time, but I took a naïve attempt at > installing > >> >> CS+DM+DAM all on the same postgres database. I am attaching two > >> >> CS+DM+screenshots > >> >> of the results. There are only a few errors during the DM+DAM > >> >> startup, but things seem to run well enough. There > appears to be > >> >> promise. Two glaring things are that the > "default-domain" that is > >> >> normally part of the top-level of DM is missing. Looking > >> inside each > >> >> CS domain shows a workspace for each type, but they are > empty. I > >> >> would hope that it is only a matter of adding the proper Nuxeo > >> >> extensions to expose these types to the DM interface. Any > >> insight the > >> >> development team has would be interesting. In the mean > >> time I believe we are going to relate our DM documents to > >> placeholders documents. > >> >> The prospect of creating relationship between DM > documents and CS > >> >> ones feels close though. > >> >> > >> >> - Charlie > >> >> > >> >> From: Christopher Pott <Christopher.Pott@smk.dk> > >> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 > >> >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman > >> >> <chris.hoffman@berkeley.edu> > >> >> Cc: <talk@lists.collectionspace.org> > >> >> Subject: SV: [Talk] CAP 5.5 + CS > >> >> > >> >> Hi Charlie, > >> >> > >> >> Here at SMK we're also in the process of defining our > requirements > >> >> for a DAM solution and as a part of this process have also > >> tested an > >> >> earlier Nuxeo DAM version. It was basic, but seemed fast > >> and stable > >> >> in the short period we tested it. Relating texts and > documents to > >> >> artworks is also a pressing use case for us - although > >> Ihope we can > >> >> integrate this into CollectionSpace either through the > >> Media Handling > >> >> procedure by supporting some new document types (pdf, doc, > >> html etc.) > >> >> or possibly even by creating a new procedure for > handling related > >> >> texts. In any case I look forward to following your > investigations. > >> >> > >> >> Regards, > >> >> (another) Chris > >> >> > >> >> ________________________________ > >> >> Fra: talk-bounces@lists.collectionspace.org > >> >> [mailto:talk-bounces@lists.collectionspace.org] På vegne > >> af Charlie > >> >> Moad > >> >> Sendt: 4. januar 2012 22:48 > >> >> Til: Chris Hoffman > >> >> Cc: talk@lists.collectionspace.org > >> >> Emne: Re: [Talk] CAP 5.5 + CS > >> >> > >> >> At the IMA we are just in the process of rolling out > the new DAM > >> >> software based on 5.5. We have been using DM with a select > >> group of > >> >> staff members for several months now with decent > success. We found > >> >> the previous versions of DAM lacking some very basic needs > >> and many > >> >> of those have been addressed in the latest release. We > >> even paid for > >> >> the development of some of those enhancements. In general > >> Nuxeo DAM > >> >> is fairly simple, but that's all that we (and I suspect > >> many museums) > >> >> need. We need it to be able to handle and preview media > files and > >> >> relate them to our institution. I'm not entirely sure what > >> the effort would be and if much additional work would be required. > >> >> That's why I reached out. I'll continue to investigate > >> this and come > >> >> back with progress I might have. > >> >> > >> >> - Charlie > >> >> > >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> > >> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 > >> >> To: Charles Moad <cmoad@imamuseum.org> > >> >> Cc: "talk@lists.collectionspace.org" > >> <talk@lists.collectionspace.org> > >> >> Subject: Re: [Talk] CAP 5.5 + CS > >> >> > >> >> Hi Charlie, > >> >> > >> >> At UC Berkeley, we have a very strong need to connect > collections > >> >> management and digital assetmanagement functions in the > >> way you describe. > >> >> The Nuxeo DAM has seemed like a good way to go, but we haven't > >> >> really experimented with it here. What's your experience > >> been like? > >> >> Anyway, we'll happily endorsethis too. And if it's > something that > >> >> looks like it needs another grant-funded project to do > >> right, maybe > >> >> we could get our institutions to partner on something. > >Just thinking out loud... > >> >> > >> >> Thanks, > >> >> Chris > >> >> > >> >> > >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: > >> >> > >> >> > >> >> > >> >> Thanks for following up Patrick. I'll rally my friends. > I wouldn't > >> >> expect a CollectionSpace tab in Nuxeo CAP anytime soon > >> either, but it > >> >> would be pretty powerful to have a single repository > for the sole > >> >> purpose of relating documents to collection objects, > >> exhibitions, etc. > >> >> > >> >> Keep up the good work, > >> >> Charlie > >> >> > >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> > >> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 > >> >> To: Charles Moad <cmoad@imamuseum.org>, > >> >> <talk@lists.collectionspace.org> > >> >> Subject: RE: [Talk] CAP 5.5 + CS > >> >> > >> >> Hi Charlie - > >> >> > >> >> This is something we would really like to investigate, as > >> many folks > >> >> have expressed at least some interest in this. We have > also been > >> >> assured by the Nuxeo folks that this should be > possible. At this > >> >> point, it is mostly a matter of resources and > priorities. If the > >> >> community rallies support for this as an essential > integration, we > >> >> should be able to find time in the Phase 3 project to > >> investigate it. > >> >> > >> >> Note that we are otherwise interested in getting the DM > >> working as a > >> >> diagnostic and support tool, and to aid with import/export > >> workflows. > >> >> As such, there may be some basic investigation (not necessarily > >> >> including DAM/CSpace coordination) in the near term. > >> >> > >> >> I doubt very much that CSpace will appear as a tab in > the Nuxeo UI > >> >> any time soon, as this is not ause-case that anyone > (else) has yet > >> >> requested. Am not ruling it out, just giving my > impression of the > >> >> current project priorities, in response to yourquestion on > >> a related thread. > >> >> > >> >> Thanks for the question - > >> >> > >> >> Patrick > >> >> > >> >> > >> >> > >> >> ________________________________ > >> >> > >> >> From: talk-bounces@lists.collectionspace.org > >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf > >> Of Charlie > >> >> Moad > >> >> Sent: Wednesday, January 04, 2012 6:18 AM > >> >> To: talk@lists.collectionspace.org > >> >> Subject: [Talk] CAP 5.5 + CS > >> >> > >> >> What is the feasibility of setting up a single repository > >> running the > >> >> new Nuxeo CAP 5.5 (DM + DAM specifically) and > >> CollectionSpace 2.0 in > >> >> a single repository? I would like to be able to relate > >> documents to > >> >> works in our collection. Any guidance would be greatly > appreciated. > >> >> > >> >> Thanks, > >> >> Charlie > >> >> ________________________________ > >> >> > >> >> This email message is for the sole use of the intended > >> recipient(s) > >> >> and may contain confidential and privileged information. Any > >> >> unauthorized review, use, disclosure or distribution is > >> prohibited. > >> >> If you are not the intended recipient, please contact > >> Charlie Moad by > >> >> reply email and destroy all copies of the original message. > >> >> > >> >> ________________________________ > >> >> > >> >> This email message is for the sole use of the intended > >> recipient(s) > >> >> and may contain confidential and privileged information. Any > >> >> unauthorized review, use, disclosure or distribution is > >> prohibited. > >> >> If you are not the intended recipient, please contact > >> Charlie Moad by > >> >> reply email and destroy all copies of the original message. > >> >> > >> >> _______________________________________________ > >> >> Talk mailing list > >> >> Talk@lists.collectionspace.org > >> >> > >> >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> >> onspace.org > >> >> > >> >> ________________________________ > >> >> > >> >> This email message is for the sole use of the intended > >> recipient(s) > >> >> and may contain confidential and privileged information. Any > >> >> unauthorized review, use, disclosure or distribution is > >> prohibited. > >> >> If you are not the intended recipient, please contact > >> Charlie Moad by > >> >> reply email and destroy all copies of the original message. > >> >> > >> >> ________________________________ > >> >> > >> >> This email message is for the sole use of the intended > >> recipient(s) > >> >> and may contain confidential and privileged information. Any > >> >> unauthorized review, use, disclosure or distribution is > >> prohibited. > >> >> If you are not the intended recipient, please contact > >> Charlie Moad by > >> >> reply email and destroy all copies of the original message. > >> >> > >> >> > >> >> _______________________________________________ > >> >> Talk mailing list > >> >> Talk@lists.collectionspace.org > >> >> > >> >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> >> onspace.org > >> >> > >> > > >> > ________________________________ > >> > > >> > This email message is for the sole use of the intended > recipient(s) > >> > and may contain confidential and privileged information. Any > >> > unauthorized review, use, disclosure or distribution is > >> prohibited. If > >> > you are not the intended recipient, please contact > Charlie Moad by > >> > reply email and destroy all copies of the original message. > >> > > >> > _______________________________________________ > >> > Talk mailing list > >> > Talk@lists.collectionspace.org > >> > > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> o > >> > nspace.org > >> > > >> > > >> > _______________________________________________ > >> > Talk mailing list > >> > Talk@lists.collectionspace.org > >> > > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> o > >> > nspace.org > >> > > >> > > >> > > >> > _______________________________________________ > >> > Talk mailing list > >> > Talk@lists.collectionspace.org > >> > > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti > >> o > >> > nspace.org > >> > > >> > >> _______________________________________________ > >> Talk mailing list > >> Talk@lists.collectionspace.org > >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c > >> ollectionspace.org > >> > > > > > >_______________________________________________ > >Talk mailing list > >Talk@lists.collectionspace.org > >http://lists.collectionspace.org/mailman/listinfo/talk_lists. > collection > >spa > >ce.org > > ________________________________ > > This email message is for the sole use of the intended > recipient(s) and may contain confidential and privileged > information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended > recipient, please contact Charlie Moad by reply email and > destroy all copies of the original message. >
CM
Charlie Moad
Mon, Feb 27, 2012 5:07 PM

It sounds like you are adding integration above and beyond what I was
expecting. I'll try to summarize what I see as most immediately beneficial
from a DM+DAM user perspective.

  1. CollectionSpace and Nuxeo CAP (with DM and possibly DAM enabled)
    running on the same database.
    A. This could mean running two tomcat installations pointing at the
    same database, which is what I had some success with and shared
    screenshots of. This approach gives me some concerns, because I remember
    having to enable some special clustering options when running DM and DAM
    as different tomcat installs.
    B. A more appealing approach would be having CollectionSpace and the
    CAP running inside the same tomcat as two different web apps. Hopefully
    this would remove any database contention or special configuration.

  2. Simply having the CollectionSpace documents appear in a read-only
    domain in DM. Also, from the screen shots this looks close. It might just
    be a matter of adding the appropriate extensions to expose the CS
    documents as DM documents. I could most likely offer some help here since
    I am familiar with adding custom document types to DM.

That's it for now. Having placeholder objects available in DM so relations
can be created with other documents would be huge. Then we could create
relations to know what artwork a photograph is taken of, which artwork a
conservation treatment report is of, what exhibition a loan agreement is
for, and so on.

I'm more than happy to contribute some code on the DM side of the fence.

  • Charlie

On 2/27/12 11:50 AM, "Patrick Schmitz" pschmitz@berkeley.edu wrote:

Thanks Charlie.

I agree with your comments, but hesitated to go there. Not because I take
an
issue with the substance of your argument, but because I am trying to set
expectations for functionality in this upcoming sprint.

Our goal is to get access to the admin interfaces of the DM app, and not
to
provide a seamless integration of the applications. The latter is a longer
term goal, and we've been working with the Nuxeo team to ensure this will
be
possible. But for now, we have to be careful about the scope of our
sprint.

Of course, we would welcome any contributions you can make in this area,
and
appreciate your investigations so far. If you've got time to be involved,
perhaps we can work together on this. I suspect you have more experience
with the DAM that any of us, and as you note, the DAM is closely
integrated
with the DM product (more so with the latest releases). Your experience
and
your ideas on what an integration would constitute would be very useful.

Thanks - Patrick

-----Original Message-----
From: Charlie Moad [mailto:CMoad@imamuseum.org]
Sent: Monday, February 27, 2012 6:54 AM
To: Patrick Schmitz; 'Aron Roberts'; 'Angela Spinazze'
Cc: 'CollectionSpace Talk List'
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to throw a few thoughts on top of this. Nuxeo DAM
and its features are becoming more and more integrated with
the DM interface, which is far more robust. DAM is not much
more than an advanced/visual search of the DM repository. Any
attempt to integrate with DAM at this point would most likely
lead to headaches and lost code down the road as DAM looks
more and more like part of DM. DM is where the real power and
focus of the Nuxeo team lies. Also, aligning CS with the DM
product would most likely give you DAM integration for free
as the products merge. The CS team is probably aware of this,
but I am imagine others who are not familiar with the DM/DAM
products are not.

  • Charlie

On 2/24/12 5:58 PM, "Patrick Schmitz" pschmitz@berkeley.edu wrote:

Sorry to undermine your joke, but I should note that Nuxeo DM is not
the same as Nuxeo DAM.

Nuxeo DM is the traditional Nuxeo doc management app that we

used when

we had the dual-server (JBoss) setup.

Nuxeo DAM is the Digital Asset Management application.

We would like (eventually) to support both, integrated with the same
repo as CSpace.

However, the scope of work in 2.3 is only to look at DM, so that
support for export and diagnostics is restored to what we

had previous

to 2.0. It may well be that once we figure out how to support DM and
CSpace, adding the DAM app to the mix will be

straightforward. However,

integrating DAM is not a goal in the 2.3 release.

Patrick

-----Original Message-----
From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Aron
Roberts
Sent: Friday, February 24, 2012 1:41 PM
To: Angela Spinazze
Cc: CollectionSpace Talk List
Subject: Re: [Talk] CAP 5.5 + CS

DAM the torpedoes, and full speed ahead?

Aron

(With due apologies ... it's Friday afternoon)
http://en.wiktionary.org/wiki/damn_the_torpedoes

On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze ats@atspin.com
wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread

(January 4th)

"Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential

positive impact of

getting the DM working as a diagnostic support tool, we

will include

investigation into the effort required to do so in the

scope of work

for the release 2.3 (scheduled to begin on March 5th).

Based on what

we discover in the research phase, we will determine

if/when the work

might be scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation

effort so that

everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow

afternoon

to determine just what is required and we will follow up on this
thread once we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace

development

schedule set through September 2012

0

and

0

+Proposed+Schedule

We do however, realize how important this functionality

is to many

community members. Thanks very much for keeping this

conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would

be involved

in this process. It seems like it could be really close if

it is just

a matter of exposing the CS doc types in the DM

interface. What are

the complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not

entirely sure

what to recommend bumping. For us, and I suspect most of

the current

implementers, the multi-tenant service isn't as big an

issue, but I

know it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3
roadmap? I don't know how big a chunk the Location and

Movement rewrite is.

Thanks for considering it. This would be huge for us,

and it sounds

like there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet
richard.millet@berkeley.edu wrote:

Charlie,

Thanks for experimenting with this.  One of our known

tasks is to

ensure that CollectionSpace can co-exist with Nuxeo's DM

and DAM applications.

Unfortunately, this work is not currently scheduled to

happen anytime soon.

However, we understand the value of CollectionSpace

being able to

co-exist with Nuxeo's applications.  If you feel we need

to make this

work a higher priority, please review the current

release roadmaps

and see how this work compares to what we have planned.  If you
decide this work is more important, let us know and we can

try to raise its priority.

Of Charlie

Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS

I haven't had much time, but I took a naïve attempt at

installing

CS+DM+DAM all on the same postgres database. I am attaching two
CS+DM+screenshots
of the results. There are only a few errors during the DM+DAM
startup, but things seem to run well enough. There

appears to be

promise. Two glaring things are that the

"default-domain" that is

normally part of the top-level of DM is missing. Looking

inside each

CS domain shows a workspace for each type, but they are

empty. I

would hope that it is only a matter of adding the proper Nuxeo
extensions to expose these types to the DM interface. Any

insight the

development team has would be interesting. In the mean

time I believe we are going to relate our DM documents to
placeholders documents.

The prospect of creating relationship between DM

documents and CS

ones feels close though.

  • Charlie

From: Christopher Pott Christopher.Pott@smk.dk
Date: Wed, 11 Jan 2012 14:35:34 +0100
To: Charles Moad cmoad@imamuseum.org, Chris Hoffman
chris.hoffman@berkeley.edu
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS

Hi Charlie,

Here at SMK we're also in the process of defining our

requirements

for a DAM solution and as a part of this process have also

tested an

earlier Nuxeo DAM version. It was basic, but seemed fast

and stable

in the short period we tested it. Relating texts and

documents to

artworks is also a pressing use case for us - although

Ihope we can

integrate this into CollectionSpace either through the

Media Handling

procedure by supporting some new document types (pdf, doc,

html etc.)

or possibly even by creating a new procedure for

handling related

texts. In any case I look forward to following your

investigations.

Regards,
(another) Chris


Fra: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] På vegne

af Charlie

Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS

At the IMA we are just in the process of rolling out

the new DAM

software based on 5.5. We have been using DM with a select

group of

staff members for several months now with decent

success. We found

the previous versions of DAM lacking some very basic needs

and many

of those have been addressed in the latest release. We

even paid for

the development of some of those enhancements. In general

Nuxeo DAM

is fairly simple, but that's all that we (and I suspect

many museums)

need. We need it to be able to handle and preview media

files and

relate them to our institution. I'm not entirely sure what

the effort would be and if much additional work would be required.

That's why I reached out. I'll continue to investigate

this and come

back with progress I might have.

  • Charlie

From: Chris Hoffman chris.hoffman@berkeley.edu
Date: Wed, 4 Jan 2012 13:39:36 -0800
To: Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org"

Subject: Re: [Talk] CAP 5.5 + CS

Hi Charlie,

At UC Berkeley, we have a very strong need to connect

collections

management and digital assetmanagement functions in the

way you describe.

The Nuxeo DAM has seemed like a good way to go, but we haven't
really experimented with it here.  What's your experience

been like?

Anyway, we'll happily endorsethis too.  And if it's

something that

looks like it needs another grant-funded project to do

right, maybe

we could get our institutions to partner on something.

Just thinking out loud...

Thanks,
Chris

On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:

Thanks for following up Patrick. I'll rally my friends.

I wouldn't

expect a CollectionSpace tab in Nuxeo CAP anytime soon

either, but it

would be pretty powerful to have a single repository

for the sole

purpose of relating documents to collection objects,

exhibitions, etc.

Keep up the good work,
Charlie

From: Patrick Schmitz pschmitz@berkeley.edu
Date: Wed, 4 Jan 2012 10:33:48 -0800
To: Charles Moad cmoad@imamuseum.org,
talk@lists.collectionspace.org
Subject: RE: [Talk] CAP 5.5 + CS

Hi Charlie -

This is something we would really like to investigate, as

many folks

have expressed at least some interest in this. We have

also been

assured by the Nuxeo folks that this should be

possible. At this

point, it is mostly a matter of resources and

priorities. If the

community rallies support for this as an essential

integration, we

should be able to find time in the Phase 3 project to

investigate it.

Note that we are otherwise interested in getting the DM

working as a

diagnostic and support tool, and to aid with import/export

workflows.

As such, there may be some basic investigation (not necessarily
including DAM/CSpace coordination) in the near term.

I doubt very much that CSpace will appear as a tab in

the Nuxeo UI

any time soon, as this is not ause-case that anyone

(else) has yet

requested. Am not ruling it out, just giving my

impression of the

current project priorities, in response to yourquestion on

a related thread.

Thanks for the question -

Patrick


From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf

Of Charlie

Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS

What is the feasibility of setting up a single repository

running the

new Nuxeo CAP 5.5 (DM + DAM specifically) and

CollectionSpace 2.0 in

a single repository? I would like to be able to relate

documents to

works in our collection. Any guidance would be greatly

appreciated.

Thanks,
Charlie


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited.

If you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

onspace.org


This email message is for the sole use of the intended

recipient(s)

and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is

prohibited. If

you are not the intended recipient, please contact

Charlie Moad by

reply email and destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

o

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

o

nspace.org


Talk mailing list
Talk@lists.collectionspace.org

collection

spa
ce.org


This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended
recipient, please contact Charlie Moad by reply email and
destroy all copies of the original message.


This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message.

It sounds like you are adding integration above and beyond what I was expecting. I'll try to summarize what I see as most immediately beneficial from a DM+DAM user perspective. 1. CollectionSpace and Nuxeo CAP (with DM and possibly DAM enabled) running on the same database. A. This could mean running two tomcat installations pointing at the same database, which is what I had some success with and shared screenshots of. This approach gives me some concerns, because I remember having to enable some special clustering options when running DM and DAM as different tomcat installs. B. A more appealing approach would be having CollectionSpace and the CAP running inside the same tomcat as two different web apps. Hopefully this would remove any database contention or special configuration. 2. Simply having the CollectionSpace documents appear in a read-only domain in DM. Also, from the screen shots this looks close. It might just be a matter of adding the appropriate extensions to expose the CS documents as DM documents. I could most likely offer some help here since I am familiar with adding custom document types to DM. That's it for now. Having placeholder objects available in DM so relations can be created with other documents would be huge. Then we could create relations to know what artwork a photograph is taken of, which artwork a conservation treatment report is of, what exhibition a loan agreement is for, and so on. I'm more than happy to contribute some code on the DM side of the fence. - Charlie On 2/27/12 11:50 AM, "Patrick Schmitz" <pschmitz@berkeley.edu> wrote: >Thanks Charlie. > >I agree with your comments, but hesitated to go there. Not because I take >an >issue with the substance of your argument, but because I am trying to set >expectations for functionality in this upcoming sprint. > >Our goal is to get access to the admin interfaces of the DM app, and not >to >provide a seamless integration of the applications. The latter is a longer >term goal, and we've been working with the Nuxeo team to ensure this will >be >possible. But for now, we have to be careful about the scope of our >sprint. > >Of course, we would welcome any contributions you can make in this area, >and >appreciate your investigations so far. If you've got time to be involved, >perhaps we can work together on this. I suspect you have more experience >with the DAM that any of us, and as you note, the DAM is closely >integrated >with the DM product (more so with the latest releases). Your experience >and >your ideas on what an integration would constitute would be very useful. > >Thanks - Patrick > >> -----Original Message----- >> From: Charlie Moad [mailto:CMoad@imamuseum.org] >> Sent: Monday, February 27, 2012 6:54 AM >> To: Patrick Schmitz; 'Aron Roberts'; 'Angela Spinazze' >> Cc: 'CollectionSpace Talk List' >> Subject: Re: [Talk] CAP 5.5 + CS >> >> I'd like to throw a few thoughts on top of this. Nuxeo DAM >> and its features are becoming more and more integrated with >> the DM interface, which is far more robust. DAM is not much >> more than an advanced/visual search of the DM repository. Any >> attempt to integrate with DAM at this point would most likely >> lead to headaches and lost code down the road as DAM looks >> more and more like part of DM. DM is where the real power and >> focus of the Nuxeo team lies. Also, aligning CS with the DM >> product would most likely give you DAM integration for free >> as the products merge. The CS team is probably aware of this, >> but I am imagine others who are not familiar with the DM/DAM >> products are not. >> >> >> - Charlie >> >> On 2/24/12 5:58 PM, "Patrick Schmitz" <pschmitz@berkeley.edu> wrote: >> >> >Sorry to undermine your joke, but I should note that Nuxeo DM is not >> >the same as Nuxeo DAM. >> > >> >Nuxeo DM is the traditional Nuxeo doc management app that we >> used when >> >we had the dual-server (JBoss) setup. >> > >> >Nuxeo DAM is the Digital Asset Management application. >> > >> >We would like (eventually) to support both, integrated with the same >> >repo as CSpace. >> > >> >However, the scope of work in 2.3 is only to look at DM, so that >> >support for export and diagnostics is restored to what we >> had previous >> >to 2.0. It may well be that once we figure out how to support DM and >> >CSpace, adding the DAM app to the mix will be >> straightforward. However, >> >integrating DAM is not a goal in the 2.3 release. >> > >> >Patrick >> > >> >> -----Original Message----- >> >> From: talk-bounces@lists.collectionspace.org >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Aron >> >> Roberts >> >> Sent: Friday, February 24, 2012 1:41 PM >> >> To: Angela Spinazze >> >> Cc: CollectionSpace Talk List >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> DAM the torpedoes, and full speed ahead? >> >> >> >> Aron >> >> >> >> (With due apologies ... it's Friday afternoon) >> >> http://en.wiktionary.org/wiki/damn_the_torpedoes >> >> >> >> On Fri, Feb 24, 2012 at 1:31 PM, Angela Spinazze <ats@atspin.com> >> >> wrote: >> >> > Hi all, >> >> > >> >> > A brief update for you on this Nuxeo DM question. >> >> > >> >> > As Patrick mentioned in an earlier post to this thread >> >> (January 4th) >> >> > "Note that we are otherwise interested in getting the DM >> >> working as a >> >> > diagnostic and support tool, and to aid with import/export >> >> workflows. >> >> > As such, there may be some basic investigation (not necessarily >> >> > including DAM/CSpace >> >> > coordination) in the near term." >> >> > >> >> > Given the level of interest in and the potential >> positive impact of >> >> > getting the DM working as a diagnostic support tool, we >> >> will include >> >> > investigation into the effort required to do so in the >> >> scope of work >> >> > for the release 2.3 (scheduled to begin on March 5th). >> >Based on what >> >> > we discover in the research phase, we will determine >> >> if/when the work >> >> > might be scheduled to take place within the current schedule. >> >> > >> >> > We'll be creating a new Jira for this investigation >> effort so that >> >> > everyone who is interested can keep an eye on our progress. >> >> > >> >> > Cheers, >> >> > >> >> > Angela >> >> > >> >> > >> >> > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: >> >> > >> >> > Hi Charlie, >> >> > >> >> > Patrick, Megan and I will be discussing this work tomorrow >> >> afternoon >> >> > to determine just what is required and we will follow up on this >> >> > thread once we've had a chance to explore this in more detail. >> >> > >> >> > As Richard pointed out, we have our core CollectionSpace >> >> development >> >> > schedule set through September 2012 >> >> > >> >> >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3. >> >> 0 >> >> > and >> >> > >> >> >> http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3. >> >> 0 >> >> > +Proposed+Schedule >> >> > >> >> > We do however, realize how important this functionality >> is to many >> >> > community members. Thanks very much for keeping this >> >> conversation alive! >> >> > >> >> > Angela >> >> > >> >> > >> >> > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: >> >> > >> >> > It would help to know if someone could express what would >> >> be involved >> >> > in this process. It seems like it could be really close if >> >> it is just >> >> > a matter of exposing the CS doc types in the DM >> interface. What are >> >> > the complicating factors beyond that? >> >> > >> >> > - Charlie >> >> > >> >> > From: Nate Solas <nate.solas@walkerart.org> >> >> > Date: Tue, 21 Feb 2012 11:52:38 -0600 >> >> > To: Richard Millet <richard.millet@berkeley.edu> >> >> > Cc: Charles Moad <cmoad@imamuseum.org>, >> >> > <talk@lists.collectionspace.org> >> >> > Subject: Re: [Talk] CAP 5.5 + CS >> >> > >> >> > I'd like to +1 a raised priority for this, but I'm not >> >> entirely sure >> >> > what to recommend bumping. For us, and I suspect most of >> >> the current >> >> > implementers, the multi-tenant service isn't as big an >> issue, but I >> >> > know it's core to the long-term sustainability of the software. >> >> > >> >> > It seems like there might be some room for this work in the 2.3 >> >> > roadmap? I don't know how big a chunk the Location and >> >> Movement rewrite is. >> >> > >> >> > Thanks for considering it. This would be huge for us, >> and it sounds >> >> > like there is a lot of support out there. >> >> > Nate >> >> > >> >> > >> >> > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet >> >> > <richard.millet@berkeley.edu> wrote: >> >> >> >> >> >> Charlie, >> >> >> >> >> >> Thanks for experimenting with this. One of our known >> tasks is to >> >> >> ensure that CollectionSpace can co-exist with Nuxeo's DM >> >> and DAM applications. >> >> >> Unfortunately, this work is not currently scheduled to >> >> happen anytime soon. >> >> >> However, we understand the value of CollectionSpace >> being able to >> >> >> co-exist with Nuxeo's applications. If you feel we need >> >> to make this >> >> >> work a higher priority, please review the current >> release roadmaps >> >> >> and see how this work compares to what we have planned. If you >> >> >> decide this work is more important, let us know and we can >> >> try to raise its priority. >> >> >> >> >> >> -Richard >> >> >> >> >> >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> >> Of Charlie >> >> >> Moad >> >> >> Sent: Thursday, February 16, 2012 7:14 PM >> >> >> To: Christopher Pott; Chris Hoffman >> >> >> Cc: talk@lists.collectionspace.org >> >> >> >> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> >> >> >> >> >> I haven't had much time, but I took a naïve attempt at >> installing >> >> >> CS+DM+DAM all on the same postgres database. I am attaching two >> >> >> CS+DM+screenshots >> >> >> of the results. There are only a few errors during the DM+DAM >> >> >> startup, but things seem to run well enough. There >> appears to be >> >> >> promise. Two glaring things are that the >> "default-domain" that is >> >> >> normally part of the top-level of DM is missing. Looking >> >> inside each >> >> >> CS domain shows a workspace for each type, but they are >> empty. I >> >> >> would hope that it is only a matter of adding the proper Nuxeo >> >> >> extensions to expose these types to the DM interface. Any >> >> insight the >> >> >> development team has would be interesting. In the mean >> >> time I believe we are going to relate our DM documents to >> >> placeholders documents. >> >> >> The prospect of creating relationship between DM >> documents and CS >> >> >> ones feels close though. >> >> >> >> >> >> - Charlie >> >> >> >> >> >> From: Christopher Pott <Christopher.Pott@smk.dk> >> >> >> Date: Wed, 11 Jan 2012 14:35:34 +0100 >> >> >> To: Charles Moad <cmoad@imamuseum.org>, Chris Hoffman >> >> >> <chris.hoffman@berkeley.edu> >> >> >> Cc: <talk@lists.collectionspace.org> >> >> >> Subject: SV: [Talk] CAP 5.5 + CS >> >> >> >> >> >> Hi Charlie, >> >> >> >> >> >> Here at SMK we're also in the process of defining our >> requirements >> >> >> for a DAM solution and as a part of this process have also >> >> tested an >> >> >> earlier Nuxeo DAM version. It was basic, but seemed fast >> >> and stable >> >> >> in the short period we tested it. Relating texts and >> documents to >> >> >> artworks is also a pressing use case for us - although >> >> Ihope we can >> >> >> integrate this into CollectionSpace either through the >> >> Media Handling >> >> >> procedure by supporting some new document types (pdf, doc, >> >> html etc.) >> >> >> or possibly even by creating a new procedure for >> handling related >> >> >> texts. In any case I look forward to following your >> investigations. >> >> >> >> >> >> Regards, >> >> >> (another) Chris >> >> >> >> >> >> ________________________________ >> >> >> Fra: talk-bounces@lists.collectionspace.org >> >> >> [mailto:talk-bounces@lists.collectionspace.org] På vegne >> >> af Charlie >> >> >> Moad >> >> >> Sendt: 4. januar 2012 22:48 >> >> >> Til: Chris Hoffman >> >> >> Cc: talk@lists.collectionspace.org >> >> >> Emne: Re: [Talk] CAP 5.5 + CS >> >> >> >> >> >> At the IMA we are just in the process of rolling out >> the new DAM >> >> >> software based on 5.5. We have been using DM with a select >> >> group of >> >> >> staff members for several months now with decent >> success. We found >> >> >> the previous versions of DAM lacking some very basic needs >> >> and many >> >> >> of those have been addressed in the latest release. We >> >> even paid for >> >> >> the development of some of those enhancements. In general >> >> Nuxeo DAM >> >> >> is fairly simple, but that's all that we (and I suspect >> >> many museums) >> >> >> need. We need it to be able to handle and preview media >> files and >> >> >> relate them to our institution. I'm not entirely sure what >> >> the effort would be and if much additional work would be required. >> >> >> That's why I reached out. I'll continue to investigate >> >> this and come >> >> >> back with progress I might have. >> >> >> >> >> >> - Charlie >> >> >> >> >> >> From: Chris Hoffman <chris.hoffman@berkeley.edu> >> >> >> Date: Wed, 4 Jan 2012 13:39:36 -0800 >> >> >> To: Charles Moad <cmoad@imamuseum.org> >> >> >> Cc: "talk@lists.collectionspace.org" >> >> <talk@lists.collectionspace.org> >> >> >> Subject: Re: [Talk] CAP 5.5 + CS >> >> >> >> >> >> Hi Charlie, >> >> >> >> >> >> At UC Berkeley, we have a very strong need to connect >> collections >> >> >> management and digital assetmanagement functions in the >> >> way you describe. >> >> >> The Nuxeo DAM has seemed like a good way to go, but we haven't >> >> >> really experimented with it here. What's your experience >> >> been like? >> >> >> Anyway, we'll happily endorsethis too. And if it's >> something that >> >> >> looks like it needs another grant-funded project to do >> >> right, maybe >> >> >> we could get our institutions to partner on something. >> >Just thinking out loud... >> >> >> >> >> >> Thanks, >> >> >> Chris >> >> >> >> >> >> >> >> >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote: >> >> >> >> >> >> >> >> >> >> >> >> Thanks for following up Patrick. I'll rally my friends. >> I wouldn't >> >> >> expect a CollectionSpace tab in Nuxeo CAP anytime soon >> >> either, but it >> >> >> would be pretty powerful to have a single repository >> for the sole >> >> >> purpose of relating documents to collection objects, >> >> exhibitions, etc. >> >> >> >> >> >> Keep up the good work, >> >> >> Charlie >> >> >> >> >> >> From: Patrick Schmitz <pschmitz@berkeley.edu> >> >> >> Date: Wed, 4 Jan 2012 10:33:48 -0800 >> >> >> To: Charles Moad <cmoad@imamuseum.org>, >> >> >> <talk@lists.collectionspace.org> >> >> >> Subject: RE: [Talk] CAP 5.5 + CS >> >> >> >> >> >> Hi Charlie - >> >> >> >> >> >> This is something we would really like to investigate, as >> >> many folks >> >> >> have expressed at least some interest in this. We have >> also been >> >> >> assured by the Nuxeo folks that this should be >> possible. At this >> >> >> point, it is mostly a matter of resources and >> priorities. If the >> >> >> community rallies support for this as an essential >> integration, we >> >> >> should be able to find time in the Phase 3 project to >> >> investigate it. >> >> >> >> >> >> Note that we are otherwise interested in getting the DM >> >> working as a >> >> >> diagnostic and support tool, and to aid with import/export >> >> workflows. >> >> >> As such, there may be some basic investigation (not necessarily >> >> >> including DAM/CSpace coordination) in the near term. >> >> >> >> >> >> I doubt very much that CSpace will appear as a tab in >> the Nuxeo UI >> >> >> any time soon, as this is not ause-case that anyone >> (else) has yet >> >> >> requested. Am not ruling it out, just giving my >> impression of the >> >> >> current project priorities, in response to yourquestion on >> >> a related thread. >> >> >> >> >> >> Thanks for the question - >> >> >> >> >> >> Patrick >> >> >> >> >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> >> >> From: talk-bounces@lists.collectionspace.org >> >> >> [mailto:talk-bounces@lists.collectionspace.org] On Behalf >> >> Of Charlie >> >> >> Moad >> >> >> Sent: Wednesday, January 04, 2012 6:18 AM >> >> >> To: talk@lists.collectionspace.org >> >> >> Subject: [Talk] CAP 5.5 + CS >> >> >> >> >> >> What is the feasibility of setting up a single repository >> >> running the >> >> >> new Nuxeo CAP 5.5 (DM + DAM specifically) and >> >> CollectionSpace 2.0 in >> >> >> a single repository? I would like to be able to relate >> >> documents to >> >> >> works in our collection. Any guidance would be greatly >> appreciated. >> >> >> >> >> >> Thanks, >> >> >> Charlie >> >> >> ________________________________ >> >> >> >> >> >> This email message is for the sole use of the intended >> >> recipient(s) >> >> >> and may contain confidential and privileged information. Any >> >> >> unauthorized review, use, disclosure or distribution is >> >> prohibited. >> >> >> If you are not the intended recipient, please contact >> >> Charlie Moad by >> >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> ________________________________ >> >> >> >> >> >> This email message is for the sole use of the intended >> >> recipient(s) >> >> >> and may contain confidential and privileged information. Any >> >> >> unauthorized review, use, disclosure or distribution is >> >> prohibited. >> >> >> If you are not the intended recipient, please contact >> >> Charlie Moad by >> >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> _______________________________________________ >> >> >> Talk mailing list >> >> >> Talk@lists.collectionspace.org >> >> >> >> >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> >> onspace.org >> >> >> >> >> >> ________________________________ >> >> >> >> >> >> This email message is for the sole use of the intended >> >> recipient(s) >> >> >> and may contain confidential and privileged information. Any >> >> >> unauthorized review, use, disclosure or distribution is >> >> prohibited. >> >> >> If you are not the intended recipient, please contact >> >> Charlie Moad by >> >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> ________________________________ >> >> >> >> >> >> This email message is for the sole use of the intended >> >> recipient(s) >> >> >> and may contain confidential and privileged information. Any >> >> >> unauthorized review, use, disclosure or distribution is >> >> prohibited. >> >> >> If you are not the intended recipient, please contact >> >> Charlie Moad by >> >> >> reply email and destroy all copies of the original message. >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> Talk mailing list >> >> >> Talk@lists.collectionspace.org >> >> >> >> >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> >> onspace.org >> >> >> >> >> > >> >> > ________________________________ >> >> > >> >> > This email message is for the sole use of the intended >> recipient(s) >> >> > and may contain confidential and privileged information. Any >> >> > unauthorized review, use, disclosure or distribution is >> >> prohibited. If >> >> > you are not the intended recipient, please contact >> Charlie Moad by >> >> > reply email and destroy all copies of the original message. >> >> > >> >> > _______________________________________________ >> >> > Talk mailing list >> >> > Talk@lists.collectionspace.org >> >> > >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> o >> >> > nspace.org >> >> > >> >> > >> >> > _______________________________________________ >> >> > Talk mailing list >> >> > Talk@lists.collectionspace.org >> >> > >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> o >> >> > nspace.org >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Talk mailing list >> >> > Talk@lists.collectionspace.org >> >> > >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >> >> o >> >> > nspace.org >> >> > >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c >> >> ollectionspace.org >> >> >> > >> > >> >_______________________________________________ >> >Talk mailing list >> >Talk@lists.collectionspace.org >> >http://lists.collectionspace.org/mailman/listinfo/talk_lists. >> collection >> >spa >> >ce.org >> >> ________________________________ >> >> This email message is for the sole use of the intended >> recipient(s) and may contain confidential and privileged >> information. Any unauthorized review, use, disclosure or >> distribution is prohibited. If you are not the intended >> recipient, please contact Charlie Moad by reply email and >> destroy all copies of the original message. >> > ________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Charlie Moad by reply email and destroy all copies of the original message.
NS
Nate Solas
Tue, Jul 10, 2012 2:12 PM

Just wanted to "bump" this if I could. I'm in the process of getting some
assets moved into Nuxeo DAM and am curious if any progress was made or
research done into the integration of Nuxeo DM/DAM and CSpace? I looked for
a Jira but didn't see one for this issue (but the search seems to ignore
short words like "DAM" so maybe I missed it?).

Anyway, I'm going to put some time in on this in the next couple days and I
don't want to duplicate any work that's been done if anyway has tried in
the meantime. Let me know. Thanks,
Nate

On Fri, Feb 24, 2012 at 3:31 PM, Angela Spinazze ats@atspin.com wrote:

Hi all,

A brief update for you on this Nuxeo DM question.

As Patrick mentioned in an earlier post to this thread (January 4th) "Note
that we are otherwise interested in getting the DM working as a diagnostic
and support tool, and to aid with import/export workflows. As such, there
may be some basic investigation (not necessarily including DAM/CSpace
coordination) in the near term."

Given the level of interest in and the potential positive impact of
getting the DM working as a diagnostic support tool, we will include
investigation into the effort required to do so in the scope of work for
the release 2.3 (scheduled to begin on March 5th).  Based on what we
discover in the research phase, we will determine if/when the work might be
scheduled to take place within the current schedule.

We'll be creating a new Jira for this investigation effort so that
everyone who is interested can keep an eye on our progress.

Cheers,

Angela

On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote:

Hi Charlie,

Patrick, Megan and I will be discussing this work tomorrow afternoon to
determine just what is required and we will follow up on this thread once
we've had a chance to explore this in more detail.

As Richard pointed out, we have our core CollectionSpace development
schedule set through September 2012
http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 and
http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule

We do however, realize how important this functionality is to many
community members. Thanks very much for keeping this conversation alive!

Angela

On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote:

It would help to know if someone could express what would be involved
in this process. It seems like it could be really close if it is just a
matter of exposing the CS doc types in the DM interface. What are the
complicating factors beyond that?

  • Charlie

From: Nate Solas nate.solas@walkerart.org
Date: Tue, 21 Feb 2012 11:52:38 -0600
To: Richard Millet richard.millet@berkeley.edu
Cc: Charles Moad cmoad@imamuseum.org, talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS

I'd like to +1 a raised priority for this, but I'm not entirely sure what
to recommend bumping. For us, and I suspect most of the current
implementers, the multi-tenant service isn't as big an issue, but I know
it's core to the long-term sustainability of the software.

It seems like there might be some room for this work in the 2.3 roadmap?
I don't know how big a chunk the Location and Movement rewrite is.

Thanks for considering it. This would be huge for us, and it sounds like
there is a lot of support out there.
Nate

On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet <
richard.millet@berkeley.edu> wrote:

Charlie,****


Thanks for experimenting with this.  One of our known tasks is to ensure
that CollectionSpace can co-exist with Nuxeo’s DM and DAM applications.
Unfortunately, this work is not currently scheduled to happen anytime
soon.  However, we understand the value of CollectionSpace being able to
co-exist with Nuxeo’s applications.  If you feel we need to make this work
a higher priority, please review the current release roadmaps and see how
this work compares to what we have planned.  If you decide this work is
more important, let us know and we can try to raise its priority.****


-Richard****



From: talk-bounces@lists.collectionspace.org [mailto:
talk-bounces@lists.collectionspace.org] *On Behalf Of *Charlie Moad
Sent: Thursday, February 16, 2012 7:14 PM
To: Christopher Pott; Chris Hoffman
Cc: talk@lists.collectionspace.org

Subject: Re: [Talk] CAP 5.5 + CS****


I haven't had much time, but I took a naïve attempt at installing
CS+DM+DAM all on the same postgres database. I am attaching two screenshots
of the results. There are only a few errors during the DM+DAM startup, but
things seem to run well enough. There appears to be promise. Two glaring
things are that the "default-domain" that is normally part of the top-level
of DM is missing. Looking inside each CS domain shows a workspace for each
type, but they are empty. I would hope that it is only a matter of adding
the proper Nuxeo extensions to expose these types to the DM interface. Any
insight the development team has would be interesting. In the mean time I
believe we are going to relate our DM documents to placeholders documents.
The prospect of creating relationship between DM documents and CS ones
feels close though.****


  • Charlie****

*From: *Christopher Pott Christopher.Pott@smk.dk
*Date: *Wed, 11 Jan 2012 14:35:34 +0100
*To: *Charles Moad cmoad@imamuseum.org, Chris Hoffman <
chris.hoffman@berkeley.edu>
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] CAP 5.5 + CS


Hi Charlie,****


Here at SMK we’re also in the process of defining our requirements for a
DAM solution and as a part of this process have also tested an earlier
Nuxeo DAM version. It was basic, but seemed fast and stable in the short
period we tested it. Relating texts and documents to artworks is also a
pressing use case for us – although Ihope we can integrate this into
CollectionSpace either through the Media Handling procedure by supporting
some new document types (pdf, doc, html etc.) or possibly even by creating
a new procedure for handling related texts. In any case I look forward to
following your investigations. ****


Regards,****
(another) Chris ****



Fra: talk-bounces@lists.collectionspace.org [
mailto:talk-bounces@lists.collectionspace.orgtalk-bounces@lists.collectionspace.org]
På vegne af Charlie Moad
Sendt: 4. januar 2012 22:48
Til: Chris Hoffman
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] CAP 5.5 + CS
**


At the IMA we are just in the process of rolling out the new DAM
software based on 5.5. We have been using DM with a select group of staff
members for several months now with decent success. We found the previous
versions of DAM lacking some very basic needs and many of those have been
addressed in the latest release. We even paid for the development of some
of those enhancements. In general Nuxeo DAM is fairly simple, but that's
all that we (and I suspect many museums) need. We need it to be able to
handle and preview media files and relate them to our institution. I'm not
entirely sure what the effort would be and if much additional work would be
required. That's why I reached out. I'll continue to investigate this and
come back with progress I might have.****


  • Charlie****

*From: *Chris Hoffman chris.hoffman@berkeley.edu
*Date: *Wed, 4 Jan 2012 13:39:36 -0800
*To: *Charles Moad cmoad@imamuseum.org
Cc: "talk@lists.collectionspace.org" talk@lists.collectionspace.org
Subject: Re: [Talk] CAP 5.5 + CS


Hi Charlie,****


At UC Berkeley, we have a very strong need to connect collections
management and digital assetmanagement functions in the way you describe.
The Nuxeo DAM has seemed like a good way to go, but we haven't really
experimented with it here.  What's your experience been like?  Anyway,
we'll happily endorsethis too.  And if it's something that looks like it
needs another grant-funded project to do right, maybe we could get our
institutions to partner on something.  Just thinking out loud...****


Thanks,****
Chris****



On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:****


Thanks for following up Patrick. I'll rally my friends. I wouldn't
expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but it would
be pretty powerful to have a single repository for the sole purpose of
relating documents to collection objects, exhibitions, etc.****


Keep up the good work,****
Charlie****
****
*From: *Patrick Schmitz pschmitz@berkeley.edu
*Date: *Wed, 4 Jan 2012 10:33:48 -0800
*To: *Charles Moad cmoad@imamuseum.org, <talk@lists.collectionspace.org

Subject: RE: [Talk] CAP 5.5 + CS**


Hi Charlie - ****


This is something we would really like to investigate, as many folks have
expressed at least some interest in this. We have also been assured by the
Nuxeo folks that this should be possible. At this point, it is mostly a
matter of resources and priorities. If the community rallies support for
this as an essential integration, we should be able to find time in the
Phase 3 project to investigate it. ****


Note that we are otherwise interested in getting the DM working as a
diagnostic and support tool, and to aid with import/export workflows. As
such, there may be some basic investigation (not necessarily including
DAM/CSpace coordination) in the near term.****


I doubt very much that CSpace will appear as a tab in the Nuxeo UI any
time soon, as this is not ause-case that anyone (else) has yet requested.
Am not ruling it out, just giving my impression of the current project
priorities, in response to yourquestion on a related thread. ****


Thanks for the question - ****


Patrick****



From: talk-bounces@lists.collectionspace.org [
mailto:talk-bounces@lists.collectionspace.orgtalk-bounces@lists.collectionspace.org]
On Behalf Of Charlie Moad
Sent: Wednesday, January 04, 2012 6:18 AM
To: talk@lists.collectionspace.org
Subject: [Talk] CAP 5.5 + CS
**
What is the feasibility of setting up a single repository running the
new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace 2.0 in a
single repository? I would like to be able to relate documents to works in
our collection. Any guidance would be greatly appreciated.****


Thanks,****
Charlie****

This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message. ****

This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message. ****


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org




This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message. ****

This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and destroy
all copies of the original message. ****


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact Charlie Moad by reply email and
destroy all copies of the original message.


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Just wanted to "bump" this if I could. I'm in the process of getting some assets moved into Nuxeo DAM and am curious if any progress was made or research done into the integration of Nuxeo DM/DAM and CSpace? I looked for a Jira but didn't see one for this issue (but the search seems to ignore short words like "DAM" so maybe I missed it?). Anyway, I'm going to put some time in on this in the next couple days and I don't want to duplicate any work that's been done if anyway has tried in the meantime. Let me know. Thanks, Nate On Fri, Feb 24, 2012 at 3:31 PM, Angela Spinazze <ats@atspin.com> wrote: > Hi all, > > A brief update for you on this Nuxeo DM question. > > As Patrick mentioned in an earlier post to this thread (January 4th) "Note > that we are otherwise interested in getting the DM working as a diagnostic > and support tool, and to aid with import/export workflows. As such, there > may be some basic investigation (not necessarily including DAM/CSpace > coordination) in the near term." > > Given the level of interest in and the potential positive impact of > getting the DM working as a diagnostic support tool, we will include > investigation into the effort required to do so in the scope of work for > the release 2.3 (scheduled to begin on March 5th). Based on what we > discover in the research phase, we will determine if/when the work might be > scheduled to take place within the current schedule. > > We'll be creating a new Jira for this investigation effort so that > everyone who is interested can keep an eye on our progress. > > Cheers, > > Angela > > > On Feb 22, 2012, at 10:47 AM, Angela Spinazze wrote: > > Hi Charlie, > > Patrick, Megan and I will be discussing this work tomorrow afternoon to > determine just what is required and we will follow up on this thread once > we've had a chance to explore this in more detail. > > As Richard pointed out, we have our core CollectionSpace development > schedule set through September 2012 > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0 and > http://wiki.collectionspace.org/display/collectionspace/Roadmap+to+3.0+Proposed+Schedule > > We do however, realize how important this functionality is to many > community members. Thanks very much for keeping this conversation alive! > > Angela > > > On Feb 21, 2012, at 11:58 AM, Charlie Moad wrote: > > It would help to know if someone could express what would be involved > in this process. It seems like it could be really close if it is just a > matter of exposing the CS doc types in the DM interface. What are the > complicating factors beyond that? > > - Charlie > > From: Nate Solas <nate.solas@walkerart.org> > Date: Tue, 21 Feb 2012 11:52:38 -0600 > To: Richard Millet <richard.millet@berkeley.edu> > Cc: Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org> > Subject: Re: [Talk] CAP 5.5 + CS > > I'd like to +1 a raised priority for this, but I'm not entirely sure what > to recommend bumping. For us, and I suspect most of the current > implementers, the multi-tenant service isn't as big an issue, but I know > it's core to the long-term sustainability of the software. > > It seems like there might be some room for this work in the 2.3 roadmap? > I don't know how big a chunk the Location and Movement rewrite is. > > Thanks for considering it. This would be huge for us, and it sounds like > there is a lot of support out there. > Nate > > > On Fri, Feb 17, 2012 at 12:22 PM, Richard Millet < > richard.millet@berkeley.edu> wrote: > >> Charlie,**** >> ** ** >> Thanks for experimenting with this. One of our known tasks is to ensure >> that CollectionSpace can co-exist with Nuxeo’s DM and DAM applications. >> Unfortunately, this work is not currently scheduled to happen anytime >> soon. However, we understand the value of CollectionSpace being able to >> co-exist with Nuxeo’s applications. If you feel we need to make this work >> a higher priority, please review the current release roadmaps and see how >> this work compares to what we have planned. If you decide this work is >> more important, let us know and we can try to raise its priority.**** >> ** ** >> -Richard**** >> ** ** >> ** ** >> *From:* talk-bounces@lists.collectionspace.org [mailto: >> talk-bounces@lists.collectionspace.org] *On Behalf Of *Charlie Moad >> *Sent:* Thursday, February 16, 2012 7:14 PM >> *To:* Christopher Pott; Chris Hoffman >> *Cc:* talk@lists.collectionspace.org >> >> *Subject:* Re: [Talk] CAP 5.5 + CS**** >> >> ** ** >> I haven't had much time, but I took a naïve attempt at installing >> CS+DM+DAM all on the same postgres database. I am attaching two screenshots >> of the results. There are only a few errors during the DM+DAM startup, but >> things seem to run well enough. There appears to be promise. Two glaring >> things are that the "default-domain" that is normally part of the top-level >> of DM is missing. Looking inside each CS domain shows a workspace for each >> type, but they are empty. I would hope that it is only a matter of adding >> the proper Nuxeo extensions to expose these types to the DM interface. Any >> insight the development team has would be interesting. In the mean time I >> believe we are going to relate our DM documents to placeholders documents. >> The prospect of creating relationship between DM documents and CS ones >> feels close though.**** >> ** ** >> - Charlie**** >> ** ** >> *From: *Christopher Pott <Christopher.Pott@smk.dk> >> *Date: *Wed, 11 Jan 2012 14:35:34 +0100 >> *To: *Charles Moad <cmoad@imamuseum.org>, Chris Hoffman < >> chris.hoffman@berkeley.edu> >> *Cc: *<talk@lists.collectionspace.org> >> *Subject: *SV: [Talk] CAP 5.5 + CS**** >> ** ** >> Hi Charlie,**** >> **** >> Here at SMK we’re also in the process of defining our requirements for a >> DAM solution and as a part of this process have also tested an earlier >> Nuxeo DAM version. It was basic, but seemed fast and stable in the short >> period we tested it. Relating texts and documents to artworks is also a >> pressing use case for us – although Ihope we can integrate this into >> CollectionSpace either through the Media Handling procedure by supporting >> some new document types (pdf, doc, html etc.) or possibly even by creating >> a new procedure for handling related texts. In any case I look forward to >> following your investigations. **** >> **** >> Regards,**** >> (another) Chris **** >> **** >> ------------------------------ >> *Fra:* talk-bounces@lists.collectionspace.org [ >> mailto:talk-bounces@lists.collectionspace.org<talk-bounces@lists.collectionspace.org>] >> *På vegne af *Charlie Moad >> *Sendt:* 4. januar 2012 22:48 >> *Til:* Chris Hoffman >> *Cc:* talk@lists.collectionspace.org >> *Emne:* Re: [Talk] CAP 5.5 + CS**** >> **** >> At the IMA we are just in the process of rolling out the new DAM >> software based on 5.5. We have been using DM with a select group of staff >> members for several months now with decent success. We found the previous >> versions of DAM lacking some very basic needs and many of those have been >> addressed in the latest release. We even paid for the development of some >> of those enhancements. In general Nuxeo DAM is fairly simple, but that's >> all that we (and I suspect many museums) need. We need it to be able to >> handle and preview media files and relate them to our institution. I'm not >> entirely sure what the effort would be and if much additional work would be >> required. That's why I reached out. I'll continue to investigate this and >> come back with progress I might have.**** >> **** >> - Charlie**** >> **** >> *From: *Chris Hoffman <chris.hoffman@berkeley.edu> >> *Date: *Wed, 4 Jan 2012 13:39:36 -0800 >> *To: *Charles Moad <cmoad@imamuseum.org> >> *Cc: *"talk@lists.collectionspace.org" <talk@lists.collectionspace.org> >> *Subject: *Re: [Talk] CAP 5.5 + CS**** >> **** >> Hi Charlie,**** >> **** >> At UC Berkeley, we have a very strong need to connect collections >> management and digital assetmanagement functions in the way you describe. >> The Nuxeo DAM has seemed like a good way to go, but we haven't really >> experimented with it here. What's your experience been like? Anyway, >> we'll happily endorsethis too. And if it's something that looks like it >> needs another grant-funded project to do right, maybe we could get our >> institutions to partner on something. Just thinking out loud...**** >> **** >> Thanks,**** >> Chris**** >> **** >> **** >> On Jan 4, 2012, at 12:38 PM, Charlie Moad wrote:**** >> >> ** ** >> Thanks for following up Patrick. I'll rally my friends. I wouldn't >> expect a CollectionSpace tab in Nuxeo CAP anytime soon either, but it would >> be pretty powerful to have a single repository for the sole purpose of >> relating documents to collection objects, exhibitions, etc.**** >> **** >> Keep up the good work,**** >> Charlie**** >> **** >> *From: *Patrick Schmitz <pschmitz@berkeley.edu> >> *Date: *Wed, 4 Jan 2012 10:33:48 -0800 >> *To: *Charles Moad <cmoad@imamuseum.org>, <talk@lists.collectionspace.org >> > >> *Subject: *RE: [Talk] CAP 5.5 + CS**** >> **** >> Hi Charlie - **** >> **** >> This is something we would really like to investigate, as many folks have >> expressed at least some interest in this. We have also been assured by the >> Nuxeo folks that this should be possible. At this point, it is mostly a >> matter of resources and priorities. If the community rallies support for >> this as an essential integration, we should be able to find time in the >> Phase 3 project to investigate it. **** >> **** >> Note that we are otherwise interested in getting the DM working as a >> diagnostic and support tool, and to aid with import/export workflows. As >> such, there may be some basic investigation (not necessarily including >> DAM/CSpace coordination) in the near term.**** >> **** >> I doubt very much that CSpace will appear as a tab in the Nuxeo UI any >> time soon, as this is not ause-case that anyone (else) has yet requested. >> Am not ruling it out, just giving my impression of the current project >> priorities, in response to yourquestion on a related thread. **** >> **** >> Thanks for the question - **** >> **** >> Patrick**** >> >> ** ** >> ------------------------------ >> >> *From:* talk-bounces@lists.collectionspace.org [ >> mailto:talk-bounces@lists.collectionspace.org<talk-bounces@lists.collectionspace.org>] >> *On Behalf Of *Charlie Moad >> *Sent:* Wednesday, January 04, 2012 6:18 AM >> *To:* talk@lists.collectionspace.org >> *Subject:* [Talk] CAP 5.5 + CS**** >> What is the feasibility of setting up a single repository running the >> new Nuxeo CAP 5.5 (DM + DAM specifically) and CollectionSpace 2.0 in a >> single repository? I would like to be able to relate documents to works in >> our collection. Any guidance would be greatly appreciated.**** >> **** >> Thanks,**** >> Charlie**** >> ------------------------------ >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. **** >> ------------------------------ >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. **** >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> **** >> **** >> ------------------------------ >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. **** >> ------------------------------ >> This email message is for the sole use of the intended recipient(s) and >> may contain confidential and privileged information. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not the >> intended recipient, please contact Charlie Moad by reply email and destroy >> all copies of the original message. **** >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > ------------------------------ > This email message is for the sole use of the intended recipient(s) and > may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact *Charlie Moad* by reply email and > destroy all copies of the original message. > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >