small frontend adjustments for first integration

[ChristianGerloff]

• [x] add default start date
• [x] bug: search string was not updated
• [x] start with simple table to display results (rayya)
• [x] replace download component
• [x] reset limit
• [x] consider keys
• [x] provide Search obj as json download
• [x] provide option to insert plan search string directly ,e.g. [brain-to-brain] AND [hyperscanning]
• [x] avoid index of csv @kashyapm94
• [x] provide an option to remove last added chars of string @kashyapm94
• [x] provide an option to clean the search string @kashyapm94
• [x] currently no keys are used: results_as_df (set default to true) have to be created earlyer or within seach part @kashyapm94
• [x] discuss: remove search class
• [x] reduce deps
• [x] use multi-page structure

[kashyapm94]

@ChristianGerloff When you say remove last added chars of string, do you mean remove the last query string?

Example:

If a query string is: [hyperscanning] AND [fNIRS], then when the user clicks the button, fNIRS should be deleted and the final query string should be [hyperscanning]?

[ChristianGerloff]

Hey @kashyapm94, yes, exactly! thanks for clarifying that 😃

[kashyapm94]

@ChristianGerloff Assume that the user chose to insert plain search string directly,e.g. [brain-to-brain] AND [hyperscanning], and then want to delete it. In this case, we have a button that clears the entire string.

Should we also add the option to remove the last added chars of string for this case as mentioned in the comment above or is it only when the user builds the query string instead of entering it manually?

discuss: remove search class

For this task, it makes sense to delete the search module since we no longer need it. What do you think?