Dataset from a study aiming to analyze the coverage of Latin American and Caribbean journals in Google Scholar Metrics (GSM). Data from 8,205 journals from 24 countries of the region were downloaded from Latindex database. A Python script was used for automated title search and data extraction (titles, h5-index, h5-median, URLs) in GSM. For the journals not found, a manual search was carried out, with attempts by variations of the title. It was found 3,070 journals indexed in GSM, which corresponds to 37.42% of the Latindex list. The search was performed on the 2021 edition of GSM, which considers articles published between 2016 and 2020 and citations registered until July 2021. The number of all types of documents published (productivity) in the h5-index period (2016-2020) in Scopus, Journal Citation Reports, and SciELO of 1,314 journals was also identified.

The present dataset is the result of this study, which is under peer-review in a scientific journal.

The dataset comprises titles, h5-index; h5-median, URLs of 3,070 publications from Latin America and the Caribbean identified in Google Scholar Metrics, and the respective editorial information of the publications was extracted from Latindex

The original language of the content was kept, mainly Spanish in the case of editorial data from Latindex. The columns descriptors are also shown in English.

The productivity data refer to the number of all types of documents published by the journals in the period 2016-2020. Data were extracted from the InCities Journal Citation Reports, Scopus, and SciELO Citation Index (Web of Science database).

