You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-- ID: joomla-tags-- DESCRIPTION: Return information about each tag and related general result-- of tagged articles via `content_count` and `content_hits`---- AUTHOR: Emerson Rocha <emerson[at]alligo.com.br>-- COMPANY: Alligo-- LICENSE: "SPDX-License-Identifier: MIT"-- VERSION: 1.1-- CREATED: 2021-01-18 22:00 BRT-- REVISION: 2021-01-23 06:19 UTC 1.1 Added tag_hits and content_hits
Version 1.1 added tag_hits and content_hits.
I think that both joomla-tags.sql and joomla-users.sql could already return some better statistics without need of use data mining. Since the queries are not meant to be ligth, we can get pretty intense on what to return. But the final idea still let major processing for outside tools, like Orange or Weka. Thats why all fields already are prefixed with tag_: this both helps with be sure from were the data is, and also can even allow build models to predict behavior.
The text was updated successfully, but these errors were encountered:
Version 1.1 added
tag_hits
andcontent_hits
.I think that both joomla-tags.sql and joomla-users.sql could already return some better statistics without need of use data mining. Since the queries are not meant to be ligth, we can get pretty intense on what to return. But the final idea still let major processing for outside tools, like Orange or Weka. Thats why all fields already are prefixed with
tag_
: this both helps with be sure from were the data is, and also can even allow build models to predict behavior.The text was updated successfully, but these errors were encountered: