On 4/04/2019 7:39 am, Rob Atkinson wrote:
yes i know the "all graphs" snapshot, but i need to have a much more
modular approach where applications bring in a number of relevant
modules - like your product views - there will be a set of "product"
modules, a configuration, then a set of data ingested from external
systems, then a set of data managed under EDG workflows. They all need
to be persisted differently.
I havent unpacked the DASH stuff yet beyond a couple of examples
running inside TBC - this is where a CI (continuous integration with
test cases for regression testing) implementation guide would be
appropriate IMHO.
I have build a loading harness using TTL - but its challenging because
there is no easily accessible documentation about the contracts behind
each project type - for example needing to define a base class.
Enumerations dont work in 6.2 unless you import a EnumerationsType
etc. At the moment I have to guess all these requirements by creating
things manually and looking at the imports used by exporting. (Is
there a shape definition for all the requirement per project type -
and if so a process to define your own project types with its own
shapes definition. (i.,e. EDG uses introspection to list available
services (nice, but hidden away a bit) - is there an equivalent for
the data architecture?)
No sorry, this requires some plumbing as you have noticed. On the plus
side, it's all model-driven, and you can see which triples you need from
the TCH graphs etc.
Holger
rob
On Wednesday, 3 April 2019 19:59:54 UTC+11, Holger Knublauch wrote:
Hi Rob,
assuming you are keeping your TTL-based graphs (e.g. SWP files) in
your own projects that can be zipped and shared using project
upload. We do have some basic support for taking snapshots of all
graphs under teamwork control using the admin feature "Create
Snapshot of EDG (e.g., for testing)", and its sibling "Restore
Snapshot of EDG". Have you tried those or what would be missing?
They operate on quad files.
(FWIW the DASH test case framework uses a similar notion of
"environments" and tests can switch between such environments when
needed, by switching to a temp workspace).
The usual warnings apply - these features are quite ambitious and
would of course not scale to all sizes of data, neither have they
been used much yet.
Holger
On 3/04/2019 8:45 am, Rob Atkinson wrote:
+1 for removing samples by default
but wondering if there are other options for managing default
project inclusion
I havent yet played with automated build and testing, but lets
say I have followed some good practices in software design and
factored out common capabilities, domain specific configurations
and app specific functionality and configuration - so will have
say half a dozen modules managed as separate projects in a
complex app that all need to be installed... I will also have
test cases and production data environments to install.
ideally there is a way of programattically creating a workspace
so i can set up an instance of EDG for testing - does such a
thing exist?
in the short term, the "add projects from File system" function
has several painful defaults - is there a way to control these:
1) it persists in turning on auto-search for projects - so you
have to uncheck two boxes manually Every. Single. $#%^$#^!. Time
2) it never remembers where you have been - so you need to type
the same variations in again, and again.
Also is there a way to save a state of EDG into a project -
specifically the things I would want to do are to have a project
load read-only Ontology and Reference Data Asset Collections for
models that are related to the functionality in the project.
Presumably the installation of Samples project now does this -
but when I tried moving just moving repositories to a specific
project it didnt find them, so is there some trick to this?
RA
--
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
