eScriptorium issueshttps://gitlab.inria.fr/scripta/escriptorium/-/issues2021-09-01T08:27:06+02:00https://gitlab.inria.fr/scripta/escriptorium/-/issues/356freeze automatic reordering button needed urgently2021-09-01T08:27:06+02:00daniel stoeklfreeze automatic reordering button needed urgentlyVery frequently we encounter the situation that complex line ordering has been manually fixed and then someone notices that a line needs to be added or deleted and all the reordering work needs to be redone. The best solution would be a ...Very frequently we encounter the situation that complex line ordering has been manually fixed and then someone notices that a line needs to be added or deleted and all the reordering work needs to be redone. The best solution would be a button on top of the segmentation panel (because here is what causes the reordering) that can toggle the ability to automatically reorder. This should be written into the dbase for the relative part and changed only if the button is hit another time to untoggle. It is really important to keep the workflow straight. Sometimes time for manual reordering correction can be longer than for all other steps.https://gitlab.inria.fr/scripta/escriptorium/-/issues/355Transcription lost (?), unable to download even the corrected segmentation2021-06-16T09:42:46+02:00Thibault ClériceTranscription lost (?), unable to download even the corrected segmentationI don't know if this is a bug or a feature, but here is what happened to two colleagues over the last couple days: they tried a lot of different segmenter, and ended up using it on manuscripts that had some ground truth of segmentation.
...I don't know if this is a bug or a feature, but here is what happened to two colleagues over the last couple days: they tried a lot of different segmenter, and ended up using it on manuscripts that had some ground truth of segmentation.
It seemed it removed their ability to transcribe (`e.line.currentTrans` is undefined` in console), and because there was no transcription, the export button would not appear (even so there is segmentation ground truth).
I found a "quick fix hack" that is: simply run a transcription model on ONE of the page at least. Button reappears, everybody is happy.
But I thought it might be a bug ?https://gitlab.inria.fr/scripta/escriptorium/-/issues/354transcription of same image changes when rotated2021-05-19T19:17:14+02:00daniel stoekltranscription of same image changes when rotatedE.g. normal: ![image](/uploads/7137fd166665c1e7eb7bb4558e932a48/image.png)
upside down: (screenshot exported to paint, rotated there and switched panel 2 and 3 to make it comparable): ![image](/uploads/65570cc744a0df4358d6a6336c0a51a6/im...E.g. normal: ![image](/uploads/7137fd166665c1e7eb7bb4558e932a48/image.png)
upside down: (screenshot exported to paint, rotated there and switched panel 2 and 3 to make it comparable): ![image](/uploads/65570cc744a0df4358d6a6336c0a51a6/image.png)
look especially on the short lines on the right or the completely empty lines.https://gitlab.inria.fr/scripta/escriptorium/-/issues/352increase/decrease fontsize button in transcription modal2021-05-17T00:25:46+02:00daniel stoeklincrease/decrease fontsize button in transcription modalCould we pleeeeeeeeeeeeeeeeeeeeeeeeeeeease get two buttons for increase/decrease font size for the comparison visualization in the transcription modal? It can be so tiny. I know the trick to switch the rem in the console but it is a nigh...Could we pleeeeeeeeeeeeeeeeeeeeeeeeeeeease get two buttons for increase/decrease font size for the comparison visualization in the transcription modal? It can be so tiny. I know the trick to switch the rem in the console but it is a nightmare to teach this in a tutorial and quite time consuming because one has to do it again as soon as one goes to the image wheel and back. Here is a common example display:
![image](/uploads/9a18924dcbd932b68dc97f388fe546bb/image.png)https://gitlab.inria.fr/scripta/escriptorium/-/issues/351newly created line in segmentation filled with wrong text2021-05-15T11:07:00+02:00daniel stoeklnewly created line in segmentation filled with wrong textIf I create a new line in the segmentation panel in a text with existing transcription and then want to add it's text, it is filled with the text of the previous/next line and I am not sure what would happen if I started to correct this....If I create a new line in the segmentation panel in a text with existing transcription and then want to add it's text, it is filled with the text of the previous/next line and I am not sure what would happen if I started to correct this. After hitting F5 it is fine, but this seems a digression.https://gitlab.inria.fr/scripta/escriptorium/-/issues/350Move api's bulk_create, bulk_update and bulk_delete to a single bulk endpoint2021-05-04T13:49:35+02:00Robin TissotMove api's bulk_create, bulk_update and bulk_delete to a single bulk endpointFor both lines and transcriptions. Use the request method to instantiate the serializer accordingly.For both lines and transcriptions. Use the request method to instantiate the serializer accordingly.https://gitlab.inria.fr/scripta/escriptorium/-/issues/349adding text to lines without polygons in either 3rd or 4th panel gives js error2021-05-04T11:29:45+02:00Robin Tissotadding text to lines without polygons in either 3rd or 4th panel gives js errorhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/343too sensitive2021-04-06T01:54:09+02:00daniel stoekltoo sensitiveThere is some change in the behavior for mouse clicks in the segmentation panel. I have much pain in correcting layout because it starts creating lines all the time when I try to select a line instead. and then the escape key usually doe...There is some change in the behavior for mouse clicks in the segmentation panel. I have much pain in correcting layout because it starts creating lines all the time when I try to select a line instead. and then the escape key usually doesnt kill the unborn line right away.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/340Error while editing parts of documents when the document name contains a sing...2021-03-23T17:50:32+01:00TADJO TAKIANPI Yves ConstantinError while editing parts of documents when the document name contains a single quote.Input :
- Document name : DAHN d'Estournelles
- Some images
clicking on the edit tab displays nothing.
![Console_javascript_error](/uploads/3c37f3a10589e712ee16af38aa046139/Console_javascript_error.png)Input :
- Document name : DAHN d'Estournelles
- Some images
clicking on the edit tab displays nothing.
![Console_javascript_error](/uploads/3c37f3a10589e712ee16af38aa046139/Console_javascript_error.png)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/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/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/331Import transcriptions from PDF2021-02-11T14:33:02+01:00Alix ChaguéImport transcriptions from PDFI propose to work on a transformation scenario enabling users to transform a PDF into an ALTO XML v. 4 compatible with eScriptorium.
At the moment I have two use cases:
- PDF generated with FineReader
- PDF generated with Limb
For now, ...I propose to work on a transformation scenario enabling users to transform a PDF into an ALTO XML v. 4 compatible with eScriptorium.
At the moment I have two use cases:
- PDF generated with FineReader
- PDF generated with Limb
For now, this would be a step the user has to take before using the "import XML" option, outside of eScriptorium.https://gitlab.inria.fr/scripta/escriptorium/-/issues/329Ability to load font or provide also MUFI compatible font2021-02-10T12:00:09+01:00Thibault ClériceAbility to load font or provide also MUFI compatible font**Description**
When dealing with medieval manuscripts (mostly), there is sometime a need for having our own font or at least MUFI compatible font ( See https://mufi.info/m.php?p=mufi&i=960 ). Some users like Jean-Baptiste Camps are def...**Description**
When dealing with medieval manuscripts (mostly), there is sometime a need for having our own font or at least MUFI compatible font ( See https://mufi.info/m.php?p=mufi&i=960 ). Some users like Jean-Baptiste Camps are definitely having a huge use of these kind of fonts.
**Proposed solutions**
1. Have the ability to select the display font with pre-loaded fonts like some from MUFI
2. Have the ability to upload our own fonts (probably with some security issue ?)
3. Have the ability to load fonts in our localStorage ? See https://jaicab.com/2015/03/03/introducing-localfont-a-localstorage-solution/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/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.