fix: preserve page hierarchy and property links in File-to-DB imports - #13188

All committers have signed the CLA.

With Import all tags enabled, tags are converted into classes. If a tag has the same name as the parent page in a namespace such as father/child, converting father into a class conflicts with the DB model: a page's parent must also be a page, not a class.

I think the better way is the importer detect this conflict and explicitly report that the graph cannot be imported with the current options. It should ask the user to rename the conflicting tag, or rename the parent page and update its namespace references, or remove the child page.

Adding an order to child or keeping father out of Library does not resolve the conflict. The resulting parent–child relationship would still violate the DB model.

That makes sense, I agree. I’m happy to update the implementation

Should we detect these conflicts in the import modal and block the import before it starts?

My concern is that some graphs might have thousands of these cases. Could we offer a bulk fix, like renaming conflicting tags to father-tag, or changing father/child to father-child and updating the references?

What approach would you prefer? I can adjust the PR accordingly

In fact, there is one more scenario that can also lead to the same issue, for example, both of these inputs conflict with the DB model:

• category/child together with #category when Import all tags is enabled, because category would be converted into a class.
• category/child together with a category:: value property declaration, because category would be converted into a property.

In the DB model, the parent of a page must also be a page.

I think we better give the choice to the user, and the importer should detect the conflict before importing, stop the import, and ask the user to resolve the source data. The message should identify the conflicting namespace parent and explain the available options:

• Rename the conflicting tag or property.
• Rename the namespace parent and update its references.
• Rename or remove the child page.
• For tag conflicts, disable Import all tags.