{"id":"411361b7-9784-48c7-ae38-c19619e7f2ab","arxiv_id":"2412.10714","paper_version":1,"verdict":"REJECT","confidence":"HIGH","novelty_score":2.0,"correctness_risk":"high","formal_verification":"none","parameter_count":0,"one_line_summary":"The paper outlines a hybrid movie recommender that merges static Kaggle data with scraped real-time data, but it provides no evaluation to justify its claim of improved recommendations.","lead":"This paper describes a movie recommendation system that would combine a static database of movie details with live information scraped from Rotten Tomatoes and IMDb. It presents the design and example code, yet offers no experiments, measurements, or comparisons to support the claim that this improves recommendations.","discovery_kind":"extension","skeptic_critique":{"model":"deepseek-v4-flash","headline":"Central claim is asserted, not demonstrated: no experiment compares static-only vs. static-plus-web-crawled recommendations, and the real-time data pipeline in Sec. 3.1.1 is explicitly hypothetical.","rationale":"The reader's weakest assumption focuses on the unverified scraping pipeline, which is one important gap. My stress-test finds an even more load-bearing gap: even granting that real-time data can be fetched, the paper provides no empirical evidence that such data changes or improves recommendations. The abstract and Section 4 state the dynamic-data benefit as a conclusion, but the body only gives illustrative code and describes static-dataset processing. No metrics, no baseline comparison, no temporal evaluation, and no user study appear anywhere. This is not a disagreement with consensus; it is an unsupported causal claim in a research preprint. A machine-checked proof, a shipped reproducible artifact, or a parameter-free derivation could substitute for experiments, but none is present. The paper could serve as a project report or tutorial, and as such it may be useful for educational purposes, but the central claim is not substantiated. Therefore the rejection stands, with no change to the reader's verdict.","tokens_in":7838,"tokens_out":2449,"duration_ms":23538,"concrete_test":"Implement the proposed system end-to-end for a fixed period: use official APIs or permitted feeds to collect dated records (new releases, ratings, reviews) for, say, 60 days; build user profiles only from actions before each date; generate recommendations with (i) the static TMDB/MovieLens model and (ii) the static-plus-real-time hybrid; evaluate on held-out later user interactions or a user study. Report NDCG@10, recall@10, and satisfaction ratings for both variants. If the dynamic variant does not significantly outperform the static baseline on these held-out temporal metrics, the central claim is unsupported.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim (abstract; Section 4) is that incorporating dynamic web-crawled data boosts user satisfaction and aligns recommendations with current viewing trends. That claim is causal and empirical: it requires a comparison of a static-only recommender against a static-plus-real-time recommender on the same users, ideally with a temporal train/test split. The manuscript does not supply this. Section 3.1.1 explicitly says Rotten Tomatoes blocks scraping, that prior permission is required, and that the code examples are based on a hypothetical or similar site-scraping approach. Section 3.1.2 describes APIs and code snippets but produces no crawled dataset, no collection timestamps, and no evidence that any real-time feed was ever fetched. Section 3.2 evaluates nothing; it merely describes using TMDB and MovieLens static datasets. Section 4 then asserts the effectiveness of the integration. Thus the weakest load-bearing step is not the algorithm itself but the unverified empirical bridge from 'real-time data can be fetched' to 'real-time data improves recommendations'. Even if every code snippet works, the headline claim could still be false; the paper gives no way to test it.","agreement_with_reader":"partial"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper proposes a movie recommendation system that combines static datasets (TMDB 930K movies and MovieLens 25M) with real-time data collected from Rotten Tomatoes and IMDb via scraping and APIs. It outlines content-based, collaborative (SVD), and hybrid filtering components, and includes illustrative Python code snippets for data collection. The central claim, stated in the abstract and repeated in Section 4, is that incorporating dynamic web-crawled data boosts user satisfaction and aligns recommendations with current viewing trends. No experimental evaluation is provided; Section 3.2 describes datasets and Figure 3 shows example top-5 lists, but there are no metrics, baselines, or temporal train/test comparisons.","tokens_in":8036,"tokens_out":3388,"duration_ms":29769,"significance":"If the central claim were established, a validated static-plus-real-time hybrid recommender would be a useful engineering contribution. The paper has some strengths: it explicitly acknowledges that Rotten Tomatoes blocks scraping (Sec. 3.1.1), it recommends API access as a legal alternative, and it provides code snippets that illustrate the intended data-collection workflow. However, because the paper contains no experimental evidence that real-time data improves recommendation quality, the significance is currently potential rather than demonstrated.","major_comments":[{"comment":"The headline claim that incorporating dynamic data 'boosts user satisfaction' and 'aligns recommendations with current viewing trends' is causal and empirical, but the manuscript provides no evaluation comparing a static-only recommender against a static-plus-real-time recommender. There is no temporal train/test split, no metrics, no baselines, and no error analysis. Figure 3 shows example top-5 lists but supplies no ground truth or accuracy measure, so the central contribution is asserted rather than supported.","section":"Abstract and Sec. 4"},{"comment":"The dynamic-data pipeline is explicitly hypothetical. Section 3.1.1 states that Rotten Tomatoes 'actively blocks scraping attempts' and that the code examples are 'based on a hypothetical or similar site-scraping approach.' Section 3.1.2 presents API and scraping code snippets but reports no crawled dataset, no collection timestamps, and no evidence that any real-time feed was actually fetched. The Oppenheimer example is illustrative only, so the paper does not validate the feasibility of the real-time component at any scale.","section":"Sec. 3.1.1 and Sec. 3.1.2"},{"comment":"The paper claims to have 'evaluated our approach' on the TMDB 930K dataset and MovieLens 25M and to 'demonstrate robustness across various movie pools and feature sets,' but no evaluation protocol, performance metrics, or comparisons with prior recommendation methods are given. Without quantitative results, these statements cannot be checked, and Section 3.2 functions as a data description rather than an evaluation.","section":"Sec. 3.2"},{"comment":"The three recommendation models are described only at a conceptual level (cosine similarity for content-based filtering, SVD for collaborative filtering, and a sequential combination for the hybrid model). No implementation details, hyperparameters, or validation procedure are reported, making it impossible to reproduce the claimed recommendations or to assess whether the hybrid model actually combines the two signals.","section":"Sec. 3.3"}],"minor_comments":[{"comment":"The heading 'W eb Scrapping' contains a typo, and 'Scrapping' should be 'Scraping' in Section 3.1 and its subsections (e.g., the subsection labeled 'Scrapping.').","section":"Headers and Sec. 3.1"},{"comment":"The term 'context-based filtering' is used where 'content-based filtering' appears to be meant (Scope and Contributions; Sec. 3.3 first paragraph). Please make the terminology consistent.","section":"Sec. 1 and Sec. 3.3"},{"comment":"There are typographical errors such as 'featureed' and 'useing' in the sentence describing Kumar et al.; these should be corrected.","section":"Sec. 2.2"},{"comment":"The code snippets contain typographic curly quotes (e.g., `{'query': query}`) that are not valid Python string delimiters and would cause syntax errors if copied directly.","section":"Sec. 3.1.2"},{"comment":"The API key placeholders such as 'ACTUAL_API_KEY_FROM_ROTTEN_TOMATOES' are fine as placeholders, but the text should recommend reading keys from environment variables rather than hard-coding them, and should note that the Rotten Tomatoes public API has been discontinued.","section":"Sec. 3.1.2"},{"comment":"The comparison with existing work is entirely qualitative and would benefit from a table contrasting prior systems in terms of data sources, real-time capability, and evaluation methodology.","section":"Sec. 2.3"}],"recommendation":"reject","confidential_remarks":"I agree with the reader's rejection recommendation. The paper's central empirical claim is unsupported by any experiment, and the real-time data pipeline is explicitly hypothetical. Adding an evaluation section is theoretically possible, but it would require substantial new work—actual data collection, a static-versus-dynamic comparison, and quantitative benchmarking—rather than local revisions. The paper is more of a project report than a research contribution in its current form."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"This paper is best read as a student project write-up, not a research contribution. It describes a plausible architecture: scrape or API-fetch fresh movie data from Rotten Tomatoes and IMDb, combine it with a static Kaggle/TMDB/MovieLens dataset, and feed both into standard content-based, collaborative, and hybrid filtering. The code snippets are illustrative and the descriptions of the standard methods are accurate. The paper also honestly acknowledges that Rotten Tomatoes blocks scraping and that the examples are hypothetical, which is more candid than many submissions in this space.\n\nThe problem is that the headline claim—that incorporating dynamic data boosts user satisfaction and aligns recommendations with current trends—is simply asserted. There is no evaluation section, no metrics, no baseline, and no comparison of a static-only system against a static-plus-crawled one. The 'evaluation' mentioned in Section 3.2 is just a hand-picked top-5 list from TMDB and MovieLens; it does not measure accuracy, freshness, or user satisfaction. The entire real-time pipeline is unverified: no crawled dataset was produced, no timestamps, no evidence any API call returned data. The central causal claim could still be true, but the paper gives the reader no way to test it.\n\nI agree with the reader's take. The novelty is thin because combining scraping with recommendation is already present in the cited literature (e.g., refs 16 and 21). The soundness is low because the evidence does not match the claims. The paper does not deserve peer review as is; it would be a desk reject. That said, it is not incoherent or dishonest on its own terms. The authors know the limits of their approach and say so explicitly. If they added a real experiment—collecting a small crawled dataset with timestamps and comparing static-only against dynamic— this could become a workshop-level paper. As it stands, it is a tutorial.\n\nRecommendation: desk reject, but gently. Tell the authors to either scope the paper as a system design description or produce actual evidence for the effectiveness claim.","headline":"An honest but unevaluated design sketch that asserts the value of real-time web-crawled data in movie recommendation without any experiment; the central claim is unsupported.","tokens_in":8530,"tokens_out":1408,"would_cite":false,"duration_ms":13676,"reading_group":"no","serious_thinker":"yes","would_accept_peer_review":false},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"This paper proposes adding web-crawled real-time movie data to static datasets so that hybrid recommendations track new releases and current trends.","keywords":["movie recommendation","web crawling","content-based filtering","collaborative filtering","hybrid model","real-time data","web scraping","cosine similarity"],"falsifier":"Run the paper's collection code against the two movie-rating websites for a week and count how many requests return valid, schema-consistent records; if the sites block automated queries, return empty JSON, or change their HTML structure so the selectors fail, the dynamic-data layer as described does not function. Separately, compare the share of recommended titles released in the last month for the hybrid with and without the live-data layer to test the freshness claim.","tokens_in":7675,"feed_emoji":"🎬","tokens_out":10206,"duration_ms":83490,"temperature":0.7,"pith_summary":"This paper argues that movie recommendation systems built only on static datasets miss newly released and trending films. It proposes a system that pairs a large static movie dataset (over 930,000 records, plus a 25-million-rating benchmark) with real-time data gathered from movie-rating websites through Python-based scraping and API calls. Three recommendation models are described: content-based filtering using cosine similarity over genre, director, and cast features; collaborative filtering using matrix factorization; and a hybrid model that generates candidates with collaborative filtering and refines them by content. The paper's stated result is that incorporating dynamic data boosts user satisfaction and aligns recommendations with current viewing trends. The manuscript gives a system design and code sketches rather than a measured evaluation of that claim.","feed_headline":"Live web data proposed to keep movie picks on trend","feed_subtitle":"The design blends static datasets with live Rotten Tomatoes and IMDb scraping in a hybrid filtering model.","key_machinery":"The central mechanism is a two-tier data pipeline: a history tier built on a large static movie dataset and a live tier fed by scraping and API requests to movie-rating websites. The recommendation machinery combines content-based cosine similarity on genre, director, and cast vectors with SVD-based collaborative filtering, and then merges them in a hybrid model defined as collaborative-filtering output refined by content-based criteria. That hybrid is the object meant to keep recommendations both personalized and current, and the paper's running example is the system identifying a new biopic as trending and surfacing it for the right audience.","core_discovery":"The central claim is that a movie recommender can be made more responsive and more satisfying by merging a static historical dataset with real-time data pulled from movie websites through web crawling and APIs. The static layer supplies the base for content-based and collaborative models, while the dynamic layer is meant to catch recently released and trending movies, illustrated in the paper by Oppenheimer (2023) being picked up as trending and recommended to users interested in biographical dramas. The paper states that this combination 'boosts user satisfaction' and keeps recommendations aligned with current viewing trends, but the text does not report measured results from the real-time pipeline. Read in good faith, the contribution is a proposed architecture for adding freshness to hybrid filtering.","pith_inferences":["Editorial inference: the freshness claim could be checked by comparing the share of recommended titles released in the last 30 days for the hybrid with and without the live-data layer.","Editorial inference: since the two movie sites restrict automated access, the practical contribution is probably the API-access pattern (keys, JSON-LD parsing, offline HTML fallback) rather than crawling per se.","Editorial inference: the hybrid's order means any popularity bias in the collaborative step carries into the final list, a side effect the paper does not discuss.","Editorial inference: a natural extension would be feeding seasonal and holiday trends into the live layer as an explicit third input, something the paper lists as future work."],"forward_implications":["Streaming services could surface new releases and trending titles without waiting for ratings to accumulate, if the live-data layer functions as described.","The hybrid ordering (collaborative candidates, then content-based refinement) would let a system balance broad popularity with individual taste in one pass.","Web-crawled critic and audience scores could make recommendations sensitive to seasonal and holiday-specific viewing patterns, as the paper suggests.","Static-only recommenders would be at a structural freshness disadvantage, making licensed API access a natural part of production recommendation pipelines.","Because no evaluation is reported, these consequences hold conditionally on the scraping and API calls returning valid data at scale."],"supporting_citations":[{"why":"Supplies the hybrid recommender approach the paper builds on.","marker":"[24]"},{"why":"Provides the three-way taxonomy of content, collaborative, and hybrid filtering that structures the models.","marker":"[7]"},{"why":"Exemplifies content-based filtering with cosine similarity, the method used for the content layer.","marker":"[15]"},{"why":"Exemplifies collaborative filtering from user preferences, the basis of the SVD step.","marker":"[22]"},{"why":"Defines web crawling, the technique behind the real-time data layer.","marker":"[12]"},{"why":"Stresses code reuse and maintenance for scrapers, supporting the claim that live scraping is feasible.","marker":"[8]"},{"why":"Shows web scraping used for real-time product updates on an e-commerce site, a precedent for fresh-data recommendation.","marker":"[13]"},{"why":"States that current systems are limited by static datasets, the gap the paper tries to fill.","marker":"[11]"},{"why":"Presents an existing real-time recommendation system that the paper contrasts with its hybrid design.","marker":"[21]"},{"why":"The HTTP library used in the paper's code snippets for API requests to the movie sites.","marker":"[17]"}],"fun_headline_variants":["Web scraping spices up movie recommendations","Fresh movie picks via live web scraping","Hybrid recommender gets a web data boost","Crawl the web, suggest better movies","Real-time data enhances movie suggestions"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The entire real-time layer rests on the unverified assumption that movie-rating websites will serve scrapeable or API-accessible data at scale; the paper itself concedes that these sites actively block scraping and that the code examples are hypothetical.","fun_headline_variants_meta":{"raw":{"variants":["Web scraping spices up movie recommendations","Fresh movie picks via live web scraping","Hybrid recommender gets a web data boost","Crawl the web, suggest better movies","Real-time data enhances movie suggestions"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000321,"raw_usage":{"total_tokens":1716,"prompt_tokens":761,"completion_tokens":955,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":377,"completion_tokens_details":{"reasoning_tokens":893}},"tokens_in":377,"tokens_out":955,"duration_ms":9180,"temperature":1.0,"reasoning_tokens":893,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-11T15:39:51.753108+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Run the paper's collection code against the two movie-rating websites for a week and count how many requests return valid, schema-consistent records; if the sites block automated queries, return empty JSON, or change their HTML structure so the selectors fail, the dynamic-data layer as described does not function. Separately, compare the share of recommended titles released in the last month for the hybrid with and without the live-data layer to test the freshness claim.","supporting_citations":[{"cited_title":"Journal of Emerging Tech- nologies in Web Intelligence2(4) (2010)","cited_arxiv_id":null,"evidence_quote":"Supplies the hybrid recommender approach the paper builds on."},{"cited_title":"Int’l Journal of Emerging Technologies in Learning (iJET)16(3), 274–306 (2021)","cited_arxiv_id":null,"evidence_quote":"Provides the three-way taxonomy of content, collaborative, and hybrid filtering that structures the models."},{"cited_title":"Int’l’ Journal on Information and Communication Tech","cited_arxiv_id":null,"evidence_quote":"Exemplifies content-based filtering with cosine similarity, the method used for the content layer."},{"cited_title":"Applied Artif","cited_arxiv_id":null,"evidence_quote":"Exemplifies collaborative filtering from user preferences, the basis of the SVD step."},{"cited_title":"Foundations and Trends® in Infor- mation Retrieval 4(3), 175–246 (2010)","cited_arxiv_id":null,"evidence_quote":"Defines web crawling, the technique behind the real-time data layer."},{"cited_title":"Int’l Journal of Adv in Soft Comput","cited_arxiv_id":null,"evidence_quote":"Stresses code reuse and maintenance for scrapers, supporting the claim that live scraping is feasible."},{"cited_title":"Developing Products Update-Alert System for e-Commerce Websites Users Using HTML Data and Web Scraping Technique","cited_arxiv_id":"2109.00656","evidence_quote":"Shows web scraping used for real-time product updates on an e-commerce site, a precedent for fresh-data recommendation."},{"cited_title":"IEEE Access 10, 86578–86623 (2022)","cited_arxiv_id":null,"evidence_quote":"States that current systems are limited by static datasets, the gap the paper tries to fill."},{"cited_title":"In: 2017 IEEE Int’l Conf","cited_arxiv_id":null,"evidence_quote":"Presents an existing real-time recommendation system that the paper contrasts with its hybrid design."},{"cited_title":null,"cited_arxiv_id":null,"evidence_quote":"The HTTP library used in the paper's code snippets for API requests to the movie sites."}],"review_version":1}