Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Tania Tudorache <tudorache at stanford.edu>: Re: Question about query export

tudorache at stanford.edu tudorache at stanford.edu
Fri Jul 11 11:34:49 PDT 2008


Dies ist eine Benachrichtigung des E-Mail-Servers von faktorM. · Mensch im
Unternehmen.

Folgende E-Mail ist eingetroffen:

  Absender:     Tania Tudorache <tudorache at stanford.edu>
  Betreff:      Re: [protege-discussion] Question about query export
  Organisation: Biomedical Informatics Research
  Empfänger:    protege-discussion at mailman.stanford.edu
  Kopieliste:   [keine Angabe]
  Gesendet:     Freitag, 11. Juli 2008, 11:13:18 Uhr -0700
  Anhang:       "protege.jar"

clamav found malware: Zip.ExceededFilesLimit FOUND; Gefährlicher Anhang
gefunden: "protege.jar"; Dateityp: Executable Jar File. Dieser Dateityp wird
von den Sicherheitsrichtlinien nicht zugelassen. Die Datei wird
ausgeblendet. Bitte wenden Sie sich innerhalb der nächsten 90 Tage an Ihren
Administrator, falls Sie sie benötigen! (mailto:administrator at faktorm.de)

Vollständiger Nachrichtentext in reduzierter Formatierung:

Hi Nafiye,

Nafiye Talas wrote:
> Hi Tania and Jonathan,
>  
> I also tried those delimiters (?, |, "", ^, ~) but unfortunatelly it 
> does not change the 2 issues that are in the CSV file.
> So indeed like Jonathan says the export is still separating fields by 
> the ',' and <enter>.

I find this hard to believe. I've tested this yesterday and it works 
fine. Do you mean that the file produced by protege has the wrong 
delimiters, or that when you import it in Excel, you get the wrong split 
in columns? I don't think it is the case with the former, but with the 
latter, you need to configure Excel to use other delimiters when it 
imports the file. You should also try to open the file in a text editor 
(not in eclipse), to see exactly what is being exported.

Please note also that there are two delimiters: one is for the slot 
values (which you would want to have in the same coulumn, and which 
defaults to ","), and one is for different slots (which defaults to "\t" 
and should be exported to different columns).

>  
> If you can send me the jar file that would be great.

I've attached the jar.

>  
> I hope that this new jar will solve the problem. Since it is not 
> desirable to replace all the comma's ',' and <enter>
> in all the instances.
No, definitely. But, you should use other delimiters instead of "," for 
the slot values when you export.

Tania

>
> Thanks both for the quick reply.
>  
> Nafiye
>  
>
----------------------------------------------------------------------------=
------------------------
>  
> Hi Nafiye,
>
> We have fixed this problem for the next beta release. If you need it
> earlier, I can send you a jar.
>
> The new version of *export* will quote all new lines with double quotes
> and it will quote all double quotes with double quotes :) If this makes
> sense.. The idea is that Open Office Spreadsheet and Microsoft Excel
> understand this quotations and will import the data correctly.
>
> As for the slot value delimiter, Jonathan's advice is good: try to use a
> delimiter that is not used in your values. E.g. use "|".
>
> Tania
>
> Jonathan Carter wrote:
> > Hi Nafiye,
> >
> > Almost a classic data *export* problem - I had something similar when
> > importing text that had been entered manually in a recent project.
> > I'd like to clarify what's going on.
> > Even if you set the delimiters to something like '|' [pipe] and '~',
> > the *export* is still separating fields by the ',' and <enter>?
> >
> > If you can, I'd recommend using delimiters that are not likely to
> > appear in the text that your users have produced. You can then use
> > these as the delimiters in Excel perhaps (?) or do a quick search and
> > replace on them in the CSV before importing to Excel. The other thing
> > you'd need to do before that is to replace all the ',' and <enter>
> > that users have inputted with something else otherwise Excel will get
> > confused as to what's a separator and what is cell content.
> >
> > It's a tricky one, as the whole point of a CSV file is that the values
> > are separated by commas.
> > Have you tried using '"' (that's double quotes) as the slot delimiter?
> > In an attempt to escape the value of each slot?
> >
> > Jonathan
> >
> > __________________________________________
> > Jonathan Carter - Head of Technical Architecture
> > Enterprise Architecture Solutions Ltd
> >
> > Assess your EA maturity at:
> > _www.enterprise-architecture.com/EAvaluator_ 
> <http://www.enterprise-architecture.com/EAvaluator>
> > <_http://www.enterprise-architecture.com/EAvaluator_>
> > __________________________________________
> >
> > On 10 Jul 2008, at 16:05, Nafiye Talas wrote:
> >
> >> Dear Community,
> >> 
> >> I'm using the *export* functionality within the *query* tab.
> >> And I'm bumping into problems:
> >> 
> >> 1. when a user entered a text with a comma ',' the text after the
> >> comma is put in a seperate field in excel
> >> 2. when a user entered a text with an <enter> the text after the
> >> enter is also put in a seperate field.
> >> 
> >> I tried a lot of different delimiter values but it no effect on the
> >> *export* file.
> >> 
> >> I will attach a picture of the *export* values, the instance and the
> >> *export*ed file.
> >> 
> >> Thanks in advance for any help.
> >> 
> >> Nafiye Talas
>
>
> ------------------------------------------------------------------------
> Lees jij al je Hotmail op je mobiel? Probeer het nu! 
> <http://windowslivemobile.msn.com/BrowserServiceHotmail.aspx?lang=nl-nl>
> ------------------------------------------------------------------------
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
http://protege.stanford.edu/doc/faq.html#01a.03 
>   


_______________________________________________
protege-discussion mailing list
protege-discussion at lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing:
http://protege.stanford.edu/doc/faq.html#01a.03 




More information about the protege-discussion mailing list