Jump to content

glossaLAB:To-Do List

From glossaLAB
Purpose & Methodology: This page contains the list of tasks to be done, classified according to priority.
  • We describe them in English considering that any member of the larger team may collaborate.
  • Thanks to the history tool, once a task has been conpleted it suffices removing the item completely.
  • If you take a task that is still unfinished but you are ocuppying, use the following template to mark it as such: {{task | [ongoing, paused, cancelled, done] | [task description] | ~~~}}, where '~~~' automatically enters your own username if you're taking the task, but you can also enter other username(s) who puts hands on the task.
  • Feel free to add any task you consider interesting to be addressed.
  • If you wish to activelly cooperate please added to the watch list and ensure your email is confirmed (user preferences > user profile > email options)

High priority

  • ✅ Form:Proposal should include a new Pending improvements textarea field, applicable whenever a page is rejected. The field contents should be stored at PAGENAME/Pending improvements.
    • ❌ PF requires heavy JS trickery to create two pages on a single save; we don't want to. Better, we can create a two-step individual review process, based on two, consecutive forms: first form will allow to introduce the data regarding 'evaluation' and 'comments to author'. Saving first form would redirect automatically to a new, second form, allowing to define 'suggested improvements' to the page. This would be saved on 'Talk:PAGENAME/Suggested improvements', as a mean to separate suggestions from contents.
    • ✅ MediaWiki:Gadget-ReviewTool generates a new menu item on every 'Category:Proposal' page, called 'Improvements', that allows to create/edit 'Talk:PAGENAME/Suggested improvements' through a form. Contents of this page are automatically transcluded on the proposal page by means of existent Template:Comments.
  • Template:Infobox proposal should show an alert box, noticing the existence of PAGENAME/Pending improvements.
  • 🏃 The revision mechanism, based first in individual reviews (which suffices for gL.edu) has to be set up. This is required to fulfil the workflow of a clarification activity.
    • ✅ First approach has been implemented (31/12/25-4/1/26): An 'Add review'/'Añadir revisión' is shown next to 'Edit source' whenever a 'curator' visits an 'In review/En revisión' page. Note that this behaviour will only be possible when clicking on the 'Add review' automatic link, and not by visiting the form page. The revision created through 'Add review' link is listed automatically on the infobox of the reviewed article. The creation of the review link is based on JavaScript code, Extension:Gadgets and moving the JS code to MediaWiki:Gadget-ReviewTool.
    • An enhanced approach should move the article to a 'proofreading' state (corrección de pruebas) or directly to publication as collection article.
  • ✅ In the proposal infobox: make that the clarification activities to which a given proposal belongs is obtained from a semantic query requesting what clarification activities include the term among the ones proposed by them.
    • Change formats to make parts of the infobox more easily recognisible.
  • Help pages for clarification activities have to be reformed to adapt them to the current workflow. The idea is to breake it down into smaller pages whose development can be distributed into smaller units/tasks:
    • Edit with forms, code or visual editor.
    • How to edit your user profile.
    • How to autoconfirm your user to enable communication.
    • How to open a clarification proposal collaboratively.
    • How to comment an existing article.
    • How to edit a draft proposal.
    • How to introduce references.
    • How to use AI. Misuse warnings.
    • How to enrole into a clarification proposal.
    • How to open and coordinate a clarification activity.
    • How to add an institution.
    • How to add a knowledge domain.
    • Central help pages.
    • Language approach.
  • Design central pages providing information about sections (collections, clarification activities, congresses, news), collecting new adds, highlighted articles.
  • All project team members should have autoconfirmed glossaLAB accounts, which is not the case in most of the cases, otherwise the platform cannot communicate with them.
  • Ency needs to operationalise links. To that purpose, assignation mechanism has be developed.
  • Fix the ambiguities and misleading categorisation of Person properties: Highest Academic Degree vs Pursued Academic Degree and associated fields (which belongs to title).
    • ✅ To SOLVE these ambiguities new help pages have been created where Academic degree and Professional level is clarified. However, these pages have been linked in the information tips given in the Person form, and is still PENDING to make that professional and academic categories in different languages correspond to the same object instead of as it is now (e.g. Bachelor Degree and Grado, or as it is now called, are different). This make no sense when we want for instance filter for all students studying bachelor degrees. (José María Díaz Nafría [JDíaz] (talk) 13:01, 14 January 2026 (CET)): PARTIALLY FIXED on Form:Person. User is offered with a verbose level list (like 'Bachelor's or Equivalent Level (ISCED-6)') but only the current level is stored as a text string with format ISCED-#, where # is the level number. Being there, noticed that 'Field of pursued academic degree is declared as 'tokens' type: that may act counterintuitively, because writting alone a word won't be saved if you actually don't push 'enter' or click on the label that appears just under the word you're writting. This issue is important, because most students will we only writing one value (been there, bitten by that). FINAL FIX. Migrated all user data to a new, numerical-only academic level, based on ISCED. So, 'Property:Has academic degree' and 'Property:Pursues academic degree' becomes superseded by 'Property:Has ISCED level' and 'Property:Pursues ISCED level'. This approach makes trivial search academic levels by ranges. 'Template:Person', 'Template:Infobox person' and 'Form:Person' has been updated accordingly. User paremeters in profiles have been also updated, so migration is complete.
    • Related to the previous task, new ambiguities have appeared after masive replacement. The 'highest academic level' property of many students have been declared with level 3, where it should actually be 4 (with High School diploma or midlevel vocational education), the same happens with people with higher vocational education to whom short-term vocational training has been attributed. Probably a massive replacement has to be carried out for the first type, but for the second it should be reviewed if original declaration didn't include short-term vocational training.

Medium Priority

  • Revision of Knowledge Domains to fix inconsistences: after consensus is reached an automatic conversion of previos KD should be carried out.
  • Template:Clarus and Template:infobox_clarus needs the following changes: (i) elimination of linked url (instead, context is a page, including external url linkage if required), (ii) Property changed to: Related to knowledge branch (which can be 0..9), (iii) Additional property: Related to kwoledge domain, which should be normalised if possible.
  • GlossariumBITri's contents in Spanish needs to be reviewed to ensure consistent changes as applied to the English version (revision logs: g-sheets in shared drive)
  • Fixing the broken links between Concept:GlossariumBITri (es) and Concept:GlossariumBITri (en)
  • Fixing GlossariumBITri's author names. The name in the short citation is the user name instead of either the author's name or the signature name (e.g. gB:Alfabeto).
  • Ency needs to be reviewed to ensure correct transformation into wikitext. Comparison with shared original text is required. Since we have about 4000 pages, this task has to be subdivided into smaller tasks of reviewing 400 articles, identified by their ID (adding review marks).
    • IDs 0001-0400
    • IDs 0401-0800
    • IDs 0801-1200
    • IDs 1201-1600
    • IDs 1600-2000
    • IDs 2001-2400
    • IDs 2401-2800
    • IDs 2801-3200
    • IDs 3201-3600
    • IDs 3601-3806
  • Template:Clarus needs template information
  • Template:Person needs template information
  • Template:Article needs template information
  • ✅ Perform OCR on introduction from IESC.

Low Priority

Retrieved from "https://www.glossalab.org/w/index.php?title=glossaLAB:To-Do_List&oldid=31933"
This website only uses its own cookies for technical purposes; it does not collect or transfer users' personal data without their knowledge. However, it contains links to third-party websites with third-party privacy policies, which you can accept or reject when you access them.