Programming Suggestions to Geni

Jadranka's very cogent suggestions to Geni programmers - cut (with her permission) from the wikipaedia discussion:

"The way I see it
1) we have currently
a. first name
b. middle name
c. surname: maiden + married (2 fields)
d. suffix
e. display name
2) what we need
a. first name – option to enter alternative versions of the same name – all searchable
b. middle name – does not do much for me – I think it is not helping at all as you can’t see it during merge process, could be used for titles
c. surname: maiden + married (2 fields) – both needed
d. suffix, same as middle name, not useful
e. display name – should be constructed based on users own settings and choice to accommodate the variety we obviously have

For me that would mean to add additional fields (searchable) to the name fields so we can enter versions of names in different languages (with some code specifying which language it is). Geni could then have options under settings so each user can choose what they like and are used to, without limiting others to use their own conventions. The name stays the same, but it gets displayed depending on country, language, culture or simply users own preference (casual users vs hard core genealogists)."

I would add to this list that a prefix or title field is needed for sir, lord, lady, doctor etc.

I would add to this list that a prefix or title field is needed for sir, lord, lady, doctor etc.

Terry
I was thinking of using suffix for that, as we can (and should) put suffix in the first name field (again, my views are driven by making merges less prone to errors)

Very often a title and a suffix are needed, the title being almost a shorthand of the suffix, and yes it should make merges less prone to errors and make searching names less frustrating.
For example:
Sir,first name, last name, Knight of the garter

Without the extra prefix field may be confused with Jack Knight or Jack Smith (with Suffix: Lord)

My first reaction was, no, I don't needed it, but then I remebered all the possible combinations and orders I have seen-
I was writing this in the field for profession

But then, that field is not searchable, so if somone is looking for Kralj Tomislav (king Tomislav) they will not find him.

so, YES - it is needed

I would love to see "prefix" and "title(s)" added as database fields within Geni. I assume this is not so easy though.

"Suffix" is *not* the same as title.

I find the middle name field very useful. Many of the Dutch Settler descendants here in South Africa have ended up with the same first and surnames but different middle names. And the Ovenstones are sorted according to their middle names so an Ovenstone will have 1 first name but 15 middle names!
The middle name field is VERY useful.

Why do you need separate prefix and title?
What would be the difference (I can't see where it could be needed)?

Apparently in the United States middle names began to be used in the early 1700s, starting with the "artistocratic" settlers in the Virginia Colony area.

I suspect usage was much earlier in Holland? Do you have an idea when?

@Erica - Nope, I have no idea when their usage started in Holland but I assume it was much earlier than the 1700s.

I'd love soundex searchable name fields. Between typos, variations, nicknames, etc. some people are really difficult to find.

I know Geni has looked into soundex etc. for searches. Maybe we can get an update from them on their "search" parameters and that would help us with our User Guides.

Have a thought for those of us whose lines are not first world fast! ;->

I would dearly like for the dates to enable us to indicate, before (bef.), after (aft.) and between (bet.) rather than just circa. Much more accurate and better for searching.

Further comment re: names... ON GENI.... Because we are on Geni and using Geni, where a lot of people come to FIND their ancestors, people who have never done this before, no pros.. many are not professional genealogists. (I am not so sure it is our task to teach them and insist they use the systems that professional genealogists use.) And, because a lot of people do not know quite what they are doing, it is better to remember THAT, when we place names in the various name slots. I put multiple name in the display section in order to prevent, or help prevent, bad merges on the part of folks that are not paying close attention, newbies, and those who tend to be a little rushed or accidently careless. I would never do that in any other place except Geni. And it gives the person looking, a gentle hint, as to who else is in the background of that specific profile. For example if you have 3 or 4 names in the display name and only the first is compatible with the info you may have, then a logical person would easily see that that one first name is probably not related to the profile being visited, right off the bat, and an incorrect merge might be thwarted, if you get my jest.

I'd have to agree with Sally on the bef. and aft. part... as well as a fl. ... circa is very limited on descriptions. And a range part would also be useful to (bet.).

Sally,

This point is brilliant and I couldn't agree more:

"And, because a lot of people do not know quite what they are doing, it is better to remember THAT, when we place names in the various name slots ..."

Remember that geni is NOT a "traditional" genealogy program.

- It is a Web 2.5 interface that is more accurately described as "Facebook meets Wikipedia meets Ancestry meets The History Channel."

- It is a "sticky" (that is, addictive:) application: easy to learn, powerful to explore.

- It is a social networking tool, first and foremost.

- It is a collaborative knowledge building enterprise.

- It is a next generation dynamic database.

- It is a continually evolving visual interface.

- It is a document collection and researching tool.

- It is a report generator and diagram builder.

What we are concerned with, in *this* Project, is --

-- making it easiest for everyone to build the data in the most complete manner possible

-- making it easiest for everyone to find the data

So let's keep those parameters in mind.

Again, thank you, Sally, for articulating Mission so well.

Every profile have tab "Revisions". It contains records when revision was made, but without the "delta", - which field(s) was exactly changed. The problem with profiles, having several managers. Impossible to recognize the change.
Sometimes managers use "Change" to see the fields better and then press "Ok" without any change. Such "Change" also tracked in "Revisions".
It will be very helpful, if Revision will contain delta in any form.

Agreed. Geni is working on "revisions" and making it more transparent. Expect to see a fast introduction of more enhancements on that tab as it is a dependency for full "Wikification" of profiles, which is the goal.

There is the "delta" available in revisions. It uses the "on mouse over" functionality (currently not-translatable - English only).

Test it. If there are marked "private" - then mouse will give you False (manager set profile Public) or True (manager set profile Private).
If there is marked "living status" then again False (dead) and True (living) will give you change.
Revisions like "birth" or "death" will give you (with mouse) the dates "Date: mm/dd/yyyy" entered/changed by managers.

Of course - such a revisions where nothing was changed (manager just re-saved the profile) is no need to list as "{user} updated {profile}'s profile." under the revisions.

Thanks Lauri, it works.
not so comfortable. I see in ballon new value, but cannot see the previous one. btw, it shows any language, not only English. The ballon not shows a big texts. "about me", for example.