1. Re: Default report installation (John B Lowe)
2.

Hi ​Mahendra, If you need to add cspace as a sudoer, try this - http://askubuntu.com/questions/7477/how-can-i-add-a-new-user-as-sudoer-using-the-command-line -Yousuf On Wed, Jul 13, 2016 at 9:00 AM, <talk-request@lists.collectionspace.org> wrote: > Send Talk mailing list submissions to > talk@lists.collectionspace.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > or, via email, send a message with subject or body 'help' to > talk-request@lists.collectionspace.org > > You can reach the person managing the list at > talk-owner@lists.collectionspace.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk digest..." > > > Today's Topics: > > 1. Re: Default report installation (John B Lowe) > 2. > ​​ > CollectionSpace installation Issue > (mahendra.pratap@inficaretech.com) > 3. Bugs filed during v4.4 QA (Megan Forbes) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Jul 2016 14:13:22 -0700 > From: John B Lowe <jblowe@berkeley.edu> > To: Aron Roberts <aron@socrates.berkeley.edu> > Cc: Dave Ross <dross@rossmail.us>, CollectionSpace Talk List > <talk@lists.collectionspace.org> > Subject: Re: [Talk] Default report installation > Message-ID: > <CADzezfJ3FK3=AVdicYLQ7DBo_WMy6hiiK1b93nwTOyrc= > ce_3Q@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Dave, > > You can try a *different* set of scripts to maintain reports: > > https://github.com/cspace-deployment/Tools/tree/master/reports/helpers > > I just made a pass at this suite to update documentation and code > details... the scripts *may* actually work as documented! > > NB: this suite ONLY maintains the "report records" in CSpace -- you have to > copy the report files (".jrxml files") to the correct server directory > yourself. > > Good hunting, let me know if you have any success (or failure) with these > tools. > > John > > On Mon, Jul 11, 2016 at 3:37 PM, Aron Roberts <aron@socrates.berkeley.edu> > wrote: > > > Hi Dave, > > > > Riffing on John's response, it appears this script defaults to installing > > reports on a CollectionSpace server on localhost: > > > > > > > https://github.com/collectionspace/Tools/blob/d9fd6bc8bc26ed6cb4e8e6d222ecca7e54d5d5cd/scripts/create-report-records.sh#L88 > > > > If you're running the script over the network, against a non-local, > > production CollectionSpace server, you'd replace 'localhost' with the > > hostname or IP address of that server. > > > > If this is not the issue, two other things you might try, right off: > > > > - Verifying that the report records are present via a Services REST API > > call. You can do this most simply in your browser, by first logging in as > > an admin user in the appropriate tenant in your production instance, and > > then visiting this URL (substituting your hostname and port as > appropriate): > > > > http://yourhost:yourport/cspace-services/reports > > > > - Ensuring that you're visiting the appropriate record type(s), in the > > relevant tenant, in the CollectionSpace UI, to be able to view available > > reports in the Run Report dropdown menu. (Visiting the Acquisition record > > in the 'core' tenant might be a good place to start, as that record has > > three different types of reports associated with it.) > > > > Aron > > > > On Mon, Jul 11, 2016 at 2:10 PM, John B Lowe <jblowe@berkeley.edu> > wrote: > > > >> Dave, > >> > >> I had just a quick look at the scripts you mentioned. If I read them > >> correctly, they will only install report on servers with hostnames like > >> "<xxx>.collectionspace.org", which I doubt is the case for your servers > >> (even, I suspect, for what you call the "core.collectionspace.org > >> deployment", since that hostname is not really available to you.) > >> > >> If I'm right, you'll need to edit the scripts to get them to work... > >> > >> I also have a feeling that when you are running the scripts on the "the > >> core.collectionspace.com [sic] instance" -- probably the scripts are > >> referencing the actually server, which you may not be able to modify... > >> > >> Good hunting, > >> > >> John > >> > >> On Sun, Jul 10, 2016 at 7:56 PM, Dave Ross <dross@rossmail.us> wrote: > >> > >>> Hi All, > >>> > >>> I?ve tried creating the ?canned? reports available in the Tools repo > and > >>> we?re not able to get those reports to appear either locally, on our > >>> production environment, or the core.collectionspace.org deployment. > In > >>> each case the "./scripts/install_report_records.sh? appears to execute > >>> without problems but no reports are available afterwards. This is > still > >>> the case for the core.collectionspace.com instance- they have been run > >>> there and when an attempt to rerun the script is made a series of > outputs > >>> result like this: > >>> WARNING: Found an existing 'Loan Out Report' report record in the > 'core' > >>> tenant. No new record created. > >>> Checking for an Object Exit Report report record in the 'core' tenant > ... > >>> > >>> However when I log into the application no reports are available. > >>> > >>> If anyone has been able to get the ?canned? reports to work I?d really > >>> appreciate the steps that they took to get a good result. > >>> > >>> Thank you, > >>> -Dave Ross > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> > >> > > >