I merged @Aradhya05 's solution. Thank you!

Merged @Nurah_Wakili 's contribution. Thank you!!

I merged @Sopzy 's solution. Thanks!!

I merged @Chumzine 's solution. Thanks!

I merged @Chumzine solution. Thanks to everyone!

Done! Now, the advanced search details section is open by default in the "Results" page and the interface shows the selected filters (they are taken from the URL parameters). This is the commit: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/commit/6c8d39f402569a14f2d9b0a9c0283da5c36e6653

I merged @AnbaNguyen's contribution.

Merged @Dipanshu1223's solution. Thanks everyone for your work!

@Mind_Booster_Noori Thank you for your suggestion about this important feature, and @Oluwatumininu.m @System625 thank you for your contributions! Date of birth and date of death filters are something I've been considering for quite some time, but until now I haven't been able to implement it precisely for performance reasons. Since searches with "haswbstatement" using the Action API don't allow the "date" data type, we have to use SPARQL, which significantly impacts performance. Some weeks ago I left a comment on an old ticket about this, asking for the date data type to be added to haswbstatement: T238498

@Miiswom I liked very much your solution. It works super well in all the different cases. I also liked that you used existing styles for the elements like buttons. Congrats!

@Sopzy You did a great job implementing everything we asked for in a very straightforward way. Perhaps the only thing missing is the ability to exit editing without saving, but that''s something I didn't explicitly ask for.

@Afanyulionel @Sopzy Excellent work. You catched the logic of the task.

@Miiswom @Chumzine @Aradhya05 Good work!

@Miiswom Good work! The solution you implemented works very well, congrats! I noticed that you implemented the feature using an API proxy, and this gives me the opportunity to make a general comment:

@Rolalove Good work! Autocomplete works very well. I also liked the way you handled the styles of the autocomplete list! Just a couple of comments. Perhaps it would be better to search in the user's language, using the {{CURRENT_LANGUAGE}} variable instead of "en" in the API call. E. g.: &language={{ CURRENT_LANGUAGE }}&uselang={{ CURRENT_LANGUAGE }}
The other caveat is something I perhaps explained poorly in the instructions: the important thing isn't that the search be restricted to items with P 31, but that they be common P 31 values. For example, literary work (Q7725634) is a type of value that would need to be searched for (it doesn't have P 31 but is a common P 31 value for other items).

@System625 Perfect! And thanks for detecting and coding a fix for the JavaScript errors!

@Oluwatumininu.m @Dipanshu1223 @Nurah_Wakili Perfect!

@Aradhya05 Nice work! It works really well. I also liked that you used code like request.args.get('nationality', country_qid) so that, when the URL parameters for countries are present, it also prefills the country filters. Actually, Paulina still needs some polish to make all the search filters persistent, and this can be a good approach.

@Oluwatumininu.m Good work! The feature works well. The only minor detail is that when the user switches between Author and Work, the country dropdowns have different styles (one with yellow background and the other with white background). As for app.py, the two new variables you created are interchangeable with each other.

@Joyakinyi Thanks for your contribution! I like your minimalist, clear and simple approach to solve the task. The code is super easy to read. Just a couple of details: the field "Ethnicity" is missing in the dropdown; and it's a bit strange that when all values are complete, the dropdown is shown (although without options).

@Oluwatumininu.m Great work, I really like your solution! It works just as expected. I like that you also included code to hide the button when all fields are complete. Congrats!

@Ritika-Bhambri11 I like very much your approach, and I also like that you added the cancel button and the "Esc" key cancel action. It works well and the code is pretty straightforward. Congrats!

@shreya-bhagat Thanks for your contribution! You've solved the problem very well using a strategy similar to the one you used in T406909. I think you're taking full advantage of the Jinja template engine's capabilities.

Excellent @Kimondorose! Your solution works well and you understood the logic. Anyway, you might be interested in reading the comment I left for @Lebogang , since there are slightly simpler conditional solutions for adding the vertical bar separator in the template.

@Oluwatumininu.m Thanks for your contribution! You managed to place the Wikidata link very well. However, with your current solution, the Wikimedia Commons link isn't displayed. This is because the work.html template doesn't receive a variable named "work_commons_link." For a clue on how to resolve this issue, it might be helpful to revisit the task of adding the "inception" field to the work page: T406949

@Oluwatumininu.m Thanks for your contribution! I think there are some changes from other tasks included in the MR diff and the commit diff, but I was easy to identify the changes corresponding to this task, so don't worry. You did a good job, finally identifying the necessary changes to the Work class in pdclasses.py, the work route in app.py, and the template. I tried your code and it works fine.

@Oluwatumininu.m, Thanks for your contribution. You catched the essence of the task: adding if statements with Jinja2 in the author.html page. Simple and readable. Congrats!

Excellent work, @AnbaNguyen I tried your code and it works perfect. It was a clever strategy to create the parameter 'prefill_country_qid'!

@Sopzy Hi! Good questions.

Hi @Prithika2804 ! This task is not for the Outreachy process, since it's not related with the specific goal of the Outreachy project. Please choose a task from this list of Outreachy tasks: T392429

Don't worry if you enter a task from the list and you see it says it's assigned to someone else. From now on, all tasks from the list will remain open for all contributors to work on. Anyone can choose the tasks they like best and submit their contribution to that task. You can simply complete the task, submit the merge request, and let the mentors know you did by leaving a comment on the Phabricator task. In summary, from now on, it's okay if more than one person does a task.

Excellent job, @Nurah_Wakili! I tried it with and without Javascript and it works perfectly!

Excellent job, @shreya-bhagat! I think you've got a good understanding of how the tool works, from how the "Author" class is built, to how Flask sends data to the HTML template, and how that data is displayed in the template.

@AnbaNguyen I've assigned this task to you, since Sandijigs has already other task assigned. Thanks!

Sure @OlusegunFaj. I assigned it to you. Go ahead. Thanks!

I assigned this task to @Oreoluwa.

Great, Nurah, it has been assigned to you.

Great, @Sandijigs the task is assigned to you.