Jari Häkkinen wrote:
> I have not encountered any problems with attaching files earlier. I
> decided to play around with partially filled import files. I succeeded
> in creating a file that fails to attach files even though the importer
> reports success. BASE 2.8.4 and my 2.9pre test version bo
I have not encountered any problems with attaching files earlier. I
decided to play around with partially filled import files. I succeeded
in creating a file that fails to attach files even though the importer
reports success. BASE 2.8.4 and my 2.9pre test version both fails but
the resolution
No, still no joy.
> Are the raw data files "visible" to the plug-in? If you upload the
> files
> with ftp they are not automatically assigned to a project.
I uploaded them with HTTP, and they have definitely been assigned to the
project.
> You need to
> set the parameter defining how the plug-i
> It may actually be a little easier to first use the auto-inherit
> function even if you get duplicates. That is because you can then use
> the "Experiment overview" to see all duplicates and there are
> "quick-links" to access the annotations/inherited annotations dialog for
> all item
Are the raw data files "visible" to the plug-in? If you upload the files
with ftp they are not automatically assigned to a project. You need to
set the parameter defining how the plug-in should find existing items
referenced in the file. If this is not the problem, can you try to only
map the f
Bob MacCallum wrote:
> >
> > > We have to inherit from just one of the two biosources because BASE
> > > doesn't know which is experimental (ch1) and which is control (ch2).
> > > BASE will later choose one arbitrarily (in Experiment Explorer for
> > > example).
> >
> > No, this was a bug
Nicklas Nordborg writes:
> Bob MacCallum wrote:
> > For two colour designs, we usually only inherit from the "experimental"
> > biosource. (Explanation: an experimental samples might be annotated as
> > "Infected with E. coli", "Infected with S. aureus" and so on, and the
> > control
> > s
Bob MacCallum wrote:
> > > Also: the only reason I am trying to do things this way is because it
> > > seems the only way to automate annotation of raw bioassays, but
> > > technically they should really inherit their annotations from the
> > > appropriate entity upstream (e.g. BioSources). Is
Hello again,
I can't get the raw bioassay batch importer to attach actual file
objects to the raw bioassays I am importing. I have
- provided a data column with file names in my data batch import file
- mapped this column to the File property in the import config
- provided a path to the data dir
> > Also: the only reason I am trying to do things this way is because it
> > seems the only way to automate annotation of raw bioassays, but
> > technically they should really inherit their annotations from the
> > appropriate entity upstream (e.g. BioSources). Is there any means of
> > "bat
Micha Bayer wrote:
> Hi,
>
> When configuring the mass annotation importer plugin, an error is thrown
> when one has mapped only the names of the raw bioassays, and not their
> ID:
>
> "A mapping for either 'Name' or 'Internal ID' must be given. "
>
> This happens even when the mapping for the n
Hi,
When configuring the mass annotation importer plugin, an error is thrown
when one has mapped only the names of the raw bioassays, and not their
ID:
"A mapping for either 'Name' or 'Internal ID' must be given. "
This happens even when the mapping for the name has already been
provided.
When
12 matches
Mail list logo
