Nate, Here is a related JIRA task: http://issues.collectionspace.org/browse/CSPACE-4790 We’ve done no work on this so far. I’ll let Angela (et al) respond to the corresponding project priority issues around this task. -Richard From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Nate Solas Sent: Tuesday, July 10, 2012 7:13 AM To: Angela Spinazze Cc: CollectionSpace Talk List Subject: Re: [Talk] CAP 5.5 + CS 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+Propo sed+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

Hi Nate, An update for you on where the Nuxeo DM console and Nuxeo DAM module stand in terms of CSpace priorities moving forward. We did discuss the DM console issue yesterday during a Steering Committee call as part of a larger conversation that we are having about development priorities for bringing CollectionSpace 'to market' (the productization of the application so to speak). As part of our sustainability planning work, we are gathering a set of development activities that are currently not on the schedule and that are essential for moving the application from project to product. As you can see from Jira 4790, this is a set of tasks around the documentation and integration of the Nuxeo DM console only. The same tasks for the Nuxeo DAM module have not been codified into a Jira yet. Based on our conversation yesterday, the investigation and documentation of what it would take to re-integrate the Nuxeo DM console and deliver it as part of the CSpace stack is a higher priority than getting the DAM module integrated. I would expect that the DM console investigation work to happen before the end of 2012 (probably 4th quarter) with development work to be scheduled after that (probably not before 1st quarter 2013). With regard to the Nuxeo DAM module, it is very helpful to hear that this is still of interest to Walker. As Richard pointed out, we have not done any work to investigate what it means to integrate the DAM module with CSpace. Once we understand the amount of effort involved, we will be in a better position to consider scheduling that work, however, the investigation is not slated to happen this year given our current slate of deliverables. Please let us know what you learn in your investigations, and any thoughts you have about the probability of its use at Walker. Your investigations and continued interest - along with that of SMK, IMA Lab, and others - means that it will stay on the list of possible work for 2013. Cheers, Angela On Jul 10, 2012, at 2:09 PM, Richard Millet wrote: > Nate, > > Here is a related JIRA task: http://issues.collectionspace.org/browse/CSPACE-4790 > > We’ve done no work on this so far. I’ll let Angela (et al) respond to the corresponding project priority issues around this task. > > -Richard > > From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Nate Solas > Sent: Tuesday, July 10, 2012 7:13 AM > To: Angela Spinazze > Cc: CollectionSpace Talk List > Subject: Re: [Talk] CAP 5.5 + CS > > 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 2012http://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 >