RE: [Soaplab-users] "Allowed values" in metadata

[Marc L. <Mar...@DE...>]

> >    The way how to define is the same as for emboss=20
> appliactions. You=20
> > use standard ACD keys for that. For example:
> >=20
> >   values: "20;30;40;50;60;70;80;90;100;110;120;130;140;150"
> >=20
> > will give you allowed values: 20, 30, 40, 50, 60, 70, 80, 90, 100,=20
> > 110, 120, 130, 140, 150. But you have also to say:
> >   min: 1
> >   max: 1
> >=20
> Do you have to set the min and max also for strings ? In my=20
> case, the parameter is of type 'string'.
> Actually, I tried it before, in the way you suggest, except=20
> using a comma instead of a semi colon. But I also added=20
> "delimiter =3D ','" to indicate that.
> Unfortunately I will not be able to test your suggestion immediately.
> I'am stuck in a meating for a whole day. Yikes :-( I'll come=20
> back to you as soon as I've done a few tests.

Wait!
The attributes you mention ("values","minimum" and "maximum") are only
valid for the types "list" and "selection". I was talking about a
parameter of type "string".
Just like you have e.g. the sformat parameter in EMBOSS applications,
which is also of type "string" (at least according to the metadata you
get when you run 'run/run-analysis -name edit.seqret -ii'). According to
ACDParser.pm these attributes are not valid to type "string".
For that reason (see my previous mails) I was trying my luck with
general attributes like "valid" and "expected".

Marc