OpenAtlas

Dear Enric,

Thank you for reaching out. I'll take this as a reason to update the manual regarding imports. It has grown in the last year, and while I tried to keep it small and comprehensible, I should extend it with multiple examples.

I created an example (also attached as a file to this ticket):

id,name,description,reference_ids,reference_system_wikidata,origin_reference_ids,parent_id,openatlas_parent_id
type_1,New type attached to hierarchy,,,Q152419;close_match,,,29
type_2,Sub type ,,,,,type_1,
type_3,Sub type 2,,,,,type_1,
type_4,Sub sub type,,,,,type_3,
type_5,Type attached to existing type,,,,,,4067
type_6,Sub type of type_5,,,,,type_5,

First, you cannot create a new hierarchy through the import. Each entry must have either a parent_id or an openatlas_parent_id. The required columns are: id, name, parent_id, and openatlas_parent_id.

You can attach it directly to a hierarchy (e.g., Actor function) or to an existing type (e.g., Kinship). If you want to create a more nested structure, you can use parent_id (this is the ID you give the imported entries, e.g., type_1) to specify which imported type is the super type.

So in my example:

• type_1 is connected to a hierarchy, e.g., Actor relation.
• type_2 and type_3 are connected to the newly created type_1.
• type_4 is connected to the newly created type_3.
• type_5 is connected to an existing type, e.g., Kinship.
• type_6 is connected to the newly created type_5.

The order in which you enter it in the CSV should not be important, as long as each type has a parent (either through parent_id or openatlas_parent_id, not both, but this will be checked during import).

Regarding SQL, we removed this function due to security concerns. I'm sure you have already read that.

Thank you Enric for reporting and Bernhard for taking care of it.

About finding out the ids of the type roots. You can find it out through a sub type.
E.g. at the demo entry for Abbess at https://demo.openatlas.eu/entity/316 you can see the root Actor function in the breadcrumb and if you hover over it it will show: https://demo.openatlas.eu/entity/10, so the id of the Actor function root type would be 10.

Of course now that I'm writing this I realize how cumbersome that may be so I wrote an issue (see, #2605) to display it more conveniently.