Datasets:

ontocord

/

CulturaP

like 0

en

The legal department of the Wikimedia Foundation runs a year-round internship program for law students and recent law graduates. Between three and five positions are available every spring and fall semester and over the summer. The interns assist the Foundation’s six attorneys and get a chance to experience the workings of an in-house legal department at a non-profit, user-driven Internet company whose projects like Wikipedia are visited by 500 million people, making them the fifth-most popular web property world-wide. The program was started in 2011, and to date, there have been 27 interns. Ranging from first year law students to recent graduates, interns have hailed from the following schools: Berkeley, Columbia, the University of Colorado, Cornell, Georgetown, Harvard, Hastings, Michigan State, the University of Minnesota, Santa Clara, Stanford, and Vanderbilt. As of this year, the program is also becoming more international. This fall, the program will have its first intern from the Universidad de los Andes in Bogotá, Colombia, and the author of this blog post comes from Bucerius Law School in Hamburg, Germany. The current interns with Rory, the legal mascot. The Wikimedia legal department handles complex legal situations that touch on a broad range of topics, and the interns support this effort: We work on dozens of different projects, from small drafting assignments to extensive research memos. In tackling these projects, we gain experience in a wide variety of legal practice areas, such as copyright and trademark law, privacy, non-profit governance and public advocacy. We work with copyright and trademark law, privacy, foundation governance and public advocacy. The community aspect of the Wikimedia Foundation adds another layer of complexity to our legal projects — the Wikimedia community and movement values must be taken into account and prioritized in finding any legal solution to an issue. In a typical week, an intern could deal with U.S. federal tax law, Kenyan data protection law, Indian copyright, Indonesian trademark registration and the Florida law on corporations. In a time when governmental actions like the Stop Online Piracy Act (SOPA) or the U.S. National Security Agency’s PRISM scandal threaten the Wikimedia projects and the free knowledge movement, we also help the Foundation navigate current political issues and we assist in executing the courses of action that are supported by the volunteer Wikimedia community. And our work yields visible results. Many postings on the Wikilegal database – while not legal advice – are created with the help of preliminary intern research. For an example, see the memo on “Flags and logos from international organizations”, originally prepared as preliminary thoughts for community input by a Berkeley Law student (now alumnus) during his 2L internship in the spring of 2012. Recently, we interns invited our counterparts from tech companies and like-minded organizations in the San Francisco Bay Area to the Wikimedia office, hosting an expert panel on “Law, Tech and Social Change”. What’s more, one of the Foundation’s current lawyers, Stephen LaPorte, was a former intern and is a Wikimedian. On a personal note, one of the best things about this internship is that I know that I am ‘on the good side.’ My coworkers and I work to defend and expand freedom of expression and we help provide access to free knowledge for the entire planet. And all that with the support of thousands of volunteers from all around the globe. If you would like to know more about the legal intern program at the Wikimedia Foundation, you can read about the current open positions, or you can contact the Wikimedia Foundation legal internship program coordinator Michelle Paulson for more information. Lukas Mezger, Legal Intern, Wikimedia Foundation Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. I am a graduate from the university of community of community health .I study in Economics in post graduated course. I interested in economics reforms in my country.So that Please would you like give me some economics books (currency policy, economics policy, management and strategy,Technical support of applied economics , )and also guide me some website. Posted in LegalTagged multilingual post, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/09/16/wikimedia-legal-intern-program/

cc40

The legal department of the Wikimedia Foundation runs a year-round internship program for law students and recent law graduates. Between three and five positions are available every spring and fall se

en

During her last year of high school, Anne Kingsley took a variety of classes at Sierra College, her local community college in Rocklin, CA. The experience greatly influenced her decision to pursue a career in teaching. “I loved the atmosphere of the community college and remember spending a lot of time printing out articles and copying books in the library,” Anne recalled. “I remember study groups with recent high school grads, returning students, veterans, single moms.” The eclectic nature of the community college served her well in her first teaching position in 2002 at a New York organization called Friends of Island Academy (FOIA), where she helped youth in the criminal justice system gain literacy and other basic skills. At that time, the Internet was starting to become a valuable educational resource that would soon make photocopying books in the library a nostalgic pastime. Her time at FOIA was the beginning for discovering innovative ways to solve big educational problems. “Because I had to run a classroom that had very little materials and almost no budget, you had to be creative about content and curriculum design,” explained Kingsley. “This was a powerful experience to build a foundation for classroom experience as it taught me how to think outside of conventional teaching practices.” Anne went on to teach at Northeastern University, Menlo College and Santa Clara University. While at Northeastern she pursued her doctorate and was part of a training program where the faculty encouraged curriculums that incorporated new media into the classroom. “This was the beginning of blogs and Facebook, so I remember experimenting with these kinds of shared information sources,” said Anne. At the same time Wikipedia, only a few years old at the time, was becoming an increasingly comprehensive encyclopedia. Though in its onset Wikipedia had a reputation for being discouraged by teaching professionals, it has since slowly garnered support and trust from a number of institutions. Today Anne teaches at Diablo Valley College in Pleasant Hill, California, and finds herself once again experimenting with different teaching methods, including the use of Wikipedia. Tired of assigning the standard research paper and disillusioned by its merits in the 21st century, Anne started to realize that technology has greatly altered the way we access information. Anne elaborates, “I kept thinking that technology has changed the place for research, so why do we keep handing in these static articles as though information doesn’t shift and change all the time. I also knew that old research papers that I had assigned my students were literally piled up in my closet, shoved into boxes, and forgotten about.” Simultaneously, Anne kept hearing about underrepresented histories on Wikipedia – from women’s literature to African American history. Though underrepresentation of marginalized subjects is still a concern on Wikipedia, much is being done to address it thanks to people like Anne. “Given that I was teaching at a community college, I figured, let’s see what my students could do with Wikipedia. We all use Wikipedia, so why not see if we could become producers of information rather than just consumers.” As a Harlem Renaissance enthusiast, Anne taught a course titled “Critical thinking: Composition and Literature Reading the Harlem Renaissance.” It was during this course that she experimented with her idea of producing information in a public forum as a method of learning. Part of the course was to edit articles pertaining to the Harlem Renaissance that were not covered fully on Wikipedia. Using online publications like The Crisis Magazine — an important early 20th century publication for African American culture — the students set out on a journey to research, edit and contribute to the world’s largest encyclopedia. Humanities Building Classroom at DVC. Anne and her students soon became aware of the initial learning gap that many new editors face with regards to the Wikipedia syntax. Though somewhat intimidating at first, Anne agrees that editing Wikipedia was a great way to teach students how to become literate in new media language. Her students weren’t the only ones learning something new, Anne explains, “It certainly opened their (and my) eyes to what takes place behind the nicely edited entries.” Another obstacle was trying to figure out how and where to contribute. Anne recalls a student who was hoping to contribute a “religion” entry to the Harlem Renaissance page. The challenge was to figure out where it belonged and how they would go about incorporating it into an existing page in a cohesive manner. Despite a period of adjustment, Anne makes it clear that the benefits her and the students garnered greatly outnumber any difficulties they might initially have had. From an academic perspective, the assignment captured many of the elements of research that the course aimed to teach – understanding of source material, citation, scholarly research and careful language craft. The fact that Wikipedia is a public forum motivated the students in a manner that perhaps a normal research paper wouldn’t, that is to say, it no longer was just the professor who read the work but also other editors from around the world. The project also proved to be a great collaboration process between the students and the professor. The project lent itself to broader collaboration, especially when it came to the selection process and some of the smaller nuances of contributing to Wikipedia. The project also seemed to greatly improve composition, says Anne, “They (the students) would literally groom their language sentence by sentence – as opposed to earlier experiences writing seven-page research papers where the language fell apart.” Perhaps most satisfying for the students was the sense of accomplishment in seeing their hard work in a public space. Among the new articles created were pages for Arthur P. Davis, a section for religion in the Harlem Renaissance article and a page for Georgia Douglas Johnson – formerly a stub. Anne expresses great interest in assigning this project again to her students. “I don’t always get to select the classes I teach, but if I had the opportunity to teach the Harlem Renaissance again, I would repeat this curriculum.” When asked what she would do differently, if anything, she replied, “More time. I only gave my students four weeks to create their entries. I did not realize how many of them would choose to create full-length articles or more complex entries.” Anne is part of a growing number of teaching professionals who choose to think outside the box and embrace new mediums in an effort to not only contribute to the greater good, but also prepare their students for a 21st century academic landscape. She had a clear message to her colleagues who perhaps might not be as embracing of Wikipedia in the classroom, she says, “Think big…students have this amazing capacity to want to experiment with you and others, especially when it makes their work visible and meaningful.” Carlos Monterrey, Communications Associate at the Wikimedia Foundation Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Love this. There are so many benefits to learning like this, including: – Students given the autonomy to choose their projects are more motivated. – Students get to develop multidisciplinary skills (a more real-world situation). – Students can feel like they are contributing to something meaningful (again, a big motivator). – Teachers can feel like they are contributing to something meaningful. I can’t think of a better way to teach modern research in the classroom. These days, teachers when give a research assignment to students, they also ask them that it should be a research and not just a copy past from Wikipedia. 🙂 Today I learned on Wikipedia that Diablo Valley College is known for a six-year-long scheme where students traded sex and money for falsified grades in the registrar’s computer system. I also caught a BLP violation in the Wikipedia article about the college. Excellent “teachable moment”, right, Professor Kingsley? Greg, it’s unclear what that 2007 incident has to do with Anne Kingsley’s Harlem Renaissance project. Please note that we reserve the right to put commenters on moderation, in particular if they have already been banned on Wikipedia by the Wikipedia community. Posted in CommunityTagged Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/08/18/wikipedia-in-the-classroom-empowering-students-in-the-digital-age/

cc40

During her last year of high school, Anne Kingsley took a variety of classes at Sierra College, her local community college in Rocklin, CA. The experience greatly influenced her decision to pursue a c

en

The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action Document Type : Review Article Irwin Rose Alencar de Menezes 8 Henrique Douglas Melo Coutinho 9 José Galberto Martins Costa 10 1 Department of Biological Sciences, Faculty of Science, University of Kurdistan, Sanandaj, Iran 2 Nanobiotechnology Laboratory, Department of Biology, Razi University, Kermanshah, Iran 3 Nanobiotechnology Laboratory, Department of Biotechnology, SGB Amravati University, Amravati-444 602, Maharashtra, India 4 Department of Microbiology, Nicolaus Copernicus University, 87-100 Toruń, Poland 5 Department of Pharmacy, Faculty of Sciences, Universidad Nacional de Colombia, South America, Colombia 6 Nanobiotechnology Department, Faculty of Innovative Science and Technology, Razi University, Kermanshah, Iran 7 Department of Pharmacy, Abdul Wali Khan University Mardan, Khyber-Pakhtunkhwa, Pakistan 8 Laboratory of Pharmacology and Molecular Chemistry; Department of Biological Chemistry; Regional University of Cariri; Rua Coronel Antônio Luis 1161, Pimenta, CEP 63105-000, Crato, Ceará, Brazil 9 Laboratory of Microbiology and Molecular Biology; Department of Biological Chemistry; Regional University of Cariri; Rua Coronel Antônio Luis 1161, Pimenta, CEP 63105-000, Crato, Ceará, Brazil 10 Research Laboratory of Natural Products, Department of Biological Chemistry, Regional University of Cariri, Crato, CE 63105-000, Brazil The applications of nanoparticles in various practical fields, owing to their unique properties compared with bulk materials, have been occupying the minds of scientists for several decades. In this regard, a combination of pharmacology and nanotechnology has contributed to producing newer effective anticancer and antimicrobial agents to inactivate resistant cancer cells and microorganisms, specifically multidrug-resistant ones. The physicochemical properties of nanoparticles based on metalloid, metal, and metal oxides such as selenium, silver, gold, titanium dioxide, zinc oxide, copper oxide, platinum, and magnesium oxide, have been well known and referred to as anticancer and antimicrobial agents or carriers. The inactivation and eradication of Gram-positive and Gram-negative bacteria may be mainly resulted from the oxidative damages in the bacterial medium. Overall, metalloid, metal and metal oxide NPs can be functionalized by other antibacterial or anticancer agents and biocompatible stabilizers to increase their efficiency in physiological conditions. However, the undesirable cytotoxicity of these nanoparticles in physiological conditions is the major hindrance to their application in the pharmaceutical industry and therapeutics. Nevertheless, it is expected that these problems will be solved in the near future. Therefore, the main objective of this review is to report an overview of the recent signs of progress in increasing anticancer and antibacterial mechanisms of metal and metal-based nanoparticles. Selected author of this article by journal Kurdistan University of Medical Sciences Universidad Nacional de Colombia Abdul Wali Khan University Mardan ِDr. Irwin Rose Alencar de Menezes Universidade Regional do Cariri ِDr. Jose Galberto Martins da Costa Universidade Regional do Cariri This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Abbas-Al-Khafaji ZK, Aubais-aljelehawy Qh (2021) Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital. Cellular, Molecular and Biomedical Reports 1(2):60-68 Aubais aljelehawy Qh, Hadi Alshaibah LH, Abbas Al- Khafaji ZK (2021) Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital. Cellular, Molecular and Biomedical Reports 1(2):78-87 Rahbar-Karbasdehi E, Rahbar-Karbasdehi F (2021) Clinical challenges of stress cardiomyopathy during coronavirus 2019 epidemic. Cellular, Molecular and Biomedical Reports 1(2):88-90 Fazeli-Nasab B, Sayyed RZ, Sobhanizadeh A (2021) In Silico Molecular Docking Analysis of a-Pinene: An Antioxidant and Anticancer Drug Obtained from Myrtus communis. Int J Cancer Manag 14(2):e89116. doi:https://doi.org/10.5812/ijcm.89116 Alavi M, Asare-Addo K, Nokhodchi A (2020) Lectin Protein as a Promising Component to Functionalize Micelles, Liposomes and Lipid NPs against Coronavirus. Biomedicines 8(12). doi:https://doi.org/10.3390/biomedicines8120580 Basavegowda N, Baek K-H (2021) Multimetallic Nanoparticles as Alternative Antimicrobial Agents: Challenges and Perspectives. Molecules 26(4):912 Alavi M, Adulrahman NA, Haleem AA, Al-Râwanduzi ADH, Khusro A, Abdelgawad MA, Ghoneim MM, Batiha GE-S, Kahrizi D, Martinez F, Koirala N (2022) Nanoformulations of curcumin and quercetin with silver nanoparticles for inactivation of bacteria. Cellular and Molecular Biology 67(5):151-156. doi:https://doi.org/10.14715/cmb/2021.67.5.21 Fazeli-Nasab B (2021) In Silico Analysis of the Effect of Scrophularia striata Linalool on VacA Protein of Helicobacter Pylori. scientific journal of ilam university of medical sciences 29(1):50-64 Ahmed SF, Mofijur M, Rafa N, Chowdhury AT, Chowdhury S, Nahrin M, Islam ABMS, Ong HC (2022) Green approaches in synthesising nanomaterials for environmental nanobioremediation: Technological advancements, applications, benefits and challenges. Environmental Research 204:111967. doi:https://doi.org/10.1016/j.envres.2021.111967 Niculescu A-G, Chircov C, Grumezescu AM (2022) Magnetite nanoparticles: Synthesis methods – A comparative review. Methods 199:16-27. doi:https://doi.org/10.1016/j.ymeth.2021.04.018 Qi Y, Yu Z, Hu K, Wang D, Zhou T, Rao W (2022) Rigid Metal/ Liquid Metal Nanoparticles: Synthesis and Application for Locally Ablative Therapy. Nanomedicine: Nanotechnology, Biology and Medicine):102535. doi:https://doi.org/10.1016/j.nano.2022.102535 Alavi M, Kennedy JF (2021) Recent advances of fabricated and modified Ag, Cu, CuO and ZnO nanoparticles by herbal secondary metabolites, cellulose and pectin polymers for antimicrobial applications. Cellulose 28(6):3297-3310. doi:https://doi.org/10.1007/s10570-021-03746-5 Taran M, Rad M, Alavi M (2016) Biological synthesis of copper nanoparticles by using Halomonas elongata IBRC-M 10214. Industria Textila 67(5):351-356 Alavi M, Karimi N (2020) Hemoglobin self-assembly and antibacterial activities of bio-modified Ag-MgO nanocomposites by different concentrations of Artemisia haussknechtii and Protoparmeliopsis muralis extracts. International Journal of Biological Macromolecules 152:1174-1185. doi:https://doi.org/10.1016/j.ijbiomac.2019.10.207 Alavi M (2022) Bacteria and fungi as major bio-sources to fabricate silver nanoparticles with antibacterial activities. Expert Review of Anti-infective Therapy):1-10. doi:https://doi.org/10.1080/14787210.2022.2045194 Taran M, Monazah A, Alavi M (2017) Using petrochemical wastewater for synthesis of cruxrhodopsin as an energy capturing nanoparticle by Haloarcula sp. IRU1. Progress in Biological Sciences 6(2):151-157. doi:https://doi.org/10.22059/PBS.2016.590017 Alavi M, Rai M (2020) Topical delivery of growth factors and metal/metal oxide nanoparticles to infected wounds by polymeric nanoparticles: an overview. Expert Review of Anti-infective Therapy 18(10):1021-1032. doi:https://doi.org/10.1080/14787210.2020.1782740 Ismail M, Khan MI, Khan SA, Qayum M, Khan MA, Anwar Y, Akhtar K, Asiri AM, Khan SB (2018) Green synthesis of antibacterial bimetallic Ag–Cu nanoparticles for catalytic reduction of persistent organic pollutants. Journal of Materials Science: Materials in Electronics 29(24):20840-20855. doi:https://doi.org/10.1007/s10854-018-0227-2 Alavi M, Rai M (2021) Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports 1(2):52-59 Díez-Pascual AM (2020) Recent Progress in Antimicrobial Nanomaterials. Nanomaterials 10(11):2315 Alavi M, Rai M (2021) Chapter 11 - Antibacterial and wound healing activities of micro/nanocarriers based on carboxymethyl and quaternized chitosan derivatives. In: Rai M, dos Santos CA (eds) Biopolymer-Based Nano Films. Elsevier, pp 191-201. doi:https://doi.org/10.1016/B978-0-12-823381-8.00009-0 Alavi M, Nokhodchi A (2022) Micro- and nanoformulations of paclitaxel based on micelles, liposomes, cubosomes, and lipid nanoparticles: Recent advances and challenges. Drug Discovery Today 27(2):576-584. doi:https://doi.org/10.1016/j.drudis.2021.10.007 Alavi M, Webster TJ (2021) Recent progress and challenges for polymeric microsphere compared to nanosphere drug release systems: Is there a real difference? Bioorganic & Medicinal Chemistry 33:116028. doi:https://doi.org/10.1016/j.bmc.2021.116028 Aygun A, Gulbagca F, Altuner EE, Bekmezci M, Gur T, Karimi-Maleh H, Karimi F, Vasseghian Y, Sen F (2022) Highly active PdPt bimetallic nanoparticles synthesized by one-step bioreduction method: Characterizations, anticancer, antibacterial activities and evaluation of their catalytic effect for hydrogen generation. International Journal of Hydrogen Energy). doi:https://doi.org/10.1016/j.ijhydene.2021.12.144 Alavi M, Varma RS (2020) Overview of novel strategies for the delivery of anthracyclines to cancer cells by liposomal and polymeric nanoformulations. International Journal of Biological Macromolecules 164:2197-2203. doi:https://doi.org/10.1016/j.ijbiomac.2020.07.274 Chen S, Sang N (2016) Hypoxia-Inducible Factor-1: A Critical Player in the Survival Strategy of Stressed Cells. J Cell Biochem 117(2):267-278. doi:https://doi.org/10.1002/jcb.25283 Ruan T, Liu W, Tao K, Wu C (2020) A Review of Research Progress in Multidrug-Resistance Mechanisms in Gastric Cancer. Onco Targets Ther 13:1797-1807. doi:https://doi.org/10.2147/OTT.S239336 Alavi M, Webster TJ (2020) Nano liposomal and cubosomal formulations with platinum-based anticancer agents: therapeutic advances and challenges. Nanomedicine 15(24):2399-2410. doi:https://doi.org/10.2217/nnm-2020-0199 Zhan H, Zhou X, Cao Y, Jagtiani T, Chang T-L, Liang JF (2017) Anti-cancer activity of camptothecin nanocrystals decorated by silver nanoparticles. Journal of Materials Chemistry B 5(14):2692-2701. doi:https://doi.org/10.1039/C7TB00134G Elbaz NM, Ziko L, Siam R, Mamdouh W (2016) Core-Shell Silver/Polymeric Nanoparticles-Based Combinatorial Therapy against Breast Cancer In-vitro. Scientific Reports 6(1):30729. doi:https://doi.org/10.1038/srep30729 Sengupta M, Pal R, Nath A, Chakraborty B, Singh LM, Das B, Ghosh SK (2018) Anticancer efficacy of noble metal nanoparticles relies on reprogramming tumor-associated macrophages through redox pathways and pro-inflammatory cytokine cascades. Cellular & Molecular Immunology 15(12):1088-1090. doi:https://doi.org/10.1038/s41423-018-0046-7 Ratan ZA, Haidere MF, Nurunnabi M, Shahriar SM, Ahammad AJS, Shim YY, Reaney MJT, Cho JY (2020) Green Chemistry Synthesis of Silver Nanoparticles and Their Potential Anticancer Effects. Cancers 12(4). doi:https://doi.org/10.3390/cancers12040855 Menon S, Ks SD, R S, S R, S VK (2018) Selenium nanoparticles: A potent chemotherapeutic agent and an elucidation of its mechanism. Colloids and Surfaces B: Biointerfaces 170:280-292. doi:https://doi.org/10.1016/j.colsurfb.2018.06.006 Ma J, Li K, Gu S (2022) Selective strategies for antibacterial regulation of nanomaterials. RSC Advances 12(8):4852-4864. doi:https://doi.org/10.1039/D1RA08996J Alabresm A, Chandler SL, Benicewicz BC, Decho AW (2021) Nanotargeting of Resistant Infections with a Special Emphasis on the Biofilm Landscape. Bioconjugate Chemistry 32(8):1411-1430. doi:https://doi.org/10.1021/acs.bioconjchem.1c00116 Shah S, Barton G, Fischer A (2015) Pharmacokinetic considerations and dosing strategies of antibiotics in the critically ill patient. J Intensive Care Soc 16(2):147-153. doi:https://doi.org/10.1177/1751143714564816 Alavi M, Karimi N (2022) Antibacterial, hemoglobin/albumin-interaction, and molecular docking properties of phytogenic AgNPs functionalized by three antibiotics of penicillin, amoxicillin, and tetracycline. Microbial Pathogenesis 164:105427. doi:https://doi.org/10.1016/j.micpath.2022.105427 Payne JN, Waghwani HK, Connor MG, Hamilton W, Tockstein S, Moolani H, Chavda F, Badwaik V, Lawrenz MB, Dakshinamurthy R (2016) Novel Synthesis of Kanamycin Conjugated Gold Nanoparticles with Potent Antibacterial Activity. Frontiers in microbiology 7:607-607. doi:https://doi.org/10.3389/fmicb.2016.00607 Deng H, McShan D, Zhang Y, Sinha SS, Arslan Z, Ray PC, Yu H (2016) Mechanistic Study of the Synergistic Antibacterial Activity of Combined Silver Nanoparticles and Common Antibiotics. Environ Sci Technol 50(16):8840-8848. doi:https://doi.org/10.1021/acs.est.6b00998 Mu H, Tang J, Liu Q, Sun C, Wang T, Duan J (2016) Potent Antibacterial Nanoparticles against Biofilm and Intracellular Bacteria. Scientific Reports 6(1):18877. doi:https://doi.org/10.1038/srep18877 Ahmed B, Ameen F, Rizvi A, Ali K, Sonbol H, Zaidi A, Khan MS, Musarrat J (2020) Destruction of Cell Topography, Morphology, Membrane, Inhibition of Respiration, Biofilm Formation, and Bioactive Molecule Production by Nanoparticles of Ag, ZnO, CuO, TiO2, and Al2O3 toward Beneficial Soil Bacteria. ACS Omega 5(14):7861-7876. doi:https://doi.org/10.1021/acsomega.9b04084 Rosli NA, Teow YH, Mahmoudi E (2021) Current approaches for the exploration of antimicrobial activities of nanoparticles. Sci Technol Adv Mater 22(1):885-907. doi:https://doi.org/10.1080/14686996.2021.1978801 Lunardi CN, Gomes AJ, Rocha FS, De Tommaso J, Patience GS (2021) Experimental methods in chemical engineering: Zeta potential. The Canadian Journal of Chemical Engineering 99(3):627-639. doi:https://doi.org/10.1002/cjce.23914 Kumar A, Dixit CK (2017) 3 - Methods for characterization of nanoparticles. In: Nimesh S, Chandra R, Gupta N (eds) Advances in Nanomedicine for the Delivery of Therapeutic Nucleic Acids. Woodhead Publishing, pp 43-58. doi:https://doi.org/10.1016/B978-0-08-100557-6.00003-1 Chaudhari KR, Ukawala M, Manjappa AS, Kumar A, Mundada PK, Mishra AK, Mathur R, Mönkkönen J, Murthy RSR (2012) Opsonization, Biodistribution, Cellular Uptake and Apoptosis Study of PEGylated PBCA Nanoparticle as Potential Drug Delivery Carrier. Pharmaceutical Research 29(1):53-68. doi:https://doi.org/10.1007/s11095-011-0510-x Goel S, Ferreira CA, Dogra P, Yu B, Kutyreff CJ, Siamof CM, Engle JW, Barnhart TE, Cristini V, Wang Z, Cai W (2019) Size-Optimized Ultrasmall Porous Silica Nanoparticles Depict Vasculature-Based Differential Targeting in Triple Negative Breast Cancer. Small 15(46):1903747. doi:https://doi.org/10.1002/smll.201903747 Spagnoletti FN, Kronberg F, Spedalieri C, Munarriz E, Giacometti R (2021) Protein corona on biogenic silver nanoparticles provides higher stability and protects cells from toxicity in comparison to chemical nanoparticles. Journal of Environmental Management 297:113434. doi:https://doi.org/10.1016/j.jenvman.2021.113434 El-Nahhal IM, Salem JK, Kuhn S, Hammad T, Hempelmann R, Al Bhaisi S (2016) Synthesis & characterization of silica coated and functionalized silica coated zinc oxide nanomaterials. Powder Technology 287:439-446. doi:https://doi.org/10.1016/j.powtec.2015.09.042 Leandro MKdNS, Moura JVB, Freire PdTC, Vega ML, Lima CdL, Hidalgo ÁA, Araújo ACJd, Freitas PR, Paulo CLR, Sousa AKd, Rocha JE, Leandro LMG, Silva ROMd, Cruz-Martins N, Coutinho HDM (2021) Characterization and Evaluation of Layered Bi2WO6 Nanosheets as a New Antibacterial Agent. Antibiotics 10(9):1068. doi:https://doi.org/10.3390/antibiotics10091068 Ahmed DS, Mohammed MKA (2020) Studying the bactericidal ability and biocompatibility of gold and gold oxide nanoparticles decorating on multi-wall carbon nanotubes. Chemical Papers 74(11):4033-4046. doi:https://doi.org/10.1007/s11696-020-01223-0 Rana A, Yadav K, Jagadevan S (2020) A comprehensive review on green synthesis of nature-inspired metal nanoparticles: Mechanism, application and toxicity. Journal of Cleaner Production 272:122880. doi:https://doi.org/10.1016/j.jclepro.2020.122880 Attarilar S, Yang J, Ebrahimi M, Wang Q, Liu J, Tang Y, Yang J (2020) The Toxicity Phenomenon and the Related Occurrence in Metal and Metal Oxide Nanoparticles: A Brief Review From the Biomedical Perspective. Frontiers in Bioengineering and Biotechnology 8 Bhunia AK, Kamilya T, Saha S (2017) Silver nanoparticle-human hemoglobin interface: time evolution of the corona formation and interaction phenomenon. Nano Convergence 4(1):28. doi:https://doi.org/10.1186/s40580-017-0122-1 Chakraborty M, Paul S, Mitra I, Bardhan M, Bose M, Saha A, Ganguly T (2018) To reveal the nature of interactions of human hemoglobin with gold nanoparticles having two different morphologies (sphere and star-shaped) by using various spectroscopic techniques. Journal of Photochemistry and Photobiology B: Biology 178:355-366. doi:https://doi.org/10.1016/j.jphotobiol.2017.11.026 Khan SA (2020) Chapter 1 - Metal nanoparticles toxicity: role of physicochemical aspects. In: Shah MR, Imran M, Ullah S (eds) Metal Nanoparticles for Drug Delivery and Diagnostic Applications. Elsevier, pp 1-11. doi:https://doi.org/10.1016/B978-0-12-816960-5.00001-X Wakeel A, Xu M, Gan Y (2020) Chromium-Induced Reactive Oxygen Species Accumulation by Altering the Enzymatic Antioxidant System and Associated Cytotoxic, Genotoxic, Ultrastructural, and Photosynthetic Changes in Plants. International Journal of Molecular Sciences 21(3):728 Flores-López LZ, Espinoza-Gómez H, Somanathan R (2019) Silver nanoparticles: Electron transfer, reactive oxygen species, oxidative stress, beneficial and toxicological effects. Mini review. Journal of Applied Toxicology 39(1):16-26. doi:https://doi.org/10.1002/jat.3654 Chien K-J, Yang M-L, Tsai P-K, Su C-H, Chen C-H, Horng C-T, Yeh C-H, Chen W-Y, Lin M-L, Chen C-J, Chian C-Y, Kuan Y-H (2018) Safrole induced cytotoxicity, DNA damage, and apoptosis in macrophages via reactive oxygen species generation and Akt phosphorylation. Environmental Toxicology and Pharmacology 64:94-100. doi:https://doi.org/10.1016/j.etap.2018.09.012 Aggarwal V, Tuli HS, Varol A, Thakral F, Yerer MB, Sak K, Varol M, Jain A, Khan MA, Sethi G (2019) Role of Reactive Oxygen Species in Cancer Progression: Molecular Mechanisms and Recent Advancements. Biomolecules 9(11):735 Jadhav MS, Kulkarni S, Raikar P, Barretto DA, Vootla SK, Raikar US (2018) Green biosynthesis of CuO & Ag–CuO nanoparticles from Malus domestica leaf extract and evaluation of antibacterial, antioxidant and DNA cleavage activities. New Journal of Chemistry 42(1):204-213. doi:https://doi.org/10.1039/C7NJ02977B Yin IX, Zhang J, Zhao IS, Mei ML, Li Q, Chu CH (2020) The Antibacterial Mechanism of Silver Nanoparticles and Its Application in Dentistry. Int J Nanomedicine 15:2555-2562. doi:https://doi.org/10.2147/IJN.S246764 Ferrag C, Li S, Jeon K, Andoy NM, Sullan RMA, Mikhaylichenko S, Kerman K (2021) Polyacrylamide hydrogels doped with different shapes of silver nanoparticles: Antibacterial and mechanical properties. Colloids and Surfaces B: Biointerfaces 197:111397. doi:https://doi.org/10.1016/j.colsurfb.2020.111397 Sehar S, Naz I, Rehman A, Sun W, Alhewairini SS, Zahid MN, Younis A (2021) Shape-controlled synthesis of cerium oxide nanoparticles for efficient dye photodegradation and antibacterial activities. Applied Organometallic Chemistry 35(1):e6069. doi:https://doi.org/10.1002/aoc.6069 Acharya D, Singha KM, Pandey P, Mohanta B, Rajkumari J, Singha LP (2018) Shape dependent physical mutilation and lethal effects of silver nanoparticles on bacteria. Scientific Reports 8(1):201. doi:https://doi.org/10.1038/s41598-017-18590-6 Mann R, Holmes A, McNeilly O, Cavaliere R, Sotiriou GA, Rice SA, Gunawan C (2021) Evolution of biofilm-forming pathogenic bacteria in the presence of nanoparticles and antibiotic: adaptation phenomena and cross-resistance. Journal of Nanobiotechnology 19(1):291. doi:https://doi.org/10.1186/s12951-021-01027-8 Ali SG, Ansari MA, Sajid Jamal QM, Khan HM, Jalal M, Ahmad H, Mahdi AA (2017) Antiquorum sensing activity of silver nanoparticles in P. aeruginosa: an in silico study. In Silico Pharmacology 5(1):12. doi:https://doi.org/10.1007/s40203-017-0031-3 Zhang H, Li Z, Dai C, Wang P, Fan S, Yu B, Qu Y (2021) Antibacterial properties and mechanism of selenium nanoparticles synthesized by Providencia sp. DCX. Environmental Research 194:110630. doi:https://doi.org/10.1016/j.envres.2020.110630 Volume 2, Issue 1 Cellular, Molecular and Biomedical Reports Receive Date: 17 October 2021 Revise Date: 21 November 2021 Accept Date: 20 December 2021 First Publish Date: 01 March 2022 Alavi, M., Rai, M., Martinez, F., Kahrizi, D., Khan, H., Rose Alencar de Menezes, I., Douglas Melo Coutinho, H., & Costa, J. (2022). The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action. Cellular, Molecular and Biomedical Reports, 2(1), 10-21. doi: 10.55705/cmbr.2022.147090.1023 Mehran Alavi; Mahendra Rai; Fleming Martinez; Danial Kahrizi; Haroon Khan; Irwin Rose Alencar de Menezes; Henrique Douglas Melo Coutinho; José Galberto Martins Costa. "The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action". Cellular, Molecular and Biomedical Reports, 2, 1, 2022, 10-21. doi: 10.55705/cmbr.2022.147090.1023 Alavi, M., Rai, M., Martinez, F., Kahrizi, D., Khan, H., Rose Alencar de Menezes, I., Douglas Melo Coutinho, H., Costa, J. (2022). 'The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action', Cellular, Molecular and Biomedical Reports, 2(1), pp. 10-21. doi: 10.55705/cmbr.2022.147090.1023 Alavi, M., Rai, M., Martinez, F., Kahrizi, D., Khan, H., Rose Alencar de Menezes, I., Douglas Melo Coutinho, H., Costa, J. The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action. Cellular, Molecular and Biomedical Reports, 2022; 2(1): 10-21. doi: 10.55705/cmbr.2022.147090.1023 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_147090.html

cc40

The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action Cellular, Molecular and Biomedical Reports Publication Et

en

Wikimedia Argentina hosts edit-a-thon, facilitates donation of high-quality images from museum – Diff 2 January 2013 by Matthew Roth This past month, Argentina joined the Latin American “edit-a-thon” fever, together with Chile and Mexico. On December 8th, nearly 20 Wikipedia volunteers participated in the first edit-a-thon organized in Buenos Aires. The event was hosted by Wikimedia Argentina and the Museum of the Bicentenary, which was also the venue for the activity. Urna electoral de 1916, exhibida en el Museo del Bicentenario. Esta fotografía fue elegida por la comunidad de Wikimedia Commons como “imagen destacada” del sitio./Ballot box used in 1916, exhibited in the Museum of the Bicentenary. This photograph was chosen by the community of Wikimedia Commons as a “featured picture” of the site. After a tour in the museum, the Wikipedians edited and developed several articles on Spanish Wikipedia related to Argentine history and the articles of the museum’s collection. For this, the Museum of the Bicentenary released several high-quality images of objects currently on display, works of art from its collection and photographs of the museum itself. These 86 images were published under free licenses and can be used on Wikipedia and by anybody else, while attributing the author of the work and keeping the original license. Among the published images are the official portrait of Juan Domingo Perón and his wife Eva, made by Numa Ayrinhac, the presidential sash and baton of Raúl Alfonsín and the first presidential chair, used by Santiago Derqui. In only a few weeks, more than 40 images have already been used in more than 16 languages (from Spanish to Aragonese, Arabic and Ukrainian). It is estimated that over 2 million people per month will see the images of the Museum that are currently in use on Wikipedia, but that number could rise as volunteers illustrate new Wikipedia articles with these images. The initiative was welcomed by Juan José Ganduglia, Director of the Museum, who was actively involved in the activity, supporting attendees and providing information about the museum and the history behind its exhibits. The success of this first edit-a-thon will make it possible to host new events for 2013 in the Museum and in other similar institutions within Argentina. Osmar Valdebenito, Executive Director, Wikimedia Argentina Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Chapters, EventsTagged multilingual post, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/01/02/wikimedia-argentina-hosts-editathon-gets-image-donation/

cc40

Wikimedia Argentina hosts edit-a-thon, facilitates donation of high-quality images from museum – Diff 2 January 2013 by Matthew Roth This past month, Argentina joined the Latin American “edit-a-thon”

en

Fundraising from the heart: Crafting powerful, authentic messages that move millions to support Wikipedia – Diff 30 November 2017 by Caitlin Cogdill Photo by Eric Kilby via Flickr, CC BY-SA 2.0. “As I look around the internet today, I think back to when I first discovered Wikipedia. The internet was still a pretty free-wheeling place, and Wikipedia was born out of that spirit of creativity and possibility. The rest of the web has changed a lot—we all use the same few big sites, we do less creating and more consuming. But Wikipedia is still independent, still written by ordinary people, still has that can-do spirit.” –Katherine Maher, Wikimedia Foundation Executive Director Picture this: On the second floor of a quiet coworking space, a group of people are squeezed around a table in a small conference room. There is barely enough room for our chairs. The air is stuffy after hours of batting ideas around, but there is an energetic buzz in the room—and not just from the many empty coffee cups scattered about. The clatter of laptop keys is the only sound except for small moments when someone, bemused at what they’ve just written, reads a line aloud to the group and the room explodes with laughter and new ideas. A triumphant, “Done!” then came from one corner of the room where Katherine Maher sat—because this was a special day for the team. After writing together for a week, we all knew we needed something new: an insider’s voice to introduce readers to Wikipedia’s bright new future. When we heard that Katherine would be in the same city as us for a few short hours, we asked her to come contribute her unique voice. It had been a long afternoon of writing for Katherine, but when her breathless “Done!” reverberated off the tight walls of the conference room, we knew this one would be special. The room went silent as we all read, carefully, and saw with satisfaction that there was nothing we would change. Not even a comma. “It’s a little awkward to say this, but consider that fewer than 1% of readers donate to Wikipedia. It’s your generosity that keeps us going. The knowledge that what we’re doing matters, and it matters to people like you. It ensures Wikipedia is here for you when you need us.” Sixteen different messages were tested that day, but we all could have guessed the winner from the get-go. The message that was written in Katherine’s own hand, her honest appeal to Wikipedia donors, rose to the top. She was able to tap into that combination of frankness, humor, and aspiration that makes donors see what Wikimedia means to the world. Every quote in this post comes from Katherine, made in that stuffy conference room back in October. Creating effective, authentic messages is about a lot more than brainstorming in a hot room. From these initial brainstorm and testing sessions, themes emerge that present opportunities for focused experimentation and refinement. We find inspiration combing through interviews, articles, and the depths of our own love for this project to craft more than a thousand different messages every year (to say nothing of experiments with design, payment options, personalization, and localization). All this testing is in the service of a specific goal: understand why most people love Wikipedia, and give them a powerful reminder to support the internet’s most used non-profit website. Here’s what we know. Wikipedia is useful to everyday people all around the world. It strives to be nonpartisan and consensus-driven so that normal people can make it better. It is important that Wikipedia will never bombard its readers with ads or paywalls because its integrity is rooted in its independence. People experience Wikipedia in an intimate way—it’s there to answer our silliest and most embarrassing questions and to guide us to profound discoveries—so it’s important that our messages reinforce that relationship. We don’t mince words. We ask real people, like Katherine, to tell donors why they are essential to defending this resource. Sure, we also use statistics, coding, and some sophisticated software to help us do our jobs, but our creative team’s most magical moments happen when we come together in a room, put our heads down, and tell it like it is. The next time you see a Wikipedia fundraising banner or receive an email from us, think about it as being part of a real, human relationship—you, us, and Wikipedia—sustaining free knowledge for another year. But don’t take it from me, let Katherine tell you: “Folks like you help us maintain our integrity, quality, and accessibility. You safeguard our nonprofit mission. Please help us keep this wonderful website free and independent for another year, and do your part to make a better world for years to come.” Caitlin Cogdill, Senior Fundraising Engagement Manager, Advancement Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. When I received the first request for a donation I gladly gave a donation. It was more than $3. Now that I am receiving a second request, should i donate again? Or are you talking to those who have not donated? You might make this clear in your request Just want to say that I had no idea that you needed funding. I love wiki and use it all the time. I’m thankful for you. I’m sure most people are just like me, You never asked for money so I didn’t know you needed it. Definitely a duh on my part but I’m sure I’m not alone. I do think you’re going to get tons of money from that really lovely message; honesty shines from it. I was thinking past the current mess, Well I gave $100 instantly when I saw your message so lots will do the same.… Read more » Throughout my career, I have found the most effective fundraising messages to be those that strike an emotional chord. Messages that touch upon the human condition, generate enthusiasm for the cause, and spur advocacy through a sense of community and shared beliefs will always generate results. In this way, the human/personal element is indeed important. Much continued success to the Wikimedia Foundation in 2018! Posted in Foundation, FundraisingTagged banner, donors, Fundraising, messaging, Wikimedia Blog (EN Archive), Wikimedia Foundation Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2017/11/30/fundraising-from-the-heart/

cc40

Fundraising from the heart: Crafting powerful, authentic messages that move millions to support Wikipedia – Diff 30 November 2017 by Caitlin Cogdill Photo by Eric Kilby via Flickr, CC BY-SA 2.0. “As I

en

Students at the University of California at Berkeley's "Politics of Piracy" class are participating in the Public Policy Initiative this fall. We’ve reached the mid point of the first term of the Wikipedia Public Policy Initiative – and we’ve had a lot of excitement and interest so far. Our students are beginning to write their first articles, a handful of which have already been featured in the Did You Know? section of the front page of English Wikipedia. Here’s an update on where we are: One thing we’ve already learned is that professors are very enthusiastic about working with us to incorporate editing Wikipedia into their classroom. From our initial course announcement, we’ve added five more schools. We have public schools, private schools; large research universities, small liberal arts schools; small classes, large classes; graduate students and undergraduates – all told, we have a diverse set of classes that are improving Wikipedia articles. You can see the full list on the Courses page of our WikiProject (and see below for more information about opportunities for the spring term). Our students are working on more than 100 articles. Some students are just beginning to select their topics. Others have completed significant work on their articles, either in the mainspace or in article sandboxes (temporary spaces for experimenting with new articles). For an example of what our students are doing, take a look at the Food Quality Protection Act article. It had languished as a stub article since its creation in 2007. Since mid-October of this year, however, a Syracuse University student has researched the Act and significantly improved its Wikipedia coverage, expanding the content of the article and adding photos from Wikimedia Commons (see the diff). The article was featured in the Did You Know? section on the English Wikipedia main page. One thing you’ll notice if you look through the history of the Food Quality Protection Act article is that several other Wikipedians collaborated with the student during the improvement of the Food Quality Protection Act article. Many of them are part of our Wikipedia Ambassador program. Campus Ambassadors (WP:CAMPUS) work with students in the classrooms on their Wikipedia assignments, including leading in-person sessions that teach students how to edit Wikipedia. The online counterpart to Campus Ambassadors are Online Ambassadors (WP:ONLINE), who serve as online mentors to the students, explaining both the how and the why of Wikipedia-editing. As with everything we’re doing with the Public Policy Initiative, we’re working to make the Ambassador program self-sustaining at the end of our grant, and one of the ways we’re doing that is by making the Ambassador program community-driven. We’ve formed an Ambassador Steering Committee that is thinking through the big questions about the Ambassador program. Committee members include experienced Campus Ambassadors, Online Ambassadors, Wikipedians, and Wikimedia Foundation staff. We’re also hard at work on a qualitative and quantitative assessment of how we’re actually doing. We’ve created a more detailed assessment scheme that translates article scores into traditional article quality ratings (see the Assessment page of our WikiProject for more information). Several Wikipedians and public policy experts are volunteering to use this new assessment to rate articles within the scope of the Public Policy WikiProject, including articles students have worked on. We’re also hosting the pilot of the new Article Feedback Tool, which offers Wikipedia readers the opportunity to rate articles. The initial results of our data analysis will be released in early 2011. We’re now in the planning stages for what we want to accomplish in spring 2011. We’ve lined up most of the professors for our spring slots, but we still have the ability to support five more courses that focus on issues related to U.S. public policy. Do you know a professor who teaches a public-policy-related course? Are you interested in being a Wikipedia Ambassador for a local university? Leave a message for our Campus Team Coordinator, Annie Lin, at her Wikipedia talk page. You’re always welcome to find us in the #wikimedia-outreach IRC channel on freenode as well. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Community, Outreach, Public Policy Initiative, WikipediaTagged Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2010/11/01/the-public-policy-initiative-midterm/

cc40

Students at the University of California at Berkeley's "Politics of Piracy" class are participating in the Public Policy Initiative this fall. We’ve reached the mid point of the first term of the Wiki

en

T228856: RemexStripTagHandler should strip contents Framawiki created this task.Jun 21 2019, 7:26 PM2019-06-21 19:26:41 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 21 2019, 7:26 PM2019-06-21 19:26:41 (UTC+0) Framawiki triaged this task as High priority.Jun 22 2019, 8:29 PM2019-06-22 20:29:56 (UTC+0) Has been reproduced by another user, @Bastenbas, hence increasing the priority. Aklapper added a comment.Jun 23 2019, 8:08 AM2019-06-23 08:08:40 (UTC+0) @Framawiki: Well, is only that one single image affected, or many files? Just because I can also reproduce it does not necessarily mean that it's high priority, otherwise every issue that two people see would suddenly be high priority. :) The displayed CSS seems to come from https://fr.wikipedia.org/wiki/Modèle:Légende/styles.css However when I go to https://fr.wikipedia.org/w/index.php?title=Fronti%C3%A8re_entre_l%27Inde_et_le_Pakistan&debug=true&oldid=159781368#/map/0 , I get no map displayed at all. I wonder if that is related. Or not. My browser's Developer Tools show Error: "Invalid GeoJSON object." geometryToLayer https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:10574 _initialize https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:13465 setGeoJSON https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:13408 initialize https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:13401 NewClass https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:414 featureLayer https://fr.wikipedia.org/w/extensions/Kartographer/lib/external/mapbox/mapbox-lib.js?12d15:13499 addGeoJSONLayer https://fr.wikipedia.org/w/extensions/Kartographer/modules/box/Map.js?36be0:449 addDataGroups https://fr.wikipedia.org/w/extensions/Kartographer/modules/box/Map.js?36be0:396 each jQuery addDataGroups https://fr.wikipedia.org/w/extensions/Kartographer/modules/box/Map.js?36be0:387 Aklapper renamed this task from Map title not shown but CSS code to Map title not shown on fr.wp but local CSS code.Jun 23 2019, 8:09 AM2019-06-23 08:09:56 (UTC+0) TheDJ added a subscriber: TheDJ.Mar 18 2020, 5:04 PM2020-03-18 17:04:13 (UTC+0) This is templatestyles being inserted into the "text=" attribute of Pikne edited projects, added Maps (Kartographer); removed Maps (Kartotherian).Mar 18 2020, 5:48 PM2020-03-18 17:48:11 (UTC+0) Pikne added a subscriber: Pikne. In T226279#5980612, @TheDJ wrote: This is templatestyles being inserted into the "text=" attribute of Is this due to T228856? TheDJ added a comment.Mar 18 2020, 6:22 PM2020-03-18 18:22:07 (UTC+0) No, dont think so. Pikne closed this task as a duplicate of T292598: Full screen map fails to handle style elements in caption text properly.Oct 6 2021, 11:04 AM2021-10-06 11:04:26 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T226279

cc40

T228856: RemexStripTagHandler should strip contents Framawiki created this task.Jun 21 2019, 7:26 PM2019-06-21 19:26:41 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald Tra

en

After the positive results for T142037, David suggested adding ascii-folding for the French Wikipedia. As noted elsewhere, [citation needed], it's common to see queries without diacritics, and enabling ascii-folding would improve matches in those cases. We can run a similar analysis as with T142037, setting up the analysis chain as it currently is for French Wikipedia, and then modifying it with the new ascii-folding. We can determine the raw number of new collisions caused by introducing ascii-folding, and get similar automated estimates of similar terms being bucketed together. T139575 EPIC: Plan to enable BM25 on fulltext search T141216 ÿ in Spécial:IndexPages search T142620 Test effect of adding ascii-folding on French Wikipedia T75605: No normalization for ancient greek accents in searches T104814: Appropriately ignore diacritics for German-language wikis T147505: [tracking] CirrusSearch: what is updated during re-indexing T144429: Commit changes to implement ascii-folding for French T41501: Merging Unicode similar-looking characters in internal search (apostrophes, "x" and "×", etc) T141216: ÿ in Spécial:IndexPages search T42612: Japanese filenames do not appear in search results if file extension dropped T64733: CirrusSearch does not find all JavaScript and CSS pages when using insource and intitle syntax T137830: Use the icu_folding filter if available instead of asciifolding T143541: Search for acronyms is not properly handled by the FullTextSimpleMatchQueryBuilder query builder T142037: Test effect of re-ordering kstem and asciifolding on English Wikipedia TJones created this task.Aug 10 2016, 7:07 PM2016-08-10 19:07:20 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 10 2016, 7:07 PM2016-08-10 19:07:20 (UTC+0) TJones added a subscriber: debt.Aug 10 2016, 7:07 PM2016-08-10 19:07:53 (UTC+0) @debt: David and I think this should be high priority because we're going to be re-indexing everything in a few weeks for BM25. We should do any of these re-indexing–type studies before that. Re-indexing at a later date is possible but may be too much disruption for this smaller change. debt added a subtask: T141216: ÿ in Spécial:IndexPages search.Aug 11 2016, 4:36 PM2016-08-11 16:36:06 (UTC+0) debt removed a subtask: T141216: ÿ in Spécial:IndexPages search. debt added a parent task: T141216: ÿ in Spécial:IndexPages search. debt edited projects, added Discovery-Search (Current work); removed Discovery-Search.Aug 11 2016, 4:38 PM2016-08-11 16:38:19 (UTC+0) debt added a parent task: T139575: EPIC: Plan to enable BM25 on fulltext search. debt triaged this task as High priority.Aug 11 2016, 5:10 PM2016-08-11 17:10:54 (UTC+0) TJones moved this task from Incoming to not in use - please delete on the Discovery-Search (Current work) board.Aug 11 2016, 5:15 PM2016-08-11 17:15:33 (UTC+0) TJones mentioned this in T141216: ÿ in Spécial:IndexPages search.Aug 12 2016, 7:27 PM2016-08-12 19:27:09 (UTC+0) EBernhardson added a subscriber: EBernhardson.Aug 15 2016, 10:12 PM2016-08-15 22:12:06 (UTC+0) TJones mentioned this in T41501: Merging Unicode similar-looking characters in internal search (apostrophes, "x" and "×", etc).Aug 19 2016, 4:32 PM2016-08-19 16:32:21 (UTC+0) TJones moved this task from not in use - please delete to Needs review on the Discovery-Search (Current work) board.Edited · Aug 19 2016, 8:28 PM2016-08-19 20:28:18 (UTC+0) The default French analysis chain unexpectedly does some ascii-folding already, after stemming. Unpacking the default French analysis chain per the Elasticsearch docs leads to different results, but most of the changes are desirable, and the effect size is very small. English and Italian, which have been similarly unpacked to add ascii-folding in the past, include a bit of extra tokenizing help for periods and underscores, which we may want to also do for French—though it does violence to acronyms and may not work with BM25. Ascii-folding itself effects significantly more tokens than ascii-folding in English—50 times as many (as a percentage) for a 50K article corpus—which is not entirely a surprise, since many more accented characters are regularly used in French. Recommendations: turn on ascii-folding as a final step for French, add an initial custom filter for Turkish İ, explore disabling word_break_helper for enwiki and itwiki! • ksmith added a subscriber: • ksmith.Aug 30 2016, 10:05 PM2016-08-30 22:05:04 (UTC+0) @TJones : You moved this to "Needs Review", but who should review it? dcausse added a comment.Edited · Aug 31 2016, 9:43 AM2016-08-31 09:43:38 (UTC+0) I've reviewed the conclusions of this analysis and I agree. I'm not entirely sure but I think that the problem with the Turkish İ should be resolved as part of T137830. But since it looks like a regression compared to the previous configuration we should add it. Concerning the word_breaker_helper: removing it can cause a regression on T42612 and T64733, I'd suggest working on a proper fix at the analysis level (some thoughts here: T143541). Concerning "Unexpected Differences in Unpacked Analysis Chain": I'd like to understand why unpacking the analysis chain causes differences, it's maybe a bug in the elasticsearch documentation. @TJones are you sure that these "Unexpected Differences in Unpacked Analysis Chain" were seen before adding ascii folding? Or I misunderstood something and the title of this section should be renamed "Unexpected Differences in Unpacked Analysis Chain with an additional ascii folding filter" ? Should we create a followup task to implement the recommendations? TJones mentioned this in T144429: Commit changes to implement ascii-folding for French.Aug 31 2016, 7:34 PM2016-08-31 19:34:55 (UTC+0) TJones moved this task from Needs review to Needs Reporting on the Discovery-Search (Current work) board. @dcausse and I reviewed the unpacked French analysis chain, and it looks as though I unpacked it correctly. I double checked the default French vs Unpacked vs Unpacked+Ascii-Folding on a couple of the characters that showed the effects: ς & ϐ. They were unchanged by the French analysis, folded to σ and B when French was unpacked, and folded and duplicated when asciifolding_preserve was added, so the analysis is right. We discovered a semi-bug in the implementation of word_breaker_helper: it's added to the default custom analysis chain in the code, but that doesn't affect the built-in language analyzers. Thus, it is not currently enabled for French, and so we're going to leave it off for now, and deal with that as a separate issue. I'll add comments in the appropriate place in the code to reduce confusion until it is addressed directly. Changes will be committed under T144429. debt closed this task as Resolved.Sep 1 2016, 8:52 PM2016-09-01 20:52:35 (UTC+0) Thanks, @TJones and @dcausse ! TJones mentioned this in T147505: [tracking] CirrusSearch: what is updated during re-indexing.Oct 6 2016, 6:04 PM2016-10-06 18:04:20 (UTC+0) TJones mentioned this in T104814: Appropriately ignore diacritics for German-language wikis.Jun 27 2017, 9:38 PM2017-06-27 21:38:37 (UTC+0) TJones mentioned this in T75605: No normalization for ancient greek accents in searches.Jul 6 2017, 8:52 PM2017-07-06 20:52:14 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T142620

cc40

After the positive results for T142037, David suggested adding ascii-folding for the French Wikipedia. As noted elsewhere, [citation needed], it's common to see queries without diacritics, and enablin

en

2 Department of Internal Medicine, Faculty of Medicine, Mashhad University of Medical Sciences, Mashhad, Iran Seabuckthorn has multiple-use properties. This review explores the medicinal applications of Hippophae rhamnoides in healing ailments. The plant is being used in different parts of the world for its nutritional and medicinal properties. Sea buckthorn-based preparations have been extensively exploited in folklore treatment of slow digestion, stomach malfunctioning, cardiovascular problems, liver injury, tendon and ligament injuries, skin diseases and ulcers. In recent years, the medicinal and pharmacological activities of Seabuckthorn have been well investigated using limited clinical trials. Homeopathy is a well-respected modality to assist wellness. Traditional and modern medicinal experts have been applied this plant to treat various diseases. Seabuckthorn is an important plant because of its immense medicinal and therapeutic potential. However, several knowledge gaps identified in this paper would give impetus to new academic and R&D activities, especially for the development of Sea buckthorn-based herbal medicine and nutraceuticals. Its full application in dermatology may be attributed to the presence of a variety of flavonoids, vitamins, and unsaturated fatty acids. Great use of the plant in the traditional system for dermatological aspects, demands further comprehensive phytochemical work based on its actual use by the traditional population. Anti-inflammation is the most important applicable ingredient of this miracle berry. Selected author of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Olas B, Skalski B, Ulanowska K (2018) The anticancer activity of sea buckthorn [Elaeagnus rhamnoides (L.) A. Nelson]. Frontiers in pharmacology 9:232. doi:https://doi.org/10.3389/fphar.2018.00232 Malik S, Babbar S, Chaudhary M, Sharma S, Raina SN, Babbar SB (2022) Authentication and deciphering interrelationships of Hippophae species using DNA barcodes. The Nucleus 2022:1-13. doi:https://doi.org/10.1007/s13237-021-00382-z Pundir S, Garg P, Dviwedi A, Ali A, Kapoor V, Kapoor D, Kulshrestha S, Lal UR, Negi P (2021) Ethnomedicinal uses, phytochemistry and dermatological effects of Hippophae rhamnoides L.: A review. Journal of Ethnopharmacology 266:113434. doi:https://doi.org/10.1016/j.jep.2020.113434 Ahani H, Jalilvand H, Vaezi J, Sadati SE (2016) Studying the seed germination traits of Seabuckthorn (Elaeagnus rhamnoides) of Iran, China and Tibet. Forest and Wood Products 69(2):225-235. doi:https://dx.doi.org/10.22059/jfwp.2016.59038 Ahani H, Jalilvand H, Vaezi J, Sadati S (2015) Effect of different treatments on Hippophae rhamnoides seed germination in laboratory. Iranian journal of forest 7(1):45-56 Ahani H, Jalilvand H, Vaezi J, Sadati S, Jia D, Bai X, Bagheri H DNA quality and quantity of Sea Buckthorn (Hippophae rhamnoides) subspecies in Iran and China. In: 7th conference of International Seabuckthorn Association, India, 2015. Ahani H, Tabatabaei S (2018) Impact of irrigation with saline water on morphology of sea buckthorn seedlings in nursery. Forest Res Eng Int J 2(6):326-333 Ciesarová Z, Murkovic M, Cejpek K, Kreps F, Tobolková B, Koplík R, Belajová E, Kukurová K, Daško Ľ, Panovská Z (2020) Why is sea buckthorn (Hippophae rhamnoides L.) so exceptional? A review. Food Research International 133:109170. doi:https://doi.org/10.1016/j.foodres.2020.109170 Li TS, Schroeder WR (1996) Sea buckthorn (Hippophae rhamnoides L.): a multipurpose plant. HortTechnology 6(4):370-380. doi:https://doi.org/10.21273/HORTTECH.6.4.370 Krejcarová J, Straková E, Suchý P, Herzig I, Karásková K (2015) Sea buckthorn (Hippophae rhamnoides L.) as a potential source of nutraceutics and its therapeutic possibilities-a review. Acta Veterinaria Brno 84(3):257-268. doi:https://doi.org/10.2754/avb201584030257 Suryakumar G, Gupta A (2011) Medicinal and therapeutic potential of Sea buckthorn (Hippophae rhamnoides L.). Journal of Ethnopharmacology 138(2):268-278. doi:https://doi.org/10.1016/j.jep.2011.09.024 Rongsen L, Ahani H, Shaban M, Esfahani M, Alizade G, Rostampour M, Moazeni N, Javadi S, Mahdavian S (2013) The genetic resources of Hippophae genus and its utilization. Int J Scholary Res Gate 1:15-21 Zielińska A, Nowak I (2017) Abundance of active ingredients in sea-buckthorn oil. Lipids in health and disease 16(1):1-11. doi:https://doi.org/10.1186/s12944-017-0469-7 Rehman A, Hussain S, Javed M, Ali Z, Rehman H, Shahzady TG, Zahra A (2018) Chemical composition and remedial perspectives of Hippophae rhamnoides linn. Postepy Biologii Komorki 45(3):199-209 Reynolds KA, Juhasz ML, Mesinkovska NA (2019) The role of oral vitamins and supplements in the management of atopic dermatitis: a systematic review. International journal of dermatology 58(12):1371-1376. doi:https://doi.org/10.1111/ijd.14404 Rédei D, Kúsz N, Rafai T, Bogdanov A, Burián K, Csorba A, Mándi A, Kurtán T, Vasas A, Hohmann J (2019) 14-Noreudesmanes and a phenylpropane heterodimer from sea buckthorn berry inhibit Herpes simplex type 2 virus replication. Tetrahedron 75(10):1364-1370. doi:https://doi.org/10.1016/j.sjbs.2016.01.004 Jain A, Chaudhary S, Sharma PC (2014) Mining of microsatellites using next generation sequencing of seabuckthorn (Hippophae rhamnoides L.) transcriptome. Physiology and Molecular Biology of Plants 20(1):115-123. doi:https://doi.org/10.1007/s12298-013-0210-6 Guliyev VB, Gul M, Yildirim A (2004) Hippophae rhamnoides L.: chromatographic methods to determine chemical composition, use in traditional medicine and pharmacological effects. Journal of chromatography B 812(1-2):291-307. doi:https://doi.org/10.1016/j.jchromb.2004.08.047 Enkhtaivan G, John KM, Pandurangan M, Hur JH, Leutou AS, Kim DH (2017) Extreme effects of Seabuckthorn extracts on influenza viruses and human cancer cells and correlation between flavonol glycosides and biological activities of extracts. Saudi Journal of Biological Sciences 24(7):1646-1656. doi:https://doi.org/10.1016/j.sjbs.2016.01.004 Nikolaeva LG, Maystat TV, Masyuk LA, Pylypchuk VS, Volyanskii YL, Kutsyna GA (2008) Changes in CD4+ T-cells and HIV RNA resulting from combination of anti-TB therapy with Dzherelo in TB/HIV dually infected patients. Drug design, development and therapy 2:87. doi:PMCID: PMC2761183; PMID: 19920896 Shipulina L, Tolkachev O, Krepkova L, Bortnikova V, Shkarenkov A (2005) Anti-viral anti-microbial and toxicological studies on Seabuckthorn (Hippophae rhamnoides). Seabuckthorn (Hippophae L): A Multipurpose Wonder Plant 2:471-483 Torelli A, Gianchecchi E, Piccirella S, Manenti A, Piccini G, Pastor EL, Canovi B, Montomoli E (2015) Sea buckthorn bud extract displays activity against cell-cultured Influenza virus. Journal of Preventive Medicine and Hygiene 56(2):E51. doi:PMCID: PMC4718352; PMID: 26789988 Ghimire B, Sharma S (2018) Nutritional security and biodiversity conservation with Sea Buckthorn (Hippophae Spp. L.): an underutilized species of Himalayan. Int J Agric Biosyst Eng 3:42-45 Razali N, Mat-Junit S, Abdul-Muthalib AF, Subramaniam S, Abdul-Aziz A (2012) Effects of various solvents on the extraction of antioxidant phenolics from the leaves, seeds, veins and skins of Tamarindus indica L. Food chemistry 131(2):441-448. doi:https://doi.org/10.1016/j.foodchem.2011.09.001 Michel T, Destandau E, Le Floch G, Lucchesi ME, Elfakir C (2012) Antimicrobial, antioxidant and phytochemical investigations of sea buckthorn (Hippophaë rhamnoides L.) leaf, stem, root and seed. Food chemistry 131(3):754-760. doi:https://doi.org/10.1016/j.foodchem.2011.09.029 Masoodi KZ, Wani W, Dar ZA, Mansoor S, Anam-ul-Haq S, Farooq I, Hussain K, Wani SA, Nehvi FA, Ahmed N (2020) Sea buckthorn (Hippophae rhamnoides L.) inhibits cellular proliferation, wound healing and decreases expression of prostate specific antigen in prostate cancer cells in vitro. Journal of Functional Foods 73:104102. doi:https://doi.org/10.1016/j.jff.2020.104102 Hibasami H, Mitani A, Katsuzaki H, Imai K, Yoshioka K, Komiya T (2005) Isolation of five types of flavonol from seabuckthorn (Hippophae rhamnoides) and induction of apoptosis by some of the flavonols in human promyelotic leukemia HL-60 cells. International journal of molecular medicine 15(5):805-809. doi:https://doi.org/10.3892/ijmm.15.5.805 Zhamanbaeva G, Murzakhmetova M, Tuleukhanov S, Danilenko M (2014) Antitumor activity of ethanol extract from Hippophae rhamnoides L. leaves towards human acute myeloid leukemia cells in vitro. Bulletin of experimental biology and medicine 158(2):252-255. doi:https://doi.org/10.1007/s10517-014-2734-3 Patel CA, Divakar K, Santani D, Solanki HK, Thakkar JH (2012) Remedial prospective of Hippophae rhamnoides Linn.(sea buckthorn). International Scholarly Research Notices 2012:Article ID: 436857. doi:https://doi.org/10.5402/2012/436857 Kalyani D, Divakar G, Chirag P, Ansari MA (2010) Cytotoxic and antiproliferative effects of hydroalcoholic extract of Hippophae rhamnoides Linn seeds against human leukemia cancer (HL-60) and BHK-21 normal cells. Annals of Biological Research 1(3):190-199. doi:Record Number : 20103302447 Basu M, Prasad R, Jayamurthy P, Pal K, Arumughan C, Sawhney R (2007) Anti-atherogenic effects of seabuckthorn (Hippophaea rhamnoides) seed oil. Phytomedicine 14(11):770-777. doi:https://doi.org/10.1016/j.phymed.2007.03.018 Dong K, Fernando WMB, Durham R, Stockmann R, W. Jayatunga DP, Jayasena V (2020) A role of sea buckthorn on Alzheimer’s disease. International Journal of Food Science & Technology 55(9):3073-3081. doi:https://doi.org/10.1111/ijfs.14571 Gutzeit D, Mönch S, Jerz G, Winterhalter P, Rychlik M (2008) Folate content in sea buckthorn berries and related products (Hippophae rhamnoides L. ssp. rhamnoides): LC-MS/MS determination of folate vitamer stability influenced by processing and storage assessed by stable isotope dilution assay. Analytical and bioanalytical chemistry 391(1):211-219. doi:https://doi.org/10.1007/s00216-008-1905-3 Ran B, Guo CE, Li W, Li W, Wang Q, Qian J, Li H (2021) Sea buckthorn (Hippophae rhamnoides L.) fermentation liquid protects against alcoholic liver disease linked to regulation of liver metabolome and the abundance of gut microbiota. Journal of the Science of Food and Agriculture 101(7):2846-2854. doi:https://doi.org/10.1002/jsfa.10915 Koskovac M, Cupara S, Kipic M, Barjaktarevic A, Milovanovic O, Kojicic K, Markovic M (2017) Sea buckthorn oil—A valuable source for cosmeceuticals. Cosmetics 4(4):40. doi:https://doi.org/10.3390/cosmetics4040040 Larmo P, Järvinen R, Laihia J, Löyttyniemi E, Maavirta L, Yang B, Kallio H, Sandberg-Lall M (2019) Effects of a sea buckthorn oil spray emulsion on dry eye. Contact Lens and Anterior Eye 42(4):428-433. doi:https://doi.org/10.1016/j.clae.2018.11.011 Dubey S, Deep P, Singh AK (2016) Phytochemical characterization and evaluation of anticataract potential of seabuckthorn leaf extract. Veterinary Ophthalmology 19(2):144-148. doi:https://doi.org/10.1111/vop.12271 Volume 2, Issue 1 Cellular, Molecular and Biomedical Reports Receive Date: 18 October 2021 Revise Date: 29 December 2021 Accept Date: 30 January 2022 First Publish Date: 01 March 2022 Ahani, H., & Attaran, S. (2022). Therapeutic potential of Seabuckthorn (Hippophae rhamnoides L.) in medical sciences. Cellular, Molecular and Biomedical Reports, 2(1), 22-32. doi: 10.55705/cmbr.2022.330326.1020 Hamid Ahani; Soroush Attaran. "Therapeutic potential of Seabuckthorn (Hippophae rhamnoides L.) in medical sciences". Cellular, Molecular and Biomedical Reports, 2, 1, 2022, 22-32. doi: 10.55705/cmbr.2022.330326.1020 Ahani, H., Attaran, S. (2022). 'Therapeutic potential of Seabuckthorn (Hippophae rhamnoides L.) in medical sciences', Cellular, Molecular and Biomedical Reports, 2(1), pp. 22-32. doi: 10.55705/cmbr.2022.330326.1020 Ahani, H., Attaran, S. Therapeutic potential of Seabuckthorn (Hippophae rhamnoides L.) in medical sciences. Cellular, Molecular and Biomedical Reports, 2022; 2(1): 22-32. doi: 10.55705/cmbr.2022.330326.1020 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_147366.html

cc40

2 Department of Internal Medicine, Faculty of Medicine, Mashhad University of Medical Sciences, Mashhad, Iran Seabuckthorn has multiple-use properties. This review explores the medicinal applications

en

The Medical Translation Task Force has boosted its productivity by 17% and increased the amount of health care content by using the Content Translation tool. Rather than handing out a Microsoft Word document full of Wikimedia markup for translation, translators are being coached on how to use the Content Translation. As a new process, this change met some resistance, but the payoffs are justifying the effort—more total content is being uploaded to local-language Wikipedias and certain languages now have complete coverage of a health topic. In this case, we’re working on the 23 ‘essential’ vaccines, as determined by the World Health Organization. It is like the old parable: give a man a fish and you feed him for a day (akin to individual translation requests); teach a man to fish and you feed him for a lifetime (akin to using Content Translation). The greatest success stories thus far are in Burmese, Malay, and Odia. An additional 136.5 million native language speakers now have access to accurate, free, and easy to access health care information on all 23 essential vaccines in their local-language (where virtually none existed before). This breadth of medical content is important to make Wikipedia a go-to and trusted source of information. An additional 71.7 million speakers (in such languages as Thai, Romanian, and Yoruba) now have access to at least a third of the 23 vaccine articles. We are actively working in 31 other languages to improve articles about vaccines. But more significant is that the total time spent requesting translations, uploading and merging translations, and following up with volunteers has decreased. It is estimated that productivity (new medical articles relative to the coordination efforts to create them) has improved 17%. Quite simply, once translators learn to use the Content Translation tool, they are self-directed and generate more output with less project management. Content Translation is a beta feature available on all Wikipedias. Once enabled, users can easily start a side-by-side translation that preserves all the important wikicode—notably the citations and interwiki links (templates are an exception) and then upload it to the target Wikipedia with a single click. It requires lots of encouragement and facilitating to get non-Wikipedian volunteer translators to put aside trusted translation software and try Content Translation, as non-Wikipedians seem intimidated by the prospect of making a public mistake on Wikipedia. To ease the process, they are being given a unique pre-made Wikipedia user account with the beta Content Translation activated, a note on their user page, and a couple of vaccine summaries pre-loaded on their account. All they have to do is log-in and try it out. A YouTube video serves as the how-to file. The pre-made user accounts also make it easy to track volunteers’ progress and do quality control. In some instances, helpers are hesitant to hit “publish” button and project coordinators intervene and make their contribution live. In other instances, the published translations have to be moved from a work space into the main space. Since this project uses summary files—basically the leads of the English articles rather than full length medical articles—the repository of files is not in the main space. Content Translation normally presumes that you are translation an existing article from the main space of one language to fill in for a non-existent article in another language. Members of the Translation Task Force (notably Doc James) generate these summaries by improving and referencing the leads. The vaccine articles get about 275,000 pageviews in English per month. The volunteer translators consist of past helpers from Translators Without Borders (TWB). In collaboration with TWB, these particular translations took place entirely on the Content Translation platform yet credit (word count) is still given in the TWB workspace to both honor the great working relationship with TWB and reward the volunteers. Numerous translators request getting TWB recognition prior to agreeing to try Content Translation. So at month end, the Translation Task Force uploads quasi work orders on TWB to acknowledge the efforts of these volunteers. Over time, we imagine improving Wikipedia will grow to become an even greater reward. Lucas559, WikiProject Med Foundation The views expressed in these stories are not necessarily those of the Wikimedia Foundation or Wikipedia; responses and critical commentary are invited in the comments section below. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. A great write up about an important project. Content translation tool hits milestone with one hundred thousand articles – Wikimedia Blog […] to expand its coverage of essential health content in many languages; they have observed about 17% improved productivity in the efforts taken to coordinate and complete translations, thus helping spread medical information faster around the world. We plan to continue supporting […] ഓരോ അഞ്ച് മിനിറ്റിലും പുതിയ ലേഖനം; വിക്കിപീഡിയ ബഹുഭാഷാ സാന്നിധ്യം വർദ്ധിക്കുന്നു Posted in Community, Free Knowledge, Technology, WikipediaTagged Content translation, free knowledge, medical, translation, vaccine, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2016/03/29/wikipedias-essential-vaccines/

cc40

The Medical Translation Task Force has boosted its productivity by 17% and increased the amount of health care content by using the Content Translation tool. Rather than handing out a Microsoft Word d

en

In January 2017, the Wikimedia movement started an ambitious process to find alignment, rebuild trust, and identify a shared strategic direction for the 2030 horizon. Dozens of groups and organizations have now come together to endorse the Wikimedia movement’s new strategic direction, focused on “Knowledge as a service” and “Knowledge equity”. The direction is the result of months of discussions, surveys, interviews, and research to better understand the needs of communities, the vision of the movement, and future trends (like misinformation) relevant to the Wikimedia movement and its role in the ecosystem of knowledge. As a movement, we discussed what we shouldn’t change, what we should improve, and what would change around us. Several themes emerged from the mass of information and were further integrated into successive drafts of the direction. A stable version emerged shortly before the Wikimania conference in August and was discussed extensively online and in Montréal. It was rewritten, revised, refined, and eventually became the final version of the strategic direction. Beyond developing content as we have done in the past, the resulting direction is composed of two components: Knowledge as a service: To serve our users, we will become a platform that serves open knowledge to the world across interfaces and communities. We will build tools for allies and partners to organize and exchange free knowledge beyond Wikimedia. Our infrastructure will enable us and others to collect and use different forms of free, trusted knowledge. Knowledge equity: As a social movement, we will focus our efforts on the knowledge and communities that have been left out by structures of power and privilege. We will welcome people from every background to build strong and diverse communities. We will break down the social, political, and technical barriers preventing people from accessing and contributing to free knowledge. On October 26, groups and individuals started declaring their intent to work together towards this future by endorsing the direction. A week later, over 70 groups and organizations have already committed to participating in the next phase in good faith and to define, by Wikimania 2018, how to come to an agreement on roles, responsibilities, and organizational strategies that enable the movement to implement that future. The signatories include regional chapters from all around the world, thematic organizations, user groups, and the Wikimedia Foundation. Among their comments, some groups have expressed their hopes brought by the direction. CIS-A2K shared their “hopes that the divide between Global North and Global South will be bridged effectively”. The Wikimedians of Bashkortostan endorsed “with hope for more attention to the question of regional languages”. The Wikimedia Community User Group Brasil hopes that the direction “can be a guiding light for the whole movement on the path to healthier and more inclusive communities”. Individuals called the direction “Outstanding” and hoped for “un futuro como movimiento más equitativo y diverso“. Some even wrote essays about why the process and direction matter to them. A few Wikimedians also expressed their concerns with the text or the process. Many groups and individuals are now looking forward to the next steps of the process and to making the direction a reality, like Wikimedia Portugal‘s “group of new members committed to collaborate regularly in its implementation”. High-level planning for the next phase has started and will be further developed through November, notably by learning from what worked and didn’t work in the first phase. Some of the upcoming discussions will revolve around “big questions” like movement roles, governance, and decision making, while others will be more goal-oriented and will aim to build organizational strategies and multi-year strategic plans. Guillaume Paumier, co-lead architect, movement strategy Nicole Ebber, movement strategy track lead for organized groups Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Community, Foundation, Strategy, WikimediaTagged #Wikimedia2030, knowledge as a service, knowledge equity, Strategy, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2017/11/03/wikimedia-movement-new-direction/

cc40

In January 2017, the Wikimedia movement started an ambitious process to find alignment, rebuild trust, and identify a shared strategic direction for the 2030 horizon. Dozens of groups and organization

en

The National Emergency Crisis and Disasters Management Authority (NCEMA), in coordination with its main partners, has announced updating the Covid-19 countermeasures from tomorrow, February 26, 2022. The announcement comes in support of the ongoing efforts at the country level to achieve sustainable recovery while maintaining public health and safety against the background of the continuation of various activities and return to normalcy nationwide. According to the announcement, mask-wearing is mandatory in public indoor spaces and optional outdoors. It's also been decided to cancel the quarantine requirements for Covid-19 contacts. Covid contacts working in all state sectors have to conduct a PCR test daily for five days' time. NCEMA added that the isolation protocol for infected will continue as previously announced, without any change. The infected, however, will no longer wear wristbands. At the local level, each emirate has the flexibility to determine the duration of the quarantine period and PCR tests for Covid contacts in their respective sectors and professions, according to the vital sectors in the country, while necessarily maintaining the need to follow precautionary and preventive measures, which include adherence to physical distancing, and mask-wearing at all times. The authority also approved the return of the pre-pandemic time intervals between prayer calls and the iqaamah, in addition to the return of Noble Qur’an books to mosques in a limited number on the condition of being sterilised after each prayer. The current one-metre distance between worshipers in mosques and places of worship will also be maintained. Those coming to the UAE have to make sure to present an approved QR code- accompanied Covid-19 vaccination certificate containing a QR code; unvaccinated travelers have to present an approved negative PCR test result received within 48 hours, or a QR code-accompanied certificate of recovery from a Covid-19 infection obtained within one month from the date of travel. Travelers from the UAE have to follow the requirements of medical examinations and vaccinations in place in their countries of destination. NCEMA stressed the continuity of following the Green Pass requirement, or presenting a negative PCR test result of no more than 96 hours to attend all local events, exhibitions, and cultural and social activities. For economic and tourist sectors, physical distancing has been canceled while mask-wearing in closed places is still mandatory. The authority announced the return of all sports activities for all age groups, while obligating the public to follow the Green Pass protocol or present a negative PCR of not more than 96 hrs, in addition to maintaining the mandatory wearing of masks in all outdoor and indoor spaces given the turnout found in such activities. The authority calls on all community members to cooperate and adhere to preventive measures to confront the Covid-19, in order to preserve the gains being witnessed today in terms of recovery, crisis management, and comprehensive community health and safety. NCEMA stressed that the role of society in the next stage is not less important than the roles and responsibilities of the competent authorities to handle the pandemic, noting that the full return to normalcy requires commitment to preventive measures over the coming period.

https://covid19.ncema.gov.ae/en/News/Details/2316

cc40

The National Emergency Crisis and Disasters Management Authority (NCEMA), in coordination with its main partners, has announced updating the Covid-19 countermeasures from tomorrow, February 26, 2022.

en

(Update 2: The search interface was updated on May 20. This update addresses the problems where search query is truncated under some circumstances, and the problem that search suggestion is cut-off. Thank you for your prompt feedback.) (Update: We have received problem reports and feedback that search queries were truncated sometimes and the search suggestions were hard to read due to the limited width. In order to mitigate the problem, the new search function was disabled and the search field was increased by fifty percent. We also have updated the new search interface which we are currently staging on the prototype. This updates address the reported issues such as truncation of search queries and the problems that search suggestions are cut-off. Prototypes in various languages are also available here. Please try it out and let us know your feedback. Thanks!) Wikipedia has some new improvements, thanks to the hard work and dedication of over half a million beta testers and volunteers who worked with the Wikimedia User Experience team over the last year!  With a beta testing group of 635,000 people and an 83% user retention rate, we’re proud to introduce you to Wikipedia’s new look and feel.  As of 8:00am UTC today, the new features moved from beta and will be available for everyone to use.  This is the first major initiative the Wikimedia Foundation and its volunteers have ever undertaken for Wikipedia’s interface. And there’s more to come. It’s been one year since we began the usability initiative, and we’ve rolled out the new interface to Wikinews (English and Serbian), Wikimedia Commons, and now English Wikipedia. That means that hundreds of millions of people around the world will now experience an easier to use, and more importantly, easier to edit Wikipedia.  Our most recent interface launch, on Wikimedia Commons, was a great success with continued adoption by over 91% of Commons contributors. Over the next few weeks, the new interface will cascade to all language Wikipedias. Look and feel: We’ve introduced a new theme we call “Vector” which makes essential functions easier to find. Navigation: We’ve improved the navigation for reading and editing pages. Now, the tabs at the top of each page more clearly define whether you’re reading or editing a page. There’s also a collapsible navigation for the left sidebar that hides items that aren’t used often, but allows them to continue to be easily accessible. Editing improvements: We’ve reorganized the editing toolbar to make it easier to use. Now, formatting pages is simpler and more intuitive. And we’ve introduced a table wizard to make creating tables easier. You’ll also discover a new find and replace feature to simplify page editing. Link wizard: An easy-to-use tool allows you to add links to other pages on Wikipedia, or to pages on external sites. Search improvements: Search suggestions are now improved to get you to the page you are looking for more quickly. Pediapress book creator: Create a printed book by selecting Wikipedia articles and adding them to the Book Creator.  Your articles will be turned into a PDF (or OpenDocument) file so you can easily take Wikipedia wherever you go. Updated Puzzle globe and wordmark: The well-known Wikipedia globe and wordmark have been enhanced and improved. We’ve introduced Linux Libertine, an open source typeface to help support the creation of hundreds of localized Wikipedia wordmarks, and the internationally-recognized puzzle globe has been recreated in 3D and includes even more languages.  Read more from our recent blog post. We kicked off this effort in April 2009, and immediately went to work to figure out how to make Wikipedia easier to use for everyone.  We started with usability testing among everyday readers with no editing experience, and we learned about the way people interact with Wikipedia and how we could make the experience better.  Using this valuable information, we incrementally released new features to users who opted into our beta testing group.  Over the next several months, we continued to improve the features based on feedback from both our beta testers and from usability studies we conducted.  We’re thankful for the input of thousands of international users and volunteers who gave us feedback on our progress. During our initial beta testing phases, 81% of Spanish and Portuguese Wikipedia beta participants kept using  the new editing interface. Seventy to seventy-nine percent of German, Russian, Chinese, French and Italian Wikipedia beta users also maintained the new interface. Retention rates for Polish and Japanese were relatively low in the beginning (65% and 60%, respectively). Since then, we used feedback directly from our users all over the world to increase the quality of the interface and design. If you prefer the classic interface, called monobook (without the enhancements), don’t worry, you can click on the “Take me back” link at the top of the page to go back to the previous interface.  You’ll also be able to return to monobook interface whenever you’d like. With the support of hundreds of thousands of volunteers and the generous support from organizations like the Stanton Foundation, we’re making our projects easier for people from all parts of the world to contribute and access high-quality free educational information, which is central to our mission here at the Wikimedia Foundation. This isn’t the only project we plan to release to make it easier to use Wikipedia, and all of our Wikimedia projects; it’s just the first.  We’ve built an FAQ and feedback page which we encourage you to use — any feedback is valuable and will help us make our projects better. We’d like to thank the many volunteers who have supported the User Experience team since this project began, as well as the Foundation’s donors and supporters. Naoko Komura, Head of User Experience Programs Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. I really like the new look. Following is a suggestion for display of external links. Currently, if a link is external, this is indicated to the user by having a special symbol after it. I find that the symbol is a bit off-putting in text. Another way to indicate externality is to have external links become reverse video, instead of underlined, when hovered over. There is an example (on my site) at The interface wasn’t broken, you shouldn’t have tried to fix it. Looks good, I wonder if Media Wiki will make the “Vector” theme the default for all media wiki installations? The new design is nice enough, but I really don’t care for the seemingly arbitrary relocation of the search field to the top right of the page. We in the west read left to right, so naturally start at the left of the screen to assess what we’re looking at – at least I do. Placing the search field where it is now seems counter-intuitive and more work to find, especially after having it at the left for so long. Also, the field is just too small. Searching is such a huge component of experiencing Wikipedia – obviously! As it… Read more » can you please make an RSS feed for the main page. It will be the most popular RSS feed in the world! I’ve been trying out wikipedia beta. for several times before its launch today. It is really amazing.The design is so good. Thanks the wikimedia foundation I agree completely with Eric above. I had a tough time(few seconds)locating the search box because the first reaction was to find it in the collapsible menu items in the left pane. The top right corner was the last place I looked at. Overall the new look seems refreshing.Probably a shuffle of content boxes on the Main Page will add to the change. I totally agree with Eric and Abhijeet. Scientifiv research shows that web site users pay most intention to items in the top left part of a website. The search box being a very important part of the wikipedia pages, I really don’t see any advantage in putting it to the top right. It took me quite a while until I have found it, because I also started looking at the callapsible menus in the right part first. I am quite sure that you will confuse many users with this change. I really like the new look, but the search box… Read more » I’ve been using Vector from the beginning and while some serious issues remain, I consider it far superior to the old monobook skin. However, please fix the “Search” box! The text inside is horribly misaligned in Firefox. I’m a writer, and several years ago wrote my one and only Wikipedia article (James Robinson Risner). Later became increasingly horrified at how it was altered (IT WAS MINE!)……finally calmed down and realized Wikipedia is not perfect, but it is important. I hope y’all give some sort of special privileges for older guys (and girls) like me, who have been here since the early days. I always edit publicly — I don’t even know how to “sign in”! — and don’t really care about my anonymity, credit-for-contributing, etc. I just liked the good old days when we signed every change:… Read more » Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | The Internet Database […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | Technology and Web 2.0 […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] This new look is terrible, first youtube, then google….now wikipedia. Thank God there is an option to “take you back” this time. Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | Hooked On 'Tronics […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] The only change I mind is the search bar on the top right. It’s counter-intuitive. That was extremely unnecessary, what was the point in that? When is the package going to be available for the rest of us to use? I’m tired of the outdated look and want to update mine (without using the beta). How long should we expect to wait for the full version? BTW don’t like the search bar where it is. “Search improvements: Search suggestions are now improved to get you to the page you are looking for more quickly”, you say. But where is the option of searching for a word in the whole article space? If it’s still there, it’s hidden, and in either case that’s a new limitation, quite unnecessary. Otherwise, I haven’t looked around or adjusted yet, but I appreciate the amount of voluntary work going into things like this. Put the search box back in the menu on the left (or have two search boxes if you insist). Please. Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | Startup Websites […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] I always liked Wikipedia’s style. Now it looks better: light and modern Top of the page is the standard location for the search box (check e.g. Facebook or Youtube) so the current place seems better to me. Getting rid of the labels was also a good idea. I agree it is too small, though. Even back in 2002, Nielsen recommended 25 characters at least ( http://www.useit.com/alertbox/20020512.html ) – Vector has 16. Even worse is the search suggestion box not expanding when the content does not fit. It makes longer titles totally unreadable, and the search suggestions don’t take any screen real estate when not used so there would be no drawback to… Read more » First impression is that I like the new look; a little less cluttered and a little smoother. I wonder if there will be a new look each decade, so then people can say “that look was so naughties”. It will be interesting to see if sites like Conservapedia will follow suit. But, when I visit http://www.wikipedia.org, it still seems to have the old globe logo (maybe my cache?) At least on my Mac, the new stylesheet makes the text smaller by default. I know how to use browser options to make it bigger, but I worry that less tech-savvy users (e.g., many of the elderly) will be turned off from Wikipedia because it is now harder to read by default. Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | Viningmedia Nieuws […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Why did you change the font size for the main body of the text from “normal” to “almost too small to read comfortably”? Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo : Bloggii – The Global News Aggregator […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | Juegando […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Hi, left column width depends on text size. So if someone has smaller font than usual, logo is trimmed and looks ugly. Minimal width shuld be specified. Its very nice now and there is directly appears seearch box. . .so one can easily search in it. . . .nice very nice. . . I appreciate it . . . . The SEARCH bar should be in a more convenient place! If anything, it should appear where it says ‘Article’ ‘Discussion’ The new logo sucks. Additionally, there’s excess blank space at the top, but I’m most worried about the uglification of the logo. I had already gone back to the old look before I noticed what happened to the search box, but I agree with many previous posters – its new location isn’t good at all ! It’s just like separating the “article” and “edit” thumbnails. It scatters primordial functions all over the page, and you have to actually look for them, whereas the previous search box was easily found since it was with all the others menu items ! Frankly, I didn’t even see where the new search box had gone before reading tgr’s comment about it being top right. And by… Read more » Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | bruno trani dot info […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Nice update. When do you approve it for the other localisations of the wiki? I agree with the overall consensus: search and other items on the right is UNACCEPTABLE. With a very wide-screen monitor, it just is totally wrong for all the other standards in our left-to-right reading world. And it should hold more characters. Otherwise, I welcome the new interface and other improvements. I don’t mind the search box location, but one thing I believe is a serious error is making some of the menus / link sections (e.g. Languages) collapsed by default. I very often use Wikipedia in my work as a translator, looking up a term in the English-language version and then going to another language version of the article (Polish, in my case). I do this a minimum of a dozen times per day, on average. Today, I looked up an entry in the English Wikipedia, saw that there are no other language versions, and then continued to look for… Read more » Wikipedia Gets A Revamp, Better Search And Navigation – And An Updated Logo | The Good NET Guide […] look like that’s going to change anytime soon. This morning, the Wikimedia Foundation announced a number of changes it has made to make the experience for visitors and contributors […] Could you please update the wikipedia logo on wikipedia.org (not en.wikipedia, the main all language http://www.wikipedia.org.) Otherwise, it looks quite nice, but PUT THE DAMN SEARCH BOX BACK, FOR THE LOVE OF GOD PUT IT BACK NOW AHHHHH. Long life Wikipedia! Long life Wikipedia! Long life Wikipedia! I don’t like it. I don’t need it. I wish there was a simple query field in the middle of the screen on a white page with wikipedia logo and perhaps one or two options to edit or go to forum on top. Much like google page. Now THAT would be perfect. I think the search box needs to be on the left of the page; but right to the Wikipedia logo. In my opinion, though this may different from fact, the majority of people are going to want to search for another article than ‘discuss’ the writing of the article. And, now that the search box is on the right, it is competing with the native browser search box (in Safari, Firefox, Internet Explorer). So, the user will search via their preferred search engine for more information on a topic, and more often than not, the user will end up on… Read more » The text runs off the page at the right side on my 23-inch screen. I have to use that drag bar at the bottom to move the end of every line of type into view. In other words, it is not formatting to my screen. GRUMBLE. Please put the search box back on the left side of the page. I read from left to right. All your good work goes for naught if I can’t read the tiny type. Please! I like all of it except the location of the search field. It looks like you are ashamed of it so stick it miles away in the top corner of the screen – and with a 28″ monitor its a very long way away to quickly look for. For now I feel I HAVE to revert until that search box is moved +the search box is still way too small Wikipedia Gets Big Design Overhaul - News: Everything-e […] world will now experience an easier to use, and more importantly, easier to edit Wikipedia," says Naoko Komura, on behalf of the Wikimedia User Experience team. "Our most recent interface […] I like it all except the search being in top right. I liked it where it used to be. The average position of both my eyes and my mouse are the left, the old position was much better, and I would like that changed back (or made an option to be changed in our profile). Count me in with those who hate the new search box location. The top of the page is fine, but put it on the left. And what’s up with the text size? I like to keep my browser set for “smaller” text. On the new interface, that results in ridiculously tiny text. It’s a pain to have to reset the text size just because I come to Wikipedia. Posted in Highlights, MediaWiki, Technology, Usability initiative, WikipediaTagged Vector, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2010/05/13/a-new-look-for-wikipedia/

cc40

(Update 2: The search interface was updated on May 20. This update addresses the problems where search query is truncated under some circumstances, and the problem that search suggestion is cut-off. T

en

1 Department of Internal Medicine, School of Medicine, Amir al momenin Hospital, Zabol University of Medical Sciences, Zabol, Iran 2 Forensic medicine and toxicology, Zabol University of medical sciences, Zabol, Iran. 3 Department of Obstetrics and Gynecology, Medical Faculty, Zabol University of Medical Sciences, Zabol, Iran 4 Department of Pathology, School of Medicine, Zabol University of Medical Sciences, Zabol, Iran 5 Student Research Committee, zabol university of Medical Sciences, zabol, Iran 6 Social Medicine Department, Medical Facuty, Zabol University of Medical Sciences, Zabol, Iran 7 Department of Microbiology, Medical Faculty- Zabol University of Medical Sciences, Zabol, Iran Today, due to the increase in life expectancy in HIV-infected patients, the incidence of related diseases such as hepatitis B and C due to similarity in transmission routes has become a major concern of the health community. Therefore, this study was performed to determine the prevalence of hepatitis B among HIV + patients in Zabol. This descriptive cross-sectional study was performed on 37 HIV-infected patients in Zabol city (2021-2022). In the present study, HIV-infected patients were screened for hepatitis B by measuring serum levels of HBC Ab and HBs Ag. Finally, the data in SPSS V21 software were analyzed. In the present study, a total of 37 HIV-infected patients with a mean age of 40.81- 11.64 years were evaluated. The present study's prevalence of HIV and HCV co-infection was 21.6%. Also, 13.5% of HIV patients had HBV and HCV simultaneously. Examination of risk factors for viral hepatitis in HIV-infected patients showed that unprotected sex (100%), injecting drug use or IDU (87.5%), dental procedures (75%), history of imprisonment (62.5%) and tattooing (50.5%) were the most common factors in HIV patients. Family history of hepatitis B (12.5%), alcohol (12.5%), transfusion (12.5%) and cupping (25%) were among the lowest cases in these patients. the frequency of HBV infection and co-infection with HCV and HBV in HIV-positive patients were relatively high. Except for the history of tattoos, there is no significant relationship between other risk factors and hepatitis B among HIV-positive patients. Selected author of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Indolfi G, Easterbrook P, Dusheiko G, Siberry G, Chang M-H, Thorne C, Bulterys M, Chan P-L, El-Sayed MH, Giaquinto C (2019) Hepatitis B virus infection in children and adolescents. The Lancet Gastroenterology & Hepatology 4(6):466-476. doi:https://doi.org/10.1016/S2468-1253(19)30042-1 Thitipatarakorn S, Chinbunchorn T, Peelay J, Seekaew P, Amatavete S, Sangsai M, Pankam T, Avihingsanon A, Avery M, Phanuphak P (2022) Prevalence and the associated factors of hepatitis B and hepatitis C viral infections among HIV-positive individuals in same-day antiretroviral therapy initiation program in Bangkok, Thailand. BMC Public Health 22(1):1-9. doi:https://doi.org/10.1186/s12889-021-12429-6 Thio CL, Seaberg EC, Skolasky Jr R, Phair J, Visscher B, Muñoz A, Thomas DL (2002) HIV-1, hepatitis B virus, and risk of liver-related mortality in the Multicenter Cohort Study (MACS). The Lancet 360(9349):1921-1926. doi:https://doi.org/10.1016/S0140-6736(02)11913-1 Barin F (2022) HIV/AIDS as a model for emerging infectious disease: origin, dating and circumstances of an emblematic epidemiological success. La Presse Médicale):104128. doi:https://doi.org/10.1016/j.lpm.2022.104128 Kenfack-Momo R, Kenmoe S, Takuissu GR, Ebogo-Belobo JT, Kengne-Ndé C, Mbaga DS, Tchatchouang S, Oyono MG, Kenfack-Zanguim J, Lontuo Fogang R (2022) Epidemiology of hepatitis B virus and/or hepatitis C virus infections among people living with human immunodeficiency virus in Africa: A systematic review and meta-analysis. PloS one 17(5):e0269250. doi:https://doi.org/10.1371/journal.pone.0269250 Crowell TA, Gebo KA, Balagopal A, Fleishman JA, Agwu AL, Berry SA, Network HR (2014) Impact of hepatitis co-infection on hospitalization rates and causes in a multi-center cohort of persons living with HIV. Journal of acquired immune deficiency syndromes (1999) 65(4):429. doi:https://doi.org/10.1097%2FQAI.0000000000000059 Matthews PC, Geretti AM, Goulder PJ, Klenerman P (2014) Epidemiology and impact of HIV coinfection with hepatitis B and hepatitis C viruses in Sub-Saharan Africa. Journal of clinical virology 61(1):20-33. doi:https://doi.org/10.1016/j.jcv.2014.05.018 Liang X, Bi S, Yang W, Wang L, Cui G, Cui F, Zhang Y, Liu J, Gong X, Chen Y (2009) Epidemiological serosurvey of hepatitis B in China—declining HBV prevalence due to hepatitis B vaccination. Vaccine 27(47):6550-6557. doi:https://doi.org/10.1016/j.vaccine.2009.08.048 Zhang L, Guo J, Duan K (2019) Comparative analysis of the safety and efficacy of HBsAg-1018 versus HBsAg-Eng: A meta-analysis. Central European Journal of Immunology 44(4):455-462. doi:https://doi.org/10.5114/ceji.2019.92808 Wang H, Men P, Xiao Y, Gao P, Lv M, Yuan Q, Chen W, Bai S, Wu J (2019) Hepatitis B infection in the general population of China: a systematic review and meta-analysis. BMC infectious diseases 19(1):1-10. doi:https://doi.org/10.1186/s12879-019-4428-y Song C, Lv J, Liu Y, Chen JG, Ge Z, Zhu J, Dai J, Du L-B, Yu C, Guo Y (2019) Associations between hepatitis B virus infection and risk of all cancer types. JAMA network open 2(6):e195718-e195718. doi:https://doi.org/10.1001/jamanetworkopen.2019.5718 Hui C, Nan L, Ji ZH, Pu ZS, Guo ZW, Jie G, Shao ZJ, Liu YW, Yan YP (2020) Assessment on the effects of hepatitis B prevention and control measures in western China: a comparison of three population-based serosurveys. Biomedical and Environmental Sciences 33(10):735-744. doi:https://doi.org/10.3967/bes2020.098 Hou C, Hua Z, Xu P, Xu H, Wang Y, Liao J, Di B (2020) Estimating the prevalence of hepatitis B by wastewater-based epidemiology in 19 cities in China. Science of the Total Environment 740:139696. doi:https://doi.org/10.1016/j.scitotenv.2020.139696 Ayana DA, Mulu A, Mihret A, Seyoum B, Aseffa A, Howe R (2020) Occult Hepatitis B virus infection among HIV negative and positive isolated anti-HBc individuals in eastern Ethiopia. Scientific reports 10(1):1-9. doi:https://doi.org/10.1038/s41598-020-79392-x Hamilton E, Yang L, Mentzer AJ, Guo Y, Chen Y, Lv J, Fletcher R, Wright N, Lin K, Walters R (2022) Conventional and genetic risk factors for chronic Hepatitis B virus infection in a community-based study of 0.5 million Chinese adults. Scientific reports 12(1):1-11. doi:https://doi.org/10.1038/s41598-022-16360-7 Sun X, Zhu Y, Tang F, Deng X, Wang Z, Liu Y (2021) Analysis of epidemiological serosurvey of hepatitis B virus among people under 29 years of age in Jiangsu Province, China. Human vaccines & immunotherapeutics 17(10):3729-3734. doi:https://doi.org/10.1080/21645515.2021.1928461 Miao Z, Zhang S, Ou X, Li S, Ma Z, Wang W, Peppelenbosch MP, Liu J, Pan Q (2020) Estimating the global prevalence, disease progression, and clinical outcome of hepatitis delta virus infection. The Journal of infectious diseases 221(10):1677-1687. doi:https://doi.org/10.1093/infdis/jiz633 Dias J, Hengst J, Parrot T, Leeansyah E, Lunemann S, Malone DF, Hardtke S, Strauss O, Zimmer CL, Berglin L (2019) Chronic hepatitis delta virus infection leads to functional impairment and severe loss of MAIT cells. Journal of hepatology 71(2):301-312. doi:https://doi.org/10.1016/j.jhep.2019.04.009 Dore GJ, Soriano V, Rockstroh J, Kupfer B, Tedaldi E, Peters L, Neuhaus J, Puoti M, Klein MB, Mocroft A (2010) Frequent hepatitis B virus (HBV) rebound among HIV–HBV coinfected patients following antiretroviral therapy interruption in the SMART study. AIDS (London, England) 24(6):857. doi:https://doi.org/10.1097%2FQAD.0b013e328334bddb Singh KP, Crane M, Audsley J, Lewin SR (2017) HIV-Hepatitis B virus co-infection: epidemiology, pathogenesis and treatment. AIDS (London, England) 31(15):2035. doi:https://doi.org/10.1097%2FQAD.0000000000001574 Leumi S, Bigna JJ, Amougou MA, Ngouo A, Nyaga UF, Noubiap JJ (2020) Global burden of hepatitis B infection in people living with human immunodeficiency virus: a systematic review and meta-analysis. Clinical infectious diseases 71(11):2799-2806. doi:https://doi.org/10.1093/cid/ciz1170 Kafeero HM, Ndagire D, Ocama P, Walusansa A, Sendagire H (2020) Sero-prevalence of human immunodeficiency virus–hepatitis B virus (HIV–HBV) co-infection among pregnant women attending antenatal care (ANC) in sub-Saharan Africa (SSA) and the associated risk factors: a systematic review and meta-analysis. Virology journal 17(1):1-19. doi:https://doi.org/10.1186/s12985-020-01443-6 Ataei B, Tayeri K, Kassaian N, Farajzadegan Z, Babak A (2010) Hepatitis B and C among patients infected with human immunodeficiency virus in Isfahan, Iran: seroprevalence and associated factors. Hepatitis monthly 10(3):188. doi:PMCID: PMC3269083; PMID: 22308138 Nokhodian Z, Meshkati M, Adibi P, Ataei B, Kassaian N, Yaran M, Shoaei P, Hassannejad R (2012) Hepatitis C among intravenous drug users in Isfahan, Iran: a study of seroprevalence and risk factors. International journal of preventive medicine 3(Suppl1):S131. doi:PMCID: PMC3399288; PMID: 22826755 Tien PC (2005) Management and Treatment of Hepatitis C Virus Infection in HIV-Infected Adults: Recommendations from the Veterans Affairs Hepatitis C Resource Center Program and National Hepatitis C Program Office: 1. Official journal of the American College of Gastroenterology| ACG 100(10):2338-2354 Alavi SM, Etemadi A (2007) HIV/HBV, HIV/HCV and HIV/HTLV-1 co infection among injecting drug user patients hospitalized at the infectious disease ward of a training hospital in Iran. PAKISTAN JOURNAL OF MEDICAL SCIENCES 23(4):510-513 Ejele O, Nwauche C, Erhabor O (2004) The prevalence of hepatitis B surface antigenaemia in HIV positive patients in the Niger Delta Nigeria. Nigerian Journal of Medicine: Journal of the National Association of Resident Doctors of Nigeria 13(2):175-179. doi:PMID: 15293840 Yang H, Li X, Stanton B, Liu H, Liu H, Wang N, Fang X, Lin D, Chen X (2005) Heterosexual transmission of HIV in China: a systematic review of behavioral studies in the past two decades. Sexually transmitted diseases 32(5):270. doi:https://doi.org/10.1097%2F01.olq.0000162360.11910.5a Li X, Stanton B, Fang X, Lin D, Mao R, Wang J, Cottrell L, Harris C (2004) HIV/STD risk behaviors and perceptions among rural-to-urban migrants in China. AIDS education and prevention: official publication of the International Society for AIDS Education 16(6):538. doi:https://doi.org/10.1521%2Faeap.16.6.538.53787 Alam MM, Zaidi SZ, Malik SA, Shaukat S, Naeem A, Sharif S, Angez M, Butt JA (2007) Molecular epidemiology of Hepatitis B virus genotypes in Pakistan. BMC infectious diseases 7(1):1-6. doi:https://doi.org/10.1186/1471-2334-7-115 Weng MK, Doshani M, Khan MA, Frey S, Ault K, Moore KL, Hall EW, Morgan RL, Campos‐Outcalt D, Wester C (2022) Universal hepatitis B vaccination in adults aged 19–59 years: Updated recommendations of the advisory committee on immunization practices—United States, 2022. American Journal of Transplantation 22(6):1714-1720. doi:https://doi.org/10.1111/ajt.16661 Volume 1, Issue 3 Cellular, Molecular and Biomedical Reports Receive Date: 17 March 2021 Revise Date: 22 May 2021 Accept Date: 18 July 2021 First Publish Date: 01 December 2021 Rezaie-Kahkhaie, L., Saravani, K., Rezaie-Keikhaie, K., Azimi-Khatibani, S. E., Daman-Sooz, A. H., Afshari, M., & kamali, A. (2021). Prevalence of hepatitis B in HIV-positive patients in Zabol. Cellular, Molecular and Biomedical Reports, 1(3), 105-112. doi: 10.55705/cmbr.2021.356667.1058 Leli Rezaie-Kahkhaie; Khadije Saravani; Khadije Rezaie-Keikhaie; Seyed Esmaeil Azimi-Khatibani; Abdul Hafiz Daman-Sooz; Mehdi Afshari; Atefeh kamali. "Prevalence of hepatitis B in HIV-positive patients in Zabol". Cellular, Molecular and Biomedical Reports, 1, 3, 2021, 105-112. doi: 10.55705/cmbr.2021.356667.1058 Rezaie-Kahkhaie, L., Saravani, K., Rezaie-Keikhaie, K., Azimi-Khatibani, S. E., Daman-Sooz, A. H., Afshari, M., kamali, A. (2021). 'Prevalence of hepatitis B in HIV-positive patients in Zabol', Cellular, Molecular and Biomedical Reports, 1(3), pp. 105-112. doi: 10.55705/cmbr.2021.356667.1058 Rezaie-Kahkhaie, L., Saravani, K., Rezaie-Keikhaie, K., Azimi-Khatibani, S. E., Daman-Sooz, A. H., Afshari, M., kamali, A. Prevalence of hepatitis B in HIV-positive patients in Zabol. Cellular, Molecular and Biomedical Reports, 2021; 1(3): 105-112. doi: 10.55705/cmbr.2021.356667.1058 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_155089.html

cc40

1 Department of Internal Medicine, School of Medicine, Amir al momenin Hospital, Zabol University of Medical Sciences, Zabol, Iran 2 Forensic medicine and toxicology, Zabol University of medical scien

en

Prof. ِDr. Fleming Martinez Department of Pharmacy, Faculty of Sciences, Universidad Nacional de Colombia, South America, Colombia Physical pharmacy, Solubility, Solution thermodynamics, Pharmaceutics, History of Pharmacy Prof. ِDr. Sabu Thomas School of Chemical Sciences, Mahatma Gandhi University, Priyadarshini Hills P.O., Kottayam, Kerala 686 560, India Polymer Science & Engineering, Green Nanocomposites, bionanocomposites, Biomedical Sciences, Polymer Blends Prof. Dr. Nima Rezaei Tehran University of Medical Sciences; Universal Scientific Education and Research Network (USERN), Tehran, Iran Immunology, Genetics, Infectious, Diseases, Pediatrics Dr. Antonio Simone Laganà Department of Obstetrics and Gynecology, “Filippo Del Ponte” Hospital, University of Insubria, Varese, Italy Ph.D. at Endometriosis, Gynecological Endocrinology, Infertility, Assisted Reproduction Technologies, Reproductive Immunology, Minimally Invasive Gynecological Surgery (Laparoscopy, Hysteroscopy) Research interest: Endometriosis, Gynecological Endocrinology, Infertility, Assisted Reproduction Technologies, Reproductive Immunology, Minimally Invasive Gynecological Surgery (Laparoscopy, Hysteroscopy) Prof. Dr Haroon Khan Department of Pharmacy, Abdul Wali Khan University Mardan, Khyber-Pakhtunkhwa, Pakistan Drug Discovery from Natural h-index: in Google Scholar CV of Prof. Dr Haroon Khan Prof. Dr. Marcello Iriti Department of Biomedical, Surgical and Dental Sciences, Università degli Studi di Milano, Italy Plant Biology and Pathology h-index: in google scholar Professor of Plant Biology and Pathology at the Department of Biomedical, Surgical and Dental Sciences, Milan State University. He has been studying nutraceuticals, functional foods, phytotherapeutics and essential oils relevant for human and animal health, focusing on their preclinical (in vitro/in vivo) and in human pharmacological activities. He has been investigating the health-promoting effects of traditional Mediterranean diet as well as the ethnopharmacology of herbal remedies of traditional healing systems. Member of the World Academy of Sciences, Asian Council of Science Editors and Society of African Journal Editors. Founding Member of the Italian Society of Environmental Medicine. Member of the Working Group ‘Pharmacognosy, Phytotherapy and Nutraceuticals’ of the Italian Pharmacological Society. Main Patent: ‘Compositions Comprising Rutin Useful for the Treatment of Tumors Resistant to Chemotherapy’ (WO2015036875A1; US20160213698; US9757405B2; EP3043821). Orcid - https://orcid.org/0000-0002- 5063-1236 Publons - https://www.webofscience. com/wos/author/record/842879 Google scholar - https://scholar.google.it/ citations?user=9PwTCY8AAAAJ& hl=it&authuser=1 Homepage - https://www.unimi.it/en/ ugov/person/marcello-iriti Prof. Dr. Hassane Zouhal Department of Science and Techniques of Physical and Sporting Activities (STAPS), Université de Rennes 2, Rennes,France h-index: in Google Scholar Professor Dr. Mahendra Rai Department of Biotechnology, UGC-Basic Science Research Faculty Fellow, SGB Amravati University, Amravati- 444 602, Maharashtra, India h-index: in Google Scholar A Curriculum Vitae of Professor Mahendra Rai Prof. ِDr. Fleming Martinez Department of Pharmacy, Faculty of Sciences, Universidad Nacional de Colombia, South America, Colombia Physical pharmacy, Solubility, Solution thermodynamics, Pharmaceutics, History of Pharmacy h-index: in Google Scholar Prof. Dr. Irwin Rose Alencar de Menezes Pharmacology and Molecular Chemistry Laboratory, Department of Chemical Biology, Regional University of Cariri, CEP 63105-000, Crato, Ceara, Brazil Farmacologia, Química, Medicinal, Toxicologia, Produto Natural, Atividade biológica h-index: in Google Scholar Dr. Muhammad Tarek Abdel Ghafar Clinical Pathology, Faculty of Medicine, Tanta University, Tanta, Egypt Associate professor of clinical pathology h-index: in Google Scholar Scopus Author ID: 57201741255 Prof. Dr. Rayees U.H. Mattoo 1. Department of Structural Biology, Stanford University School of Medicine, Stanford, CA 94305, USA 2. Department of Plant Molecular Biology, Faculty of Biology and Medicine, University of Lausanne, 1015 Lausanne, Switzerland Biochemistry, Biophysics, structural Biology, CryoEM, Crystallography h-index: in Google Scholar Prof. Dr. Danial Kahrizi Department of Plant Production and Genetics, Faculty of Agriculture, Razi University, Kermanshah, Iran Professor in Plant Molecular Genetics and Genetic Engineering h-index: in Google Scholar A Curriculum Vitae of Professor D. Kahrizi Dr. Kawsar Ahmed Department of Information and Communication Technology, Mawlana Bhashani Science and Technology University, Santosh 1902, Tangail,Bangladesh Assistant Professor, Data Mining, Photonic Crystal Fiber, Bioinformatics, Image Processing h-index: in Google Scholar Dr. Seyed Ali Reza Mousavi Department of Neuroscience, Doris Neuroscience Center, 5The Scripps Research Institute, La Jolla, California 92037, USA Assistant Professor at Mechanotransduction, PIEZO, Ion Channels h-index: in Google Scholar The Article of Dr. Mousavi that Was published in Nature journal Prof. Dr. Hamid Ashrafi Plants for Human Health Institute, Department of Horticultural Science, North Carolina State University, Kannapolis, North Carolina, USA Bioinformatics, Genomics, Blueberry, Next Generation Sequencing h-index: in Google Scholar Dr. Bahman Fazeli-Nasab Research and Development Department, Giga Biotics, San Diego, California, USA Assistant Professor at Biotechnology h-index: in Google Scholar Prof. Dr. Gandla Kumaraswamy Department of Pharmaceutical Analysis, Chaitanya deemed to be University, Hanamkonda, Warangal, Telangana, India h-index: in Google scholar Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/journal/editorial.board

cc40

Prof. ِDr. Fleming Martinez Department of Pharmacy, Faculty of Sciences, Universidad Nacional de Colombia, South America, Colombia Physical pharmacy, Solubility, Solution thermodynamics, Pharmaceutics

en

Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue Document Type : Original Article 1 Research and Development Department, Giga Biotics, San Diego, California, USA 2 Department of Nursing, College of Nursing, Hawler Medical University, Erbil, Iraq 3 Department of Mathematics, Zhejiang Chinese Medical University, Zhejiang, China 4 Department of Urology, Icahn School of Medicine, Mount Sinai Hospitals, NY, USA Naproxen is a common analgesic and antipyretic medication that is widely used around the world. This medicine at high doses leads to liver and kidney necrosis in humans and animals. The mechanism of kidney damage, unlike liver damage, is not well understood and is one of the most common causes of emergency department patients. Therefore, in the present study, the protective effect of curcumin, a compound derived from turmeric, was investigated on renal damage caused by naproxen. For this purpose, 25 male Wistar rats were selected and were randomly divided into five groups. Naproxen was dissolved in a 5% dimethyl sulfoxide (DMSO) solution and was injected intraperitoneally at 1000 mg/kg of animal weight. Also, curcumin was dissolved in 5% DMSO and was injected within peritoneum at a dose of 200 mg/kg of animal weight into the relevant groups. After 24 hours of injection, rats were bled and plasma urea and creatinine levels were measured. The rate of lipid peroxidation, the activity of superoxide dismutase and catalase in the kidney, total plasma antioxidant capacity, and PGC-1a gene expression were measured. The results showed that naproxen significantly increased the levels of biochemical markers of urea and creatinine in plasma and lipid peroxidation in the kidney; also, it decreased the activity of the antioxidants enzymes. The use of curcumin in naproxen-exposed groups significantly reduced the concentrations of urea, creatinine, and lipid peroxidation. Curcumin increased the activity of catalase, superoxide enzymes, and the total antioxidant capacity of plasma. Also, curcumin increased the expression of the PGC-1a gene, which reduces the effects of naproxen. Therefore, according to the current study results, curcumin could significantly reduce the harmful effects of naproxen on the kidneys. However, in future studies, the effect of curcumin should be evaluated on the naproxen mechanism in the treatment of those patients who need naproxen. Selected author of this article by journal University of San Diego This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Sadrjavadi K, Shahlaei M, Bahrami G, Majnooni MB, Mohebbi M (2015) Comparison of correlation ranking and eigenvalue ranking unfolded principal component regression for direct determination of naproxen in human serum using excitation–emission matrix fluorescence spectroscopy. Journal of the Iranian Chemical Society 12(6):967-977. doi:http://doi.org/10.1007/s13738-014-0559-7 Czech B, Kończak M, Rakowska M, Oleszczuk P (2021) Engineered biochars from organic wastes for the adsorption of diclofenac, naproxen and triclosan from water systems. Journal of Cleaner Production 288:125686. doi:http://doi.org/10.1016/j.jclepro.2020.125686 Al-Zoubi N, Odeh F, Partheniadis I, Gharaibeh S, Nikolakakis I (2021) Spray drying of naproxen and naproxen sodium for improved tableting and dissolution–physicochemical characterization and compression performance. Pharmaceutical Development and Technology 26(2):193-208. doi:http://doi.org/10.1080/10837450.2020.1853769 Magni A, Agostoni P, Bonezzi C, Massazza G, Menè P, Savarino V, Fornasari D (2021) Management of osteoarthritis: expert opinion on NSAIDs. Pain and Therapy):1-26. doi:http://doi.org/10.1007/s40122-021-00260-1 García‐Martín E, García‐Menaya JM, Esguevillas G, Cornejo‐García JA, Doña I, Jurado‐Escobar R, Torres MJ, Blanca‐López N, Canto G, Blanca M (2021) Deep sequencing of prostaglandin‐endoperoxide synthase (PTGE) genes reveals genetic susceptibility for cross‐reactive hypersensitivity to NSAID. British Journal of Pharmacology 178(5):1218-1233. doi:http://doi.org/10.1111/bph.15366 Liu M, Guo M-N, Chen L-H (2021) Research advances of prostaglandin E 2 synthases and receptors in cardiovascular diseases. Sheng li xue bao:[Acta Physiologica Sinica] 73(4):665-680. doi:http://doi.org/10.1042/BST20140016 Nishi O (2021) Comment on: Intraindividual comparison of cytokine and prostaglandin levels with and without low-energy, high-frequency femtosecond laser cataract pretreatment after single-dose topical NSAID application. Journal of Cataract & Refractive Surgery 47(2):280-281. doi:http://doi.org/10.1097/j.jcrs.0000000000000573 Bernardi M, Lazzeri L, Perelli F, Reis FM, Petraglia F (2017) Dysmenorrhea and related disorders. F1000Research 6. doi:http://doi.org/10.12688/f1000research.11682.1 Hall JE, do Carmo JM, da Silva AA, Wang Z, Hall ME (2019) Obesity, kidney dysfunction and hypertension: mechanistic links. Nature reviews nephrology 15(6):367-385. doi:http://doi.org/10.1038/s41581-019-0145-4 Dizaji R, Sharafi A, Pourahmad J, Vatanpour S, Hosseini M-J, Vatanpour H (2020) The effects of Hemiscorpius lepturus induced-acute kidney injury on PGC-1a gene expression: From induction to suppression in mice. Toxicon 174:57-63. doi:http://doi.org/10.1016/j.toxicon.2019.12.154 Fontecha‐Barriuso M, Martín‐Sánchez D, Martinez‐Moreno JM, Carrasco S, Ruiz‐Andrés O, Monsalve M, Sanchez‐Ramos C, Gómez MJ, Ruiz‐Ortega M, Sánchez‐Niño MD (2019) PGC‐1a deficiency causes spontaneous kidney inflammation and increases the severity of nephrotoxic AKI. The Journal of pathology 249(1):65-78. doi:http://doi.org/10.1002/path.5282 Katsouri L, Parr C, Bogdanovic N, Willem M, Sastre M (2011) PPARY co-activator-1a (PGC-1a) reduces amyloid-B generation through a PPARY-dependent mechanism. Journal of Alzheimer's Disease 25(1):151-162. doi:http://doi.org/10.3233/JAD-2011-101356 Sriperumbuduri S, Hiremath S (2019) The case for cautious consumption: NSAIDs in chronic kidney disease. Current opinion in nephrology and hypertension 28(2):163-170. doi:http://doi.org/10.1097/MNH.0000000000000473 Hörl WH (2010) Nonsteroidal anti-inflammatory drugs and the kidney. Pharmaceuticals 3(7):2291-2321. doi:http://doi.org/10.3390/ph3072291 Ejaz P, Bhojani K, Joshi V (2004) NSAIDs and kidney. Japi 52(632-640):371. doi:https://doi.org/10.3390/ph3072291 S Darvesh A, B Aggarwal B, Bishayee A (2012) Curcumin and liver cancer: a review. Current pharmaceutical biotechnology 13(1):218-228. doi:http://doi.org/10.2174/138920112798868791 Li S, Wang X, Xiao Y, Wang Y, Wan Y, Li X, Li Q, Tang X, Cai D, Ran B (2021) Curcumin ameliorates mercuric chloride-induced liver injury via modulating cytochrome P450 signaling and Nrf2/HO-1 pathway. Ecotoxicology and Environmental Safety 208:111426. doi:http://doi.org/10.1016/j.ecoenv.2020.111426 Abraham P (2005) Vitamin C may be beneficial in the prevention of paracetamol-induced renal damage. Clinical and experimental nephrology 9(1):24-30. doi:http://doi.org/10.1007/s10157-004-0335-6 Niki E (2008) Lipid peroxidation products as oxidative stress biomarkers. Biofactors 34(2):171-180. doi:http://doi.org/10.1002/biof.5520340208 McCord JM, Fridovich I (1969) Superoxide dismutase: an enzymic function for erythrocuprein (hemocuprein). Journal of Biological chemistry 244(22):6049-6055. doi:http://doi.org/10.1016/S0021-9258(18)63504-5 Aebi H (1983) Catalase. Catalase In: Bergmeyer, HU, Ed, Methods of Enzymatic Analysis, Verlag Chemie, Weinhem):273- 286. doi:http://doi.org/10.1016/S0076-6879(84)05016-3 Prior RL, Gu L, Wu X, Jacob RA, Sotoudeh G, Kader AA, Cook RA (2007) Plasma antioxidant capacity changes following a meal as a measure of the ability of a food to alter in vivo antioxidant status. Journal of the American College of Nutrition 26(2):170-181. doi:http://doi.org/10.1080/07315724.2007.10719599 Costes SV, Daelemans D, Cho EH, Dobbin Z, Pavlakis G, Lockett S (2004) Automatic and quantitative measurement of protein-protein colocalization in live cells. Biophysical journal 86(6):3993-4003. doi:http://doi.org/10.1529/biophysj.103.038422 Hunter LJ, Wood DM, Dargan PI (2011) The patterns of toxicity and management of acute nonsteroidal anti-inflammatory drug (NSAID) overdose. Open access emergency medicine: OAEM 3:39. doi:http://doi.org/10.2147/OAEM.S22795 Weir MR (2002) Renal effects of nonselective NSAIDs and coxibs. Cleveland Clinic journal of medicine 69(1):53-58. doi:http://doi.org/10.3949/ccjm.69.suppl_1.si53 Whelton A, Schulman G, Wallemark C, Drower EJ, Isakson PC, Verburg KM, Geis GS (2000) Effects of celecoxib and naproxen on renal function in the elderly. Archives of Internal Medicine 160(10):1465-1470. doi:http://doi.org/10.1001/archinte.160.10.1465 Kovacevic L, Bernstein J, Valentini RP, Imam A, Gupta N, Mattoo TK (2003) Renal papillary necrosis induced by naproxen. Pediatric Nephrology 18(8):826-829. doi:http://doi.org/10.1007/s00467-003-1167-4 Castaño PR, Parween S, Pandey AV (2019) Bioactivity of curcumin on the cytochrome P450 enzymes of the steroidogenic pathway. International journal of molecular sciences 20(18):4606. doi:http://doi.org/10.3390/ijms20184606 Reddy ACP, Lokesh B (1994) Effect of dietary turmeric (Curcuma longa) on iron-induced lipid peroxidation in the rat liver. Food and chemical toxicology 32(3):279-283. doi:http://doi.org/10.1016/0278-6915(94)90201-1 Chainoglou E, Hadjipavlou-Litina D (2020) Curcumin in health and diseases: Alzheimer’s disease and curcumin analogues, derivatives, and hybrids. International Journal of Molecular Sciences 21(6):1975. doi:https://doi.org/10.3390/ijms21061975 Jiang M, Wei Q, Pabla N, Dong G, Wang C-Y, Yang T, Smith SB, Dong Z (2007) Effects of hydroxyl radical scavenging on cisplatin-induced p53 activation, tubular cell apoptosis and nephrotoxicity. Biochemical pharmacology 73(9):1499-1510. doi:http://doi.org/10.1016/j.bcp.2007.01.010 Weisel T, Baum M, Eisenbrand G, Dietrich H, Will F, Stockis JP, Kulling S, Rüfer C, Johannes C, Janzowski C (2006) An anthocyanin/polyphenolic‐rich fruit juice reduces oxidative DNA damage and increases glutathione level in healthy probands. Biotechnology Journal: Healthcare Nutrition Technology 1(4):388-397. doi:http://doi.org/10.1002/biot.200600004 Abuhijleh AL, Khalaf J (2010) Copper (II) complexes of the anti-inflammatory drug naproxen and 3-pyridylmethanol as auxiliary ligand. Characterization, superoxide dismutase and catecholase–mimetic activities. European journal of medicinal chemistry 45(9):3811-3817. doi:http://doi.org/10.1016/j.ejmech.2010.05.031 Ahmad MH, Fatima M, Hossain M, Mondal AC (2018) Evaluation of naproxen-induced oxidative stress, hepatotoxicity and in-vivo genotoxicity in male Wistar rats. Journal of pharmaceutical analysis 8(6):400-406. doi:http://doi.org/10.1016/j.jpha.2018.04.002 Rakotoarisoa M, Angelov B, Espinoza S, Khakurel K, Bizien T, Angelova A (2019) Cubic liquid crystalline nanostructures involving catalase and curcumin: BioSAXS study and catalase peroxidatic function after cubosomal nanoparticle treatment of differentiated SH-SY5Y cells. Molecules 24(17):3058. doi:http://doi.org/10.3390/molecules24173058 Najjar FM, Ghadari R, Yousefi R, Safari N, Sheikhhasani V, Sheibani N, Moosavi-Movahedi AA (2017) Studies to reveal the nature of interactions between catalase and curcumin using computational methods and optical techniques. International journal of biological macromolecules 95:550-556. doi:http://doi.org/10.1016/j.ijbiomac.2016.11.050 Gómez-Estaca J, Balaguer M, López-Carballo G, Gavara R, Hernández-Muñoz P (2017) Improving antioxidant and antimicrobial properties of curcumin by means of encapsulation in gelatin through electrohydrodynamic atomization. Food Hydrocolloids 70:313-320. doi:http://doi.org/10.1016/j.foodhyd.2017.04.019 Salimi A, Neshat MR, Naserzadeh P, Pourahmad J (2019) Mitochondrial permeability transition pore sealing agents and antioxidants protect oxidative stress and mitochondrial dysfunction induced by naproxen, diclofenac and celecoxib. Drug research 69(11):598-605. doi:http://doi.org/10.1055/a-0866-9356 Wang X, Shen K, Wang J, Liu K, Wu G, Li Y, Luo L, Zheng Z, Hu D (2020) Hypoxic preconditioning combined with curcumin promotes cell survival and mitochondrial quality of bone marrow mesenchymal stem cells, and accelerates cutaneous wound healing via PGC-1a/SIRT3/HIF-1a signaling. Free Radical Biology and Medicine 159:164-176. doi:http://doi.org/10.1016/j.freeradbiomed.2020.07.023 Silva J, Spatz MH, Folk C, Chang A, Cadenas E, Liang J, Davies DL (2021) Dihydromyricetin improves mitochondrial outcomes in the liver of alcohol-fed mice via the AMPK/Sirt-1/PGC-1a signaling axis. Alcohol 91:1-9. doi:http://doi.org/10.1016/j.alcohol.2020.10.002 Volume 1, Issue 1 - Serial Number 1 Cellular, Molecular and Biomedical Reports Receive Date: 05 August 2021 Revise Date: 15 September 2021 Accept Date: 16 October 2021 First Publish Date: 16 October 2021 Aziziaram, Z., Bilal, I., Zhong, Y., Mahmod, A., & Roshandel, M. R. (2021). Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue. Cellular, Molecular and Biomedical Reports, 1(1), 23-32. doi: 10.55705/cmbr.2021.138879.1001 Zahra Aziziaram; Ismael Bilal; Yuan Zhong; Azzadin Kamal Mahmod; Mohammad Reza Roshandel. "Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue". Cellular, Molecular and Biomedical Reports, 1, 1, 2021, 23-32. doi: 10.55705/cmbr.2021.138879.1001 Aziziaram, Z., Bilal, I., Zhong, Y., Mahmod, A., Roshandel, M. R. (2021). 'Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue', Cellular, Molecular and Biomedical Reports, 1(1), pp. 23-32. doi: 10.55705/cmbr.2021.138879.1001 Aziziaram, Z., Bilal, I., Zhong, Y., Mahmod, A., Roshandel, M. R. Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue. Cellular, Molecular and Biomedical Reports, 2021; 1(1): 23-32. doi: 10.55705/cmbr.2021.138879.1001 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_138879.html

cc40

Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding P

en

Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital Document Type : Original Article Qassim hassan Aubais aljelehawy 1, 2 Layth Hussein Hadi Alshaibah 1, 2 Zahraa Khudhair Abbas Al- Khafaji 1, 2 1 Medical Laboratory Technique Department, The Islamic University, Diwaniya, Iraq 2 Research and Studies Department, The Islamic University, Najaf, Iraq Staphylococcus aureus contains numerous surface proteins called microbial surface components recognizing adhesive matrix molecules (MSCRAMMs) that mediate binding to host tissues and initiate colonization leading to infection. Virulence genes such as enzymes, toxins, adhesin proteins, cell surface proteins play an important role in the pathogenicity of S. aureus strains. The distribution and prevalence of virulence genes vary among S. aureus strains in different regions. However, the highest frequency of virulence genes among S. aureus strains is related to toxin genes. There are many PCR methods for detecting these microorganisms such as conventional PCR, multiplex PCR, reverse transcription PCR (RT-PCR), and quantitative PCR (qPCR). Therefore, this study aimed to investigate the presence of virulence genes among methicillin-resistant S. aureus (MRSA) strains. In this study, multiplex PCR technique was applied to determine the presence of virulence genes among MRSA strains. Results showed the frequency of virulence genes among bacterial strains isolated from Al-Najaf Al-Ashraf teaching hospital. In addition, among the strains, hla gene with 91% frequency, exhibited the highest prevalence among pathogenic genes. Sea, mecA, clfB, femA, fnbB, tsst, hlb genes with 88%, 65%, 54%, 45%, 39%, 27% and 13% were in the next ranks, respectively. This investigation showed mecA is a gene found in bacterial cells that allows them to be resistant to antibiotics such as methicillin and other penicillin-like antibiotics. Selected author of this article by journal ِDr. Qassim hassan Aubais aljelehawy Researchgate ; Google Scholar This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Abbas-Al-Khafaji ZK, Aubais-aljelehawy Qh (2021) Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-Yarmouk hospital. Cellular, Molecular and Biomedical Reports 1(2):60-68 Alavi M, Rai M (2021) Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports 1(2):52-59 Almasian-Tehrani N, Alebouyeh M, Armin S, Soleimani N, Azimi L, Shaker-Darabad R (2021) Overview of typing techniques as molecular epidemiology tools for bacterial characterization. Cellular, Molecular and Biomedical Reports 1(2):69-77 Alavi M, Adulrahman NA, Haleem AA, Al-Râwanduzi ADH, Khusro A, Abdelgawad MA, Ghoneim MM, Batiha GE-S, Kahrizi D, Martinez F, Koirala N (2022) Nanoformulations of curcumin and quercetin with silver nanoparticles for inactivation of bacteria. Cellular and Molecular Biology 67(5):151-156. doi:https://doi.org/10.14715/cmb/2021.67.5.21 Aljelehawy Q, Karimi N, Alavi M (2021) Comparison of antibacterial and cytotoxic activities of phytosynthesized ZnONPs by leaves extract of Daphne mucronata at different salt sources. Materials Technology 36(12):747-759. doi:https://doi.org/10.1080/10667857.2020.1794280 Alavi M, Karimi N (2022) Antibacterial, hemoglobin/albumin-interaction, and molecular docking properties of phytogenic AgNPs functionalized by three antibiotics of penicillin, amoxicillin, and tetracycline. Microbial Pathogenesis 164:105427. doi:https://doi.org/10.1016/j.micpath.2022.105427 Becker K, Skov RL, von Eiff C (2015) Staphylococcus, Micrococcus, and Other Catalase-Positive Cocci. In: Manual of Clinical Microbiology. pp 354-382. doi:https://doi.org/10.1128/9781555817381.ch21 Diekema DJ, Pfaller MA, Schmitz FJ, Smayevsky J, Bell J, Jones RN, Beach M (2001) Survey of infections due to Staphylococcus species: frequency of occurrence and antimicrobial susceptibility of isolates collected in the United States, Canada, Latin America, Europe, and the Western Pacific region for the SENTRY Antimicrobial Surveillance Program, 1997-1999. Clinical infectious diseases : an official publication of the Infectious Diseases Society of America 32 Suppl 2:S114-132. doi:https://doi.org/10.1086/320184 Stein GE, Wells EM (2010) The importance of tissue penetration in achieving successful antimicrobial treatment of nosocomial pneumonia and complicated skin and soft-tissue infections caused by methicillin-resistant Staphylococcus aureus: vancomycin and linezolid. Current Medical Research and Opinion 26(3):571-588. doi:https://doi.org/10.1185/03007990903512057 Kadariya J, Smith TC, Thapaliya D (2014) Staphylococcus aureus and Staphylococcal Food-Borne Disease: An Ongoing Challenge in Public Health. BioMed Research International 2014:827965. doi:https://doi.org/10.1155/2014/827965 Tuomanen EI, Que Y-A, François P, Haefliger J-A, Entenza J-M, Vaudaux P, Moreillon P (2001) Reassessing the Role of Staphylococcus aureus Clumping Factor and Fibronectin-Binding Protein by Expression in Lactococcus lactis. Infection and Immunity 69(10):6296-6302. doi:https://doi.org/10.1128/IAI.69.10.6296-6302.2001 Foster TJ (2016) The remarkably multifunctional fibronectin binding proteins of Staphylococcus aureus. European Journal of Clinical Microbiology & Infectious Diseases 35(12):1923-1931. doi:https://doi.org/10.1007/s10096-016-2763-0 Grumann D, Nübel U, Bröker BM (2014) Staphylococcus aureus toxins – Their functions and genetics. Infection, Genetics and Evolution 21:583-592. doi:https://doi.org/10.1016/j.meegid.2013.03.013 Tuomanen EI, Karlsson A, Saravia-Otten P, Tegmark K, Morfeldt E, Arvidson S (2001) Decreased Amounts of Cell Wall-Associated Protein A and Fibronectin-Binding Proteins in Staphylococcus aureus sarA Mutants due to Up-Regulation of Extracellular Proteases. Infection and Immunity 69(8):4742-4748. doi:https://doi.org/10.1128/IAI.69.8.4742-4748.2001 Oliveira D, Borges A, Simões M (2018) Staphylococcus aureus Toxins and Their Molecular Activity in Infectious Diseases. Toxins 10(6):252 Otto M (2010) Staphylococcus colonization of the skin and antimicrobial peptides. Expert Review of Dermatology 5(2):183-195. doi:https://doi.org/10.1586/edm.10.6 Peschel A, Otto M (2013) Phenol-soluble modulins and staphylococcal infection. Nature Reviews Microbiology 11(10):667-673. doi:https://doi.org/10.1038/nrmicro3110 Houri H, Samadpanah M, Tayebi Z, Norouzzadeh R, Malekabad ES, Dadashi A-R (2020) Investigating the toxin profiles and clinically relevant antibiotic resistance genes among Staphylococcus aureus isolates using multiplex-PCR assay in Tehran, Iran. Gene Reports 19:100660. doi:https://doi.org/10.1016/j.genrep.2020.100660 Budzyńska A, Skowron K, Kaczmarek A, Wietlicka-Piszcz M, Gospodarek-Komkowska E (2021) Virulence Factor Genes and Antimicrobial Susceptibility of Staphylococcus aureus Strains Isolated from Blood and Chronic Wounds. Toxins 13(7). doi:https://doi.org/10.3390/toxins13070491 Loges LA, Silva DB, Paulino GVB, Landell MF, Macedo AJ (2020) Polyketides from marine-derived Aspergillus welwitschiae inhibit Staphylococcus aureus virulence factors and potentiate vancomycin antibacterial activity in vivo. Microbial Pathogenesis 143:104066. doi:https://doi.org/10.1016/j.micpath.2020.104066 Arciola CR, Campoccia D, Montanaro L (2018) Implant infections: adhesion, biofilm formation and immune evasion. Nature Reviews Microbiology 16(7):397-409. doi:https://doi.org/10.1038/s41579-018-0019-y Xiong M, Zhao J, Huang T, Wang W, Wang L, Zhao Z, Li X, Zhou J, Xiao X, Pan Y, Lin J, Li Y (2020) Molecular Characteristics, Virulence Gene and Wall Teichoic Acid Glycosyltransferase Profiles of Staphylococcus aureus: A Multicenter Study in China. Frontiers in Microbiology 11. doi:https://doi.org/10.3389/fmicb.2020.02013 Wang X, Liu Q, Zhang H, Li X, Huang W, Fu Q, Li M (2018) Molecular Characteristics of Community-Associated Staphylococcus aureus Isolates From Pediatric Patients With Bloodstream Infections Between 2012 and 2017 in Shanghai, China. Frontiers in Microbiology 9. doi:https://doi.org/10.3389/fmicb.2018.01211 Zhao H, Xu S, Yang H, He C, Xu X, Hu F, Shu W, Gong F, Zhang C, Liu Q (2019) Molecular Typing and Variations in Amount of tst Gene Expression of TSST-1-Producing Clinical Staphylococcus aureus Isolates. Frontiers in Microbiology 10. doi:https://doi.org/10.3389/fmicb.2019.01388 Zi C, Zeng D, Ling N, Dai J, Xue F, Jiang Y, Li B (2018) An improved assay for rapid detection of viable Staphylococcus aureus cells by incorporating surfactant and PMA treatments in qPCR. BMC Microbiology 18(1):132. doi:https://doi.org/10.1186/s12866-018-1273-x Fraunholz M, Sinha B (2012) Intracellular Staphylococcus aureus: live-in and let die. Frontiers in cellular and infection microbiology 2:43. doi:https://doi.org/10.3389/fcimb.2012.00043 Mehrotra M, Wang G, Johnson WM (2000) Multiplex PCR for detection of genes for Staphylococcus aureus enterotoxins, exfoliative toxins, toxic shock syndrome toxin 1, and methicillin resistance. Journal of clinical microbiology 38(3):1032-1035. doi:https://doi.org/10.1128/JCM.38.3.1032-1035.2000 Eftekhar F, Rezaee R, Azad M, Azimi H, Goudarzi H, Goudarzi M (2017) Distribution of Adhesion and Toxin Genes in Staphylococcus aureus Strains Recovered From Hospitalized Patients Admitted to the ICU. Arch Pediatr Infect Dis 5(1):e39349. doi:https://doi.org/10.5812/pedinfect.39349 Tavares A, Nielsen JB, Boye K, Rohde S, Paulo AC, Westh H, Schønning K, de Lencastre H, Miragaia M (2014) Insights into alpha-hemolysin (Hla) evolution and expression among Staphylococcus aureus clones with hospital and community origin. PLoS One 9(7):e98634-e98634. doi:https://doi.org/10.1371/journal.pone.0098634 Kmieciak W, Szewczyk EM, Ciszewski M (2016) Searching for Beta-Haemolysin hlb Gene in Staphylococcus pseudintermedius with Species-Specific Primers. Curr Microbiol 73(1):148-152. doi:https://doi.org/10.1007/s00284-016-1038-4 Costa AM, Kay I, Palladino S (2005) Rapid detection of mecA and nuc genes in staphylococci by real-time multiplex polymerase chain reaction. Diagnostic microbiology and infectious disease 51(1):13-17. doi:https://doi.org/10.1016/j.diagmicrobio.2004.08.014 Kamarehei F, Ghaemi EA, Dadgar T (2013) Prevalence of enterotoxin A and B genes in Staphylococcus aureus isolated from clinical samples and healthy carriers in Gorgan City, North of Iran. Indian journal of pathology & microbiology 56(3):265-268. doi:https://doi.org/10.4103/0377-4929.120388 Kreiswirth BN, Projan SJ, Schlievert PM, Novick RP (1989) Toxic shock syndrome toxin 1 is encoded by a variable genetic element. Reviews of infectious diseases 11 Suppl 1:S83-88; discussion S88-89. doi:https://doi.org/10.1093/clinids/11.supplement_1.s83 Nagao M, Okamoto A, Yamada K, Hasegawa T, Hasegawa Y, Ohta M (2009) Variations in amount of TSST-1 produced by clinical methicillin resistant Staphylococcus aureus (MRSA) isolates and allelic variation in accessory gene regulator (agr) locus. BMC Microbiol 9:52. doi:https://doi.org/10.1186/1471-2180-9-52 Xie Y, He Y, Gehring A, Hu Y, Li Q, Tu S-I, Shi X (2011) Genotypes and Toxin Gene Profiles of Staphylococcus aureus Clinical Isolates from China. PLoS One 6(12):e28276. doi:https://doi.org/10.1371/journal.pone.0028276 Pakbaz Z, Sahraian MA, Sabzi S, Mahmoodi M, Pourmand MR (2017) Prevalence of sea, seb, sec, sed, and tsst-1 genes of Staphylococcus aureus in nasal carriage and their association with multiple sclerosis. Germs 7(4):171-177. doi:https://doi.org/10.18683/germs.2017.1123 Thalsø-Madsen I, Torrubia FR, Xu L, Petersen A, Jensen C, Frees D (2019) The Sle1 Cell Wall Amidase Is Essential for B-Lactam Resistance in Community-Acquired Methicillin-Resistant Staphylococcus aureus USA300. Antimicrob Agents Chemother 64(1):e01931-01919. doi:https://doi.org/10.1128/AAC.01931-19 Galdiero E, Liguori G, D'Isanto M, Damiano N, Sommese L (2003) Distribution of mecA among methicillin-resistant clinical staphylococcal strains isolated at hospitals in Naples, Italy. European Journal of Epidemiology 18(2):139-145. doi:https://doi.org/10.1023/A:1023067930211 Choi SM, Kim SH, Kim HJ, Lee DG, Choi JH, Yoo JH, Kang JH, Shin WS, Kang MW (2009) Multiplex PCR for the Detection of Genes Encoding Aminoglycoside Modifying Enzymes and Methicillin Resistance among Staphylococcus Species. jkms 18(5):631-636. doi:https://doi.org/10.3346/jkms.2003.18.5.631 Askari E, Soleymani F, Arianpoor A, Tabatabai SM, Amini A, Naderinasab M (2012) Epidemiology of mecA-Methicillin Resistant Staphylococcus aureus (MRSA) in Iran: A Systematic Review and Meta-analysis. Iran J Basic Med Sci 15(5):1010-1019 Li X, Xiong Y, Fan X, Feng P, Tang H, Zhou T (2012) The role of femA regulating gene on methicillin-resistant Staphylococcus aureus clinical isolates. Médecine et Maladies Infectieuses 42(5):218-225. doi:https://doi.org/10.1016/j.medmal.2008.09.031 Kobayashi N, Wu H, Kojima K, Taniguchi K, Urasawa S, Uehara N, Omizu Y, Kishi Y, Yagihashi A, Kurokawa I (1994) Detection of mecA, femA, and femB genes in clinical strains of staphylococci using polymerase chain reaction. Epidemiology and Infection 113(2):259-266. doi:https://doi.org/10.1017/S0950268800051682 Breves A, Miranda CAC, Flores C, Filippis Id, Clementino MM (2015) Methicillin-and vancomycin-resistant Staphylococcus aureus in health care workers and medical devices. Jornal brasileiro de patologia e medicina laboratorial 51:143-152. doi: https://doi.org/10.5935/1676-2444.20150025 Xiao M, Zhao R, Zhang Q, Fan X, O’Sullivan MVN, Li D-F, Wang X-Y, Wu H-L, Kong F, Xu Y-C (2016) Genotypic Diversity of Staphylococcus aureus a-Hemolysin Gene (hla) and Its Association with Clonal Background: Implications for Vaccine Development. PLoS One 11(2):e0149112. doi:https://doi.org/10.1371/journal.pone.0149112 Zhang D-X, Li Y, Yang X-Q, Su H-Y, Wang Q, Zhang Z-H, Liu Y-C, Tian C-L, Cui C-C, Liu M-C (2020) In vitro Antibiotic Susceptibility, Virulence Genes Distribution and Biofilm Production of Staphylococcus aureus Isolates from Bovine Mastitis in the Liaoning Province of China. Infect Drug Resist 13:1365-1375. doi:https://doi.org/10.2147/IDR.S247765 Ren Q, Liao G, Wu Z, Lv J, Chen W (2020) Prevalence and characterization of Staphylococcus aureus isolates from subclinical bovine mastitis in southern Xinjiang, China. Journal of Dairy Science 103(4):3368-3380. doi:https://doi.org/10.3168/jds.2019-17420 Nemati M, Hermans K, Devriese LA, Maes D, Haesebrouck F (2009) Screening of genes encoding adhesion factors and biofilm formation in Staphylococcus aureus isolates from poultry. Avian Pathology 38(6):513-517. doi:https://doi.org/10.1080/03079450903349212 Burke FM, McCormack N, Rindi S, Speziale P, Foster TJ (2010) Fibronectin-binding protein B variation in Staphylococcus aureus. BMC Microbiology 10(1):160. doi:https://doi.org/10.1186/1471-2180-10-160 Kot B, Szweda P, Frankowska-Maciejewska A, Piechota M, Wolska K (2016) Virulence gene profiles in Staphylococcus aureus isolated from cows with subclinical mastitis in eastern Poland. Journal of Dairy Research 83(2):228-235. doi:https://doi.org/10.1017/S002202991600008X Volume 1, Issue 2 - Serial Number 2 Cellular, Molecular and Biomedical Reports Receive Date: 05 June 2021 Revise Date: 14 August 2021 Accept Date: 18 October 2021 First Publish Date: 18 October 2021 Aubais aljelehawy, Q. H., Hadi Alshaibah, L. H., & Abbas Al- Khafaji, Z. K. (2021). Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital. Cellular, Molecular and Biomedical Reports, 1(2), 78-87. doi: 10.55705/cmbr.2021.144995.1017 Qassim hassan Aubais aljelehawy; Layth Hussein Hadi Alshaibah; Zahraa Khudhair Abbas Al- Khafaji. "Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital". Cellular, Molecular and Biomedical Reports, 1, 2, 2021, 78-87. doi: 10.55705/cmbr.2021.144995.1017 Aubais aljelehawy, Q. H., Hadi Alshaibah, L. H., Abbas Al- Khafaji, Z. K. (2021). 'Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital', Cellular, Molecular and Biomedical Reports, 1(2), pp. 78-87. doi: 10.55705/cmbr.2021.144995.1017 Aubais aljelehawy, Q. H., Hadi Alshaibah, L. H., Abbas Al- Khafaji, Z. K. Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital. Cellular, Molecular and Biomedical Reports, 2021; 1(2): 78-87. doi: 10.55705/cmbr.2021.144995.1017 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_144995.html

cc40

Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital Cellular, Molecular and Biomedical Repor

en

Our publication ethicsand publication malpractice statement ismainly based on theCode of Conduct andBest-Practice Guidelines for Journal Editors(Committeeon Publication Ethics, 2011). At least two international reviewers, who are expert in the given area of research, conduct strict peer review and screen the scientific quality of submissions. Associate Editors and Editor in Chief are in charge of selecting these reviewers. It is also possible for the authors to recommend reviewers for some journals and article types. · The journal takes a number of criteria into consideration, including relevance, originality, readability, statistical validity, and language. · The reviews will result in one of the following decisions, i.e. acceptance, minor revisions, major revision, or rejection. · The authors must know that the revisions and resubmitted submissions may not necessarily guarantee the acceptance of the revised version. · There will be no further re-review for rejected papers. · The acceptance of submissions is constrained by such legal requirements as shall then be in force regarding libel, copyright infringement, and plagiarism. · Each research can be published only once, whether within the same journal or in another journal. The International Committee of Medical Journal Editors Recommendations for Conducting, Reporting, Editing, and Publication of Scholarly Work in Medical Journals (ICMJE Recommendations 2013) recommends that authorship should be based on the following four criteria: 1. The authors must have substantial involvement in the conception or design of the work; or they should be fundamentally involved in the process of acquisition, analysis, or interpretation of data for the work. 2. The authors must have substantial contribution to drafting the work or to its required critical revision as a result of important intellectual content. 3. The authors must be involved in approval of the final version that is going to be published. 4. The authors must have consensus about being responsible for all the aspects of the work. Hence, they would be able to justify the questions related to the accuracy or integrity of any part of the work. · The authors are required to ensure that the submitted work is their original research. · The authors are required to ensure that their submitted work has not been published elsewhere. Moreover, they must certify that their submitted work is not under review in another journal. · The authors are required to follow the comments provided in the peer review process. · The authors are required to make retractions or correction as necessary. · All authors of the submitted work must be fundamentally involved in the research. The range of their involvement must be specified under the “Authors’ Contributions” section. · The authors are required to be able to claim that all the presented data are real and authentic. · Any conflict of interest must be informed to the Editors of the journal. · The authors must be able to determine all the sources cited in the body of the paper. · In case the authors notice any error in the published article, they must inform the Editors. · In case the authors notice any error in the published article, they must inform the Editors. · Authors must not use irrelevant sources. · The authors must know that if they decide to withdraw their paper within the review process, they are subject to any penalty stipulated by the publisher. Peer Review/Responsibility for the Reviewers · The reviewers are required to preserve the confidentiality of all the information, regarding the content of the papers and consider them as privileged information. · The reviewers are required to guarantee full objectivity, with no bias or privilege given to the author, i.e. the reviewers’ personal knowledge of the author(s) must not be effective in providing comments and making decisions. · The reviewers’ point of view must be stated clearly along with constructive arguments in 500-1000 words. · The reviewers may find relevant published works, which are not specified by the authors. · If the reviewers have any knowledge with regard to any similarity or overlap between the paper under review and other papers, they are required to notify the Editor in Chief. · When potential conflict of interests arises between the reviewers and any of the authors, companies, agencies, or institutions connected to the papers, the reviewers should not review the paper. · The Editors (Associate Editors or Editor in Chief) reserve the right to accept/reject a submitted manuscript. · The contents and overall quality of the publication is under constant surveillance of the editors. · In enhancing the publication’s quality, the Editors prioritize the needs of authors and readers. · The Editors are in charge of ensuring the quality, validity, and reliability of academic productions. · The Editors must consider that, when necessary, an erratum should be published containing the revisions. · The Editors should be provided with a clear image of the funding sources of the research. · The main concentration of Editors must solely circle around the papers' importance, originality, clarity, and relevance to the publication's scope. · The editors cannot reverse their decision without reasonable explanations, nor can they overturn the decisions made by previous editors unless they have legitimate reasons. · The Editors should be concerned with maintaining the anonymity of reviewers (in half blind peer review journals). · The editors must guarantee that all of their published manuscripts are in line with the international accepted ethical guidelines. · The Editors’ acceptance of a paper should be finalized when they are reasonably certain. · When the Editors suspect any misconduct, they should take action, regardless of the paper’s having been published or unpublished. Consequently, they must make all efforts in resolving the problem. · The editors must consider that suspicions do not justify rejection of papers; hence, they should have proof of misconduct. · The editors must not permit any conflict of interests between staff, authors, reviewers, and board members. · After submitting a decision, the editors must not withdraw their decision (especially after rejection or acceptance) unless they have reasonable causes. 1. Journal policies on authorship and contributorship; According to the Recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals, released by the ICMJE, an “Author” is generally considered to be someone who simultaneously meets the following conditions 1, 2, 3, and 4. 1.1-Substantial contributions to the conception or design of the work; or the acquisition, analysis, or interpretation of data for the work; AND 1.2-Drafting the work or revising it critically for important intellectual content; AND 1.3-Final approval of the version to be published; AND 1.4-Agreement to be accountable for all aspects of the work in ensuring that questions related to the accuracy or integrity of any part of the work are appropriately investigated and resolved. Find out more: publicationethics.org/authorship The contributions of all authors must be described. CBMR have adopted the CRediT Taxonomy to describe each author’s individual contributions to the work. The submitting author is responsible for providing the contributions of all authors at submission. We expect that all authors will have Ideas; formulation or evolution of overarching research goals and aims. Management activities to annotate (produce metadata), scrub data and maintain research data (including software code, where it is necessary for interpreting the data itself) for initial use and later reuse. Application of statistical, mathematical, computational, or other formal techniques to analyze or synthesize study data. Acquisition of the financial support for the project leading to this publication. Conducting a research and investigation process, specifically performing the experiments, or data/evidence collection. Development or design of methodology; creation of models Management and coordination responsibility for the research activity planning and execution. Provision of study materials, reagents, materials, patients, laboratory samples, animals, instrumentation, computing resources, or other analysis tools. Programming, software development; designing computer programs; implementation of the computer code and supporting algorithms; testing of existing code components. Oversight and leadership responsibility for the research activity planning and execution, including mentorship external to the core team. Verification, whether as a part of the activity or separate, of the overall replication/reproducibility of results/experiments and other research outputs. Preparation, creation and/or presentation of the published work, specifically visualization/data presentation. Writing – Original Draft Preparation Creation and/or presentation of the published work, specifically writing the initial draft (including substantive translation). Writing – Review & Editing Preparation, creation and/or presentation of the published work by those from the original research group, specifically critical review, commentary or revision – including pre- or post-publication stages. 2. How the journal will handle complaints and appeals; This journal follows COPE Guidelinesfor handling complaints against the journal, its staff, editorial board or publisher. Find out more: publicationethics.org/appeals CBMR follow the Committee on Publication Ethics (COPE) guidelines on appeals to journal editor decisions and complaints about a journal’s editorial management of the peer review process. If you wish to appeal a journal editor’s decision, please submit an appeal letter to the journal’s online editorial office. Please address this to the editor and explain clearly the basis for an appeal. You should: Detail why you disagree with the decision. Please provide specific responses to any of the editor’s and/or reviewers’ comments that contributed to the reject decision. Provide any new information or data that you would like the journal to take into consideration. Provide evidence if you believe a reviewer has made technical errors in their assessment of your manuscript. Include evidence if you believe a reviewer may have a conflict of interest. 3. Journal policies on conflicts of interest / competing interests; We request all authors and reviewers to inform us about any kinds of “Conflict of Interest” (such as financial, personal, political, or academic) that would potentially affect their judgment. Authors are preferably asked to fill the uniform disclosure form available through: Find out more: publicationethics.org/competinginterests 4. Journal policies on data sharing and reproducibility; This journal havepolicies on data availability and encourage the use of reporting guidelines and registration of clinical trials and other study designs according to standard practice in their discipline. Find out more: publicationethics.org/data 5. Journal’s policy on ethical oversight; CBMR is a member of the Committee on Publication Ethics (COPE). COPE’s flowcharts and guidelines are approached in confronting any ethical misbehavior. The Journal also follows the guidelines mentioned in the Recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals issued by the International Committee of Medical Journal Editors (ICMJE). Find out more: publicationethics.org/oversight 6. Journal’s policy on intellectual property; and All policies on intellectual property, including copyright and publishing licenses, should be clearly described. In addition, any costs associated with publishing should be obvious to authors and readers. Policies should be clear on what counts as prepublication that will preclude consideration. What constitutes plagiarism and redundant/overlapping publication should be specified. Find out more: publicationethics.org/intellectualproperty 7. Journal’s options for post-publication discussions and corrections. The Journal will publish an erratum when a factual error in a published item has been documented. Scientific Reports' Editors and Editorial Board members assess all such cases on their individual merits. When plagiarism becomes evident post-publication, we may correct or retract the original publication depending on the degree of plagiarism, context within the published article and its impact on the overall integrity of the published study. Scientific Reports is part of Similarity Check, a service that uses software tools to screen submitted manuscripts for text overlap. Contribution to editorial decisions The peer-reviewing process assists the editorand the editorial board in making editorial decisions and may also serve the author in improving the paper. Any selected referee who feels unqualified to review the research reported in a manuscript or knows that its prompt review will be impossible should notify the editor and withdraw from the review process. Any manuscripts received for review must be treated as confidential documents. They must not be disclosed toor discussed with others except as authorized by the editor. Reviews should be conducted objectively. Personal criticism of the author is inappropriate. Referees should express their views clearly with supporting arguments. Reviewers should identify cases in which relevant published work referred to in the paper has not been cited in the reference section. They shouldpoint out whether observations or argumentsderived from other publications areaccompanied by the respectivesource. Reviewerswillnotify the editor of any substantialsimilarity or overlap between the manuscript under consideration and any other published paper of which they have personal knowledge. Disclosure and conflict of interest Privileged information or ideas obtained through peer review must be kept confidential and not used for personal advantage. Reviewers should not consider manuscripts in which they have conflicts of interest resulting from competitive, collaborative, or other relationships or connections with any of the authors, companies, or institutions associated withthe papers. · COPE rules must be followed and approved by all editorial members, reviewers, and authors. · Corresponding author, as the point of contact for queries, can withdraw the article when it is incomplete (before entering the review process or upon revision requirements). · No fundamental changes can be made by authors after acceptance without a serious reason. · The editorial members and authors must publish corrections honestly and completely. · Any notes of plagiarism, fraudulent data or any other kinds of fraud must be reported completely to COPE. · Under the materials and methods’ section, ethical considerations must be discussed. · Please make sure that all human adult subjects and the parents or legal guardians of minors provided informed consent prior to participation. · The name of the appropriate institutional review board, that approved the project, should be included. · It should be confirmed that maintenance and care of experimental animals complies with national Institutes of health guidelines for the humane use of laboratory animals, or those of your Institute or agency. · Any sources of funding and potential conflicting interest must be acknowledged and declared. The authors must clarify issues such as receiving funds or fees by, or holding stocks and shares in, an organization that may profit or lose through publication of your paper. · Declaration of competing interests will not lead to immediate rejection of the paper, but the Editors must be informed in advance. Committee on Publication Ethics (COPE). Code of Conduct and Best-Practice Guidelines for Journal Editors. Available here. Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/page_778.html

cc40

Our publication ethicsand publication malpractice statement ismainly based on theCode of Conduct andBest-Practice Guidelines for Journal Editors(Committeeon Publication Ethics, 2011). At least two int

en

Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria Document Type : Original Article 1 Zoology Department, Faculty of Science, Gombe State University, Gombe, Nigeria. 2 Zoology Department, Faculty of Life Sciences, Modibbo Adama University, Yola, Nigeria 3 Department of Biomedical and Pharmaceutical Technology, Federal Polytechnic, Mubi, Adamawa Sate, Nigeria Chloroquine was one of the most cheapest and effective chemotherapeutic drugs for Plasmodium falciparum-malaria, but for a long, the drug has been officially withdrawn in almost all malaria-endemic countries including Nigeria, due to the development of resistance by the parasite. Withdrawal of the drug may make the drug regains its efficacy. Therefore, this study aimed to determine the presence of Biomarkers associated with chloroquine resistance from Gombe Local Government Area, Gombe State, Nigeria after its withdrawal in 2005. Twenty hundred blood samples were collected from consented study subjects and analysed using Microscopy, RDT and PCR. DNA was extracted using Quick-DNA™ Miniprep (No. D4069), Purity and Concentration of the DNA were determined using Nanodrop Spectrophotometer. 57 true positive samples were selected for molecular analysis. Nested PCR was used to amplify the required codon (C72S, M74I, K76T and N75E) position of PCRT the gene of P. falciparum. Both Primary and Secondary PCR was carried out. The PCR products were subjected to electrophoresis in 2% agarose and stained with ethidium bromide. The amplicons were purified and sequenced, after which the sequenced products were subjected to BLAST software. Single Nucleotide Polymorphism was recorded from C72S and K76T with a prevalence of 05(8.80%) and 46(80.70%) respectively. Confirmed biomarkers of Chloroquine resistance are still present in P. falciparum isolate from Gombe L.G.A. Selected author of this article by journal This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Owoloye A, Olufemi M, Idowu ET, Oyebola KM (2021) Prevalence of potential mediators of artemisinin resistance in African isolates of Plasmodium falciparum. Malaria journal 20(1):1-12. doi:https://doi.org/10.1186/s12936-021-03987-6 Shafik SH, Cobbold SA, Barkat K, Richards SN, Lancaster NS, Llinás M, Hogg SJ, Summers RL, McConville MJ, Martin RE (2020) The natural function of the malaria parasite’s chloroquine resistance transporter. Nature communications 11(1):1-16. doi:https://doi.org/10.1038/s41467-020-17781-6 Ahouidi A, Oliveira R, Lobo L, Diedhiou C, Mboup S, Nogueira F (2021) Prevalence of pfk13 and pfmdr1 polymorphisms in Bounkiling, Southern Senegal. PloS one 16(3):e0249357. doi:https://doi.org/10.1371/journal.pone.0249357 De-Dios T, van Dorp L, Gelabert P, Carøe C, Sandoval-Velasco M, Fregel R, Escosa R, Aranda C, Huijben S, Balloux F (2019) Genetic affinities of an eradicated European Plasmodium falciparum strain. Microbial genomics 5(9):PMC6807384. doi:https://doi.org/10.1099/mgen.0.000289 Tola M, Ajibola O, Idowu ET, Omidiji O, Awolola ST, Amambua-Ngwa A (2020) Molecular detection of drug resistant polymorphisms in Plasmodium falciparum isolates from Southwest, Nigeria. BMC Research Notes 13(1):1-7. doi:https://doi.org/10.1186/s13104-020-05334-5 Voumbo-Matoumona DF, Kouna LC, Madamet M, Maghendji-Nzondo S, Pradines B, Lekana-Douki JB (2018) Prevalence of Plasmodium falciparum antimalarial drug resistance genes in Southeastern Gabon from 2011 to 2014. Infection and drug resistance 11:1329-1338. doi:https://doi.org/10.2147/IDR.S160164 Adam R, Mukhtar MM, Abubakar UF, Damudi HA, Muhammad A, Ibrahim SS (2021) Polymorphism Analysis of pfmdr1 and pfcrt from Plasmodium falciparum Isolates in Northwestern Nigeria Revealed the Major Markers Associated with Antimalarial Resistance. Diseases 9(1):1-12 Beargie SM, Higgins CR, Evans DR, Laing SK, Erim D, Ozawa S (2019) The economic impact of substandard and falsified antimalarial medications in Nigeria. PloS one 14(8):e0217910. doi:https://doi.org/10.1371/journal.pone.0217910 Muhammad I, Sale PM, Midala AL (2022) Absence of Biomakers of Resistance in K13 Propeller Gene of Plasmodium falciparum from Gombe LGA of Gombe State, Nigeria. Advances 3(1):25-33 Stokes BH, Dhingra SK, Rubiano K, Mok S, Straimer J, Gnädig NF, Deni I, Schindler KA, Bath JR, Ward KE (2021) Plasmodium falciparum K13 mutations in Africa and Asia impact artemisinin resistance and parasite fitness. Elife 10:e66277. doi:https://doi.org/10.7554/eLife.66277 Parray JA, Ali U, Mir MY, Shameem N (2021) A high throughputs and consistent method for the sampling and isolation of Endophytic bacteria allied to high altitude the medicinal plant Arnebia benthamii (Wall ex. G. Don). Micro Environer 1(1):1-6. doi:https://doi.org/10.54458/mev.v1i01.6668 Karabulut F, Parray JA, Mir MY (2021) Emerging trends for Harnessing plant metabolome and microbiome for sustainable food Production. Micro Environer 1(1):33-53 doi:https://doi.org/10.54458/mev.v1i01.6672 Ghafari M, Beigomi Z, Javadian E (2021) Evaluation of antibacterial activity of extract plant against Staphylococcus aureus and Candida albicans isolated from women Micro Environer 1(2):78-85. doi:https://doi.org/10.54458/mev.v1i02.6675 Jahantigh M, ahmadi H (2021) Analysis of the antimicrobial activity of Ashurak extracts prepared with different solvents on Klebsiella pneumoniae and Shigella dysentery isolated from poultry faeces. Micro Environer 1(1):54-62. doi:https://doi.org/10.54458/mev.v1i01.6673 Karabulut F, Aydın S, Parray JA (2021) Interactions of antioxidant defense mechanisms developed by plants and microorganisms against pesticides Micro Environer 1(2):63-77. doi:https://doi.org/10.54458/mev.v1i02.6674 Kayiba NK, Yobi DM, Tshibangu-Kabamba E, Tuan VP, Yamaoka Y, Devleesschauwer B, Mvumbi DM, Wemakoy EO, De Mol P, Mvumbi GL (2021) Spatial and molecular mapping of Pfkelch13 gene polymorphism in Africa in the era of emerging Plasmodium falciparum resistance to artemisinin: a systematic review. The Lancet Infectious Diseases 21(4):e82-e92. doi:https://doi.org/10.1016/S1473-3099(20)30493-X Beigomi M, Biabangard A, Rohani R (2021) Evaluation of antimicrobial effects of Rosemary and Withania somnifera methanol extract prepared by ultrasound waveform on Escherichia coli biofilm isolated from urinary tract infection. Micro Environer 1(2):17-25. doi:https://doi.org/10.54458/mev.v1i01.6670 Beigomi M, shakoory-moghadam V, Biabangard A, Behzadmehr R (2021) Evaluation of the antimicrobial activity of plant extracts on Escherichia coli and Candida albicans. Micro Environer 1(2):86-92. doi:https://doi.org/10.54458/mev.v1i02.6676 Chagona P, Kwamboka N, Gaya H, Makonde H, Adem A, Osano K, Kawaka F (2021) Phytochemical Analysis and Antibacterial Activity of the Kenyan Wild Orchids. Micro Environer 1(2):93-100. doi:https://doi.org/10.54458/mev.v1i02.6677 Simon-Oke IA, Ade-Alao AO, Ologundudu F (2020) The impact of HIV-associated immunosuppression on the Plasmodium falciparum chloroquine resistance transporter gene (PfCRT) of HIV patients in Akure, Nigeria. Bulletin of the National Research Centre 44(1):1-7. doi:https://doi.org/10.1186/s42269-020-00401-0 Xu C, Wei Q, Yin K, Sun H, Li J, Xiao T, Kong X, Wang Y, Zhao G, Zhu S (2018) Surveillance of antimalarial resistance Pfcrt, Pfmdr1, and Pfkelch13 polymorphisms in African Plasmodium falciparum imported to Shandong Province, China. Scientific reports 8(1):1-9. doi:https://doi.org/10.1038/s41598-018-31207-w Solomon VR, Lee H (2009) Chloroquine and its analogs: a new promise of an old drug for effective and safe cancer therapies. European journal of pharmacology 625(1-3):220-233. doi:https://doi.org/10.1016/j.ejphar.2009.06.063 Balikagala B, Sakurai-Yatsushiro M, Tachibana S-I, Ikeda M, Yamauchi M, Katuro OT, Ntege EH, Sekihara M, Fukuda N, Takahashi N (2020) Recovery and stable persistence of chloroquine sensitivity in Plasmodium falciparum parasites after its discontinued use in Northern Uganda. Malaria journal 19(1):1-12. doi:https://doi.org/10.1186/s12936-020-03157-0 Zhao D, Zhang H, Ji P, Li S, Yang C, Liu Y, Qian D, Deng Y, Wang H, Lu D (2021) Surveillance of Antimalarial Drug-Resistance Genes in Imported Plasmodium falciparum Isolates From Nigeria in Henan, China, 2012–2019. Frontiers in cellular and infection microbiology 11(Article 644576):1-9. doi:https://doi.org/10.3389/fcimb.2021.644576 Agomo CO, Oyibo WA, Sutherland C, Hallet R, Oguike M (2016) Assessment of markers of antimalarial drug resistance in Plasmodium falciparum isolates from pregnant women in Lagos, Nigeria. PloS one 11(1):e0146908. doi:https://doi.org/10.1371/journal.pone.0146908 Mwanza S, Joshi S, Nambozi M, Chileshe J, Malunga P, Kabuya J-BB, Hachizovu S, Manyando C, Mulenga M, Laufer M (2016) The return of chloroquine-susceptible Plasmodium falciparum malaria in Zambia. Malaria journal 15(1):1-6. doi:https://doi.org/10.1186/s12936-016-1637-3 Oladipo OO, Wellington OA, Sutherland CJ (2015) Persistence of chloroquine-resistant haplotypes of Plasmodium falciparum in children with uncomplicated Malaria in Lagos, Nigeria, four years after change of chloroquine as first-line antimalarial medicine. Diagnostic pathology 10(1):1-8. doi:https://doi.org/10.1186/s13000-015-0276-2 Pathak A, Mårtensson A, Gawariker S, Sharma A, Diwan V, Purohit M, Ursing J (2020) Stable high frequencies of sulfadoxine–pyrimethamine resistance associated mutations and absence of K13 mutations in Plasmodium falciparum 3 and 4 years after the introduction of artesunate plus sulfadoxine–pyrimethamine in Ujjain, Madhya Pradesh, India. Malaria journal 19(1):1-7. doi:https://doi.org/10.1186/s12936-020-03274-w Menard D, Dondorp A (2017) Antimalarial drug resistance: a threat to malaria elimination. Cold Spring Harbor Perspectives in Medicine 7(7):a025619. doi:https://doi.org/10.1101/cshperspect.a025619 Mahende C, Ngasala B, Lusingu J, Yong T-S, Lushino P, Lemnge M, Mmbando B, Premji Z (2016) Performance of rapid diagnostic test, blood-film microscopy and PCR for the diagnosis of malaria infection among febrile children from Korogwe District, Tanzania. Malaria journal 15(1):1-7. doi:https://doi.org/10.1186/s12936-016-1450-z Ippolito MM, Moser KA, Kabuya J-BB, Cunningham C, Juliano JJ (2021) Antimalarial drug resistance and implications for the WHO global technical strategy. Current Epidemiology Reports 8(2):46-62. doi:https://doi.org/10.1007/s40471-021-00266-5 Khan HM, Kirmani S, Khan PA, İslam U (2016) Prevalence of chloroquine resistant Plasmodium falciparum malaria in pregnant females attending North Indian hospital. Eastern Journal Of Medicine 21(2):64-68 Nneji C, Adedapo A, Okorie P, Ademowo P (2015) Chloroquine resistance and host genetic factors among nigerian children with uncomplicated P. falciparum Infection. Arch Med 7(4):1-9 Bello SO, Chika A, Bello AY (2010) Is Chloroquine better than Artemisinin combination therapy as first line treatment in adult Nigerians with uncomplicated malaria? a cost effective analysis. African Journal of Infectious Diseases 4(2):29-42. doi:https://doi.org/10.4314/ajid.v4i2.55145 Adyanthaya S, Jose M (2013) Quality and safety aspects in histopathology laboratory. Journal of oral and maxillofacial pathology: JOMFP 17(3):402. doi:https://dx.doi.org/10.4103%2F0973-029X.125207 García-Alegría AM, Anduro-Corona I, Pérez-Martínez CJ, Guadalupe Corella-Madueño MA, Rascón-Durán ML, Astiazaran-Garcia H (2020) Quantification of DNA through the nanodrop spectrophotometer: methodological validation using standard reference material and Sprague Dawley Rat and human DNA. International journal of analytical chemistry 2020:Article ID: 8896738. doi:https://doi.org/10.1155/2020/8896738 Mogeni P, Williams TN, Omedo I, Kimani D, Ngoi JM, Mwacharo J, Morter R, Nyundo C, Wambua J, Nyangweso G (2017) Detecting malaria hotspots: a comparison of rapid diagnostic test, microscopy, and polymerase chain reaction. The Journal of infectious diseases 216(9):1091-1098. doi:https://doi.org/10.1093/infdis/jix321 Londono BL, Eisele TP, Keating J, Bennett A, Chattopadhyay C, Heyliger G, Mack B, Rawson I, Vely J-F, Désinor O (2009) Chloroquine-resistant haplotype Plasmodium falciparum parasites, Haiti. Emerging infectious diseases 15(5):735. doi:https://dx.doi.org/10.3201%2Feid1505.081063 Atroosh WM, Al-Mekhlafi HM, Mahdy MA, Surin J (2012) The detection of pfcrt and pfmdr1 point mutations as molecular markers of chloroquine drug resistance, Pahang, Malaysia. Malaria journal 11(1):1-7. doi:https://doi.org/10.1186/1475-2875-11-251 Olukosi YA, Oyebola MK, Ajibaye O, Orok BA, Aina OO, Agomo CO, Iwalokun BA, Akindele SK, Enya VN, Okoh HI (2014) Persistence of markers of chloroquine resistance among P. falciparum isolates recovered from two Nigerian communities. Mal World J 5(3):3-6 Aguiar AC, Murce E, Cortopassi WA, Pimentel AS, Almeida MM, Barros DC, Guedes JS, Meneghetti MR, Krettli AU (2018) Chloroquine analogs as antimalarial candidates with potent in vitro and in vivo activity. International Journal for Parasitology: Drugs and Drug Resistance 8(3):459-464. doi:https://doi.org/10.1016/j.ijpddr.2018.10.002 Zhao Y, Liu Z, Soe MT, Wang L, Soe TN, Wei H, Than A, Aung PL, Li Y, Zhang X (2019) Genetic variations associated with drug resistance markers in asymptomatic Plasmodium falciparum infections in Myanmar. Genes 10(9):1-17. doi:https://doi.org/10.3390/genes10090692 Mittra P, Vinayak S, Chandawat H, Das MK, Singh N, Biswas S, Dev V, Kumar A, Ansari MA, Sharma YD (2006) Progressive increase in point mutations associated with chloroquine resistance in Plasmodium falciparum isolates from India. The Journal of infectious diseases 193(9):1304-1312. doi:https://doi.org/10.1086/502979 Patel P, Bharti PK, Bansal D, Ali NA, Raman RK, Mohapatra PK, Sehgal R, Mahanta J, Sultan AA, Singh N (2017) Prevalence of mutations linked to antimalarial resistance in Plasmodium falciparum from Chhattisgarh, Central India: a malaria elimination point of view. Scientific reports 7(1):1-8. doi:https://doi.org/10.1038/s41598-017-16866-5 Huang F, Yan H, Xue J-B, Cui Y-W, Zhou S-S, Xia Z-G, Abeyasinghe R, Ringwald P, Zhou X-N (2021) Molecular surveillance of pfcrt, pfmdr1 and pfk13-propeller mutations in Plasmodium falciparum isolates imported from Africa to China. Malaria journal 20(1):1-11. doi:https://doi.org/10.1186/s12936-021-03613-5 Antony HA, Das S, Parija SC, Padhi S (2016) Sequence analysis of pfcrt and pfmdr1 genes and its association with chloroquine resistance in Southeast Indian Plasmodium falciparum isolates. Genomics data 8:85-90. doi:https://doi.org/10.1016/j.gdata.2016.04.010 Folarin O, Gbotosho G, Sowunmi A, Olorunsogo O, Oduola A, Happi T (2008) Chloroquine resistant Plasmodium falciparum in Nigeria: relationship between pfcrt and pfmdr1 polymorphisms, in-vitro resistance and treatment outcome. The open tropical medicine journal 1:74-82. doi:https://dx.doi.org/10.2174%2F1874315300801010074 Idowu AO, Oyibo WA, Bhattacharyya S, Khubbar M, Mendie UE, Bumah VV, Black C, Igietseme J, Azenabor AA (2019) Rare mutations in Pfmdr1 gene of Plasmodium falciparum detected in clinical isolates from patients treated with anti-malarial drug in Nigeria. Malaria journal 18(1):1-9. doi:https://doi.org/10.1186/s12936-019-2947-z TAS M, Timothy S, Emenike I (2016) Assessment of chloroquine tablets used in the treatment of malaria in northern nigeria. International Journal 7(1):2671-2677 Yang Z, Zhang Z, Sun X, Wan W, Cui L, Zhang X, Zhong D, Yan G, Cui L (2007) Molecular analysis of chloroquine resistance in Plasmodium falciparum in Yunnan Province, China. Tropical Medicine & International Health 12(9):1051-1060. doi:https://doi.org/10.1111/j.1365-3156.2007.01882.x Xiao X, Shen J, Wang S, Xiao H, Tong G (2010) The variation of the southwest monsoon from the high resolution pollen record in Heqing Basin, Yunnan Province, China for the last 2.78 Ma. Palaeogeography, Palaeoclimatology, Palaeoecology 287(1-4):45-57. doi:https://doi.org/10.1016/j.palaeo.2010.01.013 Ocan M, Akena D, Nsobya S, Kamya MR, Senono R, Kinengyere AA, Obuku EA (2019) Persistence of chloroquine resistance alleles in malaria endemic countries: a systematic review of burden and risk factors. Malaria journal 18(1):1-15. doi:https://doi.org/10.1186/s12936-019-2716-z Plummer WB, Pereira LMP, Carrington CV (2004) Pfcrt and pfmdr1 alleles associated with chloroquine resistance in Plasmodium falciparum from Guyana, South America. Memorias do Instituto Oswaldo Cruz 99(4):389-392 Farcas GA, Soeller R, Zhong K, Zahirieh A, Kain KC (2006) Real-time polymerase chain reaction assay for the rapid detection and characterization of chloroquine-resistant Plasmodium falciparum malaria in returned travelers. Clinical infectious diseases 42(5):622-627. doi:https://doi.org/10.1086/500134 Cheruiyot J, Ingasia LA, Omondi AA, Juma DW, Opot BH, Ndegwa JM, Mativo J, Cheruiyot AC, Yeda R, Okudo C (2014) Polymorphisms in Pf mdr1, Pf crt, and Pf nhe1 genes are associated with reduced in vitro activities of quinine in Plasmodium falciparum isolates from Western Kenya. Antimicrobial agents and chemotherapy 58(7):3737-3743. doi:https://doi.org/10.1128/AAC.02472-14 Singh G, Singh R, Urhehar AD (2016) Simple molecular methods for early detection of chloroquine drug resistance in Plasmodium vivax and Plasmodium falciparum. Journal of clinical and diagnostic research: JCDR 10(7):DC19. doi:https://dx.doi.org/10.7860%2FJCDR%2F2016%2F18596.8154 Djimdé A, Doumbo OK, Cortese JF, Kayentao K, Doumbo S, Diourté Y, Coulibaly D, Dicko A, Su X-z, Nomura T (2001) A molecular marker for chloroquine-resistant falciparum malaria. New England Journal of Medicine 344(4):257-263. doi:https://doi.org/10.1056/NEJM200101253440403 Shrivastava SK, Gupta RK, Mahanta J, Dubey ML (2014) Correlation of molecular markers, Pfmdr1-N86Y and Pfcrt-K76T, with in vitro chloroquine resistant Plasmodium falciparum, isolated in the malaria endemic states of Assam and Arunachal Pradesh, Northeast India. PloS one 9(8):e103848. doi:https://doi.org/10.1371/journal.pone.0103848 Volume 2, Issue 1 Cellular, Molecular and Biomedical Reports Receive Date: 05 January 2022 Revise Date: 12 February 2022 Accept Date: 24 March 2022 First Publish Date: 24 March 2022 Muhammad, I., Sale, P., Salisu, M., Muhammad, T., Abubakar, B., Maidala, A., & Nuwanyada, E. (2022). Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria. Cellular, Molecular and Biomedical Reports, 2(1), 42-55. doi: 10.55705/cmbr.2022.335753.1033 Ismail Muhammad; Pukuma Micah Sale; Muhammad Khadija Salisu; Tanko Mahmoud Muhammad; Bala Abubakar; Augustine Linda Maidala; Enock Nuwanyada. "Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria". Cellular, Molecular and Biomedical Reports, 2, 1, 2022, 42-55. doi: 10.55705/cmbr.2022.335753.1033 Muhammad, I., Sale, P., Salisu, M., Muhammad, T., Abubakar, B., Maidala, A., Nuwanyada, E. (2022). 'Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria', Cellular, Molecular and Biomedical Reports, 2(1), pp. 42-55. doi: 10.55705/cmbr.2022.335753.1033 Muhammad, I., Sale, P., Salisu, M., Muhammad, T., Abubakar, B., Maidala, A., Nuwanyada, E. Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria. Cellular, Molecular and Biomedical Reports, 2022; 2(1): 42-55. doi: 10.55705/cmbr.2022.335753.1033 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_148168.html

cc40

Molecular analysis of Bio-makers of Chloroquine resistance in Plasmodium falciparum Isolate from Gombe Local Government Area, Gombe State, Nigeria Cellular, Molecular and Biomedical Reports Publicatio

en

Cell. Mol. Biomed. Rep.” is an open access, peer-reviewed, interdisciplinary journal that offers researchers and practitioner’s opportunities to publish original full-length papers, short communications, reviews mini-review, or meta-analysis articles in all fields of Cellular, Molecular and Biomedical Reports about the medicine or other organisms that have been used in medicine. Cell. Mol. Biomed. Rep. focuses on: - All aspects of Cell. Mol. Biomed. Rep. - All aspects related to the different structures and functions of the cell and to its components (DNA, RNA, protein) are relevant to the scope of this journal - DNA replication, transcription, nucleic acid-protein interaction, RNA processing, intracellular transport, protein biosynthesis are examples of topics within the Cellular, Molecular and Biomedical field - Nuclear function, cytoskeleton and cell membrane interactions, transport of cellular products between different organelles fits in the Cellular, Molecular and Biomedical category. The Journal welcomes the submission of manuscripts that meet the general criteria of significance and scientific excellence in the diverse fields of microbiological processes and developments in environment. It provides a key forum to bring together state-of-the-art research of interest to scientists, engineers and policymakers in related fields worldwide. Submitted manuscripts will be evaluated by at least two independent reviewers who are either members of the Editorial Board or ad hoc referees. Accepted manuscripts will be available online as PDF files immediately upon their acceptance for publication. Micro-Environer is published quarterly in 4 issues. Authors retain the copyright of their articles and are free to reproduce and disseminate their work. Cell. Mol. Biomed. Rep. reviews all the submitted manuscripts. The editor selects peer reviewers upon the recommendation of the Editorial Board members. Typically, the scientific review of manuscript is handled by an Associate Editor who selects at least two investigators in the field as referees according to recommendation of Editor or Editorial board. The reviewed manuscripts are returned back to the corresponding author with comments and recommended revisions. Though the peer review process may in general take six to eight weeks after submission of the manuscript, more time may be need to finalize the review process. Failure to resubmit the revised manuscript within five weeks is regarded as a withdrawal. Corresponding author must indicate clearly what alterations have been made in response to the referee’s comments point by point. Acceptable reasons should be given for noncompliance with any recommendation of the referees. Once accepted, original articles will be published with order. It is necessary to upload these files separately: 1- Main File; without title page (*) 4- Graphical Abstract (JPEG or cdx) 5- Completed Copyright Form (*) All fields should be completed by authors Article similarity (plagiarism) should be less than 15% All references should be written based on the journal guide and also with the EndNote software (the EndNote file of the journal is prepared and can be downloaded from the journal site) Articles should be in the form of a A4 (Width equal to 21 cm and height equal to 29.7 cm), with a margin of 2.5 cm on all four sides Although the main text of journal articles is two columns, authors must submit their articles to the journal from one column. If the article is accepted, at the time of publication, the original text of the article will be in two columns by the journal page designer. Cell. Mol. Biomed. Rep.: Instructions for Authors Submission of a manuscript implies that the work has not been published and is not submitted for publication anywhere else. All authors must approve publication. Authors should accept publication fees. Financial, personal or other conflicts should be disclosed by authors. 1.3 Ethics for animal experiments and medical studies Experiments should be carried out in accordance with the guidelines laid down by the International animal ethics committee or institutional ethics committee and in accordance with local laws and regulations. Authors are requested to indicate ethical declarations in the Experimental section. The publication fee for manuscripts submitted is free per paper, whatever their type or length. The authors of the articles should note that before submitting an article to this journal, they should be fully aware of the conditions and if they have submitted an article, they can only request to withdraw the article before the scientific acceptance. If the article is scientifically accepted, the authors do not have the right to cancel or withdraw the article unless they pay a review fee of about 50$. All articles published by Cell. Mol. Biomed. Rep. are made freely and permanently accessible online immediately upon publication, without subscription charges or registration barriers. Authors are the copyright holders of their articles. Letters in Bioscience publishes Research articles, Short communications, Reviews and others Use Times New Roman 12 with 1.5 line spacing throughout the manuscript. Tables and figures should not be included in main manuscript. Italics should be used in the text for all scientific names and other terms such as genes, mutations, genotypes and alleles. SI units should be used throughout the manuscript. Manuscripts should be prepared according to the following order Abstract and 5–7 keywords Tables (up to 5) Figures (up to 5) References (up to 35) Title: Concise and informative, avoid abbreviations and formulas where possible Author names and affiliations: List of all authors with full given and family names (not capitalized), addresses of all authors, name of corresponding author with e-mail address. The abstract should be concise and factual written in a single paragraph. It should state briefly the purpose of research the principal results and major conclusions. References and abbreviations should be avoided but if essential they must be defined at their first mention in the abstract itself. Keywords: A maximum of 5 to 7 specific keywords is required State the objectives of the work and provide an adequate background, avoiding a detailed literature survey or a summary of the results. 3.5 Materials and Methods Materials and methods section should include the design of the study, the type of materials involved, a clear description of all comparisons, and should be concise but sufficient for repetition by other qualified investigators. Methods already published should be indicated by a reference: only relevant modifications should be described. Results should be clear and concise. Authors should use tables only to achieve concise presentation or where the information cannot be given satisfactorily in other ways. Tables should be numbered consecutively using Arabic numerals and should be in the text itself at appropriate place not at the end or as separate attachment. Each table should have an explanatory caption which should be as concise as possible. Authors may use line diagrams and photographs to illustrate these from their text. The figures should be clear, easy to read and of good quality. Styles and fonts should match those in the main body of the article. Lettering and lines should be of uniform density and the lines unbroken. Axis labels should be in bold face. Units should be placed next to variables in parentheses. All figures must be in the text itself appropriate place not at the end or as separate attachment. This should explore the significance of the results of the work, not repeat them. A combined Results and Discussion section is often appropriate. Avoid extensive citations and discussion of published literature. The main conclusions of the study should be presented in under this section. All contributors who do not meet the criteria for authorship as defined above should be listed in an acknowledgements section. Examples of those who might be acknowledged include a person who provided purely technical help, writing assistance, or a department chair that provided only general support. The references section must include all relevant published works, and all listed references. At the end, you will see the writing format in detail Type of Manuscript: Original Article Title of Manuscript: (Font; Cambria 16 Bold) Abstract: (Font; Cambria 10 Bold) Background: (Font; Cambria 10 Bold) Text for this section of the abstract (Font; Cambria 10 Regular) Methods: (Font; Cambria 10 Bold) Text for this section of the abstract… Results; (Font; Cambria 10 Bold) Text for this section of the abstract… Conclusions: (Font; Cambria 10 Bold) Text for this section of the abstract… Keywords: 3 to 6 keywords to describe your manuscripts subject, Taken from the Mesh and PubMed web site and Sort alphabetically. Write the MeSH Unique ID or PubMed Number (or PMID) of each word in front of it. *Before text of first line of all major paragraphs should be dented by half a centimetre All main and sub-titles of the main text of the article should be numbered. 1. Background (Font; Cambria 10 Bold) Text for this section (Font; Cambria 10 Regular) 2. Material and Methods (Font; Cambria 10 Bold) 2.1. Sub- heading for this section (Font; Cambria 10 Bold) Text for this sub-section. (Font; Cambria 10 Regular) 2.2. Sub- heading for this section (Font; Cambria 10, Bold) Text for this sub-section. (Font; Cambria 10 Regular) 2.3. Sub- heading for this section (Font; Cambria 10 Bold) Text for this sub-section. (Font; Cambria 10 Regular) 3. Results (Font; Cambria 10 Bold) 3.1. Sub- heading for this section (Font; Cambria 10 Bold) Text for this sub-section. (Font; Cambria 10 Regular) 3.2. Sub- heading for this section (Font; Cambria 10 Bold) Text for this sub-section. (Font; Cambria 10 Regular) 3.3. Sub- heading for this section (Font; Cambria 10 Bold) Text for this sub-section. (Font; Cambria 10 Regular) All Figures/images should be inserted within the text as close as possible to where they are referenced (fig. 1). Authors should not upload them as separate files. Fig. 1. The leaf and flower of Tecomella undulate (Font; Cambria 10)(reference) Picture resolution= 300 dpi *The bottom titles of the figures should be in the middle Notice: if your pictures are not based on your research you have to cite the reference that you used Note: The number of figures in each article should not exceed 5 All Tables should be inserted within the text as close as possible to where they are referenced (table 1). Authors should not upload them as separate files. Table 2. Effect of temperature on pupation of S. littoralis (Font; Cambria 10)* *, ** significant and 5 and 1 percent, respectively, ns; non-significant. The data in the table are the means ± SE. Different letters in the same column indicate significant differences at P < 0.05 *Tables should not have lines between their rows *The top and bottom titles of the tables should be in the middle *Note: The number of tables in each article should not exceed 5 Text for this section (Font; Cambria 10 Regular) Text for this section (Font; Cambria 10 Regular) Authors should write full words or phrases, abbreviated in the article text, in this section All authors have to declare their conflict of interest. All authors have to write this sentence that they read and approved the final manuscript for publication. Availability of data and material The authors have to declare that they embedded all data in the manuscript. All authors should write their part in designing the idea, doing, analyzing and writing the article. Authors should mention the company, institution or organization that paid for the research Ethics approval and consent to participate[1]: The authors have to declare that they do not use human or animals in their research but if they used, they have to write name of the ethics committee that has approved the study of enter the code of research ethics (provided by the institution or university where the research was conducted) in the article. If necessary, the authors can thank people or institutions that have provided them with scientific or material assistance in doing and writing the article. Maximum number of the references should be 35 titles. All references should have doi Arrange references as a simple list here by using the EndNote. All references have to be hanging with 0.5 cm (The first line of each reference entry is aligned flush with the left margin and each subsequent line has a hanging indent of 0.5 cm) (Font; Cambria 12 Regular) Note: The number of references must be a maximum of “35”, and on the other hand, all references must have a “doi”. No reference without “doi” in the article will be accepted. Note: Authors are not allowed to cite their previous articles for more than 5 references You can use the Endnote Style in below link: References - In the text, number references in order of appearance using Arabic numerals [e.g. 1, 2, 3] in parentheses for citations. Multiple citations within a single set of brackets should be separated by commas. Where there are three or more sequential citations, they should be given as a range [2,3-7,15]. List the references at the end of the paper in numbered order. The list should contain at least fifteen references and should be arranged in the order of citation in text. References to articles must include: 1. name(s) and initials of author(s), if more than six (6) authors add an et al. after the sixth author.; 2. title of paper; 3. title of the journal in the standard manner (see Index Medicus/Pubmed); 4. publication year; 5. volume number; 6. first and last page numbers of the article (references to online articles should have the same structure and additionally the appropriate web address following page numbers). Important: References numbers should be linked to reference list. Journal names should be in the most famous form (it doesn't matter whether it is abbreviate or full name) according to Cell. Mol. Biomed. Rep.. Authors are fully responsible for the accuracy of the references. Hakimian H, Rezaei-Zarchi S, Javid A (2021) The Toxicological effect of Cuscuta epithymum and Artemisia absinthium species on CP70 ovarian cancer cells. Int J Adv Biol Biomed Res:-. doi:10.22034/ijabbr.2021.526486.1355 Abbas G, Murtaza B, Bibi I, Shahid M, Niazi NK, Khan MI, Amjad M, Hussain M (2018) Arsenic uptake, toxicity, detoxification, and speciation in plants: physiological, biochemical, and molecular aspects. Int J Environ Res Public Health 15:59. doi:https://doi.org/10.3390/ijerph15010059 Hall J, Soole K, Bentham R (2011) Hydrocarbon phytoremediation in the family Fabaceae--a review. Int J Phytoremediation 13:317-332. doi:10.1080/15226514.2010.495143 Abbasi-Moghadam J, Shahriari A, Fazeli-Nasab B (2017) Investigation of bacteria and fungi populations associated with airborne dust during ‘’wind of 120 days’’ blowing in the urban areas of Sistan plain. Paper presented at the 15th Iranian Soil Science Congress, Isfahan University of Technology, Isfahan, Iran, Congress COI: SSCI15, Article COI: SSCI15_687, Ali-Soufi M, Shahriari A, Shirmohammadi E, Fazeli-Nasab B (2017) Investigation of biological properties and microorganism identification in susceptible areas to wind erosion in Hamoun wetlands. Paper presented at the Congress on restoration policies and approaches of Hamoun international wetland Zabol Book (book Chapter and book section) Fazeli-Nasab B, Sayyed RZ (2019) Plant Growth-Promoting Rhizobacteria and Salinity Stress: A Journey into the Soil. In: Sayyed RZ, Arora NK, Reddy MS (eds) Plant Growth Promoting Rhizobacteria for Sustainable Stress Management : Volume 1: Rhizobacteria in Abiotic Stress Management. Springer Singapore, Singapore, pp 21-34. doi:https://doi.org/10.1007/978-981-13-6536-2_2 Rasouli H, Popović-Djordjević J, Sayyed RZ, Zarayneh S, Jafari M, Fazeli-Nasab B (2020) Nanoparticles: A New Threat to Crop Plants and Soil Rhizobia? In: Hayat S, Pichtel J, Faizan M, Fariduddin Q (eds) Sustainable Agriculture Reviews 41: Nanotechnology for Plant Growth and Development. Springer International Publishing, Cham, pp 201-214. doi:https://doi.org/10.1007/978-3-030-33996-8_11 AMFEP (2015) Association of manufacturers and formulators of enzyme products. List of commercial enzymes. http://www.amfep.org/content/list-enzymes. Appendix 1 – Sample title Appendix 2 – Sample title Cell. Mol. Biomed. Rep. Article Types: These articles consist of Systematic Review, Meta-analysis, Systematic Reviews and Meta-analysis, Meta-Synthesis, Scoping Review, Literature Review, and Narrative Review. These articles may be up to 7000 words excluding abstract, tables, and references. Inclusion and exclusion criteria for studies should be described in a flow diagram. The specific type of study or analysis, intervention, population, exposure, outcomes or tests should be described for each data source or article. Authors are to clearly cover the following topics in the method section: search strategy and selection criteria, data extraction, quality assessment, and data analysis. A structured abstract is required that should include: Background; Methods and Analysis; Discussion; Registry and number (if the protocol of these articles had been registered in a registry system). For these articles authors need to complete and include a PRISMA-P checklist (please find it from http://prisma-statement.org/prismastatement/Checklist.aspx) and upload as a supplementary file. Authors MUST ensure that all points are included and state page numbers where each item can be found. IJHPM welcomes study protocols for any study design. We will not consider the manuscript if the data collection is complete. Protocols for studies that will require ethical approval, such as trials, will not be considered without receiving the approval. By publishing your study protocol at the IJHPM, you are not committed to submit subsequent reports of the study to IJHPM, although we do welcome such submissions. Study protocols should be maximum 5000 words (excluding abstract, figures, tables, and references) and cover the following components: Title: this should include the specific study type, e.g. randomised controlled trial. Abstract: this should be structured with the following sections. Background; Methods and Analysis; Discussion; Registry and number (if the protocol had been registered in a registry system). Background: explain the rationale for the study and the gap in the literature it may fill. Methods and Analysis: provide a thorough description of the study design, including sample selection; interventions to be measured; the sample size calculation; procedures, measurements and analytical techniques; a data analysis plan. Discussion: discuss how the methods and statistics will meet the study aims. We recommend registering the protocol in PROSPERO(https://www.crd.york.ac.uk/PROSPERO). This makes the review process for these articles faster as they have already passed a review process. These articles must be of primary research, methodologically accurate, and relevant to international health policy and management. They should contain no more than 7000 words excluding structured abstract, tables, and references. Each manuscript should clearly state an objective or hypothesis; the design of study and methodology (including study setting, patients or participants, inclusion and exclusion criteria, sampling and data source); data analysis and interpretations; the main results of the study, discussing the results; addressing study limitations and the conclusion. For all original articles, a structured abstract is required (please see instructions for preparing Abstracts(https://www.ijhpm.com/journal/authors.note.php#Abstract)). In line with the Knowledge Translation movements, IJHPM has adopted an initiative by which all original articles are required to have Key Messages under two separate headings namely: Implications for Policy Makers and Implications for Public (please see instructions for preparing Key Messages(www.ijhpm.com/journal/authors.note#KeyMessages)). Only original articles require Key Messages. You can submit your manuscript using the Sample Word Template provided here(https://www.cmbr-journal.com/contacts ). Short communications are short articles (mini original articles) that present original and important preliminary findings that do not warrant publication as a full-length article but are still worthy of publication. Short communications should have an un-structured abstract and should not be more than 4000 words including references and up to three tables or figures. The main text should be sub-divided into background, methods, results, and discussion, but should be written as concisely as possible. To maintain brevity, these articles do not need key messages. These articles are invited on selected Cell. Mol. Biomed. Rep. publications mainly from leading scholars in the field. Authors of the lead article and editors decide whom to invite. These types of articles should not be more than 2000 words including maximum 2 figures or tables with an unstructured abstract. These articles are mainly written in response to published commentaries by authors whose articles have been subject to commentaries. These types of articles should not exceed 1000 words including maximum 1 table or figure, references and the main text. No abstract is required for these articles. We welcome short letters with topics of interest to the Cell. Mol. Biomed. Rep. readership. These letters should not exceed 700 words including only one table or figure, references and the main text. No abstract is required for these articles. Please insert the type of your manuscript on top of the Title Page and Main Manuscript. [1] Protection of Human Subjects and Animals in Research (Prepared Based on ICMJE's Recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals) In Cell. Mol. Biomed. Rep., when reporting experiments on human subjects, authors should indicate whether the procedures followed were in accordance with the ethical standards of the responsible committee on human experimentation (institutional and national) and with the Helsinki Declaration of 1975, as revised in 2013. If doubt exists whether the research was conducted in accordance with the Helsinki Declaration, the authors must explain the rationale for their approach and demonstrate that the institutional review body explicitly approved the doubtful aspects of the study. When reporting experiments on animals, authors should indicate whether the institutional and national guide for the care and use of laboratory animals was followed. Informed Consent in Patients and Study Participants (Prepared Based on ICMJE's Recommendations for the Conduct, Reporting, Editing and Publication of Scholarly Work in Medical Journals) In Cell. Mol. Biomed. Rep., patients have a right to privacy that should not be violated without informed consent. Identifying information, including names, initials, or hospital numbers, should not be published in written descriptions, photographs, or pedigrees unless the information is essential for scientific purposes and the patient (or parent or guardian) gives written informed consent for publication. Informed consent for this purpose requires that an identifiable patient be shown the manuscript to be published. Authors should disclose to these patients whether any potential identifiable material might be available via the Internet as well as in print after publication. Patient consent should be written and archived either with the journal, the authors, or both, as dictated by local regulations or laws. Nonessential identifying details should be omitted. Informed consent should be obtained if there is any doubt that anonymity can be maintained. For example, masking the eye region in photographs of patients is inadequate protection of anonymity. If identifying characteristics are altered to protect anonymity, such as in genetic pedigrees, authors should provide assurance, and editors should so note that such alterations do not distort scientific meaning. When informed consent has been obtained, it should be indicated in the published article. Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/journal/authors.note

cc40

Cell. Mol. Biomed. Rep.” is an open access, peer-reviewed, interdisciplinary journal that offers researchers and practitioner’s opportunities to publish original full-length papers, short communicatio

en

A type of viral pneumonia that broke out in Wuhan, China in December 2019, and new strains of it are spreading rapidly around the world, is called coronavirus disease 2019 (COVID-19). The incidence of cardiovascular complications has increased both in the general population and in patients diagnosed with the disease during the COVID-19 epidemic. One of the conditions is stress cardiomyopathy, which may be related to COVID-19. During the COVID-19 epidemic, stress cardiomyopathy may be present as a complication of acute infection or as an indirect consequence of quarantine. These conditions have created complications in patient care that have led to increased adverse outcomes, hospitalization, and medical costs. Stress cardiomyopathy is caused by various emotional and physical stressors such as anger, sadness, happiness, surgery, multiple medications, general anesthesia, and infectious diseases. The outbreak of the new coronavirus has posed an ongoing challenge for these patients with several medical and economic consequences. Providing useful information on stress and COVID-19 to people with heart disease and their families can be very important, and also, education and psychotherapy of heart patients can reduce the number of hospitalization and their complications. Selected author of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Velavan TP, Meyer CG (2020) The COVID-19 epidemic. Trop Med Int Health 25(3): 278-280. doi:https://doi.org/10.1111/tmi.13383 Fazeli-Nasab B (2021) Biological Evaluation of Coronaviruses and the Study of Molecular Docking, Linalool, and Thymol as orf1ab Protein Inhibitors and the Role of SARS-CoV-2 Virus in Bioterrorism. journal of ilam university of medical sciences 28(6):77-96. doi:https://doi.org/10.29252/sjimu.28.6.77 Pasqualetto MC, Secco E, Nizzetto M, Scevola M, Altafini L, Cester A, et al. (2020) Stress cardiomyopathy in COVID-19 disease. Eur J Case Rep Intern Med 7(6): 001718. doi:https://doi.org/10.12890/2020_001718 Giustino G, Croft LB, Oates CP, Rahman K, Lerakis S, Reddy VY, et al. (2020) Takotsubo cardiomyopathy in COVID-19. J Am Coll Cardiol 76(5): 628-629. doi:https://doi.org/10.1016/j.jacc.2020.05.068 Shafi AM, Shaikh SA, Shirke MM, Iddawela S, Harky A (2020) Cardiac manifestations in COVID‐19 patients-a systematic review. J Card Surg 35(8): 1988-2008. doi:https://doi.org/10.1111/jocs.14808 Bader F, Manla Y, Atallah B, Starling RC (2021) Heart failure and COVID-19. Heart Fail Rev 26(1): 1-10. doi:https://doi.org/10.1007/s10741-020-10008-2 Salah HM, Mehta JL (2020) Takotsubo cardiomyopathy and COVID-19 infection. Eur Heart J Cardiovasc Imaging 21(11): 1299-1300. doi:https://doi.org/10.1093/ehjci/jeaa236 Sahoo S, Mehra A, Grover S (2021) Stress cardiomyopathy/takotsubo syndrome and COVID-19: An important link to understand. Indian Journal of Clinical Cardiology 2(2): 124-125. doi:https://doi.org/10.1177%2F26324636211000580 Nguyen D, Nguyen T, De Bels D, Castro Rodriguez J (2020) A case of takotsubo cardiomyopathy with COVID 19. Eur Heart J Cardiovasc Imaging 21(9): 1052. doi:https://doi.org/10.1093/ehjci/jeaa152 Volume 1, Issue 2 - Serial Number 2 Cellular, Molecular and Biomedical Reports Receive Date: 15 July 2021 Revise Date: 01 September 2021 Accept Date: 04 November 2021 First Publish Date: 04 November 2021 Rahbar-Karbasdehi, E., & Rahbar-Karbasdehi, F. (2021). Clinical challenges of stress cardiomyopathy during coronavirus 2019 epidemic. Cellular, Molecular and Biomedical Reports, 1(2), 88-90. doi: 10.55705/cmbr.2021.145790.1018 Ebrahim Rahbar-Karbasdehi; Fatemeh Rahbar-Karbasdehi. "Clinical challenges of stress cardiomyopathy during coronavirus 2019 epidemic". Cellular, Molecular and Biomedical Reports, 1, 2, 2021, 88-90. doi: 10.55705/cmbr.2021.145790.1018 Rahbar-Karbasdehi, E., Rahbar-Karbasdehi, F. (2021). 'Clinical challenges of stress cardiomyopathy during coronavirus 2019 epidemic', Cellular, Molecular and Biomedical Reports, 1(2), pp. 88-90. doi: 10.55705/cmbr.2021.145790.1018 Rahbar-Karbasdehi, E., Rahbar-Karbasdehi, F. Clinical challenges of stress cardiomyopathy during coronavirus 2019 epidemic. Cellular, Molecular and Biomedical Reports, 2021; 1(2): 88-90. doi: 10.55705/cmbr.2021.145790.1018 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_145790.html

cc40

A type of viral pneumonia that broke out in Wuhan, China in December 2019, and new strains of it are spreading rapidly around the world, is called coronavirus disease 2019 (COVID-19). The incidence of

en

The UAE has announced that COVID-19 test will be mandatory for all inbound and transit passengers, including Emiratis, residents, and tourists, arriving via the country's airports, irrespective of the countries they are coming from. The decision to apply prior testing on all those coming to the country shall be applied as of 1st August without impingement on the mandatory testing measures that travellers have to follow upon arrival at the country's airports. According to a joint statement by the National Crisis and Emergency Management Authority, NCEMA, and the Ministry of Foreign Affairs and International Cooperation, MOFAIC, all passengers travelling through the country's airports to the EU countries and the UK, as well as other countries that require PCR test, have to get tested prior to boarding their respective planes. The announcement is in line with the country’s efforts to protect the health and safety of its citizens and residents and reduce the spread of coronavirus. Children under the age of 12 and those with severe and moderate disabilities will be exempted from the test requirement, which has 96 hours of validity from the date of testing. NCEMA and MoFAIC highlighted the necessity for all airlines operating in the UAE to comply with these requirements.

https://covid19.ncema.gov.ae/en/News/Details/1393

cc40

The UAE has announced that COVID-19 test will be mandatory for all inbound and transit passengers, including Emiratis, residents, and tourists, arriving via the country's airports, irrespective of the

en

This would promote better bug reporting when things are down and shorten time to recover. It would also help users understand what's happening in general if they ran a query that fills the system RAM or something that isn't immediately fixable. T172086 Gigantic query results cause a SIGKILL and the query status do not update T137517 Wrong status of queries in Recent Queries list T278583 Quarry should detect a dead worker and report something better than "running" forever T307263: Kill all queries stuck in running or queued state T290146: Pressing the Stop button in Quarry results in a 500 error T264254: Prepare Quarry for multiinstance wiki replicas T265155: Quarry seems to hang somehow T170464: Quarry cannot store results with identical column names T111779: Time limit on quarry queries T133738: Quarry task running for a while T209000: Update status when internal error occurs in worker T274071: Quarry queries forever stuck in queue Bstorm triaged this task as Medium priority.Mar 26 2021, 7:51 PM2021-03-26 19:51:02 (UTC+0) Bstorm created this task. Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 26 2021, 7:51 PM2021-03-26 19:51:02 (UTC+0) Bstorm merged a task: T274071: Quarry queries forever stuck in queue.Mar 26 2021, 7:52 PM2021-03-26 19:52:06 (UTC+0) Bstorm moved this task from Backlog to Bugs (Endless Query Run) on the Quarry board. Bstorm merged a task: T209000: Update status when internal error occurs in worker. Bstorm added subscribers: Bdijkstra, RhinosF1, Framawiki. Bstorm added a subscriber: zhuyifei1999. Bstorm added a parent task: T172086: Gigantic query results cause a SIGKILL and the query status do not update.Mar 26 2021, 7:54 PM2021-03-26 19:54:10 (UTC+0) Bstorm added a parent task: T137517: Wrong status of queries in Recent Queries list.Mar 26 2021, 7:56 PM2021-03-26 19:56:18 (UTC+0) Bstorm merged a task: T133738: Quarry task running for a while. Bstorm merged a task: T111779: Time limit on quarry queries . Bstorm added subscribers: QEDK, Liuxinyu970226. Bstorm added subscribers: Jarekt, Dvorapa, StudiesWorld. Bstorm merged a task: T170464: Quarry cannot store results with identical column names.Mar 26 2021, 7:58 PM2021-03-26 19:58:24 (UTC+0) Bstorm added subscribers: awight, Wurgl, Thjarkur and 8 others. Bstorm mentioned this in T264254: Prepare Quarry for multiinstance wiki replicas.Mar 26 2021, 10:44 PM2021-03-26 22:44:36 (UTC+0) zhuyifei1999 added a comment.Mar 27 2021, 9:25 AM2021-03-27 09:25:47 (UTC+0) Hmm. Is the goal trying to find when a worker gets SIGKILL-ed? Celery does internally detect when a worker dies, as per the logs, but I did not figure out how to hook it so that it would report to the db. Wurgl added a comment.Mar 27 2021, 10:11 AM2021-03-27 10:11:12 (UTC+0) At least one occurrence of this error can be reproduced with a simple query like "Select page_title, page_title from page where page_id = 1", see T265155 or look at https://quarry.wmflabs.org/query/53652 Bstorm added a comment.Mar 30 2021, 3:17 PM2021-03-30 15:17:15 (UTC+0) In T278583#6951002, @zhuyifei1999 wrote: Hmm. Is the goal trying to find when a worker gets SIGKILL-ed? Celery does internally detect when a worker dies, as per the logs, but I did not figure out how to hook it so that it would report to the db. When it gets SIGKILL-ed or maybe also if other things happen...but mostly when it gets SIGKILL-ed because that's what I see happening regularly. If there's some kind of hook to place in a try: except: raise that'd be slick in general as well because anything that does cause exception also causes the confusing state just like SIGKILL does. Thanks @Wurgl, that reproducible example should help. Overall, this is a bug that has it's own workboard column, so it seems like a place to spend some time if it has been confusing people for that many years. nskaggs moved this task from Bugs (Endless Query Run) to Planning on the Quarry board.Aug 2 2021, 8:44 PM2021-08-02 20:44:12 (UTC+0) GeoffreyT2000 moved this task from Planning to Bugs (Endless Query Run) on the Quarry board.Apr 30 2022, 4:14 AM2022-04-30 04:14:43 (UTC+0) rook mentioned this in T290146: Pressing the Stop button in Quarry results in a 500 error.May 6 2022, 7:54 PM2022-05-06 19:54:51 (UTC+0) rook mentioned this in T307263: Kill all queries stuck in running or queued state.May 18 2022, 11:14 AM2022-05-18 11:14:53 (UTC+0) rook merged a task: T307263: Kill all queries stuck in running or queued state. rook added subscribers: GeoffreyT2000, rook. rook added a comment.May 18 2022, 11:18 AM2022-05-18 11:18:06 (UTC+0) Workers sometimes die unexpectedly, and leave the db in the state described "Running". One method to clean this up may be to inspect the running processes on the quarry database. As a dead worker will not have a running process, Any process that is in the running state and is older than the oldest process in quarry can be updated to "failed" from "running". I believe this will clean out any not really running processes that are older than an hour. Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T278583

cc40

This would promote better bug reporting when things are down and shorten time to recover. It would also help users understand what's happening in general if they ran a query that fills the system RAM

en

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/subscriptions/list/PHID-TASK-wsdv2u5d5yivtrteoljp/

cc40

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this

en

This year, for the first time ever, the Wikimedia Foundation’s Global Advocacy and Public Policy team sponsored the Digital Rights and Inclusion Forum (DRIF). The forum is hosted by the Paradigm Initiative, and aims to bring together digital rights activists and scholars from across Africa to work towards a digitally inclusive and rights respecting future for the continent. Supporting DRIF is part of our team’s support for events for digital rights activists, who advocate for policy frameworks and regulations that promote human rights on the internet. It is also a way to promote knowledge equity and expand participation in knowledge creation and sharing in the region. Through our sponsorship of DRIF, the Foundation covered internet access costs for a number of registered attendees participating in online events, ensuring that there could be greater access to and participation in the Forum among African civil society groups and individuals. DRIF is a mixture of both in-person and online events and sessions that run from mid-April to mid-May 2022. We connected with one of the DRIF organizers, Thobekile Matimbe from Paradigm Initiative, to learn more about what impact the event has made for digital rights discussions, coalition engagements, and advocacy work across the continent. Q: Can you please tell us who you are, and what you do at the Paradigm Initiative? My name is Thobekile Matimbe. I am a Community Manager at Paradigm Initiative (PIN). I have worked at PIN for almost 2 years now, and coordinate the Digital Rights and Inclusion Forum (DRIF) as well as manage our coalition engagements and advocacy work. Q: What is your most recent experience with Wikimedia? Our collaboration with Wikimedia in hosting DRIF22, which has been extraordinary as it enabled over 350 additional attendees to join the Forum with the necessary data support (editor’s note: this support focused on data packages for connectivity) that the Foundation provided. Q: What is your event’s focus? The 9th edition of DRIF focused on digital inclusion and digital rights under the theme, “Towards a digitally inclusive and rights-respecting Africa.” The online event held from 12–14 April had over 500 attendees who engaged with diverse topics such as women’s rights online, digital inclusion for persons with disabilities, and online media freedoms, to name a few. DRIF was also held in person in 17 African countries. Q: What outcomes in terms of digital policy or partnerships do you hope will be sparked as a result of this conference? We hope that the African states can craft better policies and laws, which promote digital inclusion and review the current normative standards to ensure compliance with international standards. In addition, one of the key outcomes of hosting DRIF is to provide an important strategy for engaging all relevant stakeholders, including the private sector, in shaping internet freedom in Africa. As PIN, we hope attendees continue to raise awareness of the issues discussed in their respective countries, and will build on the networks that are forged during the Forum. Q: What similarities and/or differences do you see between last year’s and this year’s conference? Last year we were not able to offer data support to attendees. In total, DRIF21 reached 445 attendees. This year, through the Wikimedia support, we were able to involve more people and the bar was raised! Over 500 attendees joined DRIF22, of which 372 benefited from Wikimedia’s data support. Q: How do you see Wikimedia fitting into the conversations and topics that were aired at the conference this year and, more broadly, in the digital rights space across Africa? Wikimedia has a part to play in raising awareness on digital rights issues and supporting activities that promote digital inclusion in Africa. More support is welcome in the future to ensure that platforms like DRIF reach an even wider audience, not only at virtual sessions, but also at in-person convenings in different countries. One of the topics discussed this year had to do with how African languages can have a meaningful space on the internet. Looking at Wikipedia, this is an area of ongoing development and engagement where it is possible to ensure African languages are given more visibility online. Q: What other Paradigm Initiative projects are keeping you busy in your digital rights work? We have our Digital Rights Media Fellowship programs planned for the year. Through these fellowships we hope to reach the media to enhance their awareness and reporting of digital rights issues. We recently had the launch of our annual report on the state of digital rights and inclusion in Africa, “Londa,” which covers 22 African countries (a title of Zulu origin calling for action to protect or defend). The launch took place at our DRIF22 closing Media Parley on 20 May 2022 in Nairobi, Kenya. We are also looking forward to releasing a short film, which will capture the key findings of the report. Apart from this, we are conducting advocacy initiatives in Africa, engaging at the national level with governments and the private sector on the findings of our annual report, and also making representations to the African Commission on Human and Peoples’ Rights at relevant ordinary sessions, among other projects. If you are interested in learning more about these and similar events, follow the Global Advocacy and Public Policy team on Twitter to stay up-to-date on public policy issues that affect free knowledge. Comments are closed automatically after 21 days. Posted in Global Advocacy, Main page (EN), Policy & AdvocacyTagged digital rights, Digital Rights and Inclusion Forum, global advocacy, public policy Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2022/05/31/the-digital-rights-and-inclusion-forum-shaping-internet-freedom-in-africa/

cc40

This year, for the first time ever, the Wikimedia Foundation’s Global Advocacy and Public Policy team sponsored the Digital Rights and Inclusion Forum (DRIF). The forum is hosted by the Paradigm Initi

en

After the eminent success of the previous two editions of the WikiGap edit-a-thons, the Swedish Embassy in Skopje decided to continue with the good practice and decided to hold the event in the second half of the year, which prompted the Macedonian Wikipedia community to look for an alternative in an editing day on “Macedonian women” to commemorate International Women’s Day. The outbreak of the COVID-19 pandemic, however, has taken a toll on the event and led to changing to an online environment. Another novelty was the Gender gap editing week immediately succeeding the online edit-a-thon. The WikiGap online edit-a-thon was a four-hour event that took place on 30 September using the Zoom platform. At the beginning, introductory speeches to welcome participants were given from representatives of the three partnering organisations — Swedish Embassy, UN Women and Shared Knowledge — followed by a brief training about how to get started with Wikipedia and how to use the content translation tool. The remaining time of the event was dedicated to writing articles on the Macedonian Wikipedia, with participants being mentored by experienced Wikipedians. Inspired by the persistent efforts that the medics put to tackle the pandemic, the main topic of this year’s event were famous and influential females in the field of medicine. For that purpose, three lists of females in the field were proposed — namely, physicians, pharmacists and dentists. The two-volume Macedonian Encyclopedia, published by the Macedonian Academy of Sciences and Arts, was recommended as a useful reference work, while the WikiGapFinder tool and the archive of the Macedonian assembly members were put forth in order to easily get suggestions about topics with non-existing articles on the Macedonian Wikipedia. Group photo of participants in WikiGap Skopje 2020 (Credit: Toni Ristovski, CC-BY-SA 4.0) Contributions were tracked on the event’s dashboard. A total of 18 participants — mostly female and first-time editors — created 61 and improved 2 articles. More than one half of the edited articles were about local personalities with no articles on any other Wikipedia. The Gender gap editing week The Gender gap editing week took place immediately after the conclusion of the online edit-a-thon and its scope covered famous Swedish and Macedonian women. Besides the Swedish embassy in Skopje and Shared Knowledge, the initiative was additionally supported by two other organisations — the National Youth Council of Macedonia and MladiHub — and was organised on a competitive basis. In a similar way as for the online edit-a-thon, contributions were tracked on the initiative’s dashboard. A total of 8 participants — all female — enriched the Macedonian Wikipedia with 477 new and 37 improved articles. The top three contributors according to the total number of bytes added were invited for a Nobel dinner with the Swedish ambassador and received in-kind prizes in the form of trainings for acquiring advanced IT, digital and business skills for the top three participants. Comments are closed automatically after 21 days. Posted in Campaigns, Community Engagement, Gender gap, Partnerships & Events, Regional news, WikipediaTagged campaign, Editor Engagement, Gender gap on Wikipedia, online-attendance Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner Embassy of Sweden in Skopje, Macedonia This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2020/10/18/wikigap-skopje-2020-and-gender-gap-editing-week/

cc40

After the eminent success of the previous two editions of the WikiGap edit-a-thons, the Swedish Embassy in Skopje decided to continue with the good practice and decided to hold the event in the second

en

Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Document Type : Original Article 1 Department of Medical Biochemistry, Faculty of Medicine, Zabol University of Medical Sciences, Zabol, Iran 2 Department of Maternal Fetal Medicine, Zabol Medicinal Plants Research Center, Zabol University of Medical Sciences Zabol, Iran 3 Department of Internal Medicine, School of Medicine, Amir al momenin Hospital, Zabol University of Medical Sciences, Zabol, Iran 4 Forensic medicine and toxicology, Zabol University of medical sciences, Zabol, Iran. 5 Department of Microbiology, Medical Faculty- Zabol University of Medical Sciences, Zabol, Iran The DNA polymorphisms found in clinical strains of Mycobacterium tuberculosis drive altered physiology, virulence, and pathogenesis in them. This study aimed to investigate the association between IL23R 1142 G/A (Arg381Gln) and GM-CSF 3928 C/T (Ile117Thr) gene polymorphisms with the incidence rate of tuberculosis in the population of Sistan. This study was based on the descriptive and applied type. All patients with active pulmonary tuberculosis were referred to the tuberculosis center of Zabol city for one year, with an equal number of healthy people adapted to the patients examined in terms of age. After data collecting to compare the frequency of polymorphisms, the chi-square test and OR index were used using SPSS software version 16. We have found that the IL23R reduced-function allele 1142A and genotypes CC and TC were overrepresented, especially in the Pad subgroup compared with the control group (44% versus 42%, 21% versus 22%, and 44% versus 39%, respectively. Increased risks of TB with minimal/moderate lung involvement, respectively. Our results demonstrate that the reduced-function polymorphism 1142G ¡ A encoded by IL23R influences the outcome of disease severity of active pulmonary TB in ZABOL patients. The genotypic and allelic frequency of IL23R 1142 G/A, and GM-CSF 3928 C/T (Ile117Thr) polymorphism in patients with tuberculosis was significantly different from the control group and this polymorphism was associated with the incidence of tuberculosis in the population of Sistan. Selected author of this article by journal ِDr. Khadije Rezaie Keikhaie Zabol University of Medical Sciences This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Luo Y, Xue Y, Song H, Tang G, Liu W, Bai H, Yuan X, Tong S, Wang F, Cai Y, Sun Z (2022) Machine learning based on routine laboratory indicators promoting the discrimination between active tuberculosis and latent tuberculosis infection. Journal of Infection 84(5):648-657. doi:https://doi.org/10.1016/j.jinf.2021.12.046 Xin H, Zhang H, Yang S, Liu J, Lu W, Bai L, Cao X, Feng B, Jin Q, Gao L (2019) 5-Year Follow-up of Active Tuberculosis Development From Latent Infection in Rural China. Clinical Infectious Diseases 70(5):947-950. doi:https://doi.org/10.1093/cid/ciz581 Ghadimi D, de Vrese M, Heller KJ, Schrezenmeir J (2010) Lactic acid bacteria enhance autophagic ability of mononuclear phagocytes by increasing Th1 autophagy-promoting cytokine (IFN-Y) and nitric oxide (NO) levels and reducing Th2 autophagy-restraining cytokines (IL-4 and IL-13) in response to Mycobacterium tuberculosis antigen. International Immunopharmacology 10(6):694-706. doi:https://doi.org/10.1016/j.intimp.2010.03.014 Roetzer A, Diel R, Kohl TA, Rückert C, Nübel U, Blom J, Wirth T, Jaenicke S, Schuback S, Rüsch-Gerdes S, Supply P, Kalinowski J, Niemann S (2013) Whole Genome Sequencing versus Traditional Genotyping for Investigation of a Mycobacterium tuberculosis Outbreak: A Longitudinal Molecular Epidemiological Study. PLOS Medicine 10(2):e1001387. doi:https://doi.org/10.1371/journal.pmed.1001387 Feo F, De Miglio MR, Simile MM, Muroni MR, Calvisi DF, Frau M, Pascale RM (2006) Hepatocellular carcinoma as a complex polygenic disease. Interpretive analysis of recent developments on genetic predisposition. Biochimica et Biophysica Acta (BBA) - Reviews on Cancer 1765(2):126-147. doi:https://doi.org/10.1016/j.bbcan.2005.08.007 Cohen T, Helden PDv, Wilson D, Colijn C, McLaughlin MM, Abubakar I, Warren RM (2012) Mixed-Strain Mycobacterium tuberculosis Infections and the Implications for Tuberculosis Treatment and Control. Clinical Microbiology Reviews 25(4):708-719. doi:https://doi.org/10.1128/CMR.00021-12 Divangahi M, Khan N, Kaufmann E (2018) Beyond Killing Mycobacterium tuberculosis: Disease Tolerance. Frontiers in Immunology 9. doi:https://doi.org/10.3389/fimmu.2018.02976 Zhao ZZ, Savage NW, Sugerman PB, Walsh LJ (2002) Mast cell/T cell interactions in oral lichen planus. Journal of Oral Pathology & Medicine 31(4):189-195. doi:https://doi.org/10.1034/j.1600-0714.2002.310401.x Ramon-Luing LA, Carranza C, Téllez-Navarrete NA, Medina-Quero K, Gonzalez Y, Torres M, Chavez-Galan L (2022) Mycobacterium tuberculosis H37Rv Strain Increases the Frequency of CD3+TCR+ Macrophages and Affects Their Phenotype, but Not Their Migration Ability. International Journal of Molecular Sciences 23(1):329 Choreño Parra JA, Martínez Zúñiga N, Jiménez Zamudio LA, Jiménez Álvarez LA, Salinas Lara C, Zúñiga J (2017) Memory of Natural Killer Cells: A New Chance against Mycobacterium tuberculosis? Frontiers in Immunology 8. doi:https://doi.org/10.3389/fimmu.2017.00967 Ogongo P, Tezera LB, Ardain A, Nhamoyebonde S, Ramsuran D, Singh A, Ng’oepe A, Karim F, Naidoo T, Khan K, Dullabh KJ, Fehlings M, Lee BH, Nardin A, Lindestam Arlehamn CS, Sette A, Behar SM, Steyn AJC, Madansein R, Kløverpris HN, Elkington PT, Leslie A (2021) Tissue-resident-like CD4+ T cells secreting IL-17 control Mycobacterium tuberculosis in the human lung. The Journal of Clinical Investigation 131(10). doi:https://doi.org/10.1172/JCI142014 Damiani G, McCormick TS, Leal LO, Ghannoum MA (2020) Recombinant human granulocyte macrophage-colony stimulating factor expressed in yeast (sargramostim): A potential ally to combat serious infections. Clinical Immunology 210:108292. doi:https://doi.org/10.1016/j.clim.2019.108292 Puttur F, Gregory LG, Lloyd CM (2019) Airway macrophages as the guardians of tissue repair in the lung. Immunology & Cell Biology 97(3):246-257. doi:https://doi.org/10.1111/imcb.12235 Carey B, Trapnell BC (2010) The molecular basis of pulmonary alveolar proteinosis. Clinical Immunology 135(2):223-235. doi:https://doi.org/10.1016/j.clim.2010.02.017 Mishra A, Singh VK, Jagannath C, Subbian S, Restrepo BI, Gauduin MC, Khan A (2022) Human Macrophages Exhibit GM-CSF Dependent Restriction of Mycobacterium tuberculosis Infection via Regulating Their Self-Survival, Differentiation and Metabolism. Front Immunol 13:859116. doi:https://doi.org/10.3389/fimmu.2022.859116 Ehlers S, Schaible U (2013) The Granuloma in Tuberculosis: Dynamics of a Host–Pathogen Collusion. Frontiers in Immunology 3. doi:https://doi.org/10.3389/fimmu.2012.00411 Kopf M, Schneider C, Nobs SP (2015) The development and function of lung-resident macrophages and dendritic cells. Nature Immunology 16(1):36-44. doi:https://doi.org/10.1038/ni.3052 Baharom F, Rankin G, Blomberg A, Smed-Sörensen A (2017) Human Lung Mononuclear Phagocytes in Health and Disease. Frontiers in Immunology 8. doi:https://doi.org/10.3389/fimmu.2017.00499 Rolandelli A, Pellegrini JM, Hernández Del Pino RE, Tateosian NL, Amiano NO, Morelli MP, Castello FA, Casco N, Levi A, Palmero DJ, García VE (2019) The Non-synonymous rs763780 Single-Nucleotide Polymorphism in IL17F Gene Is Associated With Susceptibility to Tuberculosis and Advanced Disease Severity in Argentina. Frontiers in Immunology 10. doi:https://doi.org/10.3389/fimmu.2019.02248 Scheller J, Berg A, Moll JM, Floss DM, Jungesblut C (2021) Current status and relevance of single nucleotide polymorphisms in IL-6-/IL-12-type cytokine receptors. Cytokine 148:155550. doi:https://doi.org/10.1016/j.cyto.2021.155550 Lewinsohn DM, Leonard MK, LoBue PA, Cohn DL, Daley CL, Desmond E, Keane J, Lewinsohn DA, Loeffler AM, Mazurek GH, O’Brien RJ, Pai M, Richeldi L, Salfinger M, Shinnick TM, Sterling TR, Warshauer DM, Woods GL (2017) Official American Thoracic Society/Infectious Diseases Society of America/Centers for Disease Control and Prevention Clinical Practice Guidelines: Diagnosis of Tuberculosis in Adults and Children. Clinical Infectious Diseases 64(2):e1-e33. doi:https://doi.org/10.1093/cid/ciw694 American Thoracic S (2000) Diagnostic standards and classification of tuberculosis in adults and children. Am J Respir Crit Care Med 161:1376-1395. doi:https://doi.org/1571417124337616000 Zakeri S, Pirahmadi S, Mehrizi AA, Djadid ND (2011) Genetic variation of TLR-4, TLR-9 and TIRAP genes in Iranian malaria patients. Malaria Journal 10(1):77. doi:https://doi.org/10.1186/1475-2875-10-77 Bafica A, Scanga CA, Feng CG, Leifer C, Cheever A, Sher A (2005) TLR9 regulates Th1 responses and cooperates with TLR2 in mediating optimal resistance to Mycobacterium tuberculosis. Journal of Experimental Medicine 202(12):1715-1724. doi:https://doi.org/10.1084/jem.20051782 Kuai S-G, Ou Q-F, You D-H, Shang Z-B, Wang J, Liu J, Zhou X-K, Pei H, Huang L-H (2016) Functional polymorphisms in the gene encoding macrophage migration inhibitory factor (MIF) are associated with active pulmonary tuberculosis. Infectious Diseases 48(3):222-228. doi:https://doi.org/10.3109/23744235.2015.1107188 Jiang D, Wubuli A, Hu X, Ikramullah S, Maimaiti A, Zhang W, Wushouer Q (2015) The variations of IL-23R are associated with susceptibility and severe clinical forms of pulmonary tuberculosis in Chinese Uygurs. BMC Infectious Diseases 15(1):550. doi:https://doi.org/10.1186/s12879-015-1284-2 Abdelaal EB, Abdelsamie HM, Attia SM, Amr KS, Eldahshan RM, Elsaie ML (2021) Association of a novel Granulocyte-Macrophage Colony-Stimulating Factor (GM-CSF)-3928C/T and GM-CSF(3606T⁄C) Promoter gene polymorphisms with the pathogenesis and severity of acne vulgaris: A case-controlled study. Journal of Cosmetic Dermatology 20(11):3679-3683. doi:https://doi.org/10.1111/jocd.14481 Robinson RT (2017) T Cell Production of GM-CSF Protects the Host during Experimental Tuberculosis. mBio 8(6):e02087-02017. doi:https://doi.org/10.1128/mBio.02087-17 Saeki H, Tsunemi Y, Asano N, Nakamura K, Sekiya T, Hirai K, Kakinuma T, Fujita H, Kagami S, Tamaki K (2006) Analysis of GM-CSF gene polymorphisms (3606T/C and 3928C/T) in Japanese patients with atopic dermatitis. Clinical and Experimental Dermatology 31(2):278-280. doi:https://doi.org/10.1111/j.1365-2230.2005.02052.x Volume 1, Issue 3 Cellular, Molecular and Biomedical Reports Receive Date: 17 March 2021 Revise Date: 22 June 2021 Accept Date: 29 July 2021 First Publish Date: 01 December 2021 Rezaie-Kahkhaie, K., Rezaie-Keikhaie, K., Rezaie-Kahkhaie, L., Saravani, K., & kamali, A. (2021). The relationship between IL23R 1142G / A (Arg381Gln) and GM-CSF 3928 C / T (Ile117Thr) gene polymorphism in Iranian patients with tuberculosis disease. Cellular, Molecular and Biomedical Reports, 1(3), 113-121. doi: 10.55705/cmbr.2021.356674.1059 Kolsoum Rezaie-Kahkhaie; Khadije Rezaie-Keikhaie; Leli Rezaie-Kahkhaie; Khadije Saravani; Atefeh kamali. "The relationship between IL23R 1142G / A (Arg381Gln) and GM-CSF 3928 C / T (Ile117Thr) gene polymorphism in Iranian patients with tuberculosis disease". Cellular, Molecular and Biomedical Reports, 1, 3, 2021, 113-121. doi: 10.55705/cmbr.2021.356674.1059 Rezaie-Kahkhaie, K., Rezaie-Keikhaie, K., Rezaie-Kahkhaie, L., Saravani, K., kamali, A. (2021). 'The relationship between IL23R 1142G / A (Arg381Gln) and GM-CSF 3928 C / T (Ile117Thr) gene polymorphism in Iranian patients with tuberculosis disease', Cellular, Molecular and Biomedical Reports, 1(3), pp. 113-121. doi: 10.55705/cmbr.2021.356674.1059 Rezaie-Kahkhaie, K., Rezaie-Keikhaie, K., Rezaie-Kahkhaie, L., Saravani, K., kamali, A. The relationship between IL23R 1142G / A (Arg381Gln) and GM-CSF 3928 C / T (Ile117Thr) gene polymorphism in Iranian patients with tuberculosis disease. Cellular, Molecular and Biomedical Reports, 2021; 1(3): 113-121. doi: 10.55705/cmbr.2021.356674.1059 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_155090.html

cc40

Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) P

en

Beta Features, a new way for users to try out new features on Wikipedia and other Wikimedia sites before they are released for everyone; The launch of our search for a VP of Engineering; A retrospective by the Mobile engineering team on best practices for collaboration while working distributedly; The activation of OAuth on Wikimedia wikis, which allows users to authorize third-party applications to take actions on their behalf without sharing their password; A presentation of the “Wikidata concept cloud“; A retrospective on the ability to add musical scores to pages on Wikimedia sites. Note: We’re also providing a shorter, simpler and translatable version of this report that does not assume specialized technical knowledge. 146 unique committers contributed patchsets of code to MediaWiki. The total number of unresolved commits went from around 1122 to about 1230. About 29 shell requests were processed. 4.1 Editor retention: Editing tools Are you looking to work for Wikimedia? We have a lot of hiring coming up, and we really love talking to active community members about these roles. Software Engineer – Core Features Software Engineer – VisualEditor (Features) Software Engineer – Language Engineering Senior Software Engineer – Team Lead Software Engineer Data Analytics (Back End) Graphic Design Interns – Paid Jeff Hall joined the Platform engineering group as a member of the QA team (announcement). Aaron Arcos joined the Platform engineering group as a volunteer developer working with the Multimedia team (announcement). Dario Taraborelli was promoted to the position of Senior Research Scientist, Research and Data team lead. (announcement). Aaron Halfaker was promoted to the position of Research Scientist (announcement). Moiz Syed joined the User Experience team as User Experience Designer (announcement). A new dynamic proxy system has been deployed on Labs; it allows the admin of any project to arrange for public web access and a dedicated DNS hostname for a project instance without requesting an IP address. Labs staff and volunteers will now be reclaiming quite a few IPs as existing projects migrate to a dynamic proxy setup. The WMF has hired a short-term contractor, Mike Hoover, to assist with the migration of Labs infrastructure from Tampa to our new datacenter in Ashburn. Mike has spent a lot of time exploring the existing infrastructure and running test setups; soon he will start to configure the new OpenStack nodes in production. Andrew Bogott has been working on cleaning up stale and unused resources. He’s working on some automatic documentation that will help users track the status of their projects and instances with an eye towards predicting the impact of the coming migration. Labs suffered two brief outages: a brief, self-inflicted network failure, and a longer outage during which one of the virtualization hosts failed. Both outages were swiftly resolved, but there’s a bit of lag as some tools and services failed to come back properly afterwards due to poor distribution of virtual servers (inter alia, both the grid master and the shadow [backup] master were on the same server). Preparation for the move to the Ashburn data center is well in progress, with the new storage server being physically configured this week as well as the new hardware servers for user databases (including the new PostgreSQL instance intended for OpenStreetMap). Editor retention: Editing tools In November, the VisualEditor team continued to improve the stability and performance of the system, and add new features. The deployed version of the code was updated three times (1.23-wmf3, 1.23-wmf4 and 1.23-wmf5). Most of the team’s focus was on fixing bugs, and on some major infrastructure changes, splitting out the OOJS and OOJS-UI libraries from VisualEditor to make them available to other teams. Much of the team travelled to the Open Source Language Summit in Pune, India to learn more about how to improve VisualEditor for a variety of languages, scripts, users and systems. Two new members of the QA team joined in to help improve VisualEditor – Jeff Hall and Rummana Yasmeen, and thanks to them, the automated browser tests have expanded in breadth and depth of coverage. Work continued on major new features like full rich copy-and-paste from external sources, a dialog for quickly adding citation templated references, and a tool to insert characters not available on users’ keyboards. The editor was made available by default on just over 100 additional Wikipedias as part of the continuing roll-out. VisualEditor was also enabled for opt-in testing on Swedish Wiktionary and Wikimedia Sweden’s wiki, the first time it has been available on a non-Wikipedia production wiki. November saw the deployment of major changes to the DOM spec in coordination with the VisualEditor team. Link types are now marked up by semantics rather than syntax, interwiki links are detected automatically, categories are marked as page properties and more. During the deployment, we found that the newer libraries used by the web service front-end were buggy. We reverted the library upgrade and contributed fixes upstream. This incident prompted us to work on tests for the HTTP web service to catch issues like this in continuous integration. After these issues were sorted out, we continued with continuous improvement and fixes. Editing support for magic words and categories was improved, several dirty diff issues were fixed and the API was refined for page-independent wt2html and html2wt conversion. See our deployment page for details. Cassandra load testing for the Rashomon storage service continued and uncovered several issues that were reported back upstream. With Cassandra 2.0.3 the 2.0 branch is now stabilizing in time to make deployment in December feasible. Cassandra is now stable at extremely high write loads of around 900 revisions per second, which is more than 10 times the load we experience in production. In November, we deployed Notifications on the German and Italian Wikipedias, completing our worldwide release of this tool. Fabrice Florin, Denis Barthel, Jan Eissfeldt, Erica Litrenta and Keegan Peterzell managed the community outreach for these final releases, while Benny Situ oversaw the technical deployments. Community response to Notifications has been generally favorable on all wikis. While feature development has now ended for this project, we expect new notifications and features to be developed by other teams in coming months. To learn more, visit our project hub, read the help page and join the discussion on the talk page. This month, the Flow team finished out the feature set for our minimum viable product. We added watchlist integration, the ability to see board, topic, and post histories, and did a first round of community feedback and testing with our product to date. We also prepared for release to production wikis in December by working on Operations and Security needs. In November, the Growth team primarily worked on refactoring the GuidedTour and GettingStarted extensions, including development of an API for the latter. This public API will be used by the Growth team, the Mobile team and others to deliver editing tasks to users across a variety of Wikipedia interfaces. The team also spent significant time on the research and design preparations for its anonymous editor acquisition and Wikipedia article creation projects. This included participating in a community Request for Comment about a potential Draft namespace for articles, requirements gathering, and working on a Draft namespace patch. Matthew Flaschen and Pau Giner attended the Wikimedia Diversity Conference and presented (along with Jared Zimmerman and Vibha Bamba) on how diversity related to the team’s engineering and product work. This month, we improved a feature that was built in October (allowing instructors to assign articles to student editors), completed a new feature (allowing instructors to add users as students) and started another one (displaying information about student editors’ courses on Special:Contributions). We fixed some bugs, and kept up with changes in MediaWiki core. We also continued preliminary work—started last month—towards renewing the UX and broadening the extension’s scope. During the last month, the team monitored the rollout of Wikipedia Zero via text (USSD/SMS) in partnership with Airtel Kenya and Praekelt for the first pilot of the program. Additionally, Yuri Astrakhan promoted the program abroad. The team also prepared code and configuration for approval, finalized IP addresses for zero-rating and deployed bugfixes for the Wikipedia app for Firefox OS. We added support for simpler JSON in configuration files, enhanced performance and redirect features and constrained ZeroRatedMobileAccess extension loading to guard against repeats of last month’s configuration bug. The Onboarding A/B Test resulted in an Edit Guider, now available. The overlay UI overhaul currently in beta is planned to become available on the main site. User profiles intent is also in testing in beta. Team highlights for this past month include a very successful Open Source Language Summit in Pune, India co-organized with Red Hat. More than 60 developers joined in to collaborate and work together on improving language support for Wikipedia on the web and mobile. Work sprints on integration of input methods in VisualEditor, Indic Fontbook specification, mobile input methods and content translation were held. The team also fixed and deployed several issues related to performance and saving preferences for the Universal Language Selector (ULS). Other tasks completed include creating a class for interlanguage links using where the Autonym font can be used only for autonym items. The team also worked on collating documentation about all initial inclusion requests for each web font served through ULS also documented in the font.ini files of each font in the repository. The DevOps sprint participants focused their efforts towards monitoring related work, specifically getting Logstash in production and puppetizing/migrating Graphite (both still in-progress). Cache related fixes were made to avoid users seeing outdated version of pages when using non canonical URL forms. A fix was made to the commons upload process to update all articles that use that page as users would expect. Before November 18, we were spinning up an aggressive plan to add many new wikis to CirrusSearch. On November 18, we had multiple incidents that caused us to roll all wikis using CirrusSearch back to Lucene; we’ve spent the rest of November implementing fixes for all issues discovered on the 18th. That is now done and we plan to switch all wikis that used to have CirrusSearch back to running it as a secondary search engine on December 2. We’ll attempt to restart our aggressive plan as soon as we’re comfortable with it again. Site performance and architecture We ran a controlled experiment to test the impact of module storage on performance. We expect to publish our findings within a week. We puppetized Graphite and MediaWiki’s profiling log aggregator and migrated them to our Ashburn data center. Finally, we started working on a replacement profiling log aggregator that will process and visualize profiling data from both client-side and server-side code. Our preliminary version of OAuth is now live on all Wikimedia wikis. Since the rollout, five OAuth consumers have been accepted. We’re hopeful many more consumers will be proposed. Work is progressing towards a planned launch of the application on 2013-12-19. The source code has been imported into an internal git repository and is now being managed via gerrit. A bugzilla component has been created under the Wikimedia product to track defects and feature requests. Several changesets are in review to complete the basic functionality of the application and prepare for an internal security review. Security auditing and response We released a security update to MediaWiki to fix a number of issues in core and extensions. Security reviews of Limn, GWTools and Flow extensions are in progress. This activity is still officially on hold. However, progress on the global rename user tool continued, as well as implementing global CSS/JS. November saw significant improvements to the QA documentation on mediawiki.org contributed by both staff and volunteers. Participants in the Google Code-in program made even more contributions, to both documentation and browser test code. The QA team welcomed new staff members Rummana Yasmeen and Jeff Hall, who made immediate contributions to the VisualEditor project and to the browser test automation. In November, the Beta cluster saw greatly improved support for testing Parsoid, the parsing engine behind VisualEditor. The Beta cluster also continues to provide a real-world simulation for the Flow project in advance of Flow’s limited release scheduled for December. Beta continues to be the the main test environment for MobileFrontend, CirrusSearch, and many other Wikimedia software projects. In November, we added significant browser test coverage for the Flow project, and the addition of Jeff Hall to WMF staff brought a focus to testing VisualEditor. Browser tests now reside in ten different repositories across WMF projects. November saw a increased browser test coverage for the Language, VisualEditor, and Flow projects, among others. The diversity of browser tests in project repositories has been a force behind great improvements in infrastructure, with code shared among the projects now residing in the repository at mediawiki/selenium. In November, the Engineering community team held their second monthly showcase, as well as their quarterly review for the July–September period. Andre Klapper and Quim Gil prepared and organized Wikimedia’s participation in Google Code-In. This includes supporting mentors and students by writing documentation and importing tasks. Code-related, Andre cleaned up Wikimedia Bugzilla’s custom CSS by removing 16 CSS files with 6 left to stay, prepared and tested patches for upgrading Wikimedia Bugzilla from version 4.2 to 4.4, updated the Greasemonkey triagescripts (e.g. stock answers to ping assignees), and sync’ed the “WeeklyReport” Bugzilla extension code with upstream. WMF’s Operations team installed new SSL certificates for bugzilla.wikimedia.org. The “shellpolicy” keyword in Bugzilla was renamed to “community-consensus-needed” and the “wikidata” keyword was removed. Furthermore, Andre created a draft for a Bugzilla etiquette. We started successfully Wikimedia’s first participation in Google Code-In. Six candidates were selected as new interns at the FOSS Outreach Program for Women – Round 7: Anu G Enchackal – UploadWizard:OSM Map Embedding (mentored by Gergő Tisza) Diwanshi Pandey – Complete the MediaWiki development course at Codecademy (Yuri Astrakhan) Brena Monteiro – mediawiki.org homepage redesign (Heather Walls and Quim Gil) Be Birchall – Clean up Parsoid round-trip testing UI, including using a templating system (Marc Ordinas and Subramanya Sastry) Maria Pacana – Clean up tracing/debugging/logging inside Parsoid (Subramanya Sastry and Arlo Breault) Niharika Kohli – Compact interlanguage links as a beta feature (Sucheta Ghoshal and Pau Giner) We also confirmed the participation of Wikimedia in the Facebook Open Academy program. In November, Guillaume Paumier‘s primary focus was on preparing for the Google Code-in program, and mentoring students once the program started. In 2 weeks, 18 students worked on writing discovery reports (candid essays from the perspective of newcomers to the Wikimedia technical community); among them, seven completed their task successfully. Guillaume also assembled and published the weekly technical newsletter and provided ongoing communications support for the engineering staff. Volunteer coordination and outreach Erik Moeller’s talk “The Wikipedia stack” was accepted for the main track session at FOSDEM. The call for proposals for the Wikis devroom at FOSDEM was extended until December 15. Wikimedia applied for a stand. A Request for Proposals for a technical writer contractor was also sent. Last, we helped establishing a routine around Architecture meetings. In November, Mark Holmquist and Gergő Tisza developed a second beta version of the Media Viewer, based on new designs by Pau Giner. For a more immersive experience, this next version displays larger images, as shown in the demo. We also released Beta Features on all Wikimedia wikis, where it is already used by thousands of users. This experimental program invites users to try out new features before they are released widely, then give feedback to developers. To use Beta Features, click on the small ‘Beta’ link next to your ‘Preferences’ on your site, or test the latest version on MediaWiki.org. Fabrice Florin managed product development, led the creation of the Multimedia Vision 2016 (with Pau Giner), hosted roundtable discussions and updated the team’s multimedia plans, based on community and team feedback. Bryan Davis, Aaron Schulz and Chris Steipp reviewed new code for the upcoming GLAM Toolset for batch uploads by museum curators. We also welcomed Aaron Arcos as volunteer software engineer, who is joining our multimedia team full-time through Spring 2014. To discuss these features and keep up with our work, we invite you to join the multimedia mailing list. We are also recruiting for a senior software engineer position on our team. We continued to make progress on event delivery via Kafka. We identified and tested solutions for issues encountered with event delivery from the Amsterdam data center. We also tested solutions to fix Ganglia logging issues. We concluded Phase 1 of Wikimetrics, by implementing asynchronous cohort validation, editor survivor and threshold metrics. We identified issues with over-counting page views, and deployed a fix in November. Data from July onward were restated. This month, we started work on metrics standardization, one of the team’s quarterly goals. We published a number of supportive analyses of new user acquisition, activation and retention as well as “active editors” to assess issues and potential benefits of new definitions. The outcome of this analysis will inform design decisions for new dashboards focused on editor engagement. In collaboration with the Platform team, we ran an A/B test to determine performance gains of localStorage. The results indicate that the use of localStorage significantly improves the site’s performance for the end user: Module storage is faster. Readers whose pages load slower tend to browse less. Mobile browsers don’t seem to benefit substantially from caching. We published the results of a test designed to explore if displaying a short tutorial could improve the first-edit completion rate of newly-registered users on mobile devices. The results support the hypothesis, indicating that edit guiders are a good onboarding strategy for new mobile users. We ran an analysis of anonymous editor acquisition as background research for new onboarding strategies designed by the Growth team and found that editors who edit as an IP right before registering an account are our most productive newcomers. On November 9, 2013 we hosted the inaugural Labs2 Wiki Research Hackathon: it was the first in a series of global events meant to “facilitate problem solving, discovery and innovation with the use of open data and open-source tools” (read the full announcement). Highlights from the event are available in the latest issue of the Research Newsletter. We are planning to host a new hackathon in Spring 2014 and we are actively seeking volunteers to host local and virtual meetups. The Kiwix project is funded and executed by Wikimedia CH. We have released two new versions of Kiwix for Android this month (1.5 & 1.6), providing many new features; most of them were developed by young new developers as part of the Google Code-in program. We have also released a new and unique tool to easily create ZIM file yourself from data on your hard drive; the tool is stable and can now be used. Work continues around tools based on Parsoid output, especially as we need to rewrite the ZIM-related code for the Mediawiki offline toolchain, currently under heavy re-engineering. The Wikidata project is funded and executed by Wikimedia Deutschland. Wikidata developers held an office hour to give a status update and answer questions (read the log). In addition, they worked on ranks, ordering of statements and the quantities datatype. The quantities datatype is needed, for example, to enter the number of inhabitants of a country in Wikidata. It is available for testing now on http://test.wikidata.org. Ranks will allow for certain statements to be marked as preferred or deprecated. This is for example useful to indicate a previous mayor of a city, or the number of inhabitants of a country in 1900. Magnus Manske wrote a gadget that allows you to additionally show Wikidata search results when doing a search on Wikipedia. He also extended the Reasonator tool to now also work for cities. Until now, it only supported people and species. The engineering management team continues to update the Deployments page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the annual goals, listing ongoing and future Wikimedia engineering efforts. This article was written collaboratively by Wikimedia engineers and managers. See revision history and associated status pages. A wiki version is also available. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Technology, WMF engineering reportsTagged report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/12/09/engineering-report-november-2013/

cc40

Beta Features, a new way for users to try out new features on Wikipedia and other Wikimedia sites before they are released for everyone; The launch of our search for a VP of Engineering; A retrospecti

en

When we started doing backy2 backups, the goal was recovering VMs that were hard to replace and our glance images in the event of a ceph cluster disaster (since we caused one by trying to involve the wrong VLANs during a network renumbering). Over time, backy2 has proven that it likes to occasionally explode, and it has exposed that some of our openstack APIs occasionally just return random errors or loss of auth (which is another problem). However, we've now introduced cinder (T269511: Attachable block storage in cloud-vps), which is intended to be more-persistent storage than VM disks, without backing it up and have had to remove VMs from the system over time. Ceph is now quite stable, but recovering it would require a proper mirror at this point anyway, which we don't have plans to implement so far. I'm suggesting we should stop supporting the backy2 backups since they are becoming increasingly unhelpful, and everything we support is extra work we could be putting elsewhere. It was just meant as a stopgap until we were sure we'd stabilized ceph, anyway. T289623: We almost never actually free up space from deleted VMs T289502: Figure out how to delete Glance images T209530: Build user data backup service based on remote sync rather than NFS T269511: Attachable block storage in cloud-vps Bstorm created this task.Aug 19 2021, 5:48 PM2021-08-19 17:48:44 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 19 2021, 5:48 PM2021-08-19 17:48:45 (UTC+0) Bstorm renamed this task from Shall we drop the backy2 backup jobs from ceph? to Shall we drop the backy2 backup jobs.Aug 19 2021, 5:49 PM2021-08-19 17:49:48 (UTC+0) Bstorm moved this task from Inbox to Needs discussion on the cloud-services-team (Kanban) board. nskaggs triaged this task as Medium priority.Aug 19 2021, 8:01 PM2021-08-19 20:01:43 (UTC+0) dcaro added a subscriber: dcaro.Aug 20 2021, 8:45 AM2021-08-20 08:45:16 (UTC+0) Though I agree that the current setup is not as useful as it could be, I do think that we should find a replacement first, this might require some refining, some random ideas, feel free to ignore them: Goals (as I understand them): Cloud VPS/toolforge (and maybe quarry/paws?) disaster recovery due to ceph breakage (deemed unlikely, so only for very critical VMs/volumes) Prevent disasters on the user side for any VPS project (ex. bad upgrade, filesystem corruption, bad puppet patch, rm -rf *, ...) Prevent disasters on the admin side for any VPS project (ex. removing a VM, bad puppet patch, ...) Backup targets (so far, might expand in the future with sway/radosgw/s3 stuff): a) critical/service VM images b) non-critical/service VM images c) critical/service cinder volumes (we have none right now afaik) d) non-critical/service cinder volumes Amount of infra needed: Amount of one-time effort needed (gauged): Amount of continuous effort needed (gauged): Similar approach to current: a) Back them up out of ceph and snapshots. (addresses 1/2/3, infra L, one-time L, continuous M) b) Back them up as ceph snapshots. (addresses 2/3, infra M, one-time M, continuous M) c) Back them up out of ceph and snapshots. (addresses 1/2/3, infra L, one-time L, continuous M) d) Back them up as ceph snapshots. (addresses 2/3, infra M, one-time M, continuous M) e) Back them out of ceph and snapshots. (addresses 1/2/3, infra L, one-time L, continuous M) a) Make sure to have an up-to-date and robust way of rebuilding the VMs (including no SPOF, this is ) (addresses 1/2/3, infra M, one-time XL, continuous M) -> this might be tricky and hard to achieve, or not ¯\_(ツ)_/¯ b) Back them up as ceph snapshots. (addresses 2/3, infra M, one-time M, continuous M) c) Back them up out of ceph and snapshots. (addresses 1/2/3, infra L, one-time L, continuous M) d) Back them up as ceph snapshots. (addresses 2/3, infra M, one-time M, continuous M) e) Back them out of ceph and snapshots. (addresses 1/2/3, infra L, one-time L, continuous M No assurance that we can recover any VM/volume/image so increased downtime risk and effect, but no work or infra at all needed for it (infra S, one-time S, continuous S). And of course, there's most probably many more options, specially if you get a better/different idea of the goals and backup targets. Sorry for the long post. Bstorm mentioned this in T289502: Figure out how to delete Glance images.Aug 23 2021, 9:39 PM2021-08-23 21:39:02 (UTC+0) Andrew mentioned this in T289623: We almost never actually free up space from deleted VMs.Aug 24 2021, 8:19 PM2021-08-24 20:19:36 (UTC+0) Andrew added a subscriber: Andrew.Aug 24 2021, 8:21 PM2021-08-24 20:21:38 (UTC+0) I generally think that it's good to have backups. I'd rather we moved forward towards backing up cinder volumes as well as or instead of VMs. Another path forward is to use swift and/or snapshots to allow users to effectively back up their own things as needed. I'm not sure I like that better than automatic universal backups though. Bstorm added a comment.Aug 24 2021, 11:00 PM2021-08-24 23:00:26 (UTC+0) My concern here is that we never planned this as a viable backup service in the first place. This was a stopgap solution selected quickly in order to have a buffer in case our ceph layout was somehow inherently unstable--and we now are convinced it is not. We had no cinder storage and only had ephemeral storage and necessarily-poorly-designed VMs. We have never announced this or provided it as a direct service to users except in an incidental case where we deleted a VM once because it was not intended to exist. We did not plan staffing or hardware resourcing for this as a long term backup solution. We chose backy2 because it was the least firmly warned against option that existed. Maintaining a system that wasn't intended to be permanent or intentionally planned is part of why the cloud easily burns out people and describes more of the setup than I'd like to think. If we go trying to design this out as a real service, we must also figure out how to staff and hardware resource it properly. We also should probably not be thinking of it in terms of VMs. Clouds where people are actually paying for the VMs don't provide VM backups. The design of Openstack is overall intended to be that if it's not on cinder or swift, it's temporary (life of the VM). By backing up the VMs, we are kind of upending that and duplicating the glance images in many ways, so I don't think it's a good idea and encourages poor behavior to begin with. Our old build of Openstack necessitated bad practices, but we've been working in the right direction since. I'd like to build on that. For user data, we have aimed for the past 3 years to provide a self-serve solution since we would otherwise need to provide a staffed service (which the NFS sort is, currently) (T209530). We bought the hardware for the previous vision for it, but since we have ceph, it seems a lot smarter to use snapshots, cinder and swift where we have quotas, multitenancy and self-serve out of the box. To complicate this, we are also users of this setup, and we should design backups of our own stuff that's in the cloud, but we should be doing that in ways that the users can use. When we go and just work around things with root, we make more work for ourselves and limit the help we can get from the community. So that's part of my context for this. Backups are good, but these aren't the backups we are looking for. To my mind this is a question not of "should we have backups" but "should we keep trying to prevent this specific kind of disaster at this point". Bstorm added a comment.Aug 24 2021, 11:18 PM2021-08-24 23:18:46 (UTC+0) In T289282#7297098, @dcaro wrote: Though I agree that the current setup is not as useful as it could be, I do think that we should find a replacement first, this might require some refining, some random ideas, feel free to ignore them: This is good thinking. I think we need to go through a planning process like this before we actually deploy a backup system, and that's part of why I kind of want to kill off this one. I don't think we should view it as needing replacing because it was really just a hack that won't scale as is and wasn't meant to be a real backup solution despite how much you and @Andrew managed to make it work like one. We've got software, but we don't have an actual plan or design for backups because we weren't really intending to do that. I'm interested if you think we should replace it first in the context of my rant above or if we are stable enough now to drop it so it stops absorbing disk space, work, alerts, etc and try to put time into the replacement besides that. Goals (as I understand them): Cloud VPS/toolforge (and maybe quarry/paws?) disaster recovery due to ceph breakage (deemed unlikely, so only for very critical VMs/volumes) Prevent disasters on the user side for any VPS project (ex. bad upgrade, filesystem corruption, bad puppet patch, rm -rf *, ...) Prevent disasters on the admin side for any VPS project (ex. removing a VM, bad puppet patch, ...) The goals for this system were so much less ambitious. It was really just "have a backout plan". It sort of became a lot more than that, but that's why I'm trying to stop and think about it here--especially with it causing space issues and with how much troubleshooting time it has absorbed. My version of your above goals are: Establish a service continuity plan for Cloud VPS itself. This has not been done and was almost funded, but then it wasn't. I think a ceph mirror of some kind would be part of that, ideally, which appears to be what most other openstack service providers are doing. Provide self-serve tools for Cloud VPS users to keep their data safe and prevent VMs from becoming pets instead of cattle that are easily replaced. Use those tools for WMCS-maintained VPS projects to set up service continuity plans for those projects. I feel like none of those are well-served by this setup, but that I am eager to prioritize doing them with a new setup. We could at least start the task since that doesn't change anyone's existing goals or plans, no? Bstorm added a comment.Aug 24 2021, 11:22 PM2021-08-24 23:22:43 (UTC+0) In T289282#7306233, @Andrew wrote: I generally think that it's good to have backups. I'd rather we moved forward towards backing up cinder volumes as well as or instead of VMs. What if we *only* backed up cinder volumes? I'm not sure I like that all that much either using this system since we aren't taking into account how the databases and such actually work (our backups would not be consistent state), but it would be closer to the practice of treating cinder like the valuable data and make it a better story for our users. I still have my concerns about this as a WMCS-provided service, though. Another path forward is to use swift and/or snapshots to allow users to effectively back up their own things as needed. I'm not sure I like that better than automatic universal backups though. I actually view the latter as the better option per my rants above. This means ceph backs up to ceph, of course.... Andrew closed this task as Declined.Sep 29 2021, 3:55 PM2021-09-29 15:55:22 (UTC+0) boldly closing! Lots of interesting discussion here but the answer to the main question is 'no' Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T289282

cc40

When we started doing backy2 backups, the goal was recovering VMs that were hard to replace and our glance images in the event of a ceph cluster disaster (since we caused one by trying to involve the

en

1 Department of Gynecology and Obstetrics, Basaksehir Cam and Sakura City Hospital, University of Health Science, Istanbul, Turkey 2 Department of Pharmacy, Faculty of Medical, Tianjin Medical University, Tianjin P.R. China 3 Department of Pharmacy, Faculty of Medical, Gasha technical Institute, Erbil, Iraq 4 Department of Biology, College of Education, Salahaddin University-Erbil, Erbil, Iraq 5 Department of Pharmacy, Faculty of Medical, Zhejiang Chinese Medical University, Hangzhou, Zhejiang, China 6 Research and Development Department, Giga Biotics, San Diego, California, USA Selected author of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Mueck W, Lensing AW, Agnelli G, Decousus H, Prandoni P, Misselwitz F (2011) Rivaroxaban. Clinical pharmacokinetics 50:675-686. doi:http://doi.org/10.2165/11595320-000000000-00000 De Vriese AS, Caluwé R, Van Der Meersch H, De Boeck K, De Bacquer D (2021) Safety and efficacy of vitamin K antagonists versus rivaroxaban in hemodialysis patients with atrial fibrillation: a multicenter randomized controlled trial. Journal of the American Society of Nephrology 32:1474-1483. doi:http://doi.org/10.1681/ASN.2020111566 Rymer JA, Webb L, McCall D, Hills MT, Wang TY (2021) Differences in Preferences Between Clinicians and Patients for the Use and Dosing of Direct Oral Anticoagulants for Atrial Fibrillation. Journal of the American Heart Association 10:e020697. doi:http://doi.org/10.1161/JAHA.120.020697 Fernández MS, Marín F, Rafols C, Arribas F, Barrios V, Cosín-Sales J, Sánchez MA (2021) Thromboembolic and bleeding events with rivaroxaban in clinical practice in Spain: impact of inappropriate doses (the EMIR study). Journal of Comparative Effectiveness Research 10:583-593. doi:http://doi.org/10.2217/cer-2020-0286 Kreutz R, Mantovani LG, Haas S, Monje D, Schneider J, Bugge J-P, Gebel M, Tamm M, Ageno W, Turpie AG (2019) XALIA-LEA: An observational study of venous thromboembolism treatment with rivaroxaban and standard anticoagulation in the Asia-Pacific, Eastern Europe, the Middle East, Africa and Latin America. Thrombosis research 176:125-132. doi:http://doi.org/10.1016/j.thromres.2019.02.010 Eerenberg E, Middeldorp S, Levi M, Lensing A, Büller H (2015) Clinical impact and course of major bleeding with rivaroxaban and vitamin K antagonists. Journal of Thrombosis and Haemostasis 13:1590-1596. doi:http://doi.org/10.1111/jth.13051 Siegal DM, Konkle BA (2014) What is the effect of rivaroxaban on routine coagulation tests? Hematology 2014, the American Society of Hematology Education Program Book 2014:334-336. doi:http://doi.org/10.1182/asheducation-2014.1.334 Tsai HON, Goh JJN, Aw JWX, Lin Y, Fong AYY, Tiong LL, Tan DS-Y (2018) Comparison of rivaroxaban concentrations between Asians and Caucasians and their correlation with PT/INR. Journal of thrombosis and thrombolysis 46:541-548. doi:https://doi.org/10.1007/s11239-018-1726-y Samama MM, Contant G, Spiro TE, Perzborn E, Le Flem L, Guinet C, Gourmelin Y, Rohde G, Martinoli J-L (2013) Laboratory assessment of rivaroxaban: a review. Thrombosis journal 11:1-7. doi:https://doi.org/10.1186/1477-9560-11-11 Rathbun S, Tafur A, Grant R, Esmon N, Mauer K, Marlar RA (2015) Comparison of methods to determine rivaroxaban anti-factor Xa activity. Thrombosis research 135:394-397. doi:https://doi.org/10.1016/j.thromres.2014.11.017 Robert J, Le Morvan V, Smith D, Pourquier P, Bonnet J (2005) Predicting drug response and toxicity based on gene polymorphisms. Critical reviews in oncology/hematology 54:171-196. doi:https://doi.org/10.1016/j.critrevonc.2005.01.005 Rocha V, Porcher R, Fernandes J, Filion A, Bittencourt H, Silva W, Vilela G, Zanette D, Ferry C, Larghero J (2009) Association of drug metabolism gene polymorphisms with toxicities, graft-versus-host disease and survival after HLA-identical sibling hematopoietic stem cell transplantation for patients with leukemia. Leukemia 23:545-556. doi:https://doi.org/10.1038/leu.2008.323 Prabhune SS, Dighe V, Pradhan NS (2015) Enantiomeric separation of rivaroxaban by a chiral liquid chromatographic method. International Journal of Pharmacy and Pharmaceutical Sciences 7:399-402 Wong C-K, White HD (2013) Rivaroxaban for the treatment of acute coronary syndromes. Expert opinion on pharmacotherapy 14:917-927. doi:https://doi.org/10.1517/14656566.2013.780029 Straub A, Roehrig S, Hillisch A (2010) Entering the era of non-basic P1 site groups: discovery of Xarelto™(Rivaroxaban). Current topics in medicinal chemistry 10:257-269. doi:https://doi.org/10.2174/156802610790725506 Werk AN, Cascorbi I (2014) Functional gene variants of CYP3A4. Clinical Pharmacology & Therapeutics 96:340-348. doi:https://doi.org/10.1038/clpt.2014.129 Gnerre C, Blättler S, Kaufmann MR, Looser R, Meyer UA (2004) Regulation of CYP3A4 by the bile acid receptor FXR: evidence for functional binding sites in the CYP3A4 gene. Pharmacogenetics and Genomics 14:635-645. doi:https://doi.org/10.1124/dmd.114.062836 García‐Martín E, Martínez C, Pizarro RM, García‐Gamito FJ, Gullsten H, Raunio H, Agúndez JA (2002) CYP3A4 variant alleles in white individuals with low CYP3A4 enzyme activity. Clinical pharmacology & therapeutics 71:196-204. doi:https://doi.org/10.1067/mcp.2002.121371 Li AP, Kaminski DL, Rasmussen A (1995) Substrates of human hepatic cytochrome P450 3A4. Toxicology 104:1-8. doi:https://doi.org/10.1016/0300-483X(95)03155-9 Drabina P, Feixová V, Sedlák M (2019) New synthetic strategy for preparation of the anticoagulant drug Rivaroxaban via an asymmetric Henry reaction. Tetrahedron Letters 60:99-101. doi:https://doi.org/10.1016/j.tetlet.2018.11.067 Hesselink DA, van Schaik RH, Van Der Heiden IP, van der Werf M, Gregoor PJS, Lindemans J, Weimar W, van Gelder T (2003) Genetic polymorphisms of the CYP3A4, CYP3A5, and MDR‐1 genes and pharmacokinetics of the calcineurin inhibitors cyclosporine and tacrolimus. Clinical Pharmacology & Therapeutics 74:245-254. doi:https://doi.org/10.1016/S0009-9236(03)00168-1 Matsumura K, Saito T, Takahashi Y, Ozeki T, Kiyotani K, Fujieda M, Yamazaki H, Kunitoh H, Kamataki T (2004) Identification of a novel polymorphic enhancer of the human CYP3A4 gene. Molecular pharmacology 65:326-334. doi:https://doi.org/10.1124/mol.65.2.326 Klein K, Thomas M, Winter S, Nussler AK, Niemi M, Schwab M, Zanger UM (2012) PPARA: a novel genetic determinant of CYP3A4 in vitro and in vivo. Clinical Pharmacology & Therapeutics 91:1044-1052. doi:https://doi.org/10.1038/clpt.2011.336 Rodríguez-Antona C, Sayi JG, Gustafsson LL, Bertilsson L, Ingelman-Sundberg M (2005) Phenotype–genotype variability in the human CYP3A locus as assessed by the probe drug quinine and analyses of variant CYP3A4 alleles. Biochemical and biophysical research communications 338:299-305. doi:https://doi.org/10.1016/j.bbrc.2005.09.020 Gellner K, Eiselt R, Hustert E, Arnold H, Koch I, Haberl M, Deglmann CJ, Burk O, Buntefuss D, Escher S (2001) Genomic organization of the human CYP3A locus: identification of a new, inducible CYP3A gene. Pharmacogenetics and Genomics 11:111-121. doi:https://doi.org/10.1097/00008571-200103000-00002 Bruckmueller H, Werk AN, Renders L, Feldkamp T, Tepel M, Borst C, Caliebe A, Kunzendorf U, Cascorbi I (2015) Which genetic determinants should be considered for tacrolimus dose optimization in kidney transplantation? A combined analysis of genes affecting the CYP3A locus. Therapeutic drug monitoring 37:288-295. doi:https://doi.org/10.1097/FTD.0000000000000142 Falzoi M, Mossa A, Congeddu E, Saba L, Pani L (2010) Multiplex genotyping of CYP3A4, CYP3A5, CYP2C9 and CYP2C19 SNPs using MALDI-TOF mass spectrometry. Pharmacogenomics 11:559-571. doi:https://doi.org/10.2217/pgs.09.172 Kubitza D, Becka M, Zuehlsdorf M, Mueck W (2007) Body weight has limited influence on the safety, tolerability, pharmacokinetics, or pharmacodynamics of rivaroxaban (BAY 59‐7939) in healthy subjects. The Journal of Clinical Pharmacology 47:218-226. doi:https://doi.org/10.1177/0091270006296058 Lorenzini K, Daali Y, Fontana P, Desmeules J, Samer C (2016) Rivaroxaban-induced hemorrhage associated with ABCB1 genetic defect. Frontiers in pharmacology 7:494. doi:https://doi.org/10.3389/fphar.2016.00494/full Gouin‐Thibault I, Delavenne X, Blanchard A, Siguret V, Salem J, Narjoz C, Gaussem P, Beaune P, Funck‐Brentano C, Azizi M (2017) Interindividual variability in dabigatran and rivaroxaban exposure: contribution of ABCB 1 genetic polymorphisms and interaction with clarithromycin. Journal of Thrombosis and Haemostasis 15:273-283. doi:https://doi.org/doi.org/10.1111/jth.13577 Nakagawa J, Kinjo T, Iizuka M, Ueno K, Tomita H, Niioka T (2021) Impact of gene polymorphisms in drug‐metabolizing enzymes and transporters on trough concentrations of rivaroxaban in patients with atrial fibrillation. Basic & Clinical Pharmacology & Toxicology 128:297-304. doi:https://doi.org/10.1111/bcpt.13488 Sychev D, Minnigulov R, Bochkov P, Ryzhikova K, Yudina I, Lychagin A, Morozova T (2019) Effect of CYP3A4, CYP3A5, ABCB1 gene polymorphisms on rivaroxaban pharmacokinetics in patients undergoing total hip and knee replacement surgery. High Blood Pressure & Cardiovascular Prevention 26:413-420. doi:https://doi.org/10.1007/s40292-019-00342-4 Hsieh K-P, Lin Y-Y, Cheng C-L, Lai M-L, Lin M-S, Siest J-P, Huang J-D (2001) Novel mutations of CYP3A4 in Chinese. Drug metabolism and disposition 29:268-273 Wojakowski E, Cheruvil C, Hassan A, Holsen M, Chen L, Rossi M, Wilcox N, Woodruff A (2020) Albumin and bleed risk in rivaroxaban treated patients. Journal of thrombosis and thrombolysis 50:1004-1011. doi:https://doi.org/10.1007/s11239-020-02092-w Escolar G, Carne X, Arellano-Rodrigo E (2015) Dosing of rivaroxaban by indication: getting the right dose for the patient. Expert opinion on drug metabolism & toxicology 11:1665-1677. doi:https://doi.org/10.1517/17425255.2015.1085022 De Vriese AS, Caluwé R, Bailleul E, De Bacquer D, Borrey D, Van Vlem B, Vandecasteele SJ, Emmerechts J (2015) Dose-finding study of rivaroxaban in hemodialysis patients. American Journal of Kidney Diseases 66:91-98. doi:https://doi.org/10.1053/j.ajkd.2015.01.022 Ashida R, Okamura Y, Ohshima K, Kakuda Y, Uesaka K, Sugiura T, Ito T, Yamamoto Y, Sugino T, Urakami K (2017) CYP3A4 gene is a novel biomarker for predicting a poor prognosis in hepatocellular carcinoma. Cancer genomics & proteomics 14:445-453. doi:https://doi.org/10.21873/cgp.20054 Hole K, Wollmann BM, Nguyen C, Haslemo T, Molden E (2018) Comparison of CYP3A4-inducing capacity of enzyme-inducing antiepileptic drugs using 4B-hydroxycholesterol as biomarker. Therapeutic drug monitoring 40:463-468. doi:https://doi.org/10.1097/FTD.0000000000000518 Lv J, Liu F, Feng N, Sun X, Tang J, Xie L, Wang Y (2018) CYP3A4 gene polymorphism is correlated with individual consumption of sufentanil. Acta Anaesthesiologica Scandinavica 62:1367-1373. doi:https://doi.org/10.1111/aas.13178 Yamamoto T, Nagafuchi N, Ozeki T, Kubota T, Ishikawa H, Ogawa S, Yamada Y, Hirai H, Iga T (2003) CYP3A4* 18: it is not rare allele in Japanese population. Drug metabolism and pharmacokinetics 18:267-268. doi:https://doi.org/10.2133/dmpk.18.267 Volume 1, Issue 1 - Serial Number 1 Cellular, Molecular and Biomedical Reports Receive Date: 02 August 2021 Revise Date: 20 September 2021 Accept Date: 16 October 2021 First Publish Date: 16 October 2021 Ercisli, M., Lechun, G., Azeez, S., Hamasalih, R., Song, S., & Aziziaram, Z. (2021). Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients. Cellular, Molecular and Biomedical Reports, 1(1), 33-41. doi: 10.55705/cmbr.2021.138880.1003 Muhammed Furkan Ercisli; Gao Lechun; Sarhang Hasan Azeez; Rebwar Muhammad Hamasalih; Siyan Song; Zahra Aziziaram. "Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients". Cellular, Molecular and Biomedical Reports, 1, 1, 2021, 33-41. doi: 10.55705/cmbr.2021.138880.1003 Ercisli, M., Lechun, G., Azeez, S., Hamasalih, R., Song, S., Aziziaram, Z. (2021). 'Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients', Cellular, Molecular and Biomedical Reports, 1(1), pp. 33-41. doi: 10.55705/cmbr.2021.138880.1003 Ercisli, M., Lechun, G., Azeez, S., Hamasalih, R., Song, S., Aziziaram, Z. Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients. Cellular, Molecular and Biomedical Reports, 2021; 1(1): 33-41. doi: 10.55705/cmbr.2021.138880.1003 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_138880.html

cc40

1 Department of Gynecology and Obstetrics, Basaksehir Cam and Sakura City Hospital, University of Health Science, Istanbul, Turkey 2 Department of Pharmacy, Faculty of Medical, Tianjin Medical Univers

en

Earlier today the folks over at Google provided an update on their progress using Translation Toolkit with volunteers and translators to improve the article count in smaller language versions of Wikipedia, including Arabic, Gujarati, Hindi, Kannada, Swahili, Tamil and Telugu.  Google is a passionate believer in the need to translate and bring more high quality works of text to less-represented languages on the web. Michael Galvez, a Product Manager from Google, presented the recent findings of these efforts at this year’s Wikimania in Gdańsk – which wrapped up on Sunday, July 11 of this year. We believe that translation is key to our mission of making information useful to everyone. For example, Wikipedia is a phenomenal source of knowledge, especially for speakers of common languages such as English, German and French where there are hundreds of thousands—or millions—of articles available. For many smaller languages, however, Wikipedia doesn’t yet have anywhere near the same amount of content available. Google is reporting an increase of about 16 million words so far due to the efforts of local volunteers and translators using the Translation Toolkit.  In Hindi Wikipedia these efforts have resulted in an increase in size of about 20 per cent. They continue their work directly with volunteers from these language projects, and continue to expand the capabilities of the translation toolkit in new languages. A big thanks for the ongoing efforts of the volunteers and translators, and to Google for continuing to invest time and resources in this great translation system. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Google’s translation work is amazing, world changing to a degree. I have friends in Hungary and Russia who write to me entire emails in their own language. I can use the google translate and their letters appear in highly readable english. And I can reply. And in chrome it is possible to translate webpages on the fly. Amazing. Game changing. Thanks to google, wikipedia etc for bringing me closer to my friends! Tobias (User:Church of emacs) Great project! I don’t know much about this tool, so please forgive me if my question is stupid: Most “big” Wikipedia language versions are quite strict in copyright issues, e.g. respecting the license and attributing authors properly. Large efforts, like transwikiimport or importupload are taken to ensure that translated articles contain the history of the original page. So my question is: how does author attribution work with the google toolkit? Are the authors of the original article properly attributed? Is the history imported? Seeing that this is a medium/large software project, one would expect that license issues are considered as… Read more » What happened on the Google Challenge @علاء the Swahili Wikipedia A Review on Google Translation project in Tamil Wikipedia Google’s Tool Kit is a amazing tool but is it acceptable to allow Google to use Wikipedia as a testing platform for their project???. Obviously they encourage people to translate using Toolkit because they want more “Translation Memory” in many languages. I personally believe we should not encourage such efforts where GNU project and its volunteers should not be used for a proprietary reserved product. The problem denoted by the Swahili language Wikipedia is so scary… Too much of anything is not good!! Posted in Friends, HighlightsTagged Google, translation, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2010/07/15/update-on-translation-toolkit/

cc40

Earlier today the folks over at Google provided an update on their progress using Translation Toolkit with volunteers and translators to improve the article count in smaller language versions of Wikip

en

ask @jeena for help with running the test in CI (all it needs to do is to run npm start and npm run selenium-test) WIP The first Selenium test T272143 QTE + Apps automation T262437: [Bug] Page content service is deployed with localhost links to the CSS and JS, breaking all pages that have been edited recently zeljkofilipin created this task.Oct 1 2020, 5:42 PM2020-10-01 17:42:21 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 1 2020, 5:42 PM2020-10-01 17:42:21 (UTC+0) zeljkofilipin triaged this task as Medium priority.Oct 1 2020, 5:42 PM2020-10-01 17:42:33 (UTC+0) zeljkofilipin moved this task from Inbox to Test engineering on the Quality-and-Test-Engineering-Team (QTE) board. zeljkofilipin moved this task from Backlog ⏪ to In Progress 🏋️‍♂️ on the User-zeljkofilipin board. zeljkofilipin updated the task description. (Show Details) zeljkofilipin added subscribers: Jpita, Tsevener, Jrbranaa and 2 others.Oct 1 2020, 5:48 PM2020-10-01 17:48:48 (UTC+0) @ABorbaWMF @Jrbranaa @Dbrant @Jpita @Tsevener let me know if I misunderstood what needs to be done. Jpita added a comment.Oct 1 2020, 7:07 PM2020-10-01 19:07:23 (UTC+0) What's the purpose of this? Who's the tester in the api team? or a better question, who's the team owner of this api endpoints? zeljkofilipin added a comment.Oct 2 2020, 8:43 AM2020-10-02 08:43:24 (UTC+0) In T264340#6510150, @Jpita wrote: What's the purpose of this? Both iOS and Android apps just render HTML pages provided by those API endpoints. They had problems in the past where endpoints changed and it broke the apps. Apps teams said the first and easy step could be a few tests for the endpoints. Who's the tester in the api team? Nobody, as far as I know. or a better question, who's the team owner of this api endpoints? Product Infrastructure, according to https://www.mediawiki.org/wiki/Developers/Maintainers (the repository is https://github.com/wikimedia/mobileapps). Jpita added a comment.Oct 2 2020, 8:58 AM2020-10-02 08:58:17 (UTC+0) Can we ping someone from that team to check if they have any unit or integration tests? Make 0 sense to me for us to be creating tests for other teams work zeljkofilipin added a comment.Oct 2 2020, 10:36 AM2020-10-02 10:36:44 (UTC+0) @Jpita according to source code, there are tests: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/services/mobileapps/+/refs/heads/master/test Jpita added a comment.Oct 2 2020, 11:38 AM2020-10-02 11:38:17 (UTC+0) In T264340#6512010, @zeljkofilipin wrote: @Jpita according to source code, there are tests: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/services/mobileapps/+/refs/heads/master/test it seems they even use the Dog page nothing for us to do here then? Tsevener added a subscriber: JoeWalsh.Oct 5 2020, 3:02 PM2020-10-05 15:02:33 (UTC+0) @Jpita @zeljkofilipin This seemed like good low-hanging fruit for first tests to have with the QTE team, since it has recently broken in the past for us and is displayed directly in both iOS and Android apps. Correct me if I'm wrong @JoeWalsh but the thinking was that the existing tests on the mobileapps repo should just be unit tests on the service itself, whereas QTE could write tests against the service at a higher level to test it's integration with other systems. Originally we were thinking against the Beta cluster though there were some concerns that the fact that it's different data could throw things off (Dog already looks different in the Beta cluster vs. Prod). This was the last issue we had, a config change that caused the base domain referenced in the response to be localhost, essentially breaking all the CSS and JS on the screen. Jpita added a comment.Oct 7 2020, 3:16 PM2020-10-07 15:16:48 (UTC+0) My main concerns with this is (something that happened in both my teams): we create tests for an endpoint we don't own (running the tests against production) something breaks the tests, by now it's too late because the code is already in production and our users already encounter the bug we create tests for an endpoint we don't own (running the tests against beta cluster) the tests pass, but then we find a bug in production because the data is different (as you mentioned in the previous comment) we create tests for an endpoint we don't own (running the tests against beta cluster) assuming the code is deployed to beta cluster when is merged to master BUT before train deployment the tests fail, when we create a ticket and contact the team owner of the endpoint, the code is already merged and the bug is not a priority so the train still runs and the KNOW bug hits production -- How it should be done -- The team that owns the endpoint: has tests for it running in the CI with every build does not break existing functionalities by creating different versions of the endpoint instead of changing the existing one Where does the QTE team help: Having one dedicated person on the team OR helping the team with their test plan zeljkofilipin added a comment.Oct 7 2020, 5:51 PM2020-10-07 17:51:13 (UTC+0) @Jpita maybe there's a misunderstanding here. This is supposed to be an experiment, not a test we will maintain forever. Jpita added a comment.Oct 7 2020, 5:55 PM2020-10-07 17:55:19 (UTC+0) In T264340#6526379, @zeljkofilipin wrote: @Jpita maybe there's a misunderstanding here. This is supposed to be an experiment, not a test we will maintain forever. That’s not mentioned anywhere in the task. And we’re talking about real problems that happened to our teams so not an experiment, something really needed JoeWalsh added subscribers: • dcipoletti, WDoranWMF.Oct 7 2020, 6:44 PM2020-10-07 18:44:02 (UTC+0) The team that owns the endpoint: has tests for it running in the CI with every build does not break existing functionalities by creating different versions of the endpoint instead of changing the existing one Where does the QTE team help: Having one dedicated person on the team OR helping the team with their test plan @Jpita in this case, there were two separate services owned by two separate teams involved (RESTBase and the mobileapps service). There are unit tests running with the CI for each service, but as far as I know, there aren't extensive tests of the integration of those two services. The initial thought was to test against the beta cluster since that's the earliest point the two services are integrated. Happy to hear other ideas though - ideally issues would get caught on commit before making it to the beta cluster. CC @WDoranWMF and @dcipoletti if they have other thoughts or ideas. We're specifically trying to prevent more issues like T262437 and T263798 from cropping up as changes are made to the services that currently run through RESTBase. Jrbranaa added a comment.Edited · Oct 7 2020, 7:12 PM2020-10-07 19:12:54 (UTC+0) I think the points/concerns brought up by @Jpita are quite valid. These are some of the experiences that we've had across a number of teams that we've worked with. That being said, there are a lot of separate problems that we need to address that will need to be done in parallel. When, where, and how something gets tested all have an impact on the usefulness of the test(s). These need to be better defined in an API testing strategy that needs to be developed. This is something that QTE and Platform Infrastructure will partner up to develop. In the near-term, I think creating some automated tests to cover past known regressions is a useful and interesting first step. Although it doesn't address many of the larger concerns, it does get us going down the path of better understanding the scope of the problem. If it is also something that the Mobile Teams can use as a basic acceptance test of the API, even better. zeljkofilipin added a comment.Oct 8 2020, 8:36 AM2020-10-08 08:36:11 (UTC+0) In T264340#6512322, @Jpita wrote: it seems they even use the Dog page nothing for us to do here then? I've forgotten to reply to this. As far as I can see, that's just a fixture, a static HTML page that is used by other tests, not the test itself. It does mean that there is a test for it, for example in test/diff/test-spec.js#246 new TestSpec('en.wikipedia.org', 'transform/html/to/mobile-html', ['Dog'], { suffix: 'html', method: 'POST', headers: { 'Content-Type': 'text/html' }, payloadFile: 'test/fixtures/Dog.html' }), This page is tested, but since it breaks (in context of android/ios apps) from time to time, it's not tested in a way that would catch the problem (for example T262437: [Bug] Page content service is deployed with localhost links to the CSS and JS, breaking all pages that have been edited recently). gerritbot added a comment.Oct 13 2020, 4:56 PM2020-10-13 16:56:20 (UTC+0) Change 633787 had a related patch set uploaded (by Zfilipin; owner: Zfilipin): [mediawiki/services/mobileapps@master] WIP The first Selenium test gerritbot added a project: Patch-For-Review.Oct 13 2020, 4:56 PM2020-10-13 16:56:21 (UTC+0) zeljkofilipin updated the task description. (Show Details)Oct 14 2020, 5:55 PM2020-10-14 17:55:19 (UTC+0) zeljkofilipin updated the task description. (Show Details) zeljkofilipin updated the task description. (Show Details)Oct 14 2020, 5:57 PM2020-10-14 17:57:30 (UTC+0) zeljkofilipin added a subscriber: jeena. zeljkofilipin updated the task description. (Show Details)Oct 15 2020, 5:55 PM2020-10-15 17:55:51 (UTC+0) zeljkofilipin removed zeljkofilipin as the assignee of this task.Dec 22 2020, 6:39 PM2020-12-22 18:39:41 (UTC+0) zeljkofilipin moved this task from In Progress 🏋️‍♂️ to Next ⏭ on the User-zeljkofilipin board. zeljkofilipin added a parent task: T272143: QTE + Apps automation.Jan 15 2021, 1:06 PM2021-01-15 13:06:53 (UTC+0) zeljkofilipin moved this task from Next ⏭ to Backlog ⏪ on the User-zeljkofilipin board.Feb 11 2021, 6:39 PM2021-02-11 18:39:38 (UTC+0) gerritbot added a comment.Mar 11 2021, 3:35 PM2021-03-11 15:35:34 (UTC+0) Change 633787 abandoned by Zfilipin: [mediawiki/services/mobileapps@master] WIP The first Selenium test Maintenance_bot removed a project: Patch-For-Review.Mar 12 2021, 9:49 AM2021-03-12 09:49:08 (UTC+0) zeljkofilipin raised the priority of this task from Medium to Needs Triage.May 17 2021, 1:51 PM2021-05-17 13:51:34 (UTC+0) zeljkofilipin closed this task as Declined.Sep 16 2021, 11:04 AM2021-09-16 11:04:34 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T264340

cc40

ask @jeena for help with running the test in CI (all it needs to do is to run npm start and npm run selenium-test) WIP The first Selenium test T272143 QTE + Apps automation T262437: [Bug] Page content

en

How do Wikimedia programs and projects start? In the beginning, there is an idea. If you want to build a better Wikimedia and want to focus on a specific issue, Individual Engagement Grants (IEG) can help you achieve this. The IEG program is staging a new open call for proposals. You can submit yours this month from September 1st to the 30th! Your idea doesn’t have to be a massive, game-changing project (although big ideas are welcome!). It could be a new tool or gadget, an experiment in improving a community space, research on an important issue facing Wikimedia projects, or something else aimed at helping build Wikimedia community and content. Whether you need $200 or $30,000, Individual Engagement Grants can cover project development time and expenses for you and your team. User I JethroBT at IdeaLab mixer in Wikimania London. The program has a flexible schedule and reporting structure and the Grantmaking staff are there to support you through all stages of the process. We’ll even help you find project mentors! After you submit your proposal, the grantmaking team will go through it to make sure it meets all eligibility criteria. Proposals should support the achievement of Wikimedia’s mission and strategic priorities. We are looking for experiments with high potential for learning and impact, and lots of community engagement, among other selection criteria. Proposals are commented on and reviewed by the community from October 1 to November 3rd, and grantees are announced on December 5. Some ideas funded in the past include a pronunciation recording tool for Wiktionary, a Medicine Translation Project, Reimagining Wikipedia Mentorship, and both community organizing initiatives and research on Wikipedia’s gender gap. Check out the list of all projects that received funding in the past IEG round for inspiration. Test your idea and get advice Tuesday, Sept 16, 1600 UTC: How to write an IEG proposal. Thursday, Sept 25, 1700 UTC: IEG Proposal Clinic. Sunday, Sept 28, 1700 UTC: IEG Proposal Clinic. Do you have have a good idea, but you are worried that it isn’t developed enough for a grant? Put it into the IdeaLab, where volunteers and staff will give you advice and guidance on how to bring it to life. During the month of September, we’ll be hosting three online Hangout sessions for real-time help on how to make your proposal better. The first one, How to Write an IEG Proposal, will take place on September 16, at 1600 UTC. By working together we can make an impact on the future of Wikimedia projects. We are excited to see the new ways your project ideas can support the Wikimedia community! Share your proposal in September. María Cruz, Community Coordinator of Program Evaluation & Design Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in GrantmakingTagged Individual Engagement Grants, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/09/02/open-call-for-grants-proposals/

cc40

How do Wikimedia programs and projects start? In the beginning, there is an idea. If you want to build a better Wikimedia and want to focus on a specific issue, Individual Engagement Grants (IEG) can

en

While attempting to handle some "lost" File: namespace page ediths from P8677 list (T173070) I encoutered a problem with merging history of pages in File: namespace: moving a "lost" File: page (with no file associated) onto a recently deleted file generates an error: The page could not be moved, for the following reasons: The title is the same; cannot move a page over itself. A page of that name already exists, or the name you have chosen is not valid. Please choose another name. (The target file was actually deleted at that time.) The problem is not related to the files listed, as an attempt to move a fresh, recently created file page gives the same result. Tested with the following examples (all failed): Any hints how to merge wikitext revision of such pages are welcome. T227590: Renaming a page in File namespace without a file associated triggers an error T173070: Set default aliases for Project_talk namespace P8677 Masterwork From Distant Lands Ankry created this task.Jun 30 2019, 9:04 AM2019-06-30 09:04:48 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 30 2019, 9:04 AM2019-06-30 09:04:49 (UTC+0) Reedy added projects: MediaWiki-File-management, Commons.Jun 30 2019, 10:44 AM2019-06-30 10:44:09 (UTC+0) Restricted Application added a project: Multimedia. · View Herald TranscriptJun 30 2019, 10:44 AM2019-06-30 10:44:10 (UTC+0) Ankry updated the task description. (Show Details)Jun 30 2019, 1:28 PM2019-06-30 13:28:46 (UTC+0) Steinsplitter added a subscriber: Steinsplitter.Jul 1 2019, 2:10 PM2019-07-01 14:10:58 (UTC+0) zhuyifei1999 added a subscriber: zhuyifei1999.Jul 2 2019, 3:45 AM2019-07-02 03:45:49 (UTC+0) Urbanecm added a subscriber: Urbanecm.Jul 6 2019, 12:39 PM2019-07-06 12:39:47 (UTC+0) You can do this manually, by merging the wikitext by hand and then deleting the prefixed version. Ankry added a comment.Jul 6 2019, 12:52 PM2019-07-06 12:52:27 (UTC+0) In T226922#5310950, @Urbanecm wrote: You can do this manually, by merging the wikitext by hand and then deleting the prefixed version. The intention of history merging is to keep the original contributor information, not only the content. Ankry added a comment.Jul 6 2019, 1:43 PM2019-07-06 13:43:16 (UTC+0) As suggested by @Urbanecm I also tried Special:MergePages with a strange result: Source page: File:T173070Ryde Tesco pedestrian walkway.JPG Destination page: File:Ryde Tesco pedestrian walkway.JPG No revisions can be merged. Wargo added a subscriber: Wargo.Jul 8 2019, 11:16 AM2019-07-08 11:16:49 (UTC+0) You can only merge revisions from "older" page to "newer". "Newer" is based on first revision (I suppose). So, you need... merge some revisions from the "valid" page to the "orphaned" page and then do second merge to move all again to the valid title. But be careful! Test it first outside production! And wait for another solutions first! Ankry mentioned this in T227590: Renaming a page in File namespace without a file associated triggers an error.Jul 9 2019, 3:06 PM2019-07-09 15:06:18 (UTC+0) This is probably a side effect of T227590. MGA73 added a subscriber: MGA73.Feb 4 2021, 5:00 PM2021-02-04 17:00:53 (UTC+0) I have not testet it but if it is only possible to move a page if there is also a file involved then this might work. If you want to move File:A.jpg ---> File:B.jpg Undelete File:B.jpg (if it is deleted and if not just skip to 2) Move File:B.jpg ---> File:A.jpg Move File:A.jpg ---> File:B.jpg Delete File:B.jpg (if it is supposed to be deleted) Ankry added a comment.Feb 5 2021, 11:48 PM2021-02-05 23:48:21 (UTC+0) In T226922#6804308, @MGA73 wrote: I have not testet it but if it is only possible to move a page if there is also a file involved then this might work. If you want to move File:A.jpg ---> File:B.jpg Undelete File:B.jpg (if it is deleted and if not just skip to 2) Move File:B.jpg ---> File:A.jpg Move File:A.jpg ---> File:B.jpg Delete File:B.jpg (if it is supposed to be deleted) Well, as the initial problem was triggered by a software error, it may be simpler to ask developers to move the revision server-side. I am just wondering if there is a good reason that moving such page is not allowed even by privileged users. Note, I can find a dosen reasons when the undelete/move mentioned above is technically not possible or not allowed by policy or very inconvenient. Umherirrender added a project: MediaWiki-Page-rename.Apr 7 2022, 8:29 PM2022-04-07 20:29:54 (UTC+0) Umherirrender added a subscriber: Umherirrender. Works for me locally: Create page "File:TestUpload.jpg" with a real file over Special:Upload Create "File:TestNoUpload.jpg" with action=edit Move "File:TestNoUpload.jpg" to "File:TestUpload.jpg" with success Is this still an issue or a software/server outage which is already resolved? Umherirrender removed a subscriber: Umherirrender.Jun 19 2022, 7:39 PM2022-06-19 19:39:54 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T226922

cc40

While attempting to handle some "lost" File: namespace page ediths from P8677 list (T173070) I encoutered a problem with merging history of pages in File: namespace: moving a "lost" File: page (with n

en

1 Department of biological science, Faculty of Science, Kurdistan University, Sanandaj, Kurdistan, Iran 2 Nanobiotechnology Department, Faculty of Innovative Science and Technology, Razi University, Kermanshah, Iran 3 Laser Research Centre, Faculty of Health Science, University of Johannesburg, Doornfontein, 2028, South Africa 4 Wellman Centre for Photomedicine, Massachusetts General Hospital, Boston, MA 02114, USA 5 Department of Dermatology, Harvard Medical School, Boston, MA 02115, USA 6 Australasian Nanoscience and Nanotechnology Initiative (ANNI), 8054 Monash University LPO, Clayton, Victoria 3168, Australia 8 Laboratory of Pharmacology and Molecular Chemistry; Department of Biological Chemistry; Regional University of Cariri; Rua Coronel Antônio Luis 1161, Pimenta, CEP 63105-000, Crato, Ceará, Brazil Bacterial infections can be caused by contamination of labile blood products with specific bacteria, such as Staphylococcus aureus and Staphylococcus epidermidis. Hospital equipment, bio-protective equipment, delivery systems, and medical devices can be easily contaminated by microorganisms. Multidrug-resistant bacteria can survive on various organic or inorganic polymeric materials for more than 90 days. Inhibiting the growth and eradicating these microorganisms is vital in blood transfusion processes. Blood bags and other related medical devices can be improved by the incorporation of organic or inorganic nanomaterials, particularly silicon dioxide (SiO2) nanoparticles. The addition of solid organic or inorganic nanoparticles to synthetic polymers or biopolymers can provide new properties in addition to antimicrobial activity. Among these NPs, formulations composed of SiO2 nanoparticles and polymers have been shown to improve the mechanical and antimicrobial properties of catheters, prosthetic inserts, blood bags, and other medical devices SiO2 nanoparticles possess several advantages, including large-scale synthetic availability, simple one-pot synthesis methods, porous structure for loading antibacterial agents, good biocompatibility, and thermal stability. Plasticized polyvinyl chloride is the main polymer, which has been functionalized by these nanoparticles. In this review, we discuss the recent advances and challenges regarding the functionalization of polyvinyl chloride by SiO2 nanoparticles to hinder bacterial contaminations in blood products. Selected author of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Lin CK, Leung JNS, So BKL, Lee CK (2014) Donor selection for blood safety: is it still necessary? ISBT Science Series 9(1):26-29. doi:https://doi.org/10.1111/voxs.12056 Murphy MF, Stanworth SJ, Yazer M (2011) Transfusion practice and safety: current status and possibilities for improvement. Vox Sanguinis 100(1):46-59. doi:https://doi.org/10.1111/j.1423-0410.2010.01366.x Basu D, Kulkarni R (2014) Overview of blood components and their preparation. Indian J Anaesth 58(5):529-537. doi:https://doi.org/10.4103/0019-5049.144647 Innerhofer P, Fries D, Mittermayr M, Innerhofer N, von Langen D, Hell T, Gruber G, Schmid S, Friesenecker B, Lorenz IH, Ströhle M, Rastner V, Trübsbach S, Raab H, Treml B, Wally D, Treichl B, Mayr A, Kranewitter C, Oswald E (2017) Reversal of trauma-induced coagulopathy using first-line coagulation factor concentrates or fresh frozen plasma (RETIC): a single-centre, parallel-group, open-label, randomised trial. The Lancet Haematology 4(6):e258-e271. doi:https://doi.org/10.1016/S2352-3026(17)30077-7 Bresnick EH, Hewitt KJ, Mehta C, Keles S, Paulson RF, Johnson KD (2018) Mechanisms of erythrocyte development and regeneration: implications for regenerative medicine and beyond. Development 145(1):dev151423. doi:https://doi.org/10.1242/dev.151423 EASL Clinical Practice Guidelines on prevention and management of bleeding and thrombosis in patients with cirrhosis (2022). Journal of Hepatology). doi:https://doi.org/10.1016/j.jhep.2021.09.003 Kumar H, Gupta PK, Mishra DK, Sarkar RS, Jaiprakash M (2006) Leucodepletion and Blood Products. Med J Armed Forces India 62(2):174-177. doi:https://doi.org/10.1016/S0377-1237(06)80064-X Hadjesfandiari N, Khorshidfar M, Devine DV (2021) Current Understanding of the Relationship between Blood Donor Variability and Blood Component Quality. International journal of molecular sciences 22(8):3943. doi:https://doi.org/10.3390/ijms22083943 Beliën J, Forcé H (2012) Supply chain management of blood products: A literature review. European Journal of Operational Research 217(1):1-16. doi:https://doi.org/10.1016/j.ejor.2011.05.026 Lacetera N, Macis M, Slonim R (2012) Will There Be Blood? Incentives and Displacement Effects in Pro-social Behavior. American Economic Journal: Economic Policy 4(1):186-223. doi:https://doi.org/10.1257/pol.4.1.186 Kiss JE, Vassallo RR (2018) How do we manage iron deficiency after blood donation? British Journal of Haematology 181(5):590-603. doi:https://doi.org/10.1111/bjh.15136 Gifford SC, Strachan BC, Xia H, Vörös E, Torabian K, Tomasino TA, Griffin GD, Lichtiger B, Aung FM, Shevkoplyas SS (2018) A portable system for processing donated whole blood into high quality components without centrifugation. PLoS One 13(1):e0190827. doi:https://doi.org/10.1371/journal.pone.0190827 Chell K, Davison TE, Masser B, Jensen K (2018) A systematic review of incentives in blood donation. Transfusion 58(1):242-254. doi:https://doi.org/10.1111/trf.14387 Chen Z, Sun Y (2006) N-Halamine-Based Antimicrobial Additives for Polymers: Preparation, Characterization and Antimicrobial Activity. Ind Eng Chem Res 45(8):2634-2640. doi:https://doi.org/10.1021/ie060088a Dietvorst J, Vilaplana L, Uria N, Marco M-P, Muñoz-Berbel X (2020) Current and near-future technologies for antibiotic susceptibility testing and resistant bacteria detection. TrAC Trends in Analytical Chemistry 127:115891. doi:https://doi.org/10.1016/j.trac.2020.115891 Rajapaksha P, Elbourne A, Gangadoo S, Brown R, Cozzolino D, Chapman J (2019) A review of methods for the detection of pathogenic microorganisms. Analyst 144(2):396-411. doi:https://doi.org/10.1039/C8AN01488D Abbas-Al-Khafaji ZK, Aubais-aljelehawy Qh (2021) Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital. Cellular, Molecular and Biomedical Reports 1(2):60-68. doi:https://doi.org/10.55705/cmbr.2021.142761.1015 Almasian-Tehrani N, Alebouyeh M, Armin S, Soleimani N, Azimi L, Shaker-Darabad R (2021) Overview of typing techniques as molecular epidemiology tools for bacterial characterization. Cellular, Molecular and Biomedical Reports 1(2):69-77. doi:https://doi.org/10.55705/cmbr.2021.143413.1016 Franza T, Rogstam A, Thiyagarajan S, Sullivan MJ, Derré-Bobillot A, Bauer MC, Goh KGK, Da Cunha V, Glaser P, Logan DT, Ulett GC, von Wachenfeldt C, Gaudu P (2021) NAD+ pool depletion as a signal for the Rex regulon involved in Streptococcus agalactiae virulence. PLOS Pathogens 17(8):e1009791. doi:https://doi.org/10.1371/journal.ppat.1009791 Liang H, Mao Y, Sun Y, Gao H (2019) Transcriptional regulator ArcA mediates expression of oligopeptide transport systems both directly and indirectly in Shewanella oneidensis. Scientific Reports 9(1):13839. doi:https://doi.org/10.1038/s41598-019-50201-4 Aubais aljelehawy Qh, Hadi Alshaibah LH, Abbas Al- Khafaji ZK (2021) Evaluation of virulence factors among Staphylococcus aureus strains isolated from patients with urinary tract infection in Al-Najaf Al-Ashraf teaching hospital. Cellular, Molecular and Biomedical Reports 1(2):78-87. doi:https://doi.org/10.55705/cmbr.2021.144995.1017 Brecher Mark E, Hay Shauna N (2005) Bacterial Contamination of Blood Components. Clinical Microbiology Reviews 18(1):195-204. doi:https://doi.org/10.1128/CMR.18.1.195-204.2005 Dreier J, Störmer M, Kleesiek K (2007) Real-Time Polymerase Chain Reaction in Transfusion Medicine: Applications for Detection of Bacterial Contamination in Blood Products. Transfusion Medicine Reviews 21(3):237-254. doi:https://doi.org/10.1016/j.tmrv.2007.03.006 Levy JH, Neal MD, Herman JH (2018) Bacterial contamination of platelets for transfusion: strategies for prevention. Critical Care 22(1):271. doi:https://doi.org/10.1186/s13054-018-2212-9 Di Gaudio F, Indelicato S, Indelicato S, Tricoli MR, Stampone G, Bongiorno D (2018) Improvement of a rapid direct blood culture microbial identification protocol using MALDI-TOF MS and performance comparison with SepsiTyper kit. Journal of Microbiological Methods 155:1-7. doi:https://doi.org/10.1016/j.mimet.2018.10.015 Godbey EA, Thibodeaux SR (2019) Ensuring safety of the blood supply in the United States: Donor screening, testing, emerging pathogens, and pathogen inactivation. Seminars in Hematology 56(4):229-235. doi:https://doi.org/10.1053/j.seminhematol.2019.11.004 Saravani K, Afshari M, Aminisefat A, Bameri O (2021) Blood Sugar Changes in Patients with Acute Drug Poisoning. Cell Mol Biomed Rep 1(2):91-97. doi:http://dx.doi.org/10.55705/cmbr.2021.146061.1022 Crawford E, Kamm J, Miller S, Li LM, Caldera S, Lyden A, Yokoe D, Nichols A, Tran NK, Barnard SE, Conner PM, Nambiar A, Zinter MS, Moayeri M, Serpa PH, Prince BC, Quan J, Sit R, Tan M, Phelps M, Derisi JL, Tato CM, Langelier C (2020) Investigating Transfusion-related Sepsis Using Culture-Independent Metagenomic Sequencing. Clinical Infectious Diseases 71(5):1179-1185. doi:https://doi.org/10.1093/cid/ciz960 Panch SR, Bikkani T, Vargas V, Procter J, Atkins JW, Guptill V, Frank KM, Lau AF, Stroncek DF (2019) Prospective Evaluation of a Practical Guideline for Managing Positive Sterility Test Results in Cell Therapy Products. Biology of Blood and Marrow Transplantation 25(1):172-178. doi:https://doi.org/10.1016/j.bbmt.2018.08.003 Zhu Z, Wang Z, Li S, Yuan X (2019) Antimicrobial strategies for urinary catheters. Journal of Biomedical Materials Research Part A 107(2):445-467. doi:https://doi.org/10.1002/jbm.a.36561 Erythropel HC, Maric M, Nicell JA, Leask RL, Yargeau V (2014) Leaching of the plasticizer di(2-ethylhexyl)phthalate (DEHP) from plastic containers and the question of human exposure. Applied Microbiology and Biotechnology 98(24):9967-9981. doi:https://doi.org/10.1007/s00253-014-6183-8 Hasirci V, Hasirci N (2018) Polymers as Biomaterials. In: Hasirci V, Hasirci N (eds) Fundamentals of Biomaterials. Springer New York, New York, NY, pp 65-82. doi:https://doi.org/10.1007/978-1-4939-8856-3_5 Madhumanchi S, Srichana T, Domb AJ (2021) Polymeric Biomaterials. In: Narayan R (ed) Biomedical Materials. Springer International Publishing, Cham, pp 49-100. doi:https://doi.org/10.1007/978-3-030-49206-9_2 Tokhadzé N, Chennell P, Pereira B, Mailhot-Jensen B, Sautou V (2021) Critical Drug Loss Induced by Silicone and Polyurethane Implantable Catheters in a Simulated Infusion Setup with Three Model Drugs. Pharmaceutics 13(10). doi:https://doi.org/10.3390/pharmaceutics13101709 Costoya A, Velázquez Becerra LE, Meléndez-Ortiz HI, Díaz-Gómez L, Mayer C, Otero A, Concheiro A, Bucio E, Alvarez-Lorenzo C (2019) Immobilization of antimicrobial and anti-quorum sensing enzymes onto GMA-grafted poly(vinyl chloride) catheters. Int J Pharm 558:72-81. doi:https://doi.org/10.1016/j.ijpharm.2018.12.075 Zaokari Y, Persaud A, Ibrahim A (2020) Biomaterials for Adhesion in Orthopedic Applications: A Review. Engineered Regeneration 1:51-63. doi:https://doi.org/10.1016/j.engreg.2020.07.002 Zare M, Ghomi ER, Venkatraman PD, Ramakrishna S (2021) Silicone-based biomaterials for biomedical applications: Antimicrobial strategies and 3D printing technologies. Journal of Applied Polymer Science 138(38):50969. doi:https://doi.org/10.1002/app.50969 Xu C-a, Chen G, Tan Z, Hu Z, Qu Z, Zhang Q, Lu M, Wu K, Lu M, Liang L (2020) Evaluation of cytotoxicity in vitro and properties of polysiloxane-based polyurethane/lignin elastomers. Reactive and Functional Polymers 149:104514. doi:https://doi.org/10.1016/j.reactfunctpolym.2020.104514 Xu C-A, Nan B, Lu M, Qu Z, Tan Z, Wu K, Shi J (2020) Effects of polysiloxanes with different molecular weights on in vitro cytotoxicity and properties of polyurethane/cotton–cellulose nanofiber nanocomposite films. Polymer Chemistry 11(32):5225-5237. doi:https://doi.org/10.1039/D0PY00809E Aymes-Chodur C, Salmi-Mani H, Dragoe D, Aubry-Barroca N, Buchotte M, Roger P (2021) Optimization of microwave plasma treatment conditions on polydimethylsiloxane films for further surface functionalization. European Polymer Journal 150:110416. doi:https://doi.org/10.1016/j.eurpolymj.2021.110416 Chouirfa H, Bouloussa H, Migonney V, Falentin-Daudré C (2019) Review of titanium surface modification techniques and coatings for antibacterial applications. Acta Biomaterialia 83:37-54. doi:https://doi.org/10.1016/j.actbio.2018.10.036 Hage M, Khelissa S, Akoum H, Chihib N-E, Jama C (2022) Cold plasma surface treatments to prevent biofilm formation in food industries and medical sectors. Applied Microbiology and Biotechnology 106(1):81-100. doi:https://doi.org/10.1007/s00253-021-11715-y Alavi M, Webster TJ (2021) Recent progress and challenges for polymeric microsphere compared to nanosphere drug release systems: Is there a real difference? Bioorg Med Chem 33:116028. doi:https://doi.org/10.1016/j.bmc.2021.116028 Alavi M, Rai M (2020) Topical delivery of growth factors and metal/metal oxide nanoparticles to infected wounds by polymeric nanoparticles: an overview. Expert Rev Anti-Infect Ther 18(10):1021-1032. doi:https://doi.org/10.1080/14787210.2020.1782740 Alavi M, Nokhodchi A (2022) Micro- and nanoformulations of paclitaxel based on micelles, liposomes, cubosomes, and lipid nanoparticles: Recent advances and challenges. Drug Discovery Today 27(2):576-584. doi:https://doi.org/10.1016/j.drudis.2021.10.007 Sun W, Liu W, Wu Z, Chen H (2020) Chemical Surface Modification of Polymeric Biomaterials for Biomedical Applications. Macromolecular Rapid Communications 41(8):1900430. doi:https://doi.org/10.1002/marc.201900430 Yin L, Liu L, Zhang N (2021) Brush-like polymers: design, synthesis and applications. Chemical Communications 57(81):10484-10499. doi:https://doi.org/10.1039/D1CC03940G Liu M, Li S, Wang H, Jiang R, Zhou X (2021) Research progress of environmentally friendly marine antifouling coatings. Polymer Chemistry 12(26):3702-3720. doi:https://doi.org/10.1039/D1PY00512J Altinkok C, Karabulut HRF, Tasdelen MA, Acik G (2020) Bile acid bearing poly (vinyl chloride) nanofibers by combination of CuAAC click chemistry and electrospinning process. Materials Today Communications 25:101425. doi:https://doi.org/10.1016/j.mtcomm.2020.101425 Venkatesan R, Rajeswari N (2019) Preparation, Mechanical and Antimicrobial Properties of SiO2/ Poly(butylene adipate-co-terephthalate) Films for Active Food Packaging. Silicon 11(5):2233-2239. doi:https://doi.org/10.1007/s12633-015-9402-8 Shen W, He P, Xiao C, Chen X (2018) From Antimicrobial Peptides to Antimicrobial Poly(a-amino acid)s. Adv Healthc Mater 7(20):1800354. doi:https://doi.org/10.1002/adhm.201800354 Yu L, Li K, Zhang J, Jin H, Saleem A, Song Q, Jia Q, Li P (2022) Antimicrobial Peptides and Macromolecules for Combating Microbial Infections: From Agents to Interfaces. ACS Applied Bio Materials 5(2):366-393. doi:https://doi.org/10.1021/acsabm.1c01132 Alavi M, Nokhodchi A (2022) Antimicrobial and wound healing activities of electrospun nanofibers based on functionalized carbohydrates and proteins. Cellulose 29(3):1331-1347. doi:10.1007/s10570-021-04412-6 Alavi M (2022) Bacteria and fungi as major bio-sources to fabricate silver nanoparticles with antibacterial activities. Expert Rev Anti-Infect Ther):1-10. doi:10.1080/14787210.2022.2045194 Alavi M, Karimi N (2022) Antibacterial, hemoglobin/albumin-interaction, and molecular docking properties of phytogenic AgNPs functionalized by three antibiotics of penicillin, amoxicillin, and tetracycline. Microbial Pathogenesis 164:105427. doi:https://doi.org/10.1016/j.micpath.2022.105427 Alavi M, Varma RS (2021) Antibacterial and wound healing activities of silver nanoparticles embedded in cellulose compared to other polysaccharides and protein polymers. Cellulose 28(13):8295-8311. doi:10.1007/s10570-021-04067-3 Colino CI, Lanao JM, Gutierrez-Millan C (2021) Recent advances in functionalized nanomaterials for the diagnosis and treatment of bacterial infections. Materials Science and Engineering: C 121:111843. doi:https://doi.org/10.1016/j.msec.2020.111843 Selvarajan V, Obuobi S, Ee PLR (2020) Silica Nanoparticles—A Versatile Tool for the Treatment of Bacterial Infections. Frontiers in Chemistry 8. doi:https://doi.org/10.3389/fchem.2020.00602 Adinarayana TVS, Mishra A, Singhal I, Koti Reddy DVR (2020) Facile green synthesis of silicon nanoparticles from Equisetum arvense for fluorescence based detection of Fe(iii) ions. Nanoscale Advances 2(9):4125-4132. doi:https://doi.org/10.1039/D0NA00307G Fonseca S, Cayer M-P, Ahmmed KMT, Khadem-Mohtaram N, Charette SJ, Brouard D (2022) Characterization of the Antibacterial Activity of an SiO(2) Nanoparticular Coating to Prevent Bacterial Contamination in Blood Products. Antibiotics (Basel) 11(1):107. doi:https://doi.org/10.3390/antibiotics11010107 Tallet L, Gribova V, Ploux L, Vrana NE, Lavalle P (2021) New Smart Antimicrobial Hydrogels, Nanomaterials, and Coatings: Earlier Action, More Specific, Better Dosing? Adv Healthc Mater 10(1):2001199. doi:https://doi.org/10.1002/adhm.202001199 Liu K, Zhang F, Wei Y, Hu Q, Luo Q, Chen C, Wang J, Yang L, Luo R, Wang Y (2021) Dressing Blood-Contacting Materials by a Stable Hydrogel Coating with Embedded Antimicrobial Peptides for Robust Antibacterial and Antithrombus Properties. ACS Applied Materials & Interfaces 13(33):38947-38958. doi:https://doi.org/10.1021/acsami.1c05167 Sheridan M, Winters C, Zamboni F, Collins MN (2022) Biomaterials: Antimicrobial surfaces in biomedical engineering and healthcare. Current Opinion in Biomedical Engineering 22:100373. doi:https://doi.org/10.1016/j.cobme.2022.100373 Vladkova TG, Staneva AD, Gospodinova DN (2020) Surface engineered biomaterials and ureteral stents inhibiting biofilm formation and encrustation. Surface and Coatings Technology 404:126424. doi:https://doi.org/10.1016/j.surfcoat.2020.126424 Moustafa H, Darwish NA, Youssef AM (2022) Rational formulations of sustainable polyurethane/chitin/rosin composites reinforced with ZnO-doped-SiO2 nanoparticles for green packaging applications. Food Chemistry 371:131193. doi:https://doi.org/10.1016/j.foodchem.2021.131193 Sánchez SV, Navarro N, Catalán-Figueroa J, Morales JO (2021) Nanoparticles as Potential Novel Therapies for Urinary Tract Infections. Frontiers in cellular and infection microbiology 11:656496-656496. doi:https://doi.org/10.3389/fcimb.2021.656496 Allafchian A, Hosseini SS (2019) Antibacterial magnetic nanoparticles for therapeutics: a review. IET nanobiotechnology 13(8):786-799. doi:https://doi.org/10.1049/iet-nbt.2019.0146 Jiménez-Jiménez C, Moreno VM, Vallet-Regí M (2022) Bacteria-Assisted Transport of Nanomaterials to Improve Drug Delivery in Cancer Therapy. Nanomaterials 12(2). doi:https://doi.org/10.3390/nano12020288 Silhavy TJ, Kahne D, Walker S (2010) The bacterial cell envelope. Cold Spring Harb Perspect Biol 2(5):a000414-a000414. doi:https://doi.org/10.1101/cshperspect.a000414 Alavi M, Rai M, Martinez F, Kahrizi D, Khan H, Rose Alencar de Menezes I, Douglas Melo Coutinho H, Costa JGM (2022) The efficiency of metal, metal oxide, and metalloid nanoparticles against cancer cells and bacterial pathogens: different mechanisms of action. Cellular, Molecular and Biomedical Reports 2(1):10-21. doi:10.55705/cmbr.2022.147090.1023 Alavi M, Rai M (2021) Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports 1(2):52-59. doi:https://doi.org/10.55705/cmbr.2021.142436.1014 Alavi M, Karimi N (2020) Hemoglobin self-assembly and antibacterial activities of bio-modified Ag-MgO nanocomposites by different concentrations of Artemisia haussknechtii and Protoparmeliopsis muralis extracts. Int J Biol Macromol 152:1174-1185. doi:https://doi.org/10.1016/j.ijbiomac.2019.10.207 Assis M, Simoes LGP, Tremiliosi GC, Coelho D, Minozzi DT, Santos RI, Vilela DCB, Santos JRd, Ribeiro LK, Rosa ILV, Mascaro LH, Andrés J, Longo E (2021) SiO2-Ag Composite as a Highly Virucidal Material: A Roadmap that Rapidly Eliminates SARS-CoV-2. Nanomaterials 11(3):638. doi:https://doi.org/doi:10.3390/nano11030638 Volume 2, Issue 2 Cellular, Molecular and Biomedical Reports Receive Date: 23 January 2022 Revise Date: 29 March 2022 Accept Date: 23 May 2022 First Publish Date: 23 May 2022 Alavi, M., Hamblin, M., Mozafari, M., Rose Alencar de Menezes, I., & Douglas Melo Coutinho, H. (2022). Surface modification of SiO2 nanoparticles for bacterial decontaminations of blood products. Cellular, Molecular and Biomedical Reports, 2(2), 87-97. doi: 10.55705/cmbr.2022.338888.1039 Mehran Alavi; Michael R. Hamblin; M. R. Mozafari; Irwin Rose Alencar de Menezes; Henrique Douglas Melo Coutinho. "Surface modification of SiO2 nanoparticles for bacterial decontaminations of blood products". Cellular, Molecular and Biomedical Reports, 2, 2, 2022, 87-97. doi: 10.55705/cmbr.2022.338888.1039 Alavi, M., Hamblin, M., Mozafari, M., Rose Alencar de Menezes, I., Douglas Melo Coutinho, H. (2022). 'Surface modification of SiO2 nanoparticles for bacterial decontaminations of blood products', Cellular, Molecular and Biomedical Reports, 2(2), pp. 87-97. doi: 10.55705/cmbr.2022.338888.1039 Alavi, M., Hamblin, M., Mozafari, M., Rose Alencar de Menezes, I., Douglas Melo Coutinho, H. Surface modification of SiO2 nanoparticles for bacterial decontaminations of blood products. Cellular, Molecular and Biomedical Reports, 2022; 2(2): 87-97. doi: 10.55705/cmbr.2022.338888.1039 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_150262.html

cc40

1 Department of biological science, Faculty of Science, Kurdistan University, Sanandaj, Kurdistan, Iran 2 Nanobiotechnology Department, Faculty of Innovative Science and Technology, Razi University, K

en

On 15 December, in the BiblioGAM library at the Centro Cultural Gabriela Mistral (GAM Cultural Center), Wikimedia Chile celebrated the prize ceremony of the Wiki Loves Monuments Chile 2012 photo contest, where we awarded prizes to the 10 winning photographs that represented Chile in the international contest, along with the 5 honorable mentions highlighted by the Chilean jury, and a special prize for the participant with the largest amount of images from different monuments. “This initiative is an opportunity that let us rescue our National Heritage and preserve it for future generations so they can get to know it,” said Eduardo Testart, president of Wikimedia Chile. “We are very proud of the outcome and we look forward to continue fostering Wikimedia projects in Chile,” said Mr. Testart. The contest was organized by Wikimedia Chile and sponsored by Fundación Imagen de Chile and Consejo de Monumentos Nacionales (National Monuments Council), which helped with media presence and donated prizes to the contest, which had 4,083 photographs uploaded by 330 participants. After the prize ceremony, the attendees participated of the first Edit-a-thon in Chile guided by volunteers of Wikimedia Chile, who helped participants create stubs and learn how to correctly edit their first words in articles of monuments that were photographed and didn’t have any content on Spanish Wikipedia. After the introduction, the participants, were able to create 3 new articles and enhance and expand some other existing articles. This gave symbolic closure to the contest and allowed Chileans to experience Wikipedia, something that anyone can do, if only they have the will to share knowledge through freely license content. Dennis Tobar Calderón, Wikimedia Chile Translation by Wikimedia Chile Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Chapters, OutreachTagged multilingual post, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/12/21/wikimedia-chile-hosts-first-wikipedia-editathon-in-the-country/

cc40

On 15 December, in the BiblioGAM library at the Centro Cultural Gabriela Mistral (GAM Cultural Center), Wikimedia Chile celebrated the prize ceremony of the Wiki Loves Monuments Chile 2012 photo conte

en

Today Fox News published a story that irresponsibly smeared the Wikimedia projects and a member of the Wikimedia Foundation’s staff, Erik Moeller. The story repeats serious falsehoods and offers information taken grossly out of context, resulting in what amounts to a deliberate misrepresentation of reality. Wikipedia is highly visible, and not uncontroversial. The Wikimedia Foundation wants to provide an environment in which staff and editors can do their work free of harassment and slander. The Wikimedia Foundation is appalled and angry that Erik’s employment with us has resulted in him becoming a target, and we believe that recklessly maligning him is indefensible. Erik is a principled and valued employee: we are proud to support him. On the topic of allegedly illegal materials on Wikipedia and our projects: The Wikimedia Foundation obeys the law. In the weeks since Sanger’s published allegations, the Wikimedia Foundation has not been contacted by the FBI or any other law-enforcement agency with regard to allegedly illegal content on any Wikimedia projects. Our community of volunteer editors takes action to remove illegal material when such material is brought to its attention. The Wikimedia Foundation is proud of the Wikimedia editors who zealously work to keep the projects free of illegal material. If and when we are informed by law enforcement agencies of illegal content that has not already been removed through self-policing, we will take quick action to delete it. (UPDATE) Erik Moeller has posted a detailed response in his personal blog as well. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. […] raccontando l’intera storia, da dove nascevano i pettegolezzi, il supporto dei colleghi e del datore di lavoro, come la sta vivendo lui e cerca di astrarre fino a fare una microriflessione sulla […] “The Wikimedia Foundation obeys the law.” The laws of which country or countries? The laws of the country in which Wikimedia is located, the laws of the country in which the Wikimedia servers are located, or the laws of the country in which the reader is located? How would, for example, this image from Wikimedia Commons be treated under those laws? Fox News diffame gravement Erik Möeller « Darkoneko's Weblog […] Le communiqué de la Wikimedia Foundation. […] Would it be possible to go after Fox News Corp for libel? Sue. Please sue them. As much as I hate libel/slander suits, it’s needed for these guys. Mercy! You were innocent! Knowledge invariably beats ignorant zealotry. Would it be possible to go after Fox News Corp for libel? I cannot believe that it’s taken the best part of a month for this to end up in the mainstream press. It’s clear that the images at categories lolicon and pedophilia were not child porn. Non explicit drawings that border on parody. No one really considers this child porn, Sanger probably doesn’t. What Sanger has done, is to abuse his hand-me-down authority of being Wikipedia co-founder to publicise his entirely child friendly video site. Prior to this, no one had heard of watchknow, now thousands have. He is one professional troll. Accuse di Pedofilia a Wikipedia e Una Lezione di Trasparenza | Infoservi.it […] raccontando l’intera storia, da dove nascevano i pettegolezzi, il supporto dei colleghi e del datore di lavoro, come la sta vivendo lui e cerca di astrarre fino a fare una microriflessione sulla “diffamazione […] I read the story. It’s sensational but not factually incorrect. People who think there should be a lawsuit know nothing about libel law. I am a full supporter of Wikimedia and Wikipedia. That being said, Fox News basically stated that there is a lot of graphic content on wikipedia, which is true. It also stated that Wikimedia is taking action to clean it all up, which I think is appropriate and NECESSARY. Too bad you couldn’t think of it earlier so the media wouldn’t have to publish it… Thanks for folding, Wikimedia. Way to give Fox yet another way to self aggrandise themselves. Fox News 1 :Wikimedia 0 Wiki Censorship at SlideRulesYou.com […] Fox News has been poking its puritanical (and priapic) probe into the internet again. This time, Wikimedia were the focus of their campaign. Wiki is currently executing a large-scale deletion of what the Right-Wing news network refer to as “pornographic imagery”. Jimmy Wales, President of the Wikimedia Foundation, offered assurances that “educational images about sexuality” would remain, but there have been concerns among users that art, literature and images of historical artefacts could also end up being censored. After all, the standards by which Fox judge offensiveness are somewhat different to those of most people. Wiki’s Michael Snow said:… Read more » Turbulencias en Wikipedia tras una campaña que la acusa de "pornografía infantil" | Noticortos.com […] de Wikipedia ya había obligado el pasado 28 de abril a la Fundación Wikimedia a publicar una nota en el que informaba que ninguna policía le había requerido la retirada de ningún tipo de […] I read the article, and it looks more like it’s Mr. Sanger that needs to be sued for libel, especially if he never actually complained to the FBI. It sounds like yet another “man on a mission” seeking to get Wikipedia webfiltered. And probably yet another to have minimal impact; most schools and corporations do not block the site despite so many similar attempts, such as http://wikipediaocd.wordpress.com/. its very crucial to check internet activities of kids, that’s why emonitor has been created. Thanks again for great information. Fox acusa a Wikipedia de albergar pornografía infantil y Wales renuncia | eduangi.com […] ya publicó una explicación hace tiempo diciendo que la policía no le había requerido la retirada de ningún tipo de material y que los […] Fox News diffame gravement Erik Möeller « Darkoneko's Weblog […] Le communiqué de la Wikimedia Foundation. […] Fox News diffame gravement Erik Möeller « Darkoneko's Weblog […] Le communiqué de la Wikimedia Foundation. […] Posted in HighlightsTagged Erik Moeller, Fox, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2010/04/28/wikimedia-foundation-responds-to-fox-news/

cc40

Today Fox News published a story that irresponsibly smeared the Wikimedia projects and a member of the Wikimedia Foundation’s staff, Erik Moeller. The story repeats serious falsehoods and offers infor

en

To ensure that Wikipedia users can share in the world’s knowledge more securely, the Wikimedia Foundation is implementing HTTPS, to encrypt all traffic on Wikimedia sites. Image by Hugh D’Andrade, from Electronic Frontier Foundation, freely licensed under CC BY-SA 3.0. To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years, Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere, and when directed to our sites from major search engines. Additionally, all logged in users have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be complicated. For us, this process began years ago and involved teams from across the Wikimedia Foundation. Our engineering team has been driving this transition, working hard to improve our sites’ HTTPS performance, prepare our infrastructure to handle the transition, and ultimately manage the implementation. Our first steps involved improving our infrastructure and code base so we could support HTTPS. We also significantly expanded and updated our server hardware. Since we don’t employ third party content delivery systems, we had to manage this process for our entire infrastructure stack in-house. HTTPS may also have performance implications for users, particularly our many users accessing Wikimedia sites from countries or networks with poor technical infrastructure. We’ve been carefully calibrating our HTTPS configuration to minimize negative impacts related to latency, page load times, and user experience. This was an iterative process that relied on industry standards, a large amount of testing, and our own experience running the Wikimedia sites. Throughout this process, we have carefully considered how HTTPS affects all of our users. People around the world access Wikimedia sites from a diversity of devices, with varying levels of connectivity and freedom of information. Although we have optimized the experience as much as possible with this challenge in mind, this change could affect access for some Wikimedia traffic in certain parts of the world. In the last year leading up to this roll-out, we’ve ramped up our testing and optimization efforts to make sure our sites and infrastructure can support this migration. Our focus is now on completing the implementation of HTTPS and HSTS for all Wikimedia sites. We look forward to sharing a more detailed account of this unique engineering accomplishment once we’re through the full transition. Today, we are happy to start the final steps of this transition, and we expect completion within a couple of weeks. Yana Welinder, Senior Legal Counsel, Wikimedia Foundation Victoria Baranetsky, Legal Counsel, Wikimedia Foundation Brandon Black, Operations Engineer, Wikimedia Foundation Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. @nemobis Thanks for pointing out this meta page. We will try to provide more info there eventually, but have our hands full with the rollout. In the meantime, if you would like to use the information in this post to respond to questions, that would be incredibly helpful. Glad to see Wiki turns on HTTPS by default. However, can I turn off HTTPS? Since the GFW in China blocks Wiki in HTTPS sometimes, and it takes far more time to load the site. Yana, I’m sorry but I’m unable to extract any information from this post. However, I linked it from there and updated a local it.wiki discussion with clarifications provided by ops. I’m glad to finally see this. Thanks. PLEASE leave users the possibility to opt out of HTTPS; why has it now been taken away? I don’t care about intelligence agencies spying on my Wikipedia contributions, if they ever do; I just want the best possible performance AND I’m happy to save the Wikimedia infrastructure valuable processing time, by avoiding something for me completely pointless, i.e. encryption. Shouldn’t Wikipedia be all about freedom? Then turn on HTTPS by default if you want, and then leave the user free to decide whether to turn it off or not. This is a major step forward. Makes the web a little bit safer. “We’ve been carefully calibrating our HTTPS configuration to minimize negative impacts related to latency, page load times, and user experience.” Can you please expand on this in more detail? More specifically how you decided to make tradeoffs of speed and performance and cipher suites used? Old OPERA (12.16) stop working This is great news! Everything should be encrypted by default, so that it does not look suspicious when one really needs encryption (like when searching for an illness or for chapter 11 information). The browser I use most (99 %) is Arachne running in DOS. Arachne does not do HTTPS. Is there any way I can access Wikipedia WITHOUT HTTPS ?? To elaborate on the post by Ron Clarke: Ron & I are active developers of DOS Arachne available at… The page for-which on wikipedia is no longer accessible to DOS Arachne due to https being required. Before this change to https, DOS Arachne was indeed able to access that page via… However, attempting to access via http now auto-rediects to https Please, re-think your position of requiring https access. “free” information is not so “free” after-all if accessing said information has the string attached of requiring a protocol that is not available in _all_ web browsers. Will this affect the status of the ongoing NSA lawsuit by Wikipedia? Is there any need for the lawsuit, if editors and readers are all accessing Wikipedia via HTTPS? It would be a great idea if it worked, sadly Wikipedia seems to have died for me in FF3. I’m getting an error message saying “The connection was interrupted”. Works fine in IE. @Arachne_running_in_DOS, you already have a problem today with other SSL/TLS sites like e-banking etc. Why now adding a SSL/TLS support to that browser instead, is this really something very hard to do, or just not a priority? @All_users_who_do_not_respect_privacy, actually I think you are honest, everyone want privacy, but some do not understand it. Everyone that do not need privacy, please create web page, publish all your passwords and also please upload all of your personal information – your telephone SMS, photos, all e-mail conversations, etc. You said you don’t care about privacy, so this should not be a problem. Let’s… Read more » Please try to be a little less gratuitously antagonistic to prior comments, okay? The content about government pedophiles is extreme in this context @Glenn McCorkle and Ron Clarke: “Ron & I are active developers of DOS Arachne” This ship has sailed. Every single .gov domain will be HTTPS-only by next year. Many already are. For active developers of web browsers which don’t support HTTPS, implementing it should have been the number one priority for the last few years, because other browsers – even other command-line browsers that can run on legacy hardware – support it just fine. Like an FTP program without FTPS or SFTP, or an email program without STARTTLS, you’ll lose market share and relevance. Oh, and IPv6 URLs are a… Read more » > Why now adding a SSL/TLS support to that browser instead, is this really something very hard to do, or just not a priority? Adding SSL to Arachne would be wonderful, and we wish we could. But…..we have a lack of suitably skilled coders with an interest in DOS browsers, and Arachne in particular. Now all IE6 users will be cut off from using Wikipedia: Wouldn’t it be possible to add some user-agent sniffing so that these browsers could still access Wikipedia? They are usually used by poorer people. “Wouldn’t it be possible to add some user-agent sniffing” NO! No it would not. Because then a man in the middle can replace anyone’s user agent details with another user agent, and bingo, nobody any longer has any encryption at all. Invisibly and undetectably. Why would wikimedia hand attackers such a gift on a plate? Upgrading from IE6 to a secure browser is entirely possible for every single user on the planet. There is no sane reason for anyone, anywhere, to use an insecure browser. The very worst smartphone and smartwatch in the world can browse securely. Even Lynx can… Read more » “Because then a man in the middle can replace anyone’s user agent details with another user agent, and bingo, nobody any longer has any encryption at all. Invisibly and undetectably.” Such an attack is already possible with tools such as sslstrip. Therefore user-agent sniffing doesn’t decrease security for other users out there: it will make life easier neither for criminals nor for companies that want to monitor traffic. Wikipedia is going to use HSTS and add itself to HSTS preload lists in browsers: that will block downgrade to HTTP for new browsers. “Upgrading from IE6 to a secure browser is… Read more » I *really* want the ability to connect without HTTPS. I want to avoid the overhead required by HTTPS please. > There are two reasons someone might ask for any form of downgrade or opt-out to be permitted: Make that three reasons. I run in DOS, and I like to keep the functionality of Arachne. Yes, I also run Links, Elinks and Lynx in DOS, but Arachne is more versatile than all of them – except for a lack of SSL. Very good step indeed, in fact, in cyber world https is more important because of security issues. Know a days users check website also they check that website https not. If they found https is not they click on cut button and skip from website… Great move team. Web is becoming a tool for governments and enforcement agencies to surveillance on citizens. SSL helps website visitors to send and receive encrypted data. I also want to move my website http://careervendor.com from HTTP to HTTPS. I am fearing about losing traffic, backlink and ranking. Can anyone please suggest a way for proper migration. Very good step indeed, in fact, in cyber world https is more important because of security issues. Know a days users check website also they check that website https not. If they found https is not they click on cut button and skip from website… All well and good to force everyone to use https. Would it be too much to ask to employ a real SSL certificate that doesn’t rely on a wildcard. At present, we can’t even use Wikipedia anymore because we can’t trust the website. Uggghhh… All the points are explained very clearly, Great source of information. Thanks for en-lighting us with your knowledge, it is helpful for many of us. Great step for sure, actually, in digital world https is more imperative Is there *any* way to use Wikipedia *without* https? I have an old device which is not capable of using https. And please don’t tell me to buy new hardware or software. So please offer a possibility to read Wikipedia *without* forced https!!!! BTW: I cannot follow the reasons to *enforce* https: Concerning privacy: when you browse Wikipedia the URLs contain the topic you are reading (e.g.: https://en.wikipedia.org/wiki/CMAC) thus any sniffer can track what you are currently reading. Only the *contents* is encrypted, but the contents is visible by anybody anyway (in contrast to the content of my bank account).… Read more » “Concerning privacy: when you browse Wikipedia the URLs contain the topic you are reading thus any sniffer can track what you are currently reading. Only the *contents* is encrypted, but the contents is visible by anybody anyway (in contrast to the content of my bank account).” False. The root domain (wikipedia.org) can be inferred from the IP address of the server during the TCP/IP request but the complete URL and exact page you’re reading cannot. Read the article on https. I also want there is a way to use wikipedia with plain HTTP if necessary. Currently there is a stupid debate between our government and local wiki representatives (I could not decide which of them is more stupid, I’m sorry) about restricting access to certain pages (about drugs). Providers can do this for single page if it is accessed with HTTP, but they need to deny access to whole website if it is accessed via HTTPS. So it would be good if we have some fallback, perhaps with banner explaining “all horrible consequences” of reading wiki in plain HTTP. In… Read more » Our most popular posts of 2015: black hats, artificial intelligence, John Oliver, and a photobomb – Wikimedia blog […] in 2015, we began encrypting all of our traffic with HTTPS to ensure that users and readers alike can use our services “without sacrificing privacy or […] Google steals 550+ million Wikipedia clicks in 6 months, traffic drop confirmed by Wiki's Jimmy Wales […] HTTPS fluctuations? Wikipedia moved to HTTPS before 2 months ago, but the serious drop in the organic desktop traffic began actually at […] Part 3 - The Evolving Data Story Around Wikipedia - Similarweb Blog […] has been kind enough to share their thoughts that their shift to HTTPS might have resulted in drops in traffic overall and from search engines :”This switch to […] Announcing a new informational resource on Wikimedia Foundation v. NSA and government surveillance – Wikimedia blog […] dates as these become available; helpful English Wikipedia articles about government surveillance; information about HTTPS access to the projects and online security; and social media action items for anybody […] HTTPS and Wikipedia – Crossref Blog […] June 2015 the Wikimedia foundation made the announcement that they were finalising the switch, and that within a few weeks all traffic would be […] 为什么迁移到 HTTPS 有利于网站统计 – 博客歪歪 […] 实际上已于 2015 年六月 从 HTTP 迁移到了 HTTPS.在那时,几乎所有从 wikipedia.org 到 HTTP […] 为什么迁移到 HTTPS 有利于网站统计 | 神刀安全网 […] 实际上已于 2015 年六月 从 HTTP 迁移到了 HTTPS .在那时,几乎所有从 wikipedia.org 到 HTTP […] The Lopsided Geography of Wikipedia -RocketNews […] is presently blocking Wikipedia in its entirety, in part because of the encyclopedia’s recent move to an encrypted “HTTPS” protocol that makes it harder for the government to determine […] VIVO TRENDS | A Wikipedia perdeu meio bilhão de visitas nos últimos meses […] no protocolo de navegação da Wikipédia também ajuda na queda de acessos. Em junho, foi anunciado que os sites da Wikimedia seriam criptografados com o protocolo HTTPS, que garante a segurança e […] J. Wales : « Tout ce qui resemble à un péage sur les autoroutes de l’information suscite notre inquiétude » | Le Bon Article […] fois, elle a été documentée. C’est pour éviter cela que nous avons pris la décision d’utiliser par défaut le protocole « HTTPS », qui rend la surveillance de votre navigation beaucoup plus difficile, sur toutes les […] Le cofondateur de Wikipédia inquiet de « tout ce qui resemble à un péage sur les autoroutes de l’information » | Le Bon Article […] fois, elle a été documentée. C’est pour éviter cela que nous avons pris la décision d’utiliser par défaut le protocole « HTTPS », qui rend la surveillance de votre navigation beaucoup plus difficile, sur toutes les […] Growing the Wikimedia blog – Wikimedia Blog […] Securing access to Wikimedia sites with HTTPS – 14k views […] Google usually has an alternate (cache) for each wiki link. I just use these cache pages. Let's Encrypt SSL Certificates and Nginx for HTTPS […] the use of HTTPS as a rankings signal. Over the past few years, organizations like Facebook, Wikipedia, and the Federal CIO Council have shown that properly switching to HTTPS is no longer the […] Appeal filed in Wikimedia v. NSA – Wikimedia Blog […] to protect the free expression and privacy rights of all Wikipedia users. We have since enabled default HTTPS access to protect Wikipedia users from government surveillance, and we remain committed to our stringent […] Posted in Foundation, From the archives, Legal, Platform engineering, Technology, WikipediaTagged encryption, https, Security, surveillance, technology, web, Wikimedia, Wikimedia Blog (EN Archive), Wikimedia Foundation, Wikipedia Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/

cc40

To ensure that Wikipedia users can share in the world’s knowledge more securely, the Wikimedia Foundation is implementing HTTPS, to encrypt all traffic on Wikimedia sites. Image by Hugh D’Andrade, fro

en

Ministry of Education, NCEMA announce updates to 2021-2022 National Protocol for Educational Establishments The Ministry of Education and the National Emergency Crisis and Disasters Management Authority (NCEMA), in coordination with all partners, have announced new updates to the National Protocol for Educational Establishments for the Academic Year 2021-2022, which will come into force on Thursday, 21st April, 2022. This step aligns with the UAE's strategy for ensuring community health and safety and facilitating the safe return of students to educational establishments, as well as supports national efforts to achieve sustainable recovery and the return to normalcy. The new update to the protocol allows the resumption of all activities and events in educational establishments, and permits parents to attend all student events and activities, provided they comply with preventive measures, including wearing facemasks in closed spaces and the Green Pass Protocol on Al Hosn app. Moreover, school trips organised by educational facilities will be fully restored, with all those involved required to wear facemasks while on school buses. Both vaccinated and unvaccinated staff and students will be allowed to go on such trips, provided they have green status on their Al Hosn app. The updated protocol also requires all university students wishing to enter dorms to conduct a PCR test once every month, or to follow the Green Pass Protocol for vaccinated and unvaccinated students. Under the new updates, following the Green Pass Protocol will be mandatory for all visitors of educational establishments, along with students aged 16 and above, educational staff and personnel. As for students aged under 16, they have to conduct a PCR test on a monthly basis. The new updates also outlined the procedures for the gradual closure of educational institutions in the case of confirmed COVID-19 infections, which will follow the guidelines issued by local emergency and crises committees and teams in each emirate. Such procedures include closing the educational establishment for three days, if the infection rate exceeds 15 percent of the total attendance. As per the updated protocol, those in who come into contact with COVID-19 positive cases are no longer required to quarantine, while following the guidelines issued by the health authorities as per the National Protocol for COVID-19 Close-Contact. Furthermore, those infected and those with respiratory diseases may opt for the option of distance education. The Ministry of Education and NCEMA noted that all the updates are applicable nationwide, while implementation at the local level will be carried out in coordination with local emergency, crises and disasters committees in each emirate. Meanwhile, the Ministry and NCEMA stressed that all measures announced in the national protocol are subject to change based on the global and local health situation. The Ministry and NCEMA called on all members of the public to cooperate and adhere to all preventive measures to contain the COVID-19 pandemic and sustain the UAE's positive achievements in this regard.

https://covid19.ncema.gov.ae/en/News/Details/2363

cc40

Ministry of Education, NCEMA announce updates to 2021-2022 National Protocol for Educational Establishments The Ministry of Education and the National Emergency Crisis and Disasters Management Authori

en

1 Department of microbiology and microbial biotechnology, faculty of life sciences and biotechnology, Shahid Beheshti University, Tehran, Iran. 2 Pediatric Infections Research Center, Research Institute for Children’s Health, Shahid Beheshti University of Medical Sciences, Tehran, Iran. 3 Department of Biotechnology, Faculty of Advanced Sciences and Technologies, University of Isfahan, Isfahan, Iran The main purpose of microbial typing is to evaluate the relationships between microbial isolates. Microbial typing can use for identifying the source of infection by detecting a clonal link between the strains. Moreover, it can analyze outbreaks, antimicrobial-resistant strains, and evaluate the effectiveness of control measures so, the efficiency of monitoring systems would increase. HAIs can affect hospitalized patients in all age ranges with any clinical situation, and lead to death. Molecular epidemiology is useful to determine genetic relatedness between isolated pathogens from patients, and design proper prevention plans to prevent infection through the hospital and community. Nowadays, typing methods for a wide range of bacterial strains are known as essential epidemiological tools to prevent and control infections in hospitals and communities. Although basic typing methods were more focused on phenotypic techniques like antibiogram and serotyping, new methods are based on molecular techniques including PCR-based methods and sequencing-based methods. Due to the high frequency of methods, choosing the right one for research applications seems difficult and requires basic knowledge about all of them. In this review, we aim to introduce the most useful and practical molecular typing techniques. Also, their utilization, advantages, and disadvantages were compared. Selected authors of this article by journal CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Ruppitsch W (2016) Molecular typing of bacteria for epidemiological surveillance and outbreak investigation/Molekulare Typisierung von Bakterien für die epidemiologische Überwachung und Ausbruchsabklärung. Die Bodenkultur: Journal of Land Management, Food and Environment 67(4):199-224. doi: https://doi.org/10.1515/boku-2016-0017 Foxman B, Riley L (2001) Molecular epidemiology: focus on infection. American journal of epidemiology 153(12):1135-1141. doi:https://doi.org/10.1093/aje/153.12.1135 Rodríguez-Morales AJ, Balbin-Ramon GJ, Rabaan AA, Sah R, Dhama K, Paniz-Mondolfi A, Pagliano P, Esposito S (2020) Genomic Epidemiology and its importance in the study of the COVID-19 pandemic. genomics 1:3 Jensen AK, Björkman JT, Ethelberg S, Kiil K, Kemp M, Nielsen EM (2016) Molecular typing and epidemiology of human listeriosis cases, Denmark, 2002–2012. Emerging infectious diseases 22(4):625. doi:https://doi.org/10.3201/eid2204.150998 Xiao L, Ryan UM (2007) Molecular epidemiology. In: Cryptosporidium and cryptosporidiosis. CRC press, pp 119-172 Monegro AF, Muppidi V, Regunath H (2020) Hospital acquired infections. Statpearls [Internet]) Alavi M, Rai M (2021) Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports:52-59 Azimi L, Alaghehbandan R, Asadian M, Alinejad F, Lari AR (2019) Multi-drug resistant Pseudomonas aeruginosa and Klebsiella pneumoniae circulation in a burn hospital, Tehran, Iran. GMS hygiene and infection control 14. doi: https://doi.org/10.3205/dgkh000317 Soleimani N (2018) A Review of Designing New Vaccines to Prevent Hospital-Acquired Antibiotic-Resistant Infections. International Electronic Journal of Medicine 7(2):21-29. doi:https://doi.org/10.31661/iejm861 Azimi L, Talebi M, Khodaei F, Najafi M, Lari AR (2016) Comparison of multiple-locus variable-number tandem-repeat analysis with pulsed-field gel electrophoresis typing of carbapenemases producing Acinetobacter baumannii isolated from burn patients. Burns 42(2):441-445. doi:https://doi.org/10.1016/j.burns.2015.08.024 Crabb HK, Allen JL, Devlin JM, Firestone SM, Wilks CR, Gilkerson JR (2018) Salmonella spp. transmission in a vertically integrated poultry operation: Clustering and diversity analysis using phenotyping (serotyping, phage typing) and genotyping (MLVA). PLoS One 13(7):e0201031. doi:https://doi.org/10.1371/journal.pone.0201031 Ranjbar R, Karami A, Farshad S, Giammanco GM, Mammina C (2014) Typing methods used in the molecular epidemiology of microbial pathogens: a how-to guide. New Microbiologica 37(1):1-15 Magalhães B, Valot B, Abdelbary MM, Prod'hom G, Greub G, Senn L, Blanc DS (2020) Combining standard molecular typing and whole genome sequencing to investigate Pseudomonas aeruginosa epidemiology in intensive care units. Frontiers in public health 8:3. doi:https://doi.org/10.1186/1471-2180-6-9 Abbas-Al-Khafaji ZK, Aubais-aljelehawy Qh (2021) Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital. Cellular, Molecular and Biomedical Reports:60-68 Christensen H, Bossé J, Angen Ø, Nørskov-Lauritsen N, Bisgaard M (2020) Immunological and molecular techniques used for determination of serotypes in Pasteurellaceae. Methods in Microbiology 47:117-149. doi:https://doi.org/10.1016/bs.mim.2020.01.002 Armin S, Fallah F, Karimi A, Rashidan M, Shirdust M, Azimi L (2017) Genotyping, antimicrobial resistance and virulence factor gene profiles of vancomycin resistance Enterococcus faecalis isolated from blood culture. Microbial pathogenesis 109:300-304. doi:https://doi.org/10.1016/j.micpath.2017.05.039 Kaufmann M, Pitcher D, Pitt T (2018) Ribotyping of bacterial genomes. In: Methods in Practical Laboratory Bacteriology. CRC Press, pp 123-138 Van Belkum A, Welker M, Pincus D, Charrier J-P, Girard V (2017) Matrix-assisted laser desorption ionization time-of-flight mass spectrometry in clinical microbiology: what are the current issues? Annals of laboratory medicine 37(6):475-483. doi:https://doi.org/10.3343/alm.2017.37.6.475 Besser J, Carleton HA, Gerner-Smidt P, Lindsey RL, Trees E (2018) Next-generation sequencing technologies and their application to the study and control of bacterial infections. Clinical microbiology and infection 24(4):335-341. doi:https://doi.org/10.1016/j.cmi.2017.10.013 Lagha R, Abdallah FB, ALKhammash AA, Amor N, Hassan MM, Mabrouk I, Alhomrani M, Gaber A (2021) Molecular characterization of multidrug resistant Klebsiella pneumoniae clinical isolates recovered from King Abdulaziz Specialist Hospital at Taif City, Saudi Arabia. Journal of Infection and Public Health 14(1):143-151. doi:https://doi.org/10.1016/j.jiph.2020.12.001 Singh A, Goering RV, Simjee S, Foley SL, Zervos MJ (2006) Application of molecular techniques to the study of hospital infection. Clinical microbiology reviews 19(3):512-530. doi:https://doi.org/10.1128/CMR.00025-05 Shibata N, Doi Y, Yamane K, Yagi T, Kurokawa H, Shibayama K, Kato H, Kai K, Arakawa Y (2003) PCR typing of genetic determinants for metallo-B-lactamases and integrases carried by gram-negative bacteria isolated in Japan, with focus on the class 3 integron. Journal of Clinical Microbiology 41(12):5407-5413. doi:https://doi.org/10.1128/JCM.41.12.5407-5413 Van Belkum A (1994) DNA fingerprinting of medically important microorganisms by use of PCR. Clinical Microbiology Reviews 7(2):174-184. doi:https://doi.org/10.1128/CMR.7.2.174 Van Belkum A, Tassios P, Dijkshoorn L, Haeggman S, Cookson B, Fry N, Fussing V, Green J, Feil E, Gerner‐Smidt P (2007) Guidelines for the validation and application of typing methods for use in bacterial epidemiology. Clinical Microbiology and Infection 13:1-46. doi:https://doi.org/10.1111/j.1469-0691.2007.01786.x Asadian M, Azimi L, Alinejad F, Ostadi Y, Lari AR (2019) Molecular characterization of Acinetobacter baumannii isolated from ventilator-associated pneumonia and burn wound colonization by random amplified polymorphic DNA polymerase chain reaction and the relationship between antibiotic susceptibility and biofilm production. Advanced biomedical research 8. doi:https://doi.org/10.4103/abr.abr_256_18 Bilung LM, Pui CF, Su’ut L, Apun K (2018) Evaluation of BOX-PCR and ERIC-PCR as molecular typing tools for pathogenic Leptospira. Disease markers 2018. doi:https://doi.org/10.1155/2018/1351634 Le Flèche P, Jacques I, Grayon M, Al Dahouk S, Bouchon P, Denoeud F, Nöckler K, Neubauer H, Guilloteau LA, Vergnaud G (2006) Evaluation and selection of tandem repeat loci for a Brucella MLVA typing assay. BMC microbiology 6(1):1-14. doi:https://doi.org/10.1186/1471-2180-6-9 Ardakani MA, Ranjbar R (2016) Molecular typing of uropathogenic E. coli strains by the ERIC-PCR method. Electronic physician 8(4):2291. doi:https://doi.org/10.19082/2291 Schmitt S, Stephan R, Huebschke E, Schaefle D, Merz A, Johler S (2020) DNA microarray-based characterization and antimicrobial resistance phenotypes of clinical MRSA strains from animal hosts. Journal of Veterinary Science 21(4). doi:https://doi.org/10.4142/jvs.2020.21.e54 Gaiarsa S, Batisti Biffignandi G, Esposito EP, Castelli M, Jolley KA, Brisse S, Sassera D, Zarrilli R (2019) Comparative analysis of the two Acinetobacter baumannii multilocus sequence typing (MLST) schemes. Frontiers in microbiology 10:930. doi:https://doi.org/10.3389/fmicb.2019.00930 Scholz CF, Jensen A (2017) Development of a Single Locus Sequence Typing (SLST) scheme for typing bacterial species directly from complex communities. In: Bacterial Pathogenesis. Springer, pp 97-107. doi:https://doi.org/10.1007/978-1-4939-6673-8_7 Kwok P-Y (2001) Methods for genotyping single nucleotide polymorphisms. Annual review of genomics and human genetics 2(1):235-258. doi:https://doi.org/10.1146/annurev.genom.2.1.235 Hallin M, Deplano A, Struelens MJ (2012) Molecular typing of bacterial pathogens: a tool for the epidemiological study and control of infectious diseases. In: New frontiers of molecular epidemiology of infectious diseases. Springer, pp 9-25. doi:https://doi.org/10.1007/978-94-007-2114-2_2 Tümmler B (2020) Molecular epidemiology in current times. Environmental Microbiology 22(12):4909-4918. doi:https://doi.org/10.1111/1462-2920.15238 Prado-Vivar MB, Ortiz L, Reyes J, Villacis E, Fornasini M, Baldeon ME, Cardenas PA (2019) Molecular typing of a large nosocomial outbreak of KPC-producing bacteria in the biggest tertiary-care hospital of Quito, Ecuador. Journal of global antimicrobial resistance 19:328-332. doi:https://doi.org/10.1016/j.jgar.2019.05.014 Sharma-Kuinkel BK, Rude TH, Fowler VG (2014) Pulse field gel electrophoresis. In: The Genetic Manipulation of Staphylococci. Springer, pp 117-130 García H, Cervantes-Luna B, González-Cabello H, Miranda-Novales G (2018) Risk factors for nosocomial infections after cardiac surgery in newborns with congenital heart disease. Pediatrics & Neonatology 59(4):404-409. doi:https://doi.org/10.1186/s12879-020-4769-6 Corcione S, Pensa A, Castiglione A, Lupia T, Bortolaso B, Romeo MR, Stella M, Rosa FGD (2021) Epidemiology, prevalence and risk factors for infections in burn patients: Results from a regional burn centre’s analysis. Journal of Chemotherapy 33(1):62-66. doi:https://doi.org/10.1080/1120009X.2020.1780776 Sikora A, Zahra F (2021) Nosocomial infections. StatPearls [Internet]) Baran I, Aksu N (2016) Phenotypic and genotypic characteristics of carbapenem-resistant Enterobacteriaceae in a tertiary-level reference hospital in Turkey. Ann Clin Microbiol Antimicrob 15:20. doi:https://doi.org/10.1186/s12941-016-0136-2 Volume 1, Issue 2 - Serial Number 2 Cellular, Molecular and Biomedical Reports Receive Date: 18 June 2021 Revise Date: 06 August 2021 Accept Date: 18 November 2021 First Publish Date: 18 November 2021 Almasian-Tehrani, N., Alebouyeh, M., Armin, S., Soleimani, N., Azimi, L., & Shaker-Darabad, R. (2021). Overview of typing techniques as molecular epidemiology tools for bacterial characterization. Cellular, Molecular and Biomedical Reports, 1(2), 69-77. doi: 10.55705/cmbr.2021.143413.1016 Nasim Almasian-Tehrani; Masoud Alebouyeh; Shahnaz Armin; Neda Soleimani; Leila Azimi; Roozbeh Shaker-Darabad. "Overview of typing techniques as molecular epidemiology tools for bacterial characterization". Cellular, Molecular and Biomedical Reports, 1, 2, 2021, 69-77. doi: 10.55705/cmbr.2021.143413.1016 Almasian-Tehrani, N., Alebouyeh, M., Armin, S., Soleimani, N., Azimi, L., Shaker-Darabad, R. (2021). 'Overview of typing techniques as molecular epidemiology tools for bacterial characterization', Cellular, Molecular and Biomedical Reports, 1(2), pp. 69-77. doi: 10.55705/cmbr.2021.143413.1016 Almasian-Tehrani, N., Alebouyeh, M., Armin, S., Soleimani, N., Azimi, L., Shaker-Darabad, R. Overview of typing techniques as molecular epidemiology tools for bacterial characterization. Cellular, Molecular and Biomedical Reports, 2021; 1(2): 69-77. doi: 10.55705/cmbr.2021.143413.1016 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_143413.html

cc40

1 Department of microbiology and microbial biotechnology, faculty of life sciences and biotechnology, Shahid Beheshti University, Tehran, Iran. 2 Pediatric Infections Research Center, Research Institu

en

A science workshop in Montreal held during the Francophone Contribution Month, a collaboration between Wikimedia Canada, Acfas, and BAnQ. Photo by Benoit Rochon, freely licensed under CC BY-SA 4.0. During March, across all French-speaking territories, Wikimedians are organizing dozens of events, training workshops, conferences, and photo walks to gather local contributors and promote the Wikimedia projects. By definition, editing Wikipedia and its sister projects is a solitary sport; we contribute on our computers, our tablets, and our phones. We are aiming to change this, to help local contributors meet and invite the public to join local Wikimedia groups. Together, we hope that they will share their knowledge and learn how to contributing to Wikimedia projects, in harmony… and face to face! Since early January 2016, the French-speaking Wikimedians have been preparing workshops, making lists of articles to create or rework, and looking for places for people to gather: libraries, media libraries, archive centers, universities, studios or even bistros. They have been preparing for a long time because the third annual International Francophone Contribution Month will match the International Day of Francophonie on March 20, the week of the French language from 20 to 28 March, and the month of Francophonie des Amériques. Whether in Algeria, Belgium, Cameroon, Canada, France, Guadeloupe, Madagascar, Niger, Senegal, Switzerland, Tunisia, the themes are as varied as the backgrounds of the participants: science, feminism, literature, language, geography, or history. Most residents of Francophone countries speak one or more other languages; French is their second language or the administrative language. To accommodate, workshop participants will also learn to contribute in the language versions of Wikimedia projects in English, Arabic, Creole, Hausa, Malagasy, Wolof, and others. For instance, the Wikipedia in Guadeloupean Creole version has been in the Wikimedia incubator since 2009. One of the goals of Guadeloupeans and its diaspora is to translate the most important system messages of MediaWiki, the software behind Wikipedia, and also create a significant number of articles in Guadeloupean Creole before getting this language version out of Wikimedia incubator. Thus, Guadeloupeans will eventually enrich Wikipedia in their language! We can not let others write content about us all the time; it will not be right (…) There are discussions on the Burkina Faso’s WikiProject, in the absence of Burkinabé. (Idriss Tinto, Open Knowledge Foundation, Burkina Faso) The international month of the Francophone contribution will not just enrich French-language Wikimedia projects in French, but will also train new contributors! See our workshops map and the contribution month’s official page. Benoit Rochon, vice president of Wikimédia Canada and coordinator of Wikifranca. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Chapters, Community, OutreachTagged Collaboration, francophone, francophonie, French language, multilingual post, Wikimedia Blog (EN Archive), Wikipedia Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2016/03/07/francophone-contribution-month/

cc40

A science workshop in Montreal held during the Francophone Contribution Month, a collaboration between Wikimedia Canada, Acfas, and BAnQ. Photo by Benoit Rochon, freely licensed under CC BY-SA 4.0. Du

en

Subhashish Panigrahi is a volunteer contributor for Wikipedia and has worked in the past as a community and program support consultant for Wikimedia Foundation. Internet users from around the world often turn to Wikipedia to answer questions of all kinds. The information offered there includes medical subjects, especially important in parts of the world where access to medical professionals may be limited. However, much of this information has not yet been vetted by the community as “good article” or “featured article,” and is available only in the most oft-spoken languages. A group of experienced Wikipedia editors and medical professionals are trying to change that with the Medicine Translation Project, an effort to improve health care-related topics in English Wikipedia and translate them into other languages, including Hindi, Chinese, Persian, Tagalog, Indonesian and Macedonian. Recently, the Wikimedia Foundation’s Individual Engagement Grant (IEG), a microgrant supporting work on Wikipedia-related activities, granted 10,000 US dollars to the Medicine Translation Project Community Organizing project, which aims to enhance communication and coordination among the team. Medical student and Wikipedian User:CFCF along with two advisors, Dr. James Heilman (User:Doc James) and Jake Orlowitz (User:Ocaasi) lead the group. We spoke to founder CFCF over email. Rising Voices (RV): How did the project get started? What inspired it and how did you identify the needs it would fulfill? Medical translation by CFCF (CC BY-SA 3.0) CFCF: […] The project itself started off in 2011 when Dr. James Heilman and a number of translators from Translators Without Borders: Enrique Cavalitto and Ildiko Santana teamed up in an effort to translate medical articles. Since then, the project has exploded into a larger translation forum with hundreds of translators translating articles into almost a hundred different languages.  […] For Wikimedia projects with a large pool of editors, we have been taking help from editors to assess what is needed, and what should be translated. On smaller projects we have simply set the goal to get anything on World Health Organization (WHO)’s list of essential medicines, as well as anything about neglected tropical diseases, also from a list by the WHO. As for these articles the project is still in an early phase, but we want to cover basically anything that might be relevant to readers, from cancer to emergency medicine. CFCF: […] The problem is that there are so many layers of complications in the translation process. After an article has been written and been subject to review to ensure its quality, the article needs to be prepared and proofed for translation, after which translators need to be found.  […] Many of our translators are medical professionals and have in-depth knowledge in their native languages. On the top of it, they dedicate plenty of time on the content creation and translation. This helps to get good quality translations. What this also means is they they seldom have any knowledge of Wiki markup or Wikipedia. Someone else who knows the language in question has to go through links, templates etc. and fix them, proofread the translated content so it is up to scratch and readable. RV: How is the process of translation going? CFCF: […] The problem is that there are so many layers of complications in the translation process. After an article has been written and been subject to review to ensure its quality, the article needs to be prepared and proofed for translation, after which translators need to be found.  […] Many of our translators are medical professionals and have in-depth knowledge in their native languages. On the top of it, they dedicate plenty of time on the content creation and translation. This helps to get good quality translations. What this also means is they they seldom have any knowledge of Wiki markup or Wikipedia. Someone else who knows the language in question has to go through links, templates etc. and fix them, proofread the translated content so it is up to scratch and readable. RV: How do you address this? A flow diagram illustrating the article flow process of the WP:MED journal collaboration and translation project. Flow of Article Creation by James Heilman, MD (CC BY-SA 3.0) CFCF: To fix all this, it is best to have a local Wikipedian who can integrate the text. Most of the work has already been done. But, getting these things right is very crucial, especially on Wikipedias with vast content, where there already is a lot of content to link in. I think the resistance we met early in the project’s life was not against translation of content. But, because we did not spend enough time getting the translated articles up to shape before sending them live on the target Wikipedia. What we saw on the Polish Wikipedia was that much of the issues were down to how they used different templates, and after I commissioned a bot to fix this, the articles started going live very quickly. After this, more and more editors became interested in helping out […] RV: Are you in conversation with the Wikipedia Zero team — a mobile data project focused on Wikipedia access in the developing world — about popularising this with their partners in the developing nations? CFCF: Currently we are not in touch with the Wikipedia Zero team specifically, even though our works target the same communities. The difference between us and them is that we target developed countries as well as countries where there barely is any mobile connectivity at all, such as Burma where I do not know if we will be seeing Wikipedia Zero in the foreseeable future […] RV: What are your plans to engage with the larger Wikimedia communities that are multilingual and totally diverse? CFCF: We aim to get high quality content in as many languages as we can. It is difficult to translate such deeply technical content, so we are really looking for professional translators, or individuals with some form of medical background so that information loss and corruption of content in translation is minimal.We recruit translators either off-wiki, or on the medical WikiProjects. We are still looking for translators who feel they are comfortable with such topics, and we especially need them in smaller languages. We are also searching them at Babylon on Meta Wiki. WikiProject Med Foundation was the first attempt to get a truly global organization of medical Wikipedia editors. Most medical professionals are fluent in English, and we really try to engage in discussion in other languages when we can, so I think there is a real benefit in creating a global community for medical editors. We are not large enough yet that we have all the relevant people on English Wikipedia, and we will probably never be because there are always specialists in other countries with very specific knowledge that we can leverage. That makes international collaboration really great. As for the local language integrators, the idea is to have editors who are willing help out and be an intermediary between that community and our translator community. We have a page where all our finished translations are added. An integrator would patrol that page on a regular basis, inform the respective language Wikipedia that the new translation is ready. The language Wikipedia’s reader community share feedback on the translation quality and suggest for improvement. For us, it is really easy to just add articles without going through them thoroughly. But, that would not work at all. For things to work, we need someone who both knows Wiki markup and the target language so that the integration can go smoothly. To stay up to date, follow the project’s grant page. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. He wrote the article on the Carolina Panthers: tales from Wikipedia’s NFL editors – Wikimedia Blog […] They watch over the sum of all knowledge, whether it’s American football, military history, medical content, or African breads, to ensure that it is preserved for generations to […] Posted in WikipediaTagged Individual Engagement Grants, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/07/30/doctors-working-to-bridge-wikipedias-medical-gap/

cc40

Subhashish Panigrahi is a volunteer contributor for Wikipedia and has worked in the past as a community and program support consultant for Wikimedia Foundation. Internet users from around the world of

en

Learnings from the events that presented the Wikimedia to heritage professionals in Argentina, Mexico, and Chile, while testing the Add an image feature on Wikipedia This blog post is Part I of II. Find here the Part II, with Wikimedia Mexico and Wikimedia Chile’s perspectives. As part of the 2021-2022 fiscal year, the Newcomer experience pilot, a project developed by the Wikimedia Foundation’s Growth team, started to plan the Add an image (Anãdir una imagen in Spanish) feature. This beta component would be added to a few Wikipedia languages as a way to help new users engage more with the platform through small and easy tasks. Specifically, this feature would make it easier to add images and captions to articles, based on topics, such as Art, Architecture, History, Chemistry, Technology, and so on, as well as regions (Africa, Central America, North America, South America, Asia, Europe, and Oceania). Mockup of part of the Add an image workflow But before adding this feature, the team needed to test it. That’s where the GLAM & Culture team entered the project. For us, the Add an image feature was an opportunity to not only engage new users with the visual culture of Wikimedia, but also to help improve the connection on Wikipedia between images from Wikimedia Commons and structured data from Wikidata, and consequently, enhance the appeal and readability of Wikipedia articles in Spanish. The team was especially interested in this initiative because, since its creation, it has been engaging in conversations about visual culture and the Wikimedia projects. Recently, the team even organized the Image Description Week and two Annual Planning Conversations with Maryana Iskander about Wikimedia Commons. The Add an image would also be an opportunity to engage with heritage professionals, particularly museum workers, especially as we believed this group was uniquely qualified to judge the selection and captioning of images on Wikipedia, since they usually work closely with visual culture. So, in the first half of 2022, both the GLAM & Culture and Growth teams decided to organize a series of workshops together with Wikimedia Argentina, Wikimedia Mexico, and Wikimedia Chile. In a nutshell, the objectives of these events were two: Test the Add an image feature developed for the Newcomer experience pilot; Further develop the GLAM-Wiki community in Spanish-speaking Latin America by engaging heritage professionals. To accommodate the needs of the organizing affiliates, we requested the Newcomer team to add extra filters with articles about each of the countries (Argentina, Mexico, and Chile), in addition to activating the possibility of combining topics (e.g., GLAM Argentina + art. The experiment yielded four events between March and April 2022: March 7th – Test event organized by Wikimedia Argentina with ADiMRA; March 18th – Main event organized by Wikimedia Argentina with many heritage professionals; April 1st – Event organized by Wikimedia Mexico with many heritage professionals; April 20th – Event organized by Wikimedia Chile with many heritage professionals. After the start of the initiative, we also noticed similarities this feature could have with the #1Lib1Ref campaign, but with images instead of references and museum professionals instead of librarians. That’s why, together with WMAR, WMMX, and WMCL, we decided to name this set of events #1Pic1Article. Below, you will find the stories of the three affiliates and the learnings from the point of view of each local organizer: When the Wikimedia Foundation, through the GLAM team and the Growth team, contacted us to carry out #1Pic1Article in the Latin American region, the first thing I thought was: “What a great opportunity to connect those from cultural fields with Wikimedia projects!” It was a dynamic tool, with a friendly interface for people who are not strictly from the Wikimedia universe and that would surely allow a greater real connection with participants from museums. This was an issue that was of particular interest to me, due to my museums related professional and academic background. Before working at Wikimedia Argentina, my relationship with people and heritage came through the role of facilitator in areas such as educational action and cultural mediation, that is, maintaining close contact with different audiences of museums and cultural centers, so that by activating their own prior knowledge and common senses they could achieve learning experiences around pieces of heritage. Upon discovering the Wikimedia universe, I saw myself in some ways limited in this connection with people in a physical, face-to-face, and tangible way. But on the other hand, I discovered an enormous potential linked to the collaborative building of knowledge, a fundamental pillar that is shared with educational practices in museums: understanding that there is not a single point of view on a certain subject but that there are multiple meanings, which build narratives. Narratives that are not neutral but that take on certain ideas and values. Latin America is a symbolically complex territory, with truly diverse representations, in many cases built by the outlook of others. It was not enough to just connect images to Wikipedia articles if we could not learn to discern, if these images represented ideas “of others”, and if we could not debate whether the images continued to endorse hegemonic stories. In other words, we had to address the debate of denaturalizing our gaze and learn to contextualize visual stories. Cora Garmanik, a photojournalism researcher in Argentina, was fundamental in this process and I think it was a great and successful experience to have her share her expertise in these meetings. Those who work in museums are connected to visual culture and it’s easy for them to generate adequate, accessible, and understandable descriptions because they do it on a daily basis. However, as they are immersed in a place with a heavy cultural and symbolic heritage it was important that they would be able to critically address the circulation of images both within their institutions and outside of them, in this case, in the digital ecosystem. And #1Pic1Article, through the Add an image function, turned into a great opportunity to explore this aspect and put it into practice. As in any activity where technology challenges us, we humans are the ones who have the last word in applying our criteria and our abilities to choose one thing over something else. As cultural workers – whether in museums, libraries, archives, universities, or civil organizations – the roles of research, communication, and dissemination are essential so that images do not circulate without their proper contexts and truly become allies of knowledge. In this way, an initiative that combined a thoughtful and attentive look at the use of images and a dynamic tool to connect said images with articles, attracted interest in the Argentine cultural community, with more than 150 persons interested in participating in these meetings. We had the support of the Asociación de Directores de Museos de la República Argentina (ADiMRA) (Association of Museum Directors of the Republic of Argentina) and the área de Formación y Redes de la Dirección Nacional de Museos (Training and Networks area of the National Directorate of Museums), which promoted the participation of people from museums throughout the country, thus turning the event into a national one. The production of the events at the regional level was led by Wikimedia Argentina together with the Wikimedia Foundation. During December, January, and February, preliminary preparations were carried out, such as contacting and confirming Cora Garmanik as a guest specialist, conducting a series of tests of the Add an Image tool together with the Growth team, which included the search for a selection of articles considered to be of real relevance to local contexts – e.g., working on articles not only about Argentina but also where Argentina is named. We also worked on the design of a general document that could explain the relevance of this meeting for Latin American cultural references and we began conversations with the chapters of Chile and Mexico to include them in the proposal. We defined dates and hired two people to follow through on the implementation of the project. With Andy and Nicole, we began to think about the dynamics of the event, the order and duration of the presentations, and how participatory it was going to be. We agreed at all times that the important thing was to get people interested in Wikimedia projects and that to accomplish this, we had to address their perspectives, and not ours. Also, speaking in technical terms or talking about topics that were not representative of the cultural community would not get our participants involved. Badge designed was an award upon completion of a #1Pic1Article event The events in Argentina were the first in the region – followed by Mexico and Chile, respectively – and it was possible to test different ways of approaching the participants, where some of these approaches were more motivating than others. The splitting up into Zoom groups to use the tool simultaneously allowed for a fluid exchange between different interested parties and the organizers for we made ourselves available to assist in the process of adding images to Wikipedia. Sometimes, even encouraging the participants to choose images, even though they were not familiar with the subject, valuing the role of previous research, at the very least, reading the descriptions and categories of the original images in Wikimedia Commons, in order to be able to decide their relevance in the suggested articles. I think this empowered many people who felt they “didn’t know” or “couldn’t,” discovering an easy-to-use tool with which to apply their criteria, driven by the theoretical content shared by Cora. Along the same lines, once the moment of working in small groups was over, a general exchange was encouraged where one person from each group told what theirs and their colleagues’ experience had been in the use of the Add an image feature. In the second event in Argentina, for example, I was with 5 other people from the field of museums, one of whom was excited to share his screen to show us how his process was getting along. In his case, an image of a Bayeux tapestry was being suggested in connection with an article on a plowing technique, which at first aroused doubts in everyone. Then, by researching the image and reading its description in English, we could see that in its fabric there was a scene represented where that specific plowing technique was used. In this way, this participant associated the image to the article and wrote a description using both the information that was already on Commons – translating it into Spanish – and the information from the article, thus generating a description that contextualized the image. As for the exchanges after the work in small groups, very interesting comments emerged regarding the variety and quantity of topics that exist and of which not all of us have specific knowledge about, but to which, nevertheless, we can contribute with small bits of data that connect with other pieces of information. One of the participants even referred to this tool as “a ball of wool” from which it is possible to continue pulling to obtain a thread, and that thread intersects with other threads, generating a network of knowledge and learning. Furthermore, the issue of collaboration and of being seen as agents of change, of multiplication of knowledge, came up. The idea of ​​reflecting on the use of images, of how representative they are of the topics to be discussed, and, if representative, of being very precise with their description based on the context, was also highlighted. The idea is not to overwhelm with too much information, but simply provide “small bits of data that will later form the network”, in the words of one of the participants. The most gratifying part of the meetings was this final exchange, where the knowledge of each participant connected with that of others, revealing a motivation to improve the encyclopedia and an interest in the existing possibilities in terms of the circulation of images. But above all, reflecting an empowerment in the role of collaboratively building a visual culture that is more representative of the South, that is removed from cultural stereotypes that are foreign to the region and that can reflect narratives more in line with Latin American contexts. I think our mission was accomplished. If there are people who feel motivated to improve Wikipedia, Wikimedia Commons, or any other project in order to better reflect their local history and culture, then we are on our way to promoting a more sustainable and open movement. Find here the Part II, with Wikimedia Mexico and Wikimedia Chile’s perspectives. Comments are closed automatically after 21 days. Posted in Events, GLAM, Growth, Partnerships & EventsTagged Add an image, GLAM, GLAM-Wiki, Growth, Newcomer experience pilot, Wikimedia Argentina, Wikimedia Chile, Wikimedia México, Wikimedia Mexico Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2022/06/21/1pic1article-i-how-latin-american-heritage-experts-added-images-to-wikipedia/

cc40

Learnings from the events that presented the Wikimedia to heritage professionals in Argentina, Mexico, and Chile, while testing the Add an image feature on Wikipedia This blog post is Part I of II. Fi

en

In the summer of 2011, I got an invitation to attend the Wikimedia Foundation’s education summit in Boston. The summit opened my eyes to the ways other professors were using Wikipedia in the classroom, and to the additional potential suggested by the Wikipedia community. All of my 25 students used Wikipedia, but only one or two had ever edited. But one of them, Michelle Chahine, volunteered to spent time with Wikipedia’s instructional tools and boil down a simplified version for class use. I then asked students to write, edit, or correct a Wikipedia article in English about an area of special knowledge and expertise, and record the process. Then they performed the same exercise on a Wikipedia article in an additional language. This was where things got really interesting. First, my students had assumed that Wikipedia content on the same subject would be similar in different languages. This was often not the case. One student from Eastern Europe had extensive experience in minority rights. She looked at the Wikipedia article on Roma (or gypsies) in English, and added a minor edit. But the entry in her native language disturbed her with its negative language. She performed an edit with full citation, but it was immediately taken down by the lead editor of the page, who had written the problematic content. This showed us how powerful the correction process could be in a large language group, but also signaled problems in in small language groups (in this case, about 10 million people) or countries with less experience in creating content. This year, the most interesting result came from an Asian student who had grown up in a rural area, and strongly believes in the mission of Wikipedia to bring information to areas that lack printed resources. This student reviewed the entry about women who had been captured by the Japanese army during World War II and forced to sexually service the troops. My student found that the English page used accurate language to describe their plight, but the entry in his native language used a term closer to “prostitute.” He performed an edit, and at least initially, it held. But the class was struck by the importance of the terminology, given the likelihood that the victims’ grandchildren would read this version of their families’ wartime experience. I shared student papers on these topics with the Wikimedia Foundation (with the students’ permission), and I’m eager to see where these assignments will go in the future. I can already see one major advantage: there is an absolute difference between being a passive Wikipedia reader, and performing even a single minor edit. Once a student (or a professor) gets his “feet wet” with an edit, he crosses the boundary into being a contributor, and takes the capability along wherever he goes. Anne Nelson is a specialist on international media and an award-winning author and playwright. She teaches at Columbia’s School of International and Public Affairs. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Global, Wikipedia Education ProgramTagged Academia, United States Education Program, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/02/11/multilingual-learning-through-the-wikipedia-education-program/

cc40

In the summer of 2011, I got an invitation to attend the Wikimedia Foundation’s education summit in Boston. The summit opened my eyes to the ways other professors were using Wikipedia in the classroom

en

23 February 2017 by Serena Cangiano, Giovanni Profeta, Marco Lurati, Fabian Frei, Florence Devouard, Iolanda Pensa and Samir Elsharbaty Photo by MONUSCO, CC BY-SA 2.0 A recent workshop has used Wikidata to demonstrate that a gender gap still exists on Wikipedia: women born in Africa in the 19th and 20th centuries, for example, make up only 15–20% of the total number of biographies. More broadly, systemic bias also plays a factor: the number of articles about people born in Africa is extremely limited when compared to people born in Western countries, like Germany, Switzerland, or Italy. Wikidata, a central storage place for the structured data of its Wikimedia sister projects, allows expert users to put up queries like those above and generate large data sets. From 6 to 9 February 2017, we held an intensive workshop in Lugano, Switzerland, to figure out ways to generate data visualizations and communicate the knowledge gaps that exist in Wikimedia projects. The Laboratory of Visual Culture at the University of Applied Sciences and Arts of Southern Switzerland (SUPSI) adopted the experiment in an effort to support the research project Wikipedia Primary School. Wikipedia biographies about people born in Africa, sized by total number. Red represents women, and turquoise represents men. Chart by G.prof, CC BY-SA 4.0. The workshop participants explored Wikidata queries and fundamental research questions regarding the typologies and qualities of biographies of notable persons from Africa. The queries have been supported by information about content gaps and Wikidata, provided by Wikipedians Florence Devouard and Jens Ohlig. We started working on this topic to build on a great example of data visualization about the distribution of biographies of notable people throughout history, created by the Oxford Internet Institute. The goal was to dig into this topic by manipulating large datasets and by sharing with the community pictures of the gaps existing between Africa and a selection of European countries with the largest populations. In the comparison, Africa nearly disappears. We have validated our hypothesis by finding evidence in the data and by visualizing the gap. The workshop aimed at testing a method to work with Wikidata. It is a tool that still requires the expertise of proficient users. Moreover, we were concerned with developing a valid format that can be replicated in future workshops addressing the topic of knowledge gaps in Wikimedia projects. Laboratory of Visual Culture at the University of Applied Sciences and Arts of Southern Switzerland (SUPSI) Announcing the 2017–18 Ombuds Commission: The Ombudsman Commission is a group of volunteers who investigate complaints about violations of the privacy policy, and in particular concerning the use of CheckUser and Oversight tools, on any Wikimedia project for the Board of Trustees. Early this month, the commission has announced its new and returning members for this year. More information and the announced list of members can be found on Wikimedia-l. Danish Wikipedia celebrates its fifteenth birthday: On 1 February, the Danish Wikipedia community held a meetup in Copenhagen to celebrate the fifteenth birthday of the Danish Wikipedia. The meetup was attended by Wikipedians, media representatives, and local supporters of the movement. More information on the Danish Wikipedia. Vienna hosts the second WikiCite in May 2017: WikiCite, a three-day conference, summit and hack day, will be hosted in Vienna on 23–25 May 2017. It will come only days after the Wikimedia Hackathon, which will be held from 19–21 May in the same venue. The conferences will be an opportunity for the participants to present on progress of the existing and new initiatives around citations and bibliographic data across Wikimedia projects, discuss technical, social, outreach and policy directions, and hack on new ideas and applications. More information can be found on Wikimedia-l. Europeana commemorates WWI: Europeana is challenging Wikimedia affiliates to create portfolios of their past and current activities relating to the First World War (1914–18). The contest aims to showcase the collections to demonstrate the diversity of ways to explore this period in Europe’s history. Submissions are open through the end of July 2017. More information about the contest and how to participate can be found on Meta. 400,000 photographs from the Portable Antiquities Scheme uploaded to Commons: The Portable Antiquities Scheme (PAS) publishes photographs and descriptions of archaeological finds registered in England and Wales on its website, https://finds.org.uk, under a free CC-BY license. Wikipedian Fæ has uploaded over 400,000 of these photos to Wikimedia Commons, Wikimedia’s free media repository. More information about the project is available on Commons and volunteers are welcome to help put the photos in use by adding them to Wikipedia articles. Marathon to expand the Ukrainian Wikipedia on its birthday: Last month marked the thirteenth anniversary of the Ukrainian Wikipedia. The Ukrainian community celebrated by holding an online marathon encouraging the existing and new Wikipedia editors to create at least one Wikipedia article between 28 and 30 January 2017. In addition to editing, celebration meetups were held in sixteen regions of Ukraine. More about the event on Wikimedia Ukraine blog (in Ukrainian). Compiled and edited by Samir Elsharbaty, Digital Content Intern Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Community, Community digest, Gender gapTagged Africa, Content gaps, Data visualization, wikidata, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2017/02/23/digest-data-visualization/

cc40

23 February 2017 by Serena Cangiano, Giovanni Profeta, Marco Lurati, Fabian Frei, Florence Devouard, Iolanda Pensa and Samir Elsharbaty Photo by MONUSCO, CC BY-SA 2.0 A recent workshop has used Wikida

en

Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Document Type : Review Article 1 Nanobiotechnology Department, Faculty of Innovative Science and Technology, Razi University, Kermanshah, Iran 2 Nanobiotechnology Laboratory, Department of Biotechnology, SGB Amravati University, Amravati-444 602, Maharashtra, India 3 Department of Microbiology, Nicolaus Copernicus University, 87-100 Toruń, Poland Finding efficient therapeutic strategies to fight antibiotic-resistant bacteria is a complicated affair specifically in the therapy of chronic bacterial infections related to hospital-acquired infections. Recently, three major antibacterial systems based on antisense RNA, CRISPR-Cas9, and metal/metal oxide nanoparticles particularly silver (Ag) nanoparticles have shown more effective antibacterial activity compared to conventional antibiotics. ROS generation, attachment to the cell membrane, disruption of bacterial envelop, inactivation of electron transport chain, decreasing the local pH, modulation of cell signaling, and denaturation of biological macromolecules such as proteins and nucleic acids have been found as the main antibacterial functions of Ag nanoparticles. Antisense RNA, a single-stranded RNA, can hybridize with complementary genes in messenger RNA (mRNA) followed by blockage translation of these genes into proteins. Moreover, CRISPR (clustered regularly interspaced short palindromic repeats) is a family of viral DNA sequences derived from bacteriophages, which can target and destroy foreign DNA by nuclease activity. There are 2 classes and 6 subtypes (I-VI) of CRISPR-Cas systems, which may be engineered as potential antibacterial agents to target specific sequences. Therefore, here, recent advances and challenges for the antibacterial application of these three therapeutic agents are presented. Selected author of this article by journal Google Scholar(H Index=69); Publons(H Index=48) This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible World Health O (2018) Managing epidemics: key facts about major deadly diseases. World Health Organization, Geneva Monahan M, Jowett S, Pinkney T, Brocklehurst P, Morton DG, Abdali Z, Roberts TE (2020) Surgical site infection and costs in low- and middle-income countries: A systematic review of the economic burden. PLOS ONE 15(6):e0232960. doi:https://doi.org/10.1371/journal.pone.0232960 Guo Y, Song G, Sun M, Wang J, Wang Y (2020) Prevalence and Therapies of Antibiotic-Resistance in Staphylococcus aureus. Frontiers in Cellular and Infection Microbiology 10(107). doi:https://doi.org/10.3389/fcimb.2020.00107 Chen J, Sidibi AM, Shen X, Dao K, Maiga A, Xie Y, Hesketh T (2021) Lack of antibiotic knowledge and misuse of antibiotics by medical students in Mali: a cross-sectional study. Expert Review of Anti-infective Therapy 19(6):797-804. doi:https://doi.org/10.1080/14787210.2021.1857731 Mallah N, Badro DA, Figueiras A, Takkouche B (2020) Association of knowledge and beliefs with the misuse of antibiotics in parents: A study in Beirut (Lebanon). PLOS ONE 15(7):e0232464. doi:https://doi.org/10.1371/journal.pone.0232464 Van TTH, Yidana Z, Smooker PM, Coloe PJ (2020) Antibiotic use in food animals worldwide, with a focus on Africa: Pluses and minuses. Journal of Global Antimicrobial Resistance 20:170-177. doi:https://doi.org/10.1016/j.jgar.2019.07.031 Tariq S, Wani S, Rasool W, Shafi K, Bhat MA, Prabhakar A, Shalla AH, Rather MA (2019) A comprehensive review of the antibacterial, antifungal and antiviral potential of essential oils and their chemical constituents against drug-resistant microbial pathogens. Microbial pathogenesis 134:103580. doi:https://doi.org/10.1016/j.micpath.2019.103580 Azeez SH, Jafar SN, Aziziaram Z, Fang L, Mawlood AH, Ercisli MF (2021) Insulin-producing cells from bone marrow stem cells versus injectable insulin for the treatment of rats with type I diabetes. Cellular, Molecular and Biomedical Reports 1(1):42-51 Baquero F, Martínez JL, Lanza VF, Rodríguez-Beltrán J, Galán JC, Millán AS, Cantón R, Coque TM Evolutionary Pathways and Trajectories in Antibiotic Resistance. Clinical Microbiology Reviews 0(0):e00050-00019. doi:https://doi.org/doi:10.1128/CMR.00050-19 Xue K, MacLaren RE (2020) Antisense oligonucleotide therapeutics in clinical trials for the treatment of inherited retinal diseases. Expert Opinion on Investigational Drugs 29(10):1163-1170. doi:https://doi.org/10.1080/13543784.2020.1804853 Patil SD, Sharma R, Srivastava S, Navani NK, Pathania R (2013) Downregulation of yidC in Escherichia coli by Antisense RNA Expression Results in Sensitization to Antibacterial Essential Oils Eugenol and Carvacrol. PLOS ONE 8(3):e57370. doi:https://doi.org/10.1371/journal.pone.0057370 Palacios Araya D, Palmer KL, Duerkop BA (2021) CRISPR-based antimicrobials to obstruct antibiotic-resistant and pathogenic bacteria. PLOS Pathogens 17(7):e1009672. doi: https://doi.org/10.1371/journal.ppat.1009672 Zheng Y, Han J, Wang B, Hu X, Li R, Shen W, Ma X, Ma L, Yi L, Yang S, Peng W (2019) Characterization and repurposing of the endogenous Type I-F CRISPR–Cas system of Zymomonas mobilis for genome engineering. Nucleic Acids Research 47(21):11461-11475. doi:https://doi.org/10.1093/nar/gkz940 Zohra T, Numan M, Ikram A, Salman M, Khan T, Din M, Salman M, Farooq A, Amir A, Ali M (2021) Cracking the Challenge of Antimicrobial Drug Resistance with CRISPR/Cas9, Nanotechnology and Other Strategies in ESKAPE Pathogens. Microorganisms 9(5):954. doi:https://doi.org/doi:10.3390/microorganisms9050954 Bikard D, Euler CW, Jiang W, Nussenzweig PM, Goldberg GW, Duportet X, Fischetti VA, Marraffini LA (2014) Exploiting CRISPR-Cas nucleases to produce sequence-specific antimicrobials. Nature Biotechnology 32(11):1146-1150. doi:https://doi.org/10.1038/nbt.3043 Citorik RJ, Mimee M, Lu TK (2014) Sequence-specific antimicrobials using efficiently delivered RNA-guided nucleases. Nature Biotechnology 32(11):1141-1145. doi:https://doi.org/10.1038/nbt.3011 Alavi M, Nokhodchi A (2021) Micro- and nanoformulations of paclitaxel based on micelles, liposomes, cubosomes, and lipid nanoparticles: Recent advances and challenges. Drug Discovery Today). doi:https://doi.org/10.1016/j.drudis.2021.10.007 Alavi M, Webster TJ (2021) Recent progress and challenges for polymeric microsphere compared to nanosphere drug release systems: Is there a real difference? Bioorganic & Medicinal Chemistry 33:116028. doi:https://doi.org/10.1016/j.bmc.2021.116028 Hu R, Liao G, Huang Z, Qiao H, Liu H, Shu Y, Wang B, Qi X (2021) Recent advances of monoelemental 2D materials for photocatalytic applications. Journal of Hazardous Materials 405:124179. doi:https://doi.org/10.1016/j.jhazmat.2020.124179 Alavi M, Rai M (2021) Chapter 11 - Antibacterial and wound healing activities of micro/nanocarriers based on carboxymethyl and quaternized chitosan derivatives. In: Rai M, dos Santos CA (eds) Biopolymer-Based Nano Films. Elsevier, pp 191-201. doi:https://doi.org/10.1016/B978-0-12-823381-8.00009-0 Alavi M, Jabari E, Jabbari E (2021) Functionalized carbon-based nanomaterials and quantum dots with antibacterial activity: a review. Expert Review of Anti-infective Therapy 19(1):35-44. doi:https://doi.org/10.1080/14787210.2020.1810569 Hamdan N, Yamin A, Hamid SA, Khodir WKWA, Guarino V (2021) Functionalized Antimicrobial Nanofibers: Design Criteria and Recent Advances. Journal of Functional Biomaterials 12(4):59. doi:https://doi.org/doi:10.3390/jfb12040059 Alavi M, Kennedy JF (2021) Recent advances of fabricated and modified Ag, Cu, CuO and ZnO nanoparticles by herbal secondary metabolites, cellulose and pectin polymers for antimicrobial applications. Cellulose 28(6):3297-3310. doi:https://doi.org/10.1007/s10570-021-03746-5 Choi Y, Lee SY (2020) Biosynthesis of inorganic nanomaterials using microbial cells and bacteriophages. Nature Reviews Chemistry 4(12):638-656. doi:https://doi.org/10.1038/s41570-020-00221-w Alavi M, Nokhodchi A (2021) Synthesis and modification of bio-derived antibacterial Ag and ZnO nanoparticles by plants, fungi, and bacteria. Drug Discovery Today 26(8):1953-1962. doi:https://doi.org/10.1016/j.drudis.2021.03.030 Kumar JA, Krithiga T, Manigandan S, Sathish S, Renita AA, Prakash P, Prasad BSN, Kumar TRP, Rajasimman M, Hosseini-Bandegharaei A, Prabu D, Crispin S (2021) A focus to green synthesis of metal/metal based oxide nanoparticles: Various mechanisms and applications towards ecological approach. Journal of Cleaner Production 324:129198. doi:https://doi.org/10.1016/j.jclepro.2021.129198 Alavi M, Varma RS (2021) Antibacterial and wound healing activities of silver nanoparticles embedded in cellulose compared to other polysaccharides and protein polymers. Cellulose 28(13):8295-8311. doi:https://doi.org/10.1007/s10570-021-04067-3 Yougbaré S, Mutalik C, Okoro G, Lin IH, Krisnawati DI, Jazidie A, Nuh M, Chang C-C, Kuo T-R (2021) Emerging Trends in Nanomaterials for Antibacterial Applications. Int J Nanomedicine 16:5831-5867. doi:https://doi.org/10.2147/IJN.S328767 Petriman N-A, Jauß B, Hufnagel A, Franz L, Sachelaru I, Drepper F, Warscheid B, Koch H-G (2018) The interaction network of the YidC insertase with the SecYEG translocon, SRP and the SRP receptor FtsY. Scientific Reports 8(1):578. doi:https://doi.org/10.1038/s41598-017-19019-w Kedar GC, Brown-Driver V, Reyes DR, Hilgers MT, Stidham MA, Shaw KJ, Finn J, Haselbeck RJ (2007) Evaluation of the metS and murB Loci for Antibiotic Discovery Using Targeted Antisense RNA Expression Analysis in Bacillus anthracis. Antimicrobial Agents and Chemotherapy 51(5):1708-1718. doi:https://doi.org/doi:10.1128/AAC.01180-06 Park JY, Moon BY, Park JW, Thornton JA, Park YH, Seo KS (2017) Genetic engineering of a temperate phage-based delivery system for CRISPR/Cas9 antimicrobials against Staphylococcus aureus. Scientific Reports 7(1):44929. doi:https://doi.org/10.1038/srep44929 Cobb LH, Park J, Swanson EA, Beard MC, McCabe EM, Rourke AS, Seo KS, Olivier AK, Priddy LB (2019) CRISPR-Cas9 modified bacteriophage for treatment of Staphylococcus aureus induced osteomyelitis and soft tissue infection. PLOS ONE 14(11):e0220421. doi:https://doi.org/10.1371/journal.pone.0220421 Rodrigues M, McBride SW, Hullahalli K, Palmer KL, Duerkop BA (2019) Conjugative Delivery of CRISPR-Cas9 for the Selective Depletion of Antibiotic-Resistant Enterococci. Antimicrobial Agents and Chemotherapy 63(11):e01454-01419. doi:https://doi.org/doi:10.1128/AAC.01454-19 Reuter A, Hilpert C, Dedieu-Berne A, Lematre S, Gueguen E, Launay G, Bigot S, Lesterlin C (2021) Targeted-antibacterial-plasmids (TAPs) combining conjugation and CRISPR/Cas systems achieve strain-specific antibacterial activity. Nucleic Acids Research 49(6):3584-3598. doi: https://doi.org/10.1093/nar/gkab126 Dakal TC, Kumar A, Majumdar RS, Yadav V (2016) Mechanistic Basis of Antimicrobial Actions of Silver Nanoparticles. Frontiers in Microbiology 7(1831). doi:https://doi.org/10.3389/fmicb.2016.01831 Bilal I, Xie S, Elburki MS, Aziziaram Z, Ahmed SM, Jalal Balaky ST (2021) Cytotoxic effect of diferuloylmethane, a derivative of turmeric on different human glioblastoma cell lines. Cellular, Molecular and Biomedical Reports 1(1):14-22 Aziziaram Z, Bilal I, Zhong Y, Mahmod AK, Roshandel MR (2021) Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue. Cellular, Molecular and Biomedical Reports 1(1):23-32 Ayaz M, Ullah F, Sadiq A, Ullah F, Ovais M, Ahmed J, Devkota HP (2019) Synergistic interactions of phytochemicals with antimicrobial agents: Potential strategy to counteract drug resistance. Chemico-Biological Interactions 308:294-303. doi:https://doi.org/10.1016/j.cbi.2019.05.050 Ghasemi M, Khorsandi K, Kianmehr Z (2021) Photodynamic inactivation with curcumin and silver nanoparticles hinders Pseudomonas aeruginosa planktonic and biofilm formation: evaluation of glutathione peroxidase activity and ROS production. World Journal of Microbiology and Biotechnology 37(9):149. doi:https://doi.org/10.1007/s11274-021-03104-4 Roy A, Bulut O, Some S, Mandal AK, Yilmaz MD (2019) Green synthesis of silver nanoparticles: biomolecule-nanoparticle organizations targeting antimicrobial activity. RSC Advances 9(5):2673-2702. doi:https://doi.org/10.1039/C8RA08982E Volume 1, Issue 2 - Serial Number 2 Cellular, Molecular and Biomedical Reports Receive Date: 07 October 2021 Revise Date: 17 November 2021 Accept Date: 23 December 2021 First Publish Date: 23 December 2021 Alavi, M., & Rai, M. (2021). Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports, 1(2), 52-59. doi: 10.55705/cmbr.2021.142436.1014 Mehran Alavi; Mahendra Rai. "Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria". Cellular, Molecular and Biomedical Reports, 1, 2, 2021, 52-59. doi: 10.55705/cmbr.2021.142436.1014 Alavi, M., Rai, M. (2021). 'Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria', Cellular, Molecular and Biomedical Reports, 1(2), pp. 52-59. doi: 10.55705/cmbr.2021.142436.1014 Alavi, M., Rai, M. Antisense RNA, the modified CRISPR-Cas9, and metal/metal oxide nanoparticles to inactivate pathogenic bacteria. Cellular, Molecular and Biomedical Reports, 2021; 1(2): 52-59. doi: 10.55705/cmbr.2021.142436.1014 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_142436.html

cc40

Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) P

en

There are more than 1.9 million animals, plants, and other forms of life on Earth. In May 2007, some of the world’s leading scientists announced the development of the Encyclopedia of Life (EOL) to document them all. Inspired by biologist E. O. Wilson’s TED Wish and supported by more than $25 million in funding, the project aggregates and makes accessible information about species ranging from 19th century journals to modern online databases. See the page about Solanum lycopersicum, the garden tomato, as an example. Much of the information comes from Solanaceae Source, a specialized source of  names lists, species descriptions, specimen collections and publication lists for the genus Solanum. The Biodiversity Heritage Library provides historical public domain texts about the species from various published journals. Many other specialized and general resources contribute to the overall species page. A Wikipedia article included in an Encyclopedia of Life species page. The yellow background indicates that no curator has reviewed the content yet. Click the image to enlarge. You’ll also find a “Wikipedia” entry in the table of contents. It reveals a copy of the Wikipedia article about tomatoes. As of this writing, the article text has a yellow background. This means that an Encyclopedia of Life curator has not yet reviewed the content for inclusion in EOL. An EOL species page can have one or more curators who select and validate information added to EOL pages. Wikipedia articles, where they exist, are included by default. Once the article has been validated by a curator, the yellow background is removed. The information for curators and curation standards pages on EOL give some additional background on the curation process, which applies to all content objects in EOL. Specific guidelines have been written for curation of content from Wikipedia and Wikimedia Commons. We’re particularly pleased that EOL encourages its curators to improve Wikipedia directly if errors or omissions are found. So far, more than 200 Wikipedia articles have been reviewed through this process. Reviewers classify the information as follows: ‘trusted’ – reviewed by curator and not deemed to contain substantially incorrect information ‘untrusted’ – reviewed by curator and deemed to include incorrect or unverifiable information ‘inappropriate’ – reviewed by curator and deemed to not be eligible for inclusion in EOL for other reasons (e.g. too short to add value) EOL makes the entirety of all review information (who reviewed what when, with what outcome) available through an Atom feed. This means that Wikipedians, and others, can use this information easily in the development of new applications. The book creator tool makes it possible to order a printed and bound book from any Wikipedia article selection. A custom cover can be chosen. Nautilus photograph by Lee Berger, Creative Commons Attribution/Share-Alike License. (Click to enlarge.) A proof-of-concept for expert reviews Magnus Manske is a biochemist and programmer at the Sanger Institute in the United Kingdom. He is also a long-time Wikimedia volunteer, and wrote the first version of the PHP software used by Wikipedia, which later became MediaWiki. As a scientist, Magnus has advocated for the scientific community to use and improve Wikipedia, most recently as co-author of the paper Ten Simple Rules for Editing Wikipedia. I informed Magnus about the new EOL review information, and suggested that we might want to explore using this information to generated printed books or PDF collections of reviewed articles. The software for exporting Wikipedia articles into books already exists, so it was just a matter of putting two and two together. So, Magnus used the available data feed to create an automated tool that creates a list of all EOL-reviewed article versions in a form that can be used by Wikipedia’s book tool. This makes it possible to download a PDF file or order a printed book that only contains EOL-reviewed versions of Wikipedia species articles. To try it out, visit the page for Magnus’ example book. Click “Download PDF” to generate the (very large) PDF file that contains all the species articles, or “order printed book” to preview or order a printed book from PediaPress (which, as of this month, also offers books in color and hardcover format). If you want to remix or play with the book further, you can click “Open book creator”. We’re very pleased with this first proof-of-concept, and are grateful to the Encyclopedia of Life team for engaging its community in the curation of Wikipedia articles. Both parties benefit: The Encyclopedia of Life enriches its species pages using the often well-developed Wikipedia content. Wikipedia benefits because EOL’s trusted reviewers add their stamp of approval to Wikipedia articles, which helps Wikipedia readers and editors alike. Where EOL reviewers do not approve, they are encouraged to edit the Wikipedia article. I asked Bob Corrigan, EOL Product Manager and Acting Deputy Director, to give his take on this project. He writes: “This is definitely a win-win partnership. EOL is focused on providing very deep, structured access to trusted biodiversity information from our network of content partners and curators, and vetted Wikipedia articles can be a terrific gateway to this information. We see a closer relationship with Wikimedia as an important way to expand access to global knowledge about life on Earth.” Hardcover book made from curated Wikipedia articles. Photo credit: Guillaume Paumier; Nautilus photograph by Lee Berger. Creative Commons Attribution/Share-Alike License 3.0 Example page from the book. Photo credit: Guillaume Paumier; Nautilus photograph by Lee Berger. Creative Commons Attribution/Share-Alike License 3.0 Magnus’ implementation was already created with an eye to future extensibility. If you’re inclined to take a closer technical look, check out Magnus’ “Sifter-Books” script which generates the book data, and can potentially support multiple partner institutions/organizations providing article reviews. As of the time of this writing, Magnus has already added two additional groups who review Wikipedia articles, Rfam and Pfam, databases of RNA and protein families. Moreover, Magnus has written a small proof-of–concept script which makes the existence of reviews visible on Wikipedia itself. You need to create a user account on the English Wikipedia and follow the installation instructions to use the script. Once installed, a “Reviews” tab will indicate available article reviews. We look forward to exploring similar partnerships with subject-matter experts in institutions (like universities and libraries), scientific associations, and specialized knowledge communities. If you’re interested in this model, drop me a note (erik at wikimedia dot org). Deputy Director, Wikimedia Foundation Representative of Wikimedia in the Encyclopedia of Life Institutional Council Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. The font size is screwed up in this post. It looks like the line height is as well. Someone should peek at the source and remove any unintended formatting. I didn’t know that the WMF is among EOL official partners. We all love EOL, see e.g. some previous discussions on foundation-l: http://thread.gmane.org/gmane.org.wikimedia.foundation/16907 and http://thread.gmane.org/gmane.org.wikimedia.foundation/41378 Brilliant use of Wikipedia concept. Well done Magnus Posted in Friends, Highlights, Offline, WikipediaTagged Encyclopedia of Life, PediaPress, quality, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2010/12/09/encyclopedia-of-life-curates-wikipedias-species-articles/

cc40

There are more than 1.9 million animals, plants, and other forms of life on Earth. In May 2007, some of the world’s leading scientists announced the development of the Encyclopedia of Life (EOL) to do

en

Within the Wikimedia Foundation’s Editor Growth and Contribution Program, the first phase of a new contribution portal project was piloted on the Arabic Wikipedia over four weeks between 18th June and 17th July 2012. According to a preliminary analysis, it appears to have a positive effect on the ratio of new editors who make contributions to Wikipedia. The key idea of this first phase was to create a page with a simple design in order to test the overall concept, while monitoring the ability of new users to perform various simple Wikipedia tasks relying merely on reading visualized tutorial pages. The portal was named Bawabatu Almusharakah (Arabic : بوابة المشاركة), which is literally translated as “Contribution Portal” or “The Participation Gateway”. It is meant to evoke a space which provides help as well as an being an entrance point for newcomers to Wikipedia, enabling them to contribute to its contents and share the knowledge they possess, while collaborating and communicating with existing Wikipedia community members. Tutorial showing first steps in creating a new article, starting from the search box (Arabic). The design of this phase of the contribution portal consisted simply of a main portal page leading to visual help tutorials. The main page of the portal starts with the question “What would you like to do in Wikipedia?”, followed by six buttons each listing a possible answer (create a new article, user page or redirect, fix a typo, add a reference, or post a user talk page message), and linking to a corresponding step-by-step tutorial page. For the first test of the concept, we tried to keep the page design as simple as possible to avoid any visual distraction. We also aimed to use as little text as possible in order to quickly guide visitors to their target page without requiring much time for reading. To invite users to the portal, we ran banners using the local site notice on Arabic Wikipedia. During the first week of the pilot, the banners targeted only logged-in users. This brought a small number of visitors to the portal every day. After the first week, the banners were switched to target all readers, logged-in or not, which significantly boosted the number of visitors. Contribution ratio (average in red) over the past 5 years In order to understand whether viewing the portal leads to increased editing by new users, we adapted a new metric called “Contribution Ratio.” It is calculated as the proportion of the number of contributors (registered users with at least one edit so far) to the number of new registered users. The graph on the right shows the value of the contribution ratio extracted on a daily basis starting from 2007 on the Arabic Wikipedia. It shows that the contribution ratio was roughly in the range between 4% ~ 8% over the past 4 years, which means that only 4 ~ 8 users out of each 100 new accounts made at least one edit to the Arabic Wikipedia. Change in contribution ratio over May ~ July 2012, before launching the contribution portal and after launching it on Arabic Wikipedia For the purpose of demonstrating the effect of the contribution portal on contributions of new users, the value of the contribution ratio over the past three months is shown on the right. The graph is separated into three main regions: Control 1: The period before running any banners and before launching the contribution portal Control 2: The period of running banners landing on an existing help documentation page Contribution portal: The period of running banners landing on the contribution portal with step-by-step tutorials on how to contribute to Wikipedia (first shown only to logged-in users, then to all viewers, as described above) The graph indicates that running banners inviting site viewers to contribute to Wikipedia has an impact on the contribution ratio, as the average contribution ratio increased from 4.5 % during the Control 1 period to 5.1% during the Control 2. However, by landing the banners on the contribution portal with more appealing visualized help pages, the contribution ratio increased even further to 5.7%. This appears to be the combined effect of inviting users to contribute and also providing them with an easy-to-use method of learning how to contribute. We are working now on creating a new design for the next phase of the Contribution Portal, which we are planning to launch later in August, to determine whether improving the overall look and feel of the portal has any impact on its use. The next phase aims to incorporate a section for enhancing communication between new users and the existing community member, using the concept of the Teahouse project. The outcomes of this pilot project demonstrate the high effect of running banners using the local site notice as a powerful tool for attracting new editors, and that providing new users with simple, easy to understand, visual tutorials can encourage more of them to contribute to Wikipedia. We will keep you posted as the project moves forward, and look forward to see new users learning how to edit Wikipedia at the gate. Haitham Shammaa, Contribution Research Manager Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Editor RetentionTagged Arabic, multilingual post, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/08/15/pilot-project-arabic-wikipedia-move-needle-on-editor-growth/

cc40

Within the Wikimedia Foundation’s Editor Growth and Contribution Program, the first phase of a new contribution portal project was piloted on the Arabic Wikipedia over four weeks between 18th June and

en

Scuba diver Doug Taylor took a plunge to fix an error on a Wikipedia article in 2008, and is now an active contributor to the free knowledge movement. Photo by Helpameout, CC BY-SA 4.0. Taylor uploaded this image to illustrate the Wikipedia article on oxygen toxicity. Photo by RexxS, public domain A flowchart of diver certification grades in the United Kingdom. Chart by RexxS, CC BY-SA 3.0. Expert scuba diver Doug Taylor has been diving into all sorts of bodies of water for decades. He has taught recreational diving for more than 20 years as a national instructor for the Sub-Aqua Association in the United Kingdom. He even swam beneath floating ice in freezing water, an experience he describes as peaceful and absolutely breathtaking. When he is on shore, Taylor spends his time editing and writing Wikipedia articles about scuba diving. Doug’s 24-year experience as a teacher in secondary education led him to catch a mistake on Wikipedia and making his first edit in January 2008. “The reason I got involved with Wikipedia was because I was a scuba diver and I read an article on nitrogen narcosis and spotted an error and said ‘Oh no, that’s not right’”. So he created an account to fix that mistake, and went on to create over 20 articles, mostly about scuba diving — on topics like oxygen toxicity and other conditions related to deep diving. For his Wikipedia endeavors, Taylor goes by the name Rex Schneider, which has been his virtual alter ego since the days of Usenet. In 2012, he was elected to be a trustee of Wikimedia UK and dedicated himself full time to developing and improving issues that the organization faced that year. Taylor tells us that he continues to go to Wikipedia meetups in the UK. “Oh sure, I’m definitely stuck into [Wikipedia] … I even have to force myself to take breaks once in a while.” He adds, “I’ve been known to work through the night — and the last thing that kept me awake all night was sorting out a module that imports Wikidata into info boxes in Wikimedia.” After his article on oxygen toxicity became a featured article, and his list on signs and symptoms of diving became the first featured list in Wikipedia, he decided to join WikiProject Medicine, to share more knowledge about the medical conditions related to diving. The Wikiproject Med Foundation aims to educate and inform others through providing accurate and reliable knowledge on medical conditions that go beyond illnesses related to scuba diving. “Over the years, we decided that it would be great to have an organization that has a life of its own; so we created an organization, a non profit charity in the United States,” Taylor says. Thanks to his positive experience as a contributor, he has now become an active promoter of Wikipedia and the free knowledge movement: “We want to create something with it after all, it’s the biggest encyclopedia — and it only works because of all the people put their time into it.” Profile by Yoona Ha, Assistant Storyteller Intern, Wikimedia Foundation Interview by Jan Novak, Wikimedia volunteer Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Community, Editor engagement, Global, Profiles, Wikipedia, WikiProjectTagged diving, editor, ocean, scuba, scuba diving, sea, Wikimedia Blog (EN Archive), Wikimedia UK, Wikipedia, WikiProject Medicine Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2015/05/26/scuba-diving-on-wikipedia/

cc40

Scuba diver Doug Taylor took a plunge to fix an error on a Wikipedia article in 2008, and is now an active contributor to the free knowledge movement. Photo by Helpameout, CC BY-SA 4.0. Taylor uploade

en

This post is a discovery report written by Coder55 and slightly edited for publication. It’s part of a series of candid essays written by Google Code-in students, outlining their first steps as members of the Wikimedia technical community. You can write your own. I’m a 17-year-old boy from Germany interested in computer science. I write my own little programs in PHP, Python and Java and have even produced some Android apps. I completed a Python course in three days, and now I’m using Python to solve math problems. I heard about Google Code-in on a German news site for young people interested in computer science. Account creation and language selection The instructions for Google Code-in students were easy to understand, even for people who aren’t so good in English. After that, I created an account on mediawiki.org. The registration form looked modern; I wanted to take the user name ‘Coder55’, but it was already taken so an account creation error was displayed. The text I typed in for password and email were deleted after the error; maybe it could be saved in a session variable and written into the text fields via JavaScript. After registering and logging in, I saw many different options in the top line. It was easy to change the language and to read my welcome message. Maybe the button with the text ‘log out’ could be replaced by a logout button with a little picture, to make the top line smaller and even easier to understand. After that, I changed the language to German and Spanish because I wanted to see how much of the site had been translated. I was quite disappointed that only the top menu was completely translated. The left sidebar was not completely translated, even though many important links can be found there, like one to the Main Page. I was also surprised that the language of the content on the page didn’t change after I changed my language options: if I’m on the Main Page and I change the language to German, I still see the Main Page in English, although the left menu has partially changed to German. This puzzled me until I found out I had to click on ‘Hauptseite’, ‘Página principal’ etc. to see the Main Page in another language. How to become a MediaWiki hacker One thing that was missing for someone like me: example code of a really easy extension. Although all the aspects of developing are explained in detail in the Developing manual, seeing those easy extensions requires to follow several links; it would be really helpful for beginners to include and explain one or two of these examples in the manual. I had already been programming some little programs in PHP (chat server, forum etc.) so the next thing I did was to study MediaWiki’s coding conventions; they were explained clearly and were easy to understand. The ‘C borrowings’ part was really interesting. Around MediaWiki: API, bugzilla, git and Wikitech Unfortunately, I didn’t find the video on the API page very helpful. The pictures were blinking and the voices hard to understand. But the rest of the API documentation was really informative and easy enough to understand. After that, I looked at the “Development” section of the left sidebar. I visited the Bugzilla overview, and then the actual site. I really liked the idea of Bugzilla, where every developer can see where help is needed. However, if you don’t know specifically, what to look for, the search function in Bugzilla isn’t very helpful[Note 1]. I then clicked on the link called ‘browse repository’. I was positively surprised by what the site looked like. I especially liked the possibility to see which parts of MediaWiki had been just updated. I also took a look at at Wikitech; The Main Page looked really similar to Wikipedia and MediaWiki, so it seemed easy to navigate. On the next day, I read about how to install and configure MediaWiki. The documentation was clear and easy to read, but I didn’t understand all of it, probably because I’m more interested in developing than in hosting. Following this, I looked into more details about developing at the Developer hub. I had already studied the coding conventions, so I started reading the Pre-Commit Checklist. This checklist contained many questions, but for someone like me who hasn’t already uploaded code there, they are partially not understandable. The part about Testing was clearer for me because it was explained a little bit more. Maybe the questions in the checklist should be written in a little more detail, or some of the difficult words should be converted into links. I liked having an overview over all conventions at the bottom of the page. I could easily navigate to another convention list, like the coding conventions for JavaScript. These conventions were explained in detail and with clear examples. I especially liked the part about whitespace where many rules have been written clearly and concisely. MediaWiki is a very interesting platform and although some things are not perfect (e.g. translation or registering form), it is easy to join the community. The most active contributors are accessible on IRC, which makes communication easier. After discovering the technical world of MediaWiki, I’m really interested in getting involved into the community, although that will need to wait until I finish school. 2013 Google Code-in student ↑ Editor’s note: Bugzilla has since been upgraded, and its main page now features common search queries. Read in this series: Seeing through the eyes of new technical contributors Tech discovery report: What is this Wikitech thing anyway? Through the maze of newcomer developer documentation A junior developer discovers MediaWiki Discovering and learning by asking questions A young developer’s story of discovery, perseverance and gratitude Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in TechnologyTagged Tech discovery report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/03/31/a-junior-developer-discovers-mediawiki/

cc40

This post is a discovery report written by Coder55 and slightly edited for publication. It’s part of a series of candid essays written by Google Code-in students, outlining their first steps as member

en

Volume & Issue: Volume 1, Issue 1, April 2021, Pages 1-51 (Cellular, Molecular and Biomedical Reports) Original Article Cell, Organ and Tissue Culture Neonatal Screening for Glucose-6-phosphate dehydrogenase Deficiency in Ardabil Province, Iran, 2018-2019 Afshin Fathi; Manouchehr Barak; Mahshid Damandan; Firouz Amani; Rouhallah Moradpour; Irada Khalilova; Mehdi Valizadeh Original Article DNA, RNA, protein components Association between Human Endogenous Retrovirus K gene expression and breast cancer Masoud Tourang; Le Fang; Yuan Zhong; Ram Chandra Suthar Volume 1, Issue 1 , April 2021, Pages 7-13 Breast cancer is one of the most common cancers known, and it is also a significant cause of death in women. If breast cancer is diagnosed in the early stages of the disease and treated appropriately, we can see an increase in life expectancy for more than 90% of patients. Research on molecular biomarkers ... Read More Breast cancer is one of the most common cancers known, and it is also a significant cause of death in women. If breast cancer is diagnosed in the early stages of the disease and treated appropriately, we can see an increase in life expectancy for more than 90% of patients. Research on molecular biomarkers with enough sensitivity and specificity can be a good solution for rapid diagnosis in the clinical stage. Meanwhile, endogenous retroviral biomarkers can have good functional benefits. Human Endogenous Retroviruses as heterochromatin fragments of the genome usually lack expression, but in several types of human cancers, including breast cancer, HERV-Kenv mRNA is significantly increased. This study used RT-PCR to detect the expression of HERV-K mRNA and tried to introduce screening tools for the early detection of breast cancer. In this case-control study, blood samples of 50 patients with hospitalized breast cancer and 50 healthy individuals were designed to evaluate the expression of HERV-Kenv mRNA using specific primers and were analyzed by RT-PCR. PCR test was optimized as a positive control using Hela cancer cell line (cervical adenocarcinoma), which expresses the HERV-Kenv gene. Studies on both patient and control groups showed that the increase in mRNA expression was positive in 64% of patients with breast cancer and negative in all healthy individuals. The results indicate an increase in the expression of endogenous human retroviruses (HERVs) in breast cancer. Because the amount of HERV-Kenv mRNA in the blood of breast cancer patients increases dramatically, it is predicted that these mobile genetic elements could be used as a diagnostic biomarker. Original Article Cell, Organ and Tissue Culture Cytotoxic effect of diferuloylmethane, a derivative of turmeric on different human glioblastoma cell lines Ismael Bilal; Sijia Xie; Muna S Elburki; Zahra Aziziaram; Sangar Muhammad Ahmed; Salah Tofik Jalal Balaky Volume 1, Issue 1 , April 2021, Pages 14-22 Glioblastoma is a fatal brain tumor, and the standard treatment for this cancer is the surgical removal of the tumor followed by chemotherapy with temozolomide and radiotherapy. Because chemotherapy has many side effects, the use of compounds extracted from natural herbs, due to fewer side effects, can ... Read More Glioblastoma is a fatal brain tumor, and the standard treatment for this cancer is the surgical removal of the tumor followed by chemotherapy with temozolomide and radiotherapy. Because chemotherapy has many side effects, the use of compounds extracted from natural herbs, due to fewer side effects, can be a good alternative or supplement to chemical drugs in cancer treatment. In this study, curcumin (diferuloylmethane), known as the main active ingredient of turmeric, was used to evaluate itscytotoxicity on four human glioblastoma cell lines (U373, U251, D54, and T98G). Among these cell lines, U373 was temozolomide resistance, and T98G was photodynamic treatment resistance. These cell lines were treated with increasing concentrations of diferuloylmethane. Survival percentage was assessed by MTT assay and the trypan blue staining method was used to evaluate the rate of cell death and confirm the results of the MTT assay. The results showed that diferuloylmethane has a cytotoxic effect on U251, D54, and T98G cell lines. This effect was higher in high concentrations of diferuloylmethane on U251 and D54 than on U373. Therefore, according to the results of the current study and further studies, curcumin (diferuloylmethane) can be considered an effective complementary treatment in the treatment of glioblastoma. Original Article Gene Expression Studies Protective effects of curcumin against naproxen-induced mitochondrial dysfunction in rat kidney tissue Zahra Aziziaram; Ismael Bilal; Yuan Zhong; Azzadin Kamal Mahmod; Mohammad Reza Roshandel Volume 1, Issue 1 , April 2021, Pages 23-32 Naproxen is a common analgesic and antipyretic medication that is widely used around the world. This medicine at high doses leads to liver and kidney necrosis in humans and animals. The mechanism of kidney damage, unlike liver damage, is not well understood and is one of the most common causes of emergency ... Read More Naproxen is a common analgesic and antipyretic medication that is widely used around the world. This medicine at high doses leads to liver and kidney necrosis in humans and animals. The mechanism of kidney damage, unlike liver damage, is not well understood and is one of the most common causes of emergency department patients. Therefore, in the present study, the protective effect of curcumin, a compound derived from turmeric, was investigated on renal damage caused by naproxen. For this purpose, 25 male Wistar rats were selected and were randomly divided into five groups. Naproxen was dissolved in a 5% dimethyl sulfoxide (DMSO) solution and was injected intraperitoneally at 1000 mg/kg of animal weight. Also, curcumin was dissolved in 5% DMSO and was injected within peritoneum at a dose of 200 mg/kg of animal weight into the relevant groups. After 24 hours of injection, rats were bled and plasma urea and creatinine levels were measured. The rate of lipid peroxidation, the activity of superoxide dismutase and catalase in the kidney, total plasma antioxidant capacity, and PGC-1a gene expression were measured. The results showed that naproxen significantly increased the levels of biochemical markers of urea and creatinine in plasma and lipid peroxidation in the kidney; also, it decreased the activity of the antioxidants enzymes. The use of curcumin in naproxen-exposed groups significantly reduced the concentrations of urea, creatinine, and lipid peroxidation. Curcumin increased the activity of catalase, superoxide enzymes, and the total antioxidant capacity of plasma. Also, curcumin increased the expression of the PGC-1a gene, which reduces the effects of naproxen. Therefore, according to the current study results, curcumin could significantly reduce the harmful effects of naproxen on the kidneys. However, in future studies, the effect of curcumin should be evaluated on the naproxen mechanism in the treatment of those patients who need naproxen. Original Article Gene Expression Studies Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients Muhammed Furkan Ercisli; Gao Lechun; Sarhang Hasan Azeez; Rebwar Muhammad Hamasalih; Siyan Song; Zahra Aziziaram Volume 1, Issue 1 , April 2021, Pages 33-41 Rivaroxaban is an anticoagulant drug that prevents forming of blood clots. In addition, it can be administered to prevent and treat thrombotic diseases such as atrial fibrillation, cardiac arrhythmia, heart valve disease, orthopedic surgery, and thrombophilia to reduce the risk of thrombosis. Various ... Read More Rivaroxaban is an anticoagulant drug that prevents forming of blood clots. In addition, it can be administered to prevent and treat thrombotic diseases such as atrial fibrillation, cardiac arrhythmia, heart valve disease, orthopedic surgery, and thrombophilia to reduce the risk of thrombosis. Various factors such as age, gender, diet, medications, and genetic factors effectively determine the dose of rivaroxaban. Genetic variability in drug-metabolizing enzymes, including the cytochrome P450 (CYP450) enzymes and especially CYP3A4, has been associated with rivaroxaban response. The current study aimed to identify the frequency of CYP3A4 common polymorphisms, as well as their association with rivaroxaban response in 100 patients of Arab descent (48.6% female). CYP3A4 gene polymorphisms were examined by the PCR-RFLP method, and the findings were analyzed by SPSS 16 software and t-test. The frequency of CYP3A4*1B/*1B, CYP3A4*1B/*1A, CYP3A4*1B/*1C, and CYP3A4*1A/*1C was 67.35%, 10.64%, 19.12% and 2.89%, respectively. According to our results, CYP3A4 *1B/*1B genotype was the most common, and patients with CYP3A4*1B/*1B alleles needed a higher daily dose of rivaroxaban than *1B/*1A, *1B/*1C, and *1A/*1C carriers (9.57 ± 1.54 mg/day, P=0.015). Therefore, according to the results, CYP3A4 gene polymorphism has an important effect on the dose of rivaroxaban required to maintain the International Normalized Ratio (INR) in the range of 2-3. Original Article Cell, Organ and Tissue Culture Insulin-producing cells from bone marrow stem cells versus injectable insulin for the treatment of rats with type I diabetes Sarhang Hasan Azeez; Sarwar Nawzad Jafar; Zahra Aziziaram; Le Fang; Ahang Hasan Mawlood; Muhammed Furkan Ercisli Volume 1, Issue 1 , April 2021, Pages 42-51 Recently, stem cells have been considered renewable cell sources in the treatment of diabetes and the development of insulin-producing cells. In this regard, the current study aimed to compare Insulin-producing cells from bone marrow stem cells with injectable insulin in rats with type I diabetes. For ... Read More Recently, stem cells have been considered renewable cell sources in the treatment of diabetes and the development of insulin-producing cells. In this regard, the current study aimed to compare Insulin-producing cells from bone marrow stem cells with injectable insulin in rats with type I diabetes. For this purpose, 40 rats were divided into four groups: the control or healthy group, the diabetic control group, the group that received differentiated insulin-producing cells from bone marrow, and the group that received insulin treatment. To differentiate insulin-producing cells from bone marrow, the femoral bone marrow of rats was extracted using the flushing method. Differentiated cells were evaluated using dithizone-specific dye, anti-insulin-proinsulin antibodies, and anti-insulin beta receptors. Also, the expression of the pdx-I gene, as the specific gene of pancreatic cells, was examined by RT-PCR. The results showed that transplantation of insulin-producing cells could significantly increase blood insulin levels in diabetic rats. This increase intensified in the second stage of transplantation when more cells were injected into rats. Concerning decreasing blood sugar levels, differentiated cells were able to reduce blood sugar levels significantly. Even in the first stage of cell injection, in which the rats received a small number of cells, their blood sugar levels were controlled by these cells. As a result, the present study showed that repeated transplants of insulin-producing cells differentiated from bone marrow could decrease blood sugar and increase insulin levels. Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/issue_18998_18999_Issue%201.html

cc40

Volume & Issue: Volume 1, Issue 1, April 2021, Pages 1-51 (Cellular, Molecular and Biomedical Reports) Original Article Cell, Organ and Tissue Culture Neonatal Screening for Glucose-6-phosphate dehydr

en

Dr. Taher Al Ameri, Official Spokesman of the National Crisis and Emergency Management Authority (NCEMA), has announced the protocol for Eid al-Fitr, which covers prayers in the country’s mosques, along with precautionary measures to be implemented during this period. Dr. Al Ameri said the protocol stipulates the need to put up physical distancing stickers across the outdoor spaces surrounding mosques, along with the possibility of using parks and parking lots. He noted that, as per the protocol, mosques and prayer halls will open for the Eid al-Fitr prayers after the dawn prayers on Eid days, with speakers scheduled to announce the Eid takbeers half an hour before the Eid prayers begin. According to the protocol, the combined duration of prayers and Khutba (sermon) is set to 20 minutes, while the entry and exit of worshipers will be supervised by police patrols, volunteers and imams, to prevent overcrowding and maintain order. Worshippers must wear face masks at all times, maintain a physical distance of one metre and use personal or single-use worship mats, Dr. Al Ameri explained, noting that people are advised to avoid gatherings, handshakes and physical greetings, and opt for verbal greetings while maintaining physical distancing. "The protocol includes several conditions related to Eid al-Fitr celebrations, including the need to have an active green pass on the Al Hosn app and adhering to relevant precautionary measures, such as wearing face masks and practicing physical distancing, especially when sitting with vulnerable society segments, such as people of determination, the elderly and people with chronic diseases." "We urge the public to use electronic alternatives to distribute cash bonuses and gifts, and limit celebrations to immediate family members and relatives, as well as avoid physical greetings," Dr. Dr. Al Ameri congratulated the UAE’s leadership and people, as well as other Arab and Islamic countries, on the occasion of Eid al-Fitr, stressing that the UAE, thanks to its wise leadership and its concerted national efforts, has contained the spread of the COVID-19 pandemic through adopting a set of measures, including widespread testing, contact tracing, and utilising the latest treatment protocols. "The country is continuing to see a decline in COVID-19 cases, which is mainly due to the significant efforts of various authorities, led by the health sector. The UAE has made major strides in terms of recovery and return to normalcy, which can only be maintained through the public’s adherence [to preventive measures]," he stated. Relevant national sectors are continuing to monitor and assess local and international developments of the pandemic, in order to support decisions and achieve sustainable recovery, he said, noting that the country is continuing to update its protocols to protect the community’s safety and security, and achieve balance across all sectors. He also highlighted the importance of the community’s adherence to the guidelines issued by health and other authorities, as well as to the precautionary measures, urging the public to cooperate in order to ensure getting through Eid al-Fitr celebrations safely.

https://covid19.ncema.gov.ae/en/News/Details/2381

cc40

Dr. Taher Al Ameri, Official Spokesman of the National Crisis and Emergency Management Authority (NCEMA), has announced the protocol for Eid al-Fitr, which covers prayers in the country’s mosques, alo

en

COVID-19 media briefing affirms importance of following preventive measures during travels, holidays Dr. Taher Al Ameri, Official Spokesman of the National Crisis and Emergency Management Authority (NCEMA) highlighted the need for members of the community to adhere to the preventive measures adopted by the country during their travels and holidays and the necessity of following the precautionary measures implemented by relevant authorities amidst the spread of the COVID-19 pandemic in many countries. During the UAE Government media briefing on the COVID-19 pandemic, Al Ameri urged Emirati citizens and residents wishing to travel to verify the conditions and procedures of their destination countries to avoid violating regulations. He also pointed out that the UAE and all national sectors are keen to protect the health and safety of the entire community and limit the spread of the pandemic. The country is witnessing a steady decline in infections, which underscores the directives of the UAE’s leadership to harness all national capacities and capabilities to prioritise human health, he noted. The UAE has proven its success in managing the crisis through proactive steps and plans aimed at containing the pandemic and reducing its repercussions, he added, highlighting the success of the joint efforts between all national sectors nationwide. This harmony is due to the country's strategy to maintain a balance between various sectors to achieve sustainable recovery, Al Ameri said, stressing that relevant national authorities concerned with managing the pandemic are constantly upgrading their information and studying ways of reducing and preventing risks. "The response to the crisis is still ongoing, and we are relying on the community's awareness and adherence to the precautionary measures," he stated. The country’s ongoing success in responding to the pandemic is based on the community's awareness and adherence to relevant precautionary measures and their compliance with the instructions of official authorities, he added. He then expressed his pride for the Emirati community, which helped achieve recovery and return to normalcy.

https://covid19.ncema.gov.ae/en/News/Details/2383

cc40

COVID-19 media briefing affirms importance of following preventive measures during travels, holidays Dr. Taher Al Ameri, Official Spokesman of the National Crisis and Emergency Management Authority (N

en

Taher Al Ameri, Official Spokesman of the National Emergency Crisis and Disasters Management Authority (NCEMA), announced that the UAE Government media briefing on the COVID-19 pandemic will be stopped, not to be reinstated only if exceptional developments arise regarding the pandemic in the country. Dr. Fatma Al Attar, Official Spokesperson of the Ministry of Health and Prevention (MoHAP), said the transmission rate of monkeypox among humans is relatively low, noting that the first monkeypox case in the country has been detected, and the patient is receiving the necessary medical treatment. Dr. Al Attar stressed that for over two years, the UAE has exerted significant efforts to protect the community's health and safety, by supporting the health sector and its qualified human resources, as well as providing all necessary medical resources to address the repercussions of the COVID-19 pandemic. She added that the health sector's efforts have enhanced the UAE’s positive reputation as a leading model of addressing challenges that affect the health sector, proving its ability to address such challenges with full efficiency. MoHAP announced the detection of the country’s first monkeypox case, a woman who came from abroad, she further added, noting that the patient is receiving the necessary medical treatment, and affirming that monkeypox is a rare disease of animal origin that has been spreading around West and Central Africa since the 1950s. She also explained that the clinical symptoms of infection with the monkeypox virus are rash, extreme fatigue, swollen lymph nodes and severe headache that usually begin within one to three days of the onset of fever, noting that the interval between infection and the first symptoms is usually between five and 21 days. Dr. Al Attar said everyone should undertake the necessary health procedures to reduce the risk of infection by any virus, in order to protect the health and safety of the community, as well as adhere to relevant precautionary measures. It is important to maintain personal hygiene, not exchange personal items with others, and avoid shaking hands with anyone who has skin problems, she stressed, highlighting the fact that after the detection of the first monkeypox case, all national health authorities are assessing the situation to ensure their readiness. She also underscored the importance of getting health information from official sources and avoiding the circulation of rumours. Dr. Al Ameri said the UAE has accomplished many successes in the process of achieving recovery, due to the vision of the country's leadership, stating, "This proactive strategy has supported the efforts of all local and national authorities, as well as public and private authorities." "We urge the public to adhere to the precautionary measures, and we would like to remind you of the mandatory use of face masks and quarantining upon infection," he added, noting that protecting current achievements and ensuring the continuity of the new normalcy are priorities that require everyone to commit to the precautionary measures. "In light of the achieved recovery indicators, we are responsible for protecting the community’s safety. After close national monitoring, we have accomplished many achievements related to containing the pandemic, including distributing safe vaccines to all segments of the community, with 98 percent receiving vaccines free of charge, leading to a decline in cases and deaths," he further said. "The regular media briefing of the UAE Government will stop from today, but it will be held again under exceptional circumstances based on the situation regarding the pandemic," Dr. Al Ameri said in conclusion.

https://covid19.ncema.gov.ae/en/News/Details/2384

cc40

Taher Al Ameri, Official Spokesman of the National Emergency Crisis and Disasters Management Authority (NCEMA), announced that the UAE Government media briefing on the COVID-19 pandemic will be stoppe

en

The UAE has achieved the desired goal of the National COVID-19 Vaccination Campaign and announced the completion of 100 percent vaccination and immunisation of the target groups in the country. The campaign aimed to vaccinate and immunise frontliners, volunteers, community members of the age groups specified according to the type of vaccine, the elderly and individuals with chronic diseases whose health condition allows them to take the vaccine. The UAE, through the Ministry of Health and Prevention, worked to provide the COVID-19 vaccine to all society members to reach the acquired immunity resulting from "vaccination and immunisation for individuals," which in turn reduces the number of cases and control the spread of the virus. The desired percentage was achieved by providing the vaccine across all health centres for all members of society, in addition to booster doses and various approved types of vaccines that have proven their efficiency in combating the virus.

https://covid19.ncema.gov.ae/en/News/Details/2385

cc40

The UAE has achieved the desired goal of the National COVID-19 Vaccination Campaign and announced the completion of 100 percent vaccination and immunisation of the target groups in the country. The ca

en

Dr. Taher Al Ameri, Official Spokesperson of the National Emergency Crisis and Disasters Management Authority (NCEMA), today announced an update to the green pass system on the Al Hosn app, reducing its validity period from 30 days to 14 days. The update will be applied to all categories from Wednesday, 15th June, 2022, except for workers in the education sector and students, for whom the decision will be applied on Monday, 20 June, 2022, due to the examination period, he said, stressing that the verification process will be tightened in all places that use the Al Hosn app. "The national system, since the start of the crisis, has been able to monitor the pandemic both locally and globally, and many COVID-19 cases were detected around the world," Al Ameri said, noting that recently, an increase in COVID-19 infections around the country has been detected, along with rising hospitalisation rates, and the number of cases increased by over 100 percent in one week. This increase comes after the situation has stabilised around the country, through supporting national efforts and encouraging community cooperation, he added, affirming that recently, a number of practices that pose risks to the community and public health have been witnessed, in light of non-adherence to the precautionary measures. Al Ameri stressed that research studies have proven that wearing face masks is one of the most important factors in maintaining health and safety and preventing the risk of infection with COVID-19, and are effective in reducing the rate of spread and viral load of the disease, especially in closed and crowded areas. He then noted that various segments of the community have recently shown negligence in adhering to wearing face masks in closed areas, adding that wearing masks in closed areas is mandatory and violators will be punished with a fine of up to AED3,000, according to Public Prosecution Decision No.38 for 2020. "A lack of commitment to isolating was noted among a small group of people infected with COVID-19, which threatens the safety of the community and causes the spread of the virus, due to the lack of commitment of people," Al Ameri stated, noting that such practices will be subject to legal action. "Our frontline defenders in the UAE have been working nonstop for two years, and due to their efforts, the country has contained the pandemic and achieved recovery," he stressed, noting that complying with the precautionary measures, as well as failing to meet the social role of maintaining public health and acquired immunity, has resulted in a rise in infections and new waves of the virus. He then urged the public to comply with relevant precautionary measures, including wearing face masks in closed areas, avoiding crowded places and being cautious while travelling, as well as undertaking regular tests. At the end of the briefing, Al Ameri highlighted the importance of the commitment of members of the community, following the instructions of health and relevant authorities, and adhering to relevant precautionary measures.

https://covid19.ncema.gov.ae/en/News/Details/2386

cc40

Dr. Taher Al Ameri, Official Spokesperson of the National Emergency Crisis and Disasters Management Authority (NCEMA), today announced an update to the green pass system on the Al Hosn app, reducing i

en

The Berlin hackathon 2012 brought a record number of people together who worked together on many technical issues. Some people came to learn about MediaWiki, some came to learn about the finer points of Git and Gerrit. The great thing about MediaWiki hackathons is that typically there is a great mix of knowledgeable people, talented people and people who can explain and help with difficult technical issues. It is also where new technologies are previewed, this time it was Lua who was getting a lot of the limelight. It is with pleasure to share with you with what theDJ has to say in answer to questions about the hackathon and Lua. What is the attraction of a hackathon and, what was special about Berlin 2012 For me as a volunteer the benefit of such an event is twofold. The first part is of course getting to know the people that you usually only interact with online. It’s just more fun and the connections you build are simply stronger. It often also helps you in your future online communications with these people. When you know people in person you also tend to communicate better online. The other reason is that it is a great way to do learning, brainstorming, rapid prototyping and getting questions asked and answered efficiently. Nothing beats being in the same room when discussing or working on a topic. There were several themes in the presentations and workshops … you chose Lua, what is Lua and what is its relevance The complexity of pages is actually one of our biggest performance issues right now and the [[en:Barack Obama]] page is a well known example of that. After an edit of that page it often takes well over 20 seconds for the server to render the page again. This is creating a huge resource load on the server and it is confusing the editors because it seems like the server is not responding to their edits. The complexity is caused by two things you can use in pages: templates and parser functions. The performance of these elements is shaky, for a large part because our inventive MediaWiki users have found ingenious yet complex forms of working around the limited functionality these two elements provide. Ideally much of the functionality would be converted in PHP MediaWiki extensions, but that development path is much slower and less accessible for MediaWiki users. For years there have been discussions in the developer community on how to tackle this problem, but a more clear consensus is starting to form now. The idea is to move away from the old templates and parserfunctions combination and replace much of it with a new type of code named Lua, which is still accessible for users, much more capable than templates and parser functions  yet much easier than PHP extensions. Overall Lua has the promise of a much higher performance and flexibility compared to templates and parserfunctions, yet will allow us to have the same type of safeguarding at the serverside that is so important for a major website like Wikipedia. When Lua is scheduled for 2013, why all this attention now Exactly because it is not yet deployed yet. Right now we can still make significant changes easily without causing too much trouble for users. But to know what changes are needed, you do need to use the system and learn from that usage. By engaging the developer community to experiment with writing templates and converting templates, we can find issues that are still outstanding or that were simply never anticipated when implementing the system, before it goes into wider deployment. Simply said, because the existing templates and parser functions that are in use right now on all these different MediaWiki’s are so complicated. It will take years to replace all the code, so in order to reap the benefits as soon as possible, you will want to tackle the most complex code that currently performs the worst early on in the conversion. You have been converting the “coordinates” template, what is its attraction The “Coord” template is a real life example of a template with high complexity that is used on tens of thousands of pages. Exactly the type that in theory should benefit greatly from conversion to Lua. At the same time it is still ‘small’ enough to actually get done within a reasonable amount of time. The process of converting it instead of writing something from ‘scratch’ will likely mimic the way users will start when using the new Lua capabilities and was therefore important to test. I have currently spent about 9 hours on it, and am probably about half way the conversion. After doing a full conversion I would like to benchmark the difference between the two implementations so we can further validate our suspicions of the real world benefits of this new Lua method. A partial conversion of the template seems to have already sped it up by at least 4x in my preliminary assessments. How will this functionality become available on the other 270+ Wikipedias Lua is now available on Wikimedia labs for testing and this will be followed by gradually adding mediawiki.org and other ‘low priority” production sites. There are still major parts of the extension that require attention before it is ready for a general release. In terms of the scripts themselves the users will probably start with the most resource ‘expensive’ templates on English Wikipedia and slowly work their way trough at every time trying to keep everything as compatible with the old systems as needed. Should we not implement the lessons of “Gadgets 2.0” and share them from a central site ? I think having a centralized Lua module repository, similar to the central Gadget repository for Javascript that we will soon have, is something we should definitely consider. Past experiences with scripts developed by users has taught us that it is a maintenance hell because people fork and adapt the code for every single wiki. Though most of those copies are 95% the same code, they are not actually the same script and if you want to change something to them, you need to either go trough 270 wiki’s or people invest valuable time into fixing a problem that someone else has already fixed at another wiki. For the lua modules I think it is very important to be able to share that 95% of code that will be the same on all the wiki’s. This is currently not yet possible, but has been discussed about. It is my opinion that we really need to get that working before a 2013 full deploy. Several people were hacking Lua code, even more people attended the workshop, what is the most relevant thing for them to do moving forward Provide feedback based on their experiences. As I see it, this is a learning stage and as a group we can only take all lessons into account if we share what each and everyone has learned. You identified two parts to converting templates to Lua, the conversion itself and optimisation. How relevant will optimisation be? As I said earlier, the users have found ingenious but complex ways around the limitations of templates and parser functions. A conversion is about changing from one language to the other, without change HOW the code works. This conversion will probably already provide large speed gains. Optimizing is about getting rid of all the weird constructs that we used because we worked around the limitations of templates and parser functions. These constructs are no longer required and will actually slow down the Lua script, so you will want to remove them. You use Lua in your day job. In what way is Lua for MediaWiki different from the Lua that you know? Not so much actually. Of course there is the interface towards MediaWiki which is different from the interface that I work with (an interface to write mobile applications) but the language is exactly the same. It could have been the first question, what benefit will Lua bring us It will speed up pages, but make it possible to do even more advanced templating. At the same time it will look a bit less scary to editors, and will create more readable code that is easier to maintain. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in TechnologyTagged Hackathon, interview, lua, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/07/02/lua-previewed/

cc40

The Berlin hackathon 2012 brought a record number of people together who worked together on many technical issues. Some people came to learn about MediaWiki, some came to learn about the finer points

en

Three decades ago, in a buy-sell-trade bookshop in Plattsburgh, New York, I came across a two-volume set of collected Poems published in 1916. Unfamiliar with the poet but intrigued by a platinum print photograph of a woman pasted inside the front board of volume one (above), I purchased the set for $2.50 and went home. For nearly two decades I wondered over the identity of the woman, and came to find—through an internet search—that it was the poet herself, Florence Earle Coates. Mystery solved. But I would not be satisfied with this knowledge alone. It was merely the beginning of a dedicated search into the life and times of a woman who had become my muse. Scant information was initially available on the poet. It appeared that her thoughtful, finely crafted works of poetry were important in her day—in her circles—but perhaps had not survived a supposed “renascence [sic] of poetry” or test of time. I resolved to remedy this by bringing her works back to life, but was at a loss as to how to do so until one of my children informed me that they had “edited” the Dr. Pepper article at Wikipedia. This planted a seed which would germinate a couple years later in 2009, when I created Mrs. Coates’ article at Wikipedia and author page at Wikisource—gradually adding all of her volumes of poetry over the span of about two years. But my activity did not stop there. To quote another contributor, “the power and potential of [Wikisource] is mind-blowing”: where one work refers to another (via wikilinking), thereby contributing to the “great conversation.” One author, one book leads to another author, another book—another idea. Seeing a work to its completion is a satisfying thing, but the process is perhaps even more rewarding. Word by word, line by line, page by page, proofreading is an active and learning process, as no two works are formatted alike. When necessary, there is no shortage of help from other contributors. Each offers different abilities, gifts and perspectives to the site, and I find most are eager and willing to share their unique insights and skills. You get out of proofreading what you put into it. Coates writes, “Great symphonies require more than one hearing; great poems more than one reading.” It is beneficial to first proofread and then re-read, thus ensuring the accuracy of editing, if not the cultivation of the mind. I developed anxiety following an illness a few years ago, and found proofreading to be a helpful stress reducer. One can develop a rather relaxing rhythm to editing poetry, particularly when proofreading longer works such as The Prelude by William Wordsworth:[1] “Now here, now there, moved by the straggling wind, Came ever and anon a breath-like sound, Quick as the pantings of the faithful dog, The off and on companion of my walk; And such, at times, believing them to be, I turned my head to look if he were there; Then into solemn thought I passed once more…” I use this passage to illustrate how proofreading such poetry, for me, is much like walking in step to the cadence of the panting of a faithful dog—it can be a very relaxing bit of mental exercise; but a word of warning: one must be careful to maintain focus and not become overly transfixed by the rhythmic pattern or fall into reverie too often during proofreading otherwise OCR errors and typos will be overlooked! I owe much to the works of Mrs. Coates, for her poetry sings of hope and joy, beauty and the ideal. But I am also thankful to Wikisource and its welcoming community for providing a space to showcase her poetry—and to my family, who has tolerated this editing hobby of mine. I received the following after posting some of Mrs. Coates’ poetry (on loss, grief and immortality) to another website: “Thanks for sharing these poems. I love her perspective on the human condition. I’d never heard of Coates before, but I’ll never forget her now.” My reply to the gentleman included a line from Coates’ “Deathless Death,” which states “no good, once given, can be lost.” I shared the same words a few years back with a woman whose son had died. She spoke of her son’s goodness, and the life-affirming words came to mind. This in a nutshell is why I proofread poetry. It is the stuff of the soul; it speaks to the body, the mind, and the spirit alike. In the words of Mrs. Coates, “poetry in some form is necessary to all—save, perhaps, to those who are content to live upon bread alone.” Autograph verse of “Poetry” by Florence Earle Coates. Subsequently published as “To the Muse.” Scan, public domain/CC0. [1] Florence Earle Coates wrote a poem about Wordsworth entitled “Breathless We Strive.”. “Why I …” is a new ongoing series for the Wikimedia Blog. We want to hear what motivates you to contribute to Wikimedia sites: send us an email at blogteam[at]wikimedia[dot]org if you know of someone who wants to share their story about what gets them to write articles, take photographs, proofread transcriptions, and beyond. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Very nicely explained. Sonja, you continue to excel in writing. Very dedicated. Our top posts of 2016: Wikimedia community takes center stage – Wikimedia Blog […] them to contribute to Wikimedia sites. This post is best exemplified by Sonja N Bohm’s “Why I proofread poetry at Wikisource,” where her journey to the site was motivated by bringing a single little-known poet’s […] Posted in Community, Profiles, Why I series, WikisourceTagged community, editor, Florence Earle Coates, poetry, proofread, Wikimedia, Wikimedia Blog (EN Archive), wikisource Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2016/06/02/why-i-proofread-poetry-wikisource/

cc40

Three decades ago, in a buy-sell-trade bookshop in Plattsburgh, New York, I came across a two-volume set of collected Poems published in 1916. Unfamiliar with the poet but intrigued by a platinum prin

en

This #Wiktionary screen shot shows the first iteration of the language support that will be brought to MediaWiki by the Wikimedia Localisation team. It makes it possible for people with a standard US keyboard to emulate a keyboard appropriate for their language. Narayam, the MediaWiki extension, was originally conceived by JunaidPV and has been further developed to provide keyboards for many more languages. Particularly the people who use the languages from India will benefit. Many different scripts are in use but many computers do not have an appropriate keyboard for the many different languages. Now that Narayam is live on some wikis, we will gain the experience necessary before it will go live on other projects and for other languages. When it works well, external tools like the ones shown on the Sanskrit Wiktionary can be phased out as well. At translatewiki.net you will find keyboard methods for many more languages. Please try them out and, when you cannot find a keyboard method for your language, you may discuss within your community if Narayam can be beneficial for your language. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Wikimedia blog » Blog Archive » Wikimedia engineering September 2011 report […] Major progress by our new Internationalization & localization team; […] Posted in Features, Internationalization and localization, TechnologyTagged India, language support, localization, MediaWiki, Sanskrit, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2011/09/14/the-l10n-team-brings-you-input-methods/

cc40

This #Wiktionary screen shot shows the first iteration of the language support that will be brought to MediaWiki by the Wikimedia Localisation team. It makes it possible for people with a standard US

en

santhosh committed rECTX1114ce312f24: Migrate to JSON configuration based extension registration (authored by santhosh).Jun 19 2015, 4:39 AM2015-06-19 04:39:56 (UTC+0) Legoktm mentioned this in T104255: Array to string conversion in HTMLFeatureField.Jun 29 2015, 10:05 PM2015-06-29 22:05:24 (UTC+0) Legoktm mentioned this in rECTX6421ee2a4bd9: BetaFeatures browser blacklist is an object.Jun 30 2015, 3:57 AM2015-06-30 03:57:11 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/rECTX1114ce312f24f4a88e170e6d4ce2d75eb940fcce

cc40

santhosh committed rECTX1114ce312f24: Migrate to JSON configuration based extension registration (authored by santhosh).Jun 19 2015, 4:39 AM2015-06-19 04:39:56 (UTC+0) Legoktm mentioned this in T10425

en

Learnings from the events that presented the Wikimedia to heritage professionals in Argentina, Mexico, and Chile, while testing the Add an image feature on Wikipedia This blog post is Part II. Find here the Part I, with the GLAM & Culture team and Wikimedia Argentina’s perspectives. My own history as a Wikipedian goes back more than a decade ago. The idea of contributing to a collaborative project was alluring and the markup language was way easier than keeping track of HTML tags. As a newbie editor, it felt overwhelming having to keep track of so many things at once: when should I use italics and when should I bold text? What information goes in the citation template? What was the code for displaying an image again? Slowly but surely, I made my share of mistakes and learned bit by bit the intricacies of Wikipedia so that they became sort of a second nature. When I joined Wikimedia Mexico back in 2013–14 we hosted monthly edit workshops for beginners. Anyone could come and learn how to contribute to Wikipedia: the space loaned laptops for basic editing and we could be there to teach in real-time, new editors could express their questions and get an answer in almost no time at all from an experienced Wikipedian. I felt a special kind of pride when I was asked to step up to the plate and be the host; it meant that I was trusted as having both technical skills and social grace to help newcomers. Many of our long-time local Wikipedians learned in those workshops. Back then we – and most other chapters – identified that Wikipedia would grow by bringing in people with knowledge to contribute (i.e. most everyone) and have them overcome the technical barriers to bring that knowledge to Wikipedia and the world at large. Our editathons often had people exhausted by trying to learn what I learned – markup language, style – in a single afternoon. To this day, I admire all those people who taught us so much about how to teach. As time passed, it became clear that the technical challenge of newbies on Wikipedia was actually twofold: Teaching new editors – through workshops, assisted editing, and tutorials – so that they could pass over the technical barriers, and Bringing down the technical barrier as much as possible so that contributing is easier, for new and seasoned editors alike. For the most part, we could only directly address the first of those, while the second asked us to get creative – like asking editors to write in a familiar text processor – without explicitly getting a solution. Fortunately, things have changed. New tools inside Wikipedia have helped enormously to assist users in getting their knowledge and expertise into the largest collaborative effort the world has ever seen. There’s one thing that I like to emphasize when teaching new editors: just as actors say that “there are no small roles“, so it is that there are no “small edits” on Wikipedia. Some people do contribute through writing extensive articles, but that’s not the only way to contribute. Correcting typos, rewording unclear phrases, clarifying minute details and even formatting are critical tasks to make an article the best it can be. These “small” tasks are also ideal for a new user to try out their editing powers. I’ve witnessed first-hand just how much it means to many people to see their contribution live with only a few clicks. My intuition tells me people who see how easy it is to contribute are encouraged to contribute more. So you’ll understand my excitement when I was asked to help try out a new feature aimed at new editors: an AI-powered image suggestion tool. Images are a critical part of most articles, but finding them in Commons is sometimes tricky, not to mention the fact that it requires navigating a whole different wiki – a concept that is not always easy to convey. This tool, as mentioned, is meant to be used first and foremost by new editors, so we were presented with a new challenge: in Mexico, we’ve worked with several museums, universities, government dependencies, and non-profits in the past, so much that many of their workers are no longer considered “new to Wikipedia”: and an otherwise great achievement to celebrate, but not a good fit for this and only this particular situation. The solution, then, was obvious: this was an opportunity to connect with new people and new institutions. We reached out to Mexicana – an open repository of Mexican Cultural heritage – and the Secretariat of Culture (enwiki) to help us get the word out: we’ve worked with both institutions before and we knew there’s still more to do. The response was amazing. We received over 100 sign-ups, coming from various institutions across the country: UNAM – The National Autonomous University of Mexico and the oldest university in the Americas; ENCRyM – National School of Conservation, Restoration and Museography; ENAH – National School of Anthropology and History; Public universities (University of Guadalajara, Autonomous University of Tabasco, Autonomous University of Aguascalientes, Universidad Vizcaya de las Américas); Public libraries (National Library of Mexico, Amado Nervo Community Public Library, Prof. Ma. Ignacia Martínez de Loza Community Library, Azcapotzalco Borough, Tulancingo Municipality). Testing Add an image We held the workshop on April 1, 2022, before a group of mixed ages and professions, but equally enthusiastic to try and see how images are important to Wikipedia and how they could contribute. As with previous events, we started with a short introduction to the Wikimedia Foundation and the work of Wikimedia Mexico regarding cultural heritage and GLAM. Following that, Cora Garmanik gave us a brief and very interesting lecture on how images are connected – and should be connected – with its proper context; using examples from recent Mexican history (in 1994–95). We took a small break and delved right down to add images using the tool. Yours truly gave a small introduction on what Add an image is, how it works and what it is supposed to replace. But as always, merely watching how something is done is merely the beginning; so we split into three groups to try the tool for ourselves. As is natural, we all started having questions. We worked together on finding articles to improve, navigating the article itself, opening images on Commons to read metadata, adding the image, adding an image description, and saving the article. As is natural, going through a few bumps here and there helped us learn. Asking questions of each other helped us cement knowledge, boldly editing in the knowledge that mistakes can be corrected. Lessons learned and questions for the future Our last activity before closing the event was to gather everyone’s thoughts and feelings, as well as a first round of feedback. The participants were generally happy, not only to learn how the proverbial sausage is made, but also to learn just how much work happens behind Wikipedia. Seeing their own work helped us all reflect on just how much effort goes into the pages that we all read every day to check a quick fact. Of course, this was a group of intelligent people, and they shared their observations about Add an image as a feature. Summarizing their comments: Some of them felt “frustration” at having only one image suggestion per article. Of course, for many of these articles, there’s most likely another candidate image on Commons, but the tool allowed only one suggestion, and if it’s deemed not appropriate for the article the only other option is to move to a new article. Several users wished to stay on the same article to try and see if they could improve this article instead of having to return to “square one” (i.e. finding and selecting an article to improve). On occasions, the suggested image was only very tangentially related to the article. For instance, it would suggest a picture of a place on an article about a person – sometimes their place of birth or final resting place. When selecting a category for article suggestions, the list of articles is always in the same order. In most cases, this is not a concern, but during a collective editing event, it meant that most users selected articles near the beginning of the list and, thus, we experienced several edit conflicts, when two users tried adding to the same article at almost the same time. Despite these concerns, participants were eager to learn more and keep editing. In general, their hopes and wishes for the future were: Learning how to contribute to Commons: both as individuals and as institutions. This activity led many to re-think the importance of preserving cultural heritage through images, and many were eager to learn how to improve articles through the donation of images. Learning how to improve an article’s text: the bread-and-butter of all Wikipedians. Many of the participants saw the adding of images as only the first step in improving articles. Having a positive first experience led them further down the Wikipedian pipeline Staying in touch with the local chapter: Most participants didn’t know the work made in concert between Wikimedia Mexico and local institutions. They were amazed at the potential to work on improving content related to culture… Potential for education: Several of the participants, we found out, are also teachers and lecturers and so they wondered if there was some way to incorporate what they had just learned into their syllabus and schools. We were glad to say that Wikimedia Mexico does have an Education program and the only reason why it wasn’t mentioned was a lack of time for this event. These users wondered if Wikipedia could somehow be integrated into their educational practice (the answer to which is obviously yes) Poster for the Chilean event The geographical coordinates of Chile tend to wall its history under the limits of the desert, the mountain range, and the ocean. However, the media boom that the country has reached in this digital age and the effervescence of the active social movements that have emerged since 2019, played – also – a key role in the Chilean session of #1Pic1Article. Thus, contrary to expectations, editors from different provinces in Chile (Santiago, Iquique, Curacaví, and Quillota) attended the session, as well as collaborators from Argentina (Buenos Aires), Colombia (Bogotá), Mexico (Mexico City and Tuxtla Gutiérrez), and Peru (Lima and San Juan de Lurigancho) also participated in this activity. This total participation, enriched by Latin American identities, covered a distance of more than 6,500 km and allowed for 60 editions on the day of the event, which continued to grow until reaching 151 editions in a total of 110 articles. The opportunity to bring together professionals from the cultural and heritage sectors from five different countries contributed to highlighting the regional interest present for Wikipedia and registering that, those from vastly different fields of knowledge (Art, Education, Library Science, Anthropology, Museology, Cultural management, Teaching, etc.), see in the Wikimedia community an opportunity to expand their networks and to enhance their public and professional outreach. Within the universe of attendees, we are happy to say that 70% had not participated in any previous activity, and therefore, the experiences shared by Patricia Díaz Rubio (Executive Director of Wikimedia Chile) and Giovanna Fontenelle (Program Officer, GLAM and Culture, Wikimedia Foundation) were a stimulus that broadened the gaze on all the hidden and intertwined possibilities within the largest encyclopedia in the world. The occasion led to a proposal of analyzing images as a form of a situational exercise, with a corporality and a territoriality fostered in and with the images. Thus, Cora Gamarnik (Social communicator and specialist in photojournalism) hit the nail on the head when using an image of the social protests carried out in the context of the Chilean dictatorship since 1973, contrasting their evolution in popular, editorial, and even musical culture. This allowed us to perceive how images carry a message of time, politics, use, and potential that radiates according to the context and the references that we want to give them – and also deny them. The session continued to test the Add an image feature, where the group was able to realize how agile and simple it was to cross and see the compatibility between the textual resources (which were already available) and their connected access to Wikimedia Commons. Here, as in any learning process, with hits and misses, we saw that – sometimes – the proposed topics were not limited or delimited as we would have liked, but that some links were so expansive, that they made us doubt the true connections and notice how important the source metadata were, to specify the categories and encourage inclusion. Also, language emerged as a difficulty, because, although we were working with Spanish, proposals from other languages appeared, such as German and Arabic, which made our choices difficult. Finally, already recognizing the desire to make available more new images and imaginaries for the entire population, we would have liked to have a range of possibilities, as well as a carousel of images where we could compare, cut, highlight, or indicate the explicit reference of why such image was necessary for such an article. Without a doubt, having had the opportunity to hold the last workshop, in the last country of the southern cone, favored the accumulation of experiences and the desire to continue building visual culture. The subsequent contacts and connections that were generated with different people and institutions that wished to maintain a close relationship between the Wikimedia community, Education, and Digital Culture are proof of this. Find here the Part I, with the GLAM & Culture team and Wikimedia Argentina’s perspectives. Comments are closed automatically after 21 days. Posted in Events, Events, GLAM, Growth, Partnerships & EventsTagged GLAM, GLAM-Wiki, Growth, Newcomer experience pilot, Wikimedia Argentina, Wikimedia Chile, Wikimedia México, Wikimedia Mexico Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2022/06/21/1pic1article-ii-how-latin-american-heritage-experts-added-images-to-wikipedia/

cc40

Learnings from the events that presented the Wikimedia to heritage professionals in Argentina, Mexico, and Chile, while testing the Add an image feature on Wikipedia This blog post is Part II. Find he

en

The launch of an alpha, opt-in version of the VisualEditor to the English Wikipedia, a project more complex than it appears; A research study on the use of the Article Feedback feature; New metrics for the MediaWiki community; The start of the Outreach Program for Women; Continued work to improve the workflow and interface for translators. Note: We’re also proposing a shorter, simpler and translatable version of this report that does not assume specialized technical knowledge. 113 unique committers contributed patchsets of code to MediaWiki. The total number of unresolved commits went from about 535 to about 648. About 39 shell requests were processed. Wikimedia Labs now hosts 148 projects, 847 users; to date 1378 instances have been created. Detailed community metrics are also available. Are you looking to work for Wikimedia? We have a lot of hiring coming up, and we really love talking to active community members about these roles. Software Engineer – Visual Editor Software Engineer – Editor Engagement Git and Gerrit software development (Contract) Matthew Flaschen joined the Wikimedia Features engineering team as Features Engineer (announcement). Mike Wang joined the Operations team as part time Labs Ops Engineer (consultant) (announcement). The Technical Operations team continued to work on completing the outstanding migration tasks, and to ready our Ashburn infrastructure for the big switchover day, i.e., the complete transition from the Tampa datacenter to the one in Ashburn, on the week of January 22, 2013. In the past few months, we’ve transitioned services from the Tampa datacenter to the one in Ashburn, which now serves most of our traffic (about 90%). However, application (MediaWiki), memcached and database systems are all still running exclusively out of Tampa. We have been working to upgrade the technologies and set up those systems at Ashburn, and we plan to perform the switchover of those services from Tampa to Ashburn in the coming weeks. This will provide us some assurance of a hot standby datacenter, should we encounter an irrecoverable and lengthy outage in one of the main datacenters. Because December is when the annual Wikimedia fundraiser happens, the Operations team usually makes fewer site infrastructure changes to mitigate the risks of causing outages. Some of the lesser-risk work performed include deploying the new Parsoid cluster to support the Visual Editor project, rolling out doc.wikimedia.org (our auto-generated puppet documentation), using a new and unified SSL certificate for *wikipedia.org and *.m.wikipedia.org sites, and setting up a monitoring server and service in Ashburn. Asher Feldman migrated one of the main production slave database server (db59) for the English Wikipedia (enwiki) to MariaDB 5.5.28. He has been testing 5.5.27 on the primary research slave, and on the current build on a slave in Ashburn. Taking the times of 100% of all queries over regular sample windows, the average query time across all enwiki slave queries is about 8% faster with MariaDB compared to our production build of MySQL 5.1-fb. Some queries types are 10–15% faster, some are 3% slower, and nothing looks aberrant beyond those bounds. Overall throughput as measured by qps has generally been improved by 2–10%. Asher wouldn’t draw any conclusions from this data yet: more testing is needed to filter out noise, but initial results are positive. The main reason for migrating to MariaDB is not performance, but rather by the belief that it’s in the Wikimedia Foundation’s and the open-source communities’ interest to coalesce around the MariaDB Foundation as the best route to ensuring a truly open and well-supported future for MySQL-derived database technology. Mark Bergsma and Faidon Liambotis have made tremendous progress in testing and deploying Ceph in Ashburn. We are hopeful it will be robust and scalable. Ryan Lane has been writing a new deployment system using git and Saltstack. Parsoid is currently being deployed with this system, and MediaWiki is slated to use it for its next major deployment. There were no major changes on the fundraising infrastructure because of the fundraiser itself. We ordered and received bastion hosts that we’re in the process of deploying. Monitoring got an overhaul and we’re now sending alerts to the fundraising technical staff or the technical operations team depending on what triggered the alert. A tool for dump users to set up interwiki links on their local mirrors is available in alpha, as well as documentation of the interwiki cdb file. Also, work with WanSecurity on mirroring is moving forward: they now hold a current copy of all ‘other’ files, including page views and Picture of the Year bundles, among other things. Labs came out of beta this month, following the opening of self-registration. Another major change this month was the migration from the shared NFS instance to per-project glusterfs volumes. A number of smaller changes were made, including: the Addition of puppet documentation links from classes and variables on the instance configuration pages; the modification of the project filter to act as a table of contents; a split of LDAP project groups into projects and POSIX groups; and the installation of Saltstack on all instances to act as a guest agent. Editor retention: Editing tools In December, the team deployed to the English Wikipedia an alpha version of the VisualEditor for editors to use and give feedback on issues and priorities. The team’s work focussed on ensuring that the integration was reliable, and providing a dedicated tool for editors to report problems with editing, and, after deployment, addressing the reports and ideas from editors. The early version of the VisualEditor on mediawiki.org was also updated to use the new developments (as part of 1.21-wmf6). The Parsoid project reached a major milestone with its first deployment to the English Wikipedia along with the VisualEditor. This was a major test for Parsoid, as it needed to handle the full range of arbitrary and complex existing wiki content including templates, tables and extensions for the first time. As witnessed by the clean edit diffs, Parsoid passed this test with flying colors. This represents very hard work by the team (Gabriel Wicke, Subramanya Sastry and Mark Holmquist) on automated round-trip testing and the completion of a selective serialization strategy just in time for the release. After catching their breath, the team now has its sights on the next phase in Parsoid development. This includes a longer-term strategy for the integration of Parsoid and HTML DOM into MediaWiki, performance improvements and better support for complex features of wikitext. This month, the team continued to develop key features of the Notifications project (code-named ‘Echo’), and deployed a first experimental release on mediawiki.org. Fabrice Florin expanded feature requirements for this release, and Vibha Bamba designed more components of the user experience. Ryan Kaldari and Benny Situ developed improved notification flyouts and email digests, as well as new notifications such as page links. Luke Welling built an HTML email module, which will soon be available to other projects as well. We plan to develop more features this month and deploy them for new editors on the English Wikipedia in early 2013. Please help us test these new features to provide feedback and find bugs. We’re also looking to hire a software engineer as part of this project. We made good progress on Article Feedback version 5 this month. We completed a research study on the English Wikipedia, confirming that many readers use this feature and a sizable number of them go on to register and become editors. Based on that research and editor suggestions, we started development on new features to reduce the editor workload through better filters and simpler moderation tools. We also continued to refactor our code, to support millions of comments on a dedicated database cluster to be deployed in coming months. Once this work is complete, we plan to release Article Feedback v5 to 100% of the English Wikipedia in March, and to other Wikimedia sites later this year. The German Wikipedia has already started a pilot to evaluate this tool, and a similar initiative is also under discussion on the French Wikipedia. Page Curation is now in ‘maintenance mode’, following its release on the English Wikipedia in September 2012. There was no significant development activity on this project this month. Oliver Keyes has completed a project to look at various ways of localizing Page Curation to any and all wikis that want it: it is currently being reviewed by Howie Fung to assess its feasibility. In December, the Editor Engagement Experiments team launched a new test aimed at Onboarding new Wikipedians. This interface delivers an optimized task list immediately after sign up, inviting those without an idea of how to get started to choose an article and try their hand at editing. The related GettingStarted extension was deployed mid-month and continued to evolve throughout the month, as early quantitative and qualitative research was conducted. To go along with the launch of GettingStarted and other experimentation, EventLogging underwent heavy development, including the launch of a new Schema namespace on Meta for defining the data collected in a public, collaborative manner. We created production schemas for GettingStarted, account creation, mobile, and more. Ori Livneh also reworked the format, transmission, and cleanliness of data delivered to analysts and product managers, automatically generating database tables from these schemas for incoming events. Late in the month, the team collaborated with fundraising to reach out to donors and readers as part of the annual fundraising campaign via email and a “Thank You” banner which ran at the end of the year. In addition to introducing millions of donors and readers to the Wikipedia editor community and inviting them to join, this campaign helped the team establish an experimental baseline for what a campaign to convert readers might look like. In addition to the above launches, we continued development of the new account creation experience and Guided Tours by Matt Flaschen, which will be launched in January 2013. Active development was also begun by Ryan Faulkner and Dario Taraborelli on a user metrics API. The effort is threefold: to standardize user metrics in data analysis, to build infrastructure to efficiently compute metrics for a large set of users, and finally to expose those results via an API. The 2012 annual fundraiser continued in December and was a resounding success. In addition to the ongoing maintenance required to operate the fundraiser, the team helped to execute the Thank You campaign and started to put into place new tools for auditing the fundraiser after its completion. The Mobile development and design team worked to finalize contributory and other experimental editor-focused features on the Beta site (uploads, editing, and watchlist functionality) in order to clear the way for a full push on mobile uploads by March 2013. We also worked to improve the reader and potential editor experience by introducing features geared toward educating/engaging our users, such as a human-readable last modified timestamp for articles and watchlist, and thumbnail images to illustrate the watchlist view. Lastly, because of the huge interest we generated in our Beta testing site, we created an Alpha site to house very early work on contributory features, in order not to disrupt the reading experience of our 100,000+ Beta users. GeoData Storage & API During December Max Semenik continued work on GeoData, the extension directly responsible for allowing us to easily store and retrieve GPS coordinates in our databases. Max migrated the extension from implementation, to code review, and finally deployment to the English Wikipedia. It will become 100% production-quality after a few more tweaks and fixes. After those changes, we’ll continue to roll out to the rest of the wikis. The extension is one of the precursors to having the “near by” feature on our mobile web site. During the month of December, Patrick Reilly, Dan Foy and the rest of the Zero team launched Wikipedia Zero with a new partner, Orange Congo. They resolved operational issues that prevented the team from accurately recording traffic from the Opera browser. They also helped on-board Brion Vibber to help in the interim while the team continues to look for permanent members. The team is very excited about its upcoming launches and will be announcing them as soon as possible. The J2ME app is ready to launch pending contractual negotiations with carriers. Wikipedia over SMS & USSD The USSD service is ready to launch pending contractual negotiations. The Mobile QA team planned and began several projects in December, in particular: an upcoming community test event for Mobile features; support for MobileFrontend in beta labs; and significant new UI-level automated tests in the gerrit queue. We continued the bi-weekly deployment cycle, deploying MediaWiki 1.21wmf5 and 1.21wmf6. We stopped deployments at the end of the month due to the holidays, restarting the 1.21wmf7 cycle on January 2. There’s not much to report for the month of December so far with Gerrit. New repositories continue to be created, and the vast majority of active parts of SVN have been marked read-only by now. Upgrading to a newer version of Gerrit is still blocked on our LDAP problem with master, but the patch to fix that is nearly complete. Mid-December, we extended the Verified category to now allow +2 (in addition to +1 and -1), so Jenkins has a wider range of statuses it can report. Jan Gerber continued to refine the TimedMediaHandler extension, making the transcoding steps more robust. The Wikibase client extension was deployed to test2 in December. We plan further deployment work in January, deploying to the Hungarian language Wikipedia on January 14, 2013. Captchas are ready to be served from Swift. They previously were for several days, but the configuration had to be reverted to due random errors from Swift. A new set of captchas are being tweaked for readability and are served from Swift on the test wikis. Captchas are one of the last NFS dependencies. After an assessment by Asher Feldman, Patrick Reilly and Tim Starling, the RDB database patch was canceled. Instead, in the short term, a separate vertically partitioned data cluster will be provided as a temporary storage until a horizontally scalable architecture can be finalized. Matthias Mullie is modifying the RDB-dependent ArticleFeedbackToolv5 to remove that dependency through an abstraction layer. When a sharded or horizontally scaled solution is provided, AFTv5’s abstraction will be migrated. An initial assessment of various non-MySQL alternatives for using Aaron Schulz’s JobQueue core patch in 1.20 is being done for Echo. Because of the time it takes to exhaust the Echo queues, it is written to bypass the JobQueue through direct calls. Luke Welling is abstracting the JobQueue for Redis, ZeroMQ, and others. The initial code was committed for interface for Stewards to mass-lock user accounts. For global AbuseFilters, a permission for global rule-writing was merged and the initial code for using WikiSets in the rules was written. Initial code committed for renaming CentralAuth user accounts. Wikia has completed a preliminary prototype (deemed to be disposed of after all the valuable data has been collected) in order to validate the design and its core concepts, identify and explore possible issues and test limits imposed by the platform. It will allow be used to explore the usage of PHP 5.4’s new features to ease the implementation of a maintainable versioning system (the prototype abuses PHP’s implementation of namespaces in some cases, this is not meant to persist in the final prototype but was rather a stress test), test human-readable formatting for responses when called by specific clients, and measure overhead added by the software abstraction. As a result, some pain points and alternative routes have been identified on which research work will be carried on in late January/beginning of February 2013, leading the team closer to a final implementation and related RFC. The code will be available for a short time in a dedicated branch at Wikia’s app repository at Github. Security auditing and response The team continued to respond to several reported vulnerabilities. A follow-up security review for Wikidata phase 2/3 was done. The project to support MobileFrontend in Beta labs continues. We intend for Beta labs to become a test environment for the new git-deploy script from the Operations team: this should be helpful in ongoing maintenance of the environment The last Jenkins jobs (mostly Analytics ones) that were still using the Gerrit Trigger plugin have been migrated to being triggered by Zuul. Zuul now support triggering tests for whitelisted users. This has been deployed to let trusted users have unit tests run whenever they send a patchset in mediawiki/core (gerrit change 39310). Volunteer Merlijn van Deen built a script to replicate our Jenkins installation and worked on having extensions tests run on different MediaWiki branches. After its announcement about the state of automated browser testing on wikitech-l, the QA team continued to expand test coverage, improve system and project documentation, and publicize and socialize the project by means of the “Browser Testing” MediaWiki Group. LDAP Hue/Hadoop authentication works, but group file access still needs to be worked out. We’ve puppetized an Apache proxy for internal Kraken and Hadoop web services, as well as udp2log kafka production and kafka hadoop consumption. The event.gif log stream is being consumed into Hadoop. We’re attempting to use udp2log to import logs into Kafka and Hadoop without packet loss, and backing up Hadoop service data files to HDFS (e.g. Hue, Oozie, Hive, etc.). A major rework of Limn to use d3.js and Knockout.js is complete and will be used for the next ReportCard. Dan Andreescu and David Schoonover are working on graph editing and geospatial data visualization. Daniel Zahn and Andre Klapper upgraded Bugzilla to the latest stable version (4.2.4) which provides higher flexibility for displaying interface elements, improved custom search, better JSON-RPC support and a solid base for future improvements being considered. Andre continued to improve the bug management documentation. Many bug reports that were previously closed as RESOLVED LATER were retriaged and RESOLVED LATER was disabled for future use, and a large number of previously unprioritized bug reports received a priority setting. Furthermore, Andre looked after reports about CSS issues after the MediaWiki 1.21wmf5 deployment and followed up by triaging, creating requested Bugzilla components, etc. Several smaller regex fixes were deployed in Bugzilla to fix automatic linking to Gerrit changesets. A “patch in gerrit” bug status was discussed on wikitech-l with the conclusion to wait for automatic notifications (comments) from Gerrit into Bugzilla about patch status changes first (which is being worked on by the Wikidata team). Six MediaWiki candidates have been announced for the Outreach Program for Women (OPW). 4 of them are funded by the Wikimedia Foundation and 2 by Google through an agreement with the GNOME Foundation, organizers of the program. They will work as full-time interns under the supervision of MediaWiki mentors between January and March 2013. We got 10 submissions from about 25 people interested. The rather open and participatory selection process we have defined for OPW will be used as a basis for future mentoring programs. We’ve also started matchmaking for the LevelUp mentorships for the coming quarter. Guillaume Paumier published a project plan and timeline for the consultation process started in October about how to improve 2-way communication between the technical and editing communities. He summarized the results of the first phase and reached out to the wikitech-ambassadors list to widen the consultation process by proxy. After consolidation and prioritization of the results, the most feasible solution appeared to be to grow a network of ambassadors, which he started to organize on meta. Unrelatedly, Guillaume made a list of 2012 tech blog posts to map tech blog activity by month & subdepartment (with priority activities listed separately). Work on setting up a Volunteer product manager program is also underway. Quim Gil sorted out Social media channels, and we now have @MediaWiki handles for identi.ca, Twitter, Facebook and Google+. He published the community metrics November report and a blog post introducing this new activity. Volunteer coordination and outreach MediaWiki Groups became official and the first proposals are going through the approval process. As a side effect, a process for requesting regional mediawiki-themed mailing lists has been created with mediawiki-india as the first case. At least three Wikimedia-related talks have been accepted at FOSDEM. Development of the new user interface for Translate, as well as the translation editor functionality, continued at full pace throughout the month of December, with iterative feature development and user experience improvements. Santhosh Thottingal and Niklas Laxström are leading development and Pau Giner is focusing on optimizing user experience elements. The team also released the latest version of the MediaWiki Language Extension Bundle. Increased support for language variants, alternate language codes were added to the Universal Language Selector. Alolita Sharma continued to work with Red Hat’s localization and internationalization teams to evaluate localization data, translation tools and internationalization tools and technologies. More language input methods contributed by language communities were added to the jquery.ime library. Pau Giner and Amir Aharoni participated in the Open Tech Chat this month to talk about best practices in multilingual user testing and internationalization. Amir Aharoni also participated in mentoring OPW candidate Priyanka Nag for the new LevelUp program. Srikanth Lakshmanan and Arun Ganesh’s tenure ended with the Language Engineering team in December. The Kiwix project is funded and executed by Wikimedia CH. A new Kiwix 0.9rc2 was released. This version embeds our ZIM HTTP server kiwix-serve for Windows, OSX and Linux. It is now integrated in the Kiwix UI, allowing everyone to share Wikipedia on a LAN in two clicks . We have revamped our audience measurement tool, a solution that could be interesting for other projects using Mirrorbrain. We continue at the same time to increase our ZIM production throughput with 8 new Wikipedia ZIM files in December. December was also a month of new records for Kiwix: for the first time, we have had more than 70.000 downloads a month and a Lead position for Education software at Sourceforge. The Wikidata project is funded and executed by Wikimedia Deutschland. New code and bugfixes have been deployed (with MediaWiki 1.21wmf5 and 1.21wmf6) and test2 now gets language links from Wikidata. Changes on Wikidata that concern articles on test2 are shown in the recent changes of test2 as well. If there are no problems, deployment on the Hungarian Wikipedia will happen on January 14, 2013. Other Wikipedia sites will follow. For the second phase of Wikidata, representation of values is the central focus. We published a draft and discussions have started; we’d appreciate your feedback. Additionally, Denny Vrandečić and Lydia Pintscher held IRC office hours; logs are available in English and German. The engineering management team continues to update the Deployments page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the engineering roadmap, listing ongoing and future Wikimedia engineering efforts. This article was written collaboratively by Wikimedia engineers and managers. See revision history and associated status pages. A wiki version is also available. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Technology, WMF engineering reportsTagged report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/01/10/engineering-december-2012-report/

cc40

The launch of an alpha, opt-in version of the VisualEditor to the English Wikipedia, a project more complex than it appears; A research study on the use of the Article Feedback feature; New metrics fo

en

On Saturday 28 January 2012 at 20:00 UTC there will be a workshop on Translation tools. It will take between 60 and 90 minutes and will consist of an introduction of use cases and features, as well as a Q&A. (local times) The workshop will focus on the use cases covered by the Translate extension on Wikimedia Meta-Wiki for the following user roles: writers: those who write texts that need to be translated translation administrators: those who mark pages for translations and post-process translations when they have been made Please put the following page on your watchlist and write your name down if you would like to attend. The workshop is held online using WebEx. I would advise you to log in 15 minutes in advance to ensure you have ample time to set up your computer if you have not used WebEx before. WebEx can be used in desktop environments on Linux, OSX and Windows. If you would like to familiarise yourself with the technology before the workshop, please take a look at the elaborate documentation, which includes some tutorials. In the next two weeks, the already present documentation for translators will also be completed. Credit goes to Pete Forsyth for proposing to have this workshop. Hope to see you online Saturday! Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Internationalization and localization, TechnologyTagged meta, translation, tutorial, WebEx, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/01/25/tutorial-for-using-the-translate-extension/

cc40

On Saturday 28 January 2012 at 20:00 UTC there will be a workshop on Translation tools. It will take between 60 and 90 minutes and will consist of an introduction of use cases and features, as well as

en

Today we’re pleased to release the latest annual report from the Wikimedia Foundation. The 2012-13 Annual Report celebrates “Ten years of sharing and learning,” and marks the decade milestone of the Foundation with over 20 quotes and insights we heard from within the movement over the course of the most recent fiscal year. The Foundation’s annual report is published both as a PDF for digital reading, a wiki, and as a printed document. You can access other copies of the Foundation’s reports (now in its sixth year of publication) on the WMF wiki. We hope you enjoy this year’s report, and we encourage you to share it widely within the Wikimedia movement. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Annual Reports, FoundationTagged annual report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/01/21/wikimedia-foundation-annual-report/

cc40

Today we’re pleased to release the latest annual report from the Wikimedia Foundation. The 2012-13 Annual Report celebrates “Ten years of sharing and learning,” and marks the decade milestone of the F

en

As an Open Access title, publishing an article in this journal requires an Article Processing Charge (APC) that will be billed to the submitting author following acceptance. Apart from this Article Processing Charge there are no other fees (for example submission charges, page charges, or color charges). The Article Processing Charge for the journal is free. If you've ever submit an article in our journals, you've certainly experienced these steps with us. The minimum time required to accept an article will be 2 months and the maximum will be 6 months. Once an article has been accepted for publication, an Article Processing Charge is due. The submitting author assumes responsibility for the Article Processing Charge, and CMBR will not issue refunds of any kind. CMBR operates a transparent waiver policy to help support researchers who are unable to meet some or all of the cost associated with publishing open access. Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/page_785.html

cc40

As an Open Access title, publishing an article in this journal requires an Article Processing Charge (APC) that will be billed to the submitting author following acceptance. Apart from this Article Pr

en

Visit "My HOME" to edit or update your account information and user profile. Your options are included: change your password, update your profile information, and view your saved records. I have forgotten my password—how can I retrieve it? I can't remember the e-mail address on my account. Please do not hesitate to contact the editorial office via [email protected] We will be happy to help you retrieve your account information ASAP. How can I report a technical problem with the site? Please contact editorial office ([email protected]) to report any problems. It is helpful if you can provide the URL you are accessing, the browser and operating system you are using, and any error messages you encounter. Which web browsers does https://www.cmbr-journal.com/ site support? CMBR supports a variety of browsers, including Internet Explorer, Firefox, Chrome, and Safari. If you have questions about whether the version you are using is supported, please contact us ([email protected]). Who is on the Journal’s Editorial Board? View the current list of the CMBR’s Editorial Board members in "Journal Info" section. How do I inquire about the status of a manuscript I submitted? You may check on the status of your submitted manuscripts by visiting our online manuscript processing system at "login form" and locating your manuscript in your account. How many manuscripts can any author submit? Authors may submit an unlimited number of articles, provided that all submissions are compatible with our "Guide for Authors". Once I have submitted a manuscript, how long can I expect to wait before I hear from the journal, and how much time passes between acceptance and publication of a manuscript? Submissions are acknowledged promptly by e-mail. All manuscripts submitted to the CMBR are subject to peer-review process. Authors can expect to wait about one or two months from the date of submission until receiving the journal’s decision. For manuscripts that are selected for revision, the length of time between the revision request and publication will vary widely (from two weeks to two months) depending on various factors, including the extent of revision required, the need for additional review and revision. How often does the journal get published? The CMBR is Semiannual. What is your acceptance rate? Our acceptance rate for uninvited manuscripts is free The system doesn’t recognize the email address I enter to retrieve my password. This is the email you used when you registered for CMBR account. If you no longer have access to the email used to create your account, please contact our editorial office ([email protected]) to change your email address and update your password. How can I find out why I’m not receiving alerts I’ve signed up for? If you are not receiving your e-mail alerts, check your current settings in your "My HOME" account. You will be able to manage your e-mail preferences from there. What are the publication charges for an article in CMBR? CMBR supports the Open Access initiative. Abstracts and full texts (PDF format) of all articles published by CMBR are freely accessible to everyone immediately upon publication. The publication fee is Free for each article. Can I make changes to my manuscript at proof stage? Although you will receive proofs from editorial office before your manuscript is published, the purpose of these proofs is to pick up inaccuracies or typographical errors. You will not be able to make editorial changes (e.g. changes in wording, adding references, etc.) at this stage. Indeed, it is essential that you ensure that the version you submit for publication in CMBR is your final version. Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/journal/faq

cc40

Visit "My HOME" to edit or update your account information and user profile. Your options are included: change your password, update your profile information, and view your saved records. I have forgo

en

Hover your mouse over the green question marks ([?]) to see the description of a particular project. Judging for the October 2011 Coding Challenge continued and winners will be announced in January. San Francisco hackathon (21–22 January 2012, San Francisco, California, USA) — Erik Möller and Sumana Harihareswara continued to plan and publicize this outreach-focused developers week-end. Heather Walls developed a more attractive homepage for the event. Sumana began arranging for tutorials and activities for the event, focusing on mobile, the web-accessible API and our framework for JavaScript feature development. Registration opened and more than 70 participants registered. Pune hackathon (10–12 February 2012, Pune, India) — Preparation began and registration opened for an outreach-focused developers week-end to take place in Pune, India, and led by Alolita Sharma. Approximately 70 participants are expected, focusing on the gadgets framework, mobile Wikimedia access, and internationalization. GLAMcamp DC (10–12 February 2012, Washington, D.C., USA) — Ryan Kaldari and Asaf Bartov plan to attend the technical track of this GLAM conference. Engineers will work on mass upload and analytics functionality. Are you looking to work for Wikimedia? We have a lot of hiring coming up, and we really love talking to active community members about these roles. Software Developer (Back-end, Data Analytics) Software Developer (Rich Text Editing, Features) Executive Dashboard – Analytics — Help us improve and centralize the dashboard summarizing the most important data about the Wikimedia movement to understand overall community health. XML Dumps — Help us improve the infrastructure used to build XML dumps of Wikipedia content, for backups and reuse by third parties. Mobile UX — Help us redesign our mobile platform and apps as more and more visitors access Wikipedia and its sister sites via mobile devices. Yuvaraj Pandian and Max Semenik joined the mobile team as contract developers. Sara Smollett joined the operations team as a part-time contractor. Diederik van Liere, formerly with the Community Department, is now helping the engineering department as a contractor for analytics work. Data Centers [?] — The team deployed a new MediaWiki profiling system based on graphite, to track performance across the application stack, and to provide statistics/graphing as a service for MediaWiki within the WMF production environment. Some database servers were moved to newer hardware (including OTRS), and those in the Ashburn data center were upgraded to a new build of mysql-at-facebook. Mark Bergsma refactored our configuration tool (Puppet) to address scalability and performance issues. Media Storage [?] — As part of the preparation for the migration of our media service to Swift, a distributed storage back-end, we need to keep the current system afloat a bit longer. We reclaimed some space by purging thumbnails not newly generated and not in use on any of our projects. We also performed Swift thumbnail integration and stress testing. Read performance is about 10x what we need on the performance test cluster so we’re good on that front. Write performance is only 2x what we need, but sufficient to move forward. Tests and research indicates performance drops over a few million objects; the easiest path forward is to shard the Commons container using the existing hashed characters in the URL, splitting the container into 256 containers. HTTPS — HTTPS support was added for mobile, for Wikipedia. After an initial testing period, we’ll enable this for further mobile sites. A number of other miscellaneous services also had HTTPS set up or fixed. Wikimedia Labs [?] — A server admin log was created for every project, as well as a combined log. OpenStackManager 1.3 and LdapAuthentication 2.0a were deployed to Labs. Live migration of instances has been enabled for the OpenStack Nova infrastructure, allowing updates and upgrade of hardware without bringing instances down. A gluster storage cluster has been ordered for use as volume storage. A number of projects were added or moved to Labs, including adminbot, nagios, Cluebot, testswarm and the reportcard service. There are now 33 projects, 52 instances, and 74 users. Backups and data archives Data Dumps [?] — The end of the year closed out with another full dump of the English language Wikipedia on schedule. More work was done on code to allow restart of the history phase of a dump from a specified point without a long catchup delay. An experimental service was tested this month: a newly formatted file of article content and an accompanying index, more convenient for data analysts and for use with offline readers. Visual editor [?] — The team deployed a developer prototype of the visual editor sandbox to mediawiki.org for public feedback and testing. Trevor Parscal fixed bugs and refactored code. Inez Korczynski worked on the toolbar (text styles), the undo/redo stack, and lists (creating, deleting, and changing indentation). Gabriel Wicke worked on the parser test runner and the parser pipeline, including the tokenizer and its grammar and template expansions. Neil Kandalgaonkar worked on the undo/redo feature and did a lot of refactoring. Internationalization and localization tools [?] — The WebFonts extension was deployed to select Indic languages and projects, making it possible to read content in languages using non-Latin fonts without installing fonts manually. The deployment uncovered bugs and issues that were addressed by the team, like cross-site font loading. The team also improved the Narayam and Translate extensions, and the latter was enabled on mediawiki.org to facilitate the translation of software documentation (like the Help:Extension:WebFonts page). Participation and editor retention Article feedback [?] — The team launched three test versions of the new feedback forms on a sample of pages on the English Wikipedia. Aaron Halfaker, Oliver Keyes and Dario Taraborelli are working with the editor community to evaluate comments coming in from feedback forms. Dario also developed a set of dashboards with real-time metrics and a feedback stream surfacing early data collected in the version 5 pilot. Fabrice Florin is leading development on the next round of features, including a new feedback page, special calls to action to engage new editors, and a prominent feedback link, to be implemented by OmniTI, our development partner. Feedback Dashboard [?] — Rob Moen added support for wikitext in responses, preview of changes, handling of blocked users, and fixed various bugs. Benny Situ worked on feedback response, notifications and HTML e-mails. Dario Taraborelli developed two sets of charts to visualize data from the FeedbackDashboard and response notification. UploadWizard [?] — Users can now choose a default license for all uploads in their user preferences under “Upload Wizard” (bug 24702). All license choices now also link to the legal code of a license. The built-in feedback form more prominently links to Bugzilla. TimedMediaHandler [?] — Ian Baker and Neil Kandalgaonkar completed the review of all the code, including the transcoding part. They started to plan a test plan and a deployment to Wikimedia Labs. ResourceLoader [?] — Roan Kattouw updated and created tests for PHPUnit. Timo Tijhof fixed layout bugs in the Gadget manager, did some code review, and tested the migration of gadgets on a prototype. Wikipedia Education Program [?] — Jeroen De Dauw started to work on a MediaWiki extension to support the Wikipedia Education Program; the implementation of course, term and institution management has been completed, and a test wiki is available. Mobile Research [?] — Mani Pande and Parul Vora consolidated all the research findings from Brazil, India, and the USA into one report. It’s currently being converted to PDF and wikitext to facilitate its publication. MobileFrontend [?] — We quietly launched user login alongside better support for tiered JavaScript. We also fixed long-standing issues like the locked viewport, and we updated image description pages. Finally, we deployed HTTPS support on mobile for Wikipedia, with plans to enable it for sister projects soon. Android Wikipedia App [?] — Several release candidates were released over the month and we’re nearing completion of the first version of the app, thanks to developers Yuvaraj Pandian and Brion Vibber. Nightly builds are available for testing. WikipediaZero — We began work on the infrastructure for zero-rated Wikipedia access. Next month, we’ll start testing with one of our partners to work out the kinks of giving users free data access to Wikipedia. GPS Storage/Retrieval — Max Semenik joined the mobile team and began prototying an API to store and retrieve GPS coordinates on our wikis. This will be a critical component of the mobile projects; it will replace our existing use of GeoNames.org and can also supplement GeoHack. Featured Article RSS — Max Semenik built the first version of an extension to expose featured articles, In the news, and other main page content so that our partners can better re-use our data. 2011 Fundraiser [?] — The DonationInterface extension underwent enhancements to tighten up security. Support was also added for monthly recurring donations for credit cards through our new payment processor, GlobalCollect, and we are working on automating the processing of recurring payments to our instance of CiviCRM. We built custom mass-mailing scripts to e-mail about 1 million past donors to encourage them to donate again. The ContributionReporting extension was enhanced by storing aggregated data in their own tables and updating them periodically, to eliminate the cache stampede problem uncovered last month. We added support for automatic notification of non-credit card payments from GlobalCollect, which allows us to automatically record donor and donation information in our donor database. Kiwix UX initiative [?] — Work continued on the 0.9 release of Kiwix. Lead developer Emmanuel Engelhart released Kiwix 0.9 beta5 for community testing, fixing lots of reported bugs and soliciting testers to get involved. The “MediaWiki Core” team was featured on the Wikimedia Tech blog this month. MediaWiki 1.19 [?] — Rob Lanphier continued to coordinate the efforts from Wikimedia engineers to review commits to the MediaWiki codebase, as part of the Wikimedia engineering 20% policy. Mark Hershberger started to send automated reminders to developers whose revisions are marked as “fixme” in Code review. Progress on unreviewed commits is tracked through the 1.19 revision report and the Code review statistics. As of December 31st, about 600 revisions remain to be reviewed in trunk. Brion Vibber proposed a feature freeze in trunk, to catch up on code review, instead of branching the code for release. Continuous integration [?] — The TestSwarm package was Debianized and its configuration almost entirely entered into Puppet. Antoine Musso and Daniel Zahn deployed TestSwarm to the production continuous integration portal. Git conversion [?] — The rules to convert phase3/ have been finished and a test repository is now available. Chad Horohoe is now working on convert rules for extensions, and on user permissions. VipsScaler [?] — VIPS hasn’t proven as effective at saving memory on large PNG files as what was expected, but it has shown improvements for large TIFFs. Deployment to Wikimedia sites is deferred until MediaWiki 1.19 is deployed. Bryan Tong Minh will reach out to upstream developers to include fixes for PNG and JPG files. SwiftMedia [?] — Aaron Schulz merged the FileBackend branch into /trunk, and Tim Starling started to review the code. Aaron, Ben Hartshorne, Ariel Glenn discussed sharding the Swift containers at the MediaWiki level, and Aaron started to implement it. HipHop deployment [?] — After Facebook announced that they were developing virtual machines for HipHop, Tim Starling indicated that Wikimedia would put their current efforts on HipHop on hold, until the virtual machines can be evaluated. Other performance efforts like Wikitext scripting will take priority instead. Wikimedia Report Card 2.0 [?] — The reportcard 2.0 was moved to the Labs environment, and its source code centralized. The back-end and front-end code of stats.grok.se was rewritten and is being deployed to Labs as well. A renewed effort is expected as new employees come on board in January. Technical Liaison; Developer Relations Bug management [?] — Mark Hershberger followed up on MediaWiki 1.18 bugs, and wrote a FAQ listing issues and offering solutions until 1.18.1 is released. Mark also continued to go through “highest priority” bugs, dealt with bugzilla vandalism, reviewed patches submitted in bugzilla, and held bug triages on MediaWiki 1.18 and Fundraising engineering. Summer of Code 2011 [?] — Neil Kandalgaonkar met with the Internet Archive about progress on ArchiveLinks; they are awaiting fixes and improvements in ArchiveLinks before it can go live. Yuvaraj Pandian fixed several issues with his offline article selection project, SelectionSifter, towards getting the code to a deployable state. Roan Kattouw made plans to review and merge Salvatore Ingala’s gadgets project during his ResourceLoader 2 work in February 2012. Engineering project documentation [?] — Guillaume Paumier performed perennial maintenance on project pages and the Roadmap (updating, cleaning up and organizing the content as needed), and wrote this report. Volunteer coordination and outreach [?] — Sumana Harihareswara continued to follow up on contacts and recruit new contributors to the Wikimedia tech community (especially for commit and patch review), and mentor new contributors. Eleven developers got commit access, all from the non-staff MediaWiki community. Sumana also prepared for the January San Francisco hackathon and the February Pune hackathon, and recruited participants. Partly in preparation for these coding events, Sumana and Guillaume Paumier continued to consolidate training documentation to facilitate the onboarding of new developers. MediaWiki architecture document [?] — This project was mostly on hold in December, while the book’s technical reviewers went through the content. They provided a second round of feedback and minor recommendations, that will be addressed in January. Wikimedia blog maintenance [?] — Guillaume Paumier continued to fix bugs in the blog’s theme, and started to develop a WordPress plugin to bring functionality specific to the Wikimedia blog independently of the theme (for example, expanding the group of users who can upload files). The engineering management team continues to update the Software deployments page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the engineering roadmap, listing ongoing and future Wikimedia engineering efforts. This article was written collaboratively by Wikimedia engineers and managers. See revision history and associated status pages. A wiki version is also available. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. You should do a ‘year in review’ article for the technology. Would be much appreciated, to show that progress is indeed happening. No word on LiquidThreads, is it dropped altogether? LiquidThreads dropped ? I hope not ! It looks great, and, a contrario, the current talk way in Wikipedia is really bad, really not made for discussions. Ioannis: The Wikipedia Signpost traditionally publishes a “year in review” issue, which includes an article about technology. They’re an independent community newspaper, so they should provide an unbiased progress report. Trazeris and Nicolas: The status of LiquidThreads was recently brought up on the wikitech-l mailing list; you might want to read the responses given there. @Guillaume, thank you for the link Posted in Technology, WMF engineering reportsTagged report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/01/07/engineering-december-2011-report/

cc40

Hover your mouse over the green question marks ([?]) to see the description of a particular project. Judging for the October 2011 Coding Challenge continued and winners will be announced in January. S

en

Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital Cellular, Molecular and Biomedical Reports Publication Ethics and Malpractice Statement Guiding Principles for Research Involving Animals and Human Beings Editorial Policies (Appeals and Complaints) Practical Guide to the SI Units Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital Document Type : Original Article 1 Medical Laboratory Technique Department, The Islamic University, Diwaniya, Iraq 2 Research and Studies Department, The Islamic University, Najaf, Iraq Emerging antibiotic resistance in microorganisms particularly multidrug-resistant strains among bacteria are increasing because of misusing antibiotics as well as evolution of antibiotic resistance mechanisms. In this regard, Acinetobacter baumannii is one of the six most common multidrug-resistant microorganisms in hospitals. Recently, carbapenems, as common antibiotics to treat infections of Acinetobacter have not an acceptable efficiency because of the resistance emergence to these antibiotics in many strains. In this study, resistant strains of A. baumannii were isolated and identified as an appropriate preventive strategy to reduce infections in hospitals. Disc diffusion test and PCR method were used to isolate of resistant strains and identify beta-lactamase genes of blaAmpC, blaTEM, blaVIM, and blaSHV. This study showed that these genes were contributed in antibiotic resistance with about 18.4% and ≥53.5% strains expressing all 4 genes and ≥3 genes, respectively. The blaAmpC gene is more prevalent than other genes, and this is probably due to the prevalence or rapid transfer of this beta-lactamase. However, more studies should be performed in a comparative way to isolate and identify other antibiotic-resistant bacterial strains relate to other hospitals. nosocomial infections, antibiotic-resistant bacteria, carbapenems antibacterial activity, beta-lactamase genes, the blaAmpC gene DNA, RNA, protein components Selected author of this article by journal ِDr. Qassim hassan Aubais aljelehawy Researchgate ; Google Scholar This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit: http://creativecommons.org/licenses/by/4.0/ CMBR journal remains neutral with regard to jurisdictional claims in published maps and institutional afflictions. Given that CMBR Journal's policy in accepting articles will be strict and will do its best to ensure that in addition to having the highest quality published articles, the published articles should have the least similarity (maximum 18%). Also, all the figures and tables in the article must be original and the copyright permission of images must be prepared by authors. However, some articles may have flaws and have passed the journal filter, which dear authors may find fault with. Therefore, the editor of the journal asks the authors, if they see an error in the published articles of the journal, to email the article information along with the documents to the journal office. CMBR Journal welcomes letters to the editor ([email protected]) for the post-publication discussions and corrections which allows debate post publication on its site, through the Letters to Editor. Critical letters can be sent to the journal editor as soon as the article is online. Following points are to be considering before sending the letters (comments) to the editor. [1] Letters that include statements of statistics, facts, research, or theories should include appropriate references, although more than three are discouraged. [2] Letters that are personal attacks on an author rather than thoughtful criticism of the author’s ideas will not be considered for publication. [3] There is no limit to the number of words in a letter. [4] Letter writers should include a statement at the beginning of the letter stating that it is being submitted either for publication or not. [5] Anonymous letters will not be considered. [6] Letter writers must include Name, Email Address, Affiliation, mobile phone number, and Comments [7] Letters will be answered as soon as possible Ercisli MF, Lechun G, Azeez SH, Hamasalih RM, Song S, Aziziaram Z (2021) Relevance of genetic polymorphisms of the human cytochrome P450 3A4 in rivaroxaban-treated patients. Cell Mol Biomed Rep 1(1):33-41 Tourang M, Fang L, Zhong Y, Suthar RC (2021) Association between Human Endogenous Retrovirus K gene expression and breast cancer. Cell Mol Biomed Rep 1(1):7-13 Alavi M, Webster TJ (2021) Recent progress and challenges for polymeric microsphere compared to nanosphere drug release systems: Is there a real difference? Bioorg Med Chem 33:116028. doi:https://doi.org/10.1016/j.bmc.2021.116028 Aljelehawy Q, Karimi N, Alavi M (2020) Comparison of antibacterial and cytotoxic activities of phytosynthesized ZnONPs by leaves extract of Daphne mucronata at different salt sources. Mater Technol):1-13. doi:https://doi.org/10.1080/10667857.2020.1794280 Li B, Webster TJ (2018) Bacteria antibiotic resistance: New challenges and opportunities for implant‐associated orthopedic infections. J Orthop Res 36(1):22-32. doi:http://doi.org/10.1002/jor.23656 Alavi M, Rai M (2021) Chapter 11 - Antibacterial and wound healing activities of micro/nanocarriers based on carboxymethyl and quaternized chitosan derivatives. In: Rai M, dos Santos CA (eds) Biopolymer-Based Nano Films. Elsevier, pp 191-201. doi:https://doi.org/10.1016/B978-0-12-823381-8.00009-0 Alavi M, Dehestaniathar S, Mohammadi S, Maleki A, Karimi N (2020) Antibacterial activities of phytofabricated ZnO and CuO NPs by Mentha pulegium leaf/flower mixture extract against antibiotic resistant bacteria. Adv Pharm Bull 1:1-14. doi:http://doi.org/10.34172/apb.2021.057 Georgios M, Egki T, Effrosyni S (2014) Phenotypic and molecular methods for the detection of antibiotic resistance mechanisms in Gram negative nosocomial pathogens. Trends Infect Dis):139-162. doi:http://doi.org/10.5772/57582 Ayoub Moubareck C, Hammoudi Halat D (2020) Insights into Acinetobacter baumannii: A Review of Microbiological, Virulence, and Resistance Traits in a Threatening Nosocomial Pathogen. Antibiotics 9(3):119 Bergogne-Bérézin E, Joly-Guillou ML, Towner KJ (2020) Introduction—History and Importance of Acinetobacter spp., Role in Infections, Treatment and Cost Implications. In: Acinetobacter. CRC Press, pp 1-12 Chan P-C, Huang L-M, Lin H-C, Chang L-Y, Chen M-L, Lu C-Y, Lee P-I, Chen J-M, Lee C-Y, Pan H-J (2007) Control of an outbreak of pandrug-resistant Acinetobacter baumannii colonization and infection in a neonatal intensive care unit. Infect Control Hosp Epidemiol 28(4):423-429. doi:http://doi.org/10.1086/513120 Kyriakidis I, Vasileiou E, Pana ZD, Tragiannidis A (2021) Acinetobacter baumannii Antibiotic Resistance Mechanisms. Pathogens 10(3):373. doi:http://doi.org/10.3390/pathogens10030373 Bush K, Jacoby GA (2010) Updated functional classification of beta-lactamases. Antimicrob Agents Chemother 54(3):969-976. doi:http://doi.org/10.1128/AAC.01009-09 Lee C-R, Lee JH, Park M, Park KS, Bae IK, Kim YB, Cha C-J, Jeong BC, Lee SH (2017) Biology of Acinetobacter baumannii: pathogenesis, antibiotic resistance mechanisms, and prospective treatment options. Front Cell Infect Microbiol Paterson DL, Bonomo RA (2005) Extended-spectrum B-lactamases: a clinical update. Clin Microbiol Rev 18(4):657-686. doi:http://doi.org/10.1128/CMR.18.4.657-686.2005 Alavi M, Karimi N (2019) Biosynthesis of Ag and Cu NPs by secondary metabolites of usnic acid and thymol with biological macromolecules aggregation and antibacterial activities against multi drug resistant (MDR) bacteria. Int J Biol Macromol 128:893-901. doi:https://doi.org/10.1016/j.ijbiomac.2019.01.177 Piperaki ET, Tzouvelekis LS, Miriagou V, Daikos GL (2019) Carbapenem-resistant Acinetobacter baumannii: in pursuit of an effective treatment. Clin Microbiol Infect 25(8):951-957. doi:http://doi.org/10.1016/j.cmi.2019.03.014 Leverstein-van Hall MA, Fluit AC, Paauw A, Box ATA, Brisse S, Verhoef J (2002) Evaluation of the Etest ESBL and the BD Phoenix, VITEK 1, and VITEK 2 automated instruments for detection of extended-spectrum beta-lactamases in multiresistant Escherichia coli and Klebsiella spp. J Clin Microbiol 40(10):3703-3711. doi:http://doi.org/10.1128/JCM.40.10.3703-3711.2002 Afhami S, Borumand MA, Bazzaz NE, Saffar H, Hadadi A, Nezhad MJ, Tirabadi NM (2020) Antimicrobial resistance pattern of Acinetobacter; a multicenter study, comparing European Committee on Antimicrobial Susceptibility Testing (EUCAST) and the Clinical and Laboratory Standards Institute (CLSI); evaluation of susceptibility testing methods for polymyxin. Immunopathol persa 7(1):e04-e04. doi:http://doi.org/10.34172/ipp.2021.04 Andrzejczuk S, Kosikowska U, Chwiejczak E, Stępień-Pyśniak D, Malm A (2019) Prevalence of resistance to B-lactam antibiotics and bla genes among commensal Haemophilus parainfluenzae isolates from respiratory microbiota in Poland. Microorganisms 7(10):427 Ahmed OB, Dablool AS (2017) Quality improvement of the DNA extracted by boiling method in gram negative bacteria. Int J Bioassays 6(4):5347-5349. doi:http://dx.doi.org/10.21746/ijbio.2017.04.004 Chang Y, Luan G, Xu Y, Wang Y, Shen M, Zhang C, Zheng W, Huang J, Yang J, Jia X (2015) Characterization of carbapenem-resistant Acinetobacter baumannii isolates in a Chinese teaching hospital. Front Microbiol 6:910. doi:http://doi.org/10.3389/fmicb.2015.00910 Lowings M, Ehlers MM, Dreyer AW, Kock MM (2015) High prevalence of oxacillinases in clinical multidrug-resistant Acinetobacter baumannii isolates from the Tshwane region, South Africa–an update. BMC Infect Dis 15(1):1-10. doi:http://doi.org/10.1186/s12879-015-1246-8 Yin X-L, Hou T-W, Xu S-B, Ma C-Q, Yao Z-Y, Li W, Wei L (2008) Detection of drug resistance–associated genes of multidrug-resistant Acinetobacter baumannii. Microb Drug Resist 14(2):145-150. doi:http://doi.org/10.1089/mdr.2008.0799 Mohammed H, Elsadek Fakhr A, Al Johery SaE, Abdel Ghani Hassanein W (2016) Spread of TEM, VIM, SHV, and CTX-M B-lactamases in imipenem-resistant Gram-negative bacilli isolated from Egyptian hospitals. Int J Microbiol 2016. doi:http://doi.org/10.1155/2016/8382605 Shali AAK (2012) Identification of Multidrug-Resistant Genes in" Acinetobacter baumannii" in Sulaimani City-Kurdistan Regional Government of Iraq. Asian J Med Sci 4(5):179-183 Al-Hasnawy HH, Saleh RH, Hadi BH (2018) Existence ofaESBL genes in Escherichia coli and Acinetobacter baumannii isolated from different clinical specimens. J Pharm Sci 10(5):1112-1117. doi:https://www.jpsr.pharmainfo.in/issue.php?page=105# Aziz RAR, Al-Jubori SS (2017) Molecular analysis of genetic elements responsible for XDR in highly successful pathogen Acinetobacter baumannii isolated from clinical samples of Iraqi patients. J Glob Pharma Technol 9(4):26-39. doi:http://www.jgpt.co.in/index.php/jgpt/issue/archive?issuesPage=4#issues Al-Agamy MH, Khalaf NG, Tawfick MM, Shibl AM, El Kholy A (2014) Molecular characterization of carbapenem-insensitive Acinetobacter baumannii in Egypt. Int J Infect Dis 22:49-54. doi:https://doi.org/10.1016/j.ijid.2013.12.004 Mushi MF, Mshana SE, Imirzalioglu C, Bwanga F (2014) Carbapenemase genes among multidrug resistant gram negative clinical isolates from a tertiary hospital in Mwanza, Tanzania. Biomed Res Int 2014. doi:https://doi.org/10.1155/2014/303104 Hujer KM, Hujer AM, Hulten EA, Bajaksouzian S, Adams JM, Donskey CJ, Ecker DJ, Massire C, Eshoo MW, Sampath R (2006) Analysis of antibiotic resistance genes in multidrug-resistant Acinetobacter sp. isolates from military and civilian patients treated at the Walter Reed Army Medical Center. Antimicrob Agents Chemother 50(12):4114-4123. doi:http://doi.org/10.1128/AAC.00778-06 Fallah F, Noori M, Hashemi A, Goudarzi H, Karimi A, Erfanimanesh S, Alimehr S (2014) Prevalence of blaNDM, blaPER, blaVEB, blaIMP, and blaVIM genes among Acinetobacter baumannii isolated from two hospitals of Tehran, Iran. Scientifica 2014. doi:http://doi.org/10.1155/2014/245162 Al-Kadmy IMS, Ali ANM, Salman IMA, Khazaal SS (2018) Molecular characterization of Acinetobacter baumannii isolated from Iraqi hospital environment. New Microbes New Infect 21:51-57. doi:https://doi.org/10.1016/j.nmni.2017.10.010 Volume 1, Issue 2 - Serial Number 2 Cellular, Molecular and Biomedical Reports Receive Date: 15 August 2021 Revise Date: 27 October 2021 Accept Date: 23 December 2021 First Publish Date: 23 December 2021 Abbas-Al-Khafaji, Z. K., & Aubais-aljelehawy, Q. H. (2021). Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital. Cellular, Molecular and Biomedical Reports, 1(2), 60-68. doi: 10.55705/cmbr.2021.142761.1015 Zahraa Khudhair Abbas-Al-Khafaji; Qassim hassan Aubais-aljelehawy. "Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital". Cellular, Molecular and Biomedical Reports, 1, 2, 2021, 60-68. doi: 10.55705/cmbr.2021.142761.1015 Abbas-Al-Khafaji, Z. K., Aubais-aljelehawy, Q. H. (2021). 'Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital', Cellular, Molecular and Biomedical Reports, 1(2), pp. 60-68. doi: 10.55705/cmbr.2021.142761.1015 Abbas-Al-Khafaji, Z. K., Aubais-aljelehawy, Q. H. Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital. Cellular, Molecular and Biomedical Reports, 2021; 1(2): 60-68. doi: 10.55705/cmbr.2021.142761.1015 Corresponding author ORCID 2022-05-01 Special Issue about the " Nanomaterials to Combat ... 2022-04-08 Happy News: Cellular, Molecular and Biomedical Reports ... 2021-10-10 This open-access journal is published under the terms of the Creative Commons Attribution 4.0 International License.

https://www.cmbr-journal.com/article_142761.html

cc40

Evaluation of antibiotic resistance and prevalence of multi-antibiotic resistant genes among Acinetobacter baumannii strains isolated from patients admitted to al-yarmouk hospital Cellular, Molecular

en

Wikimedia Foundation sites are the fifth most popular web property. So when we conducted our Readers Survey, we expected to hear from our readers that they valued Wikipedia as a reliable source of online information. But we were still pleasantly surprised to see the overwhelming positive feedback from readers mixed with a deep appreciation of Wikipedia and its community for the existence of the free and easily available online encyclopedia that offers a wide breadth of content. As expressed by some of the more than 2000 readers who took the opportunity to leave a free-form comment at the end of the survey: “love the site” “blessing” “thank you for existing and “you can find everything in Wikipedia.” Praise for Wikipedia was a common thread among many readers. “It is great.” “It is a living organism – constantly evolving.” Word cloud of open ended responses from the Wikipedia Readers Survey The real credit for building Wikipedia goes to the thousands of editors who volunteer hours every month editing Wikipedia, and as one reader from Egypt put it: “thank you to all who have contributed in this great work.” Readers who had never edited, but were aware that volunteers wrote Wikipedia articles acknowledged that they were embarrassed that they had never edited Wikipedia. Although readers from all age groups read Wikipedia, with the average reader being 36 years old, Wikipedia remains an important tool for school students. “Great for school work,” said one. Acknowledging the role of Wikipedia as the first stop for information for school work, a reader in India said: “I wish I had Internet and Wikipedia when I was in school in the 70s.  My grades would have sky rocketed.” Parents also acknowledged using Wikipedia for helping children with their school work. Some readers took the opportunity to point out features that they believe can be improved on Wikipedia, like search, the ability to improve the reading experience through customizable fonts and more audio and visual content to facilitate understanding of complex topics. We heard similar needs from users when we conducted user experience research in India, Brazil and the US. We have improved search functionality on the mobile site, and other features to improve the reading experience are on the product roadmap. To our surprise (this was the first time participants thanked us for providing them the opportunity to participate in a survey), many readers told us that they loved participating in the study since it helped them expand their knowledge about Wikipedia (e.g. learning about features that they had not been aware of, or about WMF’s non-profit status). “From today, I will certainly be using Wikipedia more, excellent survey, it made me understand things I have been missing,” said a reader from the UK. Mani Pande, Head of Global Development Research Ayush Khanna, Data Analyst, Global Development We recently conducted an online survey of Wikipedia readers, limited to 250 participants each in 16 countries. This is the last in a series of blog posts summarizing our findings. If you are interested, you can find out more about the methodology of the survey here. Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. First, BIG thank you for Wikipedia you did a great favor for humanity, specially in 3rd world countries (like here in Egypt) where buying books costs much. I want to volunteer in working in Wikipedia even in translating to Arabic contents, that would be great! Wikipedia is my first port of call (before cross referencing) when I want learn about something. In the darkness of ignorance one should light a lamp for showing the others the path and he is you. The middle age is not a past era but is whenever there is no information and the man who writes makes renaissance and you are the one Hey thank you everyone at wiki and for everyone at home sharing your knowledge with the world this is deffinetely the no.1 first stop for winning bets with friends lol but on a serious note much appreciated great work everyone! Thank you , Wikipedia aww, I didn’t get to do the survey, oh well, I would have said all sorts of nice things, like my Anthro professor said the reason we went from Horse and Buggy to Man on the Moon in less than 100 years is due to greater population and greater population densitiy leading to greater communications, thus now with the internet, in just a couple of years, in just a couple of seconds, its already happening at http://www.archure.net and Wikipedia too! internet without wikipedia is like earth without water. Wikipedia is not just a portal , it is part of millions of people’s daily life . It has served as the beacon of knowledge for many who can not access it otherwise . Special thanks to those volunteers who provided their contribution towards this noble cause . I am learning a lot from Wikipedia. It is the 1st choice for me whenever i want to learn something. And this is one of the best site in the Internet. Thank you so much…. Wikipedia is a great source of information and the pages are usually very well-written and very informative. Thanks to the Wikimedia foundation and to the editors for their time and effort ! However, as a reader I think it’s good practice to look at and verify the citations from time to time. Just Because Of Wikipedia , Getting My Engineering Done Is A Piece Of Cake … Hats Off To WIKIPEDIA .. Wikipedia ………The might of free knowledge By the real meaning of the word “THANK YOU” Posted in Global, ResearchTagged Readers survey, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2012/02/24/thank-you-to-all-who-have-contributed-in-this-great-work/

cc40

Wikimedia Foundation sites are the fifth most popular web property. So when we conducted our Readers Survey, we expected to hear from our readers that they valued Wikipedia as a reliable source of onl

en

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/subscriptions/list/PHID-TASK-aahnlfbjivfwgay7hbuo/

cc40

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this

en

Legal documents are intended to be precise and comprehensive. Unfortunately, they’re often not very accessible. Lawyers are used to communicating with other lawyers with jargon that is well-defined in law, but can often be difficult for others to understand. This complicated language is particularly problematic with online policies that are intended for audiences of varying ages and nationalities. To make matters worse, legal documents often have large chunks of fine print, which are difficult to read on a computer screen (not to mention, on a phone!). The Wikimedia Foundation is looking to break this pattern with a new trademark policy by using plain language and borrowing visualization techniques from information design. Information design focuses on improving user experience to effectively communicate information using images, color coding, typography, and white space. We are currently preparing a draft trademark policy based on input from Wikimedia community members in an effort to develop a document that truly reflects the values of the Wikimedia community. Our goal with the new policy is to make it easy for community members to use the Wikimedia marks. In addition to making the policy more permissive, the WMF legal team is looking to make it clear and intuitive. The policy should be straightforward and easy for anyone to navigate when looking to use a Wikimedia mark. One way the legal team has sought to make the trademark policy more accessible is by applying various readability indices to determine the reading level needed to understand the text. The legal team tried to avoid legalese and strived to use short sentences and simple words. The current draft only requires a reading level of an average 12 or 13 year old. Lowering the readability score of the text will make it simpler to translate and, therefore, more accessible to international audiences. Another way the legal team has tried to make the policy more accessible is by developing a user-friendly summary. The summary highlights the most important points in the policy and directs users to relevant portions of the text for additional information. This summary, along with the improved readability and translatability, should make the draft much more accessible and ultimately usable. The team is also looking for alternative ways to communicate the information in the policy to reinforce the text. A few weeks ago, we partnered with legal information researchers Stefania Passera, Helena Haapio, and Margaret Hagan to organize a two-part Legal Design Jam at Stanford Institute of Design and the Embassy Network. The goal of these sessions was to brainstorm about how to make our trademark policy more user-friendly using colors, visuals and various information design methods. We brought together two groups of professionals and students with law, design, computer science and policy backgrounds to work on this problem. Both legal design sessions began with a presentation by Stefania Passera regarding different information design techniques that can improve the usability of legal documents. Yana Welinder, who is leading the trademarks work and the policy update in the legal team, then presented the trademark policy draft. She focused on community interests that drive the document to make sure that the legal design participants appreciated the importance and practicality of the document. The draft was divided into sections and reviewed in groups of four to five participants. Each group spent time discussing a portion of the draft, highlighting the key concepts and thinking about how those concepts should be visualized effectively. In the first session, the legal design participants identified that the user-friendly summary contained a complicated list of trademark uses that could be broken down into three main categories. The WMF legal team wanted to emphasize the ease with which we hope community members will be able to use the trademarks under the new policy. At the same time, the trademark policy should be clear when uses require a trademark license. The legal design participants chose to represent the different trademark uses in the summary with the traffic light colors that commonly indicate go (green), caution (yellow) and stop (red). Using this color scheme, we developed a shorter summary to indicate when trademark use does not require permission (green), when permission must be sought (yellow) and a few uses that are prohibited (red). We then used the same color-scheme in symbols throughout the policy to help readers navigate the document in the same way. The legal design participants also introduced well-known symbols to visualize other sections of the policy. For example, a warning sign was chosen to represent reporting of trademark violations and a pen to represent future revisions to the policy. We are mindful that some symbols and colors may not have the same meaning worldwide. Which is why we hope that the international Wikimedia community will help us adopt globally meaningful symbols as they review and discuss the policy during the consultation period that will begin soon. We are now wikifying the designs that were developed in the legal design sessions so that community members can discuss them on Meta-Wiki. Once that discussion opens, please join in and give your feedback about this work in the consultation on the policy draft. You can also leave your thoughts in comments on this blog in the meantime. What do you think about this process? Have we overlooked anything important? We look forward to getting the community’s feedback on this. Yana Welinder, Legal Counsel, Wikimedia Foundation Heather Walls, Communications Design Manager, Wikimedia Foundation Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. LDJ @ Stanford – 11 Oct | […] The ideas developed at the Jam will be presented first to the Wikimedia community for feedback around mid November. For now, read Margaret’s summary of the lessons learnt at the Stanford Jam, and Yana’s thoughts about designing user-friendly legal documents . […] LDJ @ The Embassy SF Report | […] The ideas developed at the Jam will be presented first to the Wikimedia community for feedback around mid November. For now, read Margaret’s summary of the lessons learnt at the Stanford Jam, and Yana’s thoughts about designing user-friendly legal documents . […] Welinder and Walls on the 2013 Legal Design Jams in Northern California | Legal Informatics Blog […] Welinder, J.D., LL.M., and Heather Walls, both of the Wikimedia Foundation, have posted a report on last month’s legal design jams in northern California, entitled Designing a user-friendly trademark policy for some of the world’s most recognizable […] Designing User-Friendly Legal Documents | […] so that the design can help convey information. My colleague Heather Walls and I recently wrote a blog post about what we’re doing in that respect. Together with Stefania Passera, Helena Haapio, and […] Thanks for doing this. I and my community need this policy so that we can host small community events with guidance on how to advertise ourselves as a grassroots community effort that complies with and sets a model for respect for trademark law. Reply to Lane Rasberry Hi Lane, Thanks for your comment! We have really tried to design the draft policy around making this type of work easier for community members. We will release it shortly and I’d love to get your thoughts on whether the draft addresses your concerns. […] You can read more about the project here: > Margaret’s summary of the lessons learnt at the Stanford Jam > Yana’s thoughts about designing user-friendly legal documents […] LDJ @ The Embassy SF | Legal Design Jam […] You can read more about the project here: > Margaret’s summary of the lessons learnt at the Stanford Jam > Yana’s thoughts about designing user-friendly legal documents […] (re)Designing #MedEd: Interpretation – Council of Emergency Medicine Residency Directors (CORD) Blog […] Image Credit: Wikimedia Blog […] Orientation Introduction – Picture Symbol Icon – Ben Morris […] A design team – (https://diff.wikimedia.org/2013/10/29/designing-a-user-friendly-trademark-policy/) […] This is awesome! Thank you for sharing. I hope you keep spreading the word about the work you are doing. Posted in LicensingTagged trademark policy, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/10/29/designing-a-user-friendly-trademark-policy/

cc40

Legal documents are intended to be precise and comprehensive. Unfortunately, they’re often not very accessible. Lawyers are used to communicating with other lawyers with jargon that is well-defined in

en

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/subscriptions/list/PHID-TASK-kvzxdsabzah3ojrhnk54/

cc40

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this

en

This commit no longer exists in the repository. It may have been part of a branch which was deleted.This commit has been deleted in the repository: it is no longer reachable from any branch, tag, or ref. Support offsets in prefix searching Authored on Nov 26 2014, 6:29 PM T75522: PrefixSearch should support paging demon committed rMW14cc116a4dde: Support offsets in prefix searching (authored by demon).Dec 2 2014, 4:56 PM2014-12-02 16:56:51 (UTC+0) Commit No Longer Exists This commit no longer exists in the repository. Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/rMW14cc116a4ddeafa2af57ad6349ffc13b57569a18

cc40

This commit no longer exists in the repository. It may have been part of a branch which was deleted.This commit has been deleted in the repository: it is no longer reachable from any branch, tag, or r

en

These days we are welcoming a new wave of candidates for Google Summer of Code and FOSS Outreach Program for Women (OPW) internships. Interested? Stop reading and hurry up! Or keep reading to learn why these free software mentorship programs are doing so much good. Since 2006, Wikimedia has mentored 32 GSoC students. From those, only one (3.13%) was a woman (accepted in 2011), and she didn’t stick around. This number is even lower than the general percentage of women accepted in GSoC 2012 (8.3%) although perhaps it is in line with the composition of our own tech community (data missing). Can we do better? We think we can. This is why we joined OPW last November. It was the first round open to organizations other than the GNOME Foundation, founders of the initiative. After 5 rounds of OPW, GNOME women are not an exotic exception anymore. It is too soon to evaluate results in the Wikimedia tech community, but the six interns we got during the 5th round delivered their projects in the areas of software development, internationalization, UX design, quality assurance and product management, and so far they are sticking around. We also learned some lessons that we are applying to the next internship programs. As we speak, several women are applying for Wikimedia in the current GSoC edition. A promising trend! But there is more positive change. Paid internships are like subcutaneous injections for a free software community: in just one shot you get a full time contributor dedicated to help you within a defined scope and amount of time, with the incentive of a stipend ($5,000). The lives of the injected contributors change in the new environment. They learn and they adapt to new situations. They acquire a valuable experience that will help them becoming experienced volunteers and better professionals. At least this is the goal. But the life of the community receiving the injection also should change for good with the arrival of these full time contributors. This is also the goal. So what has improved so far in our tech community? Mentorship programs require a good alignment of project ideas supported by the community and by available mentors. Thanks to the efforts of many, we have now a list of possible projects, including a selection of featured project ideas ready to start. The list includes proposals coming from different Wikimedia projects, Wikimedia Foundation-driven initiatives and MediaWiki features for third parties. These project ideas link to Bugzilla reports in order to keep track of the technical discussion, involving the candidates, the mentors and whoever else wants to join. Full transparency! We also provide basic guidelines for candidates willing to propose their own projects. All this has been done for the current GSoC and OPW round, but is potentially also useful in the context of other initiatives like OpenHatch, SocialCoding4Good, or Wikimedia’s Individual Engagement Grants. If you want to propose a technical project that could keep a person or team busy for 3–4 months, now you know where to start. Improving our Welcome carpet We are still learning how to attract newcomers. Each mentorship program brings a wave of newcomers willing to get up to speed as soon as possible. We are betting on the “the medium is the message” approach, giving as much importance to the proposals as to the participation and collaboration of the candidate in our regular community channels. But all this requires better landing surfaces in mediawiki.org. This pressure and the repetition of similar questions by newcomers have encouraged the creation or promotion of references such as Where to start, How to contribute and Annoying little bugs. We keep working on an easier introduction to our community through the fresh and work-in-progress Starter kit, a team of volunteer Greeters and other initiatives discussed at the new Project:New contributors. And you know what? Several former interns are involved! Diversity enters our agenda We believe that “a healthy mix of demographic and cultural characteristics everywhere throughout the movement is key to Wikimedia’s success.” Diversity is good for creativity and sustainability, which are primary goals of any free software community. Yet diversity in these communities tends to be quite limited, and our case is not an exception. We have mentioned the problem of male predominance, but there are other biases and types of discrimination that we would like to help leveling. What about working on other barriers caused by abilities, age, language, or cultural, ethnic, or economic background? Just like we are doing with OPW, we can start with programs for specific audiences that we can sync with mainstream activities like GSoC, increasing their diversity. Ideas are welcome. Quim Gil, Technical Contributor Coordinator (IT Communications Manager) Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in Gender gap, MediaWiki, Summer of code, Technology, WikiWomenTagged Google Summer of Code, OPW, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2013/04/26/floss-internship-programs-as-catalysts-for-richer-community-collaboration/

cc40

These days we are welcoming a new wave of candidates for Google Summer of Code and FOSS Outreach Program for Women (OPW) internships. Interested? Stop reading and hurry up! Or keep reading to learn wh

en

As we become more involved in the Wikimedia community, and more knowledgeable about its culture, tools and policies, we tend to forget how and why we came to join that community, and what hurdles we had to overcome to get where we are now. We tend to forget the frustrations we encountered while going through the documentation, or the confusion we experienced when faced with complicated tools and arcane processes. Once we’ve gotten used to them, we have little incentive to improve the system. It’s incredibly valuable for a community to be reminded of that newcomer experience. Not only does it help identify pain points of newcomers that the community can reduce, but it can also be an eye-opening experience that challenges long-established anti-patterns. This is true whether we’re talking about new editors on a Wikimedia wiki, or new tech contributors who want to improve the software and technical infrastructure. One goal of the Engineering community team at the Wikimedia Foundation is to facilitate the integration of new tech contributors. We do this through a variety of activities, which include for instance the organization and coordination of mentoring programs, like Google Summer of Code, the Outreach Program for Women and Google Code-in. Another way to make the first steps of new tech contributors easier is to improve the portals, to make sure the documentation stays up-to-date and to identify where newcomers stumble, get blocked or rage quit. In order to capture that newcomer experience and use it to improve our pipeline, we’ve asked Google Code-in students to write “discovery reports”, i.e. short candid essays outlining what surprised them during their first steps, whether good or bad. Their mission, which 13 students chose to accept and completed successfully, was: to explore MediaWiki’s and Wikimedia’s technical world; to write down their feelings, impressions, frustrations, pleasant and unpleasant surprises with the code, community and tools as they explored; to organize their notes into a short candid essay; to create an account on mediawiki.org and post their essay on their user page. Over the next few days, I’ll be posting a selection of their essays here, slightly edited for publication. We’ve already learned a lot, and I think there’s value in showing them to a wider audience. If you’re a newcomer to the MediaWiki and Wikimedia technical community, I encourage you to write a discovery report as well. Each contributor’s perspective is different, and each candid essay sheds light on new areas of our community in need of improvement. Your exploration can focus on a specific area (for instance: setting up a development environment, finding documentation about a specific part of the software, translating the software, etc.) or be more general. Make sure to drop me a note by e-mail or talk page so your essay doesn’t get lost in an obscure corner of the wiki. If you’re a more experienced member of our community, I hope those discovery reports will be useful to you, and will help us make it easier to welcome and guide new tech contributors. Technical communications manager, Wikimedia Foundation Read in this series: Seeing through the eyes of new technical contributors Tech discovery report: What is this Wikitech thing anyway? Through the maze of newcomer developer documentation A junior developer discovers MediaWiki Discovering and learning by asking questions A young developer’s story of discovery, perseverance and gratitude Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. Comments are closed automatically after 21 days. Posted in TechnologyTagged Tech discovery report, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. The search for The Sound of All Human Knowledge begins: Global contest aims to identify the first ever sound logo for Wikipedia and Wikimedia projects 13 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2014/03/25/seeing-through-the-eyes-of-new-technical-contributors/

cc40

As we become more involved in the Wikimedia community, and more knowledgeable about its culture, tools and policies, we tend to forget how and why we came to join that community, and what hurdles we h

en

other patches which used to be part of this task, but not anymore: use post-cache transform instead of splitting the parser cache: 399907 (core): Add 'unwrap' ParserOutput post-cache transform 399909 (CiteThisPage): Use 'unwrap' post-cache transform instead of setWrapOutputClass( false ) 399910 (MobileFrontend): Use 'unwrap' post-cache transform instead of setWrapOutputClass( false ), when available (CI issues reported as T186284) 399912 (TemplateStyles): Use 'unwrap' post-cache transform instead of setWrapOutputClass( false ) 399908 (core): Remove wrapclass from parser cache key 394369 (TemplateStyles): Cache processed stylesheets during the parse 393283 (MobileFrontend): ApiMobileView: Disable 'deduplicateStyles' ParserOutput::getText() transformation 393284 (core): ParserOutput: Add 'deduplicateStyles' post-cache transformation 393285 (TemplateStyles): Deduplicate embedded style rules post-cache transforms followup (not strictly related, but tech debt reduction for something that was introduced in part due to TemplateStyles): 393262 (core): Warn if stateful ParserOutput transforms are used 393263 (core): Hard-deprecate ParserOutput stateful transform methods (probably in a separate MW release) 352835 (core): Add mw-parser-output to indicators container (needs to be rewritten) 347442 (core): ResourceLoader: Add wildcard modules (should be reviewed by an RL maintainer; not TemplateStyles related) T200506: Previewing a non-style-only gadget that you already have enabled causes a syntax error T188443: Wrap indicators in mw-parser-output class T133410: Deploy TemplateStyles to WMF production T60291: load.php should check read permissions on private wikis (exposes content of wiki pages part of a module) T186390: Javascript preview feature broken when live previews are enabled T186284: MobileFrontend npm-run-lint-modules occasionally fails with message "Failed to walk" T186286: Wikibase selenium test is flaky T155813: Decide on storage and delivery method for TemplateStyles CSS T160563: Provide infrastructure for embedding styles in the content HTML with deduplication T160690: Be able to request a custom icon pack on-the-fly without bloating RL module registry There are a very large number of changes, so older changes are hidden. Show Older Changes Restricted Application removed a project: Patch-For-Review. · View Herald TranscriptNov 17 2017, 5:42 PM2017-11-17 17:42:27 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald Transcript • ggellerman added a subscriber: Tgr.Nov 17 2017, 5:44 PM2017-11-17 17:44:42 (UTC+0) Deskana added a project: Patch-For-Review.Nov 17 2017, 5:45 PM2017-11-17 17:45:39 (UTC+0) Anomie added a subscriber: Anomie.Nov 17 2017, 6:06 PM2017-11-17 18:06:27 (UTC+0) These patches only block TemplateStyles deployment if the decision in T155813 to not block TemplateStyles deployment on deduplication is being reversed. Further, after some of the discussion with @Krinkle on T160563, I'm actually leaning towards not needing these patches to do the TemplateStyles deduplication since RL modules are reportedly not expensive to load multiple times after all. But I haven't had time to write new code. Maybe next week, if I finish gerrit:380669, don't get reviews to start updating extensions, and don't have too much other code to review. That's not to say the patches are useless. https://gerrit.wikimedia.org/r/#/c/340768 is still useful for T112474, and https://gerrit.wikimedia.org/r/#/c/347442/ might still be useful for T160690. • ggellerman removed a subscriber: • ggellerman.Nov 21 2017, 10:55 PM2017-11-21 22:55:48 (UTC+0) Anomie added a comment.Edited · Nov 24 2017, 9:43 PM2017-11-24 21:43:29 (UTC+0) The new patches needing review are: 393260: ParserOutput: Add stateless transforms to getText() (Krinkle proposed this idea a while back) 393261: Use ParserOutput stateless transforms 393284: ParserOutput: Add 'deduplicateStyles' post-cache transformation - The patch to do the deduplication in core 393285: Deduplicate embedded style rules - TemplateStyles patch to use it 393283: ApiMobileView: Disable 'deduplicateStyles' ParserOutput::getText() transformation - To avoid breaking MobileFrontend's action=mobileview if the above are merged Krinkle updated the task description. (Show Details)Nov 28 2017, 8:40 PM2017-11-28 20:40:19 (UTC+0) • ggellerman added subscribers: • pmiazga, ovasileva, cscott.Dec 5 2017, 7:44 PM2017-12-05 19:44:25 (UTC+0) Thank you, @Anomie for the new patches for review! Could you please confirm what remaining work is? It looks to me that: get response from @cscott re: your response to concern from @Krinkle: "Parsoid and VE are the only things I can think of that might have use for them, depending on how they decide to process the page. Let's ask them." It's not clear to me what next steps are here. Is it to get review from @Krinkle or @Catrope ? Ask if @ovasileva can prioritize review from @pmiazga Anomie added a subscriber: • ggellerman.Dec 5 2017, 9:34 PM2017-12-05 21:34:03 (UTC+0) In T180817#3814081, @ggellerman wrote: get response from @cscott re: your response to concern from @Krinkle: "Parsoid and VE are the only things I can think of that might have use for them, depending on how they decide to process the page. Let's ask them." It's not clear to me what next steps are here. Is it to get review from @Krinkle or @Catrope ? Review from someone, anyway. They're good candidates. Ask if @ovasileva can prioritize review from @pmiazga Probably anyone could review that, it seems simple enough. • ggellerman added a comment.Dec 6 2017, 12:54 AM2017-12-06 00:54:30 (UTC+0) Thanks, @Anomie ! For https://gerrit.wikimedia.org/r/#/c/393285/ does the reviewer need to be a ResourceLoader maintaniner or could it be anyone? @cscott could you have a look at @Anomie 's question in https://gerrit.wikimedia.org/r/#/c/393284/? Anomie added a comment.Dec 6 2017, 4:30 PM2017-12-06 16:30:24 (UTC+0) In T180817#3814906, @ggellerman wrote: Thanks, @Anomie ! For https://gerrit.wikimedia.org/r/#/c/393285/ does the reviewer need to be a ResourceLoader maintaniner or could it be anyone? That patch has nothing to do with ResourceLoader. There's also now https://gerrit.wikimedia.org/r/#/c/394369/, which also doesn't have anything to do with ResourceLoader. • ggellerman added a comment.Dec 6 2017, 5:34 PM2017-12-06 17:34:31 (UTC+0) @Anomie Thanks for the clarification. I'm looking for reviewers for patches that don't involve ResourceLoader: • ggellerman added a comment.Dec 6 2017, 9:48 PM2017-12-06 21:48:44 (UTC+0) @Tgr has agreed to review: TheDJ awarded a token.Dec 7 2017, 2:41 PM2017-12-07 14:41:43 (UTC+0) Tgr claimed this task.Jan 9 2018, 5:54 PM2018-01-09 17:54:15 (UTC+0) Tgr added a project: Product-Infrastructure-Team-Backlog (Kanban). Iniquity mentioned this in T133410: Deploy TemplateStyles to WMF production.Jan 17 2018, 10:34 PM2018-01-17 22:34:16 (UTC+0) CKoerner_WMF added a subscriber: CKoerner_WMF.Jan 18 2018, 7:24 PM2018-01-18 19:24:59 (UTC+0) Tgr renamed this task from Review patches that block TemplateStyles deployment to Review outstanding TemplateStyles patches.Jan 30 2018, 12:37 AM2018-01-30 00:37:09 (UTC+0) Tgr updated the task description. (Show Details)Jan 30 2018, 11:21 PM2018-01-30 23:21:33 (UTC+0) Tgr added a comment.Jan 30 2018, 11:25 PM2018-01-30 23:25:10 (UTC+0) The task description contained a somewhat random selection of patches so I updated to include them all. Not sure about ResourceLoader: Add wildcard modules - that was a dependency for the now-abandoned Deduplicate embedded style rules. Is it still the plan to make TemplateStyles pages into RL modules eventually? Or are star modules something we consider nice to have in general, but not related to TemplateStyles anymore? Tgr updated the task description. (Show Details)Jan 30 2018, 11:26 PM2018-01-30 23:26:20 (UTC+0) Tgr moved this task from To Do to Doing on the Product-Infrastructure-Team-Backlog (Kanban) board.Jan 30 2018, 11:43 PM2018-01-30 23:43:03 (UTC+0) Anomie added a comment.Jan 31 2018, 1:04 AM2018-01-31 01:04:40 (UTC+0) Something that might be nice to have, but aren't needed here. Tgr updated the task description. (Show Details)Feb 2 2018, 12:32 AM2018-02-02 00:32:18 (UTC+0) Tgr updated the task description. (Show Details)Feb 2 2018, 1:03 AM2018-02-02 01:03:54 (UTC+0) Tgr updated the task description. (Show Details)Feb 2 2018, 2:52 AM2018-02-02 02:52:10 (UTC+0) Tgr updated the task description. (Show Details)Feb 2 2018, 6:49 PM2018-02-02 18:49:29 (UTC+0) Tgr changed the task status from Open to Stalled.Feb 5 2018, 1:27 AM2018-02-05 01:27:22 (UTC+0) Every patch is either merged, +1'd and waiting for a dependency, waiting for a review from an RL maintainer, or has an issue that needs to be fixed. Tgr moved this task from Doing to Blocked on the Product-Infrastructure-Team-Backlog (Kanban) board.Feb 5 2018, 1:27 AM2018-02-05 01:27:39 (UTC+0) • ggellerman added a comment.Feb 6 2018, 7:13 PM2018-02-06 19:13:18 (UTC+0) @Tgr How can I help? Would you like me to try to find RL maintainers to review patches under "accurate edit previews" in the description or is there somewhere else I should start? Thanks! Tgr updated the task description. (Show Details)Feb 11 2018, 7:17 AM2018-02-11 07:17:12 (UTC+0) Tgr added a comment.Feb 11 2018, 7:33 AM2018-02-11 07:33:58 (UTC+0) In T180817#3950055, @ggellerman wrote: @Tgr How can I help? Would you like me to try to find RL maintainers to review patches under "accurate edit previews" in the description or is there somewhere else I should start? Thanks! Yeah, https://gerrit.wikimedia.org/r/#/c/340768/ would be the next step (the other patch I can review). • ggellerman added a comment.Feb 12 2018, 7:05 PM2018-02-12 19:05:44 (UTC+0) Are either of you available to review https://gerrit.wikimedia.org/r/#/c/340768/ ? Thanks! • ggellerman added a comment.Feb 22 2018, 5:15 PM2018-02-22 17:15:42 (UTC+0) I checked with @Catrope who thought that you would be more qualified to review this patch: Do you have any time to take a look? Krinkle added a project: Performance-Team.Feb 23 2018, 9:15 AM2018-02-23 09:15:56 (UTC+0) • Imarlier moved this task from Inbox to Next: Goal-oriented on the Performance-Team board.Feb 26 2018, 9:27 PM2018-02-26 21:27:46 (UTC+0) Krinkle added a comment.Feb 26 2018, 10:44 PM2018-02-26 22:44:52 (UTC+0) In T180817#3964801, @ggellerman wrote: Are either of you available to review https://gerrit.wikimedia.org/r/#/c/340768/ ? Thanks! Yep, I can take this one. @ggellerman Just one thing I'd like before I review this, which is a short description of what this is needed for within TemplateStyles, and brief steps to being able to see the feature in action. E.g. apply this patch in core, and apply patch X (which one) of TemplateStyles, and then do X/Y to see the feature working. If the dependent code hasn't been written yet, then that's also fine, just let me know. I can still review it without that. Krinkle claimed this task.Feb 26 2018, 10:45 PM2018-02-26 22:45:06 (UTC+0) Anomie added a comment.Feb 26 2018, 10:54 PM2018-02-26 22:54:40 (UTC+0) TemplateStyles doesn't need that patch anymore. It would have been needed had we still been planning on using RL to load the styles (either directly or https://gerrit.wikimedia.org/r/#/c/347441/), but that's no longer the case. It's still useful for T112474: Allow previewing a specific page when editing site JS/CSS (e.g. Common.css, Vector.js), though. IIRC you can test it by editing something like MediaWiki:Common.css to do something obvious and previewing. There's also https://gerrit.wikimedia.org/r/#/c/340769/ to let MediaWiki-extensions-TemplateSandbox be used for such edits. • ggellerman added a comment.Feb 26 2018, 11:02 PM2018-02-26 23:02:23 (UTC+0) Will review priority and timeline with @Deskana on 2018-02-27 and any other questions with @Tgr and will get back to you. Thanks for clarification @Anomie Tgr added a comment.Feb 26 2018, 11:36 PM2018-02-26 23:36:06 (UTC+0) Oh, right, I completely forgot that the excludepage stuff depends on loading template styles as RL modules. So, since the TemplateStyles parser tag calls Parser::fetchCurrentRevisionOfTitle, that means it's already compatible with TemplateSandbox, right? Nevertheless, I think that patch is still highly valuable, as it makes it easier to test gadget changes (and changes to sitewide styles, which will be required as part of the TemplateStyles migration, so it's not completely unrelated). Though I might be biased as I was hoping to use this for T187749 :) Anomie added a comment.Feb 27 2018, 3:14 AM2018-02-27 03:14:14 (UTC+0) In T180817#4004190, @Tgr wrote: Oh, right, I completely forgot that the excludepage stuff depends on loading template styles as RL modules. So, since the TemplateStyles parser tag calls Parser::fetchCurrentRevisionOfTitle, that means it's already compatible with TemplateSandbox, right? Nevertheless, I think that patch is still highly valuable, as it makes it easier to test gadget changes (and changes to sitewide styles, which will be required as part of the TemplateStyles migration, so it's not completely unrelated). That's a good point. • ggellerman changed the task status from Stalled to Open.Feb 27 2018, 6:52 PM2018-02-27 18:52:51 (UTC+0) • ggellerman triaged this task as Medium priority. • ggellerman moved this task from Backlog to Doing on the TemplateStyles board. Tgr renamed this task from Review outstanding TemplateStyles patches to Review TemplateStyles patches related to previewing site CSS changes.Feb 27 2018, 9:16 PM2018-02-27 21:16:23 (UTC+0) Tgr updated the task description. (Show Details) Tgr mentioned this in T188443: Wrap indicators in mw-parser-output class.Feb 27 2018, 9:20 PM2018-02-27 21:20:21 (UTC+0) Tgr added a comment.Feb 27 2018, 9:25 PM2018-02-27 21:25:09 (UTC+0) Having a task for an unspecified and constantly changing number of patches is not great for project management so let's split this up and make the current task to be about CSS previews which was the most important remaining issue. As for the rest, 393263 (core): Hard-deprecate ParserOutput stateful transform methods is tech debt cleanup that doesn't really need a task; filed T188443: Wrap indicators in mw-parser-output class for 352835 (core): Add mw-parser-output to indicators container; and 347442 (core): ResourceLoader: Add wildcard modules is not related to TemplateStyles anymore but probably related to the OOUI-for-mobile project so it can be handled there. Tgr updated the task description. (Show Details)Feb 27 2018, 9:25 PM2018-02-27 21:25:54 (UTC+0) Krinkle added a comment.Feb 27 2018, 11:03 PM2018-02-27 23:03:38 (UTC+0) I agree that the excludepage functionality is still valuable. It transforms an existing MediaWiki core feature (preview of user js) which is implemented with hacks in various places, with something that more generic that acknowledges the need to be able to temporally replace the content of one or more wiki pages of a ResourceLoaderWikiModule during a preview. And as part of implementing that functionally, various bugs as a result of the old implementation being a hack, will naturally be solved and work as expected. Such as T112474, from 2015. However, I don't think that bug is currently formalised as a quarterly or annual priority, and it seems too big for as an "interrupt" task to take on at this point within the current quarter. I'd have to cancel or delay other work in favour of it. I think it makes sense for TemplateStyles, as a product, to focus on gadget previewing improvements, but I suggest getting that in for the next quarter and making sure Performance Team has time set aside for supporting on that feature, as it depends on coordination within ResourceLoader. The next quarter is only a few weeks from now, so it won't delay by much, but let's circle back to this at that time. That way, I'll be able to do the code review, but beyond that also better assess the expected impact on future maintenance of ResourceLoader, and better weigh the different design choices and options. I'd like to emphasise that I'm not worried about code quality, someone else could easily take over the review of this patch if that was the (only) concern. My main concerns are of long-term impact and about the API design fitting well within ResourceLoader's overall model. And for that, I need more time than I can spare in a few hours today or next week. Krinkle moved this task from Next: Goal-oriented to Backlog: Future Goals on the Performance-Team board.Feb 27 2018, 11:03 PM2018-02-27 23:03:46 (UTC+0) Tgr added a comment.Feb 27 2018, 11:20 PM2018-02-27 23:20:34 (UTC+0) See {T186391}, T60291: load.php should check read permissions on private wikis (exposes content of wiki pages part of a module) and T186390: Javascript preview feature broken when live previews are enabled for somewhat related discussion. • ggellerman added a comment.Feb 27 2018, 11:30 PM2018-02-27 23:30:28 (UTC+0) Thanks, @Krinkle ! Re: schedule- some time in the next few weeks would be good. No need to worry about finishing in the next week. • ggellerman moved this task from Doing to Backlog on the TemplateStyles board.Mar 27 2018, 6:12 PM2018-03-27 18:12:43 (UTC+0) LGoto added a subscriber: LGoto.Apr 2 2018, 8:12 PM2018-04-02 20:12:16 (UTC+0) @ggellerman Just checking on this - Does Reading Infra need to do anything now or are they ok to move this to Tracking? Thanks! • ggellerman added a comment.Apr 2 2018, 8:26 PM2018-04-02 20:26:40 (UTC+0) @LGoto I think that this is still with @Krinkle so moving it to Tracking on Reading Infra board makes sense to me. LGoto edited projects, added Product-Infrastructure-Team-Backlog; removed Product-Infrastructure-Team-Backlog (Kanban).Apr 2 2018, 8:34 PM2018-04-02 20:34:19 (UTC+0) LGoto moved this task from Needs triage to Tracking on the Product-Infrastructure-Team-Backlog board. • ggellerman added a comment.Apr 5 2018, 5:50 PM2018-04-05 17:50:51 (UTC+0) @Krinkle do you think that you'll have time to look at 340768 (core): Generalize ResourceLoader 'excludepage' functionality in Q4? Thanks! Krinkle moved this task from Backlog: Future Goals to Next: Goal-oriented on the Performance-Team board.Apr 5 2018, 5:51 PM2018-04-05 17:51:29 (UTC+0) • ggellerman added a comment.Apr 5 2018, 6:50 PM2018-04-05 18:50:16 (UTC+0) Krinkle moved this task from Next: Goal-oriented to Doing (old) on the Performance-Team board.Apr 10 2018, 5:36 PM2018-04-10 17:36:44 (UTC+0) Krinkle added a project: MediaWiki-ResourceLoader. Krinkle moved this task from Inbox to Accepted Enhancement on the MediaWiki-ResourceLoader board. • ggellerman moved this task from Backlog to Doing on the TemplateStyles board.Apr 11 2018, 4:57 PM2018-04-11 16:57:20 (UTC+0) Krinkle added a comment.Apr 16 2018, 9:51 PM2018-04-16 21:51:10 (UTC+0) Review is almost finished, but currently stalled as the review so far uncovered bug in ResourceLoader that needs to be addressed first, in order for the main patch to work as expected. I've submitted a patch to fix said bug, at https://gerrit.wikimedia.org/r/416619. This is pending review by @Anomie. Krinkle moved this task from Doing (old) to Blocked (old) on the Performance-Team board.Apr 16 2018, 9:52 PM2018-04-16 21:52:08 (UTC+0) • ggellerman added a comment.Apr 18 2018, 4:46 PM2018-04-18 16:46:21 (UTC+0) Thanks for the update @Krinkle ! @Anomie will you have a chance to look at this soon? Thanks! Anomie added a comment.Apr 18 2018, 6:03 PM2018-04-18 18:03:43 (UTC+0) Hopefully. It's already on my list. • ggellerman added a comment.Apr 18 2018, 6:11 PM2018-04-18 18:11:51 (UTC+0) Krinkle moved this task from Blocked (old) to Doing (old) on the Performance-Team board.Apr 23 2018, 8:22 PM2018-04-23 20:22:30 (UTC+0) Tgr updated the task description. (Show Details)Apr 25 2018, 7:52 AM2018-04-25 07:52:45 (UTC+0) Tgr closed this task as Resolved.Apr 25 2018, 10:16 AM2018-04-25 10:16:42 (UTC+0) Tgr awarded a token. Deskana moved this task from Doing to Done on the TemplateStyles board.Apr 25 2018, 10:25 AM2018-04-25 10:25:30 (UTC+0) • ggellerman added a comment.Apr 25 2018, 4:37 PM2018-04-25 16:37:18 (UTC+0) @Tgr would it make sense to remove: 347442 (core): ResourceLoader: Add wildcard modules (should be reviewed by an RL maintainer; not TemplateStyles related) from this ticket if it does not related to TemplateStyles? Thanks! Tgr added a comment.Apr 26 2018, 11:10 AM2018-04-26 11:10:30 (UTC+0) I don't think it matters much, now that it's resolved. • ggellerman added a comment.Apr 26 2018, 6:13 PM2018-04-26 18:13:27 (UTC+0) @Tgr - great news for TemplateStyles that the ticket is resolved :) That said, the Resolved status does not reflect state of 347442 (core): ResourceLoader: Add wildcard modules (should be reviewed by an RL maintainer; not TemplateStyles related) which is still open. So I would advocate for tracking that patch in a different ticket. Krinkle updated the task description. (Show Details)Apr 27 2018, 7:56 PM2018-04-27 19:56:20 (UTC+0) Krinkle updated the task description. (Show Details) • ggellerman added a comment.Apr 30 2018, 5:06 PM2018-04-30 17:06:07 (UTC+0) Thank you, @Krinkle ! Nirmos mentioned this in T200506: Previewing a non-style-only gadget that you already have enabled causes a syntax error.Jul 27 2018, 10:06 AM2018-07-27 10:06:29 (UTC+0) Aklapper removed a subscriber: Anomie.Oct 16 2020, 5:42 PM2020-10-16 17:42:01 (UTC+0) · Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T180817

cc40

other patches which used to be part of this task, but not anymore: use post-cache transform instead of splitting the parser cache: 399907 (core): Add 'unwrap' ParserOutput post-cache transform 399909

en

Manu Sporny: Agenda for today is light - just updates and future planning. The other thing we may want to put on the agenda is talking about the release some of digital bazaar's source code as a commercial product and to discuss a way to allow contributors to the project to revenue share, etc. ✪ Manu Sporny: Any other changes? ✪ Manu Sporny: There are currently four calls around web payments that are going on every week. The CG, IG, IG Use Cases Task Force, IG payment agent task force. ✪ Manu Sporny: All four of those are going on every week and we may want to scale these CG calls back particularly because we don't have as much attendance on these calls. ✪ Manu Sporny: We could scale back to once a month. ✪ Dave Longley: Once per month for Web Payments CG call is enough. [scribe assist by Manu Sporny] ✪ Manu Sporny: Of course we can always call for another meeting at any point if we feel that's necessary. ✪ Manu Sporny: Ok, let's do these once per month from now on. Most of the work will shift to Web Payments IG. ✪ Topic: Web Payments IG Update Manu Sporny: We have three major task forces in IG. I'm heading up Use Cases Task Force, the purpose is to create a Use Cases document. We've taken the CG Use Cases doc and handed it over to them to seed the work. We've got ISO 20022 use cases as well. ✪ Manu Sporny: A new standard 12812 coming out of X9 and some other use cases from X9. ✪ Manu Sporny: All these docs are getting integrated into a single Use Cases doc. We have those calls Thurs 9am EST, only W3C members may join the calls. The other task force is the Payment Agent task force. The Agent is a piece of software that runs payment activities for you on the web. Parallel to the User Agent (browser). The point is to figure out the basic architecture for the Payment Agent, what it does what it can access, etc. Two docs will be created from the task forces and fed into the roadmap doc which will talk about status of payments on the Web. The roadmap doc will also demonstrate what the IG thinks is possible, where the gaps are and what can be done. ✪ Manu Sporny: There is at least one more task force of interest. The Glossary Task Force's purpose is to make sure the language is aligned with the industry, we aren't inventing new terminology or if we are we put it somewhere so people know what we're talking about. So, everything is moving well in the IG, people are motivated, we're hoping to get some docs out in Q1 in 2015. ✪ Manu Sporny: Those will be first public working drafts. ✪ Manu Sporny: That's an update from the Web Payments IG, any questions? ✪ Topic: Planning for next several months Manu Sporny: Now that the IG is up and running, what should the CG do? Certainly it an help review the Use Cases and docs and all the things IG is working on, but we should also be focusing on some technical stuff as well. We moved the credentials work to another CG, we didn't want a distraction or people wouldn't care as much as it, etc. In hindsight, it's funny because the credentials CG has tons of interest lots of people working on things. The opposite of what was predicted is happening. ✪ Manu Sporny: That CG is very active. ✪ Manu Sporny: The credentials work will continue to happen in the Credentials CG, the question is what we do here to increase activity. We do have to talk about RDF Dataset Normalization. The credentials group is almost to the point that the RDF Dataset Normalization should be pushed to official W3C work. We did have a discussion w/one of the W3C staff contacts on a mailing list about digital signatures, etc. and there may be further discussion there. This CG can play a supporting role related to that, but either way that work will continue. ✪ Manu Sporny: Are there any ideas on what the CG should be focusing on primarily over the next couple of months? ✪ Dave Longley: I think work items that we have in the charter are all relevant, all of those things will be discussed in the IG. We can be semi-reactive to IG - fill in gaps in technology/ideas, put that information into the group. [scribe assist by Manu Sporny] ✪ Dave Longley: Follow what the IG is doing, feed information into that group. [scribe assist by Manu Sporny] ✪ Manu Sporny: One of the things that makes it really difficult is that the IG has a week delay on when their minutes are approved. So it's been difficult to let the CG know what's been going on. It's not a big deal in the long term, but by the time the CG reads the minutes, the IG has already moved on from the discussion. There's new stuff that has happened since then, so coordination may be hard. But I agree we could be semi-reactive to what's going on there. ✪ Manu Sporny: The commerce spec, the WebDHT stuff, etc. things that no one has picked up yet. ✪ Manu Sporny: Fully decentralized version of identity credentials over the Web, but the credentials CG will be working on that. ✪ Manu Sporny: We might want to talk about the source code stuff. I think it's fine to be reactive to the IG right now until they get a more stable direction on where they want to go. We could just make sure the CG is aware of the discussions the IG is having, copy/paste to the mailing list so people know what's going on. ✪ Brent Shambaugh: If we meet every month we'll be able to consolidate the last three weeks, which will help ✪ Manu Sporny: Maybe if the calls are only monthly that's less of a big deal. ✪ Brent Shambaugh: They'll be publishing minutes about what they've talked about? ✪ Manu Sporny: Kind of like the minutes we publish but not as clean/pretty, but there is a log of what was discussed. ✪ Brent Shambaugh: Is it structured like a CG but just different people? ✪ Manu Sporny: It's very like how we operate here, yes. They don't record the audio like we do here. But everything else is basically run like we do in this group. Everyone there is from a company that is from the financial industry or is an implementor, so there are more industry professionals in that group. ✪ Manu Sporny: So the general plan is to be reactive to IG's needs and the people in the IG can post as much as they can (once released) from the IG to the CG mailing list. ✪ Manu Sporny: Any other comments? ✪ Topic: Release of Payswarm Source Code Manu Sporny: We've been talking about this internally at Digital Bazaar for a while now. We want to make a reference implementation available so people can hack on things and test things out and that's hard to do if you have to build the whole thing from scratch. So we've been talking about possibly releasing source code. If we do this, a big if, we'll release under a commercial license, it's all DB's intellectual property but people can look at the source but DB retains all rights. That would be stage 1, stage 2 could be that we allow non-commercial use of the platform, so for anyone who wants to develop or test an idea out, or propose an update to the specs but needs an implementation they can use the platform to do that. If the entity/org/person isn't profiting off of the source code then they can use it. Stage 3 might be a profit-sharing mechanism. We want anyone that develops on this code to get paid for doing so. We think that's the healthiest way towards a good ecosystem and healthy platform. A certain percentage of revenue made by the software goes back into the community. Meaning if a dev adds a new feature to the product and a license deal occurs later then some of that revenue goes back to the developer -- where that dev doesn't have to work at DB, they can be self-employed, work at another company, etc. ✪ Manu Sporny: The idea is to create some kind of revenue sharing mechanism with the platform. Who knows where we're going from there. ✪ Manu Sporny: We want to do smart contracts at some point, in the group, and we want to dogfood the smart contract stuff, and if we're going to do that, we should do that on the core platform, the reference implementation. In the future, the way that devs end up getting paid will be that the payments are run through the platform and the percentages for who gets paid what would be split up through a smart contract. A program will pay people instead of some human run process. ✪ Manu Sporny: That's the proposal of an idea we're playing around with right now. ✪ Brent Shambaugh: [Missed] has been allowing different people to get paid when working on a project when they aren't directly working for the companies behind the projects. ✪ Brent Shambaugh: What about other things with people gaming the system, people are too humble/meek, etc. I guess it would really need to be established, before hand or something, how much something is actually worth. ✪ Manu Sporny: Yes, that's what we've been grappling with, and if we do this, we'd be doing this in a staged approach because it may be hard to get right. ✪ Manu Sporny: A really simple approach is adding/removing lines of source are worth some percentage of revenue, but perhaps too simple. The only way to track stuff is to look at lines of source committed added/removed. The other things like documentation, evangelizing the product, etc. are all valuable things but are more difficult to handle to begin with. We can reevaluate the algorithm every year to try and make sure people are compensated for things like that but it will take stages/work to figure out how to do it properly. Like the payments work, when we started this work everyone was saying it would be too hard, no one will join the work, etc. but we've made tons of progress in that area. We think the smart contract stuff is going to work as well, and trying to integrate it into the core part of our work may help. ✪ Manu Sporny: We're hoping to pull the community group into the discussion and start out naively and see how far we get (if we decide to do this). ✪ Manu Sporny: http://www.sensorica.co/ ✪ Manu Sporny: What we're trying to do is seed the community group with technology to talk about and we're trying to make sure that the CG folks get something out of it, a financial reward out of participating rather than the typical open source thing where other companies mostly benefit from that vs. the contributors getting paid. Not that we have anything against open source, we have plenty of open source libs and use it, but we'd like to reward people for working on financial software. ✪ Manu Sporny: Any other comments? ✪ Brent Shambaugh: I've been working on my own Use Cases; I reviewed a lot of payment companies back in March, I came up with a few new things. ✪ Manu Sporny: If you've got new ones let us know because we're integrating in the IG right now. ✪ Manu Sporny: Next call will be in January, first or second week. ✪ Created by the Web Payments Community Group. Shared with love under a CC-BY license. Thanks to our contributors.

https://web-payments.org/minutes/2014-12-03/

cc40

Manu Sporny: Agenda for today is light - just updates and future planning. The other thing we may want to put on the agenda is talking about the release some of digital bazaar's source code as a comme

en

⚓ T222562 Special:MobileDiff doesn't correctly handle diff=0 if the diff would cover multiple revisions When clicking the "all changes" diff link in an email notification and being taken to the mobile site (e.g. by clicking the link from a mobile device), if the diff would cover multiple revisions, the diff shown is with the next-older revision instead. Page "Foobar" has revisions 1, 2, 3, 4, and 5. I last viewed "Foobar" while logged in after revision 3 was saved. I get an email notification for the new edit when revision 4 is saved, and before I check it, revision 5 is also saved. I click the "all changes" link, expecting to get a diff that compares revision 3 (the last one I viewed) and revision 5 (the most recent one) Instead I get a diff that compares revisions 2 and 3. Note that this also happens if you click the link and view the diff on the desktop version of the site, and then click the "Mobile view" link in the page footer. T118706 Conduct heuristic evaluation of image upload and insert flow in VisualEditor T115858 Design improvements for mw.ForeignStructuredUpload.BookletLayout T115865 Insert image in content immediately after it's uploaded, skipping the "General settings" step T115864 Figure out if the description of the image can be used as the caption on-wiki T53032 When inserting an image, set its caption by default to be the Commons image description T12863 Links on commons upload summaries do not link to commons T5498 Image history is confusing T96384 Integrate file revisions with description page history T39534 Wikimedia Commons should support searching by color T39535 Wikimedia Commons should support filtering by color T19503 Provide metadata support on Wikimedia Commons T122038 Moving/Deleting a video file does not move/delete subtitles files, nor does it inform the file mover of their existence T135221 Make TimedText content an integral part of the File page T2167 Use a dedicated interface for adding meta-data like interwiki links, rather than wikitext T132072 Integrate page meta-data as a new content model revision slot for consistency and atomicity T51662 VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog T68108 [Epic] Store media information for files on Wikimedia Commons as structured data T252280 Improve Wikilabels UI T105518 Make Wiki Labels mobile compatible T104072 Implement single column diff option (from mobile app) T56140 Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot T174043 Deploy Multi-Content Revisions T203157 Make the spam whitelist its own slot T174022 Implement multi-content revisions T189220 Ensure that relevant extensions are MCR-aware T202763 Update extensions which customize content diff rendering T94370 Implement a mechanism that recognizes syntax errors of wikicode as a Huggle extension T57793 Scoring should perhaps take into account added text rather than all text T100082 Provide useful diffs to high-volume consumers of recent changes T56328 Provide intraline diff format in API action=compare T162210 [EPIC] Upstream MobileFrontend components to core and other extensions (tracking) T238507 MobileFrontend sometimes goes to diff page instead of pending changes review page T117279 [EPIC] Core should provide inline diffs as well as side by side (Move InlineDifferenceEngine into core / remove MobileDiff) T222562 Special:MobileDiff doesn't correctly handle diff=0 if the diff would cover multiple revisions T117279: [EPIC] Core should provide inline diffs as well as side by side (Move InlineDifferenceEngine into core / remove MobileDiff) Dinoguy1000 created this task.May 6 2019, 1:43 AM2019-05-06 01:43:02 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 6 2019, 1:43 AM2019-05-06 01:43:03 (UTC+0) Dinoguy1000 added a comment.May 6 2019, 1:46 AM2019-05-06 01:46:58 (UTC+0) Just to confirm, this also happens on Wikipedia. Compare https://en.wikipedia.org/w/index.php?title=Pilot_Mound_Township,_Fillmore_County,_Minnesota&diff=0&oldid=763996346 and https://en.m.wikipedia.org/wiki/Special:MobileDiff/763996346. The problem is that Special:MobileDiff doesn't properly handle the diff=0 case; e.g. https://en.wikipedia.org/w/index.php?title=Pilot_Mound_Township,_Fillmore_County,_Minnesota&diff=840470831&oldid=763996346 results in the correct mobile diff: https://en.m.wikipedia.org/wiki/Special:MobileDiff/763996346...840470831. Dinoguy1000 renamed this task from Special:MobileDiff compares the wrong revisions when clicking a multi-revision diff link to Special:MobileDiff doesn't correctly handle diff=0 if the diff would cover multiple revisions.May 6 2019, 1:48 AM2019-05-06 01:48:06 (UTC+0) nray added a project: Readers-Web-Backlog.May 6 2019, 8:05 PM2019-05-06 20:05:50 (UTC+0) ovasileva triaged this task as Medium priority.May 8 2019, 3:35 PM2019-05-08 15:35:48 (UTC+0) Jdlrobson added a parent task: T117279: [EPIC] Core should provide inline diffs as well as side by side (Move InlineDifferenceEngine into core / remove MobileDiff).Jul 8 2019, 8:54 PM2019-07-08 20:54:01 (UTC+0) Jdlrobson lowered the priority of this task from Medium to Low.Jul 8 2019, 8:57 PM2019-07-08 20:57:01 (UTC+0) Jdlrobson edited projects, added Readers-Web-Backlog (Tracking); removed Readers-Web-Backlog. Jdlrobson added a subscriber: Jdlrobson. The page has bugs but it would be in our interest to work out the future of this code before bug fixing further. Dinoguy1000 added a comment.Jul 8 2019, 9:34 PM2019-07-08 21:34:23 (UTC+0) Of course; I wasn't aware of any potential plans to retire MobileDiff when I filed this bug report. If it's just going away, then this probably isn't worth fixing. =) Jdlrobson moved this task from Backlog to Team: web on the MobileFrontend board.Jul 24 2020, 3:00 PM2020-07-24 15:00:34 (UTC+0) Jdlrobson edited projects, added Readers-Web-Backlog; removed Readers-Web-Backlog (Tracking).Jul 24 2020, 3:08 PM2020-07-24 15:08:36 (UTC+0) Jdlrobson changed the task status from Open to Stalled.Jul 27 2020, 10:39 PM2020-07-27 22:39:31 (UTC+0) Jdlrobson moved this task from Incoming to Tracking on the Readers-Web-Backlog board.Feb 19 2021, 9:14 PM2021-02-19 21:14:00 (UTC+0) Jdlrobson edited projects, added Readers-Web-Backlog (Tracking); removed Readers-Web-Backlog. Jdlrobson moved this task from Untriaged to Move to Backlog on the Readers-Web-Backlog (Tracking) board.Sep 15 2021, 5:16 PM2021-09-15 17:16:32 (UTC+0) Jdlrobson edited projects, added Readers-Web-Backlog; removed Readers-Web-Backlog (Tracking).Oct 19 2021, 8:51 PM2021-10-19 20:51:44 (UTC+0) Jdlrobson moved this task from Tracking to Tracking on the Readers-Web-Backlog board. Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T222562

cc40

⚓ T222562 Special:MobileDiff doesn't correctly handle diff=0 if the diff would cover multiple revisions When clicking the "all changes" diff link in an email notification and being taken to the mobile

en

"Like" token, awarded by Richard_Nevell_WMUK."Love" token, awarded by Jopparn."Mountain of Wealth" token, awarded by John_Cummings. There is an error causing many of the Wikidata:Tours to be non functional, meaning the information boxes do not appear in the correct places. This happens is Chrome, Firefox and Safari. These are many non finished tours because of this issue: Its something to do with the loading order maybe? Additionally overlays were disabled in 2017 (see T178224) I'm not sure if these have been enabled again, it would be great to have them working again if possible T170071 Documentation sprint @ Wikimania hackathon 2017 T90870 selfcontained projects around Wikidata (tracking) T187319 Documentation sprint @Hackathon 2018 T159216 [Hackathon doc sprint] Beginner documentation about Wikidata T164457 [Hackathon doc sprint] Overview of Wikidata Help:Contents T164458 [Hackathon doc sprint] Answer the question "How can I help on Wikidata?" T164459 [Hackathon doc sprint] Track the outdated information on Wikidata T164461 [Hackathon doc sprint] A step-by-step process for the Query Service T164462 [Hackathon doc sprint] Improve doc about arbitrary Wikidata access on Wikipedia T165730 [Hackathon doc sprint] Beginner documentation about constraint reports T165737 [Hackathon doc sprint] Wikidata front page design recommendations T165989 Update and maintain Wikidata:Introduction T213704 Wikidata Tours don't load correctly T203717 Create a tour about lexicographical data T242489 Create documentation on creating new Wikidata tours T243825 Create a Wikidata tour about Coordinates T243828 Create a Wikidata Tour for external identifiers T243829 Create Wikidata Tour for Administrative territory T243895 Create a Wikidata Tour for Properties T244468 Create Wikidata tour for 'inception' T244467 Create Wikidata tour for 'official website' T244469 Create Wikidata tour for 'add an image' T244747 Wikidata Tours: Stepping back shows next and previous steps at once T244994 Wikidata tours: Reconcile versions of MediaWiki:Guidedtour-lib.js T245143 Publish better version of Wikidata:Tours and add new tours T245347 Wikidata Tours: Clicking final "end" tour" button should redirect to Tours page T245630 Redo Wikidata Tours main page T246488 Find out which are the most common kinds of items and statement to know what to make tours for T246554 Create Wikidata Tours for most common kinds of items and statements T243957 Review Wikidata Glossary terms for readability T246555 Write a blog post about all the new tours T246814 Wikidata Tours pollutes Recent Changes T254008 Create Wikidata Tours for Lexemes T215875 Look at material needed for GLAM professionals to learn to contribute to Wikidata T215919 Investigate 4h: Wikidata Tours don't load correctly T223999 Wikidata Tours: User can reach a step where the tour popup needs to attach to an element which is not visible T217233 Implement Model Items on Wikidata T244747: Wikidata Tours: Stepping back shows next and previous steps at once T244994: Wikidata tours: Reconcile versions of MediaWiki:Guidedtour-lib.js T215919: Investigate 4h: Wikidata Tours don't load correctly T203717: Create a tour about lexicographical data T223999: Wikidata Tours: User can reach a step where the tour popup needs to attach to an element which is not visible T195713: Have an intro tour (No. 2) T178224: Tours are broken: TypeError There are a very large number of changes, so older changes are hidden. Show Older Changes Sebastian_Berlin-WMSE moved this task from Backlog to Watchin' on the User-Sebastian_Berlin-WMSE board.Feb 5 2019, 2:49 PM2019-02-05 14:49:10 (UTC+0) John_Cummings added subscribers: • johl, Lydia_Pintscher.Feb 9 2019, 6:49 PM2019-02-09 18:49:30 (UTC+0) @Lydia_Pintscher @johl is it possible WMDE could help with this? Its a fairly major blocker to new contributors learning the basics of Wikidata Sebastian_Berlin-WMSE moved this task from Watchin' to Soon... on the User-Sebastian_Berlin-WMSE board.Feb 11 2019, 9:04 AM2019-02-11 09:04:24 (UTC+0) John_Cummings added a subtask: T215875: Look at material needed for GLAM professionals to learn to contribute to Wikidata.Feb 12 2019, 9:59 AM2019-02-12 09:59:24 (UTC+0) Lydia_Pintscher added a project: Wikidata-Campsite.Feb 12 2019, 1:37 PM2019-02-12 13:37:59 (UTC+0) We'll have a look. Lydia_Pintscher triaged this task as Medium priority.Feb 12 2019, 1:38 PM2019-02-12 13:38:13 (UTC+0) Lydia_Pintscher moved this task from Incoming to Ready to estimate on the Wikidata-Campsite board. John_Cummings added a comment.Edited · Feb 12 2019, 1:45 PM2019-02-12 13:45:22 (UTC+0) In T213704#4947316, @Lydia_Pintscher wrote: We'll have a look. Great, thanks, let me know how I can help :) • Addshore mentioned this in T215919: Investigate 4h: Wikidata Tours don't load correctly.Feb 12 2019, 3:53 PM2019-02-12 15:53:13 (UTC+0) • Addshore moved this task from Ready to estimate to Blocked / Waiting / External on the Wikidata-Campsite board. Sebastian_Berlin-WMSE moved this task from Soon... to This Week on the User-Sebastian_Berlin-WMSE board.Feb 18 2019, 9:29 AM2019-02-18 09:29:55 (UTC+0) John_Cummings added subscribers: Sebastian_Berlin-WMSE, • Addshore.Feb 19 2019, 1:12 PM2019-02-19 13:12:39 (UTC+0) @Addshore and @Sebastian_Berlin-WMSE just wanted to flag you've both moved this task to your immediate to do lists in case you wanted to work together on it :) Sebastian_Berlin-WMSE added a comment.Feb 19 2019, 1:31 PM2019-02-19 13:31:34 (UTC+0) The fact that I put it in my "This Week" initially means that I will investigate this; I haven't worked with tours before, so I need to figure out what's going on. @Addshore, do you know how tours work and have time to work on this? If so, you're more qualified than me. Ladsgroup added a subscriber: Ladsgroup.Feb 19 2019, 1:39 PM2019-02-19 13:39:21 (UTC+0) I looked into this and these are the easiest way to reproduce the problem: Click on "Edit" as it's attached to it: Click on "add qualifier" as it's attached to it: Then you will see the window at middle of the screen while it should be attached to the property field. The reason that seems most likely to me is the race condition between wikibase javascript trying to re-render the DOM and guided tour javascript trying to hook into new DOM. This is not easily fixable as they are completely different things but we can just introduce a little bit delay into hooking into new DOM in the guided tour library and it would be okay since javascript here doesn't make any API calls but if we are hooking into something that will wait for API response, we will hit the same issue again. Let me run a test and make sure. Ladsgroup added a comment.Feb 19 2019, 1:47 PM2019-02-19 13:47:59 (UTC+0) Yes, my guess was correct and it's a race condition. This hack fixes it: https://test.wikidata.org/w/index.php?title=MediaWiki:Guidedtour-lib.js&diff=470003&oldid=460451 Sebastian_Berlin-WMSE added a comment.Feb 19 2019, 2:12 PM2019-02-19 14:12:56 (UTC+0) Eww, race conditions. Would it be feasible to do something with MutationObserver to not have to use timers? That is if I understand it correctly, that the element we want to attach to hasn't been added yet when we want to attach it. Sebastian_Berlin-WMSE added a comment.Feb 19 2019, 3:42 PM2019-02-19 15:42:03 (UTC+0) I did some experiments and I think this might work: I don't have the rights to edit Guidedtour-lib.js; @Ladsgroup, can you try replacing the timeout with the above snippet and see if it works? Lydia_Pintscher closed subtask T215919: Investigate 4h: Wikidata Tours don't load correctly as Resolved.Feb 21 2019, 8:50 AM2019-02-21 08:50:06 (UTC+0) John_Cummings added a comment.Feb 21 2019, 9:28 AM2019-02-21 09:28:17 (UTC+0) This comment was removed by John_Cummings. John_Cummings added a comment.Edited · Mar 6 2019, 10:34 PM2019-03-06 22:34:59 (UTC+0) @Ladsgroup and @Sebastian_Berlin-WMSE did it work? John_Cummings added a comment.Mar 14 2019, 12:39 PM2019-03-14 12:39:25 (UTC+0) I'm still seeing boxes in the wrong place :( Sebastian_Berlin-WMSE added a comment.Mar 14 2019, 12:44 PM2019-03-14 12:44:12 (UTC+0) My proposed code hasn't been added. Someone with the necessary user right needs to do this; I don't have those. John_Cummings added a comment.Mar 14 2019, 1:02 PM2019-03-14 13:02:36 (UTC+0) In T213704#5023783, @Sebastian_Berlin-WMSE wrote: My proposed code hasn't been added. Someone with the necessary user right needs to do this; I don't have those. Thanks for writing it :) Who has the power? How can we ask them nicely? John_Cummings added a project: User-John_Cummings.Mar 14 2019, 1:16 PM2019-03-14 13:16:52 (UTC+0) Sebastian_Berlin-WMSE moved this task from This Week to Waitin' on the User-Sebastian_Berlin-WMSE board.Mar 18 2019, 7:31 AM2019-03-18 07:31:25 (UTC+0) John_Cummings added a subscriber: MartinPoulter.Mar 20 2019, 11:14 AM2019-03-20 11:14:48 (UTC+0) @MartinPoulter (saw your post about Wikidata on Commons), could that be turned into a tour? John_Cummings added a comment.Mar 20 2019, 11:15 AM2019-03-20 11:15:51 (UTC+0) @Sebastian_Berlin-WMSE I think I've found someone who could do a code review, but I don't know how to answer his question, see https://www.wikidata.org/wiki/Wikidata:Project_chat#Code_review_request_to_fix_Wikidata_Tours John_Cummings added a comment.Edited · Mar 20 2019, 2:09 PM2019-03-20 14:09:57 (UTC+0) @Addshore @Lydia_Pintscher is there a process for getting a code review for something working on beta Wikidata? • Addshore added a comment.Mar 22 2019, 8:45 AM2019-03-22 08:45:12 (UTC+0) I'v got a bit lost in this ticket now. What is the extra bit of patching that we have? Where is it? :) It looks like perhaps this is already being solved in https://www.wikidata.org/wiki/Wikidata:Project_chat#Code_review_request_to_fix_Wikidata_Tours ? Pasleim added a comment.Mar 24 2019, 11:22 AM2019-03-24 11:22:30 (UTC+0) @Sebastian_Berlin-WMSE I implemented your patch on test.wikidata but it does not seem to work. Do you know how to improve it? Otherwise I think we can proceed with the hack by @Ladsgroup. Sebastian_Berlin-WMSE added a comment.Mar 29 2019, 9:46 AM2019-03-29 09:46:10 (UTC+0) It's hard to work on this without being able to test the code myself. Is it possible to setup my common.js to run the tour code in a way that I can experiment there? I had a look at that, but couldn't figure out how to do it properly. Alternatively if I could have the rights to edit the actual tour script, that could work too. Ladsgroup added a comment.Mar 29 2019, 9:47 AM2019-03-29 09:47:44 (UTC+0) In T213704#5068921, @Sebastian_Berlin-WMSE wrote: It's hard to work on this without being able to test the code myself. Is it possible to setup my common.js to run the tour code in a way that I can experiment there? I had a look at that, but couldn't figure out how to do it properly. Alternatively if I could have the rights to edit the actual tour script, that could work too. You can just put it in "User:Sebastian_Berlin-WMSE/common.js" Sebastian_Berlin-WMSE added a comment.Mar 29 2019, 9:56 AM2019-03-29 09:56:11 (UTC+0) In T213704#5051741, @Pasleim wrote: Otherwise I think we can proceed with the hack by @Ladsgroup. The problem with this solution is that it's quite fragile: if the delay for the other operation is longer than the timeout, you will still get the unwanted behaviour. On the other hand, increasing the timeout to prevent this means that the user will experience a delay, even when not necessary. The best solution I can think of is to use a callback for the other operation, but judging from previous comments, it seems that that code was to "far away" to do that. Sebastian_Berlin-WMSE added a comment.Mar 29 2019, 10:00 AM2019-03-29 10:00:00 (UTC+0) In T213704#5068924, @Ladsgroup wrote: In T213704#5068921, @Sebastian_Berlin-WMSE wrote: It's hard to work on this without being able to test the code myself. Is it possible to setup my common.js to run the tour code in a way that I can experiment there? I had a look at that, but couldn't figure out how to do it properly. Alternatively if I could have the rights to edit the actual tour script, that could work too. You can just put it in "User:Sebastian_Berlin-WMSE/common.js" Will that override the original tours script? I thought it would just add it on top, which probably wouldn't turn out great. John_Cummings added a comment.Apr 9 2019, 11:08 AM2019-04-09 11:08:47 (UTC+0) @Ladsgroup @Pasleim @Addshore please can you help with trying to make this work? We are really dependent on this working so we can have tours to onboard new people, both in general and for our project FindingGLAMs (trying to create a worldwide database of cultural heritage institutions on Wikidata) https://meta.wikimedia.org/wiki/FindingGLAMs Ladsgroup added a comment.Apr 9 2019, 7:12 PM2019-04-09 19:12:49 (UTC+0) Hey, I really like to implement @Sebastian_Berlin-WMSE's fix in Wikidata but I can't test it and my knowledge of frontend is not good enough to understand it and its implications (for example if all of supported browsers support the implementation). If another developer gives a virtual +2, I'll happily put it in Wikidata John_Cummings added a comment.Apr 9 2019, 7:47 PM2019-04-09 19:47:53 (UTC+0) @Ladsgroup thanks very much, do you know who would be the right person/people to ask about frontend who could assess it? Ladsgroup added subscribers: Jakob_WMDE, thiemowmde.Apr 9 2019, 10:07 PM2019-04-09 22:07:52 (UTC+0) I don't want to bother them but if they have time @Jakob_WMDE and @thiemowmde both have strong frontend knowledge. John_Cummings added a comment.Apr 10 2019, 9:01 AM2019-04-10 09:01:28 (UTC+0) Thanks @Ladsgroup , @Jakob_WMDE and @thiemowmde if there's any tasks I can swap you for or any other favours that would free up a bit of time to look at this please let me know (I'm a muggle with no programming skills) John_Cummings moved this task from Backlog to This week on the User-John_Cummings board.Apr 23 2019, 12:14 PM2019-04-23 12:14:10 (UTC+0) Tarrow added a comment.Apr 23 2019, 2:44 PM2019-04-23 14:44:47 (UTC+0) Just to update this ticket: As can be seen in https://test.wikidata.org/w/index.php?title=MediaWiki:Guidedtour-lib.js&action=history both the hack by @Ladsgroup and @Sebastian_Berlin-WMSE have been put on test.wikidata.org and "tested". Even with the latest code by @Sebastian_Berlin-WMSE the boxes are still not pinned to the right place. I guess an ideal solution would be to make it clear how to work on the guided tour code without having to edit the "live version". Second might be reverting to @Ladsgroup 's hack. I didn't actually have any joy just pasting a copy of Guidedtour-lib.js into my common.js. Looking in &debug=true I suspect that my common.js is loaded and evaluated before the tour code. Tarrow moved this task from Blocked / Waiting / External to Ready to estimate on the Wikidata-Campsite board.Apr 24 2019, 11:24 AM2019-04-24 11:24:47 (UTC+0) Moved back to ready to go since it's no longer blocked by the investigation task but the problem still exists, thiemowmde added a comment.Apr 24 2019, 3:53 PM2019-04-24 15:53:39 (UTC+0) I believe we run into a very similar issue in the tour we have in the Two-Column-Edit-Conflict-Merge extension, see T195713: Have an intro tour (No. 2) as well as the patch https://gerrit.wikimedia.org/r/456176. The issue was that all the positions have been calculated to early, directly after the page finished loading. The moment the positions became relevant (i.e. the user clicked a button and the next popup was shown), all the other elements on the page could have been moved, i.e. when the user resized the browser window in the meantime, or a lazy-loading gadget made parts of the page reflow. I guess something similar might happen here. I know some quite relevant parts of the Wikibase UI (term box, collapsing references and qualifiers) only show up after the basic page loaded. Personally, I'm not able to invest time on this, unless I'm instructed to do so. John_Cummings added a comment.Apr 24 2019, 9:04 PM2019-04-24 21:04:55 (UTC+0) In T213704#5135055, @thiemowmde wrote: I believe we run into a very similar issue in the tour we have in the Two-Column-Edit-Conflict-Merge extension, see T195713: Have an intro tour (No. 2) as well as the patch https://gerrit.wikimedia.org/r/456176. The issue was that all the positions have been calculated to early, directly after the page finished loading. The moment the positions became relevant (i.e. the user clicked a button and the next popup was shown), all the other elements on the page could have been moved, i.e. when the user resized the browser window in the meantime, or a lazy-loading gadget made parts of the page reflow. I guess something similar might happen here. I know some quite relevant parts of the Wikibase UI (term box, collapsing references and qualifiers) only show up after the basic page loaded. Personally, I'm not able to invest time on this, unless I'm instructed to do so. Thanks very much @thiemowmde, just so I understand, you would be able to fix this issue if you were given it as a task by your line manager? thiemowmde added a comment.Apr 25 2019, 10:32 AM2019-04-25 10:32:29 (UTC+0) you would be able to fix this issue if you were given it as a task by your line manager? It's open source software. People can change it and fix everything. The only question is how many resources people are willing to spend. In a worst-case scenario it might take months and a complete rewrite, but it's doable. At this point my guess on how many resources this will require is at good as yours. The discussions above suggest that the biggest issue with the current code is that it is not in a Git repository, but stuck on some wiki pages. I suggest to make it an actual MediaWiki extension and continue from there. But again, how many resources are available for such a project? John_Cummings added a comment.Apr 25 2019, 4:20 PM2019-04-25 16:20:59 (UTC+0) @thiemowmde, thanks, it seems like there are a few issues, please let me know if I missed something: Technical knowledge needed to write the fix for the issue (one way or another) The permissions to review the code and implement it from someone at Wikimedia DE (not sure who this is or if its more than one person?) The whole thing may benefit from being rewritten as a Mediawiki extension (but this isn't required to fix the issue we've raised) Is this broadly correct? thiemowmde added a comment.Apr 25 2019, 4:32 PM2019-04-25 16:32:06 (UTC+0) I'm somewhat confused what the relevance of these questions is, why they are asked, and who asks them. Are you a WMF or WMDE employee I'm not aware of? I don't know who "owns" the feature this ticket is about. It's on wikidata.org and falls into the Wikidata domain. But to me it looks more like the feature and the code behind it is a volunteer thing, and the volunteer Wikidata community would be the one who is responsible to maintain it. Permissions or technical knowledge have never been an issue, as far as I'm aware of. Both can be negotiated or build up if needed. MartinPoulter added a comment.Apr 26 2019, 10:54 AM2019-04-26 10:54:14 (UTC+0) I don't get the confusion. John has explained why he is asking these questions: an important feature of Wikidata, used in an ongoing project, is not working properly and he's just trying to find out what steps are necessary to get it fixed. You've been asked because you've been recommended as someone with relevant knowledge. He's just looking to take the next step to get the problem fixed, whatever that step is. Discussing his employer doesn't identify that step. WMDE-leszek moved this task from Ready to estimate to Needs Work on the Wikidata-Campsite board.May 7 2019, 12:44 PM2019-05-07 12:44:12 (UTC+0) WMDE-leszek moved this task from Needs Work to Ready to estimate on the Wikidata-Campsite board. WMDE-leszek moved this task from Ready to estimate to Needs Work on the Wikidata-Campsite board. WMDE-leszek added a subscriber: WMDE-leszek.May 8 2019, 12:59 PM2019-05-08 12:59:30 (UTC+0) Hi @Mrjohncummings and others. WMDE Wikidata engineers will try to help the problem with this Guided Tour. To be clear about it: WMDE is not going to be able to drive overhauling GuidedTours gadget, should this become the part of the solution. This seems like a slightly bigger task, which is beyond our current capacities. While what @Tarrow suggested above, to move the code to some other location that would allow for better maintainability is a great hint indeed, let's see if we could still help regardless. @Mrjohncummings @Sebastian_Berlin-WMSE: forgive me my ignorance when talking about Guided Tours. I admit I have had very little experience with it, hence might be naming things wrong, or miss details which should have been obvious. Given there has been quite some work around the issue, I'd like to take a step back and make sure I understand what is the current state, i.e. what is currently working wrong. I've just opened https://test.wikidata.org/w/index.php?title=Q1027&tour=wbqualifiers&data=ok and while going through a tour, I noticed that the when on the step 8, ie. the one saying "In the new property field, start typing in "point in time" and select it from the drop-down to add.", the tour window is not attached to the newly opened input field, to which I should be typing into. Windows related to prior steps, including Step 7's "Next click on the [add qualifier] button that appeared." are attached as expected. Does this seem a correct observation and I pin pointed the issue right? I've performed my tests using Firefox 66.0.3 NavinoEvans added a comment.May 8 2019, 10:56 PM2019-05-08 22:56:44 (UTC+0) @WMDE-leszek Thanks so much for taking a look at this! Yes, the issue you describe on step 8 in your example is the main problem to solve. To me the root of the issue is that the user is allowed to skip through steps without having actually completed the instructions. This means that the popup is trying to attach to an element that is not visible on the page. For this main issue, it seems that the only options are to either: Complete each step for the user automatically if they have not done so themselves. This will insure that the relevant elements are visible at each step. Prevent the user from skipping to the next step until they have completed the current step (e.g. by disabling the next button) Fixing with method 2 seems a lot simpler, albeit not as nice for the end user. I would also note that there is another issue that has been identified as a 'race condition'. This is what some of the previous fixes posted earlier in the thread are addressing. In this case, the element to attach to is visible but the somehow the popup is not still not attached. These are obviously connected but not the same problem. I have not experienced this second issue myself but others have reported it. I will do some further testing on this and post an example tomorrow with steps to reproduce. Hopefully that makes sense, fire away with any further questions or things you's like us to test and report back on. NavinoEvans added a comment.May 9 2019, 12:02 PM2019-05-09 12:02:48 (UTC+0) Just to confirm from my previous message after some further testing, there are in fact two separate issues: Bug 1 - User can reach a step where the tour popup needs to attach to an element which is not visible If you use only the "next" arrow to get to the next tour window, then you can reach later steps without having actually completed the task in each instruction window. If the skipped task was needed in order to show an element on screen for the next step, then the instruction window will default to the middle of the screen as the element it needs to attach to is not visible Load this tour - https://test.wikidata.org/w/index.php?title=Q1027&tour=wbqualifiers&data=ok On Step 6 "Add Qualifiers", do not complete the instruction to click on the "edit" button. Instead just click the "next" arrow. On step 7, you can see that the tour popup is just in the centre of the screen. It is trying to attach to the "Add qualifier" button, but this is not visible because the "edit" section was not been opened in Step 6. Bug 2 - Race between DOM loading and tour popup trying to attach to it This only happens in two situations: 1. If the very first step in the tour has an attached popup The page may not have been fully loaded when the Step 1 popup tries to attach to an element. You can see an example of this when you load this test tour - https://test.wikidata.org/w/index.php?title=Q1027&tour=wbtest&data=ok For me, the popup is not attached the first time the page loads (i.e. before it's cached). On subsequent reloads it works fine, but happens once again after I clear my cache 2. The user triggers the next step by clicking on a button which shows a new part of the page This can happen in all the same situations as Bug 1 above, but by completing the instruction instead of skipping it with "next" arrow. So, whenever the user gets to the next step by performing an action that will show/create elements on the page, the next popup attachment needs to race with the DOM being updated (next popup is trying to attach to DOM elements that are being rendered simultaneously) I can't repeat this issue reliably on any particular tour. Examples can be found in any tour steps that ask you to perform an action which shows new elements like "click 'edit' button", "click 'add qualifier' button", "click add labels". See Step 7 in this tour https://www.wikidata.org/w/index.php?title=Q16943273&tour=wbitems&data=ok Sebastian_Berlin-WMSE moved this task from Waitin' to Watchin' on the User-Sebastian_Berlin-WMSE board.May 10 2019, 7:14 AM2019-05-10 07:14:46 (UTC+0) John_Cummings added a comment.May 10 2019, 3:45 PM2019-05-10 15:45:30 (UTC+0) @WMDE-leszek if it is easier to have a call about this to discuss with myself and @NavinoEvans please let us know, we are both in the UK. WMDE-leszek added a comment.May 14 2019, 3:33 PM2019-05-14 15:33:07 (UTC+0) @Mrjohncummings apologies for the suboptimal response time. At WMDE we're in the middle of getting two bigger features through the door, which steals the most of my focus currently. I will personally have a look at those two bugs at Wikimedia Hackathon this weekend. I hope I will get some of my WMDE colleagues into the fun two. I believe I understand the description you were kind to provide above. Will any of you folks @Mrjohncummings @NavinoEvans @Sebastian_Berlin-WMSE happen to be in Prague this weekend? It would be fun to poke this thing together! John_Cummings added a comment.Jun 11 2019, 9:42 AM2019-06-11 09:42:08 (UTC+0) @WMDE-leszek amazing, thanks, how did you get on? Let me know if/how I can help Richard_Nevell_WMUK added a subscriber: Richard_Nevell_WMUK.Jun 18 2019, 10:41 AM2019-06-18 10:41:05 (UTC+0) Jopparn moved this task from This week to Watching on the User-John_Cummings board.Jun 19 2019, 10:27 AM2019-06-19 10:27:47 (UTC+0) Seantime added a subscriber: Seantime.Jun 19 2019, 2:12 PM2019-06-19 14:12:33 (UTC+0) John_Cummings added a subtask: T217233: Implement Model Items on Wikidata.Jun 25 2019, 11:25 AM2019-06-25 11:25:08 (UTC+0) John_Cummings added a comment.Jul 12 2019, 12:57 PM2019-07-12 12:57:24 (UTC+0) @WMDE-leszek this would be great feature to have working for Wikimania, we are having several GLAM workshops which include Wikidata and lack of good quality instructions is a real issue Rosalie_WMDE added a subscriber: Rosalie_WMDE.Jul 16 2019, 11:47 AM2019-07-16 11:47:45 (UTC+0) WMDE-leszek added a comment.Aug 13 2019, 12:59 PM2019-08-13 12:59:01 (UTC+0) @Mrjohncummings @NavinoEvans we've made some changes, which should hopefully help. I am not able to bring the changed files to test.wikidata.org due to lack of permissions. Would you mind try it yourselves? See the github gist linked T223999#5402050 WMDE-leszek added a comment.Aug 13 2019, 2:07 PM2019-08-13 14:07:11 (UTC+0) Following up quickly the comment above: Per https://test.wikidata.org/wiki/Special:ListUsers?username=&group=interface-admin pinging @Pasleim @Ladsgroup @Rosalie_WMDE: maybe you folks could help with bring changes linked in https://phabricator.wikimedia.org/T223999#5402050 to test.wikidata.org ? Rosalie_WMDE added a comment.Edited · Aug 13 2019, 3:52 PM2019-08-13 15:52:24 (UTC+0) @Mrjohncummings @NavinoEvans The tool behaviour on test.wikidata.org https://test.wikidata.org/w/index.php?title=Q1027&tour=wbqualifiers2&data=ok. Please note that for testing purposes the changes were added to wbqualifiers2 different from wbqualifiers. NavinoEvans added a comment.Aug 14 2019, 5:49 PM2019-08-14 17:49:23 (UTC+0) @WMDE-leszek @Rosalie_WMDE Thank you so much for this, for me the issues are completely resolved in the test version :-) @Mrjohncummings is that the same for you? Thanks again @WMDE-leszek for picking this up, you've really saved the day. we have quite a few missing tours to create so will make good use of it once it goes live! John_Cummings added a comment.Aug 14 2019, 7:01 PM2019-08-14 19:01:49 (UTC+0) @WMDE-leszek @Rosalie_WMDE @NavinoEvans it works for me as well :) Thanks so much for making it happen :) What needs to happen next to make it work on Wikidata? WMDE-leszek added a comment.Aug 15 2019, 9:02 AM2019-08-15 09:02:52 (UTC+0) All credit to @Rosalie_WMDE, she fixed it all! I was just a messenger. @Mrjohncummings: to get this to Wikidata, one of interface administrators (https://www.wikidata.org/wiki/Special:ListUsers?username=&group=interface-admin) would need to update Wikidata's MediaWiki:Guidedtour-lib.js to match the one from test. And the tour definition itself, I reckon: MediaWiki:Guidedtour-tour-wbqualifiers.js Or were there more files that you've been adapting on test.wikidata.org, @Rosalie_WMDE ? Rosalie_WMDE added a comment.Aug 15 2019, 10:56 AM2019-08-15 10:56:07 (UTC+0) In T213704#5415502, @WMDE-leszek wrote: All credit to @Rosalie_WMDE, she fixed it all! I was just a messenger. Thanks! I forward all the credit to the wikidata team. ;) Or were there more files that you've been adapting on test.wikidata.org, @Rosalie_WMDE ? No, you are right. WMDE-leszek closed subtask T223999: Wikidata Tours: User can reach a step where the tour popup needs to attach to an element which is not visible as Resolved.Aug 15 2019, 12:33 PM2019-08-15 12:33:36 (UTC+0) John_Cummings added a comment.Aug 15 2019, 1:57 PM2019-08-15 13:57:31 (UTC+0) @Rosalie_WMDE thanks very much again, @Ladsgroup could you press the magic buttons to make it work on Wikidata pretty please? Jopparn awarded a token.Aug 20 2019, 1:47 PM2019-08-20 13:47:53 (UTC+0) Richard_Nevell_WMUK awarded a token.Sep 5 2019, 9:35 AM2019-09-05 09:35:32 (UTC+0) • Addshore added a comment.Nov 6 2019, 1:40 PM2019-11-06 13:40:32 (UTC+0) A couple months down the line, any movement here? Is this done? John_Cummings added a comment.Nov 6 2019, 3:00 PM2019-11-06 15:00:04 (UTC+0) Can we wait to let me make some more tours to test? I've tried some things and it worked fine but I feel like I really need to test it • Addshore assigned this task to John_Cummings.Nov 6 2019, 3:00 PM2019-11-06 15:00:49 (UTC+0) Sounds good to me • Addshore moved this task from Needs Work to Blocked / Waiting / External on the Wikidata-Campsite board.Nov 6 2019, 3:01 PM2019-11-06 15:01:00 (UTC+0) thiemowmde removed a subscriber: thiemowmde.Nov 7 2019, 7:48 AM2019-11-07 07:48:36 (UTC+0) John_Cummings added a comment.Nov 8 2019, 9:04 AM2019-11-08 09:04:01 (UTC+0) • Addshore closed this task as Resolved.Nov 8 2019, 10:51 AM2019-11-08 10:51:27 (UTC+0) Jopparn moved this task from Watchin' to Done on the User-Sebastian_Berlin-WMSE board.Nov 18 2019, 10:53 AM2019-11-18 10:53:25 (UTC+0) John_Cummings removed a subtask: T165971: Create a Wikidata Tour / tutorial about ranks.Jan 30 2020, 10:40 AM2020-01-30 10:40:20 (UTC+0) NavinoEvans mentioned this in T244994: Wikidata tours: Reconcile versions of MediaWiki:Guidedtour-lib.js.Feb 12 2020, 12:01 PM2020-02-12 12:01:45 (UTC+0) NavinoEvans mentioned this in T244747: Wikidata Tours: Stepping back shows next and previous steps at once.Feb 12 2020, 12:04 PM2020-02-12 12:04:03 (UTC+0) Jopparn closed subtask T165902: Create a Wikidata Tour / tutorial about references as Resolved.Apr 21 2020, 1:50 PM2020-04-21 13:50:38 (UTC+0) Jopparn moved this task from Watching to Done on the User-John_Cummings board.Jul 31 2020, 12:06 PM2020-07-31 12:06:21 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T213704

cc40

"Like" token, awarded by Richard_Nevell_WMUK."Love" token, awarded by Jopparn."Mountain of Wealth" token, awarded by John_Cummings. There is an error causing many of the Wikidata:Tours to be non funct

en

Manu to create a page for broad categories for use cases and transfer mailing list use cases to that wiki page. Dave Longley, Manu Sporny, David I. Lehn, Brent Shambaugh Warning: Your browser does not support the HTML5 audio element, please upgrade. Manu Sporny: Today, we'll be trying to organize the use cases into something we can feed into the upcoming web payments interest group, then figure out how workshop input fits in, then get volunteers for use case work. The goal is a consistent, updated use cases document for the upcoming Web Payments IG work. ✪ David I. Lehn: Nope ✪ Topic: Organizing In-the-Field Use Cases Manu Sporny: Brent has done a great job getting all these use cases documented on the wiki. There's a lot of data there, brent has started summarizing some of the information there at the top, what we're trying to here is take this list and demonstrate that these are the use cases that are already supported by many players out there and then we want to find the most common use cases in the area, then we're taking use cases from the workshop which are more forward looking future use case sthat would be part of new standards on the web ✪ Manu Sporny: Brent can you talk about the current use cases you've documented? ✪ Brent Shambaugh: There's a highlights section at the beginning ✪ Brent Shambaugh: And it splits things into APIs, developers, technologies that allow for a prepaid card, cryptocurrencies, things that are based on the bitcoin technologies, some of them seem to be very similar with the functionality, there's also tech like prepaid card you may get in a store that you then can use online, ✪ Brent Shambaugh: Apps that makes your smartphone become lots of different credit cards, originally developed stripe technology for these credit cards ✪ Brent Shambaugh: Take this and put it in a phone, lots of fitting legacy technologies into more technical framework, then there are several techs that rely on card readers, they may have an API, or have a card reader you attach to your phone like square so you can accept payment like that ✪ Brent Shambaugh: Then you also have things where you get some kind of number you can pay with, e-cash for example, techs that use NFC, techs that use bluetooth low energy, and using a QR-code to pay with mobiles, like starbuck's ✪ Manu Sporny: Go back to techs associated with your credit card image, how do those work? ✪ Brent Shambaugh: You may take a picture of your credit card but it's in your app so you can use it as your credit card in a way ✪ Brent Shambaugh: So for example, you can take pictures of the cards and store them, then pay using those cards. ✪ Brent Shambaugh: That's something to look at again ✪ Brent Shambaugh: Subscription payments, set up, it continues to charge the card on a scheduled basis, there's stuff to do refunds, different options for that depending what your API is ✪ Brent Shambaugh: There is also automatic application of discounts, and APIs to list products for sale on a site. ✪ Manu Sporny: By list products you mean you can use the API and submit something to a store and your product will be listed on the store? ✪ Brent Shambaugh: It might be as simple as listing the item on a website, let me get an example... ✪ Brent Shambaugh: That's an example of listing products via an API. ✪ Brent Shambaugh: So conditional payments using some pre-determined agreement. ✪ Manu Sporny: So, in the future, if you could elaborate a bit more on the list products conditional payments and coupons and the rest of them in the list, it's hard to understand what the functionality provides, you can guess you can register a product with the store, but exactly ... what does the API look like and elaborate a bit, maybe a sentence or two... what it looks like is that these broad categories that you have up top with the ... a lot of these that you put each payment provider under could be reworded as use cases, the categories can be, for example, disputes within the API could be expanded to "a mechanism is provided to the customer to allow them to click a link to dispute a transaction after the transaction has occurred and that link is provided in the digital receipt at the time of sale" ✪ Manu Sporny: That's something we could work with, assuming that's how balanced, paypal, stripe, work... just reword it so that it matches what they do in the most generic way ✪ Manu Sporny: Make sense? ✪ Brent Shambaugh: Yes ✪ Manu Sporny: You've categorized each of these into generic techs and we could go further and make a generic use case, for example, for techs that let you save cards in the app, we could change that to "save a physical credit card into the application and then use that credit card information to make a payment online" ✪ Manu Sporny: That could be a use case ✪ Manu Sporny: The next step here might be to iterate through the broad categories at the top to transform these high level categories into a 2-4 sentence use case ✪ Brent Shambaugh: That could be helpful ✪ Manu Sporny: That's what we'll be using as input to the web payments interest/business group, they need to know that that use case is already supported by X, Y, Z payment processor, we don't have that now and if we don't then the work we're doing isn't clearly influenced by real world data ✪ Brent Shambaugh: There's also this that Natasha has updated: https://github.com/w3c-webmob/payments-use-cases ✪ Manu Sporny: Do you feel like these categorizations are complete or does more need to be done? ✪ Brent Shambaugh: More needs to be done, there's a lot of data here. ✪ Brent Shambaugh: There might be some more to look at, definitely ✪ Manu Sporny: I'm trying to figure out a way that we can easily divide and conquer on this work, when we were working in the microformats community many years ago, we built an app that would let you type out features and then for each product/website you'd go through and say whether or not the feature was supported, at the end you had a big database you could run stats on, but that's a project in and of itself ✪ Manu Sporny: What i'm saying is that at some point we're going to have to list all of these features in a way that allows to easily analyze the data, right now it's a big huge website, that's not a bad thing, that's just the first iteration which we need, but now we need each feature into a use case or set of use cases to figure out which features are most common ✪ Manu Sporny: For example, being able to go to a website and click a pay button to pay the merchant is the biggest feature that all the apps provide, but the important thing for that use case is that you're directed to another website, it doesn't happen in the merchant website ✪ Manu Sporny: From an operational/coding standpoint, that's important to note even if it is an implementation detail ✪ Manu Sporny: I think it would certainly help if you just took the broad categories at the top and created use cases out of them, and saying braintree, paypal, stripe, etc. all support this use case is very useful, then we have to make another pass through and determine whether or not there are missing use cases that are fairly/broadly supported by other payments players ✪ Manu Sporny: Does that make sense, Brent? ✪ Brent Shambaugh: Yes ✪ Manu Sporny: Anything else on the high level use cases? ✪ Manu Sporny: We'll be chatting with Andrew Mackie in 10 hours about this. He usually can't join these calls because he's on australian time which is the middle of the night for him right now. He's going to try and help a bit with these as well, so we should be on for that tonight ✪ Manu Sporny: Specifically with the web payments use cases, the ones that exist out there today, any concerns/questions before we move on? ✪ No concerns, group realizes that more work needs to be done and more categorizing and elaboration on each use case is needed. ✪ Topic: Organizing Web Payments Workshop Use Cases Manu Sporny: The use cases that came out of the Web Payments Workshop are here: http://lists.w3.org/Archives/Public/public-webpayments/2014Apr/0043.html ✪ Manu Sporny: While the web payments workshop was going on, we had a person that was specifically allocated to be a use case scribe, their primary duty at the workshop was to capture use cases, to listen to people and capture the use case that the person seemed to be trying to express. When we went and cleaned up all the workshop minutes we extracted these use cases and sent and email to the mailing list on each one of these use cases ✪ Manu Sporny: So i'll go down the email with those use cases to give people an idea of what's in scope and what's out of scope. ✪ Manu Sporny: Going back to the main outcomes of the workshop, there was a fairly big desire to work on identity, payment initiation, and digital receipt ✪ Manu Sporny: So that means things like coin and loop, while very interesting, the idea that you'd put all your credit cards on a device and be able to switch It's neat but doesn't have all that much to do with web payments, other than being able to express using a card who your payment provider is, a lot of the hardware based stuff seems to be out of scope, the hardware based stuff seems to supprot the payments process, when we're talk ing specifically about web protocol-level stuff. While 2-factor auth is very important for security purposes and 2-factor will play into the payments stuff, this group probably won't be working on it other than liaising with these groups to ensure you can do 2-factor on a payment if you need to. ✪ Manu Sporny: We have to take these use cases and say there are a number of sites that support some kind of hardware-based payment today, but that is more than likely not what the web payments group will be working on ✪ Manu Sporny: I'm going to go down the list and try and say if they are in scope for this first payment iteration document ✪ Manu Sporny: Each topic is listed before the use case to give some context about the use case ✪ Manu Sporny: So, for example - Topic: Alternative Currencies - Ven and HubCulture ✪ Manu Sporny: That would have something like this: Use Case: Bots that execute financial operations on behalf of users. ✪ Manu Sporny: This is about algorithmic trading/purchasing ✪ Manu Sporny: We're laying the ground work for that to happen, but the APIs for how to interface with or manage these bots are far out of scope for the first iteration ✪ Manu Sporny: Use Case: Personal vault can host information/assets and issue ids ✪ Manu Sporny: This is useful for various things (e.g. payments) ✪ Manu Sporny: That's in scope, the idea of a digital wallet was something that people were very interested in, and having a personal vault for your identity would be important ✪ Manu Sporny: That's an example that's certainly in scope for the first iteration based on output from the workshop ✪ Manu Sporny: Use Case: Managed access to personal identity/attributes as economically valuable things. ✪ Manu Sporny: This was about being able to store valuable assets (including credentials) in a payment system ✪ Manu Sporny: That's also in scope ✪ Manu Sporny: Hopefully that outlines how we'll determine what's in scope/what isn't ✪ Manu Sporny: Any questions? ✪ Brent Shambaugh: The bots, when you're using linked data, isn't that kind of part of the use case? Linked Data? ✪ Manu Sporny: We're building a foundation for the bot case w/ Linked Data, but saying we'll write a specification that details how you do automated (bot-based) purchasing is out of scope ✪ Manu Sporny: We're getting into a space where bots could buy and sell for us on our behalf, but i don't think we'll be creating a spec to standardize that in the next 2-3 years because there's no groundwork there. We're building the groundwork. ✪ Brent Shambaugh: Could you be using linked data so you could keep track of all your transactions on your different sites, so you could find out exactly how much tax you need to pay this year ✪ Manu Sporny: Yes, a bot could keep track of your buying/selling and because there's all that linked data that says there's sales that happened on ebay and where it was sold, which state sold/bought, etc. then it could file your taxes for you ✪ Manu Sporny: But we're not going to write a spec for that yet ✪ Manu Sporny: So what we need to do is put these use cases into buckets: "identity", "initiation of payment", and "digital receipt" ✪ Manu Sporny: Those seem to be the buckets where there was rough consensus, if use cases don't fit into the buckets then they are either unknown or out of scope for the first iteration ✪ Manu Sporny: There might be a fourth category "unknown" where we don't know how this stuff will fit into what we want to do, and we put those use cases into that and the web payments interest/business group can figure out where those fit ✪ Brent Shambaugh: I'm looking at the list, URI scheme for payments? ✪ Manu Sporny: Yes, yandex was saying it would be nice if there was a URL to say who you were paying, etc., just a payment link, which we actually wrote a spec for a while ago, and we already did the work on that and found out that you need to actually work on the protocol not just the link ✪ Manu Sporny: There are a lot of these use cases, there were a ton and we don't have the time to go through it on the call and other people will need to put them into those three buckets so we can talk about them in more detail ✪ Manu Sporny: Anything else on this particular agenda item? ✪ Brent Shambaugh: Who will work on this? just start working on it and put things into buckets and other people will jump in and discuss? ✪ Manu Sporny: Yeah, if you can start that it would be great, i was going to jump in and work on it, if you can get it started and put it on a separate wiki that would be helpful ✪ Manu Sporny: To store digital identity credentials online, hubculture, ven supports that ✪ Manu Sporny: Since you have a lot of this in your head already it would help if you started this ... create a wiki page and then start categorizing into the 3 categories ... there are actually 5: "identity", "payment initiation", "digital receipts", "we don't know where this goes, but it's in scope", and "this is out of scope for the next 3 years, etc" ✪ Manu Sporny: I could try just setting up that page today, i'll do that ✪ ACTION: Manu to create a page for broad categories for use cases and transfer mailing list use cases to that wiki page. Manu Sporny: I'll create the broad categories and start classifying a couple of them and then you can classify the rest, would that work for you, brent? ✪ Brent Shambaugh: Sure ✪ Topic: Use Cases Organizers/Volunteers Manu Sporny: I will help out where i can here at a high level, Andrew Mackie and Brent may also help, once we have them in pretty good shape we could .... we've got a use cases document that we've had for a very long time, it was one of the first docs we worked on ✪ Brent Shambaugh: Would that be a template? ✪ Manu Sporny: https://web-payments.org/specs/source/use-cases/ ✪ Brent Shambaugh: So it's more readable? ✪ Manu Sporny: I put the link to the use cases doc in IRC, we want to list what the use case is and then list what the requirements are to achieve that use case ✪ Manu Sporny: And the reason these use cases and requirements are so important is because we use that to determine if the tech we've created applies to 80% of the use cases then we're in good shape, if it's 20% then we've got a problem and we need to cut use cases down or reconsider what the spec is capable of doing ✪ Manu Sporny: For right now, brent, andrew, and myself will try to look at the use cases and boil them down, i think maybe we could pull in natasha from time to time to look at the use cases, but right now it looks like we need to make a first pass over it and make it a manageable set of use cases there are too many right now ✪ Manu Sporny: When people look at all of those use cases they have a hard time figuring out which ones we're working on and which we will push off to another time, so we need a much smaller list for those 3 buckets ✪ Manu Sporny: I would imagine that we'd go through 3-4 iterations here, first was what you did brent, surveying what's out in the field and getting input from web payments workshop, second iteration is categorizing into those 5 buckets, and then we can try and combine use cases to be more succinct in what we're trying to achieve ✪ Brent Shambaugh: https://github.com/w3c-webmob/payments-use-cases --- how to relate this ? ✪ Manu Sporny: We may even want to rate (during the 4th iteration) them as the level of desire for the feature, is it highly desired or would people not mind it not being in the first iteration, etc. ✪ Brent Shambaugh: This was updated quite recently after the workshop (link in IRC) natasha and others were working on this ✪ Brent Shambaugh: They have their own kind of use cases going on ✪ Manu Sporny: Yeah, we'll want to integrate that as well ✪ Brent Shambaugh: I wasn't sure where that was coming from, from the workshop or what ✪ Brent Shambaugh: Maybe what i was producing was a little confusing and Natasha wanted to clean it up a bit ✪ Manu Sporny: That's a pretty good document -- what natasha has ✪ Manu Sporny: We're probably going to want to pull all of these in as well ✪ Manu Sporny: They may or may not have better categories ✪ Manu Sporny: They've marked mobile-specific ones ✪ Manu Sporny: We're going to want to pull these in as well, just at least to make sure that we've got it clearly ... so we've got these use cases listed somewhere ✪ Manu Sporny: This is not an easy task to pull all this information in and put it together ✪ Manu Sporny: Ok, the final thing that we have here is the use cases output document ✪ Topic: Use Cases Output Document Manu Sporny: What we're shooting for is a use cases document ... and it may be that we're talking about three different use cases docs, identity, payment initiation, digital receipt, but we'll have them all in one document with 3 sections, then we'll put each use case in those sections and then we'll have a section at the very end for future use cases and that ... if we can give that to the Web Payments IG then they can determine whether or not ... they can focus on that and then whittle that list down to what they think is achievable in the first iteration of the technology ✪ Manu Sporny: Anything else about what our output should be as far as use cases are concerned? ✪ Manu Sporny: We've got about maybe a month to get this stuff together, it's not a lot of time, if it's half-formed we can still hand it off to the IG, but it's important that we have something for them to start with rather than them just having all this raw data ✪ Brent Shambaugh: I want to make sure we don't throw anything out ✪ Manu Sporny: There's going to be an aspect of that where we throw out a use case that should have been in there, but someone will hopefully mention that and we'll get it back in, we don't want to delete the data ... use cases would just fall into the future list (things to achieve after 3-4 years) and people can scan that list and help decide if we need to move them back into more immediate use cases to cover ✪ Manu Sporny: Anything else for the call today? ✪ Manu Sporny: Virginie and Wendy couldn't make it to discuss OWASP, we'll shift that to another telecon ✪ Created by the Web Payments Community Group. Shared with love under a CC-BY license. Thanks to our contributors.

https://web-payments.org:443/minutes/2014-04-16/

cc40

Manu to create a page for broad categories for use cases and transfer mailing list use cases to that wiki page. Dave Longley, Manu Sporny, David I. Lehn, Brent Shambaugh Warning: Your browser does not

en

Manu Sporny: The call for votes went out last Friday, we have six people voting so far, so six different organizations. We should send out a reminder this week to make sure everyone tries to vote. So it closes Oct 10th, which is the same day the Web Payments Activity vote closes. We're a couple of days into the vote, we've gotten really good feedback so far. Adrian, your feedback was really good. ✪ Manu Sporny: We'll may wait until after the vote to post all the feedback together. ✪ Manu Sporny: Any questions or concerns about the votes or use cases so far? ✪ Manu Sporny: We'll send out a reminder email to everyone in the group as well as letting every other org we've been in contact with (250+) to let them know what's going on with the two votes (Activity Charter and CG) ✪ Manu Sporny: It seems some orgs are completely unaware the vote is happening or they've missed it. ✪ Topic: Agenda Bashing for W3C TPAC Manu Sporny: We have eight hours of meeting time split over two days, two hours in the morning and two in the afternoon... ✪ Manu Sporny: There are ad-hoc meetings that can happen, so for example, on Monday and Tuesday there will be ad-hoc meetings, between the official Web Payments IG meeting. ✪ Manu Sporny: Two hours of IG meeting, 4 hours of ad-hoc meetings, and then 2 hours of IG meeting again. ✪ Manu Sporny: The Web Payments IG group is there on Tuesday, see link in IRC. ✪ Manu Sporny: There's a list of people who have registered, but since W3C was late getting the item there on the agenda, people missed it when they registered so we have to tell those people to go back and re-register. ✪ Manu Sporny: So 9am-11am is the start of the IG meeting from 11am-3pm ... we could create identity credentials group meetings as a break out session and then the afternoon is more IG meetings. ✪ Manu Sporny: I'm assuming that we're going to be doing payments use cases for most of the two days in the IG. ✪ Manu Sporny: I'm assuming we'll be doing credentials use cases in the identity meetings. ✪ Manu Sporny: I'm expecting a lot of time will be spent discussing use cases and the implications around those. ✪ Adrian Hope-Bailie: Am I wrong that there is time set aside on Mon and Tues? ✪ Manu Sporny: Is there anything else we should be focusing on other than use cases, such as a roadmap, doing demos, etc. ✪ Manu Sporny: There's a specific time set aside Mon and Tue for the web payments IG which is member only and that's 9-11am and 3-5/6pm. And that's for the official work. The non-official work can happen elsewhere. ✪ Manu Sporny: I think it would be smart for us to do one break out session for identity/credentials on one day and one for web payments on another day so people who aren't in the IG can attend. ✪ Manu Sporny: If there are orgs that want to attend but can't, then we might want to have another session (web payments) in the break out room. ✪ Adrian Hope-Bailie: Having some time set aside for credentials/identity is probabaly a good idea ✪ Adrian Hope-Bailie: +1 ✪ Manu Sporny: Adrian, will you be at TPAC? ✪ Manu Sporny: The W3C TPAC thing is a pretty important meeting to make sure we bring everyone up to speed on what's been going on, so what's the general question ... ✪ Adrian Hope-Bailie: I'm talking to my board about becoming a W3C member, and then attending W3C TPAC. [scribe assist by Manu Sporny] ✪ Dave Longley: Maybe we should do some demos. Show people the direction that this stuff could head in. [scribe assist by Manu Sporny] ✪ Dave Longley: IGs going to think about which WGs should be created. [scribe assist by Manu Sporny] ✪ Dave Longley: The IGs going to create WGs for the identity work? [scribe assist by Manu Sporny] ✪ Manu Sporny: Yes, that's the plan. ✪ Dave Longley: We need to make sure the W3C members in the IG are well aware that the identity work has been split off in the CGs [scribe assist by Manu Sporny] ✪ Dave Longley: They need to understand that we still need that work to happen officially. We should also talk about Roadmaps. [scribe assist by Manu Sporny] ✪ Dave Longley: We should talk about stuff that's out of scope as well. [scribe assist by Manu Sporny] ✪ Dave Longley: Like, for example, decentralized clearing solutions - out of scope for version 1. [scribe assist by Manu Sporny] ✪ Dave Longley: We should talk about a roadmap - we have a lot of these things on the radar, they have been discussed, there is a plan. We want the work to be done in an iterative process. [scribe assist by Manu Sporny] ✪ Manu Sporny: This is bringing up the concept that we should have a roadmap discussion ✪ Manu Sporny: Start with a brief background/history on what got us to where we are today. ✪ Manu Sporny: Do a quick overview of the use cases w/o discussion. ✪ Adrian Hope-Bailie: Identify which of the payments use cases are dependent on the credentials work and which ones aren't. [scribe assist by Manu Sporny] ✪ Dave Longley: We might want to mention a roadmap fairly early, people might have questions on things on the roadmap. Maybe we can direct the discussion on things that should be handled in first version of the work. [scribe assist by Manu Sporny] ✪ Dave Longley: We can discuss this as historical background - these are the things that came up, these are the ways they were split out, these are for future versions, etc. We could then go into use cases. We need to make sure that people don't feel this is set in stone, it's just how the work has evolved. [scribe assist by Manu Sporny] ✪ Manu Sporny: Ok, so first 2 hour chunk is: 1. Overview of W3C and the process, 2. History of Web Payments at W3C and CG work, 3. Where we are now, what we need to accomplish at W3C TPAC 4. Potential Road Map ✪ Dave Longley: Somewhere in there, we'll be talking about splitting use cases into version 1, and "later" [scribe assist by Manu Sporny] ✪ Dave Longley: We found that there are two general areas that we need to work on - payments stuff and identity stuff. [scribe assist by Manu Sporny] ✪ Dave Longley: The breakout session has more to do w/ whether or not people are available. [scribe assist by Manu Sporny] ✪ Manu Sporny: We need to have two break out sessions, identity+payments, for the people not deeply involved in the IG work. ✪ Manu Sporny: We hold the payments thing on Tuesday in the middle of the day, and that will be a basic overview for people not directly involved in the work; a high-level overview of what's happened over the last two days, here are some resources to track the work, etc. ✪ Manu Sporny: I was hoping the break out session would try and summarize what's happening in the IG. ✪ Manu Sporny: I think the only way we can schedule this is credentials break out on day one and web payments break out on day two. ✪ Manu Sporny: We could do identity on both Monday and Tuesday and payments on Wednesday. ✪ Dave Longley: As long as there are enough people for payments on wednesday, that aren't going to miss out - most of focus will be on payments in official group. There is less time for the identity stuff to be discussed. [scribe assist by Manu Sporny] ✪ Manu Sporny: That will give us four hours of time to do face-to-face on identity and around those two meetings there will be payments, 8 hours total on payments. ✪ Manu Sporny: On wednesday we could have a wrap up session for those who couldn't attend on Monday and Tuesday. ✪ Manu Sporny: The Internet Identity Workshop happens on Wednesday at the same time we could do a breakout session at TPAC, which is problematic. ✪ Dave Longley: Will there be a significant number wanting to attend a breakout session. [scribe assist by Manu Sporny] ✪ Dave Longley: Do you need to squeeze anything in on Tuesday? [scribe assist by Manu Sporny] ✪ Dave Longley: Only official members can come into IG meeting - all Web Payments talk will happen Mon/Tue? [scribe assist by Manu Sporny] ✪ Manu Sporny: Yes, W3C TPAC attendance is on a bell curve - most everyone will be there on Wednesday. ✪ Manu Sporny: So Payments IG meeting Mon/Tues, in between will be break out sessions for Identity/Credentials, and then quick overviews of the payments and identity work on Wednesday in break out session starting in the morning. ✪ Adrian Hope-Bailie: +1 ✪ Manu Sporny: I would imagine the Credentials stuff will be formatted in a way that matches the Payments stuff, so we'll do a history/etc. ✪ Manu Sporny: Intro to W3C, history of what got us here, we have a set of use cases, and here's the roadmap. ✪ Manu Sporny: The second day will be just use cases, focusing/refining, getting consensus. ✪ Manu Sporny: That will be it for the credentials stuff. ✪ Manu Sporny: Monday (intro, etc.), Tuesday (use cases for 2 hours) ✪ Manu Sporny: Are we going to be able to do demos at W3C TPAC? [scribe assist by Manu Sporny] ✪ Dave Longley: The current system we have would be simpler to demo than the new system that has regulatory stuff in it. [scribe assist by Manu Sporny] ✪ Manu Sporny: Monday, 2nd Web Payments IG session - maybe start off w/ use cases, then show demos. ✪ Manu Sporny: A lot of people will be introduced to these use cases for the first time. ✪ Manu Sporny: Because their orgs have prohibited involvement until official work starts. ✪ Adrian Hope-Bailie: How much time does it take to talk through and demonstrate the use case? [scribe assist by Manu Sporny] ✪ Adrian Hope-Bailie: There are a number of use cases that we can't demo yet, I'm sure. For illustration of what the use case is intended to address, a demo is very useful. [scribe assist by Manu Sporny] ✪ Dave Longley: Something that we should probably do is order the use cases in demo-able order. An alternative would be to discuss those use cases and show a demo once, that would allow people to understand how those use cases could be addressed. Then we could keep going through the demo, that would be one way to speed it up. [scribe assist by Manu Sporny] ✪ Adrian Hope-Bailie: If we show a demo, it's not the only way to solve the use case, it's one way to solve the use case. We might want to have discussion first and then show the demo. [scribe assist by Manu Sporny] ✪ Manu Sporny: If we show the demo first they may get overly hung up on the demo and if we do it last they might not get the use case until they've seen the demo, so tradeoffs. ✪ Adrian Hope-Bailie: Maybe this needs to be done on a case-by-case basis. [scribe assist by Manu Sporny] ✪ Manu Sporny: In general, there will be some set of demos, we don't know if they'll be done first or inline w/the discussion around the use cases. ✪ Manu Sporny: What might be helpful if we do a wrap up and say everything between the intro and the wrap up will be discussion around use cases and roadmap and things like that. ✪ Manu Sporny: Let's jump to Tuesday afternoon... what do we want to put on the agenda in terms of wrap up items are concerned. ✪ Adrian Hope-Bailie: What's required for the IG to continue? What are the expected steps after TPAC? [scribe assist by Manu Sporny] ✪ Manu Sporny: We also need to give everyone an intro to the specs we have so far, they are proposals, not set in stone, but someone has to start and provide the IP to start the standardization work (that's before the wrap up). ✪ Manu Sporny: We can talk about the next steps with Stephane Boyera and the two chairs of the IG. ✪ Manu Sporny: We can identify what we need to do and where we need to go, etc. and that's a group discussion, maybe committing to some kind of time line. We'll have a technical roadmap and a procedural time line -- and we can talk about what the next year looks like and what happens in the next year, what documents are expected to be delivered, etc. things like that. ✪ Manu Sporny: The other thing we should discuss in the wrap up is recruiting, more W3C members to participate in the work, we have to take recruiting pretty seriously because everyone's time is split so much in W3C so we need to get orgs to join and assign engineers. ✪ Adrian Hope-Bailie: Does anyone have a prioritized list of candidates? People to get involved, etc.? ✪ Manu Sporny: Yeah, I keep a list, maybe I should publish that on the wiki -- to list all the orgs we want to participate and our current status in outreach to them. ✪ Manu Sporny: We need to be careful not to get in the way of W3C communications. ✪ Adrian Hope-Bailie: It's important that we reach out to many of these organizations, especially the large ones, to make sure they know what's going on. [scribe assist by Manu Sporny] ✪ Manu Sporny: Agreed, and we've been doing that for the last three years which is one reason we've got so many people involved in the workshop, etc. ✪ Adrian Hope-Bailie: With the new /official/ group, we should do more outreach. [scribe assist by Manu Sporny] ✪ Manu Sporny: We're at the top of the hour -- let's take everything we've discussed on this call, I'll try and put a proposed agenda together and we can get feedback from the CG to refine/get objections and then pass to chairs and W3C staff. ✪ David I. Lehn: Thanks, bye. ✪ Evgeny Vinogradov: Bye ✪ Created by the Web Payments Community Group. Shared with love under a CC-BY license. Thanks to our contributors.

https://web-payments.org/minutes/2014-10-01/

cc40

Manu Sporny: The call for votes went out last Friday, we have six people voting so far, so six different organizations. We should send out a reminder this week to make sure everyone tries to vote. So

en

⚓ T44090 Filter effect Gaussian blur filter not rendered correctly for small to medium thumbnail sizes For some quite impressive examples refer to: This bug severely restricts the possibilities of graphic artist on Wikimedia projects since it basically renders the Gaussian blur filter completely useless since the final rendering of the MediaWiki software is rather arbitrary and comes near to gambling in the end. However Gaussian blurring is heavily used in modern SVG images since it allows to create outstanding effects like 3D effects and superior shading. Besides art created exclusively for Wikimedia projects, many free SVG images from other sources can't be used either since they are just not compatible, would need a lot of work to render correctly at all and wouldn't look nice in the end anyway. T112421 Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues) T84950 Thumbnail generation should happen via the same setup in the beta cluster and in production (tracking) T64835 Setup a Swift cluster on beta-cluster to match production T123512 beta swift labs instances requirements T140220 "UnderflowException from ... FancyCaptcha.class.php: Ran out of captcha images" at Special:CreateAccount T116816 beta cluster missing vips command needed to render tiffs and pngs, pnmtojpeg for DjVus T142289 Setup deployment-imagescaler host(s) in Beta Cluster T142255 Move mathoid to deployment-sca* hosts in Beta Cluster T107309 Test Mathoid in Jessie T142152 Move apertium to deployment-sca* hosts in Beta Cluster T107306 Package apertium (and dependencies) for Jessie T106385 [Tracker] Move Apertium packaging to Debian T142150 Move citoid to deployment-sca* hosts in Beta Cluster T107302 Package and test Zotero for Jessie T138778 Upgrade mariadb in deployment-prep from Precise/MariaDB 5.5 to Jessie/MariaDB 5.10 T147110 Delete deployment-db1 and deployment-db2 T118112: SVG images rendering without important parts in smaller sizes T46016: SVG fails to render properly due to several issues T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues) T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues) T118112: SVG images rendering without important parts in smaller sizes T11110: SVG element missing when image is downsized • bzimport raised the priority of this task from to Lowest.Nov 22 2014, 1:04 AM2014-11-22 01:04:06 (UTC+0) • bzimport added projects: Wikimedia-SVG-rendering, acl*sre-team, Upstream. • bzimport set Reference to bz42090. • bzimport added a subscriber: Unknown Object (MLST). Patrick87 created this task.Nov 14 2012, 1:24 AM2012-11-14 01:24:00 (UTC+0) Patrick87 added a comment.Feb 4 2013, 11:51 PM2013-02-04 23:51:31 (UTC+0) Since librsvg seems rather unmaintained and there seems to be no interest on side of the Wikimedia projects to consider using an alternative library on problematic SVGs I went on and fixed the underlying bug in librsvg myself. See https://bugzilla.gnome.org/show_bug.cgi?id=605875#c9 for the patch. Sadly over at Gnome bugzilla nobody seems to be maintainig bug reports for librsvg or implementing patches given there. Therefore it's stuck right now. If there are any Gnome developers around maybe you could have a look at it? Patrick87 added a comment.Aug 15 2013, 9:48 PM2013-08-15 21:48:27 (UTC+0) Sorry guys, but this bug hits nearly every image that uses the Gaussian blur filter effect. This is a serious limitation for SVG creation! Can we please include the patch I posted upstream [1] in our local copy of rsvg until bug 51555 is solved in one way or another? Aklapper added a comment.Jun 13 2014, 11:51 AM2014-06-13 11:51:52 (UTC+0) Bug 8566 has been marked as a duplicate of this bug. *** TheDJ moved this task from Backlog to Patch proposed upstream on the Upstream board.Mar 4 2015, 8:56 PM2015-03-04 20:56:31 (UTC+0) Perhelion reopened this task as Open.Mar 4 2015, 10:29 PM2015-03-04 22:29:27 (UTC+0) Perhelion closed this task as a duplicate of T11110: SVG element missing when image is downsized. Perhelion set Security to None. Perhelion merged a task: T11110: SVG element missing when image is downsized. Perhelion added subscribers: brion, TheDJ, Matanya and 4 others. Patrick87 added a comment.Edited · Mar 27 2015, 12:36 AM2015-03-27 00:36:32 (UTC+0) This is finally fixed upstream! librsvg 2.40.9 (just released) includes the fix. [1] When / how can we get this for Wikimedia Wikis? Given the severity of this bug, it would be great to not have to wait until it's in the official Linux distro used on WMF servers... Dzahn added a subscriber: Dzahn.Edited · Mar 27 2015, 5:24 AM2015-03-27 05:24:27 (UTC+0) [2015-03-02] Accepted 2.40.8-1 in experimental (medium) (Iain Lane) Dzahn added a comment.Mar 27 2015, 5:29 AM2015-03-27 05:29:40 (UTC+0) Dzahn added a comment.Mar 27 2015, 5:35 AM2015-03-27 05:35:16 (UTC+0) adding _joe_ since he built librsvg (2.40.2-1+wm1) per debian/changelog Dzahn added a subscriber: Joe.Mar 27 2015, 5:35 AM2015-03-27 05:35:37 (UTC+0) Krenair moved this task from Patch proposed upstream to Patch merged upstream on the Upstream board.Mar 29 2015, 8:25 PM2015-03-29 20:25:33 (UTC+0) TheDJ added a comment.Mar 29 2015, 9:11 PM2015-03-29 21:11:15 (UTC+0) This is fixed upstream ??? Awesome, this really was one of the biggest problems with librsvg so far. I'm sure the SVG users of the site will be super glad with this. Krenair moved this task from Patch merged upstream to Backlog on the Upstream board.Mar 29 2015, 9:17 PM2015-03-29 21:17:36 (UTC+0) Krenair added a subscriber: Krenair. I think I made a mistake. Have been trying to deal with the ridiculous backlog on the Upstream workboard, because no one bothers to use it properly. Aklapper added a comment.Mar 30 2015, 8:33 AM2015-03-30 08:33:34 (UTC+0) The upstream fix is in librsvg version 2.40.9 (which first needs to get packaged and shipped by the distribution running on WM servers). @Krenair: Whoever created that board, "Patch merged" etc is so vague (in upstream? in WM downstream?) that I have no idea when to move cards anyway so I personally ignore it. Krenair added a comment.Mar 30 2015, 8:40 AM2015-03-30 08:40:08 (UTC+0) In T44090#1161511, @Aklapper wrote: @Krenair: Whoever created that board, "Patch merged" etc is so vague (in upstream? in WM downstream?) that I have no idea when to move cards anyway so I personally ignore it. I think it's probably supposed to be merged upstream. Would make sense. I didn't make it though. I think it should also include other upstream resolutions (e.g. Resolved, declined). Can we rename those columns? TheDJ added a comment.Mar 30 2015, 5:30 PM2015-03-30 17:30:48 (UTC+0) I made it, and yes indeed Patch Merged was meant to indicate patch merged upstream. I figured we would add columns as we see need for them. Patrick87 added a comment.Edited · May 25 2015, 2:43 PM2015-05-25 14:43:06 (UTC+0) librsvg 2.40.9-2 is now in Debian testing. Is this enough to use it on Wikimedia servers? Matanya added a subscriber: akosiaris.Jun 16 2015, 4:29 PM2015-06-16 16:29:22 (UTC+0) @akosiaris please backport the package. TheDJ moved this task from Backlog to Patch merged upstream on the Upstream board.Jun 18 2015, 12:18 AM2015-06-18 00:18:07 (UTC+0) Menner added a subtask: T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues).Sep 14 2015, 6:39 AM2015-09-14 06:39:36 (UTC+0) Ricordisamoa added a subscriber: Ricordisamoa.Sep 14 2015, 8:43 AM2015-09-14 08:43:37 (UTC+0) Tgr mentioned this in T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues).Sep 14 2015, 11:45 PM2015-09-14 23:45:36 (UTC+0) Menner mentioned this in T46016: SVG fails to render properly due to several issues.Oct 17 2015, 6:35 AM2015-10-17 06:35:54 (UTC+0) matmarex mentioned this in T118112: SVG images rendering without important parts in smaller sizes.Nov 11 2015, 4:34 AM2015-11-11 04:34:35 (UTC+0) Dvorapa added a subscriber: Dvorapa.Nov 11 2015, 5:31 AM2015-11-11 05:31:55 (UTC+0) zhuyifei1999 merged a task: T118112: SVG images rendering without important parts in smaller sizes.Nov 11 2015, 9:28 AM2015-11-11 09:28:53 (UTC+0) zhuyifei1999 added subscribers: matmarex, zhuyifei1999, Steinsplitter. Dvorapa added a comment.Nov 20 2015, 7:52 PM2015-11-20 19:52:29 (UTC+0) BTW not happy this issue is marked as a low priority :/ Dvorapa raised the priority of this task from Lowest to High.Nov 22 2015, 6:46 PM2015-11-22 18:46:02 (UTC+0) Dvorapa lowered the priority of this task from High to Medium. Bawolff added a subscriber: Bawolff.Nov 22 2015, 6:50 PM2015-11-22 18:50:12 (UTC+0) BTW not happy this issue is marked as a low priority :/ Don't get too excited. Priorities are meaningless Dvorapa added a comment.Edited · Nov 22 2015, 7:04 PM2015-11-22 19:04:12 (UTC+0) In T44090#1823750, @Bawolff wrote: BTW not happy this issue is marked as a low priority :/ Don't get too excited. Priorities are meaningless I don't know, e. g. in GitHub issues the priority is sometimes really important. matmarex added a comment.Nov 23 2015, 10:10 PM2015-11-23 22:10:27 (UTC+0) As noted above, this issue has been fixed in the rsvg library we use to convert SVG images to PNG. To resolve this issue on Commons, our copy of the library has to be updated, which is tracked as T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues). There's nothing else to do here other than wait for that to be done, and verify that it was fixed afterwards. That task actually has seen some movement recently, please watch it for updates :) MoritzMuehlenhoff added a subscriber: MoritzMuehlenhoff.Jun 22 2016, 11:41 AM2016-06-22 11:41:27 (UTC+0) That bug is fixed on the new jessie image scaler using 2.4.16 (tested locally, it's not yet pooled into the set of active scalers in production). I have scaled https://cs.wikipedia.org/wiki/Wikipedista:Dvorapa/P%C3%ADskovi%C5%A1t%C4%9B/Broken_SVG_file#/media/File:Silverwiki_Hires.svg on the new and the present image scalers and put the results at https://people.wikimedia.org/~jmm/svg/ : new-1.png / new-3.png are the results with approx. 100 and 300 pixels on the new scaler old-1.png / old-3.png are the results with the existing scalers (The pixel sizes differ slightly to prevent hitting the cached results in favour of a fresh scaler run) MoritzMuehlenhoff claimed this task.Jun 22 2016, 11:41 AM2016-06-22 11:41:45 (UTC+0) MoritzMuehlenhoff closed this task as Resolved.Jul 4 2016, 2:45 PM2016-07-04 14:45:09 (UTC+0) The trusty-based image scalers have now been disabled, so I'm marking this task as resolved. MoritzMuehlenhoff closed subtask T112421: Update rsvg on the image scalers to 2.40.16 (to solve several SVG rendering issues) as Resolved.Jul 4 2016, 2:46 PM2016-07-04 14:46:37 (UTC+0) Dvorapa added a comment.Edited · Jul 8 2016, 10:46 AM2016-07-08 10:46:07 (UTC+0) @MoritzMuehlenhoff When could we await the fix to be in a release on Wikipedias (Czech)? In yesterday's MW release it wasn't (nothing changed). In the next one? MoritzMuehlenhoff added a comment.Jul 8 2016, 10:49 AM2016-07-08 10:49:53 (UTC+0) @Dvorapa This change is not a change in Mediawiki, but in the librsvg software component installed on the Wikimedia servers. As such, the change is already available on Wikimedia servers like Commons. Dvorapa added a comment.Jul 8 2016, 11:08 AM2016-07-08 11:08:53 (UTC+0) @MoritzMuehlenhoff I see, then it is only matter of time when it will arrive to other Wikis? MoritzMuehlenhoff added a comment.Jul 8 2016, 11:24 AM2016-07-08 11:24:49 (UTC+0) If any other Mediawiki installation wants to use the fixed version, it needs to install updated librsvg packages as well. For Debian jessie you can fetch the packages we use from https://people.wikimedia.org/~jmm/rsvg-backport-jessie/ and Ubuntu 16.04 provides recent enough packages as well. But maybe I'm misunderstanding you, are you referring to a specific file on Czech Wikipedia? Dvorapa added a comment.Edited · Jul 8 2016, 1:07 PM2016-07-08 13:07:32 (UTC+0) @MoritzMuehlenhoff I just want to fix this on Czech Wikipedia. The file is uploaded on Commons, but on the Czech Wikipedia the preview is still broken. This is the reason why we can't remake all our barnstars and badges on the Czech Wikipedia from PNG to SVG (it looks broken even if perfectly valid SVG 1.1 file) jcrespo added a subscriber: jcrespo.Jul 8 2016, 1:10 PM2016-07-08 13:10:00 (UTC+0) @Dvorapa I see the files ok, please check your browser cache. Dvorapa added a comment.Jul 8 2016, 1:14 PM2016-07-08 13:14:02 (UTC+0) @jcrespo I see, thank you, it must be from today, because yesterday purging server and browser cache didn't help TheDJ added a comment.Jul 8 2016, 1:14 PM2016-07-08 13:14:29 (UTC+0) @Dvorapa The confusion we are seeing here is probably a bit logical. The issues is fixed, BUT any image that is affected will have to be manually purged. You can easily do this, by going to the file description page on commons and added "?action=purge" at the end of the URL. Dvorapa added a comment.Jul 8 2016, 1:38 PM2016-07-08 13:38:02 (UTC+0) @TheDJ I see, thank you JoKalliauer added a subscriber: JoKalliauer.Jan 20 2018, 3:21 PM2018-01-20 15:21:47 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T44090

cc40

⚓ T44090 Filter effect Gaussian blur filter not rendered correctly for small to medium thumbnail sizes For some quite impressive examples refer to: This bug severely restricts the possibilities of gra

en

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/rSVN40961

cc40

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this

en

In T220235: Migrate Beta cluster services to use Kubernetes it was decided to use plain Docker VMs for services that run on the production Kubernetes cluster. Given that the core MediaWiki application is moving to Kubernetes in the future (MW-on-K8s) and we have more and more services that MediaWiki depends on I believe it's a good idea to at least revisit that decision. Beta cluster currently runs some services in Docker containers dedicated VMs (deployment-docker-*) and a few in the legacy deployment-sca[01-02] cluster running Jessie and with Puppet totally broken due to production setup changes. New services are deployed and existing ones updated rarely if at all. Resource and implementation wise I am unfortunately not sure how feasible this is. The project is almost out of Cloud VPS quota (T257118) plus setting up and maintaining a Kubernetes cluster and services running in it requires a considerable amount of time which I'm not sure who would put it into this project. T53494 Use Beta cluster as a true canary for code deployments (epic) T87220 Minimize infrastructure differences between Beta Cluster and production T276650 Re-consider setting up a Kubernetes cluster on the Beta cluster T283030: Provide a hosted testing environment for security review if needed T276624: Delegate beta.wmcloud.org and svc.deployment-prep.eqiad1.wikimedia.cloud DNS zones to deployment-prep T254917: Implement API Gateway solution for deployment-prep T218729: Migrate deployment-prep away from Debian Jessie to Debian Stretch/Buster T196662: Set up LVS in beta like prod T215217: deployment-prep: Code stewardship request T220235: Migrate Beta cluster services to use Kubernetes T257118: Beta cluster has reached its quota taavi created this task.Mar 6 2021, 7:34 AM2021-03-06 07:34:27 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 6 2021, 7:34 AM2021-03-06 07:34:27 (UTC+0) taavi added a parent task: T87220: Minimize infrastructure differences between Beta Cluster and production.Mar 6 2021, 7:34 AM2021-03-06 07:34:57 (UTC+0) Legoktm added a comment.Mar 6 2021, 7:41 AM2021-03-06 07:41:17 (UTC+0) There is some discussion at T215217#6610236 that is related to this. taavi mentioned this in T218729: Migrate deployment-prep away from Debian Jessie to Debian Stretch/Buster.Mar 6 2021, 9:31 AM2021-03-06 09:31:22 (UTC+0) Krinkle updated the task description. (Show Details)Mar 6 2021, 10:55 AM2021-03-06 10:55:45 (UTC+0) taavi mentioned this in T254917: Implement API Gateway solution for deployment-prep.Mar 20 2021, 10:58 AM2021-03-20 10:58:55 (UTC+0) taavi updated the task description. (Show Details)Mar 20 2021, 4:20 PM2021-03-20 16:20:49 (UTC+0) taavi mentioned this in T276624: Delegate beta.wmcloud.org and svc.deployment-prep.eqiad1.wikimedia.cloud DNS zones to deployment-prep.Mar 20 2021, 4:49 PM2021-03-20 16:49:27 (UTC+0) RhinosF1 added a subscriber: RhinosF1.Mar 22 2021, 5:56 PM2021-03-22 17:56:47 (UTC+0) taavi mentioned this in T278641: Migrate deployment-prep away from Debian Stretch to Buster/Bullseye.Mar 28 2021, 8:59 AM2021-03-28 08:59:15 (UTC+0) Krenair added a subscriber: Krenair.Apr 6 2021, 10:51 PM2021-04-06 22:51:06 (UTC+0) taavi added a comment.Apr 12 2021, 5:16 PM2021-04-12 17:16:34 (UTC+0) I chatted about this on IRC with some people some time ago, the main takeaways basically were: Something needs to be done at some point, since a) things will break when MW-on-K8s becomes reality and b) the current solution for services is not ideal We're not sure if we should improve the current docker thing or to make a k8s cluster and tooling for it The overhead for a small cluster isn't that big, but that wouldn't be prod-like(TM) it's pretty minimal. for PAWS we are running the etcd nodes and k8s control nodes collapsed together. So it's like 3 small instances (plus a proxy, can be just a haproxy node or two or a full-blown LVS setup) https://openstack-browser.toolforge.org/project/paws setting up a cluster isn't a problem, building and maintaining the tooling to semi-automatically maintain it and the services running in it are a problem I suspect to make informed decisions someone might need to sit down and figure out how easy it is to take prod's k8s setup and apply the equivalent inside labs, and figure out what ongoing maintenance is needed, what is needed to keep up with prod, etc. @Krenair / @Legoktm / other interested parties: could we do that at some point? during the remote hackathon maybe? Jdforrester-WMF mentioned this in T283030: Provide a hosted testing environment for security review if needed.May 17 2021, 7:16 PM2021-05-17 19:16:27 (UTC+0) Legoktm added a parent task: T286298: Set up Shellbox for Beta cluster.Jul 7 2021, 5:48 PM2021-07-07 17:48:54 (UTC+0) Legoktm removed a parent task: T286298: Set up Shellbox for Beta cluster.Jul 7 2021, 6:13 PM2021-07-07 18:13:03 (UTC+0) hnowlan added a subscriber: hnowlan.Sep 22 2021, 9:51 AM2021-09-22 09:51:27 (UTC+0) TheresNoTime added a subscriber: TheresNoTime.Jun 1 2022, 4:29 PM2022-06-01 16:29:53 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T276650

cc40

In T220235: Migrate Beta cluster services to use Kubernetes it was decided to use plain Docker VMs for services that run on the production Kubernetes cluster. Given that the core MediaWiki application

en

As a part of the switch to a new PDF renderer, we would like to customize and update our styles for books. Books must contain the following elements: Table of contents with page numbers Selecting a section from the table of contents will navigate the user to the corresponding section within the book All article images and captions Links to pages linked from the article (blue links and external links) The references for each article from the book will appear at the end of the article Each article must begin on a new page Text and image sources, contributors, and licenses at the end of each book Book cover will be a single page. It will have following data points number of total pages inside the book The cover page will be Page Number 0 Book index is used to give a more book like experience. It will have Following elements Chapter name if it exists (ref to diff mocks for chapterless index) Name of the article with number of page it will be on H2s of the article with corresponding page numbers we won't include H3, H4, H5, H6 in the book index Index will be Page number 1 for the book Spec for chapterless index Spec for index with chapters Incorporate new print styles work into individual article Refer to the entire spec for the single article design One major difference [VIMP] We show wikipedia wordmark on the first page of individual articles. If the article is part of the book, we won't show wordmark on first page of the article, we will use that space to show 2 data points Article x of y If the chapter name doesn't exist, it will just say "Article x of y" Spec for article header with chapters Spec for article header without chapters Page number and article name on every page Page number will be printed under a horizontal line, it will be center aligned Spec for page number List of text and image contributors T150871 [EPIC] (Proposal) Replicate core OCG features and sunset OCG service T186740 [EPIC] It should be possible to print a book using the Proton service T171832 Deploy new book renderer to all projects T171833 Deploy new book renderer to all projects side by side with OCG T171836 Apply new print styles for books T167955 Create PDF styles for books T173014 Security review of pdfrw T171836: Apply new print styles for books T135643: Show tables in pdfs (#9) T184772: [EPIC] Determine next steps with books functionality T175853: [Spike 16hr] Investigate the ability of Python wrapped headless Chromium to render large books ovasileva created this task.Jun 15 2017, 11:22 AM2017-06-15 11:22:33 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 15 2017, 11:22 AM2017-06-15 11:22:33 (UTC+0) ovasileva triaged this task as High priority.Jun 15 2017, 11:22 AM2017-06-15 11:22:43 (UTC+0) TheDJ added a subscriber: TheDJ.Jun 15 2017, 3:04 PM2017-06-15 15:04:34 (UTC+0) btw i played a bit with two column print styles in Chrome (which electron calls out to). The attached file is a PDF (Chrome browser) print, using the current print css, + some extra print css of my own. It uses 2 columns, spans infoboxes 100% across a single column, and forces wiki tables to span 2 columns. There's a ton of edge cases that I haven't dealt with, but many can be taken straight from the mobile view and be reapplied to this context. James Denton - Wikipedia.pdf722 KBDownload /** you'd probably want to limit 2 column mode to certain widths btw */ @media print { #firstHeading { margin: 0; } td, li { page-break-inside: avoid; break-inside: avoid; } .mw-parser-output { column-count: 2; } /*.mw-parser-output h2,*/ .mw-parser-output .wikitable { column-span: all; } .mw-body-content table { float: none!important; margin-left: auto !important; margin-right: auto !important; } .mw-body-content .infobox, .mw-body-content .vertical-navbox, .mw-body-content .navbox, .mw-body-content .navbox > .navbox-inner { width: 100% !important; box-sizing: border-box; display: table; } .mw-body-content { word-wrap: break-word; } } /* end of print style */ @page { margin: 1cm; size: A4 portrait; } • Nirzar added a comment.Jun 15 2017, 4:58 PM2017-06-15 16:58:27 (UTC+0) @TheDJ This is great!! I was trying to figure out how we can do this. Let me add this to the new style improvements that we have been working on and post couple of examples of single column and double column. • Nirzar moved this task from Needs analysis to Designing/discussing right now on the Readers-Web-Backlog (Design) board.Jun 16 2017, 1:45 AM2017-06-16 01:45:45 (UTC+0) • Nirzar updated the task description. (Show Details)Jul 20 2017, 1:31 AM2017-07-20 01:31:38 (UTC+0) ovasileva updated the task description. (Show Details)Jul 20 2017, 6:15 PM2017-07-20 18:15:29 (UTC+0) ovasileva added a parent task: T171836: Apply new print styles for books.Jul 27 2017, 10:59 AM2017-07-27 10:59:20 (UTC+0) • Nirzar added a subscriber: bmansurov.Jul 31 2017, 8:15 PM2017-07-31 20:15:25 (UTC+0) @ovasileva was just reviewing the design requirements. one minor thing Article name on every page next to the page number - @bmansurov mentioned it would be difficult to get that technically. I am okay striking it off from requirement bmansurov added a comment.Jul 31 2017, 8:17 PM2017-07-31 20:17:29 (UTC+0) To clarify, it would take more effort to do so. It's not difficult, but if we want to deliver something sooner, we may want to start simple. ovasileva added a comment.Aug 1 2017, 2:50 PM2017-08-01 14:50:06 (UTC+0) @Nirzar, @bmansurov - not a huge deal, I think it's okay to remove. ovasileva mentioned this in T135643: Show tables in pdfs (#9).Aug 29 2017, 2:49 PM2017-08-29 14:49:06 (UTC+0) ovasileva updated the task description. (Show Details)Edited · Aug 30 2017, 5:23 PM2017-08-30 17:23:50 (UTC+0) Added chapter name to requirements. In previous book rendering, chapters had same hierarchy as article names in books without chapters. If chapters existed, article names would be pushed down. ovasileva added a project: Proton.Aug 30 2017, 5:27 PM2017-08-30 17:27:03 (UTC+0) ovasileva moved this task from Triage to Current Sprint on the Proton board. ovasileva mentioned this in T171836: Apply new print styles for books.Sep 11 2017, 11:54 AM2017-09-11 11:54:24 (UTC+0) • Nirzar updated the task description. (Show Details)Sep 11 2017, 7:55 PM2017-09-11 19:55:36 (UTC+0) • Nirzar updated the task description. (Show Details)Sep 11 2017, 8:12 PM2017-09-11 20:12:59 (UTC+0) ovasileva added a comment.Sep 13 2017, 1:39 PM2017-09-13 13:39:10 (UTC+0) @Nirzar - looking good! My only comment is the location of the wordmark on the title page, but if it was okayed by the other designers, let's keep it this way. To me, the title reads "Wikipedia Best Places to Visit in Germany" ovasileva edited projects, added Readers-Web-Backlog; removed Readers-Web-Backlog (Design).Sep 13 2017, 1:39 PM2017-09-13 13:39:36 (UTC+0) ovasileva moved this task from Incoming to Upcoming on the Readers-Web-Backlog board. ovasileva moved this task from Current Sprint to Backlog on the Proton board.Sep 19 2017, 4:38 PM2017-09-19 16:38:19 (UTC+0) ovasileva added a comment.Sep 19 2017, 4:48 PM2017-09-19 16:48:11 (UTC+0) It seems that splitting this will depend on our eventual choice of renderer. If we decide to go with headless chromium and do post-processing separately, we should pull out the styles for page numbers and toc into a separate task Niedzielski added a subscriber: Niedzielski.Sep 22 2017, 2:39 PM2017-09-22 14:39:13 (UTC+0) According to Sam's email yesterday, the renderer planned was headless Chromium and was being evaluated in T175853. The ticket resolution says headless Chromium is ok so this is ready to work on. ovasileva changed the task status from Open to Stalled.Oct 10 2017, 12:27 PM2017-10-10 12:27:46 (UTC+0) ovasileva moved this task from Upcoming to Needs Prioritization on the Readers-Web-Backlog board. Jdlrobson moved this task from Needs Prioritization to Tracking on the Readers-Web-Backlog board.Feb 7 2018, 7:23 PM2018-02-07 19:23:40 (UTC+0) Jdlrobson edited projects, added Readers-Web-Backlog (Tracking); removed Readers-Web-Backlog. Jdlrobson added a parent task: T186740: [EPIC] It should be possible to print a book using the Proton service.Feb 7 2018, 7:26 PM2018-02-07 19:26:52 (UTC+0) bmansurov removed a subscriber: bmansurov.Feb 7 2018, 8:04 PM2018-02-07 20:04:16 (UTC+0) ovasileva closed this task as Invalid.Apr 9 2018, 2:46 PM2018-04-09 14:46:37 (UTC+0) Closing as per T184772#4116906. Pediapress will be taking on rendering of PDF books. Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T167955

cc40

As a part of the switch to a new PDF renderer, we would like to customize and update our styles for books. Books must contain the following elements: Table of contents with page numbers Selecting a se

en

The Movement Strategy and Governance (MSG) team would like to deploy the Notifications system to notify eligible voters from the community to vote during the 2022 Board election. The community vote will happen from 15th to 29th August 2022. We expect this to be deployed on the first day of the voting. Purpose of the notification - Tell voters that they are eligible to vote in the 2022 Wikimedia Foundation Board of Trustees election What triggers notification? - Users are eligible to vote in the 2022 Wikimedia Foundation Board of Trustees election according to the voting eligibility criteria. "Notice" or "Alert"? - Notice Notification type (standard, bundled, expandable bundle) - Standard Body: Voting ends at 23:59, 29 August 2022 (UTC). Verify your eligibility and vote now. primary link label: Vote now #1 secondary link target: null #1 secondary link label: null Aug 14 2022, 10:00 PM T315046 Undertake the 2022 Wikimedia Foundation Board of Trustees elections T309975 Deploy Notifications for 2022 Board of Trustees election T58362: Allow users to create custom notifications onwiki T131210: Notify editors that a new Wikipedia Library database is available to them Mh-3110 created this task.Jun 6 2022, 11:26 AM2022-06-06 11:26:12 (UTC+0) Restricted Application added a project: Growth-Team. · View Herald TranscriptJun 6 2022, 11:26 AM2022-06-06 11:26:12 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald Transcript RamzyM-WMF renamed this task from Deploy Notifications for 2022 Board election to Deploy Notifications for 2022 Board of Trustees election.Jun 6 2022, 11:39 AM2022-06-06 11:39:29 (UTC+0) RamzyM-WMF updated the task description. (Show Details) Aklapper set Due Date to Aug 14 2022, 10:00 PM.Jun 6 2022, 5:37 PM2022-06-06 17:37:57 (UTC+0) RamzyM-WMF updated the task description. (Show Details)Jun 6 2022, 5:43 PM2022-06-06 17:43:02 (UTC+0) RamzyM-WMF added a subscriber: Keegan. Sgs moved this task from Inbox to Triaged on the Growth-Team board.Jun 8 2022, 11:06 AM2022-06-08 11:06:01 (UTC+0) Sgs moved this task from Triaged to Needs Discussion/Analysis on the Growth-Team board.Jun 8 2022, 11:33 AM2022-06-08 11:33:48 (UTC+0) MMiller_WMF added a subscriber: MMiller_WMF.Jun 8 2022, 2:08 PM2022-06-08 14:08:27 (UTC+0) Hello @Mh-3110. Thank you for filing this task. I want to ask some questions because creating one-off notifications is something that has been done only rarely. I think I remember that CentralNotice is usually used to notify editors about Board elections. Is this a new idea this year -- to send notifications? Will there also be CentralNotice? Mh-3110 added a comment.Jun 8 2022, 3:29 PM2022-06-08 15:29:20 (UTC+0) Yes, that is a new idea this year. We are planning to have notifications coupled with CentralNotice. Keegan added a comment.Jun 8 2022, 3:43 PM2022-06-08 15:43:55 (UTC+0) @MMiller_WMF We've been mandated to further increase global election turnout, as tools like mass email and central notice become less effective over the years we're exploring other ways to broadcast the election to the community. We're looking at folding in Notifications as part of the top-level communications about the Board of Trustees election., with the understanding that this is a rare occurrence and we only make the request with the understanding from the board that this election (and UCoC voting again within the year) are top-level priorities from the Board to community for democratic participation. We're at the point of this being a binary decision right now, is your team even interested/available to support this request or not. It's not planned work, it's an experiment we came up with, so if there's no space for the Growth team to accommodate this request it's understandable for sure. If it is possible, we're willing to take the next steps to keep scoping this out with your team. kostajh added a subscriber: kostajh.Jun 13 2022, 9:41 AM2022-06-13 09:41:19 (UTC+0) There is a request for Wikipedia Library notifications (T131210: Notify editors that a new Wikipedia Library database is available to them) that shares some characteristics with the request in this task. Echo is designed to generate notifications in response to something happening on wiki. This task proposes a different model, where we would have to create a notification that isn't associated with an on-wiki event, and also provide the ability to send these notifications via a maintenance script or on-wiki (T58362: Allow users to create custom notifications onwiki). I haven't looked closely, but I imagine this will be a decent amount of work to implement. Maybe there are other teams interested in this model of sending notifications? For example, I could see how the Campaign-Tools team might have some use cases that align with this. If we were going to do some kind of hack with less engineering effort, I suppose we could pretend that a page view is the "event", and create a notification in response to that only if the user hasn't already received the notification. That has the downside of only working for logged-in users who visit the wikis during the period when we want to send these notifications, but perhaps that is sufficient? Trizek-WMF added a subscriber: Trizek-WMF.Jun 13 2022, 12:58 PM2022-06-13 12:58:53 (UTC+0) Trizek-WMF added a comment.Jun 14 2022, 12:28 PM2022-06-14 12:28:16 (UTC+0) At some point in the future, we should consider to have a community board announcement, where these kind of global notifications would live. Trizek-WMF added a comment.Jun 14 2022, 12:41 PM2022-06-14 12:41:52 (UTC+0) Regarding the task, there is some potential for pushback when notifying eligible voters. I know it just a way to display an information about our movement's governance, but it would be perceived as canvassing. Also, some users may request to have the same thing to inform the community about their vote or their project. Voting has begun in the Wikimedia Foundation Board of Trustees elections! Can we skip the exclamation mark at the end? Enthusiasm is nice, but again, it could be perceived the wrong way. Notifying eligible voters, shouldn't ask voter "to verify their eligibility". They are notified because they are eligible. :) Only eligible voters should be notified, at the wiki they are more active. Some users have no idea of what is the Wikimedia Foundation. Should this notification provide some context? This notification must be translated to be efficient. It means that the sentences have to be on translatewiki.net, with the right formatting for dates for each language. And given the impact of deploying a new notification, it shouldn't be a one-time notification. Are you considering to reuse it for the next round of elections? RamzyM-WMF added a comment.Jun 14 2022, 1:27 PM2022-06-14 13:27:36 (UTC+0) Can we skip the exclamation mark at the end? Enthusiasm is nice, but again, it could be perceived the wrong way. Yes, this should be configurable. Notifying eligible voters, shouldn't ask voter "to verify their eligibility". They are notified because they are eligible. :) Only eligible voters should be notified, at the wiki they are more active. Some users have no idea of what is the Wikimedia Foundation. Should this notification provide some context? This is an early draft, so as above, yes we can change it. I'm not entirely convinced if we should explain what the Foundation is (we still have the unresolved debate of whether the Foundation "operates", "owns", or "hosts" Wikipedia and its sister projects... I don't think we want an ensuing uproar about this). Then again, Board election voter demographics are mostly people that have at least a basic understanding of what the Foundation do and do not do. Are you considering to reuse it for the next round of elections? If this goes well, absolutely. MMiller_WMF moved this task from Needs Discussion/Analysis to Triaged on the Growth-Team board.Jul 6 2022, 2:57 PM2022-07-06 14:57:26 (UTC+0) After talking about this with @Keegan and scoping it with the Growth team, we've decided that we can't do this task for the coming year. The Growth team's bandwidth has been limited by being down one engineer, and since Echo is not currently built for one-off notifications, sending this particular notification would be a hack that would be difficult for the team to manage. @Mh-3110, thank you for filing this task and discussing it with us. I'm sorry we couldn't help. I leave this task with you to move it or resolve it as you see fit. Sgs removed a project: Growth-Team.Jul 6 2022, 5:34 PM2022-07-06 17:34:49 (UTC+0) Trizek-WMF removed a subscriber: Trizek-WMF.Jul 6 2022, 6:09 PM2022-07-06 18:09:11 (UTC+0) Mh-3110 added a comment.Jul 6 2022, 6:48 PM2022-07-06 18:48:17 (UTC+0) Thanks @MMiller_WMF, for taking the time to scope this. Hopefully for another time. Mh-3110 closed this task as Resolved.Jul 6 2022, 6:49 PM2022-07-06 18:49:13 (UTC+0) jrbs changed the task status from Resolved to Declined.Jul 6 2022, 7:50 PM2022-07-06 19:50:51 (UTC+0) Technically this is Declined, not Resolved, so switching that. :) jrbs added a parent task: T315046: Undertake the 2022 Wikimedia Foundation Board of Trustees elections.Aug 11 2022, 10:18 PM2022-08-11 22:18:57 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T309975

cc40

The Movement Strategy and Governance (MSG) team would like to deploy the Notifications system to notify eligible voters from the community to vote during the 2022 Board election. The community vote wi

en

We're currently overloading our page headers with user tools links and that's making it difficult to use that space for important links and notices (such as a link back to the Getting Started special page). I've built a simple mockup* (see attachment) to illustrate the idea. I'm sure this has been thought of before, but I think it's time to finally execute on it, or at least re-open this for discussion. It's currently styled under the assumption that we're reusing the Guiders extension to display popovers, but I'm open to changing it to look like a more traditional dropdown menu. Frees up some much needed screen real-estate for important links Makes user tools more scannable Makes things look nicer on small resolutions. Potential loss of feature discoverability Information architecture not optimal; perhaps things like watchlist shouldn't be grouped with the user's talk page _________________ (fill in the blanks) Stalled see T46448#1021480 for details T66321 Personal tools are too crowded (tracking) T46448 Consolidate personal portlet links into collapsed control or dropdown (tracking) T66789 Compact personal bar should have RTL version of icons T66861 ULS language selector flyout does not work with the Compact Personal Bar on some wikis T66862 Echo flyout does not open on some pages when Compact Personal Bar is enabled T66898 Accesskeys are not expanded in tooltips T66909 Help link points to redirect T70310 Display bug in CPB on Firefox 5.0 T67142 Access key strings are missing modifier keys T67178 Clearing echo count from flyout or all notification page does not clear CPB flyout notification count T67246 unread count for watchlist changes is not available via API T68089 Add index wl_user_notificationtimestamp to table watchlist T67285 When user has many gadgets installed bottom items in the flyout are not visible T67288 The notifications icon in the CPB is misplaced in RTL wikis T67361 Echo API: display filtered notification lists based on type T67367 Allow all or part of a mobile formatted screen to be called from desktop site T67376 Flyout items after the first few items are not accessible in Opera 12 T67387 Flyout does not render correctly on Internet Explorer and may cause portlet links to become inaccessible T67427 Help and privacy policy links to not point to the right pages on some language wikis T67471 Echo popup goes off-screen with CPB in RTL wikis T67470 Hover doesn't work on some touch interfaces or flyout displays incorrectly. T69195 Accessibility for keyboard users and screen readers in CPB T66195 Allow ULS menu (from gear) to be opened as a modal dialog T69613 Local IME script selector conflicts with Compact personal bar T67073 "skins.vector.compactPersonalBar" breaks mw.util.addPortletLink for gadgets, user scripts and other extensions T106465: Figure out what to do with the personal tools in responsive Vector T86831: disable compact personal bar beta feature from Wikidata T85541: ULS on does not work consistently when "compact personal bar" beta feature is enabled There are a very large number of changes, so older changes are hidden. Show Older Changes Jorm added a comment.Jan 29 2013, 7:54 PM2013-01-29 19:54:37 (UTC+0) I'm going to take this bug and assign it to myself for now. We need to have a product discussion about this in a larger sense and until that happens we shouldn't implement this. I'll set up a meeting. MZMcBride added a comment.Jan 29 2013, 10:09 PM2013-01-29 22:09:55 (UTC+0) A consideration of who the interface is meant to serve would also be a good idea at this stage, I think. As it is, it feels like Monobook has become the skin of choice for editors (who need easier access to the watchlist and contributions links), while Vector has become the skin of choice for readers (mostly as it's the default). • Mattflaschen-WMF added a comment.Jan 29 2013, 10:26 PM2013-01-29 22:26:01 (UTC+0) MZMcBride, I'm not sure that's the case (Monobook vs. Vector). However, it should be relatively easy to study from the database (correlate skin use and active editing). Though we don't currently have data either way, I don't think this proposed change would make Vector worse for editors. There's a potential case that it makes it better by making things like Watchlist and Contributions that are too far right more accessible. If and when something is added to the upper right (e.g. Echo), we might want to consider placing this menu the left, which would move it (and thus the key features like Watchlist within) closer to the center of the screen. • TrevorParscal added a comment.Jan 29 2013, 10:29 PM2013-01-29 22:29:58 (UTC+0) The original vector design included grouping the user tools into a hover-to-open menu, but it got cut due to some negative feedback early on. I'm glad to see this is getting some attention now, because I've always felt it was a great way to reduce clutter - but at the same time I'm aware that it can be done wrong, and we need get it right because it's a very visible and frequently used feature. I believe we should do the following: Run click-tracking (in monobook and vector) on the personal tools links and get a feel for how they are used and by who. If people who edit a lot use some of them frequently (as MZ has suggested) it will easy to confirm in the data. Use the data we get, combined with some hallway user testing and our own brains to split the items into two levels of frequency of use. Tuck the less-used items into a menu, leave the more frequently used items where they are. Experiment with using icons for the most important items that aren't in the menu (a gear for preferences, a speech bubble or circle with number in it for notifications, etc.) Consider bringing the search to the top line, rather than the 2nd line (making more room for tabs) • TrevorParscal added a comment.Jan 29 2013, 10:40 PM2013-01-29 22:40:52 (UTC+0) Here's an example of a skin design which uses a combination of a menu and top-level items in place of the personal tools. attachment Apex.png ignored as obsolete • TrevorParscal added a comment.Jan 29 2013, 10:41 PM2013-01-29 22:41:19 (UTC+0) Here's another example of a skin design which uses a combination of a menu and top-level items in place of the personal tools. attachment Helix.jpg ignored as obsolete Jorm added a comment.Jan 29 2013, 10:46 PM2013-01-29 22:46:49 (UTC+0) I don't think we need to bother goofing with monobook, tbh. My primary concern about this change is the discoverability of "Watchlist" and "Talk" for new users and making sure that we're aligned with the plans regarding Echo and Flow. • TrevorParscal added a comment.Jan 29 2013, 11:12 PM2013-01-29 23:12:45 (UTC+0) Given that we would have to go out of our way to exclude monobook from the stats, I think it's probably worth just getting those too, if only to put to rest any debate over whether the "real" editors have incompatible usage patterns (because if we only look at vector, it's easy to say we excluded people from the survey). Jorm added a comment.Jan 29 2013, 11:19 PM2013-01-29 23:19:36 (UTC+0) Oh! I didn't mean "not do the lookup on the stats" for monobook (and I quite agree with you re: "real" editors). I was saying that when/if we develop this, we probably don't need to do it for monobook. • Mattflaschen-WMF added a comment.Jan 29 2013, 11:32 PM2013-01-29 23:32:36 (UTC+0) I agree this bug should be limited to Vector. Someone can definitely propose doing it for Monobook separately, but that's a different matter. I've emailed the analytics list regarding the statistical correlation (skin v. active editor). • Mattflaschen-WMF added a comment.Jan 29 2013, 11:38 PM2013-01-29 23:38:37 (UTC+0) I'm not that worried about exposing Talk, since recipients will get a user talk notification (or later Echo). And they can still get to it at other times through User/Profile -> Talk Milimetric added a comment.Mar 28 2013, 1:08 PM2013-03-28 13:08:27 (UTC+0) I've made this investigation official: https://gist.github.com/milimetric/5262726 I know some people might want to see this in gerrit, you're welcome to move it in there. It's just early in the morning and nobody's here to answer where it would go. Milimetric added a comment.Mar 28 2013, 1:29 PM2013-03-28 13:29:45 (UTC+0) Ok, I've got a candidate solution. The fix to the query was the one I mentioned months ago but forgot about :) Step by step analysis: • Mattflaschen-WMF added a comment.Mar 28 2013, 6:57 PM2013-03-28 18:57:14 (UTC+0) What are the empty 2525 at the top, more default/vector? It would be useful to coalesce all the vectors (default/vector/empty?) together for easier readability. Milimetric added a comment.Mar 28 2013, 7:03 PM2013-03-28 19:03:00 (UTC+0) It sounds like everyone's happy with the validity of the results, closing the bug. (Feel free to re-open if you find a problem, but maybe ping me first if you can find me) Milimetric added a comment.Mar 28 2013, 7:03 PM2013-03-28 19:03:48 (UTC+0) Oh, and it sounds like the 2525 will be the same as 'default' - assigned 'vector' Milimetric added a comment.Mar 28 2013, 7:08 PM2013-03-28 19:08:18 (UTC+0) err - 'default' is assigned 'monobook' and I'm really sorry, I was posting in the wrong bug. I have learned that bugzilla does not reward hurried responses - no way to delete. Very sorry everyone! • Jaredzimmerman-WMF added a comment.Jun 27 2013, 9:30 PM2013-06-27 21:30:23 (UTC+0) This work is planning and in progress as a desktop web beta feature you can read more about the beta features planning here http://www.mediawiki.org/wiki/Lab_experiments Nemo_bis added a comment.Apr 23 2014, 9:02 PM2014-04-23 21:02:18 (UTC+0) Almost one year of silence, resetting assignments. (In reply to Jared Zimmerman (WMF) from comment #28) This work is planning and in progress as a desktop web beta feature you can read more about the beta features planning here Moving to extension requests accordingly. Jdforrester-WMF added a comment.Apr 23 2014, 9:08 PM2014-04-23 21:08:23 (UTC+0) The code for this is being written by Juliusz inside MobileFrontend but they don't like desktop-related bugs from making that messy; the idea however is that this would be merged into Vector core, so moving back. Nemo_bis added a comment.Apr 23 2014, 9:12 PM2014-04-23 21:12:22 (UTC+0) I can't imagine this happening in core. Surely not in Vector. • bzimport added a comment.Apr 23 2014, 9:14 PM2014-04-23 21:14:01 (UTC+0) (In reply to Nemo from comment #31) I can't imagine this happening in core. Surely not in Vector. The code by Juliusz is in VectorBeta extension, where it will likely remain as long as it's a Beta Feature. You can try it out now on Beta Labs (http://en.wikipedia.beta.wmflabs.org/). • bzimport added a comment.Apr 23 2014, 9:14 PM2014-04-23 21:14:35 (UTC+0) (In reply to Steven Walling from comment #32) (In reply to Nemo from comment #31) I can't imagine this happening in core. Surely not in Vector. The code by Juliusz is in VectorBeta extension, where it will likely remain as long as it's a Beta Feature. You can try it out now on Beta Labs Sorry, *should be in* Jdforrester-WMF added a comment.Apr 23 2014, 9:15 PM2014-04-23 21:15:35 (UTC+0) (In reply to Nemo from comment #31) I can't imagine this happening in core. Surely not in Vector. The limits of your imagination notwithstanding, the intent is to make changes for all users of all MediaWiki installs, so… yes. • Jaredzimmerman-WMF added a comment.May 5 2014, 4:20 AM2014-05-05 04:20:16 (UTC+0) Should we close this as a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=44448 since that is the tracking bug for Compact Personal Bar (CPB) https://www.mediawiki.org/wiki/Compact_Personal_Bar MZMcBride added a comment.May 5 2014, 4:39 AM2014-05-05 04:39:00 (UTC+0) (In reply to Jared Zimmerman (WMF) from comment #35) Should we close this as a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=44448 since that is the tracking bug for Compact Personal Bar (CPB) I assume you mean bug 64321, not bug 44448. MZMcBride added a comment.May 5 2014, 4:39 AM2014-05-05 04:39:00 (UTC+0) (In reply to Jared Zimmerman (WMF) from comment #35) Should we close this as a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=44448 since that is the tracking bug for Compact Personal Bar (CPB) I assume you mean bug 64321, not bug 44448. • Jaredzimmerman-WMF added a comment.May 5 2014, 5:41 AM2014-05-05 05:41:27 (UTC+0) Nemo_bis added a comment.May 5 2014, 6:06 AM2014-05-05 06:06:58 (UTC+0) Bug 64321 is not the tracking bug for that feature. MZMcBride added a comment.May 5 2014, 1:04 PM2014-05-05 13:04:35 (UTC+0) (In reply to comment #38) (Sorry about the duplicate comment. This quirk is being discussed tangentially at bug 64864.) Liuxinyu970226 added a subscriber: Liuxinyu970226.Dec 12 2014, 12:24 PM2014-12-12 12:24:01 (UTC+0) Qgil added a subscriber: Qgil.Dec 22 2014, 11:09 PM2014-12-22 23:09:56 (UTC+0) Is there a list of tasks considered hard blockers of the graduation of the Compact Personal Bar? Or is there a plan to start trying wider adoption in some wikis willing to become early adopters? I'm just forwarding a question of a user in ca.wiki, being curious myself as a happy user of this beta. Ricordisamoa awarded a token.Dec 22 2014, 11:26 PM2014-12-22 23:26:11 (UTC+0) He7d3r added a subtask: T67073: "skins.vector.compactPersonalBar" breaks mw.util.addPortletLink for gadgets, user scripts and other extensions.Dec 22 2014, 11:40 PM2014-12-22 23:40:00 (UTC+0) • Jaredzimmerman-WMF added a comment.Dec 22 2014, 11:45 PM2014-12-22 23:45:12 (UTC+0) I would say most of this list of blockers is required to close before we'd graduate compact personal bar, however, we may end of taking much of the learning and apply it elsewhere rather than making any changes to Vector. • Jaredzimmerman-WMF edited projects, added Beta-Feature, MediaWiki-extensions-VectorBeta; removed Design, Vector (legacy skin).Dec 22 2014, 11:46 PM2014-12-22 23:46:10 (UTC+0) • Jaredzimmerman-WMF set Security to None. • Jaredzimmerman-WMF added a project: Compact-Personal-Bar-Beta.Dec 22 2014, 11:49 PM2014-12-22 23:49:20 (UTC+0) • Jaredzimmerman-WMF renamed this task from Consolidate personal portlet links into collapsed control or dropdown to Consolidate personal portlet links into collapsed control or dropdown (tracking task).Dec 23 2014, 12:15 AM2014-12-23 00:15:05 (UTC+0) • Jaredzimmerman-WMF updated the task description. (Show Details) Nemo_bis updated the task description. (Show Details)Dec 27 2014, 9:49 PM2014-12-27 21:49:36 (UTC+0) Quiddity added a project: Tracking-Neverending.Jan 7 2015, 8:25 PM2015-01-07 20:25:26 (UTC+0) Krinkle renamed this task from Consolidate personal portlet links into collapsed control or dropdown (tracking task) to Consolidate personal portlet links into collapsed control or dropdown (tracking).Jan 9 2015, 2:30 AM2015-01-09 02:30:28 (UTC+0) • Jaredzimmerman-WMF lowered the priority of this task from Medium to Low.Jan 16 2015, 6:45 PM2015-01-16 18:45:56 (UTC+0) • Jaredzimmerman-WMF lowered the priority of this task from Low to Lowest. Quiddity added a comment.Feb 6 2015, 9:20 PM2015-02-06 21:20:36 (UTC+0) Note: The CPB betafeature has been disabled on all wikis, per T86831. If I understand correctly, it was disabled because it was breaking the language selector at various wikis (see T85541 for details), and there were no developer resources available to fix that, or the numerous other blocker tasks listed in this tracking task, that are needed before it can/could move forward to graduate from a betafeature. Users who wish to re-enable it for themselves, via their user.js, can do so by following the instructions in this comment. Onwiki discussion is at https://www.mediawiki.org/wiki/Topic:Sa0b3ys2vr6ihen8 Quiddity changed the task status from Open to Stalled.Feb 6 2015, 9:20 PM2015-02-06 21:20:50 (UTC+0) Quiddity updated the task description. (Show Details) • Mattflaschen-WMF closed subtask T67178: Clearing echo count from flyout or all notification page does not clear CPB flyout notification count as Resolved.Feb 24 2015, 3:59 AM2015-02-24 03:59:42 (UTC+0) Liuxinyu970226 removed a subscriber: Liuxinyu970226.Feb 27 2015, 3:06 AM2015-02-27 03:06:01 (UTC+0) hashar added a subscriber: hashar.Jun 30 2015, 9:22 AM2015-06-30 09:22:04 (UTC+0) From my reply on our internal mailing list: I am wondering who maintains the extension nowadays and whether we should: A) shoot the extension / undeploy it B) fix the bug, enable the code I am not a huge fan of code bitrotting and only being used as a corner case. That is a maintenance burden. Ricordisamoa added a comment.Jun 30 2015, 9:33 AM2015-06-30 09:33:25 (UTC+0) Please do not undeploy CPB. It was one of the few recent usability improvements, and it's still being loaded by many users. Meno25 removed a subscriber: Meno25.Jun 30 2015, 9:52 AM2015-06-30 09:52:42 (UTC+0) • Kosikfl added a comment.Jul 1 2015, 2:15 AM2015-07-01 02:15:55 (UTC+0) I understand, please be patient with me. I know it must be very annoying to all you pro editors. This is my first time editing and it must be frustrating to clean up after me. I will try to learn as fast as I can I am trying to be creative I would be very created if I knew what I was doing please be patient with me and if you can help me, I will try to be as officiant as I possible you can I. I would like to make this site very unique. I would like to request to use my real name it's already out there now. If not I get it but I did go through this for four years and just doesn't make sense to use a coding when I'm already uncensored. And I did accomplish a big thing by hacking the hackers and it would be nice to get the credit for it. But it's up to you. I had my oncology appointment today and physical therapy yesterday I should be back in the game tomorrow. Thank you you have any questions let me know and I will try to do what you've asked do you have a book or is there a size that by Stepway to do what you're asking if you could give me some guidance that would be very helpful. Thank you Aklapper added a comment.Jul 1 2015, 1:44 PM2015-07-01 13:44:46 (UTC+0) In T46448#1413092, @Ricordisamoa wrote: Please do not undeploy CPB. In my understanding, the "Compact Personal Bar" code is part of the VectorBeta extension codebase and the extension itself won't get undeployed (though the CPB code might get removed?), as the CPB feature has been unavailable since January 2015 already: https://gerrit.wikimedia.org/r/#/c/185116/ Ricordisamoa added a comment.Jul 1 2015, 2:05 PM2015-07-01 14:05:04 (UTC+0) In T46448#1417190, @Aklapper wrote: the CPB feature has been unavailable since January 2015 already Yes and no, see https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=skins.vector.compactPersonalBar&fulltext=1&ns2=1. If it gets undeployed, I will host a copy on Tool Labs. Ricordisamoa mentioned this in T106465: Figure out what to do with the personal tools in responsive Vector.Jul 22 2015, 1:56 PM2015-07-22 13:56:40 (UTC+0) Catrope closed subtask T66862: Echo flyout does not open on some pages when Compact Personal Bar is enabled as Declined.Aug 3 2015, 11:57 PM2015-08-03 23:57:28 (UTC+0) Jorm removed a subscriber: Jorm.Dec 26 2015, 7:26 PM2015-12-26 19:26:57 (UTC+0) Ilya2015 added a subscriber: Ilya2015.Feb 27 2016, 8:26 AM2016-02-27 08:26:22 (UTC+0) When will the personal bar come back? hashar removed a subscriber: hashar.Feb 27 2016, 9:38 AM2016-02-27 09:38:29 (UTC+0) Ricordisamoa added a comment.Feb 27 2016, 1:04 PM2016-02-27 13:04:51 (UTC+0) In T46448#2068962, @Ilya2015 wrote: When will the personal bar come back? Compact Personal Bar is back! tarlocesilion added a comment.Feb 27 2016, 1:55 PM2016-02-27 13:55:50 (UTC+0) @Ricordisamoa, that tool has a few bugs, look: It's a screenshot taken on Meta-Wiki, but the same issue applies to any other wiki. 'Vector...', and 'help' link to pages with names beginning with <, and 'notifs' links to nothing. Ilya2015 added a comment.Feb 27 2016, 5:13 PM2016-02-27 17:13:28 (UTC+0) In T46448#2069158, @Ricordisamoa wrote: In T46448#2068962, @Ilya2015 wrote: When will the personal bar come back? Compact Personal Bar is back! Cheers! But I meant officially. Ricordisamoa added a comment.Feb 27 2016, 5:24 PM2016-02-27 17:24:44 (UTC+0) In T46448#2069213, @tarlocesilion wrote: @Ricordisamoa, that tool has a few bugs I just pushed a new version, be sure to refresh your cache to use it. Aklapper added a comment.Feb 27 2016, 8:17 PM2016-02-27 20:17:31 (UTC+0) In T46448#2069393, @Ilya2015 wrote: Please consider helping to fix T67073, e.g. by providing a patch. (See T86831 and https://meta.wikimedia.org/wiki/Tech/News/2015/05 ) GOIII added a subscriber: GOIII.Feb 28 2016, 4:40 AM2016-02-28 04:40:11 (UTC+0) fwiw... seems to still have trouble with assimilating the active language/ULS bit(s) and that was one of the previous incarnation's deal breakers. And why are the watchlist and talkpage links [repeated] outside the fly-out? If anything that is where the notification counters for alerts and messages should go (imho). Ricordisamoa added a comment.Feb 28 2016, 8:04 AM2016-02-28 08:04:44 (UTC+0) In T46448#2070079, @GOIII wrote: fwiw... seems to still have trouble with assimilating the active language/ULS bit(s) and that was one of the previous incarnation's deal breakers. Do you think that after a piece of code has been abandoned, bugs just fix themselves? :-P And why are the watchlist and talkpage links [repeated] outside the fly-out? That's how the original version worked (more or less...) GOIII added a comment.Feb 28 2016, 8:30 AM2016-02-28 08:30:42 (UTC+0) In T46448#2070202, @Ricordisamoa wrote: Do you think that after a piece of code has been abandoned, bugs just fix themselves? :-P Oh sorry. I got the impression it was refined at least a little since the last 'official' revisions removal. That's how the original version worked (more or less...) Blech. I though the whole point was to keep the total width as small as possible while still being functional. To me; that means the only things outside of the fly out should be the alert and message notifications (which have been updated to use OOUI since that snapshot was taken as well). The whole background-image/icon thing cracks me up too - so much easier to call upon FontAwesome for the same results [if not better]. Ricordisamoa added a comment.Feb 28 2016, 9:19 AM2016-02-28 09:19:16 (UTC+0) In T46448#2070215, @GOIII wrote: I got the impression it was refined at least a little since the last 'official' revisions removal. I spent a few hours to make it work, that's all. To seriously fix it, we should get in touch with someone at WMF who is willing to revive VectorBeta :-) Qgil removed a subscriber: Qgil.Feb 29 2016, 8:54 AM2016-02-29 08:54:44 (UTC+0) Ricordisamoa removed a subscriber: • Kosikfl.Mar 1 2016, 4:09 PM2016-03-01 16:09:04 (UTC+0) Milimetric removed a subscriber: Milimetric.Mar 1 2016, 11:13 PM2016-03-01 23:13:02 (UTC+0) Volker_E closed subtask T69195: Accessibility for keyboard users and screen readers in CPB as Declined.Apr 6 2016, 4:54 AM2016-04-06 04:54:18 (UTC+0) J5lx added a subscriber: J5lx.Jul 17 2016, 8:19 PM2016-07-17 20:19:40 (UTC+0) Aklapper closed this task as Declined.Oct 2 2017, 9:33 AM2017-10-02 09:33:44 (UTC+0) Aklapper closed subtask T70310: Display bug in CPB on Firefox 5.0 as Declined. Aklapper closed subtask T69613: Local IME script selector conflicts with Compact personal bar as Declined. Aklapper closed subtask T67471: Echo popup goes off-screen with CPB in RTL wikis as Declined. Aklapper closed subtask T67470: Hover doesn't work on some touch interfaces or flyout displays incorrectly. as Declined. Aklapper closed subtask T67387: Flyout does not render correctly on Internet Explorer and may cause portlet links to become inaccessible as Declined. Aklapper closed subtask T67288: The notifications icon in the CPB is misplaced in RTL wikis as Declined. Aklapper closed subtask T67142: Access key strings are missing modifier keys as Declined. Aklapper closed subtask T67073: "skins.vector.compactPersonalBar" breaks mw.util.addPortletLink for gadgets, user scripts and other extensions as Declined. Aklapper closed subtask T66898: Accesskeys are not expanded in tooltips as Declined. Aklapper closed subtask T66789: Compact personal bar should have RTL version of icons as Declined. VectorBeta is no longer supported or under development. It was removed 26 months ago from Wikimedia sites. Hence declining its remaining open tasks to reflect reality. Aklapper closed subtask T67467: Courses link is not showing up in the gadgets/extension section of compact personal bar flyout as Declined.Oct 16 2017, 8:03 AM2017-10-16 08:03:49 (UTC+0) Liuxinyu970226 moved this task from Tag to Transition completed / Archived on the Tracking-Neverending board.Mar 16 2019, 1:40 PM2019-03-16 13:40:41 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T46448

cc40

We're currently overloading our page headers with user tools links and that's making it difficult to use that space for important links and notices (such as a link back to the Getting Started special

en

JGirault created this task.Dec 9 2015, 10:29 PM2015-12-09 22:29:51 (UTC+0) JGirault assigned this task to Jdrewniak. JGirault raised the priority of this task from to Needs Triage. JGirault updated the task description. (Show Details) JGirault added projects: Discovery-Portal-Sprint, Discovery-ARCHIVED. JGirault moved this task from Needs triage to Analysis on the Discovery-ARCHIVED board. JGirault added subscribers: StudiesWorld, • MSyed, Aklapper, JGirault. JGirault removed a project: Discovery-Portal-Sprint.Dec 9 2015, 10:32 PM2015-12-09 22:32:33 (UTC+0) JGirault set Security to None. • Ironholds_backup edited projects, added Discovery-Analysis (Current work); removed Discovery-ARCHIVED.Jan 14 2016, 1:21 AM2016-01-14 01:21:38 (UTC+0) Deskana closed this task as a duplicate of T121566: Analyse the results of the Portal search box A/B test on or after 2016-01-21.Jan 19 2016, 9:14 PM2016-01-19 21:14:08 (UTC+0) Ironholds moved this task from Backlog to Done on the Discovery-Analysis (Current work) board.Jan 25 2016, 1:19 PM2016-01-25 13:19:38 (UTC+0) Deskana moved this task from Done to Resolved on the Discovery-Analysis (Current work) board.Feb 4 2016, 6:22 AM2016-02-04 06:22:21 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T121026

cc40

JGirault created this task.Dec 9 2015, 10:29 PM2015-12-09 22:29:51 (UTC+0) JGirault assigned this task to Jdrewniak. JGirault raised the priority of this task from to Needs Triage. JGirault updated th

en

Halfak committed rORESWHEELS35a710e0bf7e: Updates for revscoring 2.3.0 (authored by Halfak).Jan 3 2019, 9:28 PM2019-01-03 21:28:26 (UTC+0) Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/rORESWHEELS35a710e0bf7e4880e991c4e7a111bb73ee938ff4

cc40

Halfak committed rORESWHEELS35a710e0bf7e: Updates for revscoring 2.3.0 (authored by Halfak).Jan 3 2019, 9:28 PM2019-01-03 21:28:26 (UTC+0) Content licensed under Creative Commons Attribution-ShareAlik

en

ERROR: Unknown error occurred when processing country gb-sct in lang en (2006, 'MySQL server has gone away') We should check if it is still missing after the next harvest. If so we should figure out why. If not it might be worth considering a long-term fix for how to handle such hick-ups. T207067: Add Scotland Scheduled Monuments in English to monuments database T203348: Scotland isn't indexed into the monuments database from the English Wikipedia for a while T200112: Add wikidata-only datasets to MonumentsDatabase Lokal_Profil created this task.Jul 25 2018, 2:25 PM2018-07-25 14:25:44 (UTC+0) MichaelMaggs added a subscriber: MichaelMaggs.Edited · Aug 17 2018, 3:13 PM2018-08-17 15:13:14 (UTC+0) Not sure if this is relevant, but the tool seems to be picking up some monuments that are neither Wikidata P709 nor P718 (the only two that currently should be used). All the data for the UK campaigns are on Wikidata. We have not used the Monuments database for some years. Lokal_Profil added a comment.Aug 20 2018, 8:55 AM2018-08-20 08:55:33 (UTC+0) Thanks for the response. With "the tool" are you referring to a UK specific WLM tool, Monumental or some other tool? Is the UK campaign primarilly making use of the Wikidata items or the Wikipedia lists? If the former then it would make sense for us to switch the Monuments database over to harvesting from Wikidata instead. Could be a candidate for something similar to T200112: Add wikidata-only datasets to MonumentsDatabase. Lokal_Profil merged a task: T203348: Scotland isn't indexed into the monuments database from the English Wikipedia for a while.Sep 2 2018, 8:42 PM2018-09-02 20:42:45 (UTC+0) Lokal_Profil added a subscriber: Multichill. Lokal_Profil added a comment.Sep 2 2018, 9:07 PM2018-09-02 21:07:07 (UTC+0) Thanks @Multichill for finding the source for this. Not finding the header doesn't stop the page from being harvested, but not finding the row template does. In both cases redirects are not resolved so those entries are skipped. I'll update the config to use the two target "HS listed building header" at least. gerritbot added a subscriber: gerritbot.Sep 2 2018, 9:08 PM2018-09-02 21:08:00 (UTC+0) Change 457100 had a related patch set uploaded (by Lokal Profil; owner: Lokal Profil): [labs/tools/heritage@master] Update gb-sct header template gerritbot added a project: Patch-For-Review.Sep 2 2018, 9:08 PM2018-09-02 21:08:01 (UTC+0) Lokal_Profil added a project: Wiki-Loves-Monuments (2018).Sep 2 2018, 9:09 PM2018-09-02 21:09:09 (UTC+0) MichaelMaggs added a comment.Edited · Sep 2 2018, 10:15 PM2018-09-02 22:15:23 (UTC+0) In T200339#4513943, @Lokal_Profil wrote: Thanks for the response. With "the tool" are you referring to a UK specific WLM tool, Monumental or some other tool? Is the UK campaign primarilly making use of the Wikidata items or the Wikipedia lists? If the former then it would make sense for us to switch the Monuments database over to harvesting from Wikidata instead. Could be a candidate for something similar to T200112: Add wikidata-only datasets to MonumentsDatabase. I'm referring to Monumental here. I'm not sure where Monumental gets its data from, but it should be reading Wikidata only, for all four UK campaigns. Since 2014 the UK tool (written by Magnus) has directly used datasets on Wikidata, uploaded from the original listing authority datasets. We never take anything from Wikipedia. The mapping we use is as follows: wlm-gb-wls (Wales) maps to P1459 wlm-gb-nir (Northern Ireland) maps to P1460 wlm-gb-eng (England) maps to P1216 wlm-gb-sct (Scotland) maps to P709 (also P718 but this has few uses). As the official datasets are updated, we try to reflect that by re-importing to Wikidata. We'd prefer both the UK-specific and the Monumental tools to show exactly the same data, and that should be the Wikidata datasets mentioned above. Can Monumental read directly from Wikidata? If not, could you please amend the working database to be a direct copy of the Wikidata datasets? Paweł has been doing the recent setup work to get Monumental working for the UK campaigns, and there's recent email correspondence on the above points. MichaelMaggs added a comment.Sep 2 2018, 10:20 PM2018-09-02 22:20:10 (UTC+0) This comment was removed by MichaelMaggs. Multichill added a comment.Sep 3 2018, 4:20 PM2018-09-03 16:20:40 (UTC+0) In T200339#4552218, @Lokal_Profil wrote: Thanks @Multichill for finding the source for this. Not finding the header doesn't stop the page from being harvested, but not finding the row template does. In both cases redirects are not resolved so those entries are skipped. {{HB Scotland header}} and {{HB Scotland row}} are still referred to from the template documentation so its unclear if a search/replace is desired. I'll update the config to use the two target "HS listed building header" at least. Stuff got merged, but nobody seems to have done the clean up run. Doing that now (example edit: https://en.wikipedia.org/w/index.php?title=List_of_listed_buildings_in_Ruthven,_Angus&diff=prev&oldid=857875184 ). Can you keep an eye on it to see what you get in tomorrow? What is don't get is why https://en.wikipedia.org/wiki/List_of_Category_A_listed_buildings_in_Aberdeen wasn't harvested. gerritbot added a comment.Sep 3 2018, 4:23 PM2018-09-03 16:23:19 (UTC+0) Change 457100 merged by jenkins-bot: [labs/tools/heritage@master] Update gb-sct header template JeanFred added a comment.Sep 4 2018, 7:25 AM2018-09-04 07:25:33 (UTC+0) In T200339#4552278, @MichaelMaggs wrote: Can Monumental read directly from Wikidata? If not, could you please amend the working database to be a direct copy of the Wikidata datasets? For clarity : we (the WLM international team) support two independent data sources and associated tools. Monumental is based on Wikidata. It does not make use of the Monuments database at all. the Monuments Database (Wiki-Loves-Monuments-Database, and the associated tools) is based on the Wikipedia lists, and does not use Wikidata. Although, @Lokal_Profil and I are are trying to change that to some degree (T200112) in order to ease the migration path to Wikidata. if your data is fully hosted on Wikidata, you should not have to worry about the monuments database :) If you are transitioning your data from the Wikipedia lists to Wikidata, then T200112 may be of interest if you are heavily relying on MonumentsDB-tooling (mostly ErfgoedBot). JeanFred added a comment.Sep 4 2018, 8:18 AM2018-09-04 08:18:13 (UTC+0) This just happened again: WARNING: 46 primkey(s) missing on List_of_listed_buildings_in_Glasgow/13 (monuments_gb-sct_(en)) ERROR: Unknown error occurred when processing country gb-sct in lang en (2006, 'MySQL server has gone away') JeanFred added a comment.Edited · Sep 4 2018, 8:55 AM2018-09-04 08:55:59 (UTC+0) I cannot reproduce locally: $ docker-compose run --rm bot python erfgoedbot/update_database.py -countrycode:gb-sct -langcode:en -log WARNING: 46 primkey(s) missing on List_of_listed_buildings_in_Glasgow/13 (monuments_gb-sct_(en)) WARNING: 8 primkey(s) missing on List_of_listed_buildings_in_Kirkgunzeon,_Dumfries_and_Galloway (monuments_gb-sct_(en)) > Terminates in 4m42s Lokal_Profil moved this task from Backlog to Bugs on the Wiki-Loves-Monuments-Database board.Sep 4 2018, 3:03 PM2018-09-04 15:03:57 (UTC+0) Lokal_Profil moved this task from Backlog to In-progress on the Wiki-Loves-Monuments (2018) board.Sep 4 2018, 3:19 PM2018-09-04 15:19:49 (UTC+0) Lokal_Profil added a subscriber: Yarl.Edited · Sep 5 2018, 7:01 AM2018-09-05 07:01:08 (UTC+0) In T200339#4552280, @MichaelMaggs wrote: By the way, when a contestant photographs a monument that isn't yet on Wikidata, Monumental (or the underlying code) is updating Wikidata automatically with the new image, isn't it? I don't believe it is, for the simple reason that it is hard to judge which images are representative. But @Yarl can give a definite answer. In T200339#4554789, @JeanFred wrote: If you are transitioning your data from the Wikipedia lists to Wikidata, then T200112 may be of interest if you are heavily relying on MonumentsDB-tooling (mostly ErfgoedBot). To clarify @JeanFred's comment. Tooling here primarilly refers to automatic categorisation of uploaded images lists of images of monument where that monument does not yet have an image (in the list) @MichaelMaggs The lists of UK monuments that are on Wikipedia today, are they completely abandoned? I.e. do they receive none of the updates that are made to Wikidata? If so I would recommend Wiki-Loves-Monuments-Database to stop harvesting these. We can try switching over to a Wikidata harvest to get some of the above mentioned tooling working anyway. JeanFred added a comment.Sep 11 2018, 10:34 PM2018-09-11 22:34:07 (UTC+0) We noticed a lot of warnings for missing prim keys. This is because the config looks for hb, but some/many/all pages actually use hbnum We should search/replace the template parameters on all lists. JeanFred added a comment.Sep 11 2018, 10:59 PM2018-09-11 22:59:34 (UTC+0) We tried running harvesting just on gb-sct, and it crashed again (so it’s not due to some weird timing linked to full harvest). It always crashes at the same place − the last error was List of listed buildings in Glasgow/13. The one after is List of Category A listed buildings in Aberdeenshire. Checking that one − it uses hb − it is the first list in thousands to do so. While ErfgoedBot was going through all these pages with no primkey, it was not touching the database at all. When it reaches Aberdeenshire, it finally tries to insert something, but by then the connection to the database had timed out. MichaelMaggs added a comment.Sep 12 2018, 4:40 PM2018-09-12 16:40:20 (UTC+0) I think I must be missing something fundamental here, as I really can't understand why Scottish monuments continue to be harvested from Wikipedia into the Monuments database even after I explained above that none of the UK campaigns (including Scotland) have used the Monuments database since 2014. Since that date all UK effort has gone into updating Wikidata directly from the official government lists. We don't use the Monuments database, do not intend to, and do not want to encourage anyone to start uploading images based on the largely unchecked and unreliable Wikipedia lists - to say nothing of the fact that Wikipedia's lists omit virtually all the Grade II sites - around 500,000 or so - which we have on Wikidata. Attempting to maintain partial and incorrect UK lists as part of the old Monuments database is, so far as I can understand, simply a waste of volunteer time. Have I missed something? Lokal_Profil added a comment.Sep 13 2018, 6:29 AM2018-09-13 06:29:42 (UTC+0) @MichaelMaggs this task is partly about the Scottish dataset, partly about finding the underlying problem and ensuring it doesn't show up somewhere else. If as you say the lists are unmaintained then I too agree that the Monuments Database should switch over to harvesting these monuments from Wikidata. We've had some problems with so large datasets in the past but it would be worth a try, it would need a separate task for setting up the necessary mapping though. I assume this applies to the Wales, England and NIR lists as well? That said unless you've set up separate tools for categorizing the images on Commons and suggesting new images which can be used on Wikidata/Wikipedia then you are still relying on the Monuments Database, it's just been running on broken and/or outdated data. The lists all still provide an upload link which feeds in to the WLM competition and don't note that they are out of date so I wouldn't be surprised if some participants are still making use of them. Multichill added a comment.Sep 13 2018, 9:14 AM2018-09-13 09:14:30 (UTC+0) In T200339#4577502, @MichaelMaggs wrote: Have I missed something? The monuments database is not only for Wiki Loves Monuments. It's a representation of what is available on Wikipedia. In my view Wikidata doesn't replace Wikipedia. These lists should probably get some attention from editors to make them better. The automatic generated lists are just a starting point. These should be expanded and articles should be written (see also https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Monuments/Philosophy#Help_Wikipedia ). Look at lists like https://en.wikipedia.org/wiki/National_Register_of_Historic_Places_listings_in_Nassau_County,_Florida to see a possible end result. MichaelMaggs added a comment.Edited · Sep 16 2018, 1:21 PM2018-09-16 13:21:30 (UTC+0) @Multichill, @Lokal_Profil thanks for the feedback. I do think that the that the Monuments Database should switch over to harvesting UK monuments from Wikidata (Scotland, Wales, England and NIR lists), assuming you still think it useful to have UK sites in it at all. The WP lists of UK sites are unmaintained by us, and have no connection whatsoever with the WLM-UK campaigns. They also omit the vast majority of grade II buildings. Of course the WP lists may receive odd edits from individual editors but those aren't reflected back to Wikidata. The primary tool we use to select new candidate images for Wikidata is here: https://tools.wmflabs.org/fist/file_candidates/#/candidates/?source=COMMONS&group=ON%20WIKIDATA&size=1000&commonscat=Images%20from%20Wiki%20Loves%20Monuments%202018%20in%20the%20United%20Kingdom. That tool reads Commons categories, and adds images to Wikidata. it does not use anything from Wikipedia nor the Monuments database. JeanFred added a comment.Edited · Sep 18 2018, 10:05 AM2018-09-18 10:05:27 (UTC+0) In T200339#4586737, @MichaelMaggs wrote: The WP lists of UK sites are unmaintained by us, and have no connection whatsoever with the WLM-UK campaigns. They also omit the vast majority of grade II buildings. Of course the WP lists may receive odd edits from individual editors but those aren't reflected back to Wikidata. This is a good question in general − does the fact that WLM UK decided to run its campaign from an other platform should mean that these lists should be in general abandoned − potentially deleted from WP? On the topic of Wikidata-reliance: I would need some more data to be definitive but some thoughts: If I understood you correctly, WLM-UK is using Monumental as its primary upload tool? However it looks like direct uploads from Monumental accounts for less than 1%. Good old Upload Campaigns still account for 95% of uploads. These may come from different sources than monuments lists of course − do I misunderstand and the Wikidata-based upload tool sends back to the upload campaigns? The primary tool we use to select new candidate images for Wikidata is here: https://tools.wmflabs.org/fist/file_candidates/#/candidates/?source=COMMONS&group=ON%20WIKIDATA&size=1000&commonscat=Images%20from%20Wiki%20Loves%20Monuments%202018%20in%20the%20United%20Kingdom. That tool reads Commons categories, and adds images to Wikidata. it does not use anything from Wikipedia nor the Monuments database. This looks good ; however you are overlooking other maintenance processes :) Between September 9th and September 17th, ErfgoedBot, relying on data from the Monuments Database, categorized 334 images from the WLM-UK campaign (222 from England, 111 from Wales, and 1 from Northern Ireland) (There is no data readily available on the categorisation done from Sep 1st to 9th) This is a modest share of the total uploads but probably around 10%. Anyhow, I actually find it great that WLM-UK runs off Wikidata − it is where all campaigns should be heading to eventually and someone had to start :) But I just wanted to point out that you are probably relying on Wikidata less than what one might think :) MichaelMaggs added a comment.Sep 18 2018, 1:40 PM2018-09-18 13:40:40 (UTC+0) @JeanFred, just some more background it case it's useful. The map that the UK campaigns use ( https://tools.wmflabs.org/fist/file_candidates/#/candidates/?source=COMMONS&group=ON%20WIKIDATA&size=1000&commonscat=Images%20from%20Wiki%20Loves%20Monuments%202018%20in%20the%20United%20Kingdom) draws its information entirely from Wikidata. When a contestant clicks a pin to upload, they are automatically taken to a pre-filled version of the relevant campaign upload wizard (England, Scotland, Wales or NI depending on the location selected). There, they can edit the filename and description before uploading. Most contestants come via that route. Users are allowed to upload via Monumental if they wish, but we de-emphasise that in our publicity as Monumental does not allow the user to choose a filename, nor to edit the description. I'm not necessarily suggesting that you do anything different, but just wanted to let you have the background as it seemed that the team might be putting quite a lot of volunteer time and effort into attempting to get some Scottish monuments into the database when that's of perhaps rather marginal benefit. Multichill added a comment.Oct 14 2018, 4:55 PM2018-10-14 16:55:54 (UTC+0) Fixing the lists right now. Example edit: https://en.wikipedia.org/w/index.php?title=List_of_listed_buildings_in_Oyne%2C_Aberdeenshire&type=revision&diff=864025741&oldid=857873175 JeanFred added a comment.Oct 15 2018, 4:06 PM2018-10-15 16:06:00 (UTC+0) In T200339#4664500, @Multichill wrote: Fixing the lists right now. Example edit: https://en.wikipedia.org/w/index.php?title=List_of_listed_buildings_in_Oyne%2C_Aberdeenshire&type=revision&diff=864025741&oldid=857873175 Looks like that did the trick: 47673 gb-sct monuments popped up in the monuments database on latest harvest :) commons.wikimedia.org/wiki/Special:Diff/324109067 Multichill added a comment.Oct 15 2018, 5:36 PM2018-10-15 17:36:44 (UTC+0) And https://en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Historic_sites/Unused_images_of_listed_buildings_in_Scotland&curid=35867555&diff=864167140&oldid=858922112 is suddenly much more work. Multichill added a comment.Oct 15 2018, 5:38 PM2018-10-15 17:38:06 (UTC+0) Last part is to check enwp template with our configuration and do some last tweaks (removing multiple options for id fields and that kind of things). I hope to be doing that soon. Multichill mentioned this in T207067: Add Scotland Scheduled Monuments in English to monuments database.Oct 15 2018, 5:43 PM2018-10-15 17:43:21 (UTC+0) And the table should probably be renamed from gb-sct to gb-sct-lb because we also have scheduled monuments, see T207067 Effeietsanders added a subscriber: Effeietsanders.Nov 18 2018, 2:07 AM2018-11-18 02:07:11 (UTC+0) Am I correct that this ticket can be marked as 'done'? Multichill closed this task as Resolved.Mar 17 2019, 8:50 PM2019-03-17 20:50:07 (UTC+0) Multichill claimed this task. Investigation done. Mostly fixed Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T200339

cc40

ERROR: Unknown error occurred when processing country gb-sct in lang en (2006, 'MySQL server has gone away') We should check if it is still missing after the next harvest. If so we should figure out w

en

An open community of Web technologists is building payments into the core architecture of the Web. 2.4 billion people stand to benefit. We're creating a set of universal payment technologies to make sending and receiving money over the Web as easy as sending an email. The Web is going to play a key role in achieving a resilient financial infrastructure and creating a more equitable future for all of us. We are making it easier to send and receive money over the Web. For over two decades, email has enabled us to communicate with our friends, loved ones, and colleagues the world over. The reason email works so well is because a group of people got together many years ago and created a standard way for email to travel across the Internet. To date, we have never sat down and done the same thing for money. There is no global standard for sending money over the Internet, and we think that there should be one. A large group of us are doing just this at the Web Payments Community Group. We are making it as easy and fast to send money around the world as it is to send an email. We are building and documenting technology that explains exactly how money moves around the world via the Web. Our approach is different from the way traditional payment technology is built. We believe in a level playing field. We operate out in the open. We are transparent. Come join us and make a difference in the world. We are using the same approach that put the Web into the hands of 2.4 billion people around the world; creating technologies through standards setting organizations, leading technology companies, governments, financial institutions, and the public at large. The Web Payments Community Group operates under the framework of the World Wide Web Consortium (W3C), the group that creates the core technology for the Web. It also participates in work at the Internet Engineering Task Force (IETF). While neither the W3C or IETF officially endorses any work performed by a community group, the purpose of this community group is to create documents that will most likely be promoted for standardization by standards setting organizations. The primary output of the Web Payments Community Group are technology documents that may be elevated to world standards through standardization bodies like the W3C and IETF, and then implemented by technology companies, merchants, payment processors, banks, and governments. A summary of the technologies we are working on can be found below, further details can be found on the specifications page. Payments typically revolve around a particular product or service, so being able to describe that product or service on the Web in a standardized way is important. It is also crucial that the description of the product or service is machine-readable to ensure that search engines can easily find the things you want. New breakthroughs in cryptographic currencies and storing and transferring value on the Web provide multiple solutions to executing a monetary transaction on the Web. These technologies are being standardized into something that can be placed into browsers and mobile devices. Machine-readable digital receipts provide detailed information after a transaction has occurred. This enables you to more closely track where your money is going and more easily store your proofs-of-purchase. We are making it so your financial data is truly portable, and owned by you. One of the hardest things about transacting online is making sure that the person you're dealing with is reputable. We're working with browser vendors to make sure that the identity you use online is expressive, secure, and that you can count on the merchants you deal with online to be trustworthy. Security is our top priority, everything we work on depends on high standards with respect to secure systems. Greatly reducing fraud is dependent on stronger security features. We are working with the best security experts in the world and are hardening security practices on the Web. A programmable financial infrastructure, built on the Web... that is what we hope to achieve in the next several years. The democratization of these financial tools will lower the barrier to entry for new businesses and financial products. An open financial architecture will usher in a more equitable future. In order to build a payment system that works for the world, you have to build it differently than most payment systems in use today. You have to be open, transparent, and try to get input from everyone affected by payments on the Web. There are no requirements to join this work other than a passion to help make the world a better place. We hold weekly teleconferences that are open to the public. We have a mailing list where we discuss this work which is free to join and participate. We've removed most of the barriers to entry because this will affect all of us, so all of us should have a say in how this technology is built. Web Payments Community Group | Weekly Teleconferences | Web Payments Mailing List | @w3payments Created by the Web Payments Community Group. Shared with love under a CC-BY license. Thanks to our contributors.

https://web-payments.org:443/

cc40

An open community of Web technologists is building payments into the core architecture of the Web. 2.4 billion people stand to benefit. We're creating a set of universal payment technologies to make s

en

Tgr committed rEMMV3bb2b8185a45: Fix canvas height calculation (authored by Tgr).Feb 19 2015, 7:20 AM2015-02-19 07:20:15 (UTC+0) Tgr mentioned this in rEMMV7e1dcc77f776: Fix canvas height calculation.Feb 20 2015, 11:55 PM2015-02-20 23:55:12 (UTC+0) Tgr mentioned this in rEMMVe3da4d9094ee: Fix canvas height calculation. Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/rEMMV3bb2b8185a45fbc0c01ad53f8810fdf9ed7ca4e7

cc40

Tgr committed rEMMV3bb2b8185a45: Fix canvas height calculation (authored by Tgr).Feb 19 2015, 7:20 AM2015-02-19 07:20:15 (UTC+0) Tgr mentioned this in rEMMV7e1dcc77f776: Fix canvas height calculation.

en

With the upcoming Board of Trustees Election 2022, Movement Strategy and Governance Team’s facilitators talked to several Election Volunteers from different communities to hear about their experiences and motivation to join the Election Volunteer program. This blog is a result of collaborative writing between the MSG facilitators and EV program volunteers. Please tell us about yourself. I am Faisal Ali from Accra, Ghana. I am User:DaSupremo on the Wikimedia Movement. I created my Wikipedia account in 2014 when I was a student of Kwadaso College of Agriculture. I began an active volunteer in 2014. Currently, I supply optical frames to eye hospitals and clinics. I contribute to English Wikipedia and also translate articles to Hausa during my leisure time. I am a member of Open Foundation West Africa, Wikimedia Ghana User Group, Global Open Initiative Foundation and the Hausa Wikimedians User Group to mention a few. I also edit on Wikidata and also on Wikicommons. I also do translations on Meta from English to Hausa and also share the information to the Hausa community. What motivated you to join the EV program? I first joined the Election Volunteers program in 2021 when I saw a message on the Wikimedia General chat page on Telegram. The message was from Mahuton concerning translating of statements made by candidates of MCDC to other languages. I applied to translate from English to Hausa. Even though only statements were needed to be translated, I translated all information on the page. I translated information of 72 candidates. I was motivated to join so that I can help project the Hausa language on the web so that others who can read the language get to know what is happening in the Wikimedia Movement. In so doing, promote the aim of the movement to make knowledge easy and accessible to all. What are some challenges and successes that you would like to share? As a volunteer of the program, I have translated and shared monthly tasks to the Hausa Community on our WhatsApp page. Challenges I am facing now is the breakdown of my PC which has limited my contributions even though I use my phone to edit now. Another challenge is the high cost of data for internet connectivity. I also try to learn and collaborate with other volunteers. Looking ahead: What are your expectations for the upcoming 2022 BoT Elections? What would you like to do, and how would you like to be involved? My expectations for the 2022 BoT Elections should be diversified to include candidates from all parts of the world. Experienced members who know much about the Movement should also be involved. As a volunteer, I would like to share information to members closer to me so that they also take part in the voting process. I would also like to translate to Hausa. Comments are closed automatically after 21 days. Posted in Main page (EN), Movement StrategyTagged Board of Trustees, Election volunteers Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. सर्व मानव ज्ञान की ध्वनि की खोज प्रारंभ: इस वैश्विक प्रतियोगिता का उद्देश्य विकिपीडिया और विकिमीडिया परियोजनाओं के लिए सर्वप्रथम ध्वनि लोगो की पहचान करना है 21 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2022/05/04/learn-about-election-volunteers-dasupremo/

cc40

With the upcoming Board of Trustees Election 2022, Movement Strategy and Governance Team’s facilitators talked to several Election Volunteers from different communities to hear about their experiences

en

⚓ T183747 Create context-dependent sort key SECTIONSORT for use on Wiktionary (in addition to DEFAULTSORT) In most Wiktionary projects, a single page has several language sections, each of which has one or more entries of the same spelling (ex. wikt:en:日本). Currently, the magic word DEFAULTSORT works for an entire page, which means we cannot define a default sort key for each language in the same page. If we have a magic word for sort key for each language section, it will be much easier to correctly categorize pages on Wiktionary. My proposal is the new magic word SECTIONSORT, which defines a default sort key immediately after its use up to its next use. By using SECTIONSORT, each language section can have an appropriate default sort key according to each language’s convention. T18691: RFC: Section header "share" link T150841: [feature] Change color of the link regarding to the content of the sections in the page Takasugi_Shinji created this task.Dec 28 2017, 1:45 PM2017-12-28 13:45:22 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 28 2017, 1:45 PM2017-12-28 13:45:22 (UTC+0) Aklapper renamed this task from Context-dependent sort key: SECTIONSORT to Create context-dependent sort key SECTIONSORT for use on Wiktionary (in addition to DEFAULTSORT).Dec 28 2017, 1:47 PM2017-12-28 13:47:01 (UTC+0) Aklapper triaged this task as Low priority. Aklapper added a project: MediaWiki-Parser. Noe added a project: All-and-every-Wiktionary.Dec 29 2017, 1:04 PM2017-12-29 13:04:50 (UTC+0) Noe added a subscriber: Noe. ssastry moved this task from Backlog to Wikitext new features on the MediaWiki-Parser board.Apr 6 2018, 10:31 PM2018-04-06 22:31:07 (UTC+0) Noe mentioned this in T150841: [feature] Change color of the link regarding to the content of the sections in the page.Aug 23 2018, 9:16 AM2018-08-23 09:16:13 (UTC+0) Automatik added a subscriber: Automatik.Oct 30 2018, 12:37 AM2018-10-30 00:37:54 (UTC+0) Naggy_Nagumo added a subscriber: Naggy_Nagumo.Feb 22 2019, 8:24 AM2019-02-22 08:24:21 (UTC+0) Noe mentioned this in T18691: RFC: Section header "share" link.Oct 15 2019, 7:25 AM2019-10-15 07:25:34 (UTC+0) Ltrlg added a subscriber: Ltrlg.Oct 22 2019, 12:36 PM2019-10-22 12:36:53 (UTC+0) Urhixidur added a subscriber: Urhixidur.Oct 25 2019, 2:29 PM2019-10-25 14:29:14 (UTC+0) Thibaut120094 added a subscriber: Thibaut120094.Dec 21 2020, 5:03 PM2020-12-21 17:03:39 (UTC+0) Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T183747

cc40

⚓ T183747 Create context-dependent sort key SECTIONSORT for use on Wiktionary (in addition to DEFAULTSORT) In most Wiktionary projects, a single page has several language sections, each of which has o

en

F34574855: Screenshot 2021-08-03 at 15-44-59 Information for User Lucas Werkmeister (WMDE) sandbox - Wikidata.png Most (all?) Lua functions that return part of an entity are meant to resolve redirects, e.g. given Q123 is a redirect to Q321, mw.wikibase.getLabel('Q123') should return the label of Q321. Some of the redirect resolving functionality got introduced by accident and so the question of usage tracking did not come up. These methods currently track only the redirect but not the redirect target. What should probably happen is that if the given entity is a redirect, track an all usage for the redirect (if anything at all changes about it, we need to know), and track the relevant aspect (= same as what would be tracked if it wasn't a redirect) of the target. usages for both the redirect and target are correctly tracked wip: resolve redirects for usage DataAccess: Add usage for statements when entity id is different P123 old e-mail about dual booting woes Jakob_WMDE created this task.Apr 22 2021, 8:11 AM2021-04-22 08:11:10 (UTC+0) Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 22 2021, 8:11 AM2021-04-22 08:11:11 (UTC+0) Jakob_WMDE updated the task description. (Show Details)Apr 22 2021, 8:12 AM2021-04-22 08:12:14 (UTC+0) Maintenance_bot added a project: Wikidata.Apr 22 2021, 8:45 AM2021-04-22 08:45:56 (UTC+0) • Addshore added a project: wdwb-tech.Apr 22 2021, 3:58 PM2021-04-22 15:58:44 (UTC+0) • Addshore removed a project: Wikidata-Campsite.Apr 22 2021, 3:59 PM2021-04-22 15:59:21 (UTC+0) • Addshore moved this task from Inbox to To Prioritize on the wdwb-tech board.Jun 7 2021, 6:53 AM2021-06-07 06:53:55 (UTC+0) • Addshore moved this task from To Prioritize to Triaged Low (0-50) on the wdwb-tech board.Jun 11 2021, 9:38 AM2021-06-11 09:38:11 (UTC+0) Lydia_Pintscher added projects: Wikidata-Campsite, TestMe.Jul 4 2021, 11:17 AM2021-07-04 11:17:56 (UTC+0) Lydia_Pintscher added subscribers: Manuel, Lydia_Pintscher. @Manuel We should check here if this affects what is taken into account for watchlist notifications and purging articles. My assumption is we're missing out on showing som things in watchlist that should be shown and we're not purging some articles when we should. That'd be not great... Lucas_Werkmeister_WMDE added subscribers: Ladsgroup, hoo, Lucas_Werkmeister_WMDE.Jul 6 2021, 8:57 AM2021-07-06 08:57:05 (UTC+0) @Ladsgroup @hoo do you think tracking an “all” usage in this case would be okay? Or should it maybe be some other usage (“other”, or maybe a new type)? Ladsgroup added a comment.Jul 6 2021, 11:56 AM2021-07-06 11:56:03 (UTC+0) "X" usage is deprecated and has caused all sorts of issues including a major outage in ruwiki, we really should avoid using it unless absolutely necessary. If I understand it correctly, the usage is transient so if I check P123 of Q1 but Q1 is a redirect to Q2, I'll get just entity usage aspect of Q2#C.P123 instead of Q1#C.P123 so nothing major is lost. The only problem I can see is that when Q1 stops being a redirect and then the client wiki won't be notified to pick up the new data but that's pretty rare. One suggestion would be to have it in O (e.g. being Q1#O) and reverting a redirect making (what's the correct name for it?) would count as the same group as changing alias (by setting otherchanges to true in the change object). Would that work? Lucas_Werkmeister_WMDE added a comment.Jul 6 2021, 12:07 PM2021-07-06 12:07:53 (UTC+0) In T280910#7198823, @Ladsgroup wrote: "X" usage is deprecated and has caused all sorts of issues including a major outage in ruwiki, we really should avoid using it unless absolutely necessary. If I understand it correctly, the usage is transient so if I check P123 of Q1 but Q1 is a redirect to Q2, I'll get just entity usage aspect of Q2#C.P123 instead of Q1#C.P123 so nothing major is lost. No, you get a usage on Q1 (not quite sure what kind of usage – my sandbox page apparently uses “some labels”, rather than specifically the English label), and nothing on Q2. So edits on Q2 have no effect. Ladsgroup added a comment.Jul 6 2021, 4:38 PM2021-07-06 16:38:23 (UTC+0) okay, that's not great and needs fixing indeed but I suggest fixing it by making it transient Manuel moved this task from Needs Tech Work to Unconnected Stories on the Wikidata-Campsite board.Jul 7 2021, 7:14 AM2021-07-07 07:14:29 (UTC+0) Manuel removed a project: TestMe. Lucas_Werkmeister_WMDE set the point value for this task to 8.Jul 7 2021, 10:39 AM2021-07-07 10:39:25 (UTC+0) Manuel renamed this task from Usage tracking for redirect resolving Lua functions to Wikidata Client usage tracking for redirect resolving Lua functions.Jul 7 2021, 10:43 AM2021-07-07 10:43:45 (UTC+0) Manuel updated the task description. (Show Details) Agabi10 added a subscriber: Agabi10.Jul 7 2021, 10:52 AM2021-07-07 10:52:43 (UTC+0) In T280910#7198841, @Lucas_Werkmeister_WMDE wrote: No, you get a usage on Q1 (not quite sure what kind of usage – my sandbox page apparently uses “some labels”, rather than specifically the English label), and nothing on Q2. So edits on Q2 have no effect. The usage of "some labels" instead of the English label looks fine, because Template:Q uses the user language for the label and that language can be something other than English. That usage should still be tracked for the redirect target instead though (or to both of them). Lucas_Werkmeister_WMDE edited projects, added Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)); removed Wikidata-Campsite.Jul 7 2021, 10:59 AM2021-07-07 10:59:56 (UTC+0) Maintenance_bot moved this task from incoming to in progress on the Wikidata board.Jul 7 2021, 11:15 AM2021-07-07 11:15:38 (UTC+0) Maintenance_bot moved this task from Triaged Low (0-50) to Active on the wdwb-tech board. gerritbot added a comment.Jul 9 2021, 9:04 PM2021-07-09 21:04:54 (UTC+0) Change 703873 had a related patch set uploaded (by Ladsgroup; author: Ladsgroup): [mediawiki/extensions/Wikibase@master] DataAccess: Add usage for statements when entity id is different gerritbot added a project: Patch-For-Review.Jul 9 2021, 9:04 PM2021-07-09 21:04:54 (UTC+0) Ladsgroup added a comment.Jul 12 2021, 3:42 AM2021-07-12 03:42:17 (UTC+0) So the patch I made above would fix the statement usage and tested locally ^. Fixing label and other usages has an intricacy. We look up values of other usages through other means (like term store) meaning we should not follow redirect directly, unless we load the whole item using entity lookup which we really shouldn't. Maybe there is just a check to see if the item id resolves in a redirect (by looking up the page table?) and I missed it. toan claimed this task.Jul 15 2021, 1:19 PM2021-07-15 13:19:11 (UTC+0) toan moved this task from To Do (prioritised from top to bottom) to Doing on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board. gerritbot added a comment.Jul 16 2021, 9:44 AM2021-07-16 09:44:48 (UTC+0) Change 704930 had a related patch set uploaded (by Tobias Andersson; author: Tobias Andersson): [mediawiki/extensions/Wikibase@master] wip: resolve redirects for usage toan added a comment.Jul 16 2021, 9:52 AM2021-07-16 09:52:44 (UTC+0) I'm gonna put this back in todo as it will not be very likely finished by the end of today. I've uploaded some thoughts on how we could re-use the already existing redirect resolution that happens when looking up terms from the termfallbackcache. In the WikibaseLanguageIndependentLuaBindings we are using two different redirect resolvers that only differ by what they return as far as I can tell. By re-using them we can do the redirect lookup for free and update the usage with that? Never got it to actually update the thing in the database so I'm probably lacking in the understanding on how these usages get updated once they already exists. This method of updating(currently not updating) was inspired by looking at https://gerrit.wikimedia.org/r/703873 but I'm not sure if this is the correct way to update all of these usages? To some extent I'd probably prefer notifying the client of redirects via some other method, like a job might be a valid alternative? toan removed toan as the assignee of this task.Jul 16 2021, 9:53 AM2021-07-16 09:53:27 (UTC+0) toan moved this task from Doing to To Do (prioritised from top to bottom) on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board. toan added a subscriber: toan. Michael claimed this task.Jul 16 2021, 10:31 AM2021-07-16 10:31:40 (UTC+0) Michael moved this task from To Do (prioritised from top to bottom) to Doing on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board. Restricted Application added a project: User-Michael. · View Herald TranscriptJul 16 2021, 10:31 AM2021-07-16 10:31:40 (UTC+0) gerritbot added a comment.Jul 16 2021, 1:56 PM2021-07-16 13:56:47 (UTC+0) Change 704930 abandoned by Tobias Andersson: [mediawiki/extensions/Wikibase@master] wip: resolve redirects for usage gerritbot added a comment.Jul 20 2021, 3:56 PM2021-07-20 15:56:35 (UTC+0) Change 705711 had a related patch set uploaded (by Michael Große; author: Michael Große): [mediawiki/extensions/Wikibase@master] Track usage on redirects Michael moved this task from Doing to Peer Review on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.Jul 22 2021, 9:04 AM2021-07-22 09:04:58 (UTC+0) gerritbot added a comment.Jul 23 2021, 11:05 AM2021-07-23 11:05:56 (UTC+0) Change 705711 merged by jenkins-bot: [mediawiki/extensions/Wikibase@master] Track usage on redirects Lucas_Werkmeister_WMDE moved this task from Peer Review to Test (Verification) on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.Jul 23 2021, 11:09 AM2021-07-23 11:09:08 (UTC+0) ReleaseTaggerBot added a project: MW-1.37-notes (1.37.0-wmf.16; 2021-07-26).Jul 23 2021, 12:00 PM2021-07-23 12:00:17 (UTC+0) Lucas_Werkmeister_WMDE added a comment.Aug 3 2021, 1:45 PM2021-08-03 13:45:50 (UTC+0) Entity usage on my sandbox page looks sensible now: Manuel closed this task as Resolved.Aug 3 2021, 1:46 PM2021-08-03 13:46:10 (UTC+0) Thx for verifying this @Lucas_Werkmeister_WMDE! Ladsgroup added a comment.Aug 3 2021, 1:58 PM2021-08-03 13:58:32 (UTC+0) In T280910#7255504, @Lucas_Werkmeister_WMDE wrote: Entity usage on my sandbox page looks sensible now: Promotion: After seeing this I changed the message for other aspect to reflect reality: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/709711 Log In to Comment Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL

https://phabricator.wikimedia.org/T280910

cc40

F34574855: Screenshot 2021-08-03 at 15-44-59 Information for User Lucas Werkmeister (WMDE) sandbox - Wikidata.png Most (all?) Lua functions that return part of an entity are meant to resolve redirects

en

Join thousands of researchers, policymakers, designers, and educators who rely on Anthropocene to keep up to date on the latest sustainability science and innovations. Newsletters Newsletters Science Dispatch (weekly) Fixing Carbon (twice a month) Sign up for Anthropocene's free newsletters Reality Is Too Confining We know that nature experiences can change environmental behavior—but it turns out those experiences don’t have to be real. A woman peers through goggles embedded in a large black helmet. Forest sounds emanate from various corners of the room: a bird chirping here, a breeze whispering there. She moves slowly around the room. On the wall, a flat digital forest is projected so observers can get a rough idea of her surroundings; but in her mind’s eye, this undergrad is no longer pacing a small, cramped room in a university lab. Thanks to that black helmet, she’s walking through the woods. The latest work with virtual reality builds upon roughly half a century of behavioral studies indicating that humans’ willingness to shift behavior is directly correlated to our sense of control. In a minute, she’s handed a joystick that looks and vibrates like a chainsaw, and she’s asked to cut down a tree. As she completes the task, she feels the same sort of resistance she might feel if she were cutting down a real tree. When she leaves this forest and re-enters the “real” world, her paper consumption will drop by 20 percent, and she will show a measurable preference for recycled paper products. Those effects will continue into the next few weeks, and researchers hypothesize it will be a fairly permanent shift. By comparison, students who watch a video about deforestation or read an article on the subject will show heightened awareness of paper waste throughout that day—but they will return to their baseline behavior by the end of the week. The tree-cutting study is one of many that Stanford University researchers have conducted in its Virtual Human Interaction Lab over the past several years in an attempt to figure out the extent to which a simulated experience can affect behavior. And it’s part of a growing body of research that suggests virtual experiences may offer a powerful catalyst for otherwise apathetic groups to begin caring about issues and taking action, including on climate change. That’s important, because even though time spent in nature has been proven to be quite beneficial to human health, whether or not humans repay the favor tends to rely on the type of nature experiences they have in their youth. A 2006 study on the relationship between nature experiences and environmentalism found that while those who had spent their youth in “wild” nature, defined as hiking or playing in the woods, were more likely to be environmentalists as adults, those who had been exposed to “domesticated” nature—defined as visits to parks, picking flowers, planting seeds, or tending to gardens—were not. (1) Given the unlikelihood of every child having a “wild” nature experience, researchers are on the hunt for other ways to cultivate environmentally responsible behavior. The latest work with virtual reality builds upon roughly half a century of behavioral studies indicating that humans’ willingness to shift behavior is directly correlated to our sense of control. Climate change, like many large-scale environmental issues, is a problem which few people feel they have a direct impact on—for better or worse. Jeremy Bailenson, a cognitive psychologist and founding director of Stanford’s Virtual Human Interaction Lab, sees particular value in virtual reality related to climate change because it allows for a combination of real experience with boundless possibilities: the brain treats the virtual experience as real but, at the same time, knows that anything is possible in the simulation. “One can viscerally experience disparate futures and get firsthand experience about the consequences of human behavior,” Bailenson said. And it doesn’t always require expensive headgear. A team at Harvard recently launched EcoMUVE, a desktop computer–based virtual pond ecosystem. It’s designed to teach students basic biological processes such as photosynthesis and decomposition. The Harvard team also launched EcoMOBILE, a corresponding augmented reality app which enables students to take the EcoMUVE experience with them. For example, teachers take kids to a nearby pond and use EcoMOBILE to show them how the town dumped garbage there 60 years ago and nearly filled in what is today a pristine, natural pond. The app shows them how plants around the pond are turning sunlight into energy and reveals what microscopic pond life is doing under the water’s surface. It also walks them through the real-world collection of water samples, which it helps them to analyze. A handful of Massachusetts high schools have also tested an MIT-developed augmented reality app called Time Lapse 2100. With the app, users set various policies that affect the environment, and then the program shows them what would happen if those policies were implemented. Back at the Stanford lab, researchers are also testing their sea legs. In their Coral Reef virtual reality game, players become a tall piece of purple coral off the coast of Italy, near Ischia. Over the course of a 14-minute lesson, they are taken through the experience of being coral in an acidifying ocean. At first, the surrounding ocean is filled with an abundance of sea life. Waves around the reef are simulated by floor vibrations and ocean sounds. A lab technician periodically touches the participants with a stick in synchronized motions to coincide with what they see as a fishing net hitting the reef. Then acidification sets in. Sea life begins to die off all around. The reef begins to lose its color, as does the piece of coral the participants have become. Bailenson and his team have tested the simulation with college students. They followed the participants over weeks and compared them with a group that had simply watched a video about how ocean acidification affects coral reefs. The team found that the virtual reality experience catalyzed a longer-lasting change in attitude than any shifts stirred by the video. Amy Westervelt, an environmental journalist living in Truckee, California, is a cofounder of reporting project Climate Confidential. Amy’s work has been published most recently in the Wall Street Journal, Fast Company, and the Guardian. 1. Wells, N.M. and K.S. Lekies. 2006. Children, Youth and Environments 16(1):1–24. This story was adapted from an article produced by Climate Confidential and released for re-use under a Creative Commons Attribution 4.0 International License.

https://www.anthropocenemagazine.org/2014/10/reality-is-too-confining/

cc40

Join thousands of researchers, policymakers, designers, and educators who rely on Anthropocene to keep up to date on the latest sustainability science and innovations. Newsletters Newsletters Science

en

The tomb of Bibi Jawindi in Uch Sharif, Punjab, Pakistan, captured for Wiki Loves Monuments 2016. Photo by Usamashahid433, CC BY-SA 4.0. We are excited to announce the successful grantees from the third round of the Wikimedia Foundation’s Project Grants program. Project Grants support individuals, groups and organizations to implement new experiments and proven ideas, whether focused on building a new tool or gadget, organizing a better process on your wiki, researching an important issue, coordinating an editathon series or providing other support for community-building. We launched the Project Grants program in 2016 to pilot new program designs created in response to community feedback. In early 2017, after two rounds of funding, we conducted a community survey to understand how the changes have impacted our grantees. Our report on the results of that survey are now available on Meta. Project Grants are reviewed by a volunteer committee currently made up of 17 Wikimedians who come from over 13 different wikis and collectively speak over 15 languages. Outside of our Project Grant committee work, members edit, review, and translate content; help govern local chapters; write software; organize off-wiki events; facilitate workshops; work as sysops and bureaucrats; verify copyright and licensing permissions; draft and discuss project policies; and recruit and welcome new users to Wikimedia projects. Many members also serve as advisors to new grantees, helping to answer questions, connect them to relevant resources, and comment on monthly and midpoint reports. In this latest round, 32 eligible proposals were submitted for the committee’s review. The committee has recommended that ten projects be funded to receive $224,900, divided into three themes: online organizing, offline outreach, and software. Here is what we are funding: Online organizing: two projects funded The ceiling in the Sioni Cathedral in Tbilisi, seen from Wiki Loves Monuments 2016. Photo by Diego Delso, CC BY-SA 4.0. Wiki Loves Monuments 2017 coordination: This year, the Wiki Loves Monuments International Team will continue to encourage content on diverse cultural heritage sites in this annually-run contest. By addressing the need for partnerships and development of tools to support participants, this project hopes to bolster local communities to contribute and collaborate on the Wikimedia projects, with a focus on Commons and Wikidata. Contest toolkits and prize funds: Led by a prolific English Wikipedian, Dr.Blofeld, this project aims to equip prospective contester organizers with toolkits and design ideas, enabling them to customize their own campaigns. In addition, the project will include a large contest to boost the geographic diversity of representation of women on English Wikipedia. Offline outreach: seven projects funded Wiki Loves Monuments in Perú: Recently-recognized affiliate Wikimedians of Peru User Group will organize a Wiki Loves Monuments contest through outreach efforts with the Ministry of Culture in Peru as well as with newer participants outside of Lima to contribute national and cultural heritage to the movement. Multimedia Documentation of Traditional Trades and Crafts of Eastern, Northern and Up-Country Sri Lanka: Through extensive outreach in underrepresented regions in Sri Lanka, this project plans to expand knowledge of the traditional industries, agricultural trades, and crafts of Sri Lanka. With integrated support from the Noolaham Foundation, engagement with local communities through their livelihoods will be a significant step toward documenting cultural heritage in Tamil Wikipedia, Commons, Wiktionary, and Wikibooks. First Wikipedian in (Academic) Residence in Latin America: El Colegio de México will lead and coordinate with libraries and academic institutions in Mexico to develop and disseminate best practices in knowledge-sharing through Wikimedia projects. Wikimedian in Residence at UNESCO 2017–18: As a follow-up to a previous Foundation grant with the United Nations Educational, Scientific and Cultural Organization (UNESCO), John_Cummings and Navino Evans will facilitate long-term infrastructure to support ongoing content donations, including media and text for Wikipedia and Commons, and structured data for Wikidata.  Using the UNESCO partnership as a model, they will educate and encourage other scientific and cultural institutions to contribute open license material. Engaging with Academic Librarians and Sororities to Address the Gender Gap: A returning grantee from the Inspire Campaign, West Virginia University Libraries’ Wikipedian in Residence for Gender Equality will foster partnerships with three other academic institutions. The project will develop a scalable model for cross training student life and university library staff to promote Wikipedia editing as an option for sororities to meet their community service requirements. Wikimedia UG Nigeria/Wikipedian in Residence: Partnering with pan-African cultural and tourism program Goge Africa, Wikimedia User Group Nigeria aims to contribute and provide support for media of heritage content. UG GLAM Macedonia/Wikipedian in Residence: Through education and training, two Wikipedians in Residence will enable GLAM institutions in Skopje to produce public domain material to Macedonian Wikimedia projects. This will be an opportunity for the Macedonian community to collaborate with the State Archives in the Republic of Macedonia and City Library “Braka Miladinovci,” and to target areas for volunteers to explore and release new content to the movement. Software: one project funded EveryPolitician will populate Wikidata with structured data reflecting interrelationships of heads of government. Such information has many applications, including empowering citizen activists who fight corruption in leadership around the world. Screenshot, public domain/CC0. EveryPolitician: UK-based organization mySociety aims to populate Wikidata with well-structured, consistent data on elected officials from around the world. EveryPolitician combines data from multiple primary and secondary sources from over 3.6 million data points on almost 73,000 politicians in 233 countries and territories. Through technical infrastructure and volunteer workflows, the project will establish ongoing updates to Wikidata about political leadership around the world, providing access to crucial information for citizens seeking to engage and advocate with their elected representatives. Wikimedians in Residence (WiRs) play an important role in our movement.   They serve as critical liaisons between mission-aligned partner organizations and our extensive community of volunteer contributors.  Through these partnerships, high quality content curated and maintained by the hosting organization becomes accessible online through the Wikimedia projects.  Ideally, the hosting organization funds the WiR’s work, though the Wikimedia Foundation occasionally offers supplemental funding support when the hosting organization is not able to fully cover costs and the specific opportunity is strategically valuable for the Wikimedia movement.  Foundation-funded WiRs do not directly create content; instead, they organize and empower volunteers with the resources available through the hosting organization in order to generate meaningful new content on our projects.  The goal is to leverage the partnership to build a platform that assures sustainable outcomes long after the WiR has completed their service.  WiRs might do this in many ways, including training organizational staff to upload content, implementing infrastructure to enable ongoing content donations, and creating online and offline opportunities for volunteers to engage in content creation and curation using those donations. This year, we received six requests for Wikipedians in Residence and we have funded five of them.  Two veteran WiRs will continuing their existing work: John Cummings (now working with Navino Evans, will solidify workflows that will make Wikimedia projects ongoing recipients of UNESCO’s extensive data and collections; Kelly Doyle, based in the West Virginia University Libraries, will extend her reach to three more campuses, establishing a model to make editing Wikipedia a standardized component of sorority life across the United States.  In addition, several new WiRs will serve at El Colegio de México, Goge Africa, the State Archives in the Republic of Macedonia and City Library “Braka Miladinovci”. The oldest and perhaps best-known international photo contest in the Wikimedia movement, Wiki Loves Monuments (WLM) has been inspiring and galvanizing volunteers since its origin in 2010.  Every year, it drives widespread photo-documentation of the world’s built cultural heritage.  In addition to attracting jaw-droppingly beautiful photo contributions to our projects, the contest serves an important role in supporting Wikimedian communities.  Because it provides a clear, accessible procedure that volunteer groups with widely varying levels of experience can follow, WLM supports national-scale contests in more countries each year.  This offers both new and veteran groups a relatively simple opportunity to participate in an international activity with richly diverse cultural results.  Cumulatively, these results are significant:  according to the international organizing team, WLM has now brought together the largest collection of monument data in the world. This year, we funded two requests for WLM activities:  The international coordinating team will support the umbrella infrastructure that makes the contest as a whole possible.  In addition, we will welcome a national contest in Perú. We received many compelling proposals this year that the committee decided not to fund. We encourage applicants who were not successful in this round of funding to refine and resubmit their proposals in upcoming rounds or to pilot a smaller project in Rapid Grants. Return proposals that have been revised in response to community and committee feedback are warmly welcomed. The open call for Project Grants 2017 Round Two will launch on August 28, 2017, with applications due September 26, 2017. We look forward to reviewing your suggestions and future submissions, but for now we say congratulations to the successful grantees and encourage you to follow their progress as they begin work in the coming weeks. Marti Johnson, Program Officer, Individual Grants Morgan Jue, Community Resources Contractor Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff. WIRs FTW, but I see there is quite a lot of variance among them in terms of cost/outputs. Posted in Affiliates, Foundation, From the archives, GLAM, GrantmakingTagged committee, community, Grants, Project grants, Review, Wikimedia, Wikimedia Blog (EN Archive) Welcome to Diff, a community blog by – and for – the Wikimedia movement. Join Diff today to share stories from your community and comment on articles. We want to hear your voice! Subscribe to Diff via Email Enter your email address to subscribe to Diff and receive notifications of new posts by email. सर्व मानव ज्ञान की ध्वनि की खोज प्रारंभ: इस वैश्विक प्रतियोगिता का उद्देश्य विकिपीडिया और विकिमीडिया परियोजनाओं के लिए सर्वप्रथम ध्वनि लोगो की पहचान करना है 21 September 2022 by Wikimedia Foundation Join the Wikimania Hackathon, August 12-14 2022! 29 July 2022 by Melinda Seckington Down the Rabbit Hole The journey to make Wikipedia’s technology more equitable 9 May 2022 by Jazmin Tanner This is Diff, a Wikimedia community blog. All participants are responsible for building a place that is welcoming and friendly to everyone. Learn more about Diff. A Wikimedia Foundation Project Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted.

https://diff.wikimedia.org/2017/06/09/project-grants-round-one-2017/

cc40

The tomb of Bibi Jawindi in Uch Sharif, Punjab, Pakistan, captured for Wiki Loves Monuments 2016. Photo by Usamashahid433, CC BY-SA 4.0. We are excited to announce the successful grantees from the thi