No changes when updating a vocabulary

[sinanatra]

Hello, i am trying to update the ecrm vocabulary, from version 200717 to the current one.
I have no issues doing that in my localhost version, but not on the production server.

The only difference in both version is the namespace URI. In my localhost i have http://erlangen-crm.org whereas in prod i have http://erlangen-crm.org/200717/.

I don’t have any errors back, just the notification that there are no changes to the vocabulary - which is not the case. If i proceed, nothing changes.

Could the namespace be the issue? could i change it in someway?

[sinanatra]

actually sometimes i receive a log message.:

exception 'Omeka\Api\Exception\ValidationException' in /home/project/omeka-s/application/src/Stdlib/RdfImporter.php:118
Errors:
[]
Stack trace:
#0 /home/project/omeka-s/application/src/Stdlib/RdfImporter.php(280): Omeka\Stdlib\RdfImporter->getMembers()
#1 /home/project/omeka-s/application/src/Controller/Admin/VocabularyController.php(177): Omeka\Stdlib\RdfImporter->getDiff()
#2 /home/project/omeka-s/vendor/laminas/laminas-mvc/src/Controller/AbstractActionController.php(77): Omeka\Controller\Admin\VocabularyController->editAction()
#3 /home/project/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(321): Laminas\Mvc\Controller\AbstractActionController->onDispatch()
#4 /home/project/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(178): Laminas\EventManager\EventManager->triggerListeners()
#5 /home/project/omeka-s/vendor/laminas/laminas-mvc/src/Controller/AbstractController.php(103): Laminas\EventManager\EventManager->triggerEventUntil()
#6 /home/project/omeka-s/vendor/laminas/laminas-mvc/src/DispatchListener.php(139): Laminas\Mvc\Controller\AbstractController->dispatch()
#7 /home/project/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(321): Laminas\Mvc\DispatchListener->onDispatch()
#8 /home/project/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(178): Laminas\EventManager\EventManager->triggerListeners()
#9 /home/project/omeka-s/vendor/laminas/laminas-mvc/src/Application.php(331): Laminas\EventManager\EventManager->triggerEventUntil()
#10 /home/project/omeka-s/index.php(21): Laminas\Mvc\Application->run()
#11 {main}

[jimsafley]

It’s unusual for a vocabulary to change namespaces between versions because changes to a namespace are not backwards compatible. For example, they may look similar to our eyes, but to a machine http://erlangen-crm.org/200717/E1_CRM_Entity is not the same thing as http://erlangen-crm.org/211015/E1_CRM_Entity. Seemingly, this is why Erlang CRM has an unversioned namespace.

You have two options. First, you can import the versioned namespace as a distinct vocabulary and begin using that one, parallel to the one you already have. Second, you can edit the vocabulary’s namespace URI directly in the database to reflect either the versioned or unversioned namespace, and then update the vocabulary.

[sinanatra]

perfect thanks! it was easier to edit the db in this case