On 19/10/2018 2:55 PM, Rob Atkinson wrote:
Specifically I want to install a set of empty asset collections from
read-only template projects, installed as writable ontologies that
automated transactions will store metadata in.
I also need to make an extended set of foundation ontologies
Specifically I want to install a set of empty asset collections from
read-only template projects, installed as writable ontologies that
automated transactions will store metadata in.
I also need to make an extended set of foundation ontologies available. (
AFAICT they need to be registered
> On Oct 18, 2018, at 11:16 PM, Rob Atkinson wrote:
>
>
> If i factor out the project and close the "data project" all works OK - but
> if i open the project in the IDE then EDG includes all the data in the scan.
> Looking forward to the fix for this :-)
>
> As it happens I've been trying
On 19/10/2018 1:16 PM, Rob Atkinson wrote:
If i factor out the project and close the "data project" all works OK
- but if i open the project in the IDE then EDG includes all the data
in the scan. Looking forward to the fix for this :-)
As it happens I've been trying to get a handle on how
If i factor out the project and close the "data project" all works OK - but
if i open the project in the IDE then EDG includes all the data in the
scan. Looking forward to the fix for this :-)
As it happens I've been trying to get a handle on how EDG, projects and the
IDE interact.
We know
The notion of projects is typically not meaningful for EDG users, but rather to
TBC users. I do agree the list is often too long though. Maybe a second column
with namespaces (graph URIs) would help?
Sent from my iPad
> On 18 Oct 2018, at 16:57, Rob Atkinson wrote:
>
>
> also - I think the
also - I think the includes dialog should not list everything anyway - its
very messy and difficult to use - better to show projects - and then let
the user dive into a specific project (ideally remember the last project
selected and open it by default?)
On Thursday, 18 October 2018 09:54:28