I have a few questions about the rsc170 image section:

  • In the photo list view, you might consider eliminating the 'Collection/File' and/or 'Project' columns to make more space for the 'Title' column, which contains more relevant image management information.
  • Also, it would be useful if the 'Descriptors' field could show their 'parents'.
  • Alex replied to this.

    Hi

    Angel 'Collection/File' and/or 'Project' columns to make more space for the 'Title' column,

    Ok, but I think it's not necessary to remove both, I made a mistake with the width of the title because it had 4.5rem as maximum and, as you said, it needs more space... I have fixed it in the ontology:

    Dédalo 2024-05-21T19:50:52+02:00 Benimamet

    Update to get the changes

    Angel Also, it would be useful if the 'Descriptors' field could show their 'parents'.

    Ok, done... in the same ontology update.

    Best

    Some questions related with the images

    • Is it feasible to add to the image section a new field for 'portrayed persons'? Is a sort of basic indexation in many cases, specially in the case of activities. If possible.. it should be a portal or a selection of the area on the image to link the person?
    • The image import tool maybe should include a few more fields like; footprint, caption date, location and descriptors. With these informations the image record will be always created automatically with basic information (multi-language).
    • There are two fields with the same name under the capture area > municipality (rsc46), and under the location area (rsc65). The difference is not totally clear to me. Where should I add the inmovable heritage information? Is necessary for tagging the image and it doesn't appear if is not set with the 'toponomy' typology. Should we define by defalult inmovable (tchi1) as toponymy to solve the same scenario in every section?
    • Another interesting solution is to add to this section rsc170 the image import tool. Sometimes we import hundreds of images. As we can add descriptors, they are under control in rsc170, ready to be searched. Importing these images directly to different sections may create in certain situations a lot of noise if the amounts of pictures are noticeable over the years.
    • Alex replied to this.
      6 days later

      Manuel Gozalbes it should be a portal or a selection of the area on the image to link the person?

      Hi

      Why you need a specific field?, you can use the indexation field for images that you can point to any thing in thesauri or people or... the field name is Descriptors rsc1054

      Manuel Gozalbes The image import tool maybe should include a few more fields

      Ok, but, In which section or field you want added it?
      ex: for Objects section, the definition is in tch136 but for the Identifying images field the definition is into tch66, etc... can you specify when do you need this fields?

      Manuel Gozalbes There are two fields with the same name under the capture area > municipality (rsc46), and under the location area (rsc65). The difference is not totally clear to me. Where should I add the inmovable heritage information? Is necessary for tagging the image and it doesn't appear if is not set with the 'toponomy' typology.

      Both fields refer to the official place name, but the first rsc46 is within the capture group rsc10 so its meaning is; where was the image shot?
      the second one rsc65 is inside a Ubication group rsc13 so its meaning is; where the physical copy of the image is?, if you have a negative or positive copy of the image where is it? is in your facilities? or in other places?

      Should we define by defalult inmovable (tchi1) as toponymy to solve the same scenario in every section?

      Yes!, you can change your immovable hierarchy definition into Hierarchy section (hierarchy1) changing the Typology (hierarchy9) to include it into toponyms hierarchies selecting Toponymy (typology section_id 2), and all components that call to toponymy thesauri will can get this information. And is your decision, if you want to go in this way, and it is totally correct.

      Manuel Gozalbes add to this section rsc170 the image import tool.

      Well, nobody ever said to include an import tool directly in the images section... it could be useful but you will need to control the image to locate it, because if you upload your images and if you don't index them or if you don't add some information it will be complicated to locate them, and also you will be adding more processes to assign the images in the objects, activities, etc.

      images not linked in their corresponding sections are unused images... maybe it makes sense as a "junk drawer", but... I think that you are adding more tasks into the workflow...

      Best

        • In my installation I can't link persons of the section rsc194. The 'descriptors' include the thesauri but not the 'persons'. How can I solve that?
        • I think that fields like footprint, caption date, location and descriptors are always useful, but specially for every image related with activities where sometimes there are hundred of images, which I would like to search directly in the images section.

        Alex the second one rsc65 is inside a Ubication group rsc13 so its meaning is; where the physical copy of the image is?, if you have a negative or positive copy of the image where is it? is in your facilities? or in other places?

        Maybe is the right explanation, but then, a better name for the field is 'topography'. In our case this is not necessary because we have all the photos catalogued in tch100, where we set the topography.

        The question of uploading images without linking to any content I thin it's interesting. Is it feasible if we can attach a basic description. It usually happens that we have to upload one hundred pictures of an activity. To have one hundred pictures in any record makes a lot of noise. Maybe a good solution is to link to the record only the best ones and then to import the rest directly to images. But if they include basic descriptors, title or footprint (attached when importing) are ready to be linked. I don't know, maybe we need to think about it...

        • Alex replied to this.

          Manuel Gozalbes Maybe is the right explanation, but then, a better name for the field is 'topography'.

          I think no, topography is not the municipality that is the use for this field.

          Manuel Gozalbes In our case this is not necessary because we have all the photos catalogued in tch100, where we set the topography.

          Perfect. Do not use if you don't need it...

          Manuel Gozalbes I think that fields like footprint, caption date, location and descriptors are always useful, but specially for every image related with activities where sometimes there are hundred of images, which I would like to search directly in the images section

          Ok, it's done into the ontology:

          Dédalo 2024-05-30T18:19:49+02:00 Benimamet

          Update to get it.

          Best

          Manuel Gozalbes In my installation I can't link persons of the section rsc194. The 'descriptors' include the thesauri but not the 'persons'. How can I solve that?

          Creating new thesaurus with the People rsc194 section. You can set the new hierarchy into the Thematic typology and it will be accesible to be indexed. And if you don't want to see it into the hierarchy tree set to no the field Active in thesaurus field.

          Best