In this version 2, only the productivity data were changed, covering a larger number of journals (1,314) and including all types of documents. Other data are the same as in the first version (https://doi.org/10.5281/zenodo.5572873).

Academic journals indicators developed from the information contained in the Scopus database (Elsevier B.V.). These indicators can be used to assess and analyze scientific domains.

The risk of bias and applicability concerns of the included studies based on PROBAST.

The Repository Analytics and Metrics Portal (RAMP) is a web service that aggregates use and performance use data of institutional repositories. The data are a subset of data from RAMP, the Repository Analytics and Metrics Portal (http://rampanalytics.org), consisting of data from all participating repositories for the calendar year 2018. For a description of the data collection, processing, and output methods, please see the "methods" section below. Note that the RAMP data model changed in August, 2018 and two sets of documentation are provided to describe data collection and processing before and after the change.

Methods

RAMP Data Documentation – January 1, 2017 through August 18, 2018

Data Collection

RAMP data were downloaded for participating IR from Google Search Console (GSC) via the Search Console API. The data consist of aggregated information about IR pages which appeared in search result pages (SERP) within Google properties (including web search and Google Scholar).

Data from January 1, 2017 through August 18, 2018 were downloaded in one dataset per participating IR. The following fields were downloaded for each URL, with one row per URL:

url: This is returned as a 'page' by the GSC API, and is the URL of the page which was included in an SERP for a Google property.
impressions: The number of times the URL appears within the SERP.
clicks: The number of clicks on a URL which took users to a page outside of the SERP.
clickThrough: Calculated as the number of clicks divided by the number of impressions.
position: The position of the URL within the SERP.
country: The country from which the corresponding search originated.
device: The device used for the search.
date: The date of the search.

Following data processing describe below, on ingest into RAMP an additional field, citableContent, is added to the page level data.

Note that no personally identifiable information is downloaded by RAMP. Google does not make such information available.

More information about click-through rates, impressions, and position is available from Google's Search Console API documentation: https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics/query and https://support.google.com/webmasters/answer/7042828?hl=en

Data Processing

Upon download from GSC, data are processed to identify URLs that point to citable content. Citable content is defined within RAMP as any URL which points to any type of non-HTML content file (PDF, CSV, etc.). As part of the daily download of statistics from Google Search Console (GSC), URLs are analyzed to determine whether they point to HTML pages or actual content files. URLs that point to content files are flagged as "citable content." In addition to the fields downloaded from GSC described above, following this brief analysis one more field, citableContent, is added to the data which records whether each URL in the GSC data points to citable content. Possible values for the citableContent field are "Yes" and "No."

Processed data are then saved in a series of Elasticsearch indices. From January 1, 2017, through August 18, 2018, RAMP stored data in one index per participating IR.

About Citable Content Downloads

Data visualizations and aggregations in RAMP dashboards present information about citable content downloads, or CCD. As a measure of use of institutional repository content, CCD represent click activity on IR content that may correspond to research use.

CCD information is summary data calculated on the fly within the RAMP web application. As noted above, data provided by GSC include whether and how many times a URL was clicked by users. Within RAMP, a "click" is counted as a potential download, so a CCD is calculated as the sum of clicks on pages/URLs that are determined to point to citable content (as defined above).

For any specified date range, the steps to calculate CCD are:

Filter data to only include rows where "citableContent" is set to "Yes."
Sum the value of the "clicks" field on these rows.

Output to CSV

Published RAMP data are exported from the production Elasticsearch instance and converted to CSV format. The CSV data consist of one "row" for each page or URL from a specific IR which appeared in search result pages (SERP) within Google properties as described above.

The data in these CSV files include the following fields:

url: This is returned as a 'page' by the GSC API, and is the URL of the page which was included in an SERP for a Google property.
impressions: The number of times the URL appears within the SERP.
clicks: The number of clicks on a URL which took users to a page outside of the SERP.
clickThrough: Calculated as the number of clicks divided by the number of impressions.
position: The position of the URL within the SERP.
country: The country from which the corresponding search originated.
device: The device used for the search.
date: The date of the search.
citableContent: Whether or not the URL points to a content file (ending with pdf, csv, etc.) rather than HTML wrapper pages. Possible values are Yes or No.
index: The Elasticsearch index corresponding to page click data for a single IR.
repository_id: This is a human readable alias for the index and identifies the participating repository corresponding to each row. As RAMP has undergone platform and version migrations over time, index names as defined for the index field have not remained consistent. That is, a single participating repository may have multiple corresponding Elasticsearch index names over time. The repository_id is a canonical identifier that has been added to the data to provide an identifier that can be used to reference a single participating repository across all datasets. Filtering and aggregation for individual repositories or groups of repositories should be done using this field.

Filenames for files containing these data follow the format 2018-01_RAMP_all.csv. Using this example, the file 2018-01_RAMP_all.csv contains all data for all RAMP participating IR for the month of January, 2018.

Data Collection from August 19, 2018 Onward

RAMP data are downloaded for participating IR from Google Search Console (GSC) via the Search Console API. The data consist of aggregated information about IR pages which appeared in search result pages (SERP) within Google properties (including web search and Google Scholar).

Data are downloaded in two sets per participating IR. The first set includes page level statistics about URLs pointing to IR pages and content files. The following fields are downloaded for each URL, with one row per URL:

url: This is returned as a 'page' by the GSC API, and is the URL of the page which was included in an SERP for a Google property.
impressions: The number of times the URL appears within the SERP.
clicks: The number of clicks on a URL which took users to a page outside of the SERP.
clickThrough: Calculated as the number of clicks divided by the number of impressions.
position: The position of the URL within the SERP.
date: The date of the search.

Following data processing describe below, on ingest into RAMP a additional field, citableContent, is added to the page level data.

The second set includes similar information, but instead of being aggregated at the page level, the data are grouped based on the country from which the user submitted the corresponding search, and the type of device used. The following fields are downloaded for combination of country and device, with one row per country/device combination:

country: The country from which the corresponding search originated.
device: The device used for the search.
impressions: The number of times the URL appears within the SERP.
clicks: The number of clicks on a URL which took users to a page outside of the SERP.
clickThrough: Calculated as the number of clicks divided by the number of impressions.
position: The position of the URL within the SERP.
date: The date of the search.

Note that no personally identifiable information is downloaded by RAMP. Google does not make such information available.

More information about click-through rates, impressions, and position is available from Google's Search Console API documentation: https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics/query and https://support.google.com/webmasters/answer/7042828?hl=en

Data Processing

Upon download from GSC, the page level data described above are processed to identify URLs that point to citable content. Citable content is defined within RAMP as any URL which points to any type of non-HTML content file (PDF, CSV, etc.). As part of the daily download of page level statistics from Google Search Console (GSC), URLs are analyzed to determine whether they point to HTML pages or actual content files. URLs that point to content files are flagged as "citable content." In addition to the fields downloaded from GSC described above, following this brief analysis one more field, citableContent, is added to the page level data which records whether each page/URL in the GSC data points to citable content. Possible values for the citableContent field are "Yes" and "No."

The data aggregated by the search country of origin and device type do not include URLs. No additional processing is done on these data. Harvested data are passed directly into Elasticsearch.

Processed data are then saved in a series of Elasticsearch indices. Currently, RAMP stores data in two indices per participating IR. One index includes the page level data, the second index includes the country of origin and device type data.

About Citable Content Downloads

Data visualizations and aggregations in RAMP dashboards present information about citable content downloads, or CCD. As a measure of use of institutional repository

Performance of the included models in chronological order for the disease progression outcomes.

The characteristic of the included studies in chronological order for the disease progression outcomes.

Die Daten umfassen Stichproben an je 100 Journalartikeln und Buchpublikationen aus der Soziologie. Ausgwählt wurden Veröffentlichungen aus deutschsprachigen und nicht-deutschsprachigen Ländern.

Für alle Artikel der Stichprobe wurde geprüft,

1) ob sie im Gold Open Access verfügbar waren
2) ob sie im Green Open Access verfügbar waren
3) auf welchem Repository-Typ sie (im Falle einer Green Open Access Publikation) verfügbar waren
4) seit wann sie im Green Open Access verfügbar waren
5) ob Forschungsdaten zum Artikel verfügbar waren
6) ob Forschungssoftware zum Artikel verfügbar war
7) wie häufig der Artikel in Google Scholar zitiert wurde
8) wie häufig der Artikel im Web of Science zitiert wurde
9) wie häufig der Artikel in Scopus zitiert wurde
10) wie häufig der Artikel in den Sociological Abstracts zitiert wurde
11) wie viele Mendeley User Counts der Artikel aufwies
12) wie häufig der Artikel getwittert wurde (Datenquelle: Topsy)

Für alle Bücher der Stichprobe wurde geprüft,

1) ob sie im Gold Open Access verfügbar waren
2) ob sie im Green Open Access verfügbar waren
3) auf welchem Repository-Typ sie (im Falle einer Green Open Access Publikation) verfügbar waren
4) seit wann sie im Green Open Access verfügbar waren
5) wie häufig das Buch in Google Scholar zitiert wurde
6) wie häufig das Buch im Web of Science zitiert wurde (als Cited-Reference-Analyse)
7) wie häufig das Buch in Scopus zitiert wurde
8) wie häufig das Buch in der International Bibliography of the Social Sciences zitiert wurde
9) wie viele Mendeley User Counts das Buch aufwies
10) wie häufig das Buch getwittert wurde (Datenquelle: Topsy)

Da die Impact-Informationen unter Copyright-Schutz der Datenbank-Anbieter stehen, können diese nicht frei zugänglich gemacht werden. Es existiert jedoch eine offen verfügbare Version dieser Datensammlung, die allerdings keine Impact-Informationen enthält.