4.8. Import

Import

A -  Different ways of importing data:
    1    direct copy of records (write from database to database) 
    2    batch import via reformatting filters  
    3    filters are ready-made 
    4    existing filters can be customized
    5    user can define more filters 
    6    can capture an html WWW page and transform it into a db record
    7    can capture bibl. references from WWW pages (either download data in its own proprietary format and  import, or convert it on the fly) 
    8   from RSS feeder 
    9   XML
  10   other

Different ways of importing data 1 2 3 4 5 6 7 8 9 10
EndNote Web x x x (x) (x) [x]
RefWorks (x) x x x x x x
ProCite x x x x x x x
EndNote x x x x x x [x] x
Reference Manager x x x x x x [x] x
RefWorks (web based) Procite EndNote Reference Manager
Import  Import  Import  Import  Import 
EW: 2; 3; 4-5: cannot modify them directly: must do it within EndNote desktop and the Administrator can upload them; 7: actually a "Capture" feature does exist, as a plug-in for browsers' toolbar, but the results were extremely poor (only a couple of fields captured in a cluttered way)

RW:
1 from folder to folder;
2 yes
3 yes
4 no, unmodifiable filters:  canned and invisible* ;
5 no, cannot create more*;
6 via RefGrab-It plugin; 
7 from many sources;
8 direct import from RSS feeders: transform them into RefWorks records that can import into the database
10 can import files exported  from various bibliographic packages  

* to create a new filter you must ask and make a suggestion to the producer

Pr: 1 copy and drag-and-drop; 2, 3, 4, requires separate application program: BiblioLink; 5, 6, 7

En: 1 copy and drag-and-drop 2, 3, 4, 5, 7 yes Windows  (Scholar Google included) (for Mac see Other features);  9 can import only from its own EndNote's XML proprietary format
10 can import from Traveling library included in a MS-WORD document: once anchored to a MS-WORD document a bibliographic record is embedded in it, if one handles such a document without the relevant source EndNote db, he can still import those 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

RM: 1, 2, 3, 4 modify and save under different name 5 7 9 can import only from RM and EndNote XML proprietary format
10 can import from Traveling library included in a MS-WORD document: once anchored to a MS-WORD document a bibliographic record is embedded in it, if one handles such a document without the relevant source EndNote db, he can still import those records embedded in the paper into his own db,  thus recreating them except for the Abstract and Notes fields (the 5 Custom fields can be embedded);
can automatically convert ProCite and EndNote files. BookWhere, ISI Current Contents, ISI Web of Science can directly write data to an RM database; directly reads downloaded files from several different hosts

B - Can import delimited/tabbed stuctured input ASCII text file 

 [more specific features that could be taken into account: fixed/variable number of fields; fixed/variable fields position in different RTs;  RT can be changed; multiple value fields allowed (e.g. more names in author field ...); fields contents can also spread over different lines; can define field separator; can replace delimiter if embedded in field; can define end of record]
EW: tab delimited, must follow special instructions given by the help RW: no Pr: yes
fixed or variable number of fields ( RT; RN; plus all 45 fields or only workform related); fixed position of fields;RT cannot be changed, must be present as the first field or last used in data entry be assumed by default; multiple value fields allowed, if separated by // / or ; in name field; fields content can spread over more than one line; can define field separator; can replace delimiter if embedded in field contents; can define end-of-record
En: yes
tabbed where number of fields and their position can vary: Tab delimited: special first line for reference type and second with fields names labels according to the receiving EndNote RT; no fixed position required; recognizes multiple authors; RT can be changed and multiple value fields are allowed
RM: yes

must use only one destination field defined as "Source" with subfields and its parsing option;  number and position of fields can vary according to the specified RT; more than one RT can be defined;  multiple value fields allowed;  fields content can spread over more than one line; can define field separator; can replace delimiter if embedded in field contents;  can define end-of-record

C -  Can import alpha/numeric data from a spreadsheet

EW: tab delimited, see above RW: it can import from MS Excel via data manipulation : data has to be transformed into RW native tagged format Pr: yes as long as it is a comma/tab delimeted structured file En: yes as long as it is a tab delimited or tagged structured file, see above 2 RM: yes, see above delimited/tabbed

D -  Can import ISO 2709 format

EW: no RW: no Pr: no En: no RM: no

E -  Can import MARC format file

EW: yes, via Z39.50 from many library catalogs servers (a few filters RW: yes (pre-defined filters for: DANMARC, MARC21, UNIMARC); filters are also available to import via Z39.50 from MARC records servers such as library catalogs Pr: one has to create its own filter for a tagged MARC format (without leader and directory and each field on a different line), alternatively, download records through Z39.50 online connection and MARC tagged modifiable filters (limited options to handle subfields in names) En: one has to create its own filter for a tagged MARC format (without leader and directory, each field on a different line), then a series of specific options for handling MARC tagged records is provided (e.g. subfields to a limited extent ...); alternatively download records through Z39.50 online connection and tagged MARC filters, already made and modifiable (limited options to handle subfields in names) RM: filters for tagged MARC records are available -others can be created, e.g. for UNIMARC as well- to download and import records through Z39.50 online connection

it is really difficult to deal with embedded subfields codes

F -  Custom reformatting of tagged structured input ASCII text files:
   1 condition check
   2 change RT
   3 merge fields
   4 delete/discard fields
   5 field content parsing
   6 add field content, text strings, punctuation 
   7 tolerate fields in variable position
   8 upper/lower case conversion
   9 replace text

Custom Reformatting 1 2 3 4 5 6 7 8 9
EndNote Web
RefWorks canned
Procite (x) x x x x x x x
EndNote x x x x x x x
Reference Manager x x x x x x x x x
EW: filters as offered are canned and certainly perform some of these tasks; to modify them must do it within EndNote desktop and the EW Administrator can upload them;
as per what EndNote desktop can do with filters see here En 

RW: filters are canned and users do not have access to them;
they clearly perform some of these tasks out of user's control
Pr: 1 only: "when using workform [X], do not transfer field(s) ..." (field mapping depending on RT); 2; 3; 4; 5; 7; 8; 9 En: 2; 3; 4; 5; 6 no ; 7; 8 (any field); 9 only omitting strings for each single field RM: 1 to replace text or not; 2; 3; 4; 5 (seven predefined patterns: author, periodical, date etc.: Source field lets indicate delimiters, also commas and tabs); 6 (four keywords + date stamping --settings are not at the filter level but in the import window); 7; 8 (also Casing Term Dictionary); 9; also "Periodical term Dictionary" for terms without periods in abbreviated titles that are not abbreviated words

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

EW: yes, but cannot modify them directly: must do it within EndNote desktop and the Administrator can upload them RW: yes, can import data, users can create basic connection files;
1: no, you cannot modify filters: make suggestions to the producer to do it
Pr: yes (via incorporated subset of BookWhere® client); 1: yes En: yes (via incorporated proprietary toolkit, Yaz client ® based);
1: yes
RM: yes (via incorporated subset of BookWhere® client);
1 yes

I - Supplied import filters

EW: 671 RW: ca 1090 shipped (cannot create more, see above) Pr: hundreds + others definable via Biblio-Link + direct export from several databases En630 + can define others with no limitations: each is a separate file emedding a data conversion table RM: some 430 shipped (can create more with no limitations, via IFE Import Field Editor)
RefWorks (web based) Procite EndNote Reference Manager
Import  Import  Import  Import  Import 

Table of contents  | Index