On 16 Jan 2007, at 14:56, David Croft wrote:
Hi Arek,
by adding an importable to your dataset - you will be able
to query your dataset on your site with other peoples' data
(you 'imported' somebody's data)
by adding exportable to your dataset you make possible
for other people to query your data on their site in the context
of their data (you 'exported' your data to other people)
OK. So does that mean that I am right, i.e. the starting dataset
in a link needs an importable, the end dataset of the link needs
a corresponding exportable?
depends on what you mean by 'starting dataset' ;-)
as this means different things in the context of MView
and in the context of the actual query logic.
However, the simplest way to think about it is as follows:
In MView:
choose dataset A (your own data)
in order for this dataset to have a drop down of some other external
linked datasets (eg B, C)
external dataset B, C need to have some exportables (you need to check
what they have to offer)
and the dataset A needs an importable (you need to create it)
typically you are mostly concerned with importables on your own dataset
as these bring other data in (ei create a MView dropdown of linked
external datasets to your own dataset)
so you tend to scan external datasets for exportable(s) and create
matching
importables(s) on your own dataset
not sure if this helps :)
a.
Cheers,
David.
------------------------------------------------------------------------
-------
Arek Kasprzyk
EMBL-European Bioinformatics Institute.
Wellcome Trust Genome Campus, Hinxton,
Cambridge CB10 1SD, UK.
Tel: +44-(0)1223-494606
Fax: +44-(0)1223-494468
------------------------------------------------------------------------
-------
