I see you did but you had quotes in there. You had:

"Granat x Rouge"

but it should be

Granat x Rouge

No quotes. I fixed it by editing out the quotes and you can see that the links are working properly now.

I understand now. Oh my gosh, what an amazing new tool.

Have I told you lately that you are the best every Programming Magic Man?

Missed this update yesterday, thanks for the link @Dave! Nice to see others now enjoying what we have had in the daylily database for a long time. It's a special feature!

Sue, thanks for the idea of this great feature;

Dave, thanks for programming it for all custom databases;

Glad you all like it!!

Awesome!

banker07 said:Sue, thanks for the idea of this great feature

@banker07, it wasn't my idea!

Very happy to hear that other plants/people will now enjoy the amazing DB ability to search for and track parentage and child lines! We all enjoy the daylily DB immensely, and indeed it is the core of this wonderful place for many of us here.

Two questions about the transition? Now that the parent/child box has moved, the links at each generation open in a separate browser tab, so that if you research a pedigree back through a number of generations there are soon many many tabs open in the browser (at least in my Chrome). Is this just something that is necessary in order to expand the capability system wide, or can we still opt to have hotlinks open serially inside of one tab (back-and-forth inside a single stable tab) through the generations?

I also noted that the child field does not seem to return any search results (at least for daylilies) but I assume that is under development?

I can't imagine how much hard work has gone into this new feature and I celebrate the changes even if they may come with some compromise. Widening the DB's ability to lend more information to more people is the most wonderful, grounding, and beneficial legacy possible.

Bravo, Dave!!

chalyse said:Now that the parent/child box has moved, the links at each generation open in a separate browser tab

Thanks for that report. It shouldn't have been doing that, and I have fixed it. They will now open in the same window.

chalyse said:I also noted that the child field does not seem to return any search results (at least for daylilies) but I assume that is under development?

It sounds like a bug but I can't see where this is happening. Can you give me the steps needed to replicate this?

Yay same-window generation searches! Thanks @dave!!

Sorry about not showing the child thingy I ran into - here's what it is, based on the cultivar Monica Mead, which has two parent and one child plants.

When I go to the DDB (daylily database) directly at http://garden.org/plants/group... and enter "monica mead" in the parentage box, it returns the result for its one child, Sentinel Pink Burst.



On the other hand, when I enter "monica mead" in the child box, it does not return its two parent plants, Cotton Club and Siloam Double Classic.



Because I can sometimes get confused about the difference in searching for parentage versus child plants, here is the URL string showing no result when I entered monica mead in the "child" search box (assuming it would return its parents, cotton club and siloam double classic, since entering monica mead in the "parentage" box returns its child, Sentinel Pink Burst):

http://garden.org/plants/group...

I hope this makes sense ... to be honest, I'm not sure if the "parentage" box means "find the parents of...[enter the child name]" or "find the children who have the parentage of...[enter the parent name/s]" or whether the child box means "find the children of...[enter the parent name/s]" or "find parents of....[enter the child name]....

Either way, I haven't yet been able to get any results back from searching different cultivar names in the "child" box via the direct route into http://garden.org/plants/group... ... but, as usual, it is entire probable that I am doing something, or thinking about it, in a funky way to cause it ...

Ok, yes, I see what you're talking about.

The "Child Plants" is actually an internal field that is created by the system automatically, but isn't supposed to be searchable like that. I'm going to remove it from the advanced search.

Use "Parentage" for the functionality that you're looking for.

Awesome, that was a conclusion that occurred to me, and removing it takes away my need to monkey with stuff i see, like empty boxes especially are just too delicious not to tinker with! The parentage box, by itself, works swell for me.

.... and still celebrating the spread of parentage DBs and enjoying the single-tabs

When identifying the parentage of a Sport, these two methods work.

1) Enter the Cultivar name without quotes. ex. Midnight, see Elephant's Ear (Colocasia esculenta 'Mojito')

2) Enter Sport of: Cultivar name without quotes but including the colon. ex. Sport of: Daniel, see Peace Lily (Spathiphyllum 'Domino')

Awesome Evan.

Very nice.

I'm having a lot of fun with this feature @Dave. Hosta 'Sum and Substance' now lists 76 child plants.

dave said:The system is limited to cultivar names only. So species level names will probably not form a link although it's possible that I may extend the system to support that in the future.

Many genera I've been dealing with haven't reached the point in breeding where the parents involved are both cultivars, so species level parent(s) are common. If/when this functionality is implemented what do you suggest as the best way to list these names?

ex. Hosta 'Warwick Ballerina'.
Parentage: H. pycnophylla x Sum and Substance or Hosta pycnophylla x Sum and Substance.

I've entered parents both ways.

In cased like that just enter the full Latin name not abbreviated. I think I can work with that.

Will do.

Wow, this is sure going to be another exciting tool. We have a number of species parents in the Sempervivum database. This will be most helpful.