Updating the Project to be 2014 Current

Sharon Doubell - it is beginning to look like you are going to be unable to get/create good documentation in this project as to how Geni works because nobody knows how Geni works.

I'm just loving your ideas Lois :-)
Curators request a lot of things from Geni, but there are more of us volunteers than Geni staff-who are trying to concentrate on Geni's continued financial viability -so we get used to our ideas going into a queue :-)

Sorry. Cross--posted. Thinking of solutions.

I did realize that. (Don't think I've ever noticed two postings of exactly the same time before.)

Just checked the Help Section, re: initiating merges -- possibly relevant: http://help.geni.com/entries/469660-How-can-I-merge-my-tree-with-a-... This was updated in Nov. 2012, and I think is currently valid. Everything listed/suggested there is, I believe, something Basic Users (as well as Pros) can do. However - both the Wiki's that it links to were last updated in 2010, and are NOT accurate currently, so should NOT be there after "For information regarding XXXXX, please visit the following"

Lois - actually it's a terrible idea from a security standpoint to have more than one account. Since I have more "powers" I am more careful in their application.

Your core notion is absolutely correct, most actions will be able to be executed by basic members. Pros can do more merge work (tree) & edit work (profile). Curators can take care of errors like zombies & lack of response, in public / deceased / big tree, to merge requests. We have similar restrictions in standalone trees as anyone else.

It was probably a good idea not to carry your test further to leave that account in "standalone" mode. :):)

And luckily - since this project is about working in the big tree - we don't have to be very detailed about standalone.

Oh I didn't address the idea of a menu item to "function as a basic user."

Actually from an approvals / workflow scenario it's not a great idea. A "superuser" is best as a final step after those with lesser "powers" have vetted by proposing and setting it up correctly. Think of it from a managing editor point of view: yes, red lining has been done, profile correct, approve / go. Far more efficient.

Erica - the point of the the menu item to "function as a basic user" was so a curator could, if they chose, check if something was possible for the basic user to do / how a basic user might be able to do it, etc.

The purpose for that was so Curators could correctly explain how Geni worked when communicating individually to Users and when writing in Projects, etc. Absolutely no requirement that a given Curator use it. [Also - no need to use the function except in situations where Curators are not certain what the situation really is for the Basic user]

To the extent that a Curator wants to be able to help other Users learn how to use Geni, it might be useful.

Your comments seem to address the situation where a Curator is focused solely on building and fixing the World Tree, not in helping other Users to be more functional themselves. [I think you absolutely dp try to help others be more functional as well -- but I do not think that is what you were thinking about as you commented above]

meant "do" not "dp"

Lois I follow your points. I'd rather see an articulate basic user contribute what they can / cannot do so I can learn how to assist. I know the application (and computing) too well to be an effective tester, and this really should only be a test situation for appropriate segregation of powers.

The project IS working with the big tree so I want to keep that focus also.

I'm with Erica here: and Lois fits the bill of 'articulate user' - How long ago were you a Basic User, Lois?

Lois is too good on the app & knows the lingo! We need to see it from someone new to the Geni system but preferably not new to genealogy, perhaps

My suggestion -- you want BOTH some folks such as Erica suggests AND ALSO some folks who are currently Basic, but are experienced in Geni and Geni-lingo --

the former is more likely to be able to tell you if what is said communicates to the neophyte,
the latter is more likely to be able to tell you if there is a way for the Basic User to actually do the action - perhaps differently from how a Pro or Curator would, but is there a work-around - etc. Also perhaps more likely to be able to explain in Geni-lingo what happens when Basic User does such-and-such.

Are there any Basic Users 'listening' to this conversation? Or shall I go and advertise for them?

I did some basic cleanup on the project page. More to come.

Looking so good!

Justin -- When they first gave PRO the ability to edit Public Profiles, it was all the fields -- but then they changed it so PRO and Collaborators could just edit the fields with revision history -- to edit all the fields, you have to be one of the managers. Not sure how you want to phrase that, but somehow it belongs -- both vis a vis PRO and vis a vis Collaborator.

