Skip to content

Commit 56bab2c

Browse files
committed
Midnight commit.
1 parent a941d35 commit 56bab2c

File tree

3 files changed

+34
-1
lines changed

3 files changed

+34
-1
lines changed

api/server.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -273,7 +273,9 @@ async def lookup_curies_get(
273273

274274
@app.post("/lookup",
275275
summary="Look up cliques for a fragment of a name or synonym.",
276-
description="Returns cliques with a name or synonym that contains a specified string.",
276+
description="Returns cliques with a name or synonym that contains a specified string. "
277+
"You can find out more about this endpoint in the <a href="">NameRes documentation</a>."
278+
"Note that the cliques we search through are conflated ",
277279
response_model=List[LookupResult],
278280
tags=["lookup"]
279281
)

documentation/API.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Name Resolution API
2+
3+
The Name Resolution API is intended to provide an [Apache Solr](https://solr.apache.org/)-based interface to the
4+
[Babel](https://github.com/NCATSTranslator/Babel) cliques of equivalent identifiers.
5+
6+
largely consists of three endpoints: `/lookup` (to search for normalized concepts),
7+
`/bulk-lookup` (to search for multiple normalized concepts) and `/synonyms` (to look up for the synonyms for a normalized CURIE).
8+
9+
Unlike the Node Normalizer, the Name Resolution Service does not currently support on-the-fly conflation. Instead,
10+
all the [Babel conflations](https://github.com/NCATSTranslator/Babel/blob/master/docs/Conflation.md) are turned on
11+
when Solr database is built. This means that -- for example -- protein-encoding genes will include the synonyms found
12+
for the protein they encode, and that no separate entry will be available for those proteins.
13+
14+
## Search endpoints
15+
16+
### `/lookup`
17+
18+
### `/bulk-lookup`
19+
20+
### Scoring
21+
22+
Every `/lookup` or `/bulk-lookup` search result returns a search score. This score value is calculated by Apache Solr,
23+
and does not have an upper range. This score begins with the [TF-IDF](https://en.wikipedia.org/wiki/Tf%E2%80%93idf)
24+
(term frequency-inverse document frequency) score, which is a measure of how relevant a term is to a document in a
25+
collection of documents. The score is then multiplied by the [BM25](https://en.wikipedia.org/wiki/Okapi_BM25) score,
26+
which is a measure of how relevant a document is to a query.
27+
28+
29+
## Lookup endpoints
30+
31+
### `/synonyms`

documentation/Scoring.md

Whitespace-only changes.

0 commit comments

Comments
 (0)