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

  • ✅ Authors' order within the article's infobox is alphabetical, which is INCORRECT. Author's order has an implicit meaning as regards authorship (concerning responsibility and value of their contribution). This can be a source of friction with authors who may feel not properly treated.
    • DGG: This has been fixed for all Clarus activities. Form input from 'Author(s)' field is now stored as 'p:Has_authorship_sequence' as a complete string, used to represent authors with correct links and order. 'p:Has author' remains as a non-ordered link to every author.
  • ⚠️ Person pages with profile in 2 languages do not work properly. S. User:JDíaz. The information box only shows all the information in one language. In addition, a better approach to multilingual profiles has to be decided and documented.
    • DGG: It seems tricky to resolve this with current 'Extension:Translate', as its behaviour is wildly erratic. I advise against 'e:translate' on complex semantic pages (infoboxes). It can be useful on documentation pages, though. As a possible solution, we could modify 't:infobox person' to allow a direct call to the rendering of a selected user. This should allow us to insert a user's infobox with a simple 't:Infobox person' transclusion. Users would then create as 'User:main/lang' pages as need, manually. The template could include an additional semantic property to allow for the automatic collection of existing languages and the automatic creation of interlanguage links.
  • Currently the proposal's status whenever the voice is not included in a clarus page, can only be modified between: 'Open' and 'Review request'. This makes the curation of the old proposal difficult. The other proposal status has to be made available even when the voice is not currently proposed in a clarus page. The problem is due to the mechanism stablished to only enable coordinators to change status beyond open/review request.
  • Add to the configuration of the VE the namespaces available in order to make them searchable when using the link tool. Steps: (i) Configuration: $wgVisualEditorAvailableNamespaces = [NS_MAIN => true, NS_PROJECT => true, NS_FILE => false, 3000 => true,   // Custom namespace example]. (ii) Test it. (iii) Document it in help pages.
  • The infobox of clarus pages -after having introduced some changes in March 2026- takes the coordinator name adding the NS User: what creates the link user:user:user_name which is broken.
  • In order to create the glossaLAB.edu collection we need the following collaborative effort:
    • Add an infobox with the components required
    • ✅ The coordinators of clarification activities (Joe, Isaac, Antonio and Joe) have to identify the articles to be included in the collection and which should be moved to the daft namespace. This is particularly pressing since for the time being there are many articles not worth to be searched causing confusion and degrading the quality of the platform as a whole.
      • ✅ The moving of articles to the draft NS has to be done as follows (i) the coordinators must code-editing the page, then introducing the category Attic as follows: [[category:attic]] on the top. (ii) We'll run a bot to convert all those marked pages to the draft namespace, what will enable us to easily check what moves have been done.
      • 🏃 The promotion of selected pages to the glossaLAB.edu collection will be done similarly, though the necessary information has to be provided (authors, source clarification activity, pub date, KD, rev). To ensure quality we may also use some annotation as [[category:proof-reading-required]] or the like.
  • ✅ 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.
    • 🏃 An enhanced approach should move the article to a 'proofreading' state (corrección de pruebas) or directly to publication as collection article.
    • 🏃 Whenever the proposal's content is not worth being preserved, it is better to leave it aside identified by a new status: 'Rejected'. Current status values leave the proposal in permanent circularity until it is stablished as 'Ready to publish'. However there are many drafts corresponding voices that had more than one instance and one is either ready to publish or is better than the other. The bad ones should be REJECTED. I suggest adding to the voice the ending [Rejected/Rechazado] so that this status is clear to the person who finds it.
  • 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).
    • Related to the previous task, new ambiguities have appeared after massive 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

  • Remove redundant 'p:Was created on date' on proposals; special built-in property 'p:Creation date' is preferred.
  • 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)
  • C. François' Diccionary needs to be reviewed to ensure consitency with original scanned version (in glossaLAB dive: Desarrollo Plataforma... > Diccionario CF > original_scans drive), subdivided in the following batches:
    • IDs 001-100
    • IDs 101-200
    • IDs 201-275 + Páginas introductorias.
  • Fixing collections' 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). The place to be fixed is in Template:Show simple ref sub, now an arraymap is done with the authors names taken from the titles of their corresponding person's pages. These names are separated with commas. Instead, the property should be taken (#ask) from the person's property 'Has Citation name', which may include a comma within, e.g. Burgin, M. or Salto-Alemany, F., namely the way it is commonly shown in APA style referencing. The separation between citation names should be a semicolon ';'. In order to keep it language neutral, we skip the directive that last author name should be separated by '&' in English. By the way, we should normalize the way we call the citation parameter according to internation standars, so that the metadata provided by gL is compatible with bibliographic DB intakes.
  • 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

Low Priority

Retrieved from "https://www.glossalab.org/w/index.php?title=glossaLAB:To-Do_List&oldid=39274"
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.