On Fri, 14 Oct 2005, Pat Eyler wrote:
Actually, it would be good to go beyond passive acceptance here. Think about
what should be in the API, discuss it (use this list to keep the discussion
available) -- the church might not use all of the ideas that come up, but
they will be seen, discussed, and (maybe) used.
Without knowing too much about what features will be provided in the
'centralized repository' system that's currenlty under devlopment in the
Family History Department, it's a bit hard to specify what API
functionality we'd like to see. Would it be possible to give a general
overview of what we can expect?
As for myself, I would love to see an API exposing the search
functionality of such a system. Kind of like Google or Amazon:
- result_set = query_by_criteria(criteria)
- while (result_set.fetch_next_result()) {
do something()
}
I'd love to be able to create a variety of RSS/Atom feeds based on various
criteria, for example:
- Alert me when:
- Any information is added/updated about a given individual
- Any information is added/updated about an individual or any of his/her
ancestors/descendants
- New image sets come online from the indexing efforts at
ldsindexing.org
- If you look on any Yahoo search result page, there is an option
available to subscribe to an RSS feed of results for the query terms that
produced that result page via <link rel="alternate"
type="application/rss+xml"... So essentially being able to create a feed
based on the results of any given query. That way if any new results for a
given query turn up, I'm alerted to the fact in my news aggregator. It's
kind of like a nice research assistant who'd continually running my query
for me.
And that's just ideas for a search API. Without knowing the specific
features of how individual/family information is going to be handled in
the new system, it's hard to specify what would be desirable in an API.
Will I be able to associate images and other documents with any given
individual/event/marriage/etc? If so then mechanisms to manipulate those
associations programmatically would be nice.
Just some ideas,
-- Dan
There are a lot of people from the Family and Church History department on
this list now. I've heard it mentioned in more than 3 discussions/meetings
today alone.
Good to hear.
...Paul
-pate
Pat Eyler
Infrastructure Engineer, FCH
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
