For users who want to analyze the data stored in CELUS themselves, CELUS offers an export into a dedicated analytical database.
The export is updated weekly and contains all usage data from CELUS. Other data, such as information about harvesting success, configured credentials, etc. is not included.
Technology
The analytical database is built on top of ClickHouse - a powerful column-oriented analytical database. This database is run and maintained by CELUS on its own infrastructure.
Clickhouse is compatible with Microsoft Power BI, Apache Superset, Metabase and many other analytical tools.
Database structure
Each report from your CELUS instance is stored in a separate table in the database. For example, if you are harvesting TR, DR and PR reports, you will have three tables in the database with the names TR, DR and PR. COUNTER 5.1 reports have their own tables with the 51 suffix, e.g. TR51. Non-COUNTER reports are exported as well.
Each table has the same basic structure, with some report-specific columns. The common columns are (please note the double underscore in some of the column names):
organization_id
(integer
) - internal CELUS id of the organization that the report belongs toorganization__name
(string
) - the name of the organization that the report belongs toplatform_id
(integer
) - internal CELUS id of the platform that the report belongs toplatform__name
(string
) - the name of the platform that the report belongs todate
(date
) - the date of the usagemetric_id
(integer
) - internal CELUS id of the metric that the report belongs tometric__short_name
(string
) - the short name of the metric, for COUNTER matches the COUNTER metric nametitle_id
(integer
) - internal CELUS id of the title that the report belongs totitle__name
(string
) - the name of the titletitle__pub_type
(string
) - the publication type of the titletitle__isbn
(string
) - the ISBN of the titletitle__issn
(string
) - the ISSN of the titletitle__eissn
(string
) - the e-ISSN of the titletitle__doi
(string
) - the DOI of the titleimport_batch_id
(integer
) - internal CELUS id of the import batch - this groups together data from oneimport (harvest, manual upload, etc.). One import batch always covers one month. This column is intended mainly for internal use.
value
(integer
) - the value of the metric - the usage count
The extra columns/dimensions correspond to the COUNTER specification of that report. For example, COUNTER 5.1 TR report (stored in TR51 table) has the following extra columns:
data_type
(string
) - the data type of the titleaccess_method
(string
) - the access method of the titleplatform_in_counter_data
(string
) - whether the platform is in the COUNTER dataaccess_type
(string
) - the access type of the titlepublisher
(string
) - the publisher of the titleyop
(string
) - the year of publication of the title
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article