 |
Welcome to the EMuUsers discussion forums. All registered users are
encouraged to post new topics and also to participate in existing
discussions.
* You must register first if you wish to make postings.
* You can subscribe to one or more forums to receive email notification when new messages are posted.
* Click on a correspondent’s name to find out their title and institution.
|
| Author |
Messages |
|
Mark Pajak
Posts:6
 |
| 10-12-2009 2:54 AM |
 Alert
|
Hi,
Having recenty aquired EMu and imported all data from our natural history collections I am beggining to come to terms with the full functionality of the Taxonomy module. I would like to know how useful other people find the parent-child relationships within the module?
Our data has been migrated with no parent attachment links so they would all need creating from scratch, and I guess a record created for each higher rank, such as Phylum: Arthropoda. This could quite possibily take forever, (unless the appropriate import file can be created), given the amount of fields, so I would like to know what is accomplished by having such a structure to the data, when the fields in the higher classification tab are already populated and searchable - does this make sense?
Although our collections are moderately large they are not regularly accessed by taxonomists and identification to species is not always possible (or perhaps even necessary). Is there any enhanced functionality in terms of web access that can be gained by building the hierarchy?
Also I currently have all tabs turned on, as is the default. What is the simplest way of making the module more user friendly, i.e. hiding tabs when they are not needed. I think I am going to reduce the tab visibility quite a bit but I do not want to hide something that turns out to be vital.
Thanks
Mark
Bristol Museum
England |
|
------------------------------------------------------------------------
Mark Pajak |
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.6
|
|
 |