eScriptorium issueshttps://gitlab.inria.fr/scripta/escriptorium/-/issues2021-04-26T16:37:22+02:00https://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/341Improving names of exported archives2021-03-23T18:09:18+01:00Alix ChaguéImproving names of exported archivesBecause there is no limit to the length of documents' names, and because some of our users named their documents with a lot of details, we are sometimes facing cases where the exported file creates a Windows bug where the name of the fil...Because there is no limit to the length of documents' names, and because some of our users named their documents with a lot of details, we are sometimes facing cases where the exported file creates a Windows bug where the name of the file is too long to be able to be manipulated once it's downloaded. Besides, it is very helpful to rely of document's ids, since we can easily reconstruct the url based on this id, which is not the case with the document's name (not unique nor permanent). So, I see 2 ways to impove the naming of the archive files exported from escriptorium:
- in [`export_%s_%s_%s.txt" % (slugify(document.name).replace('-', '_'),file_format, datetime.now().strftime('%Y%m%d%H%M'))`]( https://gitlab.inria.fr/scripta/escriptorium/-/blob/develop/app/apps/imports/tasks.py#L85) ; set a max length to `document.name`
- add the document's id in the name such as : `export_%s_%s_%s_%s.txt" % (document.pk, slugify(document.name).replace('-', '_'),file_format, datetime.now().strftime('%Y%m%d%H%M'))`
---
As a side comment, Transkribus enables the user to set the pattern of the exported filename. I have never used it so I consider it's probably too much effort to build an equivalent option. But I mention it still, juste in case. It looks like this:
![image](/uploads/dfbd462cf81a08894cdf978fad2bbf16/image.png)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/338Deleting transcriptions problems2021-05-25T17:49:11+02:00Robin TissotDeleting transcriptions problemsIt was impossible to delete the 'manual' transcription before as part of the code assume there should be at least one transcription, it seems that in some case it is possible now.
The deletion confirmation doesn't make it clear that it...It was impossible to delete the 'manual' transcription before as part of the code assume there should be at least one transcription, it seems that in some case it is possible now.
The deletion confirmation doesn't make it clear that it deletes for the whole document, not just this page.https://gitlab.inria.fr/scripta/escriptorium/-/issues/337keep line numbers small2021-03-05T22:24:12+01:00daniel stoeklkeep line numbers smallsometimes the line ordering algo gives wrong line numbers and it is necessary to zoom in to understand what is before what but the line numbers get so big one cannot see nothing. Would it be possible to keep them as small as they were in...sometimes the line ordering algo gives wrong line numbers and it is necessary to zoom in to understand what is before what but the line numbers get so big one cannot see nothing. Would it be possible to keep them as small as they were initially?
![image](/uploads/0d54754d5b5a4e08dc7798cc6ac04f6b/image.png)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/335new baseline drawn inside region should be automatically associated with this...2021-03-03T13:05:00+01:00daniel stoeklnew baseline drawn inside region should be automatically associated with this region (based on mid point not starting point)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/333Lost hash in js & css file name2021-02-24T20:27:49+01:00Robin TissotLost hash in js & css file nameIt was ensuring that clients get the new version of the files when it is updated even if the browser caches it.
Tried setting STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'
but then collectstatic ...It was ensuring that clients get the new version of the files when it is updated even if the browser caches it.
Tried setting STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'
but then collectstatic raises:
```
Post-processing 'vendor.css' failed!
ValueError: The file '"images/ui-icons_555555_256x240.png"' could not be found with <django.contrib.staticfiles.storage.ManifestStaticFilesStorage object at 0x7fa1b8bbc2d0>.
```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/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/325Import non explicit line/region typologies2021-02-02T16:28:16+01:00Robin TissotImport non explicit line/region typologiesFor now it is strict, we need a non-strict mode that update the ontology on the fly when importing.For now it is strict, we need a non-strict mode that update the ontology on the fly when importing.https://gitlab.inria.fr/scripta/escriptorium/-/issues/324freeze possibility to rotate when segmenting (or transcribing?)2021-02-01T16:22:50+01:00daniel stoeklfreeze possibility to rotate when segmenting (or transcribing?)I rotated an image in the middle of segmenting it automatically. Sent you the reference via email. Do need to freeze this possibility when item is locked.I rotated an image in the middle of segmenting it automatically. Sent you the reference via email. Do need to freeze this possibility when item is locked.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/322browse through regions2021-01-27T15:01:31+01:00daniel stoeklbrowse through regionsWe do need a UI tool to browse through the regions of a part. I have seen many examples where regions are so small or hidden under other points of another region that it is impossible or really hard to attain them individually. This coul...We do need a UI tool to browse through the regions of a part. I have seen many examples where regions are so small or hidden under other points of another region that it is impossible or really hard to attain them individually. This could be a column with region numbers next to the line numbers in the textannotation panel, which are associated with these regions. This would also allow to check whether there are empty regions. Clicking on one of these region numbers would select that specific region that could then be deleted or modified or whatever.https://gitlab.inria.fr/scripta/escriptorium/-/issues/321deleting splitting regions needs automatic line de-reassociation2021-01-27T16:16:24+01:00daniel stoekldeleting splitting regions needs automatic line de-reassociationIf one deletes a region, the lines associated to it should be automatically disassociated from it.
If one divides a region into two (or more) all lines in it should automatically be reassociated to the line in which their central point i...If one deletes a region, the lines associated to it should be automatically disassociated from it.
If one divides a region into two (or more) all lines in it should automatically be reassociated to the line in which their central point is. Any other behavior is counterintuitive and will cause great confusion with users also because it is not shown in the UI that these lines are still associated to a ghost or to the wrong region. I call this a bug and not a feature request as it is unwanted behavior.https://gitlab.inria.fr/scripta/escriptorium/-/issues/320Onboarding updates needed2021-01-17T20:52:45+01:00daniel stoeklOnboarding updates neededPlease add "pdf" to the import options in onboarding.Please add "pdf" to the import options in onboarding.