Dear Miel,
Yes the normal setting (and indeed the only canonical one) is that they have separated ST instances. They are simply two different platforms that share a common technology.
Indeed, mostly for practical reasons (e.g. you want to have a DEMO pack on your laptop with both systems and you don’t want to setup different projects for them with the same content) you can use them both on the same ST instance. We did not produce any doc about this to avoid confusing users.
Long story short:
That should be enough. I don’t think that, conversely, VB has any particular setting that are not setup by ShowVoc at its first start.
Pls consider this a small hack but for demoing only, it’s not a production-wise solution :-)
Kind Regards,
Armando
--
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 on the web visit
https://groups.google.com/d/msgid/vocbench-user/aaf6cd2f-5e42-43eb-a74f-a4d8a5a215b5n%40googlegroups.com.
Hi Miel,
technically you can always do, by pointing to the same GDB/RDF4J repository stored with VB (select “ExistingRemote” on the configuration for a new Dataset in ShowVoc). However, the purpose of a publication environment separated from production was exactly that: dump a version and load it into a separate store exactly for publication, while the one in VB keeps being edited and evolved.
Then, if it is a separate store cause you want to be 100% sure that, for instance, an issue in the store on your production environment does not break your publication environment, or if it is just a separate repo on your same triple store, it’s a matter of choice.
Kind Regards,
Armando
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/8a4a6ad4-4b28-4536-8d0a-eb180e2ea52bn%40googlegroups.com.