Skip to Content.
Sympa Menu

pcplantdb - Re: [pcplantdb] a few things...

pcplantdb@lists.ibiblio.org

Subject: pcplantdb

List archive

Chronological Thread  
  • From: Bear Kaufmann <bear@ursine-design.com>
  • To: john@eco-living.net, pcplantdb <pcplantdb@lists.ibiblio.org>
  • Subject: Re: [pcplantdb] a few things...
  • Date: Sat, 30 Jul 2005 16:42:33 -0700

Not sure exactly what you mean by regroup...we may have entirely different
understandings of this...I'll give a few examples of what I mean.
As a starting point, I'm thinking that many of the current values in the database can map to either input or output.
At a simpler level (with no real connection to the backend code) just reorganize the values in advanced search into inputs/outputs, to get this idea across to the user. Later on, the backend can implement input-output connection, etc.

In advanced search right now, if I search on Plant Uses for 'timber' or
'fodder' I get zero results (all other fields empty).
This I assume is because there are no plants that indicate fodder or
timber uses in the current data set.
Just installed the DB table, and searched for unique values (Chad, I'm thinking uses_index shouldn't use a varchar for use, but an integer, related to the uses_glossary).
Here are the unique values (all 270):
Abortifacient, Acrid, Adaptogen, Adhesive, Alcohol, Alterative, Anaesthetic, Analgesic, Anaphrodisiac, Anodyne, Antacid, Anthelmintic, Antiaphonic, Antiarthritic, Antiasthmatic, Antibacterial, Antibilious, Antibiotic, Anticholesterolemic, Anticoagulant, Antidandruff, Antidermatosic, Antidote, Antiecchymotic, Antiemetic, Antifungal, Antihaemorrhoidal, Antihalitosis, Antihydrotic, Antiinflammatory, Antiperiodic, Antiphlogistic, Antipruritic, Antipyretic, Antirheumatic, Antiscorbutic, Antiscrophulatic, Antiseptic, Antispasmodic, Antitumor, Antitussive, Antivinous, Antiviral, Aperient, Aphrodisiac, Appetizer, Aromatherapy, Aromatic, Astringent, Baby care, Bach, Balsamic, Basketry, Beads, Bedding, Besom, Biomass, Birthing aid, Bitter, Blood purifier, Blood tonic, Blotting paper, Bottles, Broom, Brush, Buttons, Cancer, Cardiac, Cardiotonic, Carminative, Cathartic, Charcoal, Chocolate, Cholagogue, Cleanser, Coffee, Colouring, Compost, Condiment, Containers, Contraceptive, Cork, Cosmetic, Cotton wool, Curdling agent, Cytostatic, Cytotoxic, Darning ball, Decongestant, Demulcent, Deobstruent, Deodorant, Depurative, Detergent, Diaphoretic, Digestive, Disinfectant, Diuretic, Drink, Dye, Egg, Emetic, Emmenagogue, Emollient, Enuresis, Errhine, Essential, Expectorant, Febrifuge, Fencing, Fertilizer, Fibre, Filter, Fire retardant, Flowers, Foot care, Friction sticks, Fruit, Fruit ripening, Fuel, Fungicide, Furniture, Galactofuge, Galactogogue, Gelatine, Green manure, Ground cover, Gum, Haemolytic, Haemostatic, Hair, Hallucinogenic, Hedge, Hepatic, Herbicide, Homeopathy, Hydrogogue, Hypnotic, Hypoglycaemic, Hypotensive, Incense, Infertility, Ink, Inner bark, Insecticide, Insulation, Irritant, Kidney, Kindling, Lacquer, Latex, Laxative, Leather, Leaves, Lenitive, Lighting, Lining, Liquid feed, Lithontripic, Litmus, Manna, Microscope, Milk, Miscellany, Mordant, Mouthwash, Mulch, Musical, Mydriatic, Nails, Narcotic, Nectar, Needles, Nervine, Nutritive, Odontalgic, Oil, Ophthalmic, Oxytoxic, Packing, Paint, Paper, Parasiticide, Pectin, Pectoral, Pencil, Pins, Pioneer, Pipes, Pitch, Plant breeding, Plant support, Plaster, Polish, Pollen, Pollution, Porcelain, Pot-pourri, Potash, Poultice, Preservative, Purgative, Raffia, Refrigerant, Repellent, Resin, Resolvent, Restorative, Roofing, Root, Rooting hormone, Rootstock, Rubefacient, Rust, Rutin, Salt, Salve, Sandpaper, Sap, Scourer, Sedative, Seed, Seedpod, Shelterbelt, Sialagogue, Size, Skin, Soap, Soap making, Soil conditioner, Soil reclamation, Soil stabilization, Stabilizer, Starch, Stem, Sternutatory, Stimulant, Stings, Stomachic, Straw, Strewing, String, Stuffing, Styptic, Sweetener, Tannin, TB, Tea, Teeth, Thatching, Tinder, Tonic, Uterine tonic, Varnish, Vasoconstrictor, Vasodilator, VD, Vermifuge, Vesicant, Vulnerary, Warts, Waterproofing, Wax, Waxed paper, Weather forecasting, Weather protection, Weaving, Wick, Women's complaints, Wood.

I'm surprised not to see fodder in there. You might also try Wood. I think we need a better UI system then a text box. The list is long, but it is a limited set of values, so we should show them to people. Perhaps a Select Box, or break them into categories...Medical, Food, Animals, Functional...


I would want to be able to search on 'termite resistant timber' and 'goat
fodder', as more sophisticated examples.
Probably wouldn't work, but Wood + Insectide..?

I would also want to be able to enter such info when adding a plant or
adding info to an existing plant, as 'outputs'.
If I do advanced search on plant uses for 'tonic' I get 600+ results.
In the summary text that is returned, and in the references linked in the
summary text, I do not find any information on use of the plant as a tonic
(of whatever sort).
I admit I only checked the first three result items. However if it were
visible anywhere I would assume it would be in the top results for sure.
So what is up with this??
If I search on plant uses for 'tonic' and get results, I expect to see
info on use as tonic in the result data...??
Is this because we are only returning some kind of limited summary thus
far, that does not necessarily include the actual info asked for?
Or...what??
Good comments John. I haven't added any bugs recently, but we should keep track of these things there. (Anyone care to add some).
Sooo...apparently, filling in most values in the current advanced search returns the plants themselves, with their summary description. If you say, fill in tonic under the comments text box, you are taken to the comments that mention tonic. Honestly this isn't very user friendly. I think the so called "comments" should remain pretty tightly bundled to the parent (plant). Ideally, the term would get highlighted, and the comment cut down to size around the search word. As in my previous mockup, a comment should should what plant it's from too, otherwise the user has no idea, what it relates too, unless the user clicks "View Parent"..I'd prefer the link to the comment just be a link to the parent's (plant) view page, with an anchor that brings the user to that comment.
Note that the simple search does mix comments/plants, and searching for tonic there does show comments that match.
Recommended change: Comments show what plant they are for. Short summary text doesn't start from the beginning, but is centered around the search term(s). Link to comment actually links to plant view, with anchor (ie view?plantid=203943#comment239903).

Cheers,
Bear





Archive powered by MHonArc 2.6.24.

Top of Page