I'm getting PGV installed for the first time and having some issues.
PGV seems very much geared towards people who already have a GEDCOM file to import. That's not me. I want to use PGV as a way to edit GEDCOMs with my family.
So… I go to Create a new GEDCOM. There's a "Path and name of GEDCOM on server" which doesn't make any sense at all considering I want a *new* GEDCOM. If I leave it blank it creates an _conf.php and an _priv.php in my INDEX_DIR, and then throws errors for every operation.
That seems kind of dumb. Shouldn't it create a random name or something when creating a new GEDCOM?
I'm willing to hack on it, if this is the right answer…
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The wiki and reality disagree. The wiki says "enter a name for the new GEDCOM without the extension .ged", but the resulting file on the server does not get a .ged suffix.
The fact that I have to pick a unique name is weird. I have a lot of Hockin people who have family trees that we are trying to merge. I have to manually keep track of GEDCOM file names? Why can't the server give it a random suffix? E.g. "hockin_XXXXXX" like mktemp() does in C.
I filed a few bugs, too. Creating a GEDCOM with the same path as an existing GEDCOM clobbers the _conf and _priv files, even if I choose 'cancel'.
I've long been a genealogy nut, but this is the first time I have tried to web-ify it. PGV seems very robust, but the UI is somewhat difficult. I've tripped over a number of bugs and issues already and I haven't even started adding data :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the wiki is just out-of-date. IIRC, PGV used to do this (because Windows likes file extensions), but was taken off (because Mac and Linux users often like to go without).
The fact that I have to pick a unique name is weird
Perhaps you are weird :-) Seriously - the overwhelming majority of people either have a gedcom from a desktop application, or are creating one-or two gedcoms for branches of their family. If you are called John Doe, you'll probably want to create a gedcom called something like doe.ged.
Are you sure you want to create many separate gedcoms? The usual reason for doing this is to create separate administration/privacy rules for each. If you are hoping to link all these families together, why not put them all in the same gedcom.
FYI, I'm doing a one-name study, and put all records for this surname in the same gedcom, even if they are not yet linked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sure I am wierd. I'm just trying to figure out how best to use this software.
I have a VERY LARGE family history to input, and to be honest, the PGV user interface kind of stinks. I really want to publish this stuff so my family and I can work on it, so I am wresting with PGV.
I'm looking at other solutions, such as http://geni.com, but I really don't feel comfortable inputting all my info into YET ANOTHER website. They are also missing lots of fields and info that PGV supports. Their UI, though, is really nice.
I'm open to ideas for "best practices" using PGV. The biggest failing I see is that it is written as a tool for genealogy experts. It is very hard to use for someone who doesn't think in GEDCOM. I had no idea what the various fact codes mean, or that "Hebrew Name" is actually the native language form of a name, or even that a GEDCOM is a "tree".
Why not make the UI easier to use for casual users? I'd be more than happy to help there.
The user experience is PGV's weakest point.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And a hearty welcome to PGV indeed! Many first time users have the same experience with the UI as you voice here. But I believe you are well on your way to a new genealogy experience! Coming from an IT background and trying to help my wife establish an online tool for genealogy, I too had to switch gears from knowing about FTP and MySQL errors to understanding GEDCOMs, family relationships and Facts. But as you have observed, once PGV spoils you other solutions begin to pale quickly in regards to features and presentation.
Earlier, you say: "PGV seems very much geared towards people who already have a GEDCOM file to import. That's not me. I want to use PGV as a way to edit GEDCOMs with my family."
One idea behind PGV is that once the GEDCOM is in the database, others can be given the ability to edit the data online. In an attempt the centralize the data in one place, you also gain other protections such as the ability to filter duplicate entries, focus on missing data, make file backups - steps overlooked when several people do their own research independently.
As for creating your first GED, if you are working entirely from written records, I suggest using one ancestor as a starting point and working down the "family tree" from this person. From their page, you can add other family members - wives, children, etc. - and New people easily with the links that appear by default. On the other hand, if someone has a "family tree" going in some desktop software already, they should be able to File> Export the data into the GED format and forward that file for your use. This would eliminate the data duplication and save countless hours of typing and screen refreshes. Later, you could allow the "sharing" of your PGV data as there is a utility to create what is called a GEDCOM Clipping. This will Export out whatever parts of your database you desire.
While reading up on the GEDCOM format (standard?) is the stuff of bedtime stories (sleepy-time), one does not need to be bogged down with these great (sometmes inconsistent) details to get started in PGV. The previous posters (Fisharebest and Kiwi_pgv) are most keen on usability and are constantly working on developments which keep PGV usable - while improving funtionality.
Go ahead, take a stab at creating a GED and making a few entries. You can always delete it and start over (I have several times). (You mention C programming earlier too, this is no where near as hard !) Just remember the name you give your GED will be what shows on your homepage of your site. Give a family member or two a login after you are comfortable with a few basic elements of how PGV works.
I guess the whole point of this narrative is to encourage you to continue reading the Wiki to get a real feel for what PGV can really do. This is really a "hammer and nails" problem and you now have the Hammer!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm getting PGV installed for the first time and having some issues.
PGV seems very much geared towards people who already have a GEDCOM file to import. That's not me. I want to use PGV as a way to edit GEDCOMs with my family.
So… I go to Create a new GEDCOM. There's a "Path and name of GEDCOM on server" which doesn't make any sense at all considering I want a *new* GEDCOM. If I leave it blank it creates an _conf.php and an _priv.php in my INDEX_DIR, and then throws errors for every operation.
That seems kind of dumb. Shouldn't it create a random name or something when creating a new GEDCOM?
I'm willing to hack on it, if this is the right answer…
PGV will create the gedcom for you - but as you've discovered, you have to give it a name.
Although it stores everything in the database, it is a bit of a hybrid (for historical reasons), and also likes to have an external file.
So, pick a name. family.ged might be a good choice.
When you come to download a copy of your gedcom (a good way of making backups), the file will have this name.
Hi and welcome to PGV
There are some instructions for this process in the WIKI. Hopefully they will guide you better, but come back here if you still have problems:
http://wiki.phpgedview.net/en/index.php?title=Create_a_new_GEDCOM
The wiki and reality disagree. The wiki says "enter a name for the new GEDCOM without the extension .ged", but the resulting file on the server does not get a .ged suffix.
The fact that I have to pick a unique name is weird. I have a lot of Hockin people who have family trees that we are trying to merge. I have to manually keep track of GEDCOM file names? Why can't the server give it a random suffix? E.g. "hockin_XXXXXX" like mktemp() does in C.
I filed a few bugs, too. Creating a GEDCOM with the same path as an existing GEDCOM clobbers the _conf and _priv files, even if I choose 'cancel'.
I've long been a genealogy nut, but this is the first time I have tried to web-ify it. PGV seems very robust, but the UI is somewhat difficult. I've tripped over a number of bugs and issues already and I haven't even started adding data :)
The wiki and reality disagree.
I think the wiki is just out-of-date. IIRC, PGV used to do this (because Windows likes file extensions), but was taken off (because Mac and Linux users often like to go without).
The fact that I have to pick a unique name is weird
Perhaps you are weird :-) Seriously - the overwhelming majority of people either have a gedcom from a desktop application, or are creating one-or two gedcoms for branches of their family. If you are called John Doe, you'll probably want to create a gedcom called something like doe.ged.
Are you sure you want to create many separate gedcoms? The usual reason for doing this is to create separate administration/privacy rules for each. If you are hoping to link all these families together, why not put them all in the same gedcom.
FYI, I'm doing a one-name study, and put all records for this surname in the same gedcom, even if they are not yet linked.
I'm sure I am wierd. I'm just trying to figure out how best to use this software.
I have a VERY LARGE family history to input, and to be honest, the PGV user interface kind of stinks. I really want to publish this stuff so my family and I can work on it, so I am wresting with PGV.
I'm looking at other solutions, such as http://geni.com, but I really don't feel comfortable inputting all my info into YET ANOTHER website. They are also missing lots of fields and info that PGV supports. Their UI, though, is really nice.
I'm open to ideas for "best practices" using PGV. The biggest failing I see is that it is written as a tool for genealogy experts. It is very hard to use for someone who doesn't think in GEDCOM. I had no idea what the various fact codes mean, or that "Hebrew Name" is actually the native language form of a name, or even that a GEDCOM is a "tree".
Why not make the UI easier to use for casual users? I'd be more than happy to help there.
The user experience is PGV's weakest point.
Hello thockin -
And a hearty welcome to PGV indeed! Many first time users have the same experience with the UI as you voice here. But I believe you are well on your way to a new genealogy experience! Coming from an IT background and trying to help my wife establish an online tool for genealogy, I too had to switch gears from knowing about FTP and MySQL errors to understanding GEDCOMs, family relationships and Facts. But as you have observed, once PGV spoils you other solutions begin to pale quickly in regards to features and presentation.
Earlier, you say: "PGV seems very much geared towards people who already have a GEDCOM file to import. That's not me. I want to use PGV as a way to edit GEDCOMs with my family."
One idea behind PGV is that once the GEDCOM is in the database, others can be given the ability to edit the data online. In an attempt the centralize the data in one place, you also gain other protections such as the ability to filter duplicate entries, focus on missing data, make file backups - steps overlooked when several people do their own research independently.
As for creating your first GED, if you are working entirely from written records, I suggest using one ancestor as a starting point and working down the "family tree" from this person. From their page, you can add other family members - wives, children, etc. - and New people easily with the links that appear by default. On the other hand, if someone has a "family tree" going in some desktop software already, they should be able to File> Export the data into the GED format and forward that file for your use. This would eliminate the data duplication and save countless hours of typing and screen refreshes. Later, you could allow the "sharing" of your PGV data as there is a utility to create what is called a GEDCOM Clipping. This will Export out whatever parts of your database you desire.
While reading up on the GEDCOM format (standard?) is the stuff of bedtime stories (sleepy-time), one does not need to be bogged down with these great (sometmes inconsistent) details to get started in PGV. The previous posters (Fisharebest and Kiwi_pgv) are most keen on usability and are constantly working on developments which keep PGV usable - while improving funtionality.
Go ahead, take a stab at creating a GED and making a few entries. You can always delete it and start over (I have several times). (You mention C programming earlier too, this is no where near as hard !) Just remember the name you give your GED will be what shows on your homepage of your site. Give a family member or two a login after you are comfortable with a few basic elements of how PGV works.
I guess the whole point of this narrative is to encourage you to continue reading the Wiki to get a real feel for what PGV can really do. This is really a "hammer and nails" problem and you now have the Hammer!