@Pepe_piton
Thank you for catching this! You're right, I accidentally removed the work_language line when I was adding the work_inception_date. I have just pushed the fix for it.
https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/151/diffs#ef1b805b6792d39c7fb9b97a0fbf54dc1e780410

In T407558#11314468, @Pepe_piton wrote:

@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).

@Oluwatumininu.m Thanks, very good contribution! I really liked the work you did giving priority to the autocomplete suggestions that are actually types of works.

@Afanyulionel You created a really beautiful form. As for the autocomplete, when I tried it, it didn't work. The response was a HTTP 403 error (forbidden) from the server. The REST API doesn't like the JavaScript request. If an authentication token is not used, it gives this error:

status: {"error":"rest-cross-origin-anon-write","httpCode":403,"httpReason":"Forbidden"}

It's strange because the Wikibase REST API responds successfully to the exact same request when Python requests module is used. My guess is that the problem is a bug in the REST API that, for whatever reason, is taking a read-only request for a write request. I opened a bug report in the REST API workboard: T408441

Meanwhile, I think it will be better to use the Action API.

@System625 I really like your solution! A very interesting feature is that the interface displays the Q ID of the chosen option.

One question: Is there a reason why you created the /api/autocomplete-work-type API proxy? Was it necessary to solve a particular problem? What advantages did you see over calling the Action API directly from JavaScript?

@Dipanshu1223 Good work! I like very much the visual appeal of the form and the way it is organized. I have a similar question to the one above: why did you find it necessary to create the API call proxy in /autocomplete/work-type ?
It's not that it's wrong. It's just that, given that several people have come up with a similar solution, I'm wondering about the benefits this approach might have.

@Raboyusuf2024 Thanks for your contribution! The form works very well. The only detail I see is that this task was meant to assess your understanding of the problem of how to make calls to the Wikidata API for autocompletion, which you didn't do. Anyway, your contribution made me realize that, specifically for the "type of work" field, it might be preferable to provide a predefined list of options, just as you did using the type of work filter options (very well thought out!). But for other fields, such as the work's author(s), it will be necessary to use an autocomplete feature by running Wikidata API calls, since it would be impossible to predefine a complete list of options.

@Olatundeawo Nice! Simple and straightforward.

@Nurah_Wakili Good work! You went one step further and put together a complete form! Autocomplete works very well. I also liked your solution for the image. Maybe for languages dropdown I would have populated it using a different approach, but it works well. As with other participants, I'd like to know the logic behind creating a local proxy for the API calls: /api/search-wikidata-items

@shreya-bhagat Very good! Your form is very well conceived and complete. I liked how you handled the image search. As for the autocomplete using the REST API, please read my previous comment to Afanyulionel.

@Adwivedii Excellent work! A super nice form, and I really loved the preview feature. Autocomplete works very well. The only strange thing I noticed was that keyboard navigation through the autocomplete options didn't work quite right for me. It's a minor detail, though. Congrats!

Good evening @Pepe_piton, @Nat_WDU and @DidiCoronel
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/154
Changes made:-
Updated pdclasses.py to fetch Wikimedia Commons link.
Updated app.py to pass commons link to the template.
Updated work.html to display Wikidata, Wikipedia, and Wikimedia Commons links.

Good evening @Pepe_piton and @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/151
changes made:-

• Added inception_date to pdclass.py
• Added work_inception_date to template in app.py
• showed inception date in work.html with fallback "Unknown"

Please check my work and share feedback so I can improve.

In T407385#11300929, @Pepe_piton wrote:

@Oluwatumininu.m @Dipanshu1223 @Nurah_Wakili Perfect!

@Chumzine Very good! And very nice that you added the link on the site menu. One detail: if you set the variable wikidata_link with Jinja directly on the template, you don't need to create and pass the same variable from app.py.

@Rolalove Perfect! Don't worry about the minor changes on the term.html page.

@Adwivedii Thanks for joining. Perfect work!

@Afanyulionel You forgot to create a view function for the new page in app.py. View functions are how you tell Flask to display the corresponding template for a given route. You can see examples for existing pages, such as /about in the app.py file itself.

In the next few days I will leave feedback to the rest of the contributions.

Good evening @Pepe_piton and @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/145
Changes made:-

• Added JavaScript to implement client-side pagination for search results.
• Displayed 10 items per page with dynamic previous/next and numbered page buttons.
• Styled pagination buttons using Bootstrap classes and custom CSS.

Please check my work and share feedback so I can improve.

In T405621#11299384, @DidiCoronel wrote:

@shreya-bhagat, @Aradhya05, @Dipanshu1223 code looks ok and I was able to see the new dropdown type-to-search behavior on your PRs.

hi @Pepe_piton
i made some changes:https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/50
changes made:

• add style dropdown
• add Ethnicity in selection

Good evening @Pepe_piton @Nat_WDU @DidiCoronel
i made a merge request related this issue:https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/136
changes made:

• Reused nationality JS.
• Added combobox-container CSS.
• Added submit validation.

Thanks for the feedback. @Pepe_piton
Thanks for the feedback!
I’ve addressed the two issues you pointed out:

• Added JavaScript to prefill the 'Country of origin' field on the Work Search page.
• Set the advanced search to display open by default.

Here’s the link to the updated changes: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/89
Please check my work and share feedback so I can improve.

hello, @Pepe_piton and @Nat_WDU
my attempt related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/50
Changes made:

• Added new template file add-author.html
• Created Flask route /add-author in app.py
• Added input fields for author details such as:
  1. Name
  2. Occupation
  3. Gender
  4. Place of birth
  5. Country of birth
  6. External links (Wikidata, Wikipedia, etc.)
• Added reset and submit buttons

hi @Pepe_piton and @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/118
Changes made:

• Added add-work.html page with form for creating works.
• Implemented autocomplete for Work Type field.
• Added form reset functionality.

Please kindly review, thank you!

hey @Pepe_piton @Nat_WDU
Thanks for feedback @Pepe_piton
i made some changes a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/82
changes made:-

• Added hover effect on cursor
• Added keyboard shortcuts: Enter to save and Escape to cancel
• Added a Cancel button
• Added validation: “Nationality cannot be empty” message

I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen

hi @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/93

hey @Nat_WDU ,
thanks for feedback
i forgot test other language
i made some changes related this issue::-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/66/diffs
Changes made:

• Added support for all interface languages (replaced hardcoded “en” with the user’s selected language).

hey @Pepe_piton @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/89
changes made:-

• Added JS to auto-select country value
• Displays matched country in input field
• Keeps selected option synced with dropdown

hey @Pepe_piton
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/82
changes made:-

• Added pencil icon next to field.
• Clicking the pencil replaces the text with an input box and a check icon.
• Clicking the check saves and restores the updated value.

I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen

hi @Pepe_piton,
I made some updates to improve handling of unknown values:https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/59-

hi @Nat_WDU
i made some changes related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/66
changes made:-
Added urllib.parse import and formatted Wikidata Query Service (WQS) link for better readability and transparency

• urllib.parse is a built-in standard Python library
• Used quote(query) to encode SPARQL queries into URL-safe format
• Added wqs_link variable to generate direct WQS link
• Passed wqs_link to templates for viewing the formatted SPARQL query on Wikidata

Hey @Nat_WDU,
I’m also working on the MR related to this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/75/diffs?resolved_conflicts=true
Some sudden changes in the main branch caused conflicts with all my MRs, so I got late in making this MR. Please take a look and give me some feedback.
It’s 12:32 AM here at Night , but I’d really appreciate it if you could review my work. I want to make sure I’m meeting expectations and understand any areas for improvement.

thanks for feedback @Nat_WDU
I try my best not make mistake again.

hi @Pepe_piton @Nat_WDU
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/66
changes made:-

• Added a Wikidata Query Service (WQS) link to each author's works list.
• Users can view the SPARQL query and reuse it.
• Tested locally — link works and page renders correctly.

I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen

hi
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/59
changes made

hi
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/56/diffs
changes made

• Updated squeries.py to fetch country flags using SPARQL (?flag).
• Modified term.html to show countries in a responsive grid with flag icons.
• Tested locally — grid renders correctly and is visually clearer.

The main changes were made to term.html and squeries.py. While checking the files, I made some changes and accidentally pushed unnecessary files in the merge request.
I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen

hello, @Pepe_piton
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/50
Changes made:

• Added a button and dropdown to show empty biography fields.
• Added JavaScript to display a text input when a dropdown option is selected.
• Only shows input for selected empty fields; existing rows are reused.
• Button only appears when there are empty fields; if all fields have values, it remains hidden.

hello, @Pepe_piton
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/33/diffs?commit_id=76eab43e749393767ccf01a582f37b7fa4439365
Changes made:

• Added JavaScript check to hide rows with empty values dynamically.
• Ensured template fields such as Nationality, Ethnicity, Occupation, and Date of Death are displayed only when data is available.
• Tested locally — the layout now renders cleanly without blank rows.

I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen

hello, @Pepe_piton
i made a merge request related this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/29
I'd appreciate it if you could take a look at my work and provide feedback. I want to make sure I'm meeting expectations and understand any areas for improvemen