u/ThoriDay

Disclosure up front: I build tooling in this area, so I have an interest.
I’m asking because I genuinely don’t know what people’s real workflows look like, and every answer I’ve assumed has turned out to be wrong. Not asking what you’d recommend. Asking what you actually do, including the unglamorous version.
Specifically: When the thought first arrives, what’s the first thing you open? Google Scholar, Scopus, a specific database, Zotero, an LLM, or do you message someone?
If the first pass comes back with nothing, what’s the second move? Do you change vocabulary, chase citations backwards, ask a librarian, or decide it’s fine and get on with it? Has anything actually changed for you in the last two years? Everyone talks about Elicit, Consensus, SciSpace, Perplexity, Connected Papers, Litmaps and the rest, but I can’t tell who’s genuinely using them for this versus who tried one once. And the bit I’m most curious about: how do you know when to stop? Is there a point where you decide you’ve looked properly, or do you just run out of time and submit? Field and career stage would help if you don’t mind saying, since I suspect a first-year PhD and a 20-year PI are doing completely different things here.

Disclosure up front: I build tooling in this area, so I have an interest.
I’m asking because I genuinely don’t know what people’s real workflows look like, and every answer I’ve assumed has turned out to be wrong. Not asking what you’d recommend. Asking what you actually do, including the unglamorous version.
Specifically: When the thought first arrives, what’s the first thing you open? Google Scholar, Scopus, a specific database, Zotero, an LLM, or do you message someone?
If the first pass comes back with nothing, what’s the second move? Do you change vocabulary, chase citations backwards, ask a librarian, or decide it’s fine and get on with it? Has anything actually changed for you in the last two years? Everyone talks about Elicit, Consensus, SciSpace, Perplexity, Connected Papers, Litmaps and the rest, but I can’t tell who’s genuinely using them for this versus who tried one once. And the bit I’m most curious about: how do you know when to stop? Is there a point where you decide you’ve looked properly, or do you just run out of time and submit? Field and career stage would help if you don’t mind saying, since I suspect a first-year PhD and a 20-year PI are doing completely different things here.

Been chewing on this and want to know if it matches other people's experience or if I'm overweighting something rare.

Most mistakes in research eventually surface. Bad stats get caught. Dodgy method gets caught. Overclaimed result gets caught. Someone tells you, usually at the worst possible moment, and you fix it.

Missing a paper doesn't work like that. There's no signal. Nothing tells you the thing you've spent eight months on was published in 1996 under terminology nobody uses anymore. You find out from a reviewer, or from someone at a conference, or you never find out and neither does anyone else.

What gets me is that you can't protect yourself with effort. Searching harder means running more queries with the words you already have. If the earlier work used different words, more searching doesn't help. You'd need to already know the term in order to find the term.

And it seems to land hardest on the people least able to absorb it. Someone 25 years into a field carries a lot of it in their head, half-remembers something from the 80s, goes and looks. A first-year PhD student has none of that.

So, for people further along than me:

Does the worry ever go away, or do you just get better at living with it?

Has it actually happened to you, and how did you find out?

Do you do anything specific to guard against it, or is it just accepted as part of the job?

There's a question that sits underneath every research idea, and I have never found a tool that answers it.

Not "what has been written about this." Everything answers that. Google Scholar will hand you ten thousand papers about your topic and none of them tell you the thing you need to know, which is: has someone already done this? The exact thing I am about to spend a year on. Is what I want to say actually new, or am I about to rediscover something that has been sitting in a journal since before I was born?

I hit this properly in my third year, doing my dissertation on multitask Bayesian optimisation. I had an angle I was excited about. I searched it, found plenty of adjacent work, nothing identical, and then spent weeks unable to tell whether that meant the space was open or whether I had just failed to search well enough. Those two feel exactly the same from the inside. That is what makes it horrible. You cannot distinguish an empty space from your own blind spot, and the only way I eventually resolved it was reading until something turned up, which is not a method, it is just endurance.

And every time I asked someone further along how they handled it, the answer was some version of: you read for months, you ask your supervisor, you go to a conference, and eventually someone in the room says "have you seen the 2003 paper." That is the actual state of the art. A senior person's memory. Which works, until you do not have that person, or your supervisor's memory covers a slightly different corner of the field than the one you have wandered into.

