API for Path (relationships) info?

Regarding that 'optional facet of the API could be to ask Geni to search'

I see that as an input parameter to the query; default (if not present) could be to either return the cached path (if it exists) or a null list (if the path is currently unknown). If this parameter is set, that would be similar to invoking the Geni search for a path -- or refreshing the cached path ... and the return from that could be determined by yet another optional input parameter: to wait for the search to complete before returning, or to return after starting the search, but without waiting for the search to complete (so the application can come back to it later, if desired).

Added "Feature Request" for this ... add your vote as you wish:
http://help.geni.com/entries/69857540-Add-API-for-getting-the-Geni-...

This is such a fundamental (and exceptional) feature on Geni that I'm hesitant to enable the same experience off-site.

.... I can understand that, although the usage I was thinking of was popping up a graphical representation of the path(s) from a Chrome extension. Just thinking of other ways to creatively present the same info already found on Geni (with far less loading than creating an app which attempts to build it's own pathways between two profiles.

I could also understand not wanting to have the API 'trigger' a path search, thus restricting the API to retrieving paths which have previously been "found" by way of the Geni UI.

I would very much like to see the path in more graphical representations (as also brought up in another discussion). In case the path is not found, and we normally have to "walk it", such an app may be able to piece together the shorter paths into one.

Thinking tangential to this, we may well have this tool to "draw the minimal tree" given three or more nodes. For example, two (or more) descendants of Charlemagne may want to see not only their closest common ancestor, but also to have Charlemagne featured in it. Even for smaller sized trees, it is often desirable to only show selected profiles, as the full tree is too dense. Say we want to see all monarchs descended from Queen Victoria (and maybe their intermarriages).

Geni probably doesn't have the resources at present to do this, so it makes sense let others try. I know nothing about API, but would it be possible to have such an app "in-site"? That would actually enhance this fundamental (and exceptional) feature of Geni.

I like the way Yao is talking. I don't want to see it available to anyone but Geni members, but I think we have sufficient talent in our membership to augment core functions. So perhaps it's about permissioning?

I'd like to see something like this: http://grab.by/IJHC

Dan Cornett, drew something similar on a piece of paper when trying to show a connection for the TV interview. The graphical representation with ups and downs made the path clearer.

Here's another similar implementation to a displaying a relationship

http://grab.by/IKd0

Note that this one is from familysearch and only works on very close relationships like my 2nd great aunt. In the screen grab I've added the red circle overlays but everything else is straight from the UI and not a mockup.

To Mikes point about this being a core geni feature I agree. Perhaps its time to think about the presentation of the "found relationship" feature that already exists and discuss alternate (better ways) of displaying the results as a new enhancement to geni.

+ 1 Randy (and Yao & Dan). The relationship calculator is such a strength of Geni's, enhance the presentation options.

Randy: That is very much like what I was envisioning ... when the path gets longer, my thinking was to 'collapse' the intervening 'profiles' into simply tiny circles (hovering over one could reveal the associated info).

The "length and structure" of the resulting 'line graph' would show the character of the relationship. (As with the existing Geni path display, there could be a 'color change' when there is a jump across a marriage relationship.)

My original thought on the API enhancement was to allow us Geni members to try different ways of displaying that information -- instead of waiting for Geni resources to be made available to do such experimentation.