I’m in the process of migrating a legacy forum with about 1.3 million posts and two decades of history to Discourse. What I would like to avoid is for every user to show 0 read time from the start upon the successful migration, since many have 5, 10, and some 15+ years of history. With Discourse’s…

I think I’d do something like Post.where(user_id: user.id).where(some other stuff?).each do |post| PostTiming.create(topic_id: post.topic_id, post_number: post.post_number, user_id: user.id, msecs: READ_TIME_MSECS end [image] 007: valuing each post at 300 seconds of read time is just my my e…

I haven’t taken the time to think through the timing yet, What I was thinking is that read time technically doesn’t just take into account times when a post resulted from the reading. A lot of people read a lot and spend a lot of time skimming, which wouldn’t be taken into account at all based only …

A much more valuable use of your time is probably identifying what automatic threshold you should use for granting imported users TL2, and hand-picking the people in your community who you trust to have good judgement regarding titles and categorization to start out as TL3. TL promotion is the prim…

Estimating historical read time for a large forum import

Development

pfaffman (Jay Pfaffman) April 18, 2020, 12:41am 4

I’ve done scores of imports. No one has ever asked for making up bogus read times. I bet people will know that the stats start when you switched to discourse.

Topic		Replies	Views
Are post read counts per user accurate? Product Support	20	5544	November 27, 2017
How to mark imported posts as read Product Support	4	832	September 2, 2020
How does post tracking work in Discourse Development dev-news	4	4321	April 24, 2019
How is read time calculated? Product Support	1	2391	November 15, 2019
Fixing read counts in migrated forum data Migration	2	609	April 27, 2020

Estimating historical read time for a large forum import

Related topics