glossaLAB - User contributions [en]

Template:DGS Nota

2026-04-30T11:28:52Z

DGracia:

<noinclude>
<pre>
{{DGS_Nota
| {etiqueta; lo destacado, como por ejemplo, "Nota preliminar"}
| {Contenido; texto de la nota}
}}
</pre>
</noinclude><includeonly>
{| class="wikitable" style="font-size:0.9em;"
|-
!{{{1|}}}
|{{{2|}}}
|}
</includeonly>

Template:DGS Nota

2026-04-30T11:27:40Z

DGracia:

<noinclude>
<pre>
{{DGS_Nota
|Etiqueta = lo destacado, como por ejemplo, "Nota preliminar"
|Contenido = texto de la nota
}}
</pre>
</noinclude><includeonly>
{| class="wikitable" style="font-size:0.9em;"
|-
!{{{1|}}}
|{{{2|}}}
|}
</includeonly>

Template:DGS Nota

2026-04-30T11:26:32Z

DGracia:

Template:DGS Nota

2026-04-30T11:25:01Z

DGracia:

<noinclude>
<pre>
{{DGS_Nota
|Etiqueta = lo destacado, como por ejemplo, "Nota preliminar"
|Contenido = texto de la nota
}}
</pre>
</noinclude><includeonly>
{| class="wikitable"
|-
! <span style="font-size:0.9em;">{{{Etiqueta|}}}
|{{{Contenido|}}}
</span>
|}
</includeonly>

User:JDíaz

2026-04-29T16:56:55Z

DGracia: Reverted edits by DGracia (talk) to last revision by JDíaz

{{Person
|Given name=José María
|Family name=Díaz Nafría
|Sex=Masculino
|Country=España
|Institution=Universidad a Distancia de Madrid (UDIMA)
|Professional category=Profesionales científicos o intelectuales
|Highest academic degree=8
|Field of highest degree=Ingeniería de Telecomunicación
|KD of expertise=03, 05, 06, 10, 14, 53, 62, 65
|input language=ES (español)
|Picture=File:Jose-maria-diaz-nafria.png
}}
[[en:User:JDíaz/en]]
<languages/>
<translate>

(Salamanca, 1970; Doctor en Ingeniería de telecomunicación por la Universidad Politécnica de Madrid y licenciado en Filosofía por la UNED) es Profesor en la Universidad a Distancia de Madrid, donde es Director del Departamento de Ingeniería de Telecomunicación; profesor visitante de la Universidad Politécnica de Munich (Alemania) desde 2011, e Investigador de la Universidad de León (España) desde 2010.


Con anterioridad ha desempeñando diversas funciones: como investigador en la Vienna University of Technology (1996), en la Universidad Politécnica de Madrid (1997-2003) y la Universidad Estatal Península de Santa Elena, Ecuador (2014-2017); como profesor en la Universidad Alfonso X el Sabio (1997-2009). Ha sido profesor visitante e invitado en numerosas universidades de Europa y Latino América.


Es miembro del equipo de dirección del Institut für Design Science (Alemania), de la International Society of Information Studies (Austria) de la que es actualmente Presidente, del Institute for a Global Sustainable Information Society (Austria), del International Center for Information Ethics (Alemania), del BITrum-Grupo de Investigación (España) del que es presidente, así como en los equipos editoriales de varias revistas científicas. Su obra investigadora se centra en el estudio interdisciplinar y transdisciplinar de la información, la comunicación (incluida la comunicación clara), el conocimiento, los sistemas y la complejidad.
</translate>
{{DISPLAYTITLE:José María Díaz Nafría|noerror}}

[[Category:Person]]

glossaLAB:To-Do List

2026-04-29T14:52:29Z

DGracia: Warning: Person pages with profile in 2 languages

