Skip to content
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

Search history for CorpSum #51

Open
clamatte opened this issue Feb 1, 2024 · 3 comments
Open

Search history for CorpSum #51

clamatte opened this issue Feb 1, 2024 · 3 comments
Labels
API requires work on the interaction with NoSke documentation Improvements or additions to documentation enhancement New feature or request

Comments

@clamatte
Copy link

clamatte commented Feb 1, 2024

I was testing CorpSum, trying to figure out some different CQL-queries (especially with the simulatenous search terms), and the question arose if there was a plan to add/have a search history similar to the one in the NoSke dashboard (the search history has proven useful to my searches in the past, it's a feature of NoSke I make use of a lot)

@ctot-nondef ctot-nondef added the enhancement New feature or request label Feb 5, 2024
@ctot-nondef
Copy link
Member

thank you for the feedback - I added it to the enhancement list

@hpreki
Copy link
Contributor

hpreki commented Feb 19, 2024

search history is stored on the server - and is automatically retrieved and displayed (on the NoSke dashboard) at login with get_user_options :

json: {"options":["user_data_global","user_data_corpora","user_data_pages_favourites","user_data_pages_history","user_data_cqls","user_data_other"]}

"user_data_cqls"ist vermutlich der relevante Parameter <- fraglich! liefert kein Ergebnis

Important

Search histories are not automatically stored on the server. In the NoSke-GUI for each concordance-call an explicit set_user_options POST is issued for actually updating the user-options on the server (where they are stored as json under bonito/options/<username> )
set_user_options and get_user_options are not documented and have to be "reverse engineered" from the NoSke-GUI

@ctot-nondef ctot-nondef added the API requires work on the interaction with NoSke label Mar 5, 2024
@ctot-nondef
Copy link
Member

if search history was properly implemented in corpsum, it would also enhance the subcorpus creation, as it would not be necessary to post document Ids anymore

@ctot-nondef ctot-nondef added the documentation Improvements or additions to documentation label Mar 5, 2024
@ctot-nondef ctot-nondef changed the title Search history for CorpSum? Search history for CorpSum Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API requires work on the interaction with NoSke documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants