________________________________ From: Brian Harrington <brian.harrington@lyrasis.org> Sent: Friday, January 15, 2016 11:02 AM To: Talk Subject: Reports Issue Hi All, I'm having an issue with activating reports, and was wondering if anybody else might have some clues. Basically, reports with a "normal" docType like <forDocType>Acquisition</forDocType> activate just fine and show up in the pulldown. But reports with an "extended" docType, like <forDocType>CollectionObjectTenant101</forDocType> don't. I've verified that CollectionObjectTenant101 is the primaryType in the hierarchy table, so I'm at a bit of a loss as to what could be going wrong. Interestingly, I get the same error message, "2016-01-14 22:52:11,176 WARN [http-bio-8180-exec-21] [org.collectionspace.services.nuxeo.client.java.RemoteDocumentModelHandlerI mpl:143] Call failed to getRefnameDisplayName() for class org.collectionspace.services.report.nuxeo.ReportDocumentModelHandler", whether the report activates (with Acquisition) or doesn't (with CollectionObjectTenant101). Thanks, Brian -- Brian Harrington Repository Software Developer LYRASIS brian.harrington@lyrasis.org skype: abbistani

Hi Brian, I don’t think we have ever set the document type as something tenant-specific. That is, I think we always use > <forDocType>CollectionObject</forDocType> for reports that should show up on the cataloging screen. However, maybe you have things set up differently there. Thanks, Chris UC Berkeley > On Jan 15, 2016, at 8:11 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > > > From: Brian Harrington <brian.harrington@lyrasis.org <mailto:brian.harrington@lyrasis.org>> > Sent: Friday, January 15, 2016 11:02 AM > To: Talk > Subject: Reports Issue > > Hi All, > > I'm having an issue with activating reports, and was wondering if anybody > else might have some clues. Basically, reports with a "normal" docType > like <forDocType>Acquisition</forDocType> activate just fine and show up > in the pulldown. But reports with an "extended" docType, like > <forDocType>CollectionObjectTenant101</forDocType> don't. I've verified > that CollectionObjectTenant101 is the primaryType in the hierarchy table, > so I'm at a bit of a loss as to what could be going wrong. > > Interestingly, I get the same error message, "2016-01-14 22:52:11,176 WARN > [http-bio-8180-exec-21] > [org.collectionspace.services.nuxeo.client.java.RemoteDocumentModelHandlerI > mpl:143] Call failed to getRefnameDisplayName() for class > org.collectionspace.services.report.nuxeo.ReportDocumentModelHandler", > whether the report activates (with Acquisition) or doesn't (with > CollectionObjectTenant101). > > Thanks, > > Brian > > -- > Brian Harrington > Repository Software Developer > LYRASIS > brian.harrington@lyrasis.org <mailto:brian.harrington@lyrasis.org> > skype: abbistani > > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org>

Thanks Chris. That did the trick. It does leave me wondering about the 'Documents and "forDocType" values' section on https://wiki.collectionspace.org/display/DOC/How+to+add+and+run+reports however. Is the note about extended schemas still valid? Brian From: Talk <talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>> on behalf of Chris Hoffman <chris_h@berkeley.edu<mailto:chris_h@berkeley.edu>> Date: Monday, January 18, 2016 at 8:00 PM To: Megan Forbes <megan.forbes@lyrasis.org<mailto:megan.forbes@lyrasis.org>> Cc: CollectionSpace Talk List <talk@lists.collectionspace.org<mailto:talk@lists.collectionspace.org>> Subject: Re: [Talk] Reports Issue Hi Brian, I don't think we have ever set the document type as something tenant-specific. That is, I think we always use <forDocType>CollectionObject</forDocType> for reports that should show up on the cataloging screen. However, maybe you have things set up differently there. Thanks, Chris UC Berkeley On Jan 15, 2016, at 8:11 AM, Megan Forbes <megan.forbes@lyrasis.org<mailto:megan.forbes@lyrasis.org>> wrote: ________________________________ From: Brian Harrington <brian.harrington@lyrasis.org<mailto:brian.harrington@lyrasis.org>> Sent: Friday, January 15, 2016 11:02 AM To: Talk Subject: Reports Issue Hi All, I'm having an issue with activating reports, and was wondering if anybody else might have some clues. Basically, reports with a "normal" docType like <forDocType>Acquisition</forDocType> activate just fine and show up in the pulldown. But reports with an "extended" docType, like <forDocType>CollectionObjectTenant101</forDocType> don't. I've verified that CollectionObjectTenant101 is the primaryType in the hierarchy table, so I'm at a bit of a loss as to what could be going wrong. Interestingly, I get the same error message, "2016-01-14 22:52:11,176 WARN [http-bio-8180-exec-21] [org.collectionspace.services.nuxeo.client.java.RemoteDocumentModelHandlerI mpl:143] Call failed to getRefnameDisplayName() for class org.collectionspace.services.report.nuxeo.ReportDocumentModelHandler", whether the report activates (with Acquisition) or doesn't (with CollectionObjectTenant101). Thanks, Brian -- Brian Harrington Repository Software Developer LYRASIS brian.harrington@lyrasis.org<mailto:brian.harrington@lyrasis.org> skype: abbistani _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Brian, Ah, I think that note > Be careful when creating a report for a procedure with an extended schema. The forDocType value must correspond to the procedural document name, which generally follows the pattern acquisitionTenant## or CollectionObjectTenant## (where ## represents a tenant ID like '1' or '17’) is an artifact of old documentation. I think at one point we maybe had to do that, but it’s no longer the case (as noted by the note above the note “This paragraph needs to be cleaned up”.) I think there is a plan to clean up the reporting documentation. Chris > On Jan 19, 2016, at 7:02 AM, Brian Harrington <brian.harrington@lyrasis.org> wrote: > > Thanks Chris. That did the trick. It does leave me wondering about the 'Documents and "forDocType” values’ section on https://wiki.collectionspace.org/display/DOC/How+to+add+and+run+reports <https://wiki.collectionspace.org/display/DOC/How+to+add+and+run+reports> however. Is the note about extended schemas still valid? > > Brian > > > From: Talk <talk-bounces@lists.collectionspace.org <mailto:talk-bounces@lists.collectionspace.org>> on behalf of Chris Hoffman <chris_h@berkeley.edu <mailto:chris_h@berkeley.edu>> > Date: Monday, January 18, 2016 at 8:00 PM > To: Megan Forbes <megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>> > Cc: CollectionSpace Talk List <talk@lists.collectionspace.org <mailto:talk@lists.collectionspace.org>> > Subject: Re: [Talk] Reports Issue > > Hi Brian, > > I don’t think we have ever set the document type as something tenant-specific. That is, I think we always use >> <forDocType>CollectionObject</forDocType> > > for reports that should show up on the cataloging screen. However, maybe you have things set up differently there. > > Thanks, > Chris > UC Berkeley > >> On Jan 15, 2016, at 8:11 AM, Megan Forbes <megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>> wrote: >> >> >> From: Brian Harrington <brian.harrington@lyrasis.org <mailto:brian.harrington@lyrasis.org>> >> Sent: Friday, January 15, 2016 11:02 AM >> To: Talk >> Subject: Reports Issue >> >> Hi All, >> >> I'm having an issue with activating reports, and was wondering if anybody >> else might have some clues. Basically, reports with a "normal" docType >> like <forDocType>Acquisition</forDocType> activate just fine and show up >> in the pulldown. But reports with an "extended" docType, like >> <forDocType>CollectionObjectTenant101</forDocType> don't. I've verified >> that CollectionObjectTenant101 is the primaryType in the hierarchy table, >> so I'm at a bit of a loss as to what could be going wrong. >> >> Interestingly, I get the same error message, "2016-01-14 22:52:11,176 WARN >> [http-bio-8180-exec-21] >> [org.collectionspace.services.nuxeo.client.java.RemoteDocumentModelHandlerI >> mpl:143] Call failed to getRefnameDisplayName() for class >> org.collectionspace.services.report.nuxeo.ReportDocumentModelHandler", >> whether the report activates (with Acquisition) or doesn't (with >> CollectionObjectTenant101). >> >> Thanks, >> >> Brian >> >> -- >> Brian Harrington >> Repository Software Developer >> LYRASIS >> brian.harrington@lyrasis.org <mailto:brian.harrington@lyrasis.org> >> skype: abbistani >> >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> >> http://lists.collectionspace.org/mailman/listinfo/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