YATA issueshttps://gitlab.ethz.ch/vermeul/YATA/-/issues2022-03-07T14:32:01Zhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/33Create Development infrastructure2022-03-07T14:32:01Zvermeulswen@ethz.chCreate Development infrastructureRelated to #23.
- create docker-compose based MediaWiki
- allows to develop locally without disturbing production
- allows to switch to newer versions of MediaWiki and early detect possible backward-incompatible changesRelated to #23.
- create docker-compose based MediaWiki
- allows to develop locally without disturbing production
- allows to switch to newer versions of MediaWiki and early detect possible backward-incompatible changesInfrastructure improvementsvermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/32Error message when a new category is created with an existing hashtag2021-12-10T13:07:08Zvermeulswen@ethz.chError message when a new category is created with an existing hashtagIf I try to use an existing hashtag string for a new category, I should get a dedicated error message.If I try to use an existing hashtag string for a new category, I should get a dedicated error message.Category improvementsvermeulswen@ethz.chvermeulswen@ethz.ch2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/31Prevent accidental deletion of a categorie in use2021-12-10T12:46:44Zvermeulswen@ethz.chPrevent accidental deletion of a categorie in usethrow an exception when someone accidentally tries to delete a category which is still in use, e.g.
`{{#annotcat: del | #geometry}}`
In addition, an exception will be thrown when there is no matching category of that name/hashtag.throw an exception when someone accidentally tries to delete a category which is still in use, e.g.
`{{#annotcat: del | #geometry}}`
In addition, an exception will be thrown when there is no matching category of that name/hashtag.Category improvementsvermeulswen@ethz.chvermeulswen@ethz.ch2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/30cagetory ambiguity2021-11-30T23:36:32Zvermeulswen@ethz.chcagetory ambiguityBy default, category names can be ambiguous, their name is not unique. To exactly specify a category by its name, the `parent/child` notation must be used. By convention, `parent/child` combinations must be unique.
On the other hand, th...By default, category names can be ambiguous, their name is not unique. To exactly specify a category by its name, the `parent/child` notation must be used. By convention, `parent/child` combinations must be unique.
On the other hand, the associated hashtags to every category (e.g. `#geometry`) must always be unique.
When we assign an annotation to a category, we do not allow ambiguity, we either use the `parent/child` or the `#hashtag` notation to exactly specify the category.
Questions:
1. are the above assumptions correct?
2. should we allow ambigous categories in `annotask` queries?
3. should we allow something like `/geometry` to specify a top category in a search?Category improvementswagnerrwagnerrhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/28Query result table: specify columns to display2021-11-26T00:01:13Zvermeulswen@ethz.chQuery result table: specify columns to displayCurrently all page-wide annotations generate columns in search result tables. We would like to add a "don't include" and "include only" options (i.e. generate columns for all page-wide annotations except for specified annotations, or inc...Currently all page-wide annotations generate columns in search result tables. We would like to add a "don't include" and "include only" options (i.e. generate columns for all page-wide annotations except for specified annotations, or include only columns for specified page-wide annotations).Search improvementsvermeulswen@ethz.chvermeulswen@ethz.ch2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/27Query result table: split columns2021-11-30T23:37:19Zvermeulswen@ethz.chQuery result table: split columnsThe category column should be split into separate columns for each category (currently all search categories appear together in the first column, which makes things difficult to handle).The category column should be split into separate columns for each category (currently all search categories appear together in the first column, which makes things difficult to handle).Category improvementsvermeulswen@ethz.chvermeulswen@ethz.ch2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/24Highlighting the tagged item when linking from a search result2022-03-07T14:31:31Zvermeulswen@ethz.chHighlighting the tagged item when linking from a search resultThe annotask query generates a result table with links, including the anchor where a certain tag occurs. The tag should be highlighted.
Possible implementation: add an additional key-value to the URL and add a JavaScript which then does...The annotask query generates a result table with links, including the anchor where a certain tag occurs. The tag should be highlighted.
Possible implementation: add an additional key-value to the URL and add a JavaScript which then does the correct highlighting.
https://jira-bsse.ethz.ch/browse/SSDM-10796Search improvementsvermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/20Mispar: Enforce always https2021-03-31T15:30:05Zvermeulswen@ethz.chMispar: Enforce always httpsCurrently, mispar is not automatically switching to https – but this should be the case, as during login a password is otherwise transferred unencrypted
https://jira-bsse.ethz.ch/browse/SSDM-10752Currently, mispar is not automatically switching to https – but this should be the case, as during login a password is otherwise transferred unencrypted
https://jira-bsse.ethz.ch/browse/SSDM-10752vermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/19Mispar: error/status message when category in annotask query does not exist2021-12-10T13:50:35Zvermeulswen@ethz.chMispar: error/status message when category in annotask query does not exist* currently, a DB error message appears when a category does not exist
* instead, zero results should be shown
* if possible, show conflicting/non-existing categories and verbose output* currently, a DB error message appears when a category does not exist
* instead, zero results should be shown
* if possible, show conflicting/non-existing categories and verbose outputCategory improvementshttps://gitlab.ethz.ch/vermeul/YATA/-/issues/18Mispar: non-verbose output of annotask search2021-03-31T15:33:01Zvermeulswen@ethz.chMispar: non-verbose output of annotask searchImplement a non-verbose annotask query result as the the default.
Make the verbose output be available with an additional `[[verbose: true]]` element
https://jira-bsse.ethz.ch/browse/SSDM-10747Implement a non-verbose annotask query result as the the default.
Make the verbose output be available with an additional `[[verbose: true]]` element
https://jira-bsse.ethz.ch/browse/SSDM-10747vermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/17Mispar: Annotation search queries from outside mispar2021-11-11T12:05:58Zvermeulswen@ethz.chMispar: Annotation search queries from outside mispar(from 2021-01-19)
> We have a cooperation with a medieval Hebrew dictionary project. This cooperation requires them to initiate searches from their own system.
> These searches should be created by pressing a link on their page. The lin...(from 2021-01-19)
> We have a cooperation with a medieval Hebrew dictionary project. This cooperation requires them to initiate searches from their own system.
> These searches should be created by pressing a link on their page. The link should generate an annotation search query.
> Is this possible? Can they write a code in their system that initiates a search and displays the results in Mispar?
currently I don't know how to implement this, but in principle, it should be possible.
* the link must contain the whole query string
* it must be received and parsed by the backend
* investigate whether MediaWiki can produce ephemeral/dynamically generated pages
* investigate how the rendering needs to be done (i.e. math symbols)
* such queries cannot be cached
* possible performance issues
* possible DOS attacks?
https://jira-bsse.ethz.ch/browse/SSDM-10748https://gitlab.ethz.ch/vermeul/YATA/-/issues/15Mispar: hashtag with whitespace2021-12-09T11:29:43Zvermeulswen@ethz.chMispar: hashtag with whitespaceCreating a hashtag with a whitespace creates a database error.
Do one of the following:
- return a nice error message if whitespaces aren't allowed for some good reasons
- save the hashtag anyway
- replace whitespaces with underscores
...Creating a hashtag with a whitespace creates a database error.
Do one of the following:
- return a nice error message if whitespaces aren't allowed for some good reasons
- save the hashtag anyway
- replace whitespaces with underscores
https://jira-bsse.ethz.ch/browse/SSDM-10750User Experience improvements2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/14Combine annotations of Semantic Media Wiki with annotations in one query2019-06-24T12:33:21Zvermeulswen@ethz.chCombine annotations of Semantic Media Wiki with annotations in one queryWhat we are looking for concerning the date is that in every result table, if there is an annotation that belongs, for example, to the page:
[http://mispar.ethz.ch/wiki/ספר_החשבון_והמדות](http://mispar.ethz.ch/wiki/ספר_החשבון_והמדות)
t...What we are looking for concerning the date is that in every result table, if there is an annotation that belongs, for example, to the page:
[http://mispar.ethz.ch/wiki/ספר_החשבון_והמדות](http://mispar.ethz.ch/wiki/ספר_החשבון_והמדות)
this annotation will be marked as: Constantinople, 1450-1526 – which is the time and place in which the original text of this specific page was composed.https://gitlab.ethz.ch/vermeul/YATA/-/issues/13Display math formulas in result tables2021-01-20T08:18:22Zvermeulswen@ethz.chDisplay math formulas in result tablesIn MediaWiki, a tag with the structure {{ #functionname: param1 | param2 | param3 }}
is called a parser function (see https://www.mediawiki.org/wiki/Manual:Parser_functions)
When MediaWiki displays a page containing such a parser functi...In MediaWiki, a tag with the structure {{ #functionname: param1 | param2 | param3 }}
is called a parser function (see https://www.mediawiki.org/wiki/Manual:Parser_functions)
When MediaWiki displays a page containing such a parser function, it finds these parser functions and executes them.
These parser functions usually contain text, MediaWiki markup language and HTML. The MediaWiki markup language is
translated into HTML elements beforehand. For example, something like
```
{|
| Orange || Apple || more
|-
| Bread || Pie || more
|-
| Butter || Ice cream || and more
|}
```
Is translated into HTML:
```
<table><tbody>
<tr><td>Orange</td><td>Apple</td><td>more</td></tr>
<tr><td>Bread</td><td>Pie</td><td>more</td></tr><tr>
<td>Butter</td><td>Ice cream</td><td>and more</td></tr>
</tbody></table>
```
The browser finally translates the HTML into a visible table.
While explaining all this: I quickly googled and yes, MathML has become an HTML5 standard! So there might be actually a way to display the Math Symbols in the result!
(This is the page I found: https://www.tutorialspoint.com/html5/html5_mathml.htm)
So finally there might be a possibility to show the Math in the result set, maybe with some trickery involved...https://gitlab.ethz.ch/vermeul/YATA/-/issues/12annotations can not be found with annotask2018-09-03T09:51:08Zvermeulswen@ethz.channotations can not be found with annotaskon mispar, annotask does not work properly. Annotations are in the database but do not appear when being asked for.
--> check & correct.on mispar, annotask does not work properly. Annotations are in the database but do not appear when being asked for.
--> check & correct.vermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/11removed annotations are not removed2018-04-12T12:32:06Zvermeulswen@ethz.chremoved annotations are not removedwhen deleting an annotation on mispar, it is not removed from the database.
--> Needs to be checked & correctedwhen deleting an annotation on mispar, it is not removed from the database.
--> Needs to be checked & correctedvermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/10error when editing section containing annotation2021-02-04T13:54:04Zvermeulswen@ethz.cherror when editing section containing annotationWhen editing a section which contains a part of the annotation (e.g. annotend) it will generate an error
⧼could not find category: 18⧽When editing a section which contains a part of the annotation (e.g. annotend) it will generate an error
⧼could not find category: 18⧽vermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/8Mispar: defining a category/like/this should not lead to a database error2021-12-09T16:51:47Zvermeulswen@ethz.chMispar: defining a category/like/this should not lead to a database error… create a nice error message instead.… create a nice error message instead.Category improvementsvermeulswen@ethz.chvermeulswen@ethz.ch2021-12-31https://gitlab.ethz.ch/vermeul/YATA/-/issues/7check that double-creation of the same category creates an error2021-02-04T11:54:03Zvermeulswen@ethz.chcheck that double-creation of the same category creates an errorWill I get an error message if I accidentally create identical parent/son pairs?
Yes. This is checked when you create or update a category.Will I get an error message if I accidentally create identical parent/son pairs?
Yes. This is checked when you create or update a category.vermeulswen@ethz.chvermeulswen@ethz.chhttps://gitlab.ethz.ch/vermeul/YATA/-/issues/6identify category without knowing its parent2018-03-16T13:29:46Zvermeulswen@ethz.chidentify category without knowing its parentQuestion: if I have a node with a unique name, do I need to refer to it by "parent_name/category_name", or is "category_name" enough?
At the moment parent_name/category_name is the convention used to identify any node. If you just say «...Question: if I have a node with a unique name, do I need to refer to it by "parent_name/category_name", or is "category_name" enough?
At the moment parent_name/category_name is the convention used to identify any node. If you just say «category_name» then it is assumed to be a top category, with no parent.
Maybe we could do something like */category_name or %/category_name to specify all categories with that name, regardless of its parent.vermeulswen@ethz.chvermeulswen@ethz.ch