eScriptorium issueshttps://gitlab.inria.fr/scripta/escriptorium/-/issues2021-05-21T16:16:40+02:00https://gitlab.inria.fr/scripta/escriptorium/-/issues/353Use a Many-to-Many relation between Document and OCRModel2021-05-21T16:16:40+02:00Bastien AbadieUse a Many-to-Many relation between Document and OCRModel
The goal is to convert the `OcrModel.document` Foreign Key to an `OcrModel.documents` Many-to-Many relation towards `Document` instances.
This means several low-level changes:
- an `OcrModel` would then be usable across multiple docume...
The goal is to convert the `OcrModel.document` Foreign Key to an `OcrModel.documents` Many-to-Many relation towards `Document` instances.
This means several low-level changes:
- an `OcrModel` would then be usable across multiple documents
- a document would still be usable across multiple `OcrModel` instance
- the `OcrModel.owner` user would be the administrator of the model, no access rights could be easily extracted/aggregated from documents
A M2M "through" model named `OcrModelDocument` would be created, only to store the relationship between `OcrModel` and `Document` alongside a `created` date (it's easier to do that from the beginning than a later migration to add it).
The `OcrModelDocument` model would also store boolean states descritbing the interactions between an `OcrModel` and a `Document`:
- `trained_on` would be used when the model has been trained on the document
- `executed_on` would be used when the model has been executed on the document to produce results
A unique constraing on `document_id` and `model_id` would ensure than only one M2M relation is possible between a model and a document.
This kind of changes can break a lot of functionalities in small ways, so we would need to fix the behaviour of (at least) these parts:
- document creation interface
- training tasks
- access control to models and documents
- API `OcrModelViewSet` and its usage
At this stage, we only update the database and surrounding code, reproducing current behaviour.
The resulting code should be mergeable as-is and serve as basis for features development.Eva BardouEva Bardouhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/348Blank edit page when the title of the document contains '2021-05-04T12:32:00+02:00Robin TissotBlank edit page when the title of the document contains 'https://gitlab.inria.fr/scripta/escriptorium/-/issues/347Applying segmentation model fails2021-04-26T15:27:59+02:00Hayim LapinApplying segmentation model failshttps://www.escriptorium.fr/document/581/edit/
elements 6-10, using model: paris_BNF328_329trial_3__best several pages failed. Any way of telling whether this is a faulty model or a bug on the server side?
Document has the same 5 jpegs r...https://www.escriptorium.fr/document/581/edit/
elements 6-10, using model: paris_BNF328_329trial_3__best several pages failed. Any way of telling whether this is a faulty model or a bug on the server side?
Document has the same 5 jpegs repeated for comparison of segmentationhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/346Server not updating from web app.2021-04-28T11:40:52+02:00Hayim LapinServer not updating from web app.Firefox on Windows.
* Not recalculating masks unless individual line is double clicked
* Not saving manual resegmentation
Could this just be a load issue on the server end?
Edit: also not renumbering lines after associating with regions.Firefox on Windows.
* Not recalculating masks unless individual line is double clicked
* Not saving manual resegmentation
Could this just be a load issue on the server end?
Edit: also not renumbering lines after associating with regions.https://gitlab.inria.fr/scripta/escriptorium/-/issues/345Add default model in list of models available for finetuning2021-04-26T12:23:50+02:00Alix ChaguéAdd default model in list of models available for finetuningAt the moment it is not possible to finetune the default segmentation model (blla.mlmodel) when we train a segmenter. Is it possible to add it to the list of available models?
![image](/uploads/2adcea4fe6b972c8843217abab2cdef6/image.png)At the moment it is not possible to finetune the default segmentation model (blla.mlmodel) when we train a segmenter. Is it possible to add it to the list of available models?
![image](/uploads/2adcea4fe6b972c8843217abab2cdef6/image.png)https://gitlab.inria.fr/scripta/escriptorium/-/issues/344Hitting ctrl+arrow in the transcription modal doesn't save2021-04-26T16:37:22+02:00Robin TissotHitting ctrl+arrow in the transcription modal doesn't savehttps://gitlab.inria.fr/scripta/escriptorium/-/issues/342Letters cut off in some scripts2021-04-19T16:42:41+02:00Robin TissotLetters cut off in some scriptsThe letters are not completely visible in the transcription modal input:
![image](/uploads/88faf3dd57a717d7a5331ac78d683de9/image.png)
![Zavia_270](/uploads/9c5f057f28bcc3010fecaa53c21c6065/Zavia_270.jpg)[Zavia_270.xml](/uploads/b4c84f...The letters are not completely visible in the transcription modal input:
![image](/uploads/88faf3dd57a717d7a5331ac78d683de9/image.png)
![Zavia_270](/uploads/9c5f057f28bcc3010fecaa53c21c6065/Zavia_270.jpg)[Zavia_270.xml](/uploads/b4c84f4d895834e4cd372a9e7dce8fd2/Zavia_270.xml)https://gitlab.inria.fr/scripta/escriptorium/-/issues/339copying empty lines in panel 4 should insert CR2021-05-04T12:31:51+02:00daniel stoeklcopying empty lines in panel 4 should insert CRCurrently if one copies from one transcription level into another and there are empty lines in the middle none of these empty lines is represented by a CR and all subsequent lines are copied into wrong lines. Also for text export, I woul...Currently if one copies from one transcription level into another and there are empty lines in the middle none of these empty lines is represented by a CR and all subsequent lines are copied into wrong lines. Also for text export, I would greatly support inserting empty lines with a CR rather than nothing.https://gitlab.inria.fr/scripta/escriptorium/-/issues/336new line drawn on segmentation panel is accessible on transcription panel onl...2021-04-26T12:43:28+02:00daniel stoeklnew line drawn on segmentation panel is accessible on transcription panel only after leaving page and going back (regression)https://gitlab.inria.fr/scripta/escriptorium/-/issues/334transcription not accepted after first line2021-03-04T09:56:24+01:00daniel stoekltranscription not accepted after first lineIn the transcription modal only manual corrections to the first line corrected are accepted. All other corrections for subsequent lines are NOT stored in the database. I assume this is linked to the previous issue.In the transcription modal only manual corrections to the first line corrected are accepted. All other corrections for subsequent lines are NOT stored in the database. I assume this is linked to the previous issue.https://gitlab.inria.fr/scripta/escriptorium/-/issues/332Fix comparison modal behaviour2021-02-24T20:31:13+01:00Bastien AbadieFix comparison modal behaviour> Bug reported today by Daniel by email
The comparison modal is used to compare two different transcriptions of the same text. One chooses the transcription_levels one wants to compare here:
![image](/uploads/11c5f9b637be8228da2c5a74de...> Bug reported today by Daniel by email
The comparison modal is used to compare two different transcriptions of the same text. One chooses the transcription_levels one wants to compare here:
![image](/uploads/11c5f9b637be8228da2c5a74dec98ecf/image.png)
If I select a transcription here currently it switches the main transcription panel to it. **It should NOT do this**.
![image2](/uploads/e93ca916de9ff5a4b504f5814cc028a2/image2.png)
Rather the "transcription panel" should remain on the previously selected choice. Checking the boxes should only influence which texts are compared in the comparison modal, meaning only the two lines (circled in red), those below the line from the currently chosen transcription level (circled in blue):
It should only affect the lines encircled in red, not the text in the transcription panel (and not the line encircled in blue, taken from the transcription panel).
![image3](/uploads/590f477e373a3d8dd48d1207cf541ad8/image3.png)Eva BardouEva Bardouhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/330Have a user or document-based virtual keyboard - character/character sequenc...2021-04-26T12:53:29+02:00Thibault ClériceHave a user or document-based virtual keyboard - character/character sequence shortcut**Description**
In the context of allographetic transcription or in general when dealing with weird characters, some researchers make use of a wide range of characters. Sometime, those characters can be awful to find again (think weird ...**Description**
In the context of allographetic transcription or in general when dealing with weird characters, some researchers make use of a wide range of characters. Sometime, those characters can be awful to find again (think weird monetary characters for example) and it can be quite useful to have the ability to record them (with a name for example).
It would be great if we could have a INSERT SPECIAL CHARACTER function and USER or preferably DOCUMENT-based list of (character|character-sequence, sequence name). Other solution like Transkribus use a custom virtual keyboard but I am sure that something like a search function would be efficient as well.
Having this at the document level might facilitate using the same character when cooperating with "colleagues". Retrieving some information from the model could be useful as well when dealing with reused model (but that's more a note for later than for right now ;) )
**Relation**
This is related but not tied to #329
**Solution**
In order of preferences:
1. At the user account level, give the ability to record quick shortcut for special characters
2. At the user account level, give the ability to record quick shortcut for special characters
+
1. Ability when transcribing to use the virtual keyboard or search functionhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/328Reattribute numbers to line using text regions2021-02-24T14:58:16+01:00Thibault ClériceReattribute numbers to line using text regions**Description**
I have been playing around with copy-pasting content into eScriptorium in order to prepare our data for CREMMA. We have a lot of content that are not Transkribus-born or eScriptorium born that we'd wish to transfer onto ...**Description**
I have been playing around with copy-pasting content into eScriptorium in order to prepare our data for CREMMA. We have a lot of content that are not Transkribus-born or eScriptorium born that we'd wish to transfer onto eScriptorium. To do that, we copy past column by column the content of the text we have.
I made a small video about the whole process : https://www.youtube.com/watch?v=UZy1ajfQH0o
The issue is transcription lines are ordered by vertical appearance and are not computed again when merge into a text region. This lack of functionality is clearly damaging unnecessarily the time we spent transferring the data.
**Description of feature**
Based on text region, renumber globally the lines.https://gitlab.inria.fr/scripta/escriptorium/-/issues/327Adjustments in local install documentation2021-03-04T10:04:21+01:00Alix ChaguéAdjustments in local install documentationHi,
In the documentation on how to install escriptorium locally, it is said:
> It is then recommended to set $DJANGO_SETTINGS_MODULE
>
> ```
> $ export $DJANGO_SETTINGS_MODULE escriptorium.local_settings
> ```
But I get the following ...Hi,
In the documentation on how to install escriptorium locally, it is said:
> It is then recommended to set $DJANGO_SETTINGS_MODULE
>
> ```
> $ export $DJANGO_SETTINGS_MODULE escriptorium.local_settings
> ```
But I get the following error:
```
(env) achague@achague-vm:~/Documents/escriptorium$ export $DJANGO_SETTINGS_MODULE escriptorium.local_settings
bash: export: `escriptorium.local_settings': not a valid identifier
```
Following [Django's documentation](https://docs.djangoproject.com/fr/3.1/topics/settings/#the-django-admin-utility), I suggest this line be changed to:
```
$ export DJANGO_SETTINGS_MODULE=escriptorium.local_settings
```https://gitlab.inria.fr/scripta/escriptorium/-/issues/326region scissor mode should disenable point moving2021-03-04T15:51:33+01:00daniel stoeklregion scissor mode should disenable point movingif one is in region scissor mode, the cursor should not be able to move points. sometimes one needs to cut close to points and it is hard to get them without selecting them. for moving points one could simply switch back to non-scissor m...if one is in region scissor mode, the cursor should not be able to move points. sometimes one needs to cut close to points and it is hard to get them without selecting them. for moving points one could simply switch back to non-scissor mode.https://gitlab.inria.fr/scripta/escriptorium/-/issues/323import filename doesnt work if image_filenames include space2021-03-04T10:07:38+01:00daniel stoeklimport filename doesnt work if image_filenames include spaceIf the image fname includes a space the xml import cannot identify the img-fname in the file with the images.If the image fname includes a space the xml import cannot identify the img-fname in the file with the images.https://gitlab.inria.fr/scripta/escriptorium/-/issues/319onboarding stalls2021-03-04T10:44:09+01:00daniel stoeklonboarding stallsThe onboarding stalls after getting the explanation of the "edit" tab instead of opening the images tab upon hitting "next. You have to get out by hitting escape and then get a warning if you do not want to get further help.The onboarding stalls after getting the explanation of the "edit" tab instead of opening the images tab upon hitting "next. You have to get out by hitting escape and then get a warning if you do not want to get further help.https://gitlab.inria.fr/scripta/escriptorium/-/issues/314Incomplete importation?2021-01-08T18:14:54+01:00Alix ChaguéIncomplete importation?Hi,
I'm seeing a weird behavior when I try to import a transcription. Not all segments are created, as you can see on the images below:
> document as it should be imported:
![image](/uploads/809bcd53da227a497cba243606b743d4/image.png)
...Hi,
I'm seeing a weird behavior when I try to import a transcription. Not all segments are created, as you can see on the images below:
> document as it should be imported:
![image](/uploads/809bcd53da227a497cba243606b743d4/image.png)
> Document after import:
![image](/uploads/4eb11fe5b9e4c56e2e75fdae81031782/image.png)
It seems that the problem happens during the importation task because the transcriptions are in the XML files.
![image](/uploads/d9459ba05980c40553ca93a6524ae707/image.png)
Note that the bug happens whether I use ALTO or PAGE. It's a major problem for me at the moment because we were trying to finetune a segmenter using data exported from several eScriptorium documents.
Did you notice this issue before? We are on version 0.7d.https://gitlab.inria.fr/scripta/escriptorium/-/issues/312keep region and line IDs in export2021-01-04T10:51:48+01:00daniel stoeklkeep region and line IDs in exportCurrently, the export assigns cryptic region and line IDs in the export instead of using the eScriptorium identifiers. I think it would be much more convenient to keep them for external treatment and reimport because the identification w...Currently, the export assigns cryptic region and line IDs in the export instead of using the eScriptorium identifiers. I think it would be much more convenient to keep them for external treatment and reimport because the identification would be straightforward as long as you stay on one platform. I see no advantage in the currently used cryptic IDs that break these links.https://gitlab.inria.fr/scripta/escriptorium/-/issues/310need transcription modal max height2020-12-17T15:26:47+01:00daniel stoeklneed transcription modal max heightFor short lines the modal takes up the whole page so that e.g. the comparison lines are not displayed, i.e. https://www.escriptorium.fr/document/301/part/55455/edit/
bottom line (the only one with manual entry). One can get more real es...For short lines the modal takes up the whole page so that e.g. the comparison lines are not displayed, i.e. https://www.escriptorium.fr/document/301/part/55455/edit/
bottom line (the only one with manual entry). One can get more real estate with F11 but for some lines
even that does not suffice.
![image](/uploads/dc6ae8c5eb6d9bb1b2aaec72dca85950/image.png)