🚀 go-pugleaf

Dear Avi

Let me put in my two cents on KW.  The largest hitch that I have right now
in EndNote is KW.  I vote for having EN+ be able to pull out an index to KW
as the a feature to be included soon.  I spend a great deal of time trying
to keep track of all the KW that I use.  I usually export the keywords only
to excel and use a macro to delete the duplicates and then I print the list
out in Word.  My macro also counts the occurences of the KW (how useful is
the KW?).

As for as this idea of Hierarchy. . . A KW may fit in several places in a
tree structure.  Cat may be a mammal, but it could be four-legged too,
whereas a host of other mammals may not be.  If I look under four legged
animals will I not see cats because it's under mammals?  

One of the blessings/curse of EN+ as viewed as a database manager is that
it is specialized.  Very Capable, but specialized.  I might suggest not
making the keyword too fancy on the first excursion.  Have a KW window
float off to the side or be a pop-up window.  Have it be a simple a to z
list that works just like the main EN window--that is, if you highlight one
item you can scroll up and down.  You can highlight more than one by shift
highlighting.  You can copy fromthe list and paste into the KW field.  Or
even have a little "Insert Keywords" command.  I DO RECOMMEND a tiny button
at the bottom of the Keyword window that jumps the user to a ADD/MODIFY
window.  (4thD list windows work like this)

This floating window containing KW would essentially work the same as the
Journals file.  It would be simpler because it would only have one column
of info.  People with existing lists could build a KW file just the same as
they would build a tab delimited Journals file saving it as text.




On a separate note, I would like to ask about importing capabilities.  I
find the importing limited by the fact that whatever import filter you use,
requires some sort of tagging.  It would be nice to be able to edit what
tags are read and most of all, I would appreciate being able to import
tables of data that are not tagged at all.  It's difficult to export an EN
database to 4th D and then back again.  (Not your fault, 4th D doesn't use
tags, very few of your customers probably actually do this)  The reason I
also use 4th D is it would allow major house cleaning like capatalizing all
the entires in a field, etc, and other esoteric duties. . . . . . The point
is, I would liek to be able to import untagged tables.

Thanks

Fur

furr@u.washington.edu