Invalid component [component_relation_parent] configuration.

cbrianso

Updating from v5 to v6.6.5, I found that one of the thesaurus branches has disappeared.

Version 5

In version 6.6.4

Searching through the list, I see /dedalo/core/page/?tipo=tch280&mode=list

but it doesn't let me edit any entry, at all, it gives the following error

exporting the list, I see that in the field tch275, there are values like
[{"section_tipo":"hierarchy1","section_id":"265","from_component_tipo":"tch275"}]

According to the documentation, hierarchy1 is no longer used, how can these entries be modified to remove this parenthesis, and make it editable?

Thanks

Alex

Hi cbrianso

The thesaurus change was explained and discussed here.

cbrianso According to the documentation, hierarchy1 is no longer used...

Not really, hierarchy1 is used to create the thesaurus schema and the ontology nodes for it, but it's not a node in the thesaurus tree anymore, as it explained in the discussion about the change. So, you need the hierarchy1 definition.

And the tch280 was deprecated from the main tch schema, and it was changed to actv1.

Questions: do you have more exhibitions hierarchies for tch280? I see in the screen captures that you have hierarchy1 265 for exhibition, but the question is if you have more. (the solution could be different if you have more than 1 exhibition)
And
Do you have a specific diffusion schema for it?

Best

cbrianso

We have multiple elements tch280

We don't have any diffusion schema.

Alex

Situation:

tch280 (and its previous qdp280) section was used to create exhibitions, didactic activities, news and other general activities done by museums and projects. As tch is the definition of tangible heritage, if you want to use this activity definition in any other projects, as memory, oral history or documentary projects, you was force to load the full tch to load tch280. Therefore, actv ontology emerged as an independent ontology to be used by any kind of project, a common definition across all Dédalo projects.

And the same for the ontology definitions:

Didactic materials tch458 as clone of tch280
News tch400 as clone of tch280
And its equivalents qdp definitions.

As this sections are using as a hierarchies in thesaurus schema, they are created by the Hierarchy section, as any other thesaurus.

So, if you are using this definitions you will have a hierarchy node in Thesaurus->Hierarchy, in your specific case you have this definition as id 265

Steps to do:

1- Prepare the new situation.

Add actv TLD in your configuration, and update your ontology to get it.

2- Move your data.

We have defined 2 files to do it:

..dedalo/core/base/transform_defintion_files/move_tld/tch280_to_actv1.json
..dedalo/core/base/transform_defintion_files/move_to_table/actv1_to_matrix_activities.json

The first one map the tch280 ontology definition to new actv1 definition.

As actv1 has its own table in PostgreSQL matrix_activities and tch280 used matrix_hierarchy, the second file defines this change.

You can use the mapping data defined in maintenance panel for it:

Note: We are adding this step in the update for version 6.6.5 (released at 15-07-2025). So, you can use the update process to apply this step automatically.

Note2: The Publication definition tch478 was removed into actv, so, if you have data in this field, you need to move it into bibliographic reference actv119 manually (exporting the field data and set it as Publication into the Bibliographic Reference), this exception becomes because a double definition for publications in original qdp280 and tch280, both definitions has Publications tch478 and Bibliographic references tch453.

Note3: If you have exhibition1 hierarchy (check it previously) this step could make a conflict with that definition and stop the process by the DDBB constraints. Review your log and if this conflict appears, change TLD in the files or remove your existing exhibition1 data (if that is not used or is not relevant).

3- As your data was changed you will need to review your hierarchy definition according to the new situation.

To change it, you will need to use a local TLD for the new hierarchy, by default the mapping will change your data in this way:

qdp280 OR tch280 -----> exhibition1
qdp400 OR tch400 -----> news1
qdp458 OR tch458 -----> didactic1

But, if you need /want it, you can change the local TLD's in the map files of the point 2 previously to use it.

And you need to change the hierarchy definition similar to:

And link the main terms of the new hierarchies in the General term field:

4- As the diffusion ontology for tch280 was also deprecated and removed. You will need to create your own local diffusion definition linked to activities actv61

5- Set permissions for the users.

I hope is clear

Best

cbrianso

Thanks, the update solve the problem, and the entries are now visible. But, the entries lost the parents.

I was able to fix it manually

albert_b

Following this discussion, we have two exhibitions (exhibition1) in the thesaurus, along with an onomastic (on1) and a thematic (ts1) tree.

We need to configure the Publication API for one of the exhibitions and the thesaurus. I’ve been reading the documentation and the Agora forums, but I’m having trouble understanding the whole process.

How do we create our own local diffusion definition linked to activities (actv61)?

Following this thread: https://agora.dedalo.dev/d/169-how-to-create-a-new-web-site-in-the-tesaurus/2, I understand that I should create a new record in the Ontology main. Is that correct? Do I also need to create a new diffusion_domain?

Then, how do I define the publication schema? Can I do it entirely from the ontology tree, or do I also need to configure tables and fields in the server_config_api.php file?

Finally, do I need to set the diffusion_domain name in the server_config_api.php file?

Thank you

Alex

albert_b I should create a new record in the Ontology main. Is that correct?

Yes, you can create a local ontology with your local TLD in Ontology main.

albert_b Do I also need to create a new diffusion_domain?

Yes, because is your ontology space, but if you have one diffusion_domain defined previously, you only need to create the ontology node and rename it with your previous diffusion_domain. Take account that only 1 diffusion_domain name is allowed. So, if you have:

my_super_diffusion_domain_name -> oh56 -> diffusion_domain

and you create new node with the same name as:

