diference beetwen shedule and schedule_detail tables

Schedule holds one record for each layout scheduled. Schedule_detail holds a record for each time the record in schedule should be shown on the display.

For example if you had a display which you'd scheduled a layout to run on with a repeat once a week for 4 weeks, then you'd have one record in the schedule table and then 4 records in the schedule_detail table.

That's at least my understanding.

Alex

Thanks for that answers.

i am trying to extract:
how much layouts use more than one region (coleges said that a little bit more complicated query should do that :))
how many times the default layout was changed (as far as i see there is only data of last time changed...)
how many times a user did connect on the xibo server
how many users are using advanced features like regions, rss...
how many layouts a user created (that one i have)
data about files on the server and client (number of files, average file size, max file size - with that data i can see if the server/client should be upgraded and if the server file upload limit is set to high or to low)

Thanks Dan Garner, that solved my question.

> how much layouts use more than one region (coleges said that a little bit more complicated query should do that :))
You'd have to extract the XML from each layout and then count the number of region nodes contained in it. I don't think you'll be able to get that from a query directly.

> how many times the default layout was changed (as far as i see there is only data of last time changed...)
As you say we don't keep a history of display changes. If you have auditing enabled theoretically you could look through the log and extract it - but you'll collect a huge amount of log messages in the process.

> how many times a user did connect on the xibo server
I don't see how you'd get that either historically. You could poll the sessions table every few minutes to log out when users log in/disconnect going forwards though.

> how many users are using advanced features like regions, rss...
Again you'd have to pull all the layout XML and parse through the xml looking at the media nodes.

> data about files on the server and client (number of files, average file size,
> max file size - with that data i can see if the server/client should be
> upgraded and if the server file upload limit is set to high or to low)

Server side files are in the server library directory. That should be pretty straight forward. It should be possible to map those files on to any given client by looking at layouts scheduled to it to see what files it should have.

Alex

>>> Server side files are in the server library directory.
>>> That should be pretty straight forward.
>>> It should be possible to map those files on to any given client by looking at layouts scheduled to it to see what files it should have.

i also thinked of that, but there is a "media" table which also has filsizes in it. so that shouldnt be a problem.

and why is the sessions table even truncating?

Sessions is a list of valid login sessions - so it makes no sense to have old expired or invalid sessions in it. It would also cause the table to grow indefinitely if old sessions weren't removed.

Danilo,

As you are experiencing, Xibo has not been optimised for gathering the
statistics you mention - you are the first person to express interest in
this.

It would be a reasonably small change to collect some statistics on these
things (like number of successful logins, number of failed logins, number of
default display changes, number of regions, media summary and sizes) as they
occur.

If you create a blueprint for this with those things you want inside it we
can then consider if for a later release or a bounty depending on how much
you want it.