Page MenuHomePhabricator

Improvements to the copyright term page: term description
Closed, ResolvedPublic

Assigned To
Authored By
Nat_WDU
Sep 25 2025, 2:22 PM
Referenced Files
Restricted File
Oct 13 2025, 2:44 PM
Restricted File
Oct 13 2025, 2:44 PM
F66745729: Screen Shot 2025-10-12 at 8.14.18 PM.png
Oct 12 2025, 7:14 PM
F66745726: Screen Shot 2025-10-12 at 8.13.42 PM.png
Oct 12 2025, 7:14 PM
F66698065: imagen.png
Sep 25 2025, 2:22 PM

Description

Context: Paulina includes a page that lists all countries with copyright term 50 years pma and another one for copyright term 70 years pma. There is no explanation of the concept.

Feature: Each page should your a description of the copyright term between the page title and the list of countries. This description is the wikidata item's descripition.

The styles for this paragraph should be analog to the paragraph at the Countries and terms page:

imagen.png (187×1 px, 23 KB)

Event Timeline

I would like to take this task. From what I understand, the goal is to display a short descriptive paragraph (sourced from the corresponding Wikidata item’s description) between the page title and the list of countries on the 50 years pma and 70 years pma pages.I’ll ensure the styles for this paragraph match the existing design used on the Countries and terms page

If this task is still available, I would like to be assigned to it.

Hi @Nat_WDU,
I have successfully set up Paulina locally and would love to work on task T405598 if it becomes available again.
I’ve already reviewed the implementation steps and can start right away.
Thank you!

Hi everyone! Welcome!
@Sandijigs I see you are already working on another task, so I'll assign this one to @Ronatone

@hnin_wutt_yi let's find another one for you, thanks for your patience!

@Pepe_piton @Nat_WDU I've completed this task and created a merge request. I updated the term.html layout to display each term’s respective copyright description. You can view it here: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/15. I would appreciate your feedback!


‎Hi @Nat_WDU @Pepe_piton

‎I have completed the microtask, tested locally, and it works as expected. Screenshots are included, and a Merge Request has been submitted for review and feedback.

‎Merge Request:
https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/37

Hi @Nat_WDU @Pepe_piton
I have fixed this issue.
Now each page shows a proper explanation of the term, pulled straight from the corresponding Wikidata item right under the page title. The style matches the paragraph on the Countries and Terms page for consistency
Here is the link to my merge request: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/64

Screen Shot 2025-10-12 at 8.13.42 PM.png (764×2 px, 145 KB)

Screen Shot 2025-10-12 at 8.14.18 PM.png (764×2 px, 146 KB)

Hello, dear applicants, I have some feedback for each:

@Ronatone
I like your idea of having a placeholder paragraph for when there is no description, but I think the chosen text may be confusing. I suggest we leave it blank.
I like your attention to detail as for capitalizing and adding a period to the sentence

@Lebogang
Could be improved by capitalizing and adding a period to the sentence to make it more grammatically correct.

@Oluwatumininu.m
As requested in the ticket description, we’d like to show the wikidata item’s description at the page

You are all welcome to fix your merge requests and ping me afterwards
Other applicants are welcome submit their own merge request

Thanks, everyone!

@Oluwatumininu.m
As requested in the ticket description, we’d like to show the wikidata item’s description at the page

Hi @Nat_WDU
I have corrected this. I just made a new commit here: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/64/commits

Kindly help check it out and review.
{F66747803}

{F66747802}
Thank you.

@Lebogang
Could be improved by capitalizing and adding a period to the sentence to make it more grammatically correct.

@Nat_WDU Thanks for the feedback. I have implemented the requested fix. Please review.

Merge Request: ‎https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/37

Here's some feedback on the latest fixes and MR's:

@Oluwatumininu.m you got it right, thanks!

@Lebogang and @Oluwatumininu.m As for the capitalization and punctuation, I think I'd favour a more general and simpler approach like this one. I'm just being picky here, your solutions are good! They're in fact more robust, since it would not add the punctuation if already present, but I think it's ok to assume Wikidata descriptions come without punctuation. Leaving this for further reference - but we don't expect you to find out everything about Wikidata's conventions on your own, fill free to ask when in doubt.

@shreya-bhagat good job! The MR is presenting some conflicts now, since I've updated the main branch. Would you please update your branch with the latest changes in main so as to fix the conclicts?

Thanks everyone! Improvements to your existing MRs are welcome, as are other applicants' MRs

Hello, dear applicants, I have some feedback for each:

@Ronatone
I like your idea of having a placeholder paragraph for when there is no description, but I think the chosen text may be confusing. I suggest we leave it blank.
I like your attention to detail as for capitalizing and adding a period to the sentence

@Lebogang
Could be improved by capitalizing and adding a period to the sentence to make it more grammatically correct.

@Oluwatumininu.m
As requested in the ticket description, we’d like to show the wikidata item’s description at the page

You are all welcome to fix your merge requests and ping me afterwards
Other applicants are welcome submit their own merge request

Thanks, everyone!

I attempted this task @Nat_WDU

I noticed I had some merge conflicts but I managed to resolve them.

https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/74

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

Hey @Nat_WDU,
I’m also working on the MR related to this issue:-https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/75
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.

Here's some feedback on the latest fixes and MR's:

@Oluwatumininu.m you got it right, thanks!

@Lebogang and @Oluwatumininu.m As for the capitalization and punctuation, I think I'd favour a more general and simpler approach like this one. I'm just being picky here, your solutions are good! They're in fact more robust, since it would not add the punctuation if already present, but I think it's ok to assume Wikidata descriptions come without punctuation. Leaving this for further reference - but we don't expect you to find out everything about Wikidata's conventions on your own, fill free to ask when in doubt.

@Nat_WDU thanks for the insightful feedback

The task has been updated based on your suggestions; MR: ‎https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/37

The simpler approach makes sense, the backend passes the data directly, keeping the logic clean and following Wikidata conventions. It's also easier to maintain and consistent with other contributions.

I was wondering if the Paulina project plans to keep this simple, template-based approach for all pages going forward, or if there might be cases where more complex formatting will be needed?

@Rolalove & @Lebogang
The implementation itself is ok but your MRs include a couple of changes that roll back T405603.

@shreya-bhagat
Thanks a lot! conflicts are solved now

@Dipanshu1223
Thanks for your dedication! Please take care of yourself and rest well 😀 I like that you made a point to add a few more instructions to the page
I think it’s not a good idea to do the capitalization of the string through Javascript. We can do this either in the backend (Python), or with the features that flask templates allow. I’d reserve JS for any changes that the user needs to see without re-loading the page. Am I explaining this point? Let me know if it makes sense to you.

@System625
simple and nice! Though I prefer implementations that add the ending period and capitalization - I understand this is not specified in the task description.

@Lebogang, as for your question… I’d say that anything that is simple enough to be formatted in the template, should be done in the template. And things that are more complex in terms of logic should be solved in Python. But I don’t think we can generalize, we have to look into it case by case. Tagging @DidiCoronel and @Pepe_piton in case they have more specific answers to this question

I’ll approve and merge one of the existing MR’s please don't work any further on this task. Thanks everyone!