Marked!

Dave one more and one correction:
Amorphophallus parent: Voodoo Plant (Amorphophallus)

Plant Habit: Herb/Forb
Life cycle: Perennial
Flower Form: Spadix
Toxicity: Other: All parts of plant contain calcium oxalate crystals, an irritant to the mouth and esophagus. Toxic to cats and dogs.
Propagation: Seeds: Other info: Remove seeds from berry which contains chemicals that inhibit germination.
Propagation: Other methods: Offsets
Containers: Needs excellent drainage in pots

Alocasia parent: Elephant Ears (Alocasia) (Alocasia)
Change common name to Elephant's Ear in lieu of Upright Elephant Ear

Both items are handled!

Thanks.

I'm glad this thread rose back to the surface - it may answer a question I have about multiple cultivar entries under a species.

I'm starting in the Viburnum database with common species. Arrowwood Viburnum is one, at this link.

Arrowwood Viburnum (Viburnum dentatum)

Does this entry qualify for what is being referred to as a "Parent Plant" entry? It certainly would speed up additional entries (replete with common information) if I am understanding this properly. There are about twenty more cultivars/clones to add here.

I think I understand that I can make modifications to the new entries as needed - they would just start out with the info currently listed under the "parent".

Or - is the preference to have a designated "Parent Plant" entry be for an entire genus (in this case, Viburnum)?

The intent of the parent plants is as a genus level "encyclopedic" entry with common data points, articles and other helpful information. It also serves as a place for photographs representing the diversity of a genus as well as a place to put photos which haven't been specifically identified. Dave will be along shortly to describe ways in which he can script data across multiple entries. The idea of sub level parent plants is intriguing.

Yes - after posting I went looking.

After burrowing into some of the specific databases and clicking on the general entry, I found where the "parent entry" term comes from. Helps to be an old hand around the database to understand the lingo.

OK - I guess my real question wasn't as much related to the parent entry (since Viburnum has its own already) as it is to more rapid ways to enter common data across multiple similar entries - as Evan so ably recognized for me.

I appreciate the parent plants entry. It gives me a place to put a picture that I can't ID. Later, with more info, I can move it to where it belongs.

This is correct that we have a parent plant that covers all plants in the Viburnum genus, and a plant cannot be a child to multiple parent plants. This means that we can't make Viburnum dentatum (pid 79475) a parent plant since it is already a child.

What we did in hibiscus was to make no parent plant on the top level but have several parent plants on the species level, and that worked out very well.

Being able to share data points across multiple plants is the primary reason I created parent plants in the first place, but parent plants are currently the only possible way to automate adding data points across multiple plants.

I am wondering if this wouldn't be the answer to Sedum. Instead of one Parent Plant for all sedum, doing parent plants at species level?

The sedums are mostly alike, aren't they?

We did this for Hibiscus because there is a pretty big difference between the main Hibiscus species.

I guess what we run into with the sedum is hardiness. I just need to really take a close look to the sedum parent plant info. I'm afraid I got side tracked when this was all being done.

One more. Ligularia: Ligularias (Ligularia)
Common Name: Leopard Plant

Plant Habit: Herb/Forb
Life cycle: Perennial

Wish there were more.

Thanks Evan, I handled that.

Dave, please add this entry as a parent plant.
Sarracenia: Pitcher Plants (Sarracenia)

Done!