
Dear Sharon,
by first, apologies for not replying earlier. I haven’t found the original email in my mailbox, so I guess it got lost somehow (spam, accidental deletion, etc..).
It’s possible that this has been resolved, following a bug fix I see from last year but I’m not sure it is exactly that one.
You could make a direct attempt by downloading VB3 15.1 and, without transitioning to it all your data, just try to recreate the issue.
I would also like to help you but I need to be able to recreate the issue. Unfortunately, in your description a few things are not clear to me (e.g. “viceversa” --> are the owl:import loops?) and I lack the general settings (kind of project, fundamental features active or not, like history or validation..).
So, besides the direct attempt from your side of directly testing VB 15.1, I can assist you if you prepare for me a very simple example (the simplest that you can create that reproduces the issue) and describe exactly the actions that you conducted, in terms of non-ambiguous references to actions on the UI. If you can reproduce it with some small data, you can even attach it to the email or you can put a download link to it if it’s larger than 100Kb. I need the full setup of the projects (I hope you can reduce it to two projects, with A importing B), with semantic model, lexical model and all checked options and, as mentioned, the data being involved.
Kind Regards,
Armando
From: vocben...@googlegroups.com <vocben...@googlegroups.com> On Behalf Of Sharon Süvari
Sent: Wednesday, April 1, 2026 6:48 PM
To: vocbench-user <vocben...@googlegroups.com>
Subject: [vocbench-user] Re: Could not delete ontology import, because that operation would produce graphs only kept live by staged graphs
Hello
I wanted to check in if there's been any development regarding this problem?
Sharon
Sharon Süvari kirjutas neljapäev, 12. märts 2026 kl 10:15:28 UTC+2:
Hello,
This time I'm writing regarding an error message I keep getting:
We have one project, let's call it main project, and a bunch of additional projects that are all connected to the main project and vice versa through metadata imports and cross-project triples in VocBench. The projects are constantly changing so whenever we want to update or remove the connection in the main project we get this error message. I've tried many ways to get around this problem but right now the only thing that works is deleting ALL the projects and starting over which isn't a sustainable method.
Do You have any idea how to fix this problem? Using VocBench v 14.0.0.
Best regards,
Sharon
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/48b2e040-b920-400f-9444-4155062a6346n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/021801dcc281%24bcd49390%24367dbab0%24%40uniroma2.it.
Thanks Thomas,
that’s indeed the one I found as the throw error was the same, but the fixing commit is precedent to the release of VB 14.0
This is the fix commit:
on the 18th of October 2024, 2 days after your report on this forum
and VB14 – which Sharon is using – has been released on March 2025
so I’m inclined to exclude that.
Thanks anyway for highlighting it!
Armando