Dear Darren,
that’s indeed a nice feature to implement.
I’ll tell you what you can do now, which can spare you some time, but it’s an hack and requires to access the file system. Also, this info should be correct, but…pls take the time to play a little with it and check that everything is correct.
Basically, in the SemanticTurkeyData directory, sibling to semanticturkey-x.y, go inside the projects folder and make a copy of one project…then…
…then there are two aspects to cover: data and project configuration.
DATA
If the project’s data is in a local repository, that should be enough: the copy of the directory you made already contains a copy of the data.
If the project’s data is in a remote repository, then you need to either export the data as you used to do and then reload it through VB, or you make a copy of the repo through GDB somehow and then you make the project point to this new repo (see next section). For the name of the repo, I suggest to use a repository’s name that is consistent with the default pattern applied to the repository name based on the project name (i.e. <PROJECTNAME>_CORE )
PROJECT
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/c2f91c90-f7a9-4159-bf80-316fca5a5c2dn%40googlegroups.com.
Thanks to you Darren for the feedback,
I put it on the todo list for future roadmaps to be filled. Indeed it’s a useful feature, we simply never covered it because, in order to cover all possible cases automatically, it would not be as trivial as it might seem and then we always had other priorities taking precedence,
Kind Regards,
Armando
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/6b32e190-4f0a-4c5b-a7ea-dbef6f04c001n%40googlegroups.com.