[base] annotation importer suggestion

2008-04-11 Thread Bob MacCallum

Hi,

Would it be possible for the annotation importer plugin to be modified to
offer three options for item not found error handling:

  skip
  fail
  create

instead of the current skip/fail only?

(or have I missed something? [always worth adding this disclaimer!])

when importing biosources, this would save a lot of GUI work
(prior to the MAGE-TAB importer being completed)

I could imagine project defaults would be suitable for some of the item
attributes, otherwise they could be empty of course.

many thanks,

Bob.

-- 
Bob MacCallum | VectorBase Developer | Kafatos/Christophides Groups |
Division of Cell and Molecular Biology | Imperial College London |
Phone +442075941945 | Email [EMAIL PROTECTED]

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject unsubscribe to
[EMAIL PROTECTED]


Re: [base] annotation importer suggestion

2008-04-11 Thread Nicklas Nordborg
Bob MacCallum wrote:
 Hi,
 
 Would it be possible for the annotation importer plugin to be modified to
 offer three options for item not found error handling:
 
   skip
   fail
   create
 
 instead of the current skip/fail only?

It would be possible, but The hard part is that all items are 
created differently. Some properties are optional, some are not. For 
some it may be possible to automatically select sensible default values, 
  but for others user input is required. Some properties can maybe be 
mapped to columns in the file.

 (or have I missed something? [always worth adding this disclaimer!])
 
 when importing biosources, this would save a lot of GUI work
 (prior to the MAGE-TAB importer being completed)

I guess this is one of the simple cases that would not be very hard to 
implement. Harder cases would be LabeledExtract (which requires a 
Label), PluginDefinition (which requires a plug-in JAR file).

I think a special piece of code is more or less required for every type 
of item and in some cases, like the PluginDefinition, it will not be 
possible to have a 'create' option at all.

So, in principle it is possibly to have a 'create' option, but all cases 
are special cases and require special code. I guess this falls under the 
'contributions are welcome' paragraph.

/Nicklas


-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
The BASE general discussion mailing list
basedb-users@lists.sourceforge.net
unsubscribe: send a mail with subject unsubscribe to
[EMAIL PROTECTED]