In dedalo 6.6.4 and upper, the api call thesaurus_parents not return information

cbrianso

In some of the dedalo updates, the call to the thesaurus_parents API must have stopped working, it does not return any data.

the call
/publication/server_api/v1/json/thesaurus_parents?code=xxxxxxxx&db_name=web_tangible_heritage&lang=lg-esp&term_id=www1_117&recursive=true

return
que en alguna de las últimas actualizaciones ha dejado de funcionar, y siempre devuelve vacío

{
"result": [],
"msg": "Ok. Request done [web_data::get_thesaurus_parents]",
"debug": {
"time": 0.004
}
}

but if I ask for the same element from records, it does return information to me
/records?code=xxxxxxxxxxx&db_name=web_tangible_heritage&table=ts_web_mupreva&ar_fields=section_id, parents&section_id=117&lang=lg-spa&limit=10

    "result": [
        {
            "table": "ts_web_mupreva",
            "section_id": 117,
            "parents": "[\"www1_61\",\"www1_66\",\"www1_106\",\"www1_208\"]"
        }
    ],

PaCo

Hi cbrianso

The problem is that the PHP constant DEDALO_RELATION_TYPE_CHILDREN_TIPO is missing, which is necessary for the resolution of thesaurus parents.

Solution:

Add to your server_config_api.php file, the DEDALO_RELATION_TYPE_CHILDREN_TIPO constant definition as

// DEDALO_RELATION_TYPE_CHILDREN_TIPO.
// This constant defines the tipo (type identifier) for component_relation_children
// from the thesaurus section. It is used to filter 'from_component_tipo' locators
// in the web_data::get_thesaurus_parents() method.
define('DEDALO_RELATION_TYPE_CHILDREN_TIPO', 'dd48');

In any case, resolution by get_records is more efficient and faster if you don't need all the information provided by get_thesaurus_parents.

Best.

cbrianso

I looked at the sample.server_config_api.php and this variable is not set, shouldn't it be there if it affects the functioning of the api?

Regarding get_records, it can be more efficient, but I need to make multiple queries to obtain the information of the parents, since I don't have the option to use resolve_portal for the parents field. On the other hand, with get_thesaurus_parents I obtain all the information with a single query.

Alex

cbrianso shouldn't it be there if it affects the functioning of the api?

Yes, you right, sorry... it will be added. (In fact, you can do so by submitting a request on GitLab or GitHub. ... )

cbrianso but I need to make multiple queries to obtain the information of the parents, since I don't have the option to use resolve_portal for the parents field.

What kind of information do you need? because usually only the parents' name is needed / resolved, and it is easy to get it in \records in fact, some diffusion has parents_term resolution to get this information.

Best

cbrianso

Perfect, thanks

Alex What kind of information do you need? because usually only the parents' name is needed / resolved, and it is easy to get it in \records in fact, some diffusion has parents_term resolution to get this information.

Yes, but I don't have permision to change diffusion ontology

PaCo

Added to documentation

DEDALO_RELATION_TYPE_CHILDREN_TIPO

and to the sample config file

./dedalo/publication/server_api/v1/config_api/sample.server_config_api.php

Bye

Alex

cbrianso Yes, but I don't have permision to change diffusion ontology

Ok, but, maybe you can talk with the system administrator to add it... changing the diffusion ontology (when it is a local ontology) is a very common thing. The diffusion ontology was designed to be super adaptable and efficient to avoid recursive and high cost calls. Little changes, as parents resolution, can improve a lot the access to data.

Best