@anonymous-matomo-user opened this Issue on December 9th 2009

Currently in the database logs, browsers, operating systems, or countries are defined as static array :

static protected $browsers = array(
'opera' => 'OP',
'msie' => 'IE',
'microsoft internet explorer' => 'IE',
'internet explorer' => 'IE',

So I's currently impossible to format data with the label values accessing only database. (I must maintain a mapping list manually).

Proposal: provide API to publish this data. What data should it return appart from the Browsers and OS maps? Where should this API be?

@robocoder commented on December 9th 2009 Contributor

For performance, no, we have no plans to read from such tables, but I don't see why we couldn't maintain such tables or at least, make it export-ready via API.

@mattab commented on December 9th 2009 Member

Export ready via API sounds like a plan, not having these mapping in the DB (redundant data that we want to keep in files)

@mattab commented on December 9th 2009 Member

Of course, ideally the API would be used for everything, now that the Live! plugin (#44) has an extensive API to return the data from the piwiklog* tables.

@anonymous-matomo-user commented on December 10th 2009

Ok thanks for your reply.

@robocoder commented on March 22nd 2011 Contributor

For the purpose of discussion, I'm going to refer to this static data as System Tables.

We could add an API method for each system table in the closest/corresponding plugin, e.g., PluginName.getSystemTableName($parameters_if_any) for:

  • SitesManager: Currencies
  • UserCountry: Countries, Continents
  • LanguagesManager: Languages, LanguageToCountry
  • Referers: SearchEngines
  • UserSettings: Browsers, OperatingSystems, Plugins, Screens

Example: SitesManager.getCurrenciesSystemTable()

We could also have API.getSystemTableMetaData().

@mattab commented on March 22nd 2011 Member

System Tables are not required for any use of the API, since the API gives friendly name in output.

System tables are only used for low level SQL requests. I think API.getSystemTableMetaData() is less code & better to have all in 1 place, since one typically needs all system tables or none. Maybe named getSystemTables() ?

Powered by GitHub Issue Mirror