In T406989#11287685, @Pepe_piton wrote:

@shreya-bhagat Great work! I like very much the that you gave special treatment to each type of input. You also used very well the CSS styles, and the flow is perfect on desktop devices. The only detail I would pay attention is that the responsive behavior could be improved a little (at least on my mobile, the Add information button grows downwards in a strange way).

Thanks for the feedback!
@Pepe_piton Fixed responsiveness: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/83

@Pepe_piton thanks for the feedback!
Needed some clarifications regarding my PR:

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.

1. Reading up on MediaWiki Manual CORS, I wonder if this is an intended behaviour? Because when browser JS (origin = user's browser) calls the API without a bearer token, it’s both cross-origin and unauthenticated. while using the same functionality in python module (origin: flask server), there’s no CORS layer at all — it’s a straight network request. while using bearer token with javascript, the request is still cross origin, but authenticated, hence wikidata allows it (I try and understand it in simpler terms: as if authentication with a bearer token overrides the CORS issue). Your thoughts on this?

@Nat_WDU I had submitted my MR link but found some responsiveness issues with it. fixing them and reattaching the MR asap!

@Pepe_piton @Nat_WDU apologies for the delay due to holiday weekend in India.

@Nat_WDU @Pepe_piton hello!
my attempt: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/117

@shreya-bhagat, now I do see the correct styles.

thanks @DidiCoronel for the feedback!

Hello @DidiCoronel!
I think just before pushing I made a mistake in the css file. I've fixed that now, have a look: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/90/diffs?diff_id=136659&start_sha=f7156e42826322923b25e9e1091c5a51585ba6e1

haha thanks @Miiswom.
Yes, exactly this! played around on the UI and tested all properties.

@Miiswom I faced this error too. If you look through any test.wikidata.org page, you will notice that the property IDs used for test instances are different from production.
So, while P31 refers to instance of in wikidata, for test.wikidata, the property ID for instance of is P82

https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/91
@Pepe_piton @Nat_WDU Kindly review the changes!

Completed the task, Kindly review!
Reused the existing javascript functionality of Nationality filter.

Completed the task, kindly review @Pepe_piton @Nat_WDU

Hello! @Pepe_piton @Nat_WDU
Completed the task: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/83

@Nat_WDU Rebased my PR to the latest main. Please review!

Thanks for the feedback @Nat_WDU

@Pepe_piton thanks for the feedback!

@Nat_WDU @Pepe_piton
Completed the task, kindly review!
https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/70

@Sandijigs I didn't see any PR linked to the phabricator ticket, and the task was still marked In Progress.

Completed the task! @Pepe_piton @Nat_WDU
Was a very good learning experience , created my own test wiki data pages and played around with them. Tried all API requests on the https://test.wikidata.org/w/rest.php/wikibase base URL.

got it. thanks for the help @Xinacod @Isaac!

Implemented the changes in the above PR
For displaying values of various fields, I employed a list of dicts (with field label and value) within the jinja template, iterating over them in a for loop. Skipping the ones where the value attribute of the dict is empty.

Hello @Pepe_piton !
I completed the task, kindly review the merge request:
https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/34

Hello @Isaac @SBisson @SEgt-WMF, other mentors and fellow contributors!
Shreya Bhagat here, an outreachy applicant. Found your project very interesting and have forked your ipynb file into my PAWS account.
I'm getting started with the first task, and need a few clarifications: The question is very open ended, there are a number of relevant articles on climate change - some are based on the recent current happenings, some are basic concepts, some describing past events, etc.

1. As we are aiming for a list of newcomers, should I only target pages that need minor changes?
2. Is it okay to think from a perspective of adding new information, fact checking, removing biased content etc.?
3. Do I link such articles to my answers?

@Nat_WDU @Pepe_piton kindly review!

@Oluwatumininu.m two observations:

1. Your changes are incomplete: just modifying the jinja template will always show "inception" field as "unknown", as you're not passing the value of "inception" field to the template.
2. All your changes are in a single merge request. Each change should be on a separate PR.

@Nat_WDU @Pepe_piton Completed this task, kindly review and merge:
Merge request: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/13
Preview of changes:

Thank you @Pepe_piton!

Here's the merge request! (gitlab account was just approved)

@Nat_WDU
I've completed the task. The screenshot is attached.
However, a few concerns:

1. My Gitlab account hasn't been approved by the Administrator, I'm unable to create a PR.
2. Property 172 often is a nil value for various authors. In those cases: do you want me show the ethnicity field as empty (analogous to how Date of Death shows up for authors who are alive), or do you want me to skip the field entirely?
3. Let me know the order of properties: I'm not so sure which position will be appropriate.

Hello!
FYI, working on this issue.

okay, sure!

@adiba_anjum I'd like to take this issue up! Kindly assign it to me.

Is this the correct implementation, please clarify if incorrect?

Would be interested in taking up this task if possible!

Interested in taking up the task! Kindly assign it to me if possible.