There is a nastier version of it too, which is that fields rename things. The same idea comes back every decade or two under new vocabulary, so the paper that already did your work is sitting there fully indexed and completely invisible to you, because you have never heard the word it was filed under.

The cost of getting this wrong is not small. Months of work. A rejection that says "this has been done." Or the quieter version, where the work gets published and just does not matter, because it added nothing that was not already there.

So I built the thing I wanted to exist when I was stuck.

You give it a research idea. It goes and finds what has actually been done around it, and instead of handing you a reading list, it answers the question directly. Has someone already claimed this? If yes, it says so and names the paper. If no, it tells you what the closest work did, what it stopped short of, and what that leaves as yours. Something like: this paper established X, but never did Y, so Y is your contribution.

That sentence is the whole point. It is what I wanted at 21 and could not get.

I have started with climate science specifically, and I want to be straight about why. Climate change is real, the work matters, and the field is under more time pressure than almost any other. Every month a researcher spends discovering that their idea was published in 2011 is a month the field does not get back. If I can shave time off that anywhere, this is where I would rather it be.

Two decisions I want to be upfront about.

Every claim has to point at a real paper. In this domain, a tool that confidently invents a citation is worse than no tool at all, so grounding is verified rather than trusted.

And there is deliberately no novelty score. I built one, looked at it, and threw it away. Any number ends up measuring how crowded the topic is, and every good idea sits in a crowded topic, so everything scores middling and it tells you nothing. Worse, it punishes the best work. Taking a method somewhere it has not been used, or showing a consensus is wrong, is built entirely out of well studied pieces and is completely novel. Building on existing research is not a strike against you. It is what research is. So the output is a stated difference, not a number.

What I would like from this sub, because you are the people who would actually know:

How do you check this now, honestly? Where does your process break down? Has this bitten you, either finding out too late or nearly too late? And is "here is the closest work and here is what it did not do" the output that would actually help, or would you want something different?

If you want to try it and tell me where it falls apart, it is at unkwn42.com, free while in beta. Comment or message me and I will send an access code. I would rather someone came back and told me it missed a paper they know well than told me it looked nice. The first one I can do something with.

I'm a solo founder building unkwn42, a research terminal for climate science. Sharing it here for feedback and to talk about the build.

The core insight is that scientific literature search fails on renamed concepts. Fields recycle ideas under new vocabulary every decade, so keyword search tells researchers their idea is novel when it isn't. The consequence is wasted months and rejected papers.

The product takes a research idea and returns a grounded verdict on whether it exists already, with the prior work attached. The follow-on product, Reviewer2, takes an abstract and plays the hostile peer reviewer: it finds threatening prior art, ranks it, writes the attack a referee would make, and drafts the citation-grounded defence.

Stack is Next.js, Supabase, Railway, with OpenAlex for the corpus. Grounding verification was by far the hardest part, since a citation tool that invents papers is worse than no tool.

Beta is free: unkwn42.com, code REDDIT-CLIMATE.

Happy to go into detail on the extraction pipeline or the go-to-market if useful. Feedback on the landing page and the first-run experience especially welcome.

Full disclosure, this is my project, so treat the claims sceptically.

Climate science has a terminology problem that makes literature search unreliable. The same underlying phenomenon accumulates names over decades. Tipping points, critical transitions and rate-induced tipping overlap. On the aerosol side you have the Twomey effect, indirect effects, semi-direct effects and rapid adjustments describing a related mess of processes. If you search using this decade's vocabulary, the older work is effectively invisible to you.

I built unkwn42 to attack that specifically. You enter a research idea and it tells you whether it has already been done, surfacing prior work including the renamed and drifted versions, plus who is publishing in the area and where it seems to be heading. Every statement is tied to an actual paper, not generated from memory.

There's also Reviewer2, which takes an abstract or a rough idea and plays the hostile referee: it finds the papers someone could cite against your novelty claim, ranks them by how dangerous they are, states the attack, and drafts the defence for how your work differs.

Free during beta. Sign up at unkwn42.com, code REDDIT-CLIMATE.

The ask: if you work in climate or atmospheric science, run it on a topic where you already know the literature better than any tool does, and tell me what it got wrong. I would much rather hear that it missed an obvious 1980s paper than hear that it looked nice.