Also - Project currently has -
"Only members of the Family Group can edit a private profile." -- Geni now says these can AND Geni Curators and Geni Employees can. To keep from misleading folks, project should also probably say that. Yes??

Ditto for 'view'.

re: my comment above re: editing Public Profiles - think folks in the Family Group can also edit all the fields.

But (elaborating)-- PRO and/or Collaboration only gets you ability to edit the fields with revision history - no relationships, school, work, or personal tab, cannot edit Birth Order -- not sure what if anything else.

Timeline Events. A collaborator can add one, but only the author may change the text of an existing event.

Lois - great point about the manager vs collab edit ability but a minor point. If I remember correctly, the ability of PROs to edit public profiles "only ever" applied to fields under revision control (the big 7).

I think a link to http://www.geni.com/company/privacy shows the permissions structure well. It's understanding it that matters.

I know a PRO in the Big Tree can only edit Public Profiles in the Big Tree. Can a PRO in a StandAlone Tree only edit Public Profiles in that Standalone Tree -- or can he/she also edit Public Profiles in the Big Tree?

(Once clarified, that would also be a minor clarification that should be made to the Project - under "Editing" - to "A PRO user can edit any public profile. ")

Lois - of course a PRO in a standalone tree can edit any public profile in that tree & also private profiles based on family group.

I do not know the reverse scenario.

Erica - I was speaking only of which Public Profiles a PRO could edit -- did not mean to confuse you or anyone by suggesting they (whether in Big Tree or StandAlone Tree) could not edit private profiles of unclaimed family (and unclaimed private profiles managed by family) - see I did not state as clearly as I meant.

Can PRO in a standalone tree also edit Public Profiles in the Big Tree remains unanswered. Anybody know the answer?

http://help.geni.com/entries/20447001-What-are-the-different-types-... -- and as I look now, see no mention of one of the differences being that Pro can edit Public Profiles, Basic cannot.

I had certainly not realized that now EVERYBODY on the world tree could edit all the Public Profiles. (from my Basic Account on a Separate Tree, I still cannot edit Public Profiles on the World Tree)

SO -- The Project needs to be updated yet again, to reflect this additional change, which apparently snuck past us. (Anybody know when it was made??)

2012? The edit ability is for the fields under reversion control so needs qualification. And the fields under reversion control have changed / will change. And - I believe collaboration is still needed for many functions a basic user could perform.

re: "The edit ability is for the fields under reversion control" - yes, but it used to be a special Pro feature -- question is -- When did it change so Basic Users could also do?

You do remember, don't you, when they did a big hoopla about Pro just got better, could edit Public Profiles - yes?

http://help.geni.com/entries/20359416-August-11-Pro-Changes-and-New...
http://help.geni.com/entries/20222212-June-23-Public-editing-for-Pros

In the Privacy Policy -- under Public Profiles, across from "Who can edit profiles?" it says:
"Your Collaborators
Your Relatives
Geni Curators
Geni Employees" --

It says nothing about Pros, nor anything about all users!! Personally, if someone can edit ANY of the fields, that should be mentioned here.

Do not think the fact that there are a few fields they cannot edit counts as not being able to edit the Profile.

Who should I be flagging about this, and where?

Ticket to customer support. But as I've said, I find it a really good chart and partly exactly because it does "not" get into details of subscriptions. Any business needs flexibility on their offers, and any software developer needs to be able to implement without updating core basics.

The level of detail you are looking for would be covered in FAQ. So if I were you I'd find the relevant FAQ that could be improved.

Also I disagree on "just a couple of fields." Basic users cannot disconnect. That's a biggie.

It's a classic problem in writing documentation. Some users want a highly detailed document with every nuance discussed in detail. Other users want a general orientation piece. And each side thinks the whole thing is garbage if it isn't written their way ;)