I'm new to this, but have been reading the Help pages and wonder (apologies for the long post):
If I publish the FTB onto the web site, it can not be editied; each change I have to first perform on my home computer in FTB and re-publish. So if site members want to make changes they have to send their info to me and I have to go through this process. On the other hand:
If, on the other hand, I export FTB into GEDCOM and import that to the web site -- then members can do editing without my help. This poses two problems:
1) If members are completely free to make changes, they could mess things up; perhaps any change they do should be "approved" by the site administrator (this is less work that having me change the FTB and reload the data). Why isn't there an "approve" button?
2) The Help pages explain that GEDCOM upload / download do not transfer pictures. Does that mean that if I want to back up the site (after members make changes) to my home computer, I will not get the pictures? And while at it, if I need to fix the site by uploading a new GEDCOM -- I will have to upload pictures again each time? [I kno, you offer a backup for a few buck a month.... but my home computer should be a good back up too].
So for those with a lot of experience, what is a better option -- publish FTB or used GEDCOM format?
And for the MyHeritage managers -- what about "approve" button for changes made by members?
My own personal feeling for this question is I prefer to do all edits myself and publish. The reason being as you say "they could mess things up" after spending hours compiling the tree it would take minutes to ruin all that work. I have had family members asking me to remove ex partners and family cos they dont like them anymore, so just think what they could do if they had free access to edit.
If you want to make a tree editable for people to do work on create another tree where they can add info, ie a tree for a sibling to add nieces and nephews, info that you may not find in a search, then you can look at it and take any info to the main tree.
If there were a feature for you to "approve" I still would be wary of the members info and editing.
To bring another subject into your question "Photos and editing" I have spent months collecting documents and adding keywords for searching and also tagging photos with hundreds of people, all this work can be undone within seconds of somone just clicking the "DELETE button" so I would also ask the management for an "APPROVE" button for every "DELETE" in respect of photos and any editing of keywords and tagging.
If any management read this would it be possible for editing on photos to be restricted to certain people by having different levels of membership?
My own personal feeling for this question is I prefer to do all edits myself and publish.
If you want to make a tree editable for people to do work on create another tree where they can add info, ie a tree for a sibling to add nieces and nephews, info that you may not find in a search, then you can look at it and take any info to the main tree.
Colin Rout
Hi Colin (and others),
I like your idea of keeping 2 copies (one read-only and one updateable).
If it was integrated with a compare function of two trees that could be a base for an approvement strategy.
Colin, You have expressed my fears very well. All it takes is someone with anger motives, to destroy the entire enterprise (never mind backups). And of course, we have the worry about accidental, or a computer novice who does not know how to undo a mistake and end up causing irreparable damage. I’d think that “myheritage” site programmers would create an “approve” “reject” button and that would solve all the problems. It requires some planning the logistics, to allow the member to see his proposed changes, without affecting the actual site view, and then implementing the changes upon approval. If “management” keeps a “wish list” – this is one. Thanks, Nahum
