resolve_portals_custom with mixed table IDs

albert__

Hello,

After a recent change in the API for the Mupreva website, we ran into an issue with resolve_portals_custom.

Some fields return a serialized list of IDs that we use to make extra calls directly using the resolve_portals_custom property. These fields include, for example, lists of parents, children, relations, etc.

At some point, it was discovered that some of those lists contained IDs from different tables. To solve this problem, the IDs list was changed to also include the typology of the object (tch1_xxx, tch100_xxx, etc.), but this broke the resolve_portals_custom functionality.

Is there a way to make this work in a single call with this new format? If not, I guess the solution would be to group the IDs by typology and then make multiple calls for each type to the corresponding table.

Thanks

PaCo

Hi albert__

Resolve portals are intended for cases involving a single table only.

If you need very specific information about a parent or related term (the title, for example), store it in the table itself; create a column in the diffusion ontology with that information.

If you need something more detailed, make two calls: the first using the standard search, and from the result, retrieve the IDs or term_ids and perform another search.

There is a parameter called ‘table_thesaurus_map’ that is used to resolve thesauri in a grouped manner—that is, to perform simultaneous searches across thesaurus and toponymy tables, similar to an SQL JOIN, but intended exclusively for thesaurus use.

Hope this helps

Best