Neither the attribute nor the parents of it are invisible, either in the
importing or exporting dataset. The maxSelect field for the
AttributeCollection containing the pointer attribute was set to 0, but I
cleared that field and it didn't seem to make a difference. When I link
the datasets through the web interface, I can select the exon_name
attribute from the structure dataset and it works correctly: I can
select, say, gene_name from the gene dataset, and exon_name from the
exon dataset, and they are joined correctly. Is there something special
that needs to be done in the registry XML file to enable pointers?
--E.O. Stinson
[EMAIL PROTECTED]
Syed Haider wrote:
On Fri, 2007-02-09 at 11:31 -0500, E.O. Stinson wrote:
Hi Stinson
Hello all,
I'm running into some trouble creating pointer attributes; here's what
I've tried so far:
I have two datasets, agambiae_gene_vectorbase, and
agambiae_structure_vectorbase.
The structure dataset has "gene_id" as an exportable, and the gene
dataset has gene_id as an importable. This seems to work, as I can link
the datasets in the web-based MartView (0.5). However, when I try to add
a pointer attribute to the gene dataset, as:
internalName: exon_name
pointerDataset: agambiae_structure_vectorbase
pointerInterface: default
pointerAttribute: exon_name
...where the structure dataset contains an "exon_name" attribute, I get
a message "No visible attributes in collection link_attributes"
Could you please check your XML (through MartEditor) to see if the
attribute itself or collection isnt invisible.
cheers
syed.
when
this is the only attribute in an AttributeCollection. Is there something
obvious I'm missing? Or failing that, an example simpler than that in
the ensembl mart databases?
Thanks,
E.O. Stinson
[EMAIL PROTECTED]
