-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NarrativeRecommender: Integration into the Narrative Service (Recommender functionality) #285
Comments
…w of queried document; fixed filter error; added "show_similiar_articles" button
First prototype has been implemented. Textual similiarity is diabled for now. |
The similar articles function for COVID 19 pre-prints does not work. I assume that the "/" within the DOI causes problems, e.g., |
Seems to work quite good. However, we cannot take it live right now. We should hide the recommender tab / and similar articles link in the document representation. Code can stay. |
We need to rework the loading animation. At the moment, there is little feedback that a search is conducted. Maybe we should clear the result list before starting the recommendation so that the user receives and immediate feedback. We decided for a complete web page locking. |
We should also add logging (so write requested recommendation to a special log directory).
|
Implemented and ready. UI elements are hidden at the moment. |
We want to integrate our Narrative Recommender (graph-based recommendation) into our Narrative Service. However, the recommender relies on BM25 scores. Before we can start the integration, we need to discuss how we can compare the texts of documents. Maintaining another index for textual document content will come at high costs - so what are our alternatives?
If there is a way to do it in-memory, this could be the best way to go. The recommender has the following structure at the moment.
We could reduce the number of documents retrieved by the first stage to a few hundreds. Comparison of texts should then be very fast.
The text was updated successfully, but these errors were encountered: