Import

1 -  Different ways of importing data: 
    1.    from RSS feeder 
    2.    filters are ready-made 
    3.    filters can be customized 
    4.    user can define more filters  
    5.    can capture bibl. references from WWW pages : download data in its own proprietary format and then import it
    6.    can import from WWW pages: direct export and import   
    7.    other 

En: no RSS; yes all the rest 2-6; as far as XML is concerned it can import only from its own EndNote's XML proprietary format
6: Many data providers offer a direct EndNote export, see at: http://www.endnote.com/endnote_export.asp
can import from Traveling library included in a MS-WORD document: once a bibliographic record is anchored to a MS-WORD document it is embedded in it, if one handles such a document without the relevant EndNote source db, he can still import the records embedded in the paper into his own db, thus recreating them, except for the Abstract, Notes and the six Custom fields which are never embedded
7: En is able to import a PDF file (or a folder of PDF files). If the PDF file contains a valid DOI (Digital Object Identifier) number, by double-checking it within the CrossRef database, EndNote should be able to extract valid bib metadata and put it in the relevant fields + attaching the PDF file

2 - Can import delimited/tabbed structured input ASCII text file (CDF, CSV, <Tab>...)

1. fixed/variable number of fields; 
2. fixed/variable fields position in different RTs; 
3. RT can be changed within the same file; 
4. multiple value fields allowed (e.g. more names in author field ...); 
5. fields contents can also spread over different lines; 
6. can define field separator; 
7. can replace delimiter if embedded in field; 
8. can define end of record
9. other 

En: yes
only tab delimited -not comma or other

1. number of fields does not need to be the same as the En RT, but in the same incoming file number is fixed in columns that may be empty;
2. position of fields in the incoming record does not need to be the same as the En RT, but must be consistent in the same file; 
3. RT cannot be changed; 
4. yes, if wrapped without <CR/LF>
5. no 
6. no
7. Special first line (or column but more complicated, see help) for *reference type.
   Second line with RT specific fields names labels according to the receiving EndNote RT;
   lines are separated by paragraph mark <CR/LF>;
   fields are separated by tabs;
   no upper/lower case conversion;
   a special "Unused" field can be used for data to be discarded

3 -  Can import ISO 2709 format

4 -  Can import MARC format file

5 -  Custom reformatting of tagged input files 

1. condition check

2. change RT

3. merge incoming fields 

4. delete/discard fields 

5. field content parsing 

6. add content to fields: text strings, punctuation...

7. tolerate fields in variable position

8. upper/lower case conversion

9. replace text

10. delete text

En: yes

• 1 to a limited extent (automatic parsing ...)
• 2 yes
• 3 yes
• 4 yes: send them to {IGNORE} fields
• 5 yes, also 'smart' parsing for names and source fields
• 7 yes
• 8 upper to: unchanged, lower, sentence, headline (on each field basis)
• 10 yes, on each individual field basis

an incoming field content can be used only once; More than one conversion pattern can be supplied for one or more fields

6 -  Import through embedded Z39.50 online connection
    1 - can modify import filters

7 - Supplied import filters