I have an example where searching within a set of existing results would be useful.
The US Supreme Court term recently ended. And, a panelist in a roundtable discussion mentioned that a lower court judge responded to one of the decisions.
Mojeek did a good job of finding the case:
# Query
federal judge non compete since:20240630
# URL
https://www.mojeek.com/search?q=federal+judge+non+compete+since%3A20240630
# Decoded URL
https://www.mojeek.com/search?q=federal+judge+non+compete+since:20240630
# Result
Federal Judge in Texas Issues Injunction Putting FTC
https://www.jdsupra.com/legalnews/federal-judge-in-texas-issues-3019713/
crawled today
See more results from www.jdsupra.com »
Texas judge temporarily blocks government ban on non-compete
https://abc7.com/post/texas-judge-temporarily-blocks-government-ban-compete-agreements/15028372/
crawled 1 day ago
Judge delays ban on employee non-compete agreements
https://westsidepeoplemag.com/judge-delays-ban-on-employee-non-compete-agreements/
crawled 1 day ago
Federal Judge Considering Stay of FTC Non-Compete Rule
https://www.gkglaw.com/publications/820-federal-judge-considering-stay-ftc-non-compete-rule
crawled today
See more results from www.gkglaw.com »
However, the story I read did not mention the Supreme Court.
At this point, I could simply add keywords such as “supreme court”. But, I suspect that those added keywords would overpower my existing ones. And, the results would be dominated by higher-ranked but less relevant results.
What I really want to do is to search within these existing results. That would keep the part that is working and which I like. And, it would narrow the results and allow me to focus just on the ones which are most relevant.
Going ahead and conducting the follow-on search, Mojeek produced the following results:
# Query
supreme court federal judge non compete since:20240630
# URL
https://www.mojeek.com/search?q=supreme+court+federal+judge+non+compete+since%3A20240630
# Decoded URL
https://www.mojeek.com/search?q=supreme+court+federal+judge+non+compete+since:20240630
# Result
Federal Cases (but not US Supreme Court) | Drew Capuder's
https://dcemploymentlawblog.com/category/federal-cases-but-not-us-supreme-court/
crawled 1 day ago
See more results from dcemploymentlawblog.com »
New York Court Declines to Enforce Non-Compete Clause Against
https://www.thenjemploymentlawfirmblog.com/new-york-court-declines-to-enforce-non-compete-clause-against-former-employees/
crawled 2 days ago
Federal High Court and National Industrial Court lack
https://pmnewsnigeria.com/2024/06/21/federal-high-court-and-national-industrial-court-lack-jurisdiction-on-chieftaincy-matters/
crawled 1 day ago
Supreme Court of N.H. v. Piper :: 470 U.S. 274 (1985) :: Justia
https://supreme.justia.com/cases/federal/us/470/274/
crawled 1 day ago
See more results from supreme.justia.com »
BREAKING: District Court in Texas Issues Injunction on FTC
https://www.ctemploymentlawblog.com/2024/07/articles/breaking-district-court-in-texas-issues-injunction-on-ftc-non-compete-rule-leaving-future-in-doubt/
crawled 1 day ago
See more results from www.ctemploymentlawblog.com »
My second result was published in 2018 but was only recently crawled.
My fifth result was recently published and relates the Supreme Court decision to the lower court injunction. This was the answer I was looking for.
Returning to the original results, ctemploymentlawblog dot com appeared as my result number nineteen. So, if I had been able to search within my existing results then it is likely that would have been the top search result.
With respect to the replies I’ve missed, I want people to think about what they would do if they had a set of Mojeek results and wanted to search within those results. That is the issue I’m trying to focus on and solve.
And, my additional concern is that I would like the search process to remain simple and not involve complicated and long queries.
Also, please keep in mind that Mojeek is mostly a lexical search engine. And the implicit meaning humans use in everyday speech is not handled there. That is by design. And that’s fine. Only, there are opportunities to use lexical search more effectively. And I hope this thread demonstrates one case.
As a sidenote, if you’d like to know more about making the Web machine-readable then you might try reading this article about the semantic web: