Field tch241

pricua

Hi,

We have noticed that the autocomplete for the field Typology (tch241) has disappeared in the tch sections. We think it happened after updating to version 6.4, although we cannot be sure.
Clicking on the field in the browser console displays the following error:

We think it may be related to the fact that one of the related sections of tch241 is numisdata3, which we do not have in our installation.

If this is the reason, is there any way to fix it? I understand that one way would be to modify the ontology of the tch241 field, but when we update the ontology we would have the same problem again.

Best

pricua

Hi again,

As a clarification, it seems that modifying the ontology of the tch241 field, removing all references to numisdata from the ontology17 field, solves the problem and the autocomplete is now displayed again in the field, but we believe that this is not the best solution since it will be lost when the ontology is updated.

Best

Alex

Seems that you have the numisdata TLD active in Ontology main but you have not loaded the ontology.

Check if you have the numisdata TLD in Ontology -> Ontology main

find in the TLD component numisdata and check if the ontology is active, if is active change it to «No»

Log out and log back in to check if the error has disappeared.

In >v6.4 the main ontology controls what is active and used. If you have the TLD active but the ontology is not loaded you will get errors as you said.

And if your installation has not the numisdata ontology in Ontologies main say me to find any other cause.

Best

pricua

Hi,

After disabling the numisdata TLD in Ontology main (ID 14) the same error continues to appear. We have also tried to press the Ontology button to see if it had any effect.

I don't know if it can be related but we have detected that in the ontology tree some empty elements appear or belong to ontologies that we don't have. I don't know if it's normal or if there may be something in the ontology that we don't have right and it could be affecting it in some way.

Alex

pricua

Hi.

Can you see if you have numisdata rows in jer_dd table?

SELECT *
FROM "jer_dd"
WHERE "tld" = 'numisdata'

And if you have rows in matrix_ontology table?

SELECT *
FROM "matrix_ontology"
WHERE "section_tipo" LIKE '%numisdata%'

Seems that you have implemented numisdata ontology but is not loaded.

Best

pricua

Hi,

The first query returns a single row. This:

id    | terminoID  |    parent     | modelo | esmodelo | esdescriptor | visible | norden |    tld    | traducible |                relaciones                | propiedades |                  properties                   |                                             term                                              |  model

----------+------------+---------------+--------+----------+--------------+---------+--------+-----------+------------+------------------------------------------+-------------+-----------------------------------------------+-----------------------------------------------------------------------------------------------+---------
11454116 | numisdata0 | ontologytype8 | dd6 | no | si | si | | numisdata | no | [{"tipo":"ontology1"},{"tipo":"dd1201"}] | | {"color": "#2d8894", "main_tld": "numisdata"} | {"lg-eng": "Numismatic heritage | numisdata", "lg-spa": "Patrimonio numismático | numisdata"} | section

The second query returns no rows

Best

pricua

Hi,

We don't know if it could be related to the same thing, but another thing we have seen that happens is that in the Thesaurus listing when trying to list the relations, the following error is often displayed.

We've also seen that this error appears very often in the log

[ERROR]\n common::get_matrix_table_from_tipo Current tipo (numisdata3) model name is empty. Model is mandatory, check your model for tipo: 'numisdata3'

Any idea of what could be happening? It seems that for some reason something in numisdata is getting confused, but we don't know why.

Alex

pricua

The error seems to be the same in both cases, the thesaurus tree is calling the typology field (tch241), and the error appears because you have a numisdata ontology loaded, but only pointed to by the ontology root node. When Dédalo tries to resolve the numisdata3 model and doesn't find it in jer_dd it stops the process and logs an error.

I don't know why you have the main ontology of numisdata but you don't have the complete ontology (all nodes) and it makes a conflict.

Posible solution:, it is possible to change the behaviour to skip the resolution of the unloaded terms (if you installation doesn't have numisdata3 don't try to resolve it), in the meantime, you can remove the numisdata references in tch241 and not update the ontology, I will back when the update is ready.

Best

Alex

We've added a new control in the main ontology to prevent this cases. In version 6.4.4, the active control of the main ontology removes all nodes in the jer_dd table for the main tld. TThis prevents active but not fully loaded ontologies from affecting the usual behaviour of multiple components such as typology(tch241).

So, update your code to 6.4.4 and check if you have numisdata ontology in main ontologies section, change the active to no:

set active to no

and set the change pressing the update ontology tool.

Press the «Process» button to apply.

It will work.

Best

pricua

Hi,

I confirm that after updating to v.6.4.4 and disabling the numisdata ontology, the errors no longer appear, without having to modify the ontology of the tch241 field

Thank you so much