images > rsc170

Manuel Gozalbes

In the section 'images' (rsc170), i've replaced a text in the fields 'title' (rsc23) and 'Photo caption' (rsc31), in Valencian language, "Tresor d'Alcublas (Valencia)". and the result is this: "Tresor d%27Alcublas (Valencia)."
Application was set Valencian/Valencian.

Alex

Thanks for the report,

Yes, it happens when the data is encoded to be used in a new process handler (to show the server process to the client), the process has a check for the ' because it is necessary to break the exec shell injection and, as you explain, in cases where the text literal has ' the literal remains encoded %27 when is propagated.

It was fixed into the v6.2.1

Update your installation code to get the update and the fix.

Best

Manuel Gozalbes

In the field descriptors the autocomplete is not working when looking for entries of the inmovable heritage section (tchi1). Is it posible to link contents with the link tool, but the term linked is not displayed, only the parents are shown.
I would suggest to add to the descriptors field the activities group of thesauri to improve the capabilities of the indexation.
Thank you

Alex

Manuel Gozalbes I would suggest to add to the descriptors field the activities group of thesauri to improve the capabilities of the indexation.

Done! it was changed into the ontology:

Dédalo 2024-06-27T09:42:17+02:00 Benimamet

Update your installation to get it.

Best

Manuel Gozalbes

We have updated to v. 6.7.1 with the new fantastic features in the field image [rsc29] to crop and remove background. In our installations (mupreva and MIB) happens that when we crop the image and we press the button create new, the cropped image replaces the original one instead of creating a modified one.
Is it necessary to create a modified one to edit?
Thank you

Alex

Manuel Gozalbes , the cropped image replaces the original one instead of creating a modified one.

This behaviour is not correct, the crop/rotate process will only change the modified and other qualities, but they shouldn't touch the original files.

To clarify:

Rotate and crop processes don't create a modified. They change all other qualities except the original.
Remove background create a modified. And change all other qualities except the original.

Therefore, all changes shouldn't change the original...

Can you explain in detail the error that you found?

Best

Alex

Hi. We’ve identified an issue that may lead to unexpected behavior when handling uploaded files.

The Issue:

If you delete the original uploaded file (e.g., image.png) and only keep the normalized file (e.g., rsc29_rsc170_5.jpg), certain processes (such as Remove Background) may remove or alter the normalized file.

Why Does This Happen?

The normalized file is derived from the original uploaded file and can be regenerated from it.
When you use functions like Remove Background, Dédalo expects the original file to be present, as it uses it to recreate high-quality modified versions.
If the original file is missing, the system attempts to regenerate files from it, but since the original is gone, this can result in the unintended removal of the normalized file.

Example Scenario:

You upload image.png (stored as Original).
Dédalo generates a normalized original version: rsc29_rsc170_5.jpg.
If you delete image.png and only keep rsc29_rsc170_5.jpg, running Remove Background will fail to regenerate files properly, leading to data loss.

Solution:

Do not delete original uploaded files. They are essential for processes like background removal and image normalization.
This behavior was addressed in v6.7.2, but keeping original files is still a best practice.

Let us know if you have any questions!

Best regards
Alex

Manuel Gozalbes

In the images section rsc170, there are a couple of improvements that could enhance usability.

First, when images are imported, the target field selector (Images or Identifying Images) does not actually apply the selected value on the imported files. When a specific option is already chosen before uploading, the imported images do not use that target field value, unless it's modified. This behavior should be changed so that all imported images automatically adopt the value selected in the dropdown in every situation. Maybe, the selector should default to a blank state, requiring the user to explicitly choose the destination field before importing. The selected value should then be determinative and applied uniformly to all uploaded images. At present, inconsistencies can arise between the dropdown value displayed and the actual target field assigned to the imported images. As a result, images may end up in a destination different from the one apparently indicated by the interface, which creates confusion and undermines data integrity.

Secondly, in the rsc170 image importer, specifically the one that imports directly into the Images section, it would be nice to incorporate data fields for photographer, editor, or digitizer. These fields are already available in other contexts, such as when importing images into tch records. This would benefit the data quality when importing.

Thank you

Alex

Manuel Gozalbes

I Added the fields to the import in the image section rsc170 in the ontology:

version: 6.8.8
2026-03-12T09:49:07+01:00

Update your Dédalo to obtain it.

For the Import behavior to select the destination, it works if you change the selection after the image files are uploaded. I understand that this could be confusing when you don't change it again to set the destination in another bulk process. However, the selection change is set for an initial upload process. I recommend closing the import after the process is done to refresh all, including the process, browser caches, and connection with the server. It's a bad idea to reuse the same window to upload multiple processes (a bulk, another one, another one, etc.).

I will change the select destination behavior, but it's better to close the tool after one process and open it again in all situations.

I will back when this change will ready.

best

Manuel Gozalbes

If that is the best practice ¿is it a good option that the system closes the tab / window automatically after the import is finished?

Manuel Gozalbes

It would be useful if all the image fields can link contents just by entenring the ID of the image in the predictive text. I’m not sure whether this is something that needs to be implemented case by case, or if it could be applied globally to all image occurrences in the system. In any case, it seems like a valuable feature wherever image fields are involved.

Another interesting and useful feature would be the ability to link image batches using the link button; this is that a single click could attach all required images at once. This might be a more general functionality that could also be beneficial for any fields where content linking is used.

Thank you

Alex

Manuel Gozalbes the image fields can link contents just by entenring the ID of the image in the predictive text

I made a test in Identifying images tch66, now you can enter the id and the image can be linked. Try and tell me if this behaviour is ok.

Added in the ontology:

version: 6.8.8
2026-03-31T20:22:45+02:00

Update your installation to obtain it.

Manuel Gozalbes interesting and useful feature would be the ability to link image batches using the link button

It will wait until v7... right now, we are developing this version, and add new features in both versions are double effort... so, you will need to wait.

Best