{| class="wikitable" style="width:100%;"
|-
| <span style="font-size:11px">'''Purpose & Methodology''': This page contains the list of tasks to be done, classified according to priority.
[[File:To-do-list.png|right|frameless|100x100px|link=https://www.glossalab.org/w/index.php?title=glossaLAB:To-Do_List&veaction=edit]]<span style="font-size:11px">
* 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: '''<nowiki>{{task | [ongoing, paused, cancelled, done] | [task description] | ~~~}}</nowiki>''', where <nowiki>'~~~'</nowiki> 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 ==
* {{task|done|'''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.
* {{task|warning|'''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
** {{task|done|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.}}
*** {{task|done|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: <code><nowiki>[[category:attic]]</nowiki></code> 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.}}
*** {{task|ongoing|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 <code><nowiki>[[category:proof-reading-required]]</nowiki></code> or the like.}}
* {{task|done|[[Template:Infobox proposal]] should show an alert box, noticing the existence of ''PAGENAME/Pending improvements''.}}
* {{task|done|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.|[[User:DGracia]], [[User:JDíaz]]}}
** {{task|ongoing|An '''enhanced approach''' should move the article to a 'proofreading' state (corrección de pruebas) or directly to publication as collection article.}}
** {{task | ongoing |Whenever the '''proposal'''<nowiki/>'s content is '''not worth being preserved''', it is better to leave it aside identified by a '''new status''': ''''Rejected'''<nowiki/>'. 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.| [[User:JDíaz|JDíaz]] ([[User talk:JDíaz|talk]]) 21:56, 29 March 2026 (CEST)}}
* '''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.
* [[Concept:International_Encyclopedia_of_Systems_and_Cybernetics |'''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.
* '''[[Concept:GlossariumBITri (es)|GlossariumBITri's contents in Spanish]] needs to be reviewed''' to ensure consistent changes as applied to the English version (revision logs: [https://docs.google.com/spreadsheets/d/1bizQ89ICgH6RGPcl3tZTxa-7DtajJ9oZjsODQm4HMS4/edit?usp=sharing g-sheets in shared drive])
* '''[[Concept:Diccionario de Teoría General de Sistemas y Cibernética|C. François' Diccionary]] needs to be reviewed''' to ensure consitency with original scanned version (in glossaLAB dive: Desarrollo Plataforma... > Diccionario CF > original_scans [https://drive.google.com/drive/folders/1ekH5sxJn9yo3_SRmv0MIPsjbY97yh9KX 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.
* [[Concept:International_Encyclopedia_of_Systems_and_Cybernetics |'''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
**{{task|paused|Intros available to review at [[IESC:Introduction]] and [[IESC:Introduction to the Second Edition]]. A careful inspection is due, as I have detected/fixed a faulty column jump already.|[[User:DGracia|Daniel Gracia Garallar]] ([[User talk:DGracia|talk]]) 17:20, 10 February 2026 (CET)}}

== Low Priority ==
* Make a '''list of available templates, forms''' and '''associated categories''' for the creation and curation of glossaLAB contents.
* [[Template:eq]] needs template information
* [[Template:RefToEq]] needs template information (incl. how it works for reference from another page).
* [[Template:Show simple ref sub|Template:Show simple ref]] needs template information
* [[Template:Show simple ref sub]] needs template information
* [[Template:Show other languages]] needs template information
* [[Template:Infobox arrowlink sub]] needs template information
* [[Template:Infobox glossariumBITri]] needs template information
* [[Template:Int]] needs template information
* [[Template:Show other languages]] needs template information
* [[Template:Infobox IESC]] needs template information
* [[Template:Ency term]] needs template information
* Request assessment to the '''Ethics committee''' of: Privacy policy, Disclaimers, Copyright policy and Terms of service.
* Find a solution regarding the collection and usage of '''critical personal information''' such as '''disability level'''.
* Document pages related to [[glossaLAB:Combobox translations]] objects (all pending items contain a 'TODO' substring; get a list with [https://www.glossalab.org/w/index.php?search=TODO&title=Special%3ASearch&profile=advanced&fulltext=1&ns4=1 this search link]).
[[Category:Development]]
* Program a bot capable of verifying the page content and configuring the page language accordingly.
* Fix country list combox on [[Form:Person]] (only appears available in english).
* Check usefulness of <code><nowiki>[[subproperty of::Property:located in]]</nowiki></code> constructs.

User:JDíaz

2026-04-29T11:24:42Z

DGracia:

{{Person
|Given name=José María
|Family name=Díaz Nafría
|Sex=Masculino
|Country=España
|Institution=Universidad a Distancia de Madrid (UDIMA)
|Professional category=Profesionales científicos o intelectuales
|Highest academic degree=8
|Field of highest degree=Ingeniería de Telecomunicación
|KD of expertise=03, 05, 06, 10, 14, 53, 62, 65
|input language=ES (español)
|Picture=File:Jose-maria-diaz-nafria.png
}}
[[en:User:JDíaz/en]]
test{{#translation:}}
{{FULLPAGENAME}}
<languages/>
<translate>

(Salamanca, 1970; Doctor en Ingeniería de telecomunicación por la Universidad Politécnica de Madrid y licenciado en Filosofía por la UNED) es Profesor en la Universidad a Distancia de Madrid, donde es Director del Departamento de Ingeniería de Telecomunicación; profesor visitante de la Universidad Politécnica de Munich (Alemania) desde 2011, e Investigador de la Universidad de León (España) desde 2010.


Con anterioridad ha desempeñando diversas funciones: como investigador en la Vienna University of Technology (1996), en la Universidad Politécnica de Madrid (1997-2003) y la Universidad Estatal Península de Santa Elena, Ecuador (2014-2017); como profesor en la Universidad Alfonso X el Sabio (1997-2009). Ha sido profesor visitante e invitado en numerosas universidades de Europa y Latino América.


Es miembro del equipo de dirección del Institut für Design Science (Alemania), de la International Society of Information Studies (Austria) de la que es actualmente Presidente, del Institute for a Global Sustainable Information Society (Austria), del International Center for Information Ethics (Alemania), del BITrum-Grupo de Investigación (España) del que es presidente, así como en los equipos editoriales de varias revistas científicas. Su obra investigadora se centra en el estudio interdisciplinar y transdisciplinar de la información, la comunicación (incluida la comunicación clara), el conocimiento, los sistemas y la complejidad.
</translate>
{{DISPLAYTITLE:José María Díaz Nafría|noerror}}

[[Category:Person]]

User:JDíaz

2026-04-29T11:18:03Z

DGracia: Translation debugging

{{Person
|Given name=José María
|Family name=Díaz Nafría
|Sex=Masculino
|Country=España
|Institution=Universidad a Distancia de Madrid (UDIMA)
|Professional category=Profesionales científicos o intelectuales
|Highest academic degree=8
|Field of highest degree=Ingeniería de Telecomunicación
|KD of expertise=03, 05, 06, 10, 14, 53, 62, 65
|input language=ES (español)
|Picture=File:Jose-maria-diaz-nafria.png
}}
[[en:User:JDíaz/en]]
test{{#translation:}}
<languages/>
<translate>

(Salamanca, 1970; Doctor en Ingeniería de telecomunicación por la Universidad Politécnica de Madrid y licenciado en Filosofía por la UNED) es Profesor en la Universidad a Distancia de Madrid, donde es Director del Departamento de Ingeniería de Telecomunicación; profesor visitante de la Universidad Politécnica de Munich (Alemania) desde 2011, e Investigador de la Universidad de León (España) desde 2010.


Con anterioridad ha desempeñando diversas funciones: como investigador en la Vienna University of Technology (1996), en la Universidad Politécnica de Madrid (1997-2003) y la Universidad Estatal Península de Santa Elena, Ecuador (2014-2017); como profesor en la Universidad Alfonso X el Sabio (1997-2009). Ha sido profesor visitante e invitado en numerosas universidades de Europa y Latino América.


Es miembro del equipo de dirección del Institut für Design Science (Alemania), de la International Society of Information Studies (Austria) de la que es actualmente Presidente, del Institute for a Global Sustainable Information Society (Austria), del International Center for Information Ethics (Alemania), del BITrum-Grupo de Investigación (España) del que es presidente, así como en los equipos editoriales de varias revistas científicas. Su obra investigadora se centra en el estudio interdisciplinar y transdisciplinar de la información, la comunicación (incluida la comunicación clara), el conocimiento, los sistemas y la complejidad.
</translate>
{{DISPLAYTITLE:José María Díaz Nafría|noerror}}

[[Category:Person]]

glossaLAB:To-Do List

2026-04-29T10:28:18Z

DGracia: Done: ordered Clarus articles authorship.

{| class="wikitable" style="width:100%;"
|-
| <span style="font-size:11px">'''Purpose & Methodology''': This page contains the list of tasks to be done, classified according to priority.
[[File:To-do-list.png|right|frameless|100x100px|link=https://www.glossalab.org/w/index.php?title=glossaLAB:To-Do_List&veaction=edit]]<span style="font-size:11px">
* 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: '''<nowiki>{{task | [ongoing, paused, cancelled, done] | [task description] | ~~~}}</nowiki>''', where <nowiki>'~~~'</nowiki> 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 ==
* {{task|done|'''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.<br /> 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.
* 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
** {{task|done|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.}}
*** {{task|done|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: <code><nowiki>[[category:attic]]</nowiki></code> 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.}}
*** {{task|ongoing|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 <code><nowiki>[[category:proof-reading-required]]</nowiki></code> or the like.}}
* {{task|done|[[Template:Infobox proposal]] should show an alert box, noticing the existence of ''PAGENAME/Pending improvements''.}}
* {{task|done|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.|[[User:DGracia]], [[User:JDíaz]]}}
** {{task|ongoing|An '''enhanced approach''' should move the article to a 'proofreading' state (corrección de pruebas) or directly to publication as collection article.}}
** {{task | ongoing |Whenever the '''proposal'''<nowiki/>'s content is '''not worth being preserved''', it is better to leave it aside identified by a '''new status''': ''''Rejected'''<nowiki/>'. 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.| [[User:JDíaz|JDíaz]] ([[User talk:JDíaz|talk]]) 21:56, 29 March 2026 (CEST)}}
* '''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.
* [[Concept:International_Encyclopedia_of_Systems_and_Cybernetics |'''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.
* '''[[Concept:GlossariumBITri (es)|GlossariumBITri's contents in Spanish]] needs to be reviewed''' to ensure consistent changes as applied to the English version (revision logs: [https://docs.google.com/spreadsheets/d/1bizQ89ICgH6RGPcl3tZTxa-7DtajJ9oZjsODQm4HMS4/edit?usp=sharing g-sheets in shared drive])
* '''[[Concept:Diccionario de Teoría General de Sistemas y Cibernética|C. François' Diccionary]] needs to be reviewed''' to ensure consitency with original scanned version (in glossaLAB dive: Desarrollo Plataforma... > Diccionario CF > original_scans [https://drive.google.com/drive/folders/1ekH5sxJn9yo3_SRmv0MIPsjbY97yh9KX 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.
* [[Concept:International_Encyclopedia_of_Systems_and_Cybernetics |'''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
**{{task|paused|Intros available to review at [[IESC:Introduction]] and [[IESC:Introduction to the Second Edition]]. A careful inspection is due, as I have detected/fixed a faulty column jump already.|[[User:DGracia|Daniel Gracia Garallar]] ([[User talk:DGracia|talk]]) 17:20, 10 February 2026 (CET)}}

== Low Priority ==
* Make a '''list of available templates, forms''' and '''associated categories''' for the creation and curation of glossaLAB contents.
* [[Template:eq]] needs template information
* [[Template:RefToEq]] needs template information (incl. how it works for reference from another page).
* [[Template:Show simple ref sub|Template:Show simple ref]] needs template information
* [[Template:Show simple ref sub]] needs template information
* [[Template:Show other languages]] needs template information
* [[Template:Infobox arrowlink sub]] needs template information
* [[Template:Infobox glossariumBITri]] needs template information
* [[Template:Int]] needs template information
* [[Template:Show other languages]] needs template information
* [[Template:Infobox IESC]] needs template information
* [[Template:Ency term]] needs template information
* Request assessment to the '''Ethics committee''' of: Privacy policy, Disclaimers, Copyright policy and Terms of service.
* Find a solution regarding the collection and usage of '''critical personal information''' such as '''disability level'''.
* Document pages related to [[glossaLAB:Combobox translations]] objects (all pending items contain a 'TODO' substring; get a list with [https://www.glossalab.org/w/index.php?search=TODO&title=Special%3ASearch&profile=advanced&fulltext=1&ns4=1 this search link]).
[[Category:Development]]
* Program a bot capable of verifying the page content and configuring the page language accordingly.
* Fix country list combox on [[Form:Person]] (only appears available in english).
* Check usefulness of <code><nowiki>[[subproperty of::Property:located in]]</nowiki></code> constructs.

Draft:Test

2026-04-29T10:23:16Z

DGracia:

{{Proposal
|Was created on date=2025-11-03
|Created from clarus=Draft:Elu
|Has author=Daniel Gracia Garallar (DGracia)// David Schlaffer
|Has publication status=glossaLAB:Open
}}
gh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasd

{{int:Gl-get-logged-username}}

Draft:Test

2026-04-29T10:23:02Z

DGracia:

{{Proposal
|Was created on date=2025-11-03
|Created from clarus=Draft:Elu
|Has author=David Schlaffer// Daniel Gracia Garallar (DGracia)
|Has publication status=glossaLAB:Open
}}
gh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasdgh lka jlkafdljd a ladf lkjcfad lkcfasd

{{int:Gl-get-logged-username}}

Template:Abbr

2026-04-23T15:19:17Z

DGracia:

Template:Int

2026-04-20T12:07:30Z

DGracia: Reverted edits by Thomas Holzberger (talk) to last revision by DGracia

<noinclude>Takes a MediaWiki namespace page as anonymous argument and an optional second argument 'lang', that can specify the preferred language of transcription. By default, 'lang' = 'page content language'.
<templatedata>
{
"params": {
"1": {
"label": "Page",
"description": "The MediaWiki page (namespace page) to render a message for.",
"type": "string",
"required": true,
"example": "Property:Has_written_language_code"
},
"lang": {
"label": "Language code",
"description": "Optional. The preferred language for transcription. If omitted, the page content language is used.",
"type": "string",
"required": false,
"example": "en"
}
}
}
</templatedata></noinclude><includeonly>{{#invoke:Int|renderIntMessage|{{{1}}}|lang={{#if: {{{lang|}}}|{{{lang}}}|{{PAGELANGUAGE}}}}}}</includeonly>

Template:Infobox IESC

2026-04-20T12:05:17Z

DGracia:

<includeonly>{| class="gl-infobox IESC"
|- class="gl-infobox-firstrow"
! class="gl-infobox-label" | [[Property:Belongs to collection|{{#show:Property:Belongs to collection|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs to collection}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Was_published_on_date|{{#show:Property:Was_published_on_date|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Was_published_on_date}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | {{int|vol-num|lang={{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}}}
| class="gl-infobox-value" | [[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D|''{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}'']]([[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D-5B-5BContained_in_number-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}-5D-5D|{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]])
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Has_ID|{{#show:Property:Has_ID|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::<< {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=descending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=◀
|mainlabel=-
|searchlabel=
}} {{#show:{{FULLPAGENAME}}|?Has_ID #-}} {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::>> {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=ascending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=▶
|mainlabel=-
|searchlabel=
}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Belongs_to_type|{{#show:Property:Belongs_to_type|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs_to_type}}
|}</includeonly><noinclude>
<templatedata>
{
"description": {
"en": "Displays an infobox for IESC entries, showing semantic properties such as collection, publication date, volume, ID, and type.",
"es": "Muestra una infobox para entradas IESC, mostrando propiedades semánticas como colección, fecha de publicación, volumen, ID y tipo."
},
"params": {},
"format": "block"
}
</templatedata></noinclude>

Template:Infobox IESC

2026-04-20T12:04:28Z

DGracia:

<includeonly>{| class="gl-infobox IESC"
|- class="gl-infobox-firstrow"
! class="gl-infobox-label" | [[Property:Belongs to collection|{{#show:Property:Belongs to collection|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs to collection}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Was_published_on_date|{{#show:Property:Was_published_on_date|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Was_published_on_date}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | {{int|vol-num|lang={{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}}}
| class="gl-infobox-value" | [[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D|''{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}'']]([[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D-5B-5BContained_in_number-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}-5D-5D|{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]])|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Has_ID|{{#show:Property:Has_ID|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::<< {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=descending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=◀
|mainlabel=-
|searchlabel=
}} {{#show:{{FULLPAGENAME}}|?Has_ID #-}} {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::>> {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=ascending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=▶
|mainlabel=-
|searchlabel=
}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Belongs_to_type|{{#show:Property:Belongs_to_type|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs_to_type}}
|}</includeonly><noinclude>
<templatedata>
{
"description": {
"en": "Displays an infobox for IESC entries, showing semantic properties such as collection, publication date, volume, ID, and type.",
"es": "Muestra una infobox para entradas IESC, mostrando propiedades semánticas como colección, fecha de publicación, volumen, ID y tipo."
},
"params": {},
"format": "block"
}
</templatedata></noinclude>

Template:Ency term

2026-04-20T11:34:43Z

DGracia: Reverted edits by Thomas Holzberger (talk) to last revision by DGracia

'''{{{1|}}}'''

User:DGracia/Test

2026-04-20T09:53:35Z

DGracia:

<math>2.4</math>

Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
{{eq|<math>x=1</math>|label=thisone}}
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par

Par
Par
Par

Par
31
2
31
2
31
2
31
2
31
231
2
31
2
31
2
31
2
31
231
2
31
2
31
2
31
2
31
231
2
31
2
31
2
31
2
31
231
2
31
2
31
2
31
2
31
2

Template:Infobox glossariumBITri

2026-04-17T16:26:20Z

DGracia: Reverted edits by Thomas Holzberger (talk) to last revision by DGracia

<includeonly>{| class="gl-infobox glossariumBITri"
|- class="gl-infobox-firstrow"
! class="gl-infobox-label" | [[Property:Belongs to collection|{{#show:Property:Belongs to collection|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs to collection}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Has_author|{{#show:Property:Has_author|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Has_author}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Has_curator|{{#show:Property:Has_curator|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Has_curator}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Was_published_on_date|{{#show:Property:Was_published_on_date|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Was_published_on_date}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | {{int|vol-num|lang={{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}}}
| class="gl-infobox-value" | [[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D|''{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}'']]([[Special:Ask/-5B-5BBelongs_to_collection-3A-3A{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}-5D-5D-5B-5BHas_written_language_code-3A-3A{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}-5D-5D-5B-5BContained_in_volume-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}-5D-5D-5B-5BContained_in_number-3A-3A{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}-5D-5D|{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]])
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Has_ID|{{#show:Property:Has_ID|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::<< {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=descending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=◀
|mainlabel=-
|searchlabel=
}} {{#show:{{FULLPAGENAME}}|?Has_ID #-}} {{#ask:
[[Belongs_to_collection::{{#show:{{FULLPAGENAME}}|?Belongs_to_collection#-}}]]
[[Has_written_language_code::{{#show:{{FULLPAGENAME}}|?Has_written_language_code#-}}]]
[[Contained_in_volume::{{#show:{{FULLPAGENAME}}|?Contained_in_volume#-}}]]
[[Contained_in_number::{{#show:{{FULLPAGENAME}}|?Contained_in_number#-}}]]
[[Has_ID::>> {{#show:{{FULLPAGENAME}}|?Has_ID#-}}]]
|?#-
|sort=Has_ID
|order=ascending
|limit=1
|format=plainlist
|template=Infobox arrowlink sub
|userparam=▶
|mainlabel=-
|searchlabel=
}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Belongs_to_type|{{#show:Property:Belongs_to_type|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Belongs_to_type}}
|- class="gl-infobox-row"
! class="gl-infobox-label" | [[Property:Supported_by_Knowledge_Domain|{{#show:Property:Supported_by_Knowledge_Domain|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]
| class="gl-infobox-value" | {{#show:{{FULLPAGENAME}}|?Supported_by_Knowledge_Domain}}
{{#if: {{#show:{{FULLPAGENAME}}|?Has alternative english voice}} |<tr class="gl-infobox-row">
<th class="gl-infobox-label">[[Property:Has alternative english voice|{{#show:Property:Has alternative english voice|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]</th>
<td class="gl-infobox-value">{{#show:{{FULLPAGENAME}}|?Has alternative english voice}}</td>
</tr>}}{{#if: {{#show:{{FULLPAGENAME}}|?Has alternative spanish voice}} |<tr class="gl-infobox-row">
<th class="gl-infobox-label">[[Property:Has alternative spanish voice|{{#show:Property:Has alternative spanish voice|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]</th>
<td class="gl-infobox-value">{{#show:{{FULLPAGENAME}}|?Has alternative spanish voice}}</td>
</tr>}}{{#if: {{#show:{{FULLPAGENAME}}|?Has alternative french voice}} |<tr class="gl-infobox-row">
<th class="gl-infobox-label">[[Property:Has alternative french voice|{{#show:Property:Has alternative french voice|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]</th>
<td class="gl-infobox-value">{{#show:{{FULLPAGENAME}}|?Has alternative french voice}}</td>
</tr>}}{{#if: {{#show:{{FULLPAGENAME}}|?Has alternative german voice}} |<tr class="gl-infobox-row">
<th class="gl-infobox-label">[[Property:Has alternative german voice|{{#show:Property:Has alternative german voice|?Has preferred property label|+lang={{PAGELANGUAGE}}}}]]</th>
<td class="gl-infobox-value">{{#show:{{FULLPAGENAME}}|?Has alternative german voice}}</td>
</tr>}}
|}</includeonly>

Template:Infobox arrowlink sub

2026-04-17T16:26:05Z

DGracia: Reverted edits by Thomas Holzberger (talk) to last revision by DGracia

<includeonly>[[{{{1}}}|{{{#userparam}}}]]</includeonly>

glossaLAB:Mostly Harmless Updates

2026-04-17T16:24:18Z

DGracia: Write protect main NS.

<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>
[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=Architecture
|title=Main NS is mostly read-only (talk pages use is encouraged)
|content=
* Limit <code>main</code> namespace write permission to curator users, in order to assure all the content (searchable) namespaces expose only properly curated information. Readers and occasional contributors can leverage <code>draft</code> namespace and talk pages to suggest changes and improvements.
}}

{{LogEntry
|date=2026-04-17
|status=CRITICAL
|tags=UI
|title=Pop-up previews disabled
|content=
* 'Extension:Popups' seems to be very resource hungry for our humble server; we have disabled it.
}}

{{LogEntry
|date=2026-04-13
|status=SUCCESS
|tags=UI
|title=Pop-up previews enabled
|content=
* 'Extension:Popups' has been installed and enabled. It should ease whip through link lists.
}}

{{LogEntry
|date=2026-03-26
|status=SUCCESS
|tags=UI, Codex, NS:Edu, Python, API, NLP
|title=Codex Token Integration & 'Edu:' Namespace Expansion
|content=
* Standardized the UI palette by implementing '''Codex design tokens''' (utilizing <code>--color-</code> and <code>--background-color-</code> CSS variables).
* Verified cross-theme accessibility (Light/Dark mode) for custom HTML elements.
* Experimental rollout of theme-aware styles initiated on [[glossaLAB:Mostly Harmless Updates]].
* Successfully initialized the new '''Edu:''' namespace to support educational data structures and workflows.
* Proposed a technical roadmap for '''Python / MediaWiki API''' integration:
** Focus on tokenization strategies for semantic text processing.
** Preliminary research into generating co-occurrence matrices for knowledge domain mapping.
}}

{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

glossaLAB:Mostly Harmless Updates

2026-04-17T16:15:04Z

DGracia: Extension:Popups disabled.

<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>
[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

{{LogEntry
|date=2026-04-17
|status=CRITICAL
|tags=UI
|title=Pop-up previews disabled
|content=
* 'Extension:Popups' seems to be very resource hungry for our humble server; we have disabled it.
}}

{{LogEntry
|date=2026-04-13
|status=SUCCESS
|tags=UI
|title=Pop-up previews enabled
|content=
* 'Extension:Popups' has been installed and enabled. It should ease whip through link lists.
}}

{{LogEntry
|date=2026-03-26
|status=SUCCESS
|tags=UI, Codex, NS:Edu, Python, API, NLP
|title=Codex Token Integration & 'Edu:' Namespace Expansion
|content=
* Standardized the UI palette by implementing '''Codex design tokens''' (utilizing <code>--color-</code> and <code>--background-color-</code> CSS variables).
* Verified cross-theme accessibility (Light/Dark mode) for custom HTML elements.
* Experimental rollout of theme-aware styles initiated on [[glossaLAB:Mostly Harmless Updates]].
* Successfully initialized the new '''Edu:''' namespace to support educational data structures and workflows.
* Proposed a technical roadmap for '''Python / MediaWiki API''' integration:
** Focus on tokenization strategies for semantic text processing.
** Preliminary research into generating co-occurrence matrices for knowledge domain mapping.
}}

{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

glossaLAB:Mostly Harmless Updates

2026-04-13T17:22:36Z

DGracia: Extension:Popups enabled.

<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>
[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

{{LogEntry
|date=2026-04-13
|status=SUCCESS
|tags=UI
|title=Pop-up previews enabled
|content=
* 'Extension:Popups' has been installed and enabled. It should ease whip through link lists.
}}

{{LogEntry
|date=2026-03-26
|status=SUCCESS
|tags=UI, Codex, NS:Edu, Python, API, NLP
|title=Codex Token Integration & 'Edu:' Namespace Expansion
|content=
* Standardized the UI palette by implementing '''Codex design tokens''' (utilizing <code>--color-</code> and <code>--background-color-</code> CSS variables).
* Verified cross-theme accessibility (Light/Dark mode) for custom HTML elements.
* Experimental rollout of theme-aware styles initiated on [[glossaLAB:Mostly Harmless Updates]].
* Successfully initialized the new '''Edu:''' namespace to support educational data structures and workflows.
* Proposed a technical roadmap for '''Python / MediaWiki API''' integration:
** Focus on tokenization strategies for semantic text processing.
** Preliminary research into generating co-occurrence matrices for knowledge domain mapping.
}}

{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

glossaLAB:Reject

2026-04-09T17:48:02Z

DGracia: DGracia moved page glossaLAB:Rejected to glossaLAB:Reject without leaving a redirect

An proposal status in the clarification and publishing process.

This status indicates that the proposal has been reviewed by the curator, who considers it is not worth keeping in the ongoing clarification process.

__SHOWFACTBOX__

{{#set:
| Has label = Rejected@en
| Has label = Rechazado@es
| Has symbol = 🔴
}}

Actividades de clarificación conceptual

2026-03-27T13:06:32Z

DGracia:

{{#ask: [[Proposes to clarify voice::+]] [[Clarus:+]]
|?#-=topic
|?Relates to knowledge domain ID#-=BKD
|?Depends on hosting activity=activity
|?Has coordinator=coordinator
|?Has start date=starts
|?Has end date=ends
|order=asc
|format=template
|introtemplate=TableClarusIntro
|outrotemplate=TableClarusOutro
|named args=yes
|template=TableClarusBody
}}
[[en:Conceptual Clarification Activities]]

Señal Rectangular

2026-03-26T19:29:16Z

DGracia: Fix: set clarus

{{Proposal
|Created from clarus=Métodos numéricos y transformadas
|Has author=Juan Antonio Pérez Medina
|Has publication status=glossaLAB:In review
}}
El pulso rectangular es una de las señales elementales y base para la construcción de otras más complejas, aparece habitualmente en el tratamiento de señales y [[Draft:Sistema|sistemas]]. Tiene múltiples aplicaciones en electrónica, como por ejemplo en la generación de señales de reloj, entre muchas otras. Al tener un comportamiento binario, es decir, que alterna entre dos estados distintos, se hace especialmente útil para representar condiciones o estados distintos como encendido y apagado o 1 y 0.

==Definición==
[[File:Senalrectangular.png|thumb|'''Figura 1''': Representación gráfica de la señal rectangular]]
La [[Draft:Señal|señal]] rectangular se define matemáticamente mediante la siguiente expresión:

<math>
\text{rect}\left(\frac{t}{T}\right) =
\begin{cases}
1 & , \left| t \right| < \frac{T}{2} \\
0 & , \left| t \right| > \frac{T}{2}
\end{cases}
</math>

Es una función que se caracteriza por su [[DGS:Linealidad|linealidad]] ya que la pendiente es constante en cada uno de los trozos que la componen, es continua y diferenciable para todo punto de la misma a excepción de los vértices. Es una función simétrica/par, es decir, que satisface la siguiente propiedad:

<math>
f(t) = f(-t)
</math>
==Código==

En MATLAB, podemos definirla de múltiples formas diferentes y una de ellas es la siguiente, en la que nos ceñimos a la expresión matemática con la que la hemos definido:

<syntaxhighlight lang="matlab" style="font-size:90%">
T = 5; % Anchura del rectángulo

% Definición de señal rectangular
rect = @(t) (abs(t) <= T/2);

% Creamos el vector de tiempo sobre el que vamos a trabajar
t = linspace(-T, T, 1000);

% Evaluamos la señal
rect_signal = rect(t);
</syntaxhighlight>

También, MATLAB nos ofrece la posibilidad de representar cualquier pulso rectangular con los parámetros que deseemos utilizando la siguiente función:
<syntaxhighlight lang="matlab" style="font-size:90%">
r = rectangularPulse(a,b,x)
</syntaxhighlight>
==Referencias==

* Bosch, I., Castillo, J. G., Ricós, R. M., & Domínguez, L. V. (2015). ''Señales y Sistemas: teoría y problemas''. Valencia: Universitat Politècnica de València
* MATLAB Documentation - MathWorks España. (s.f.). Recuperado el 2 de enero, 2023, de https://es.mathworks.com/help/

Señal Rectangular

2026-03-26T19:28:41Z

DGracia:

{{Proposal
|Has author=Juan Antonio Pérez Medina
|Has publication status=glossaLAB:In review
}}
El pulso rectangular es una de las señales elementales y base para la construcción de otras más complejas, aparece habitualmente en el tratamiento de señales y [[Draft:Sistema|sistemas]]. Tiene múltiples aplicaciones en electrónica, como por ejemplo en la generación de señales de reloj, entre muchas otras. Al tener un comportamiento binario, es decir, que alterna entre dos estados distintos, se hace especialmente útil para representar condiciones o estados distintos como encendido y apagado o 1 y 0.

==Definición==
[[File:Senalrectangular.png|thumb|'''Figura 1''': Representación gráfica de la señal rectangular]]
La [[Draft:Señal|señal]] rectangular se define matemáticamente mediante la siguiente expresión:

<math>
\text{rect}\left(\frac{t}{T}\right) =
\begin{cases}
1 & , \left| t \right| < \frac{T}{2} \\
0 & , \left| t \right| > \frac{T}{2}
\end{cases}
</math>

Es una función que se caracteriza por su [[DGS:Linealidad|linealidad]] ya que la pendiente es constante en cada uno de los trozos que la componen, es continua y diferenciable para todo punto de la misma a excepción de los vértices. Es una función simétrica/par, es decir, que satisface la siguiente propiedad:

<math>
f(t) = f(-t)
</math>
==Código==

En MATLAB, podemos definirla de múltiples formas diferentes y una de ellas es la siguiente, en la que nos ceñimos a la expresión matemática con la que la hemos definido:

<syntaxhighlight lang="matlab" style="font-size:90%">
T = 5; % Anchura del rectángulo

% Definición de señal rectangular
rect = @(t) (abs(t) <= T/2);

% Creamos el vector de tiempo sobre el que vamos a trabajar
t = linspace(-T, T, 1000);

% Evaluamos la señal
rect_signal = rect(t);
</syntaxhighlight>

También, MATLAB nos ofrece la posibilidad de representar cualquier pulso rectangular con los parámetros que deseemos utilizando la siguiente función:
<syntaxhighlight lang="matlab" style="font-size:90%">
r = rectangularPulse(a,b,x)
</syntaxhighlight>
==Referencias==

* Bosch, I., Castillo, J. G., Ricós, R. M., & Domínguez, L. V. (2015). ''Señales y Sistemas: teoría y problemas''. Valencia: Universitat Politècnica de València
* MATLAB Documentation - MathWorks España. (s.f.). Recuperado el 2 de enero, 2023, de https://es.mathworks.com/help/

Señal Rectangular

2026-03-26T19:25:56Z

DGracia: Fix link: Linealidad

{{Proposal}}
El pulso rectangular es una de las señales elementales y base para la construcción de otras más complejas, aparece habitualmente en el tratamiento de señales y [[Draft:Sistema|sistemas]]. Tiene múltiples aplicaciones en electrónica, como por ejemplo en la generación de señales de reloj, entre muchas otras. Al tener un comportamiento binario, es decir, que alterna entre dos estados distintos, se hace especialmente útil para representar condiciones o estados distintos como encendido y apagado o 1 y 0.

==Definición==
[[File:Senalrectangular.png|thumb|'''Figura 1''': Representación gráfica de la señal rectangular]]
La [[Draft:Señal|señal]] rectangular se define matemáticamente mediante la siguiente expresión:

<math>
\text{rect}\left(\frac{t}{T}\right) =
\begin{cases}
1 & , \left| t \right| < \frac{T}{2} \\
0 & , \left| t \right| > \frac{T}{2}
\end{cases}
</math>

Es una función que se caracteriza por su [[DGS:Linealidad|linealidad]] ya que la pendiente es constante en cada uno de los trozos que la componen, es continua y diferenciable para todo punto de la misma a excepción de los vértices. Es una función simétrica/par, es decir, que satisface la siguiente propiedad:

<math>
f(t) = f(-t)
</math>
==Código==

En MATLAB, podemos definirla de múltiples formas diferentes y una de ellas es la siguiente, en la que nos ceñimos a la expresión matemática con la que la hemos definido:

<syntaxhighlight lang="matlab" style="font-size:90%">
T = 5; % Anchura del rectángulo

% Definición de señal rectangular
rect = @(t) (abs(t) <= T/2);

% Creamos el vector de tiempo sobre el que vamos a trabajar
t = linspace(-T, T, 1000);

% Evaluamos la señal
rect_signal = rect(t);
</syntaxhighlight>

También, MATLAB nos ofrece la posibilidad de representar cualquier pulso rectangular con los parámetros que deseemos utilizando la siguiente función:
<syntaxhighlight lang="matlab" style="font-size:90%">
r = rectangularPulse(a,b,x)
</syntaxhighlight>
==Referencias==

* Bosch, I., Castillo, J. G., Ricós, R. M., & Domínguez, L. V. (2015). ''Señales y Sistemas: teoría y problemas''. Valencia: Universitat Politècnica de València
* MATLAB Documentation - MathWorks España. (s.f.). Recuperado el 2 de enero, 2023, de https://es.mathworks.com/help/

Señal Rectangular

2026-03-26T19:24:59Z

DGracia: Fix: move to Proposal

{{Proposal}}
El pulso rectangular es una de las señales elementales y base para la construcción de otras más complejas, aparece habitualmente en el tratamiento de señales y [[Draft:Sistema|sistemas]]. Tiene múltiples aplicaciones en electrónica, como por ejemplo en la generación de señales de reloj, entre muchas otras. Al tener un comportamiento binario, es decir, que alterna entre dos estados distintos, se hace especialmente útil para representar condiciones o estados distintos como encendido y apagado o 1 y 0.

==Definición==
[[File:Senalrectangular.png|thumb|'''Figura 1''': Representación gráfica de la señal rectangular]]
La [[Draft:Señal|señal]] rectangular se define matemáticamente mediante la siguiente expresión:

<math>
\text{rect}\left(\frac{t}{T}\right) =
\begin{cases}
1 & , \left| t \right| < \frac{T}{2} \\
0 & , \left| t \right| > \frac{T}{2}
\end{cases}
</math>

Es una función que se caracteriza por su [[Linealidad|linealidad]] ya que la pendiente es constante en cada uno de los trozos que la componen, es continua y diferenciable para todo punto de la misma a excepción de los vértices. Es una función simétrica/par, es decir, que satisface la siguiente propiedad:

<math>
f(t) = f(-t)
</math>
==Código==

En MATLAB, podemos definirla de múltiples formas diferentes y una de ellas es la siguiente, en la que nos ceñimos a la expresión matemática con la que la hemos definido:

<syntaxhighlight lang="matlab" style="font-size:90%">
T = 5; % Anchura del rectángulo

% Definición de señal rectangular
rect = @(t) (abs(t) <= T/2);

% Creamos el vector de tiempo sobre el que vamos a trabajar
t = linspace(-T, T, 1000);

% Evaluamos la señal
rect_signal = rect(t);
</syntaxhighlight>

También, MATLAB nos ofrece la posibilidad de representar cualquier pulso rectangular con los parámetros que deseemos utilizando la siguiente función:
<syntaxhighlight lang="matlab" style="font-size:90%">
r = rectangularPulse(a,b,x)
</syntaxhighlight>
==Referencias==

* Bosch, I., Castillo, J. G., Ricós, R. M., & Domínguez, L. V. (2015). ''Señales y Sistemas: teoría y problemas''. Valencia: Universitat Politècnica de València
* MATLAB Documentation - MathWorks España. (s.f.). Recuperado el 2 de enero, 2023, de https://es.mathworks.com/help/

Entropía conjunta

2026-03-26T19:10:38Z

DGracia: Fix link: Shannon

{{Proposal
|Was created on date=2023-12-16
|Created from clarus=Teoría de la información
|Has author=Julio Garvía Honrado// Irene Salinero
|Has publication status=glossaLAB:Ready to publish
}}
[[Category:Proposal]]
==Definición==
Dentro del contexto de la ''teoría de la información'' (o de la teoría matemática de la comunicación, inicialmente propuesta por [[gB:Shannon, Claude Elwood (es)|C. Shannon]]), la '''entropía conjunta''' describe la incertidumbre asociada con dos o más variables aleatorias. Se trata de una medida de la cantidad promedio de información compartida entre estas variables en un sistema, es decir, mide cuánta información promedio se necesita para describir conjuntamente las dos variables aleatorias.<ref name=":0" />

Dadas dos variables aleatorias discretas <math>X</math> e <math>Y</math> de rango discreto y finito <math display="inline">X=\{x_1, x_2 ... x_n\}</math> e <math display="inline">Y=\{y_1, y_2 ... y_m\}</math> con funciones de probabilidad <math>p_x(x) = P(X=x)</math> y <math>p_y(y) = P(Y=y)</math>, se define la '''entropía conjunta''' de <math>X</math> e <math>Y</math> como la entropía de la variable aleatoria bidimensional <math>(X, Y)</math>, con rango discreto y finito <math>X \times Y = \{ f(x_i, y_i): x_i \in X; y_i \in Y\} </math> y función de probabilidad <math>p(x,y) = P(X=x, Y=y)</math><ref name=":0">López-García, C.; Fernández-Veiga, M. (2013). ''Teoría de la información y codificación.'' Santiago de Compostela: Andavira. </ref>.

{{eq|<math>H(X,Y) = \sum_{i=1}^n \sum_{j=1}^m p(x_i, y_j)\log\frac{1}{p(x_i, y_j)}</math>}}
== Relaciones con otras entropías ==

===Relación con las entropías individuales===
Se verifica, en general, que la entropía conjunta de dos variables aleatorias no puede superar a la suma de las [[Entropía o cantidad de información|entropías]] de dichas variables aleatorias consideradas por separado<ref name=":0" />.

{{eq|<math>H(X,Y) \leq H(X) + H(Y)</math>}}

Siendo condición necesaria y suficiente que las variables aleatorias <math>X</math> e <math>Y</math> sean independientes entre sí para que se cumpla que

{{eq|<math>H(X,Y) = H(X) + H(Y)</math>}}
=== Relación con la entropía condicional ===
La [[Draft:Entropía condicional|entropía condicional]] <math>H(X|Y) </math>, entendida como la incertidumbre de <math>X</math> cuando <math>Y</math> es conocida, se relaciona con la entropía conjunta mediante la siguiente expresión, conocida como ''regla de la cadena''<ref name=":0" />:

{{eq|<math>H(X,Y) = H(X) + H(Y|X)= H(Y) + H(X|Y) </math>}}

Si las variables <math>X</math> e <math>Y</math> son independientes, tenemos que <math>H(Y|X)=H(Y) </math> y <math>H(X|Y)=H(X) </math>, corroborando la igualdad citada en el teorema anterior.
==Código==
A continuación se muestra un ejemplo simple de cómo calcular la entropía conjunta en Matlab para dos variables aleatorias discretas.<ref>The MathWorks Inc. (2022).''Floating-point relative accuracy''. Natick, Massachusetts: The MathWorks Inc. Recuperado el 19/12/2023 de: [https://es.mathworks.com/help/matlab/ref/eps.html]</ref>
<syntaxhighlight lang="matlab">
% Definir dos variables aleatorias discretas
X = [1, 2, 3]; % Valores posibles para la variable X
Y = [4, 5, 6]; % Valores posibles para la variable Y

% Definir las probabilidades conjuntas P(X, Y)
P = [0.1, 0.2, 0.1; 0.2, 0.1, 0.1; 0.1, 0.1, 0.1];

% Calcular la entropía conjunta H(X, Y)
H = -sum(sum(P .* log2(P + eps))); % 'eps' se agrega para evitar el logaritmo de cero

% Mostrar los resultados
disp('Probabilidades conjuntas:');
disp(P);
disp(['Entropía conjunta H(X, Y): ', num2str(H)]);

</syntaxhighlight>
Utilizando la expresión matemática definida anteriormente, este código calcula la entropía conjunta utilizando como parámetros de entrada: (i) dos variables aleatorias discretas, <math>X</math> e <math>Y</math>, con valores posibles <math>[1, 2, 3]</math> y <math>[4, 5, 6]</math>, respectivamente, y (ii) las probabilidades conjuntas en la matriz <math>P</math>.

==Referencias ==
<references />

[[Category:GlossaLAB.edu]]
[[Category:Teoría de la información]]

glossaLAB:Mostly Harmless Updates

2026-03-26T16:30:29Z

DGracia: New entry

<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>
[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

{{LogEntry
|date=2026-03-26
|status=SUCCESS
|tags=UI, Codex, NS:Edu, Python, API, NLP
|title=Codex Token Integration & 'Edu:' Namespace Expansion
|content=
* Standardized the UI palette by implementing '''Codex design tokens''' (utilizing <code>--color-</code> and <code>--background-color-</code> CSS variables).
* Verified cross-theme accessibility (Light/Dark mode) for custom HTML elements.
* Experimental rollout of theme-aware styles initiated on [[glossaLAB:Mostly Harmless Updates]].
* Successfully initialized the new '''Edu:''' namespace to support educational data structures and workflows.
* Proposed a technical roadmap for '''Python / MediaWiki API''' integration:
** Focus on tokenization strategies for semantic text processing.
** Preliminary research into generating co-occurrence matrices for knowledge domain mapping.
}}

{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

Draft:Respuesta al impulso

2026-03-26T15:52:16Z

DGracia:

{{Proposal
|Has author=Alberto.esteban.sanchez// Irene Salinero
|Has publication status=glossaLAB:In review
}}
== Definiciones ==
La respuesta al impulso de un sistema es la salida que presenta dicho sistema cuando a la entrada se produce un pulso infinitamente corto y de amplitud infinita. Este pulso es imposible de obtener en un sistema real pero se utiliza como pulso ideal para la realización de cálculos matemáticos. Este tipo de pulso está representado por la función delta de Dirac (δ).<ref>Frwiki.(2022).''Distribución de Dirac. Introducción formal''. Consultado el 20/12/2023 en [https://es.frwiki.wiki/wiki/Distribution_de_Dirac]</ref>

=== Sistemas continuos ===
Un sistema continuo se refiere a un sistema cuyas entradas y salidas son funciones continuas en el tiempo. Cuando se habla de un sistema continuo en la definición de la delta de Dirac, se hace referencia a cómo el sistema responde o interactúa con una señal que contiene una delta de Dirac, es decir, cómo un sistema continuo responde a una entrada que contiene una delta de Dirac y la respuesta al impulso del sistema se utiliza para caracterizar esa interacción.<ref>Seoane-Pujol, I. (2023).Unidad didáctica 2:Sistemas, concepto y Presentación disponible en el aula virtual de la asignatura ''“ Métodos Numéricos y Transformadas"''. de la UDIMA. Consultado el 20/12/2023 en el Aula Virtual [https://aula.udima.es/course/view.php?id=48620]</ref>

En sistemas continuos la definición de la delta de Dirac sería la siguiente: <math>\delta (t) =
\begin{cases}
\infty, & \text{si }t=0 \\
0 & \text{si } t \neq\ 0
\end{cases}</math>
<ref>Wikipedia.(2020).''Función delta de Dirac. Introducción formal.'' Consultado el 20/12/2023 en [https://en.wikipedia.org/wiki/Dirac_delta_function?oldid=3459505]</ref><br>Teniendo en cuenta esto, la respuesta al impulso <math>h(t)</math>, es la función que determina cómo el sistema afecta al impulso de entrada, dando lugar a la función <math>y(t)</math>. Explicado de forma analítica: <math>y(t) = x(t)* h(t)</math>;

Siendo <math>x(t)</math> la entrada al sistema, <math>h(t)</math>h(t) la respuesta al impulso e <math>y(t)</math> la salida del sistema.<br>Dicha salida se consigue hallar mediante una operación de convolución entre <math>x(t)</math> y <math>h(t)</math>, definiéndose esta en sistemas continuos como:

<math>y(t)= \int_{-\infty}^{\infty} \displaystyle x(r)*h(t-r) dr</math><br>

=== '''Sistemas discretos''' ===

Un sistema discreto se refiere a un sistema en el que las variables de entrada y salida son definidas solamente en puntos discretos en el tiempo o en el espacio, solo tienen valores en momentos específicos, en lugar de ser continuas en todo el dominio. Un sistema discreto en la definición de la delta de Dirac en señales implica el uso de secuencias discretas que actúan como impulsos en puntos específicos, de manera análoga a cómo la delta de Dirac actúa como un impulso en el dominio continuo del tiempo.

En este caso la definición sería: <math>\delta (n) =
\begin{cases}
1, & \text{si }n=0 \\
0 & \text{si } n \neq\ 0
\end{cases}</math>

En el caso de sistemas discretos, la operación de convolución entre la entrada y la respuesta al impulso se define de la siguiente manera:<br><math>y[n]= \sum_{k=-\infty}^\infty\displaystyle x[n]*h[n-k] ;
</math><br>

'''Ejemplo conceptual:'''<br>Nos encontramos en una estudio de grabación, delante tenemos un medidor de sonido en forma de gráfica temporal. Nuestro impulso será el sonido que emite un globo al pincharse, se puede asemejar a un impulso de duración instantánea. Al pinchar el globo se observa en la gráfica como inicialmente se obtiene un pico de ruido seguido de varios picos más pequeños que finalmente desaparecen y vuelve a quedar la gráfica a cero. Bien, pues la respuesta al impulso sería el equivalente a cómo la sala de grabación afecta al impulso de tal forma que si conociéramos como cada punto de la sala afecta en la reflexión del sonido del impulso podríamos predecir la salida del sistema, es decir la gráfica de ruido final.<br>

== Código ==
Supongamos que la respuesta al impulso de un sistema es h(t), entonces la respuesta y(t) a una entrada x(t) se puede expresar como su convolución. Si la entrada es un impulso unitario δ(t), entonces la respuesta al impulso es simplemente h(t). Por lo tanto, la respuesta al impulso al aplicar un impulso unitario sería:

<math>
y(t)=\delta(t) * h(t) = h(t)</math>

Esto significa que la respuesta del sistema a un impulso unitario es igual a la propia respuesta al impulso del sistema. Podemos observar la cantidad de relación que tiene la respuesta al impulso con la señal impulso unitario. <ref>GlossaLAB.(2023).''Señal impulso unitario. Métodos numéricos y Transformadas.[https://www.glossalab.org/w/index.php?title=Se%C3%B1al_impulso_unitario&oldid=9171]''</ref>

Un ejemplo concreto, podríamos tener una función de respuesta al impulso

<math>

h(t)= e^(-t) * u(t)</math>

Donde u(t) es la función escalón unitario. En este caso, la respuesta al impulso al aplicar un impulso unitario sería la propia h(t)

Para resolver este ejercicio en MATLAB, primero definiremos la función de respuesta al impulso h(t) y luego convolucionaremos con el impulso unitario. Aquí está el código MATLAB correspondiente:<ref>The MathWorks Inc. (2022). ''Convolución y multiplicación polinomial.'' Massachusetts: The MathWorks Inc. Consultado el 19/12/2023 de: [https://es.mathworks.com/help/matlab/ref/conv.html]</ref>

<syntaxhighlight lang="matlab">
% Definir la función de respuesta al impulso
t = 0:0.01:5; % Definir el rango de tiempo
h = exp(-t) .* (t >= 0); % h(t) = e^(-t)u(t)

% Graficar la respuesta al impulso
figure;
subplot(2,1,1);
plot(t, h, 'LineWidth', 2);
title('Función de respuesta al impulso h(t)');
xlabel('Tiempo');
ylabel('h(t)');
grid on;

% Aplicar el impulso unitario (convolución)
delta = zeros(size(t));
delta(1) = 1;
y = conv(delta, h) * 0.01;

% Graficar la respuesta al impulso al aplicar un impulso unitario
subplot(2,1,2);
t_conv = 0:0.01:(length(y)-1)*0.01; % Rango de tiempo para la convolución
plot(t_conv, y, 'LineWidth', 2);
title('Respuesta al impulso al aplicar un impulso unitario');
xlabel('Tiempo');
ylabel('y(t)');
grid on;

</syntaxhighlight>

== Referencias ==
''
''

[[Category:Páginas con errores de matemáticas]]
[[Category:Páginas con errores de representación matemática]]

Draft:Respuesta al impulso

2026-03-26T15:52:04Z

DGracia:

{{Proposal
|Has author=Alberto.esteban.sanchez// Irene Salinero
|Has publication status=glossaLAB:Open
}}
== Definiciones ==
La respuesta al impulso de un sistema es la salida que presenta dicho sistema cuando a la entrada se produce un pulso infinitamente corto y de amplitud infinita. Este pulso es imposible de obtener en un sistema real pero se utiliza como pulso ideal para la realización de cálculos matemáticos. Este tipo de pulso está representado por la función delta de Dirac (δ).<ref>Frwiki.(2022).''Distribución de Dirac. Introducción formal''. Consultado el 20/12/2023 en [https://es.frwiki.wiki/wiki/Distribution_de_Dirac]</ref>

=== Sistemas continuos ===
Un sistema continuo se refiere a un sistema cuyas entradas y salidas son funciones continuas en el tiempo. Cuando se habla de un sistema continuo en la definición de la delta de Dirac, se hace referencia a cómo el sistema responde o interactúa con una señal que contiene una delta de Dirac, es decir, cómo un sistema continuo responde a una entrada que contiene una delta de Dirac y la respuesta al impulso del sistema se utiliza para caracterizar esa interacción.<ref>Seoane-Pujol, I. (2023).Unidad didáctica 2:Sistemas, concepto y Presentación disponible en el aula virtual de la asignatura ''“ Métodos Numéricos y Transformadas"''. de la UDIMA. Consultado el 20/12/2023 en el Aula Virtual [https://aula.udima.es/course/view.php?id=48620]</ref>

En sistemas continuos la definición de la delta de Dirac sería la siguiente: <math>\delta (t) =
\begin{cases}
\infty, & \text{si }t=0 \\
0 & \text{si } t \neq\ 0
\end{cases}</math>
<ref>Wikipedia.(2020).''Función delta de Dirac. Introducción formal.'' Consultado el 20/12/2023 en [https://en.wikipedia.org/wiki/Dirac_delta_function?oldid=3459505]</ref><br>Teniendo en cuenta esto, la respuesta al impulso <math>h(t)</math>, es la función que determina cómo el sistema afecta al impulso de entrada, dando lugar a la función <math>y(t)</math>. Explicado de forma analítica: <math>y(t) = x(t)* h(t)</math>;

Siendo <math>x(t)</math> la entrada al sistema, <math>h(t)</math>h(t) la respuesta al impulso e <math>y(t)</math> la salida del sistema.<br>Dicha salida se consigue hallar mediante una operación de convolución entre <math>x(t)</math> y <math>h(t)</math>, definiéndose esta en sistemas continuos como:

<math>y(t)= \int_{-\infty}^{\infty} \displaystyle x(r)*h(t-r) dr</math><br>

=== '''Sistemas discretos''' ===

Un sistema discreto se refiere a un sistema en el que las variables de entrada y salida son definidas solamente en puntos discretos en el tiempo o en el espacio, solo tienen valores en momentos específicos, en lugar de ser continuas en todo el dominio. Un sistema discreto en la definición de la delta de Dirac en señales implica el uso de secuencias discretas que actúan como impulsos en puntos específicos, de manera análoga a cómo la delta de Dirac actúa como un impulso en el dominio continuo del tiempo.

En este caso la definición sería: <math>\delta (n) =
\begin{cases}
1, & \text{si }n=0 \\
0 & \text{si } n \neq\ 0
\end{cases}</math>

En el caso de sistemas discretos, la operación de convolución entre la entrada y la respuesta al impulso se define de la siguiente manera:<br><math>y[n]= \sum_{k=-\infty}^\infty\displaystyle x[n]*h[n-k] ;
</math><br>

'''Ejemplo conceptual:'''<br>Nos encontramos en una estudio de grabación, delante tenemos un medidor de sonido en forma de gráfica temporal. Nuestro impulso será el sonido que emite un globo al pincharse, se puede asemejar a un impulso de duración instantánea. Al pinchar el globo se observa en la gráfica como inicialmente se obtiene un pico de ruido seguido de varios picos más pequeños que finalmente desaparecen y vuelve a quedar la gráfica a cero. Bien, pues la respuesta al impulso sería el equivalente a cómo la sala de grabación afecta al impulso de tal forma que si conociéramos como cada punto de la sala afecta en la reflexión del sonido del impulso podríamos predecir la salida del sistema, es decir la gráfica de ruido final.<br>

== Código ==
Supongamos que la respuesta al impulso de un sistema es h(t), entonces la respuesta y(t) a una entrada x(t) se puede expresar como su convolución. Si la entrada es un impulso unitario δ(t), entonces la respuesta al impulso es simplemente h(t). Por lo tanto, la respuesta al impulso al aplicar un impulso unitario sería:

<math>
y(t)=\delta(t) * h(t) = h(t)</math>

Esto significa que la respuesta del sistema a un impulso unitario es igual a la propia respuesta al impulso del sistema. Podemos observar la cantidad de relación que tiene la respuesta al impulso con la señal impulso unitario. <ref>GlossaLAB.(2023).''Señal impulso unitario. Métodos numéricos y Transformadas.[https://www.glossalab.org/w/index.php?title=Se%C3%B1al_impulso_unitario&oldid=9171]''</ref>

Un ejemplo concreto, podríamos tener una función de respuesta al impulso

<math>

h(t)= e^(-t) * u(t)</math>

Donde u(t) es la función escalón unitario. En este caso, la respuesta al impulso al aplicar un impulso unitario sería la propia h(t)

Para resolver este ejercicio en MATLAB, primero definiremos la función de respuesta al impulso h(t) y luego convolucionaremos con el impulso unitario. Aquí está el código MATLAB correspondiente:<ref>The MathWorks Inc. (2022). ''Convolución y multiplicación polinomial.'' Massachusetts: The MathWorks Inc. Consultado el 19/12/2023 de: [https://es.mathworks.com/help/matlab/ref/conv.html]</ref>

<syntaxhighlight lang="matlab">
% Definir la función de respuesta al impulso
t = 0:0.01:5; % Definir el rango de tiempo
h = exp(-t) .* (t >= 0); % h(t) = e^(-t)u(t)

% Graficar la respuesta al impulso
figure;
subplot(2,1,1);
plot(t, h, 'LineWidth', 2);
title('Función de respuesta al impulso h(t)');
xlabel('Tiempo');
ylabel('h(t)');
grid on;

% Aplicar el impulso unitario (convolución)
delta = zeros(size(t));
delta(1) = 1;
y = conv(delta, h) * 0.01;

% Graficar la respuesta al impulso al aplicar un impulso unitario
subplot(2,1,2);
t_conv = 0:0.01:(length(y)-1)*0.01; % Rango de tiempo para la convolución
plot(t_conv, y, 'LineWidth', 2);
title('Respuesta al impulso al aplicar un impulso unitario');
xlabel('Tiempo');
ylabel('y(t)');
grid on;

</syntaxhighlight>

== Referencias ==
''
''

[[Category:Páginas con errores de matemáticas]]
[[Category:Páginas con errores de representación matemática]]

Clarus:Métodos numéricos y transformadas

2026-03-26T15:43:42Z

DGracia:

{{clarus
|Input language=glossaLAB:Es
|Relates to broad knowledge domain ID=6
|Relates to knowledge domain ID=65
|Has abstract=(Pendiente)
|Recommends reading=Señal// Transformada de Fourier// Transformada de Laplace// Función de Transferencia// Convolución// Retardo de la señal// Señal Rectangular// Señal Triangular// Señal cuadrada// Señal sinc// Señal sinusoidal// frecuencia// muestreo// Teorema de muestreo// Escalado y desplazamiento temporal// Delta de Dirac// Transformada Z
|Proposes to clarify voice=Ancho de banda// Potencia// Linealidad// Propiedades de las transformadas// Señal impulso unitario// Respuesta al impulso// Goertzel (algoritmo)// Energía// Filtro ideal
|Belongs to collection=glossaLAB.edu
|Has coordinator=Isaac Seoane (User:Isaac Seoane)
|Depends on hosting activity=Métodos Numéricos y Transformadas
|Has start date=2024-03-01
|Has end date=2024-06-01
}}
[[Category:Clarus]]

Form:Clarus

2026-03-26T15:42:12Z

DGracia: Li

<noinclude>
{{int:gl-form-clarus-desc}}

{{#forminput:form=Clarus}}

</noinclude><includeonly>
<div id="wikiPreview" style="clear:both; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|clarus}}}
{{int:gl-mandatory-note}}
{| class="formtable"

| {{int:gl-form-language}}
| {{{field|Input language
| input type=combobox
| mandatory
| values=glossaLAB:En,glossaLAB:Es
| mapping template=Mapping code to lang
| existing values only
}}}

|-
!colspan="2" style="vertical-align: bottom; border-bottom-style: solid; height: 3em;"| {{int:gl-KD-involved}}{{#info:{{int:gl-tooltip-KDs}}}}

|-
! {{int:gl-base-kd}}*
| {{{field|Relates to broad knowledge domain ID
| input type=combobox
| mandatory
| values=0,1,2,3,5,6,7,8,9
| mapping template=Mapping KD to short label
| existing values only

}}}

|-
! {{int:gl-narrow-kd}}*
| {{{field|Relates to knowledge domain ID
| input type=tokens
| values from query=((Is knowledge domain definition::1)) ((Is child of::+))
| mapping template=Mapping KD to short label
| existing values only

}}}

|-
! {{int:gl-non-standard-kd}}
| {{{field|Relates to non-standard knowledge domain
| input type=tokens
| delimiter=//
| rows=1

}}}

|-
!colspan="2" style="vertical-align: bottom; border-bottom-style: solid; height: 3em;"| {{int:gl-concept-network}}

|-
! {{int:gl-form-clarus-introduction}}*
| {{{field|Has abstract
| mandatory
| input type=textarea
| rows=8
| placeholder={{int:gl-form-clarus-intro-placeholder}}
}}}

|-
! {{int:gl-form-clarus-recommends-reading}}*
| {{{field|Recommends reading
| mandatory
| input type=tokens
| delimiter=//
| values from content namespaces
}}}

|-
! {{int:gl-form-clarus-propose-to-clarify}}*
| {{{field|Proposes to clarify voice
| input type=tokens
| delimiter=//
| values from namespace=Draft 
}}}

|-
!colspan="2" style="vertical-align: bottom; border-bottom-style: solid; height: 3em;"| {{int:gl-coordination}}

|-
! {{int:gl-form-clarus-collection}}*
| {{{field|Belongs to collection
| mandatory
| input type=combobox
| values=glossaLAB.edu,glossaLAB.sci
| default=glossaLAB.edu
| existing values only
}}}

|-
! {{int:gl-form-clarus-coordinator}}*
| {{{field|Has coordinator
| mandatory
| input type=tokens
| delimiter=//
| values from query=((Defines a gL user profile::1)) ((~@*))
| existing values only
}}}

|-
! {{int:gl-form-clarus-hosting-activity}}*
| {{{field|Depends on hosting activity
| mandatory
| input type=text
}}}


|-
!colspan="2" style="vertical-align: bottom; border-bottom-style: solid; height: 3em;"| {{int:gl-dates}}

|-
! {{int:gl-form-clarus-start-date}}*
| {{{field|Has start date
| mandatory
| input type=datepicker
}}}

|-
! {{int:gl-form-clarus-end-date}}*
| {{{field|Has end date
| mandatory
| input type=datepicker
}}}
|}
{{{standard input|save}}}

{{{end template}}}
</includeonly>

Draft:Draft:Modulación de saltos de frecuencia (FSK)

2026-03-26T12:28:51Z

DGracia: DGracia moved page Draft:Draft:Modulación de saltos de frecuencia (FSK) to Draft:Modulación de saltos de frecuencia (FSK): Text replacement - "Draft:" to ""

#REDIRECT [[Draft:Modulación de saltos de frecuencia (FSK)]]

Draft:Modulación de saltos de frecuencia (FSK)

2026-03-26T12:28:51Z

DGracia: DGracia moved page Draft:Draft:Modulación de saltos de frecuencia (FSK) to Draft:Modulación de saltos de frecuencia (FSK): Text replacement - "Draft:" to ""

{{Proposal}}
==Definición==
La modulación de saltos de frecuencia (frequency-shift keying, FSK) es un tipo de modulación paso banda. En estas modulaciones, la señal de información se convierte a una forma de onda senoidal. Esta señal posee tres características que se pueden emplear para distinguirlas de otras señales: amplitud, frecuencia y fase. De este modo, las modulaciones paso banda se pueden definir como el proceso mediante el cual uno de estos elementos, o más de uno, de una señal portadora de radiofrecuencia varían según la información a transmitir <ref>Sklar, B., Harris, F. (2021). ''Digital Communications''. Pearson Education, 4.2.§. Digital bandpass modulation techniques.</ref>.

La forma general de una portadora es:

<math>s(t) = A(t) \ \cos(\theta (t))</math>,

donde ''A(t)'' es la amplitud variante en el tiempo y <math>\theta (t)</math> es el desfase en el tiempo. Esta última función se puede escribir como sigue:

<math>\theta (t) = \omega_0 t + \phi (t)</math>

De este modo, la señal portadora se puede expresar como:

<math>s(t) = A(t) \ \cos[\omega_0 t + \phi (t)]</math>,

donde <math>\omega_0</math> es la frecuencia de la portadora y <math>\phi(t)</math> es la fase.

La expresión analítica para una modulación FSK es la siguiente:

<math>s_i(t) = \sqrt{\dfrac{2E}{T}} \cos(\omega_i + \phi)</math>

con <math>0 \leq t \leq T</math> e <math>i = 1, ..., M</math>. El término de frecuencia <math>\omega_i</math> toma valores discretos y el término de fase <math>\phi</math> será una constante arbitraria. El parámetro ''E'' es la energía de símbolo y ''T'' es la duración de símbolo.

En este tipo de modulación, el parámetro que nos importa se caracteriza porque varía la señal portadora con respecto la información que se va a transmitir siendo ésta digital, es la frecuencia. Como es binario solo será posible dos valores el 0 y 1 asignando a cada uno una frecuencia distinta respectivamente. Es importante notar que a cambio de variar la frecuencia, la amplitud de la señal será constante.

Vamos a ver en la siguiente imagen una señal FSK:

[[File:Señal fsk.PNG|marco|centro]]

Como podemos ver en la imagen, aparte de lo mencionado anteriormente, vemos que el ruido apenas afecta a las señales FSK debido a no tenerse en cuenta las variaciones de amplitud de la señal, ya que como hemos visto antes dependen de la variación de la frecuencia.

Otra característica es el ancho de banda, siendo esta igual a la tasa de baudios de la señal, añadiendo la diferencia de las dos frecuencias usadas en la modulación. Como podemos ver en la siguiente expresión las frecuencias serían f1 y f2 siendo la inferior y superior respectivamente

BW = (f 2 - f 1) + N baudios

El principal pero de las señales FSK es que utilizan un mayor ancho de banda que una ASK teniendo la misma tasa de bits. El ancho de banda dependerá de la diferencia de la expresión anterior de las dos frecuencias que hemos usado en la modulación es decir las frecuencias portadoras.

Analizando la expresión se puede ver que interesa que la diferencia entre estas frecuencias sea pequeña, siendo un objetivo complicado de conseguir.

En la figura vamos a ver la forma gráfica el ancho de banda de una señal FSK:

[[File:Ancho banda fsk.PNG|marco|centro]]

<ref>Santos 2014 - Sistemas_telemáticos (pp_41-91).pdfSantos 2014 - Sistemas_telemáticos (pp_41-91)</ref>

==Referencias==
<references />

Draft:Draft:Modulación de saltos de fase (PSK)

2026-03-26T12:28:50Z

DGracia: DGracia moved page Draft:Draft:Modulación de saltos de fase (PSK) to Draft:Modulación de saltos de fase (PSK): Text replacement - "Draft:" to ""

#REDIRECT [[Draft:Modulación de saltos de fase (PSK)]]

Draft:Modulación de saltos de fase (PSK)

2026-03-26T12:28:49Z

DGracia: DGracia moved page Draft:Draft:Modulación de saltos de fase (PSK) to Draft:Modulación de saltos de fase (PSK): Text replacement - "Draft:" to ""

{{Proposal}}
==Definición==
La '''modulación de saltos de fase''' o de '''desplazamientos de fase''' (''phase-shift keying'', PSK) es un tipo de [[Draft:Modulación#Modulaciones de impulsos no codificados|modulación de impulsos codificados]] de tipo paso banda, a las que nos hemos referido de forma genérica en el artículo de [[Draft:modulación]]. En estas modulaciones, la señal de información modula una portadora sinusoidal, variando en este caso la fase de dicha portadora.<ref>Sklar, B., Harris, F. (2021). ''Digital Communications''. Pearson Education, 4.2.§. Digital bandpass modulation techniques.</ref>

Si la forma genérica de la portadora la expresamos como:

<math>s(t) = A(t) \ \cos[\omega_0 t + \phi (t)]</math>,

donde <math>\omega_0</math> es la frecuencia de la portadora y <math>\phi(t)</math> es la fase, la expresión analítica para una modulación PSK será:

<math>s_j(t) = \sqrt{\dfrac{2E}{T}} \cdot \cos[\omega_0 t+\phi_i(t)]</math>

con <math>0 \leq t \leq T</math> e <math>i = 1, ..., M</math>. El término de la fase <math>\phi_i(t)</math> toma valores discretos dados normalmente por:

<math>\phi_i(t) = \dfrac{2 \pi i}{M} , i = 1, ..., M</math>

Así pues, el parámetro que varía según la señal a transmitir es la fase, mientras que la amplitud y la frecuencia se mantienen constantes. El parámetro ''E'' es la energía de símbolo y ''T'' es la duración de símbolo.

=== <u>BPSK:</u> ===
En el caso particular de las modulaciones BPSK, la modulación se realizará variando la forma de onda <math>s_i(t)</math> a uno de los dos estados, 0 ó <math>\pi</math>.

Vamos a ver la representación de la señal PSK. Donde esta señal también se la puede llamar como 2-PSK , BPSK

[[File:Señal psk.PNG|marco|centro]]

En esta modulación cada unidad de señal (baudio) está representado por un solo bit, siendo la tasa de bits es igual a la tasa de baudios.
Esta modulación permite que se tenga pequeñas alteraciones de la fase pudiendo ser detectables en el receptor, es decir que en la práctica es sencillo utilizar más de dos fases. Esto permite que se puedan hacer otras técnicas de modulación, basado en PSK como puede ser 4 PSK, donde en este caso se utilizarían 4 fases en vez de dos para representar la información que queremos transmitir.

=== <u>4-PSK:</u> ===
El uso de las cuatro fases, nos permite usar valores de fases que sean arbitrarios , pero con la condición que la diferencia entre fases debe ser de 90 grados. Como tenemos cuatro fases necesitaremos 2 bits por valor para representar los cuatro valores distintos de fase, un ejemplo posible de esta asignación de valores puede ser el siguiente ejemplo.

*Fase-Bits
*0º-00
*90º-01
*180º-10
*270º-11

Vamos a ver un representación de 4-PSK:

[[File:Señal 4 psk.PNG|marco|centro]]

Podemos ver que la tasa de bits es el doble de la tasa de baudios. Como hemos visto estos valores pueden ser arbitrarios , teniendo en cuenta esto , ahí un tipo de PSK muy utilizado que es QPSK.

=== <u>QPSK:</u> ===
[[File:QPSK Gray Coded.svg.png|thumb|209x209px|constelación para QPSK.]]
''Quadrature Phase-Shift Keying''<ref>colaboradores de Wikipedia. (2025, 21 enero). ''Modulación por desplazamiento de fase''. Wikipedia, la Enciclopedia Libre. <nowiki>https://es.wikipedia.org/wiki/Modulaci%C3%B3n_por_desplazamiento_de_fase#QPSK_(Quadrature_Phase-Shift_Keying)</nowiki></ref>. En este tipo de PSK, los valores de fase asignados serían 45º, 135º, 225º y 315º. La asignación de bits a cada símbolo de la constelación se realiza mediante código Gray, lo que ayuda a reducir el número de bit erróneos.

En esta variante de 4-PSK, para un ancho de banda determinado, se transmite el doble de velocidad de datos en comparación con BPSK. Sin embargo, tanto los transmisores como los receptores son más complicados, pero con los avances de hoy día su coste es bastante asequible.

Cada símbolo puede describirse mediante la siguiente ecuación matemática:

<math>s_n(t) = \sqrt{\frac{2E_s}{T_s}} \cos \left ( 2 \pi f_c t + (2n -1) \frac{\pi}{4}\right ),\quad n \in \{1, 2, 3, 4 \} </math>

donde en función del valor de n, se obtiene cualquiera de los cuatro símbolos que genera QPSK.

=== <u>Otras modulaciones PSK:</u> ===
Tenemos otras modulaciones PSK que utiliza mayor número de fases como 8 PSK que tendrían 8 valores de fases diferentes , teniendo que estar cada valor de fase separada 45 grados entre sí. Como tenemos 8 valores , para representarlo en código binario , cada fase tendrá 3 bits , en consecuencia la tasa de bits se obtiene multiplicando por tres la tasa de baudios.

Finalmente el ancho de banda mínimo para las señales PSK es el mismo que para las señales ASK, es decir:
BW = N baudios

<ref>Santos 2014 - Sistemas_telemáticos (pp_41-91).pdfSantos 2014 - Sistemas_telemáticos (pp_41-91)</ref>
==Referencias==
<references />

Draft:Codificación

2026-03-26T12:27:36Z

DGracia: Fix: restore original author contents.

{{Proposal}}
{{non-free}}

{{close paraphrasing|date=May 2023|source=http://docplayer.es/10873687-Codificacion-de-la-informacion.html}}

Es un procedimiento utilizado muy frecuentemente, en el que ante una seria de señales de tipo analógico se transcriben en señales de tipo digital. De modo que de esta manera se facilita su procesamiento posterior, y también se mejoran las características físicas de la misma. Es decir, una señal analógica es muy sensible frente a interferencias, es con lleva que enviar una señal analógica por un medio, posteriormente será difícil de recuperar la señal original. Si la comparamos con una señal digital que tiene un número determinado de posibles valores. Este hecho permite que la recuperación de valores en una señal digital sea más sencilla, y por tanto se pueda utilizar para comunicaciones en largas distancias. En este procedimiento podemos destacar tres fases bien diferenciadas: Muestreo, cuantificación y codificación:[[File:Conversor A-D.png|thumbnail]]• Muestreo: Consiste en la toma de muestras de la amplitud de la señal de entrada (analógica). Un parámetro muy importante en este proceso en el número de muestras por segundo (frecuencia de muestreo).

• Cuantificación: Consiste en evaluar el valor de cada una de las muestras, de modo que se asigna uno de los posibles valores de la señal digital resultante a cada de las muestras. El proceso de cuantificación provoca el ruido de cuantificación, provocado por el recorte del número de posibles valores de la señal analógica a la señal digital.

•Codificación: Consiste en traducir los valores obtenidos en el proceso de cuantificación (ya son valores digitales) al sistema binario, mediante la utilización de una serie de códigos preestablecidos. De este modo al finalizar este procedimiento, se obtiene la deseada señal digital equivalente a la inicial analógica.

Rango dinámico

2026-03-26T11:45:52Z

DGracia: Fix link: SNR

{{Proposal
|Created from clarus=Teoría de la señal y la comunicación
|Has author=Javier Campos Andreu//JDíaz
|Has publication status=glossaLAB:Ready to publish
}}
== Definiciones ==
Se demomina '''rango dinámico''' o '''[[Draft:Margen dinámico|margen dinámico]]''' a la relación entre los valores máximo y mínimo que puede adoptar una determinada cantidad, medida ya sea como relación en unidades naturales, decibélicas o logarítmicas de base dos, o bien como diferencia entre el valor máximo y el mínimo. Se emplea especialmente en el ámbito de teoría de la [[Draft:señal]], y en particular al refererirnos a señales de [[Draft:señal de audio|sonido]] y [[Draft:señal de vídeo|vídeo]] (en el artículo de [[Draft:señal de audio]] nos hemos referido a los márgenes dinámicos típicos en sistemas de audio).

Si hablamos de una señal en fuente o destino, su [[Draft:Margen dinámico|margen dinámico]] es referido generalmente al nivel de [[Draft:ruido]] de fondo, ya que por debajo las señales pierden su utilidad. Lo más normal es referir el margen dinámico como la relación decibélica entre el nivel de pico de la señal y el nivel de ruido de fondo, pero a veces se usa también para referir el nivel de la señal, en cuyo caso sería indistinguible de la [[Draft:Relación_señal_a_ruido|relación señal a ruido]]. Para evitar la confusión es común añadir una clarificación a la medida del margen dinámico, como "60 dB (ref.nivel de pico)".

Cuando hablamos de '''sistemas''' el margen dinámico se refiere a la diferencia decibélica entre el nivel mínimo de entrada necesario para causar un efecto en el sistema (o el nivel mínimo para que éste se encuentra en una situación de funcionamiento adecuado, por ejemplo, porque su respuesta es suficientemente lineal) y el nivel de entrada que sobrecarga el sistema y se produce distorsión<ref name="Tomasi"/>. Es decir, se trata del rango de potencia de entrada en el que el sistema es útil.

Un sentido similar al anterior es el empleado en [[Draft:Conversor Analógico / Digital|'''conversores Analógico / Digitales''']], en los que se consideran los umbrales de saturación o sobrecarga inferior y superior, ya que una vez revasados por la señal de entrada se causaría distorsión. Sin embargo, aquí el ''rango dinámico'' se define más bien como la diferencia entre el valor máximo y mínimo de la señal de entrada <math>x(n)</math>: <math>RD=x_{max}-x_{min}</math>. Si hablamos de una cuantificación uniforme de ''L'' niveles, la resolución <math>\Delta</math> (o tamaño del escalón de cuantiﬁcación), dependerá directamente del ''RD''<ref name="Proakis"/>:
:<math>\Delta=\frac{x_{max}-x_{min}}{L}</math>
En sentido inverso, si se desea una cuantificación caracterizada por una resolución de <math>\Delta</math> (o menor), el margen dinámico establece el número de niveles mínimo requerido:
:<math>L_{min}=\frac{x_{max}-x_{min}}{\Delta}</math>
Y en consecuencia, el mínimo número de bits requeridos vendrá determinado por:
:<math>b=\lceil \log_2(L_{min}) \rceil \;\text{con}\;b\in\mathbb{Z}</math>
Por tanto, el número de bits necesarios para la conversión digital dependerá del márgen dinámico del conversor y de la resolución objetivo. Aquí se ha considerado (en consistencia con lo referido en el artículo de [[Draft:Conversor Analógico / Digital|conversión analógico / digital]]) que los valores máximo y mínimo de la señal de entrada no coinciden con los de la señal de salida (tras la reconstrucción). En caso de que si coincidieran, y que el RD se refiriese a la diferencia entre al valor máximo y mínimo de la señal a la salida, las relaciones anteriores serían un poco diferentes al haber ''L''-1 intervalos <math>\Delta</math> entre ambos extremos, en lugar de ''L''<ref name="Proakis"/>.

==Referencias==
<references>
<ref name="Tomasi">
Tomasi, W. (1996). Sistemas de comunicaciones electrónicas. México: Prentice-Hall Hispanoamericana.p134.
</ref>
<ref name="Proakis">
Proakis, J.G., Manolakis, D.G. (2007). Tratamiento digital de señales. Madrid: Pearson Educación, p.31
</ref>
</references>
==Palabras Clave==
[[Draft:Cuantificación]], [[Draft:Conversor Analógico / Digital]], [[Draft:Señal]]

[[Category:Migrated from old content]]

Rango dinámico

2026-03-26T11:22:11Z

DGracia: Link fix

{{Proposal
|Created from clarus=Teoría de la señal y la comunicación
|Has author=Javier Campos Andreu//JDíaz
|Has publication status=glossaLAB:Ready to publish
}}
== Definiciones ==
Se demomina '''rango dinámico''' o '''[[Draft:Margen dinámico|margen dinámico]]''' a la relación entre los valores máximo y mínimo que puede adoptar una determinada cantidad, medida ya sea como relación en unidades naturales, decibélicas o logarítmicas de base dos, o bien como diferencia entre el valor máximo y el mínimo. Se emplea especialmente en el ámbito de teoría de la [[Draft:señal]], y en particular al refererirnos a señales de [[Draft:señal de audio|sonido]] y [[Draft:señal de vídeo|vídeo]] (en el artículo de [[Draft:señal de audio]] nos hemos referido a los márgenes dinámicos típicos en sistemas de audio).

Si hablamos de una señal en fuente o destino, su [[Draft:Margen dinámico|margen dinámico]] es referido generalmente al nivel de [[Draft:ruido]] de fondo, ya que por debajo las señales pierden su utilidad. Lo más normal es referir el margen dinámico como la relación decibélica entre el nivel de pico de la señal y el nivel de ruido de fondo, pero a veces se usa también para referir el nivel de la señal, en cuyo caso sería indistinguible de la [[Draft:relación Señal a Ruido|relación señal a ruido]]. Para evitar la confusión es común añadir una clarificación a la medida del margen dinámico, como "60 dB (ref.nivel de pico)".

Cuando hablamos de '''sistemas''' el margen dinámico se refiere a la diferencia decibélica entre el nivel mínimo de entrada necesario para causar un efecto en el sistema (o el nivel mínimo para que éste se encuentra en una situación de funcionamiento adecuado, por ejemplo, porque su respuesta es suficientemente lineal) y el nivel de entrada que sobrecarga el sistema y se produce distorsión<ref name="Tomasi"/>. Es decir, se trata del rango de potencia de entrada en el que el sistema es útil.

Un sentido similar al anterior es el empleado en [[Draft:Conversor Analógico / Digital|'''conversores Analógico / Digitales''']], en los que se consideran los umbrales de saturación o sobrecarga inferior y superior, ya que una vez revasados por la señal de entrada se causaría distorsión. Sin embargo, aquí el ''rango dinámico'' se define más bien como la diferencia entre el valor máximo y mínimo de la señal de entrada <math>x(n)</math>: <math>RD=x_{max}-x_{min}</math>. Si hablamos de una cuantificación uniforme de ''L'' niveles, la resolución <math>\Delta</math> (o tamaño del escalón de cuantiﬁcación), dependerá directamente del ''RD''<ref name="Proakis"/>:
:<math>\Delta=\frac{x_{max}-x_{min}}{L}</math>
En sentido inverso, si se desea una cuantificación caracterizada por una resolución de <math>\Delta</math> (o menor), el margen dinámico establece el número de niveles mínimo requerido:
:<math>L_{min}=\frac{x_{max}-x_{min}}{\Delta}</math>
Y en consecuencia, el mínimo número de bits requeridos vendrá determinado por:
:<math>b=\lceil \log_2(L_{min}) \rceil \;\text{con}\;b\in\mathbb{Z}</math>
Por tanto, el número de bits necesarios para la conversión digital dependerá del márgen dinámico del conversor y de la resolución objetivo. Aquí se ha considerado (en consistencia con lo referido en el artículo de [[Draft:Conversor Analógico / Digital|conversión analógico / digital]]) que los valores máximo y mínimo de la señal de entrada no coinciden con los de la señal de salida (tras la reconstrucción). En caso de que si coincidieran, y que el RD se refiriese a la diferencia entre al valor máximo y mínimo de la señal a la salida, las relaciones anteriores serían un poco diferentes al haber ''L''-1 intervalos <math>\Delta</math> entre ambos extremos, en lugar de ''L''<ref name="Proakis"/>.

==Referencias==
<references>
<ref name="Tomasi">
Tomasi, W. (1996). Sistemas de comunicaciones electrónicas. México: Prentice-Hall Hispanoamericana.p134.
</ref>
<ref name="Proakis">
Proakis, J.G., Manolakis, D.G. (2007). Tratamiento digital de señales. Madrid: Pearson Educación, p.31
</ref>
</references>
==Palabras Clave==
[[Draft:Cuantificación]], [[Draft:Conversor Analógico / Digital]], [[Draft:Señal]]

[[Category:Migrated from old content]]

Module:LogEntry

2026-03-26T09:54:49Z

DGracia:

local p = {}

function p.render(frame)
local args = frame:getParent().args

-- Parameters
local date = args.date or os.date("%Y-%m-%d")
local title = args.title or "Operational Update"
local status = (args.status or "In Progress"):upper()
local tags = args.tags or "General"

-- Asterisk Fix: Prepend a newline to content so MediaWiki parses bullets correctly
local content = "\n" .. (args.content or "")

-- Status Color Mapping (Using Codex Variables)
-- Fallbacks are provided for older skins or browsers
local statusColors = {
["COMPLETED"] = "var(--color-success, #00af89)",
["SUCCESS"] = "var(--color-success, #00af89)",
["CRITICAL"] = "var(--color-destructive, #d33)",
["BUG"] = "var(--color-destructive, #d33)",
["RESEARCH"] = "var(--color-progressive, #36c)",
["IN PROGRESS"] = "var(--color-notice, #edab00)"
}
local accentColor = statusColors[status] or "var(--color-base, #202122)"

-- Build the HTML Output
local container = mw.html.create('div')
:css('font-family', '"Courier New", Courier, monospace')
-- Use interactive/subtle backgrounds for better theme integration
:css('background-color', 'var(--background-color-neutral, #f8f9fa)')
:css('color', 'var(--color-base, #202122)')
:css('border-left', '5px solid ' .. accentColor)
:css('padding', '15px')
:css('margin', '15px 0')
:css('border-radius', '0 8px 8px 0')
:css('box-shadow: 1px 2px 2px 1px color-mix(in srgb, var(--box-shadow-color-base) 40%, transparent)');

-- Header (Date & Status)
local header = container:tag('div')
:css('font-size', '0.85em')
:css('border-bottom', '1px solid var(--border-color-subtle, #c8ccd1)')
:css('margin-bottom', '10px')
:css('padding-bottom', '5px')
:css('display', 'flex')
:css('justify-content', 'space-between')

header:tag('span'):wikitext("📅 STARDATE: " .. date)
header:tag('span')
:css('color', accentColor)
:css('font-weight', 'bold')
:wikitext("[" .. status .. "]")

-- Title
container:tag('div')
:css('font-size', '1.2em')
:css('font-weight', 'bold')
-- Headings look better with slightly higher contrast
:css('color', 'var(--color-emphasized, #000)')
:css('margin-bottom', '10px')
:wikitext(title)

-- Body Content
container:tag('div')
:css('line-height', '1.5')
:wikitext(content)

-- Footer (Tags)
container:tag('div')
:css('margin-top', '15px')
:css('font-size', '0.8em')
:css('color', 'var(--color-subtle, #54595d)')
:wikitext("🏷️ TAGS: " .. tags)

-- Semantic MediaWiki Integration
if mw.smw then
mw.smw.set({
["Has log date"] = date,
["Has log status"] = status,
["Has log tag"] = tags,
["Is log entry"] = title
})
end

return tostring(container)
end

return p

Module:LogEntry

2026-03-26T09:53:18Z

DGracia:

local p = {}

function p.render(frame)
local args = frame:getParent().args

-- Parameters
local date = args.date or os.date("%Y-%m-%d")
local title = args.title or "Operational Update"
local status = (args.status or "In Progress"):upper()
local tags = args.tags or "General"

-- Asterisk Fix: Prepend a newline to content so MediaWiki parses bullets correctly
local content = "\n" .. (args.content or "")

-- Status Color Mapping (Using Codex Variables)
-- Fallbacks are provided for older skins or browsers
local statusColors = {
["COMPLETED"] = "var(--color-success, #00af89)",
["SUCCESS"] = "var(--color-success, #00af89)",
["CRITICAL"] = "var(--color-destructive, #d33)",
["BUG"] = "var(--color-destructive, #d33)",
["RESEARCH"] = "var(--color-progressive, #36c)",
["IN PROGRESS"] = "var(--color-notice, #edab00)"
}
local accentColor = statusColors[status] or "var(--color-base, #202122)"

-- Build the HTML Output
local container = mw.html.create('div')
:css('font-family', '"Courier New", Courier, monospace')
-- Use interactive/subtle backgrounds for better theme integration
:css('background-color', 'var(--background-color-neutral, #f8f9fa)')
:css('color', 'var(--color-base, #202122)')
:css('border-left', '5px solid ' .. accentColor)
:css('padding', '15px')
:css('margin', '15px 0')
:css('border-radius', '0 8px 8px 0')
:css('box-shadow: 1px 2px 2px 1px color-mix(in srgb, var(--box-shadow-color-base) 40%, transparent');

-- Header (Date & Status)
local header = container:tag('div')
:css('font-size', '0.85em')
:css('border-bottom', '1px solid var(--border-color-subtle, #c8ccd1)')
:css('margin-bottom', '10px')
:css('padding-bottom', '5px')
:css('display', 'flex')
:css('justify-content', 'space-between')

header:tag('span'):wikitext("📅 STARDATE: " .. date)
header:tag('span')
:css('color', accentColor)
:css('font-weight', 'bold')
:wikitext("[" .. status .. "]")

-- Title
container:tag('div')
:css('font-size', '1.2em')
:css('font-weight', 'bold')
-- Headings look better with slightly higher contrast
:css('color', 'var(--color-emphasized, #000)')
:css('margin-bottom', '10px')
:wikitext(title)

-- Body Content
container:tag('div')
:css('line-height', '1.5')
:wikitext(content)

-- Footer (Tags)
container:tag('div')
:css('margin-top', '15px')
:css('font-size', '0.8em')
:css('color', 'var(--color-subtle, #54595d)')
:wikitext("🏷️ TAGS: " .. tags)

-- Semantic MediaWiki Integration
if mw.smw then
mw.smw.set({
["Has log date"] = date,
["Has log status"] = status,
["Has log tag"] = tags,
["Is log entry"] = title
})
end

return tostring(container)
end

return p

Module:LogEntry

2026-03-26T09:34:34Z

DGracia:

local p = {}

function p.render(frame)
local args = frame:getParent().args

-- Parameters
local date = args.date or os.date("%Y-%m-%d")
local title = args.title or "Operational Update"
local status = (args.status or "In Progress"):upper()
local tags = args.tags or "General"

-- Asterisk Fix: Prepend a newline to content so MediaWiki parses bullets correctly
local content = "\n" .. (args.content or "")

-- Status Color Mapping (Using Codex Variables)
-- Fallbacks are provided for older skins or browsers
local statusColors = {
["COMPLETED"] = "var(--color-success, #00af89)",
["SUCCESS"] = "var(--color-success, #00af89)",
["CRITICAL"] = "var(--color-destructive, #d33)",
["BUG"] = "var(--color-destructive, #d33)",
["RESEARCH"] = "var(--color-progressive, #36c)",
["IN PROGRESS"] = "var(--color-notice, #edab00)"
}
local accentColor = statusColors[status] or "var(--color-base, #202122)"

-- Build the HTML Output
local container = mw.html.create('div')
:css('font-family', '"Courier New", Courier, monospace')
-- Use interactive/subtle backgrounds for better theme integration
:css('background-color', 'var(--background-color-neutral, #f8f9fa)')
:css('color', 'var(--color-base, #202122)')
:css('border-left', '5px solid ' .. accentColor)
:css('padding', '15px')
:css('margin', '15px 0')
:css('border-radius', '0 8px 8px 0')
:css('box-shadow', 'var(--box-shadow-color-base, 0 2px 2px 0 rgba(0,0,0,0.2))')

-- Header (Date & Status)
local header = container:tag('div')
:css('font-size', '0.85em')
:css('border-bottom', '1px solid var(--border-color-subtle, #c8ccd1)')
:css('margin-bottom', '10px')
:css('padding-bottom', '5px')
:css('display', 'flex')
:css('justify-content', 'space-between')

header:tag('span'):wikitext("📅 STARDATE: " .. date)
header:tag('span')
:css('color', accentColor)
:css('font-weight', 'bold')
:wikitext("[" .. status .. "]")

-- Title
container:tag('div')
:css('font-size', '1.2em')
:css('font-weight', 'bold')
-- Headings look better with slightly higher contrast
:css('color', 'var(--color-emphasized, #000)')
:css('margin-bottom', '10px')
:wikitext(title)

-- Body Content
container:tag('div')
:css('line-height', '1.5')
:wikitext(content)

-- Footer (Tags)
container:tag('div')
:css('margin-top', '15px')
:css('font-size', '0.8em')
:css('color', 'var(--color-subtle, #54595d)')
:wikitext("🏷️ TAGS: " .. tags)

-- Semantic MediaWiki Integration
if mw.smw then
mw.smw.set({
["Has log date"] = date,
["Has log status"] = status,
["Has log tag"] = tags,
["Is log entry"] = title
})
end

return tostring(container)
end

return p

glossaLAB:Mostly Harmless Updates

2026-03-26T09:18:28Z

DGracia:

<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>
[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

glossaLAB:Mostly Harmless Updates

2026-03-26T09:11:26Z

DGracia: CSS: add Codex color codes

[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]
<div style="clear:both;
background-color: var(--background-color-neutral, #f8f9fa);
color: var(--color-base, #202122);
border: 2px solid var(--border-color-base, #a2a9b1);
padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em;
color: var(--color-destructive, #d33);
font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>




{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}

Module:LogEntry

2026-03-26T09:08:55Z

DGracia: CSS: Codex color codes

local p = {}

function p.render(frame)
local args = frame:getParent().args

-- Parameters
local date = args.date or os.date("%Y-%m-%d")
local title = args.title or "Operational Update"
local status = (args.status or "In Progress"):upper()
local tags = args.tags or "General"

-- Asterisk Fix: Prepend a newline to content so MediaWiki parses bullets correctly
local content = "\n" .. (args.content or "")

-- Status Color Mapping (Using Codex Variables)
-- Fallbacks are provided for older skins or browsers
local statusColors = {
["COMPLETED"] = "var(--color-success, #00af89)",
["SUCCESS"] = "var(--color-success, #00af89)",
["CRITICAL"] = "var(--color-destructive, #d33)",
["BUG"] = "var(--color-destructive, #d33)",
["RESEARCH"] = "var(--color-progressive, #36c)",
["IN PROGRESS"] = "var(--color-notice, #edab00)"
}
local accentColor = statusColors[status] or "var(--color-base, #202122)"

-- Build the HTML Output
local container = mw.html.create('div')
:css('font-family', '"Courier New", Courier, monospace')
-- Use interactive/subtle backgrounds for better theme integration
:css('background-color', 'var(--background-color-neutral, #f8f9fa)')
:css('color', 'var(--color-base, #202122)')
:css('border-left', '5px solid ' .. accentColor)
:css('padding', '15px')
:css('margin', '15px 0')
:css('border-radius', '0 8px 8px 0')
:css('box-shadow', 'var(--box-shadow-drop-medium, 0 2px 2px 0 rgba(0,0,0,0.2))')

-- Header (Date & Status)
local header = container:tag('div')
:css('font-size', '0.85em')
:css('border-bottom', '1px solid var(--border-color-subtle, #c8ccd1)')
:css('margin-bottom', '10px')
:css('padding-bottom', '5px')
:css('display', 'flex')
:css('justify-content', 'space-between')

header:tag('span'):wikitext("📅 STARDATE: " .. date)
header:tag('span')
:css('color', accentColor)
:css('font-weight', 'bold')
:wikitext("[" .. status .. "]")

-- Title
container:tag('div')
:css('font-size', '1.2em')
:css('font-weight', 'bold')
-- Headings look better with slightly higher contrast
:css('color', 'var(--color-emphasized, #000)')
:css('margin-bottom', '10px')
:wikitext(title)

-- Body Content
container:tag('div')
:css('line-height', '1.5')
:wikitext(content)

-- Footer (Tags)
container:tag('div')
:css('margin-top', '15px')
:css('font-size', '0.8em')
:css('color', 'var(--color-subtle, #54595d)')
:wikitext("🏷️ TAGS: " .. tags)

-- Semantic MediaWiki Integration
if mw.smw then
mw.smw.set({
["Has log date"] = date,
["Has log status"] = status,
["Has log tag"] = tags,
["Is log entry"] = title
})
end

return tostring(container)
end

return p

Module:LogEntry

2026-03-26T09:06:23Z

DGracia: CSS: Codex color codes

local p = {}

function p.render(frame)
local args = frame:getParent().args

-- Parameters
local date = args.date or os.date("%Y-%m-%d")
local title = args.title or "Operational Update"
local status = (args.status or "In Progress"):upper()
local tags = args.tags or "General"

-- Asterisk Fix: Prepend a newline to content so MediaWiki parses bullets correctly
local content = "\n" .. (args.content or "")

-- Status Color Mapping (Using Codex Variables)
-- Fallbacks are provided for older skins or browsers
local statusColors = {
["COMPLETED"] = "var(--color-success, #00af89)",
["SUCCESS"] = "var(--color-success, #00af89)",
["CRITICAL"] = "var(--color-destructive, #d33)",
["BUG"] = "var(--color-destructive, #d33)",
["RESEARCH"] = "var(--color-progressive, #36c)",
["IN PROGRESS"] = "var(--color-notice, #edab00)"
}
local accentColor = statusColors[status] or "var(--color-base, #202122)"

-- Build the HTML Output
local container = mw.html.create('div')
:css('font-family', '"Courier New", Courier, monospace')
-- Use interactive/subtle backgrounds for better theme integration
:css('background-color', 'var(--background-color-subtle, #f8f9fa)')
:css('color', 'var(--color-base, #202122)')
:css('border-left', '5px solid ' .. accentColor)
:css('padding', '15px')
:css('margin', '15px 0')
:css('border-radius', '0 8px 8px 0')
:css('box-shadow', 'var(--box-shadow-drop-medium, 0 2px 2px 0 rgba(0,0,0,0.2))')

-- Header (Date & Status)
local header = container:tag('div')
:css('font-size', '0.85em')
:css('border-bottom', '1px solid var(--border-color-subtle, #c8ccd1)')
:css('margin-bottom', '10px')
:css('padding-bottom', '5px')
:css('display', 'flex')
:css('justify-content', 'space-between')

header:tag('span'):wikitext("📅 STARDATE: " .. date)
header:tag('span')
:css('color', accentColor)
:css('font-weight', 'bold')
:wikitext("[" .. status .. "]")

-- Title
container:tag('div')
:css('font-size', '1.2em')
:css('font-weight', 'bold')
-- Headings look better with slightly higher contrast
:css('color', 'var(--color-emphasized, #000)')
:css('margin-bottom', '10px')
:wikitext(title)

-- Body Content
container:tag('div')
:css('line-height', '1.5')
:wikitext(content)

-- Footer (Tags)
container:tag('div')
:css('margin-top', '15px')
:css('font-size', '0.8em')
:css('color', 'var(--color-subtle, #54595d)')
:wikitext("🏷️ TAGS: " .. tags)

-- Semantic MediaWiki Integration
if mw.smw then
mw.smw.set({
["Has log date"] = date,
["Has log status"] = status,
["Has log tag"] = tags,
["Is log entry"] = title
})
end

return tostring(container)
end

return p

File:GlossaLAB fish (IA generated).jpg

2026-03-26T08:33:19Z

DGracia: DGracia uploaded a new version of File:GlossaLAB fish (IA generated).jpg

== Summary ==
GlossaLAB fish (generated with Google Gemini).

glossaLAB:Mostly Harmless Updates

2026-03-26T08:13:17Z

DGracia:

[[File:GlossaLAB_fish_(IA_generated).jpg|frameless|upright=5|center]]

<div style="clear:both; background-color: #f8f9fa; border: 2px solid #a2a9b1; padding: 1em; margin: 1em 0; border-radius: 8px; text-align: center;">
<span style="font-size: 1.5em; color: #d33; font-weight: bold; display: block; margin-bottom: 0.5em;">DON'T PANIC</span>
Here you can take a look at the incremental progress of the platform. Beware, and don't forget your towel.
</div>




{{LogEntry
|date=2026-03-25
|status=SUCCESS
|tags=Migration, Documentation, Regex, NS:Draft
|title=Initialization of 'Mostly Harmless Updates' & Namespace Refactoring
|content=
* Deployed the public-facing log at [[glossaLAB:Mostly_Harmless_Updates]] to track platform progress for the general user base.
* Optimized this internal log for technical/sensitive chronology with the intent of future external indexing (AI-ready data structures).
* Executed mass migration of legacy <code><nowiki>{{Cab...}}</nowiki></code> and <code><nowiki>{{Head...}}</nowiki></code> templates into the '''Draft''' namespace, standardizing them under the <code><nowiki>{{Proposal}}</nowiki></code> header.
* Performed a "Great Cleanup" of the '''Main''' namespace, deleting superfluous and orphaned pages.
* Applied a global string substitution: <code>=TSC</code> → <code>=Teoría de la señal y la comunicación</code> within the Draft namespace and Proposal category.
* Implemented a Regex substitution to repair internal link structures by prepending the Draft prefix: <code><nowiki>[[([^:\]\|]+)(\|[^\]]*)?\]\]</nowiki></code> → <code><nowiki>[[Draft:$1$2]]</nowiki></code>.
}}

{{LogEntry
|date=2026-03-24
|status=SUCCESS
|tags=AI entry, Migration, Clarus, Proposals
|title=Old Clarification Activities Migration
|content=
* Completed processing of content related to clarification activities previously referenced with tags.
* Relocated historical comments to <code><nowiki>{{TALKPAGENAME}}/Suggested improvements</nowiki></code> to declutter the Main namespace.
* Managed three major article collisions: "Codificación convolucional," "Dear Past Life," and "Señal discreta en el tiempo".
* Simplified the <code>Proposal</code> template by automating the parent activity and creation date parameters.
}}

{{LogEntry
|date=2026-03-13
|status=SUCCESS
|tags=AI entry, DGS, Redirects, Scripts, XML
|title=DGS Redirect Overhaul & XML Import
|content=
* Developed and executed a Python script to convert DGS #REDIRECT pages into full pages utilizing the <code><nowiki>{{Redir DGS}}</nowiki></code> template.
* Generated and imported a master XML file to ensure all DGS terms are searchable and properly indexed.
* Standardized term IDs by alphabetical order for the initial DGS rollout.
}}

{{LogEntry
|date=2026-02-23
|status=SUCCESS
|tags=AI entry, DGS, UI, Search
|title=DGS First Online Version Deployment
|content=
* Deployed the first live version of the "Diccionario de Teoría General de Sistemas y Cibernética" (DGS).
* Implemented "Sentence case" normalization for all DGS titles to improve search engine success.
* Established DGS Bibliography with anchors for individual author surnames.
}}

{{LogEntry
|date=2026-02-03
|status=SUCCESS
|tags=AI entry, Reviews, Namespaces, Authors
|title=Author Response Architecture
|content=
* Implemented a system for authors to respond to reviews using the <code>Rev talk</code> namespace.
* Responses are now stored as subpages (e.g., <code>Rev talk:Ind 0000021/Author response</code>) to keep them linked to the review while remaining editable.
* Configured the <code>Proposal</code> infobox to automatically aggregate these responses for curator viewing.
}}

{{LogEntry
|date=2026-01-20
|status=SUCCESS
|tags=AI entry, Reviews, UI, Gadgets
|title=Suggested Improvements Workflow
|content=
* Launched the "Suggested Improvements" mechanism to separate editorial feedback from article content.
* New feedback is stored in <code>Talk Draft:PAGENAME/Suggested improvements</code> and transcluded into the <code>Proposal</code> template via the <code>Comments</code> template.
* Updated <code>MediaWiki:Gadget-ReviewTool.json</code> to include localized UI strings for the review bar.
}}

{{LogEntry
|date=2026-01-14
|status=SUCCESS
|tags=AI entry, SMW, Clarus, Proposals
|title=Clarus Property Refactoring
|content=
* Renamed <code>Belongs to clarus</code> to <code>Created from clarus</code> across 82 pages to better reflect origin tracking.
* Updated <code>Proposal</code> infobox to dynamically list all clarification activities proposing a voice via <code>Proposes to clarify...</code> property.
* Fixed a syntax error in <code>Proposal</code> infobox involving incorrect <code>{{!}}</code> and <code><nowiki>}}</nowiki></code> closures.
}}

{{LogEntry
|date=2025-12-22
|status=SUCCESS
|tags=AI entry, CSS, UI, Printing
|title=Print View Optimization
|content=
* Modified <code>MediaWiki:Common.css</code> to hide large SVG logos in print mode to prevent scaling errors.
* Adjusted epigraph styles to use single lines instead of double lines for better professional appearance.
}}

{{LogEntry
|date=2025-12-04
|status=SUCCESS
|tags=AI entry, Editorial, Rev, PageForms
|title=Automated Review Page Generation
|content=
* Added a "sysop-only" link to <code>Proposal</code> pages for articles marked 'In review' to trigger review forms.
* Configured forms to automatically generate pages in the <code>Rev:</code> namespace using a monotonic ascending counter (e.g., <code>Rev:Individual 123456</code>).
}}

{{LogEntry
|date=2025-11-26
|status=SUCCESS
|tags=AI entry, Extensions, Git, Maintenance
|title=UserMerge Extension Synchronization
|content=
* Resolved incompatibility between <code>UserMerge</code> and MW 1.43 by switching to the <code>REL1_43</code> stable branch in the Git repository.
* Adopted the REL1_43 LTS branch as the standard for all core extensions to ensure long-term stability.
}}

{{LogEntry
|date=2025-11-19
|status=SUCCESS
|tags=AI entry, Lua, I18n, SMW, Scripts
|title=Lua Language Retrieval Fix
|content=
* Replaced native Lua language retrieval (which queried the DB directly and ignored forced values) with Semantic queries to ensure i18n consistency.
* Converted URL-type properties to Text-type temporarily to eliminate validation warnings during mass data exports.
* Updated <code>approvePageList.php</code> script to handle error checking during batch processing of certificates.
}}

{{LogEntry
|date=2025-10-15
|status=SUCCESS
|tags=AI entry, Mobile, Minerva, Hooks
|title=Mobile Frontend UX Enhancement
|content=
* Integrated a PHP hook in <code>LocalSettings.php</code> for the Minerva theme to add a direct "Edit Profile" link to the mobile sidebar.
* The hook dynamically retrieves the current username and formats the <code>FormEdit</code> URL for the <code>Person</code> form.
}}

{{LogEntry
|date=2025-10-06
|status=SUCCESS
|tags=AI entry, PageForms, Data, I18n
|title=Global University Database Import
|content=
* Imported a curated list of ~300 international universities into <code>MediaWiki:gl-combobox-universities</code>.
* Configured <code>Form:Person</code> to use this list as an autocomplete source while maintaining a free-text fallback for new institutions.
}}

{{LogEntry
|date=2025-10-05
|status=SUCCESS
|tags=AI entry, Ontology, Forms, SMW
|title=User Profile Logic Refinement
|content=
* Implemented <code>Platform user definition = 1</code> boolean property to uniquely identify registered users in semantic searches.
* Added <code>User default language</code> capture during form submission to force consistency between the user's interface and their generated profile page.
* Activated Wikidata autocompletion for "Country" and "Institution" fields within the <code>Person</code> form.
}}

{{LogEntry
|date=2025-09-29
|status=SUCCESS
|tags=AI entry, Upgrade, Production, Maintenance
|title=Platform Synchronization
|content=
* Successfully updated production environment to '''MW 1.43.3''' and '''SMW 6.0.1'''.
* Synchronized all templates and modules between the 'beta' and 'production' environments.
* Applied a manual patch to '''PageForms''' (PF_ValuesUtils.php) to fix language-specific autocompletion from Wikibase.
}}

{{LogEntry
|date=2025-09-11
|status=SUCCESS
|tags=AI entry, Jupyter, Server, DNS
|title=JupyterHub Deployment
|content=
* Provisioned a new VPS and configured DNS for <code>jupyterhub.glossalab.org</code>.
* Installed '''The Littlest Jupyter Hub''' (TLJH) on Ubuntu 22.04.
}}

{{LogEntry
|date=2025-08-28
|status=RESEARCH
|tags=AI entry, Ontology, Person, Multilingual
|title=The 'Short Bio' Dilemma
|content=
* Removed 'short bio' from the 'person' ontology as it functions better as page content than metadata.
* Opted for transcluding language-specific subpages (/es, /en) over complex 'monolingual text' properties which Page Forms struggles to handle.
* Failed attempt to update to MW 1.43 / SMW 6.0; restored from backups.
}}

{{LogEntry
|date=2025-07-17
|status=SUCCESS
|tags=AI entry, XML, Concepts, Automation
|title=Semantic Namespace Restructuring
|content=
* Performed a mass XML export/import of the '''NS GB''' to reclassify 'Type' assignments to the '''Concept''' namespace.
* Updated timestamps and authorship in the XML to ensure MW recognized the changes as new revisions.
* Integrated '''Mendeley Developer API''' for bibliographic data retrieval.
}}

{{LogEntry
|date=2025-07-10
|status=SUCCESS
|tags=AI entry, Math, Extensions, GitHub
|title=EquationNumbering Extension Release
|content=
* Finalized the '''EquationNumbering''' extension for automatic math numbering and labeled anchors.
* Published the repository and documentation to GitHub.
* Updated license terms for the extension.
}}

{{LogEntry
|date=2025-06-12
|status=SUCCESS
|tags=AI entry, Production, Migration, Scripts
|title=The Great Production Leap
|content=
* Created <code>approvePageList.php</code> to batch-approve page lists via CLI.
* Successfully migrated gB contents, Lua modules, and templates (Article, Person, etc.) to the production server.
* Installed '''Semantic Scribunto''' in the production environment.
}}

{{LogEntry
|date=2025-05-14
|status=SUCCESS
|tags=AI entry, Ontology, SMW, UI
|title=Refining 'Article' logic & Infoboxes
|content=
* Introduced the '''specializes''' property (transitive) to track articles promoting into sections or higher abstractions.
* Resolved confusion regarding 'previous versions'; standard MW history is sufficient.
* Developed '''Module:SMWInfobox''' using <code>getQueryResult</code> to respect multilingual contexts.
* Approved the addition of 'specializes' property during the glossaLAB meeting.
}}

{{LogEntry
|date=2025-05-12
|status=RESEARCH
|tags=AI entry, PHP, Scribunto, Crypto
|title=Initialization of Extension:GlossaLAB
|content=
* Developed a custom PHP extension to support Scribunto for advanced logic.
* Implemented symmetric 'encrypt' and 'decrypt' methods using the '''OpenSSL''' library.
* Secret keys are now securely stored in <code>LocalSettings.php</code>.
* '''Limitation identified:''' Encrypted data cannot be easily transcluded via editable template parameters without manual 'subst' use.
}}

{{LogEntry
|date=2025-05-06
|status=SUCCESS
|tags=AI entry, ApprovedRevs, SMW, Security
|title=Semantic Property Synchronization
|content=
* Installed '''SemanticApprovedRevs''' to ensure SMW only recognizes properties from approved page versions.
* Documented that standard ApprovedRevs does not natively control semantic property designation.
* Implemented '''Template:Confidential_reviewer_map''' to map hash codes to real users for anonymous reviewing.
* Evaluated '''SemanticACL''' to restrict access to specific properties.
}}

{{LogEntry
|date=2025-04-25
|status=SUCCESS
|tags=AI entry, PageForms, Multilingual
|title=Multilingual Form Architecture
|content=
* Strategy: Create independent categories/forms per language referencing a single template.
* This allows localized forms where the language is linked to the category rather than the UI.
* Adopted '''Extension:TemplateData''' to facilitate metadata editing in VisualEditor.
}}

{{LogEntry
|date=2025-04-15
|status=SUCCESS
|tags=AI entry, Multilingual, I18n, Lua
|title=Internationalization Framework
|content=
* Created '''Has citation name''' property to solve citation ambiguity.
* Adopted <code><nowiki>{{int:NAME}}</nowiki></code> for message internationalization.
* Began applying i18n directly to property definitions.
* Conducted localization tests in Lua via '''Module:TemplateLabelTranslator'''.
}}

{{LogEntry
|date=2025-04-14
|status=RESEARCH
|tags=AI entry, Wikidata, Users, Security
|title=User Mapping & Wikidata Constraints
|content=
* Investigated connecting bibliographies to Wikidata via Page Forms; currently not implemented locally.
* Addressed risks in user/real name segregation and autocompletion collisions.
* Recommendation: Use usernames for data designation to ensure non-ambiguity.
}}

{{LogEntry
|date=2025-04-13
|status=CRITICAL
|tags=AI entry, Update, SMW, MW, Extensions
|title=The 5.0.0 Update Attempt
|content=
* Attempted update to '''SMW 5.0.0''' and '''MW 1.43.1'''.
* Manual updates for ApprovedRevs, cldr, and CleanChanges.
* '''Failure:''' Encountered severe configuration issues; SMW 5.0 not ready or sequence error.
* Reverted changes in Beta environment.
* Deactivated SemanticScribunto due to temporary incompatibility.
* Success: Verified Page Schemas functionality with manual fixes.
}}

{{LogEntry
|date=2025-04-08
|status=RESEARCH
|tags=AI entry, Semantic Design, SMW
|title=Refining Property Logic
|content=
* Addressed confusion between semantic design and support templates.
* '''Design Decision:''' Focus on explicit semantic properties; implicit properties (like previous versions) will be handled via queries.
* Preference for individual assignments over lists to maintain design integrity.
}}

{{LogEntry
|date=2025-04-03
|status=SUCCESS
|tags=AI entry, SMW, Excel, Images, Permalinks
|title=Data Import & Persistence Policy
|content=
* Implemented Excel import capability via '''XLSX.jl'''.
* Refined the 'review' template; removed redundant article data as references are now implicit.
* Established '''Image Policy''': Multimedia content is frozen after revision acceptance to maintain consistency between versions.
* Implemented monotonic counters for permanent links.
}}

{{LogEntry
|date=2025-04-02
|status=SUCCESS
|tags=AI entry, SMW, Ontology, Templates
|title=Ontology Initialization & FOAF Alignment
|content=
* Started development of templates described in semantic annotation design.
* Renamed 'name' and 'surname' properties to '''given name''' and '''family name''' to align with FOAF ontologies.
* Reviewed compatibility with normalized templates and external bibliography implementation.
}}