Where to find Sushi-Lite URL?

How we can find Sushi-Lite URL? At the moment use latest, OJS 3.1.2.1 version. Sushi-Lite plugin is enabled.
Thanks.

Hi @Lazar_Stosic,

I am not using the plugin, but maybe the read.me for the plugin can help: https://github.com/ulsdevteam/ojs-sushiLite-plugin

Please see the usage chapter.

Regards, Primož

1 Like

Thanks but there is not concrete instruction where to find it. This is question for Clinton Graham. He will know that.

An OJS URL is formed of the “base url” + optional “context path” + the page handler and arguments.

The SUSHI-Lite endpoint in the current release is at the page handler level, with the form: “/sushiLite/v1_7/”.

If your OJS installation is hosted at http://myjournal.com/ with mod_rewrite masking the context path, the SUSHI-Lite handlers will be under http://myjournal.com/sushiLite/v1_7/.

If you are not using mod_rewrite with RESTful URLs, the URLs will look more like those mentioned in the readme:

/ojs/index.php/index/sushiLite/v1_7/GetReport?Report=AR1
/ojs/index.php/myJournal/sushiLite/v1_7/GetReport?Report=JR1&Release=4.1&BeginDate=2015-01-01&EndDate=2015-12-31

where /ojs/ is part of the “base url”.

Thanx @ctgraham,

For command (ojs was replaced with domain of journal)

/ojs/index.php/myJournal/sushiLite/v1_7/GetReport?Report=JR1&Release=4.1&BeginDate=2015-01-01&EndDate=2015-12-31

I received>

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<sc:ReportResponse xmlns:sc=“http://www.niso.org/schemas/sushi/counter” xmlns:s=“http://www.niso.org/schemas/sushi” xmlns:c=“http://www.niso.org/schemas/counter” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation="http://www.niso.org/schemas/sushi http://www.niso.org/schemas/sushi/sushi1_7.xsd http://www.niso.org/schemas/sushi/counter http://www.niso.org/schemas/sushi/sushi_counter4_1.xsd ">

<s:Exception Created=“2019-11-07T09:04:48+01:00”>

<s:Number>3030</s:Number>

<s:Severity>Error</s:Severity>

<s:Message>

No usage available for requested dates. An internal error has occurred.

</s:Message>

<s:Data>##plugins.reports.counter.exception.noData##</s:Data>

</s:Exception>

<s:Requestor>

<s:ID>anonymous</s:ID>

<s:Name/>

<s:Email/>

</s:Requestor>

<s:CustomerReference>

<s:ID/>

</s:CustomerReference>

<s:ReportDefinition Name=“JR1” Release=“4.1”>

<s:Filters>

<s:UsageDateRange>

<s:Begin>2015-01-01</s:Begin>

<s:End>2015-12-31</s:End>

</s:UsageDateRange>

</s:Filters>

</s:ReportDefinition>

</sc:ReportResponse>

Where is the problem?

Did you also replace “myJournal” with your journal’s path (or the site context of “index”)?

The error message indicates that there are no metrics of type “ojs::counter” in your metrics database table for the period of 2015-01-01 to 2015-12-31. Do you expect to have metrics for 2015?

Yes, I tried with year 2016, 2017, 2018. The same is with all. The full link is
http://ijcrsee.com/index.php/ijcrsee.com/sushiLite/v1_7/GetReport?Report=JR1&Release=4.1&BeginDate=2017-01-01&EndDate=2017-12-31
Where I made mistake?
By the way, in the error. log receive>

[07-Nov-2019 15:23:49 Europe/Belgrade] PHP Warning: get_class() expects parameter 1 to be object, null given in /home/ijcadsee/public_html/plugins/generic/sushiLite/classes/SushiLite.inc.php on line 212

Your journal’s path is “ijcadsee”, per then end of:
http://ijcrsee.com/index.php/ijcrsee/

So, a SUSHI-Lite URL for this month’s JR1 would be:
http://ijcrsee.com/index.php/ijcrsee/sushiLite/v1_7/GetReport?Report=JR1
This does return results.

Your metrics appear to start in November 2018:
http://ijcrsee.com/index.php/ijcrsee/sushiLite/v1_7/GetReport?Report=JR1&Release=4.1&BeginDate=2018-01-01&EndDate=2018-11-01
is empty, but
http://ijcrsee.com/index.php/ijcrsee/sushiLite/v1_7/GetReport?Report=JR1&Release=4.1&BeginDate=2018-11-01&EndDate=2018-11-30
returns results.

If you have your Apache or usageStatisticsLog files from before that time, you may need to re-process them to create metrics for the prior data. This can be fraught with challenges if your OJS version or base_url has changed over time. If this is the case, let’s chat about that in a new thread.