Is this a site problem? If I go to the Sempervivum Database and enter "sempervivum lemon sky" (or just "lemon sky") I get nothing but an eternal busy spinner, and no results when I send it. But in the Plants Database it works OK. Seems to be an issue for Heuffelii only... shouldn't the Heuffelii be searchable in the Sempervivum Database? This did work previously.

It's actually in the Jovibarbas Database so it looks like Jovibarba heuffelii is now a Synonym so this is something that @valleylyn needs to address with @dave.

Moved to the Plant database forum

OK, I'll see what Lynn says.

Tim, I agree that it's silly to leave the jovibarbas out of the Sempervivum database, but here's the solution. When you search for Sempervivum, you arrive at this page:

http://garden.org/plants/searc...

Instead of clicking the link for the Sempervivum Database, click the link that says "View all plants in the genus Sempervivum." That will bring you to a list of all the Sempervivums, including the jovibarvas.

http://garden.org/plants/brows...

Click on the "L" at the top and scroll down to Lemon Sky.

http://garden.org/plants/brows...

You can also avoid all of this by searching in the main database instead of the Sempervivum Database. If you search for Sempervivum Lemon Sky, it comes right up in the results.

http://garden.org/plants/searc...

It was discussed with Dave some time back about maybe merging the Jovibarba with the Sempervivum database. It was decided that we should leave it as is, in case the botanists change their minds again. At some point in time they may be merged. Not sure?

I used the Plant Database and typed in heuffelii lemon sky. Comes right up.
I used the Jovibarba database typing in heuffelii lemon sky and then tried just Lemon Sky. Both ways it comes up with the entry.

Man... I didn't even know there was a separate Jovibarba database.

I don't know that anyone seriously expects the botanists to change their minds The reason the two weren't merged is that Jovibarba originally was treated as a separate genus, with its own database. The Jovibarba Database had a custom architecture, including data fields specific to Jovibarba. Those fields had been filled with useful information by the time the Jovibarba entries were edited to reflect Jovibarba's new status as a synonym. All of the information in those data fields would have been lost if the two genera had been merged in a single database, so the plan for the merger was scrapped in order to save that information.