MétaCan
Menu
Back to cohort
Record W6925637274 · doi:10.17632/6vc9x6g9k5.1

Customer Experience across Touchpoints along the Customer Journey. A Text Mining Analysis

2022· dataset· en· W6925637274 on OpenAlexaboutno aff

Bibliographic record

VenueData Archiving and Networked Services (DANS) · 2022
Typedataset
Languageen
FieldMedicine
TopicDown syndrome and intellectual disability research
Canadian institutionsnot available
Fundersnot available
KeywordsPython (programming language)Sentiment analysisCenter (category theory)The InternetCustomer relationship managementCustomer base

Abstract

fetched live from OpenAlex

To extract data from Foursquare, we wrote a Python script that uses the Foursquare Developers API to collect relevant data. The Foursquare API refers to physical stores in a city as “venues” and the user-written reviews of the experience in the stores as “tips”. To extract the tips for the venues, we used the “venues search” functionality of the API (Foursquare, 2020), which allowed us to search for "venues" within a certain radius (The maximum supported radius is currently 100,000 meters) from the center of a specific city. We selected Alpha and Beta, cities from the United States (New York, Chicago, Los Angeles, Washington, Boston, and San Francisco), the UK (London), Canada (Toronto), and Australia (Melbourne, Sydney) based on the “Global City Index”. Using the Twitter Search API through a Python script with the Tweepy library, we initially collected 3,114,924 anonymized tweets, which mentioned 75 retail brands between September 27th, 2018, and April 10th, 2019. This data represents a broad cross-section of English-written tweets on the retail brand’s categories in the United States.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Dataset · Consensus signal: Dataset
Teacher disagreement score0.013
Threshold uncertainty score0.027

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0000.003
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0030.004
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0070.012

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.054
GPT teacher head0.364
Teacher spread0.310 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreDataset

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueData Archiving and Networked Services (DANS)Same topicDown syndrome and intellectual disability researchFrench-language works237,207