my_super_diffusion_domain_name -> mylocalontology2 -> diffusion_domain

you will need to change the first one. Only one diffusion_domain name is valid.

albert_b how do I define the publication schema?

Creating nodes behind your diffusion_domain as diffusion_group, diffusion_element, table, etc. You can see a lots of examples in the default diffusion ontology...

albert_b Can I do it entirely from the ontology tree, or do I also need to configure tables and fields in the server_config_api.php file?

Yes, you can do it directly in the ontology. The only mandatory change in the configuration is to define what is the diffusion_domain of the installation in config.php.

albert_b do I need to set the diffusion_domain name in the server_config_api.php file?

No. server_config_api.php is the configuration for the publication API, a read only public data in diffusion system, and the diffusion_domain is used to publish data from work system to diffusion system. diffusion_domain identifies which part of the ontology will used to be applied into the publication process (when users press the publication tool button within Dédalo work system).

I hope is clear.
Best

albert_b

Hello again,

we want to use the default diffusion domain, and we are trying to create a table alias for the web exhibition

We are using the other table_alias as examples but it is not clear what we need to use in each field. What should we use as tld? and what are the connections needed in relations?

We followed the examples, but there is no publish button in exhibition1. What do we need to do to be able to publish?

Also, for a short time, we were seeing different values in "Tipo" for the ts_web on different computers, we saw a Tipo "ontology7" and a Tipo "oh0". Now it changed and both computers show "oh0", is this normal?

Thanks

Alex

albert_b We are using the other table_alias as examples but it is not clear what we need to use in each field. What should we use as tld? and what are the connections needed in relations?

Seems that you are changing, using or duplicating an Oral history node, NOT creating a node with your own TLD:

That is completely wrong and you are changing Dédalo behavior with unpredictable results.

You can not change, adding, moving, etc. a node of the sharing TLD as oh. YOU NEED TO CREATE YOUR LOCAL TLD and using it to generate new nodes.

Please read this:
Ontology

And you can see the Shared TLD here:
Defining prefix tipos
Thesaurus dependences

albert_b Also, for a short time, we were seeing different values in "Tipo" for the ts_web on different computers, we saw a Tipo "ontology7" and a Tipo "oh0". Now it changed and both computers show "oh0", is this normal?

Yes it's normal, when you open the node it will se the section_tipo as oh0 and when you click in any component it will show the tipo of the component as ontology7

Best

albert_b

We had to create our own TLD, we created a new record in Ontology main with our own TLD name making sure it's a unique name without conflict with shared TLDs, using the real section tipo of ontology1.

The oh Oral History TLD was missing from our config files, and we had to install it via Maintenance / Update Ontology, from the Official Dedalo Ontology server.

Finally we deleted all the nodes in the Ontology tree that we created and were using wrong TLD, and created a new diffusion_domain pointing to the new local TLD. You have to make sure to add the Term value for the spanish language to the diffusion domain. After that, we added children nodes to this diffusion domain (diffusion_group, diffusion_element, database_alias) always using the newly created local TLD.

The last element we created is a database_alias, pointing to the web_default database, and we were expecting this to make the default tables available to our own diffusion but we are not seeing them, and we cannot publish yet, so we are stuck again. What are we missing to be able to use these tables?

For instance, if we try to publish an element from the Thesaurus with TLD ts "Descriptors temàtics", we have the publish button available but it throws this error:

And you can see the log from Dedalo here: https://codefile.io/f/ip98nSchhC

Best

Alex

albert_b

I analyzed your error log and the main problem is:

common::get_matrix_table_from_tipo Error. Don't use non section tipo to calculate matrix_table. Use always section_tipo
 tipo: masle1
 model: diffusion_domain
 bt 0: {
    "file": "/var/www/dedalo/dedalo/core/common/class.common.php",
    "line": 3101,
    "function": "get_matrix_table_from_tipo",
    "class": "common",
    "type": "::",
    "args": [
        "masle1"
    ]
}

It appears that your local ontology masle1 was misdefined; therefore, please review your ontology to ensure it is configured correctly.
And the process explained by Paco will be useful to ensure that all shared ontologies are correct and not affected by the masle1 configuration.

Best

PaCo

Hi @albert_b,

Seems that you have a problem with some of the installed updates of code with ontology conflicts.
I think is more reliable to re-install the latest version in clean mode (6.6.5).
In order to do it, you should:

Note: Set the installation in maintenance mode if is used by other users. After finish every update step, reload the page to update the maintenance panel.

To prevent problems, make a full backup of dedalo files.

To allow code updater version detection, change manually the file version.php (../dedalo/core/base/version.inc) as:

$DEDALO_VERSION = '6.6.4';

Run the update code from the maintenance panel selecting '6.6.5' and 'Clean' option.
This will move your current Dédalo files to a backups/code/ and download a fresh Dédalo files preserving the config files.
More info about update code

Once the code has been updated, update the ontology with your list of used TLDs. like 'dd,rsc,ontology,hierarchy,lg,utoponymy,oh,ich,nexus,actv,..'

To allow data updater version detection, remove the matrix_updates record for 6.6.5 from your database.

DELETE FROM "matrix_updates" WHERE datos#>>'{dedalo_version}' = '6.6.5';

Update the code by deselecting any options that are unnecessary according to your criteria.

If the problem persists, there is something wrong with your data or ontology. In that case, you will need to debug the problem by viewing the PHP error log and reproducing the issue.

I hope this helps you

Good luck and please, post your result here to document this scenario. If you discover an existing bug, please post about it here, too.

Best