Documents [tch300]

Manuel Gozalbes

It seems that in the description of a document it could be useful to include in some field the language in which it is written. How could this be added in some field in a standardized way? For objects it may have little use in general, but for documents it seems like relevant information. Should we look for a solution?

Alex

I believe it's unnecessary. Dédalo provides a method to describe the resource language.

Each resource has its own language definition, Original language rsc263. Why? Because the inventory could consist of documents in multiple languages, and the detail is better in the rescue instead the catalog. Therefore, I think the language in the inventory isn't a suitable choice.

Best

Manuel Gozalbes

I would like to use a parallel model for the section documents [tch300] that is configured as a hierarchy but i'm not sure how can I activate it. Is it possible? Can you help me?
Thank you

Alex

The typology/model component for the tch is Type of registration tch162.
But, as the Documents tch300 section is a virtual section as Objects tch1 and the request_config doesn't define the model section_tipo into the sqo:

{
  "request_config": [
    {
      "sqo": {
        "section_tipo": []
      },
      "show": {
        "ddo_map": [
          {
            "tipo": "hierarchy25",
            "parent": "self",
            "section_tipo": "self",
            "value_with_parents": false
          }
        ],
        "fields_separator": ", "
      }
    }
  ]
}

The default will be fired, so Property typologies tch2 is the model for all virtual sections!

Explanation:
All tch sections have only one TLD for all virtual sections, unlike the thesaurus, which uses different TLDs for each virtual section (e.g., es for Spain, fr for France, etc.).

Therefore, a question arises: is this configuration acceptable? Should we have a single unique typology/model thesaurus for all tch virtual sections or do we need different typology/model thesauruses for each tch section?

Currently, we have four virtual sections.

Object tch1
Photography tch100
Inventory tch200
Documents tch300

All with the same target typology/model

Property typologies tch2

What do you think?

Best

Manuel Gozalbes

I think that keeping a unique property typologies tch2 section will be more solid and compatible with any kind of project. This is more simple and guarantees that the model will be same and always available for every project no matter the inventories they use. Generally, models are not complicated so having one sounds like a good solution.

In relation to this, there is another issue. We have enabled tch300 as a hierarchy, and the tree visualization of the contents presents a small problem. The so-called term field used in thesauri, which is the value displayed in the tree visualization for sections such as tch300 (a virtual section of tch7), is currently mapped to the name of the property component. This field does not seem the most appropriate for that purpose, as it refers to a controlled list of generic object types and makes it more difficult to understand the content when browsing the tree layout.

I would suggest using, as in thesauri, a free-text field that allows users to enter values freely, such as the title [tch63] field. This would provide a much clearer and more informative representation of records in the tree view.
Would such a change be feasible?

Alex

Manuel Gozalbes Generally, models are not complicated so having one sounds like a good solution.

But, you will see all typologies/models into all virtual sections, you can filter it, but you can't to remove a part of the models tree into the caller component. It's ok?

Manuel Gozalbes I would suggest using, as in thesauri, a free-text field that allows users to enter values freely, such as the title [tch63] field.

For me is ok, but, maybe, we need both? and take in account that title could be a large text to show it into the tree.

Any other comment about it?
@Mariajobrador @Maribel @Eulàlia Mesalles @rca

Best

Manuel Gozalbes

Alex But, you will see all typologies/models into all virtual sections, you can filter it, but you can't to remove a part of the models tree into the caller component. It's ok?

It seems that it's OK.

Alex For me is ok, but, maybe, we need both? and take in account that title could be a large text to show it into the tree.

If you can show both, it's even better. It will be more clear.

Thank you

Alex

Manuel Gozalbes If you can show both, it's even better. It will be more clear.

Done!

It was implemented into the Ontology:

v6.9.3
2026-08-18T20:37:15+02:00

Update your installation to obtain it.

best