[Using Sakai] External statistics reports

[Steve Swinsburg]

Hi Greg,

Nakamura is the backend for Sakai OAE, it's not related to Sakai CLE.

The URLs you listed are internal tool page URLs, they are not designed for being requested externally. Entity broker is a way to request data like the web services, and perhaps John's script might be better suited there, but it news to be specifically coded.

If you want to run arbitrary SQL queries against the DB, you should understand the risks before opening that up as a web service. My recommendation is that you use a tool to create these reports. You could just use an SQL query browser to do this. An admin tool to run SQL within Sakai would be neat though.

Cheers,
Steve

Sent from my iPad

On 22/08/2012, at 3:43, Gregory Guthrie <guthrie at mum.edu> wrote:

> John, Thanks for the information, I'll have to ponder a bit on it and how I could use it for my goal.
> What is the advantage of this over just using something like JDBC/ODBC queries from Python (or any program)?
> 
> Two other possibilities that I saw in browsing was something called Nakamura, which seems to provide some additional access to internal services, but seemed pretty involved and complicated to me, and not any obvious examples for the simple type of thing that I wanted to do. (Seems like it runs as a separate server?)
> 
> Another that seemed more interesting was to just curl to various services, and I see more examples of that for admin like functions. 
> It seemed to me as a naïve outsider that if there was some internal service which was what gets invoked for generating reports and exporting, that one could curl to invoke it, basically emulating GUI button pushes. Is there any semblance of reality in this?
> 
> It does seem that one has to go to the reports page first, and then request a specific report, and then export it once internally generated.
> (From playing with the URLs).
> 
> sakai statistics reports.. (URLs from GUI)
>   http://sakai.local/portal/site/5df2f-79e7-4514-b41d-388b/page/2758-e604-4621-b451-b0fa9f986f
> 
> -- seems to be stateful, must drill-down to have statistics computed before going to reports.
> Reports:
>    http://sakai. local /portal/tool/68f5-19bb-4269-8546-92a6e/?wicket:bookmarkablePage=:org.sakaiproject.sitestats.tool.wicket.pages.ReportsPage&siteId=5df2f-79e7-4514-b41d-388b
> 
> Student Visits report:   (Nope!)
>    http://sakai. local /portal/tool/68f5-19bb-4269-8546-92a6e /?wicket:interface=:4:reportsForm:myReportsContainer:myReports:2:reportRow:link::ILinkListener::
> 
> Export -> Export XLS  ???
> -------------------------------------------
>> -----Original Message-----
>> From: John Bush [mailto:john.bush at rsmart.com]
>> Subject: Re: [Using Sakai] External statistics reports
>> 
>> Here is the way I'm addressing this right now.  I've written a soap webservice, that returns
>> soap for a POST call and raw content for a GET call.  The reason for this is complicated I can
>> explain if you really care.
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> 
> TO UNSUBSCRIBE: send email to sakai-user-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"