From: Gerald B. <ger...@gm...> - 2010-11-24 16:51:32
|
Hi all -- I'm looking for some input as to the best place to store web links for sources. Consider this scenario: 1. You have a source (say, a marriage register) 2. The source has one or more web-access portals 3. You want to store the link(s) to the (those) portal(s) in the source record. You could do this: 1. Create your source 2. Add a Note to the source, with the link to the portal (possibly one per portal) or: 2. Using the data tab, add one or more items with keys like (URL, Web Link, ...) with the value being the URL -- Gerald Britton |
From: Mary L. <mar...@bl...> - 2010-11-24 21:42:10
|
I would consider the web-access portals to be repositories, and create a repository for each website. The repository editor dialog has a tab for internet, under which you can add any URL's you want to store for the site. You can add more than one repository to a source. Mary Lynch On 24/11/2010 16:51, Gerald Britton wrote: > Hi all -- I'm looking for some input as to the best place to store web > links for sources. Consider this scenario: > > 1. You have a source (say, a marriage register) > 2. The source has one or more web-access portals > 3. You want to store the link(s) to the (those) portal(s) in the source record. > > You could do this: > > 1. Create your source > 2. Add a Note to the source, with the link to the portal (possibly one > per portal) > > or: > > 2. Using the data tab, add one or more items with keys like (URL, Web > Link, ...) with the value being the URL > |
From: jerome <rom...@ya...> - 2010-11-25 09:58:11
|
+1 http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png --- En date de : Mer 24.11.10, Mary Lynch <mar...@bl...> a écrit : > De: Mary Lynch <mar...@bl...> > Objet: Re: [Gramps-users] Where do you store web links for sources > À: gra...@li... > Date: Mercredi 24 novembre 2010, 20h30 > I would consider the web-access > portals to be repositories, and create a > repository for each website. The repository editor dialog > has a tab for > internet, under which you can add any URL's you want to > store for the > site. You can add more than one repository to a source. > > Mary Lynch > > On 24/11/2010 16:51, Gerald Britton wrote: > > Hi all -- I'm looking for some input as to the best > place to store web > > links for sources. Consider this scenario: > > > > 1. You have a source (say, a marriage register) > > 2. The source has one or more web-access portals > > 3. You want to store the link(s) to the (those) > portal(s) in the source record. > > > > You could do this: > > > > 1. Create your source > > 2. Add a Note to the source, with the link to the > portal (possibly one > > per portal) > > > > or: > > > > 2. Using the data tab, add one or more items with keys > like (URL, Web > > Link, ...) with the value being the URL > > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance > To Win $500! > Tap into the largest installed PC base & get more eyes > on your game by > optimizing for Intel(R) Graphics Technology. Get started > today with the > Intel(R) Software Partner Program. Five $500 cash prizes > are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Gerald B. <ger...@gm...> - 2010-11-26 19:00:45
|
Thanks all for the input. I believe that this is the approach I should use: (Looking for comments and answers to the two questions below.) 1. An Event (such as birth, death, marriage, census etc.) will have one or more supporting Source references (each of which refers to a Source object) 2. Use Source Reference attributes to collect data not in standard fields. (e.g. Certificate number) Note: Previously I used Event Attributes for this, but I'm changing my mind. 3. For cyberspace sources, add a Source Reference attribute to hold the URL of the source (e.g. a PDF file at a government archive website) 4. When possible and practical, save copies of documents on my computer and create Media objects for them. Link the Media Objects to the Source gallery. (This way the Source object will have links to every document I have from that source.) Note: Previously I used the Event gallery for this, but I'm changing my mind. ***Question*** Should I store the URL to the archive in the Media Object Attributes as well? But then there will be two copies of the URL, since I saved one in step 3! Hmmmm.... ***Question 2*** Do you put the same Source info for the Media object? But then you have it twice...once for the Event and once for the Media object. 5. Source objects have one or more Repositories. On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: > +1 > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png > > > --- En date de : Mer 24.11.10, Mary Lynch <mar...@bl...> a écrit : > >> De: Mary Lynch <mar...@bl...> >> Objet: Re: [Gramps-users] Where do you store web links for sources >> À: gra...@li... >> Date: Mercredi 24 novembre 2010, 20h30 >> I would consider the web-access >> portals to be repositories, and create a >> repository for each website. The repository editor dialog >> has a tab for >> internet, under which you can add any URL's you want to >> store for the >> site. You can add more than one repository to a source. >> >> Mary Lynch >> >> On 24/11/2010 16:51, Gerald Britton wrote: >> > Hi all -- I'm looking for some input as to the best >> place to store web >> > links for sources. Consider this scenario: >> > >> > 1. You have a source (say, a marriage register) >> > 2. The source has one or more web-access portals >> > 3. You want to store the link(s) to the (those) >> portal(s) in the source record. >> > >> > You could do this: >> > >> > 1. Create your source >> > 2. Add a Note to the source, with the link to the >> portal (possibly one >> > per portal) >> > >> > or: >> > >> > 2. Using the data tab, add one or more items with keys >> like (URL, Web >> > Link, ...) with the value being the URL >> > >> >> >> ------------------------------------------------------------------------------ >> Increase Visibility of Your 3D Game App & Earn a Chance >> To Win $500! >> Tap into the largest installed PC base & get more eyes >> on your game by >> optimizing for Intel(R) Graphics Technology. Get started >> today with the >> Intel(R) Software Partner Program. Five $500 cash prizes >> are up for grabs. >> http://p.sf.net/sfu/intelisp-dev2dev >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> > > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > -- Gerald Britton |
From: Benny M. <ben...@gm...> - 2010-11-27 09:15:43
|
2010/11/26 Gerald Britton <ger...@gm...> > Thanks all for the input. I believe that this is the approach I > should use: (Looking for comments and answers to the two questions > below.) > > 1. An Event (such as birth, death, marriage, census etc.) will have > one or more supporting Source references (each of which refers to a > Source object) > > 2. Use Source Reference attributes to collect data not in standard > fields. (e.g. Certificate number) > Data from the source, should be stored in the source. For certificates, you can make one source per certificate, and give a title which refers to the book: Title: Baptize registry St Lawrence - John Do Many people work like this and it works great. If you create one big source, you must use an organization scheme inside the source: start pieces of John Do with the entry number. Then the source ref contains the ref number, and you know what to look for in the source. This approach is the more 'official' one. Data of the event, you learn from the source, should be part of the event, with a source attached to it. You can repeat that info in the source if that is what you like. > Note: Previously I used Event Attributes for this, but I'm changing my > mind. > > 3. For cyberspace sources, add a Source Reference attribute to hold > the URL of the source (e.g. a PDF file at a government archive > website) > > 4. When possible and practical, save copies of documents on my > computer and create Media objects for them. Link the Media Objects to > the Source gallery. (This way the Source object will have links to > every document I have from that source.) > > Note: Previously I used the Event gallery for this, but I'm changing my > mind. > > ***Question*** Should I store the URL to the archive in the Media > Object Attributes as well? But then there will be two copies of the > URL, since I saved one in step 3! Hmmmm.... > I would not do that. The repository is sufficient. You will in the future find a better repository (better scans, cheaper, ...), but the source will remain the same. > > ***Question 2*** Do you put the same Source info for the Media object? > But then you have it twice...once for the Event and once for the > Media object. > Sharing does not hurt. I add the source to as much as relevant. Note that the above problem with sources comes from the fact we track the GEDCOM implementation. There have been ideas to work with source parts. So an entry in a source relevant would be a source part, and the source view becomes a treeview. There are programs who use that approach, but somebody should put in the effort to see what is needed to do that, so also, how we import/export to GEDCOM in that case. Benny > > 5. Source objects have one or more Repositories. > > On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: > > +1 > > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png > > > > > > --- En date de : Mer 24.11.10, Mary Lynch < > mar...@bl...> a écrit : > > > >> De: Mary Lynch <mar...@bl...> > >> Objet: Re: [Gramps-users] Where do you store web links for sources > >> À: gra...@li... > >> Date: Mercredi 24 novembre 2010, 20h30 > >> I would consider the web-access > >> portals to be repositories, and create a > >> repository for each website. The repository editor dialog > >> has a tab for > >> internet, under which you can add any URL's you want to > >> store for the > >> site. You can add more than one repository to a source. > >> > >> Mary Lynch > >> > >> On 24/11/2010 16:51, Gerald Britton wrote: > >> > Hi all -- I'm looking for some input as to the best > >> place to store web > >> > links for sources. Consider this scenario: > >> > > >> > 1. You have a source (say, a marriage register) > >> > 2. The source has one or more web-access portals > >> > 3. You want to store the link(s) to the (those) > >> portal(s) in the source record. > >> > > >> > You could do this: > >> > > >> > 1. Create your source > >> > 2. Add a Note to the source, with the link to the > >> portal (possibly one > >> > per portal) > >> > > >> > or: > >> > > >> > 2. Using the data tab, add one or more items with keys > >> like (URL, Web > >> > Link, ...) with the value being the URL > >> > > >> > >> > >> > ------------------------------------------------------------------------------ > >> Increase Visibility of Your 3D Game App & Earn a Chance > >> To Win $500! > >> Tap into the largest installed PC base & get more eyes > >> on your game by > >> optimizing for Intel(R) Graphics Technology. Get started > >> today with the > >> Intel(R) Software Partner Program. Five $500 cash prizes > >> are up for grabs. > >> http://p.sf.net/sfu/intelisp-dev2dev > >> _______________________________________________ > >> Gramps-users mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-users > >> > > > > > > > > > > > ------------------------------------------------------------------------------ > > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > > Tap into the largest installed PC base & get more eyes on your game by > > optimizing for Intel(R) Graphics Technology. Get started today with the > > Intel(R) Software Partner Program. Five $500 cash prizes are up for > grabs. > > http://p.sf.net/sfu/intelisp-dev2dev > > _______________________________________________ > > Gramps-users mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-users > > > > > > -- > Gerald Britton > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Gerald B. <ger...@gm...> - 2010-11-27 14:20:42
|
On Sat, Nov 27, 2010 at 4:15 AM, Benny Malengier <ben...@gm...> wrote: > > > 2010/11/26 Gerald Britton <ger...@gm...> >> >> Thanks all for the input. I believe that this is the approach I >> should use: (Looking for comments and answers to the two questions >> below.) >> >> 1. An Event (such as birth, death, marriage, census etc.) will have >> one or more supporting Source references (each of which refers to a >> Source object) >> >> 2. Use Source Reference attributes to collect data not in standard >> fields. (e.g. Certificate number) > > Data from the source, should be stored in the source. For certificates, you > can make one source per certificate, and give a title which refers to the > book: Title: Baptize registry St Lawrence - John Do > Many people work like this and it works great. > If you create one big source, you must use an organization scheme inside the > source: start pieces of John Do with the entry number. This seems to be a workaround for gramps limitations (or our adherence to GEDCOM, more likely). If we had source reference attributes, this would be easier, I think. Also, for censuses it doesn't make sense(s...pun intended!) to have one source per...what? I started down this road while adding Canadian censuses to the Census Gramplet. The approach that plugin uses is to put all the data from one line of a census in the event reference attributes for that event for that individual. There is one source per census. Some Canadian censuses have as many as 140 pieces of data per individual (!) So there is one event (the census taker visits the household) shared by all members of the household and an event reference for each member (even those absent at the time) holding the specific data collected at that time. The problem I see is that event (reference) attributes are not the the ideal/logical place to store things like whether the house was brick or frame, how many pigs you had or the census-taker's comment that the 19-year-old daughter was very pretty. That is, that information existed before the event and continues after the event and would exist even if a census was never taken. So, I conclude that the event (reference) attributes is not the best choice. However, it appears to be the only practical choice in the current implementation. OTOH if we had attributes on source references, this is where I believe such data should go. > Then the source ref contains the ref number, and you know what to look for > in the source. This approach is the more 'official' one. I have done something like that so far, but in light of my work on censuses, I now see its limitations. I don't want to go back to the source to see how many acres of land my ggg.grandfather told the census taker he had in 1881 -- I want to record it in the database as an attribute found in the census. > > Data of the event, you learn from the source, should be part of the event, > with a source attached to it. You can repeat that info in the source if that > is what you like. This where I disagree I guess, since (in my mind) the event doesn't determine the data. The event caused the data to be recorded on the source. Also, conflicts are possible between two different sources for the same event (doesn't usually apply to censuses). Most often in the name (misspellings, abbreviations, etc.) but other things as well. Ideally, I'd want to record what I find in the sources and afterwards try to determine what is most likely the true (or best) information. > >> >> Note: Previously I used Event Attributes for this, but I'm changing my >> mind. >> >> 3. For cyberspace sources, add a Source Reference attribute to hold >> the URL of the source (e.g. a PDF file at a government archive >> website) >> >> 4. When possible and practical, save copies of documents on my >> computer and create Media objects for them. Link the Media Objects to >> the Source gallery. (This way the Source object will have links to >> every document I have from that source.) >> >> Note: Previously I used the Event gallery for this, but I'm changing my >> mind. >> >> ***Question*** Should I store the URL to the archive in the Media >> Object Attributes as well? But then there will be two copies of the >> URL, since I saved one in step 3! Hmmmm.... > > I would not do that. The repository is sufficient. You will in the future > find a better repository (better scans, cheaper, ...), but the source will > remain the same. >> >> ***Question 2*** Do you put the same Source info for the Media object? >> But then you have it twice...once for the Event and once for the >> Media object. > > Sharing does not hurt. I add the source to as much as relevant. > > Note that the above problem with sources comes from the fact we track the > GEDCOM implementation. There have been ideas to work with source parts. So > an entry in a source relevant would be a source part, and the source view > becomes a treeview. There are programs who use that approach, but somebody > should put in the effort to see what is needed to do that, so also, how we > import/export to GEDCOM in that case. Something to think about.... > > Benny >> >> 5. Source objects have one or more Repositories. >> >> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: >> > +1 >> > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png >> > >> > >> > --- En date de : Mer 24.11.10, Mary Lynch >> > <mar...@bl...> a écrit : >> > >> >> De: Mary Lynch <mar...@bl...> >> >> Objet: Re: [Gramps-users] Where do you store web links for sources >> >> À: gra...@li... >> >> Date: Mercredi 24 novembre 2010, 20h30 >> >> I would consider the web-access >> >> portals to be repositories, and create a >> >> repository for each website. The repository editor dialog >> >> has a tab for >> >> internet, under which you can add any URL's you want to >> >> store for the >> >> site. You can add more than one repository to a source. >> >> >> >> Mary Lynch >> >> >> >> On 24/11/2010 16:51, Gerald Britton wrote: >> >> > Hi all -- I'm looking for some input as to the best >> >> place to store web >> >> > links for sources. Consider this scenario: >> >> > >> >> > 1. You have a source (say, a marriage register) >> >> > 2. The source has one or more web-access portals >> >> > 3. You want to store the link(s) to the (those) >> >> portal(s) in the source record. >> >> > >> >> > You could do this: >> >> > >> >> > 1. Create your source >> >> > 2. Add a Note to the source, with the link to the >> >> portal (possibly one >> >> > per portal) >> >> > >> >> > or: >> >> > >> >> > 2. Using the data tab, add one or more items with keys >> >> like (URL, Web >> >> > Link, ...) with the value being the URL >> >> > >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Increase Visibility of Your 3D Game App & Earn a Chance >> >> To Win $500! >> >> Tap into the largest installed PC base & get more eyes >> >> on your game by >> >> optimizing for Intel(R) Graphics Technology. Get started >> >> today with the >> >> Intel(R) Software Partner Program. Five $500 cash prizes >> >> are up for grabs. >> >> http://p.sf.net/sfu/intelisp-dev2dev >> >> _______________________________________________ >> >> Gramps-users mailing list >> >> Gra...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> >> >> > >> > >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >> > Tap into the largest installed PC base & get more eyes on your game by >> > optimizing for Intel(R) Graphics Technology. Get started today with the >> > Intel(R) Software Partner Program. Five $500 cash prizes are up for >> > grabs. >> > http://p.sf.net/sfu/intelisp-dev2dev >> > _______________________________________________ >> > Gramps-users mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-users >> > >> >> >> >> -- >> Gerald Britton >> >> >> ------------------------------------------------------------------------------ >> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >> Tap into the largest installed PC base & get more eyes on your game by >> optimizing for Intel(R) Graphics Technology. Get started today with the >> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >> http://p.sf.net/sfu/intelisp-dev2dev >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users > > -- Gerald Britton |
From: Benny M. <ben...@gm...> - 2010-11-27 16:43:40
|
2010/11/27 Gerald Britton <ger...@gm...> > On Sat, Nov 27, 2010 at 4:15 AM, Benny Malengier > <ben...@gm...> wrote: > > > > > > 2010/11/26 Gerald Britton <ger...@gm...> > >> > >> Thanks all for the input. I believe that this is the approach I > >> should use: (Looking for comments and answers to the two questions > >> below.) > >> > >> 1. An Event (such as birth, death, marriage, census etc.) will have > >> one or more supporting Source references (each of which refers to a > >> Source object) > >> > >> 2. Use Source Reference attributes to collect data not in standard > >> fields. (e.g. Certificate number) > > > > Data from the source, should be stored in the source. For certificates, > you > > can make one source per certificate, and give a title which refers to the > > book: Title: Baptize registry St Lawrence - John Do > > Many people work like this and it works great. > > If you create one big source, you must use an organization scheme inside > the > > source: start pieces of John Do with the entry number. > > This seems to be a workaround for gramps limitations (or our adherence > to GEDCOM, more likely). If we had source reference attributes, this > would be easier, I think. Also, for censuses it doesn't make > sense(s...pun intended!) to have one source per...what? I started > down this road while adding Canadian censuses to the Census Gramplet. > The approach that plugin uses is to put all the data from one line of > a census in the event reference attributes for that event for that > individual. There is one source per census. Some Canadian censuses > have as many as 140 pieces of data per individual (!) So there is one > event (the census taker visits the household) shared by all members of > the household and an event reference for each member (even those > absent at the time) holding the specific data collected at that time. > > The problem I see is that event (reference) attributes are not the the > ideal/logical place to store things like whether the house was brick > or frame, how many pigs you had or the census-taker's comment that the > 19-year-old daughter was very pretty. That is, that information > existed before the event and continues after the event and would exist > even if a census was never taken. So, I conclude that the event > (reference) attributes is not the best choice. However, it appears to > be the only practical choice in the current implementation. OTOH if > we had attributes on source references, this is where I believe such > data should go. > Source reference should not have attributes because the attributes are part of the source. In good data management you don't duplicate information, but because source ref is unique to the object and the source connection, you can only duplicate. When I say repeat the information, then I mean: census: pretty girl --> attribute on the person indicating she is pretty --> attribute has source to the census source census date --> event on person/family with source the census So, everything in the census is stored in the source. And where you use that information to add info on people and families, you use the source. I can understand why this is stored with event by the census gramplet, but that is due to a technical limitation, not because it is the correct way to work, at least in my opinion. Benny > > > Then the source ref contains the ref number, and you know what to look > for > > in the source. This approach is the more 'official' one. > > I have done something like that so far, but in light of my work on > censuses, I now see its limitations. I don't want to go back to the > source to see how many acres of land my ggg.grandfather told the > census taker he had in 1881 -- I want to record it in the database as > an attribute found in the census. > > > > > Data of the event, you learn from the source, should be part of the > event, > > with a source attached to it. You can repeat that info in the source if > that > > is what you like. > > This where I disagree I guess, since (in my mind) the event doesn't > determine the data. The event caused the data to be recorded on the > source. Also, conflicts are possible between two different sources > for the same event (doesn't usually apply to censuses). Most often in > the name (misspellings, abbreviations, etc.) but other things as > well. Ideally, I'd want to record what I find in the sources and > afterwards try to determine what is most likely the true (or best) > information. > > > > >> > >> Note: Previously I used Event Attributes for this, but I'm changing my > >> mind. > >> > >> 3. For cyberspace sources, add a Source Reference attribute to hold > >> the URL of the source (e.g. a PDF file at a government archive > >> website) > >> > >> 4. When possible and practical, save copies of documents on my > >> computer and create Media objects for them. Link the Media Objects to > >> the Source gallery. (This way the Source object will have links to > >> every document I have from that source.) > >> > >> Note: Previously I used the Event gallery for this, but I'm changing my > >> mind. > >> > >> ***Question*** Should I store the URL to the archive in the Media > >> Object Attributes as well? But then there will be two copies of the > >> URL, since I saved one in step 3! Hmmmm.... > > > > I would not do that. The repository is sufficient. You will in the future > > find a better repository (better scans, cheaper, ...), but the source > will > > remain the same. > >> > >> ***Question 2*** Do you put the same Source info for the Media object? > >> But then you have it twice...once for the Event and once for the > >> Media object. > > > > Sharing does not hurt. I add the source to as much as relevant. > > > > Note that the above problem with sources comes from the fact we track the > > GEDCOM implementation. There have been ideas to work with source parts. > So > > an entry in a source relevant would be a source part, and the source view > > becomes a treeview. There are programs who use that approach, but > somebody > > should put in the effort to see what is needed to do that, so also, how > we > > import/export to GEDCOM in that case. > > Something to think about.... > > > > Benny > >> > >> 5. Source objects have one or more Repositories. > >> > >> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: > >> > +1 > >> > > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png > >> > > >> > > >> > --- En date de : Mer 24.11.10, Mary Lynch > >> > <mar...@bl...> a écrit : > >> > > >> >> De: Mary Lynch <mar...@bl...> > >> >> Objet: Re: [Gramps-users] Where do you store web links for sources > >> >> À: gra...@li... > >> >> Date: Mercredi 24 novembre 2010, 20h30 > >> >> I would consider the web-access > >> >> portals to be repositories, and create a > >> >> repository for each website. The repository editor dialog > >> >> has a tab for > >> >> internet, under which you can add any URL's you want to > >> >> store for the > >> >> site. You can add more than one repository to a source. > >> >> > >> >> Mary Lynch > >> >> > >> >> On 24/11/2010 16:51, Gerald Britton wrote: > >> >> > Hi all -- I'm looking for some input as to the best > >> >> place to store web > >> >> > links for sources. Consider this scenario: > >> >> > > >> >> > 1. You have a source (say, a marriage register) > >> >> > 2. The source has one or more web-access portals > >> >> > 3. You want to store the link(s) to the (those) > >> >> portal(s) in the source record. > >> >> > > >> >> > You could do this: > >> >> > > >> >> > 1. Create your source > >> >> > 2. Add a Note to the source, with the link to the > >> >> portal (possibly one > >> >> > per portal) > >> >> > > >> >> > or: > >> >> > > >> >> > 2. Using the data tab, add one or more items with keys > >> >> like (URL, Web > >> >> > Link, ...) with the value being the URL > >> >> > > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ > >> >> Increase Visibility of Your 3D Game App & Earn a Chance > >> >> To Win $500! > >> >> Tap into the largest installed PC base & get more eyes > >> >> on your game by > >> >> optimizing for Intel(R) Graphics Technology. Get started > >> >> today with the > >> >> Intel(R) Software Partner Program. Five $500 cash prizes > >> >> are up for grabs. > >> >> http://p.sf.net/sfu/intelisp-dev2dev > >> >> _______________________________________________ > >> >> Gramps-users mailing list > >> >> Gra...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/gramps-users > >> >> > >> > > >> > > >> > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > >> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > >> > Tap into the largest installed PC base & get more eyes on your game by > >> > optimizing for Intel(R) Graphics Technology. Get started today with > the > >> > Intel(R) Software Partner Program. Five $500 cash prizes are up for > >> > grabs. > >> > http://p.sf.net/sfu/intelisp-dev2dev > >> > _______________________________________________ > >> > Gramps-users mailing list > >> > Gra...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gramps-users > >> > > >> > >> > >> > >> -- > >> Gerald Britton > >> > >> > >> > ------------------------------------------------------------------------------ > >> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > >> Tap into the largest installed PC base & get more eyes on your game by > >> optimizing for Intel(R) Graphics Technology. Get started today with the > >> Intel(R) Software Partner Program. Five $500 cash prizes are up for > grabs. > >> http://p.sf.net/sfu/intelisp-dev2dev > >> _______________________________________________ > >> Gramps-users mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-users > > > > > > > > -- > Gerald Britton > |
From: Benny M. <ben...@gm...> - 2010-11-26 19:33:21
|
2010/11/26 Gerald Britton <ger...@gm...> > Thanks all for the input. I believe that this is the approach I > should use: (Looking for comments and answers to the two questions > below.) > > 1. An Event (such as birth, death, marriage, census etc.) will have > one or more supporting Source references (each of which refers to a > Source object) > > 2. Use Source Reference attributes to collect data not in standard > fields. (e.g. Certificate number) > What is a source reference attribute? There is only source data. The source reference has only notes. Benny > > Note: Previously I used Event Attributes for this, but I'm changing my > mind. > > 3. For cyberspace sources, add a Source Reference attribute to hold > the URL of the source (e.g. a PDF file at a government archive > website) > > 4. When possible and practical, save copies of documents on my > computer and create Media objects for them. Link the Media Objects to > the Source gallery. (This way the Source object will have links to > every document I have from that source.) > > Note: Previously I used the Event gallery for this, but I'm changing my > mind. > > ***Question*** Should I store the URL to the archive in the Media > Object Attributes as well? But then there will be two copies of the > URL, since I saved one in step 3! Hmmmm.... > > ***Question 2*** Do you put the same Source info for the Media object? > But then you have it twice...once for the Event and once for the > Media object. > > 5. Source objects have one or more Repositories. > > On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: > > +1 > > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png > > > > > > --- En date de : Mer 24.11.10, Mary Lynch < > mar...@bl...> a écrit : > > > >> De: Mary Lynch <mar...@bl...> > >> Objet: Re: [Gramps-users] Where do you store web links for sources > >> À: gra...@li... > >> Date: Mercredi 24 novembre 2010, 20h30 > >> I would consider the web-access > >> portals to be repositories, and create a > >> repository for each website. The repository editor dialog > >> has a tab for > >> internet, under which you can add any URL's you want to > >> store for the > >> site. You can add more than one repository to a source. > >> > >> Mary Lynch > >> > >> On 24/11/2010 16:51, Gerald Britton wrote: > >> > Hi all -- I'm looking for some input as to the best > >> place to store web > >> > links for sources. Consider this scenario: > >> > > >> > 1. You have a source (say, a marriage register) > >> > 2. The source has one or more web-access portals > >> > 3. You want to store the link(s) to the (those) > >> portal(s) in the source record. > >> > > >> > You could do this: > >> > > >> > 1. Create your source > >> > 2. Add a Note to the source, with the link to the > >> portal (possibly one > >> > per portal) > >> > > >> > or: > >> > > >> > 2. Using the data tab, add one or more items with keys > >> like (URL, Web > >> > Link, ...) with the value being the URL > >> > > >> > >> > >> > ------------------------------------------------------------------------------ > >> Increase Visibility of Your 3D Game App & Earn a Chance > >> To Win $500! > >> Tap into the largest installed PC base & get more eyes > >> on your game by > >> optimizing for Intel(R) Graphics Technology. Get started > >> today with the > >> Intel(R) Software Partner Program. Five $500 cash prizes > >> are up for grabs. > >> http://p.sf.net/sfu/intelisp-dev2dev > >> _______________________________________________ > >> Gramps-users mailing list > >> Gra...@li... > >> https://lists.sourceforge.net/lists/listinfo/gramps-users > >> > > > > > > > > > > > ------------------------------------------------------------------------------ > > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > > Tap into the largest installed PC base & get more eyes on your game by > > optimizing for Intel(R) Graphics Technology. Get started today with the > > Intel(R) Software Partner Program. Five $500 cash prizes are up for > grabs. > > http://p.sf.net/sfu/intelisp-dev2dev > > _______________________________________________ > > Gramps-users mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-users > > > > > > -- > Gerald Britton > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Gerald B. <ger...@gm...> - 2010-11-26 20:06:59
|
On Fri, Nov 26, 2010 at 2:33 PM, Benny Malengier <ben...@gm...> wrote: > > > 2010/11/26 Gerald Britton <ger...@gm...> >> >> Thanks all for the input. I believe that this is the approach I >> should use: (Looking for comments and answers to the two questions >> below.) >> >> 1. An Event (such as birth, death, marriage, census etc.) will have >> one or more supporting Source references (each of which refers to a >> Source object) >> >> 2. Use Source Reference attributes to collect data not in standard >> fields. (e.g. Certificate number) > > What is a source reference attribute? There is only source data. The source > reference has only notes. Source attribute > > Benny >> >> Note: Previously I used Event Attributes for this, but I'm changing my >> mind. >> >> 3. For cyberspace sources, add a Source Reference attribute to hold >> the URL of the source (e.g. a PDF file at a government archive >> website) >> >> 4. When possible and practical, save copies of documents on my >> computer and create Media objects for them. Link the Media Objects to >> the Source gallery. (This way the Source object will have links to >> every document I have from that source.) >> >> Note: Previously I used the Event gallery for this, but I'm changing my >> mind. >> >> ***Question*** Should I store the URL to the archive in the Media >> Object Attributes as well? But then there will be two copies of the >> URL, since I saved one in step 3! Hmmmm.... >> >> ***Question 2*** Do you put the same Source info for the Media object? >> But then you have it twice...once for the Event and once for the >> Media object. >> >> 5. Source objects have one or more Repositories. >> >> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: >> > +1 >> > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png >> > >> > >> > --- En date de : Mer 24.11.10, Mary Lynch >> > <mar...@bl...> a écrit : >> > >> >> De: Mary Lynch <mar...@bl...> >> >> Objet: Re: [Gramps-users] Where do you store web links for sources >> >> À: gra...@li... >> >> Date: Mercredi 24 novembre 2010, 20h30 >> >> I would consider the web-access >> >> portals to be repositories, and create a >> >> repository for each website. The repository editor dialog >> >> has a tab for >> >> internet, under which you can add any URL's you want to >> >> store for the >> >> site. You can add more than one repository to a source. >> >> >> >> Mary Lynch >> >> >> >> On 24/11/2010 16:51, Gerald Britton wrote: >> >> > Hi all -- I'm looking for some input as to the best >> >> place to store web >> >> > links for sources. Consider this scenario: >> >> > >> >> > 1. You have a source (say, a marriage register) >> >> > 2. The source has one or more web-access portals >> >> > 3. You want to store the link(s) to the (those) >> >> portal(s) in the source record. >> >> > >> >> > You could do this: >> >> > >> >> > 1. Create your source >> >> > 2. Add a Note to the source, with the link to the >> >> portal (possibly one >> >> > per portal) >> >> > >> >> > or: >> >> > >> >> > 2. Using the data tab, add one or more items with keys >> >> like (URL, Web >> >> > Link, ...) with the value being the URL >> >> > >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Increase Visibility of Your 3D Game App & Earn a Chance >> >> To Win $500! >> >> Tap into the largest installed PC base & get more eyes >> >> on your game by >> >> optimizing for Intel(R) Graphics Technology. Get started >> >> today with the >> >> Intel(R) Software Partner Program. Five $500 cash prizes >> >> are up for grabs. >> >> http://p.sf.net/sfu/intelisp-dev2dev >> >> _______________________________________________ >> >> Gramps-users mailing list >> >> Gra...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> >> >> > >> > >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >> > Tap into the largest installed PC base & get more eyes on your game by >> > optimizing for Intel(R) Graphics Technology. Get started today with the >> > Intel(R) Software Partner Program. Five $500 cash prizes are up for >> > grabs. >> > http://p.sf.net/sfu/intelisp-dev2dev >> > _______________________________________________ >> > Gramps-users mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-users >> > >> >> >> >> -- >> Gerald Britton >> >> >> ------------------------------------------------------------------------------ >> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >> Tap into the largest installed PC base & get more eyes on your game by >> optimizing for Intel(R) Graphics Technology. Get started today with the >> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >> http://p.sf.net/sfu/intelisp-dev2dev >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users > > -- Gerald Britton |
From: Gerald B. <ger...@gm...> - 2010-11-26 20:33:08
|
[snip] >> What is a source reference attribute? There is only source data. The source >> reference has only notes. > > Source attribute No, that won't work. Back to event attributes, I guess, but that's really not what I want. Say that you have a source for a census. It's a few rolls of microfilm. Each person in your tree that is in the census will share that source. However, for each person, you want to save all the good pieces of info that are in the Census. So, you clearly can't use source attributes, since they are shared. I can use Event Attributes (and have been doing that). However, I noticed that the census gramplet uses the Event Reference Attributes for this. Yet, really those are not attributes of the event (reference), since the source(s) just document the event. However, there are no attributes on the source reference, so there's really no other place at the moment. > >> >> Benny >>> >>> Note: Previously I used Event Attributes for this, but I'm changing my >>> mind. >>> >>> 3. For cyberspace sources, add a Source Reference attribute to hold >>> the URL of the source (e.g. a PDF file at a government archive >>> website) >>> >>> 4. When possible and practical, save copies of documents on my >>> computer and create Media objects for them. Link the Media Objects to >>> the Source gallery. (This way the Source object will have links to >>> every document I have from that source.) >>> >>> Note: Previously I used the Event gallery for this, but I'm changing my >>> mind. >>> >>> ***Question*** Should I store the URL to the archive in the Media >>> Object Attributes as well? But then there will be two copies of the >>> URL, since I saved one in step 3! Hmmmm.... >>> >>> ***Question 2*** Do you put the same Source info for the Media object? >>> But then you have it twice...once for the Event and once for the >>> Media object. >>> >>> 5. Source objects have one or more Repositories. >>> >>> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: >>> > +1 >>> > http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png >>> > >>> > >>> > --- En date de : Mer 24.11.10, Mary Lynch >>> > <mar...@bl...> a écrit : >>> > >>> >> De: Mary Lynch <mar...@bl...> >>> >> Objet: Re: [Gramps-users] Where do you store web links for sources >>> >> À: gra...@li... >>> >> Date: Mercredi 24 novembre 2010, 20h30 >>> >> I would consider the web-access >>> >> portals to be repositories, and create a >>> >> repository for each website. The repository editor dialog >>> >> has a tab for >>> >> internet, under which you can add any URL's you want to >>> >> store for the >>> >> site. You can add more than one repository to a source. >>> >> >>> >> Mary Lynch >>> >> >>> >> On 24/11/2010 16:51, Gerald Britton wrote: >>> >> > Hi all -- I'm looking for some input as to the best >>> >> place to store web >>> >> > links for sources. Consider this scenario: >>> >> > >>> >> > 1. You have a source (say, a marriage register) >>> >> > 2. The source has one or more web-access portals >>> >> > 3. You want to store the link(s) to the (those) >>> >> portal(s) in the source record. >>> >> > >>> >> > You could do this: >>> >> > >>> >> > 1. Create your source >>> >> > 2. Add a Note to the source, with the link to the >>> >> portal (possibly one >>> >> > per portal) >>> >> > >>> >> > or: >>> >> > >>> >> > 2. Using the data tab, add one or more items with keys >>> >> like (URL, Web >>> >> > Link, ...) with the value being the URL >>> >> > >>> >> >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> Increase Visibility of Your 3D Game App & Earn a Chance >>> >> To Win $500! >>> >> Tap into the largest installed PC base & get more eyes >>> >> on your game by >>> >> optimizing for Intel(R) Graphics Technology. Get started >>> >> today with the >>> >> Intel(R) Software Partner Program. Five $500 cash prizes >>> >> are up for grabs. >>> >> http://p.sf.net/sfu/intelisp-dev2dev >>> >> _______________________________________________ >>> >> Gramps-users mailing list >>> >> Gra...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >> >>> > >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>> > Tap into the largest installed PC base & get more eyes on your game by >>> > optimizing for Intel(R) Graphics Technology. Get started today with the >>> > Intel(R) Software Partner Program. Five $500 cash prizes are up for >>> > grabs. >>> > http://p.sf.net/sfu/intelisp-dev2dev >>> > _______________________________________________ >>> > Gramps-users mailing list >>> > Gra...@li... >>> > https://lists.sourceforge.net/lists/listinfo/gramps-users >>> > >>> >>> >>> >>> -- >>> Gerald Britton >>> >>> >>> ------------------------------------------------------------------------------ >>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>> Tap into the largest installed PC base & get more eyes on your game by >>> optimizing for Intel(R) Graphics Technology. Get started today with the >>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >>> http://p.sf.net/sfu/intelisp-dev2dev >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >> >> > > > > -- > Gerald Britton > -- Gerald Britton |
From: Nick H. <nic...@ho...> - 2010-11-30 00:32:07
|
Gerald, I have a couple of comments (below) that are specific to census data. Gerald Britton wrote: > On Sat, Nov 27, 2010 at 4:15 AM, Benny Malengier > <ben...@gm...> wrote: > >> 2010/11/26 Gerald Britton <ger...@gm...> >> >>> Thanks all for the input. I believe that this is the approach I >>> should use: (Looking for comments and answers to the two questions >>> below.) >>> >>> 1. An Event (such as birth, death, marriage, census etc.) will have >>> one or more supporting Source references (each of which refers to a >>> Source object) >>> >>> 2. Use Source Reference attributes to collect data not in standard >>> fields. (e.g. Certificate number) >>> >> Data from the source, should be stored in the source. For certificates, you >> can make one source per certificate, and give a title which refers to the >> book: Title: Baptize registry St Lawrence - John Do >> Many people work like this and it works great. >> If you create one big source, you must use an organization scheme inside the >> source: start pieces of John Do with the entry number. >> > > This seems to be a workaround for gramps limitations (or our adherence > to GEDCOM, more likely). If we had source reference attributes, this > would be easier, I think. Also, for censuses it doesn't make > sense(s...pun intended!) to have one source per...what? I started > down this road while adding Canadian censuses to the Census Gramplet. > The approach that plugin uses is to put all the data from one line of > a census in the event reference attributes for that event for that > individual. There is one source per census. Some Canadian censuses > have as many as 140 pieces of data per individual (!) So there is one > event (the census taker visits the household) shared by all members of > the household and an event reference for each member (even those > absent at the time) holding the specific data collected at that time. > > The problem I see is that event (reference) attributes are not the the > ideal/logical place to store things like whether the house was brick > or frame, how many pigs you had or the census-taker's comment that the > 19-year-old daughter was very pretty. The idea was to put this type of data as attributes of the census event object rather than attributes of the event reference objects. Recording data such as "whether the house was brick or frame, how many pigs" as attributes on the event record is on my ToDo list. > That is, that information > existed before the event and continues after the event and would exist > even if a census was never taken. So, I conclude that the event > (reference) attributes is not the best choice. However, it appears to > be the only practical choice in the current implementation. OTOH if > we had attributes on source references, this is where I believe such > data should go. > > >> Then the source ref contains the ref number, and you know what to look for >> in the source. This approach is the more 'official' one. >> > > I have done something like that so far, but in light of my work on > censuses, I now see its limitations. I don't want to go back to the > source to see how many acres of land my ggg.grandfather told the > census taker he had in 1881 -- I want to record it in the database as > an attribute found in the census. > > >> Data of the event, you learn from the source, should be part of the event, >> with a source attached to it. You can repeat that info in the source if that >> is what you like. >> > > This where I disagree I guess, since (in my mind) the event doesn't > determine the data. The event caused the data to be recorded on the > source. Also, conflicts are possible between two different sources > for the same event (doesn't usually apply to censuses). Yes, for censuses there will be a one-to-one correspondence between the source and the census event. Sources provide the data to be recorded against people and events. The data itself should not be recorded on the source object. Where the source provides data for one particular person for an event with multiple participants, then the event reference object for the person/event seems a reasonable place to store the data. Nick. > Most often in > the name (misspellings, abbreviations, etc.) but other things as > well. Ideally, I'd want to record what I find in the sources and > afterwards try to determine what is most likely the true (or best) > information. > > >>> Note: Previously I used Event Attributes for this, but I'm changing my >>> mind. >>> >>> 3. For cyberspace sources, add a Source Reference attribute to hold >>> the URL of the source (e.g. a PDF file at a government archive >>> website) >>> >>> 4. When possible and practical, save copies of documents on my >>> computer and create Media objects for them. Link the Media Objects to >>> the Source gallery. (This way the Source object will have links to >>> every document I have from that source.) >>> >>> Note: Previously I used the Event gallery for this, but I'm changing my >>> mind. >>> >>> ***Question*** Should I store the URL to the archive in the Media >>> Object Attributes as well? But then there will be two copies of the >>> URL, since I saved one in step 3! Hmmmm.... >>> >> I would not do that. The repository is sufficient. You will in the future >> find a better repository (better scans, cheaper, ...), but the source will >> remain the same. >> >>> ***Question 2*** Do you put the same Source info for the Media object? >>> But then you have it twice...once for the Event and once for the >>> Media object. >>> >> Sharing does not hurt. I add the source to as much as relevant. >> >> Note that the above problem with sources comes from the fact we track the >> GEDCOM implementation. There have been ideas to work with source parts. So >> an entry in a source relevant would be a source part, and the source view >> becomes a treeview. There are programs who use that approach, but somebody >> should put in the effort to see what is needed to do that, so also, how we >> import/export to GEDCOM in that case. >> > > Something to think about.... > >> Benny >> >>> 5. Source objects have one or more Repositories. >>> >>> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: >>> >>>> +1 >>>> http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png >>>> >>>> >>>> --- En date de : Mer 24.11.10, Mary Lynch >>>> <mar...@bl...> a écrit : >>>> >>>> >>>>> De: Mary Lynch <mar...@bl...> >>>>> Objet: Re: [Gramps-users] Where do you store web links for sources >>>>> À: gra...@li... >>>>> Date: Mercredi 24 novembre 2010, 20h30 >>>>> I would consider the web-access >>>>> portals to be repositories, and create a >>>>> repository for each website. The repository editor dialog >>>>> has a tab for >>>>> internet, under which you can add any URL's you want to >>>>> store for the >>>>> site. You can add more than one repository to a source. >>>>> >>>>> Mary Lynch >>>>> >>>>> On 24/11/2010 16:51, Gerald Britton wrote: >>>>> >>>>>> Hi all -- I'm looking for some input as to the best >>>>>> >>>>> place to store web >>>>> >>>>>> links for sources. Consider this scenario: >>>>>> >>>>>> 1. You have a source (say, a marriage register) >>>>>> 2. The source has one or more web-access portals >>>>>> 3. You want to store the link(s) to the (those) >>>>>> >>>>> portal(s) in the source record. >>>>> >>>>>> You could do this: >>>>>> >>>>>> 1. Create your source >>>>>> 2. Add a Note to the source, with the link to the >>>>>> >>>>> portal (possibly one >>>>> >>>>>> per portal) >>>>>> >>>>>> or: >>>>>> >>>>>> 2. Using the data tab, add one or more items with keys >>>>>> >>>>> like (URL, Web >>>>> >>>>>> Link, ...) with the value being the URL >>>>>> >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Increase Visibility of Your 3D Game App & Earn a Chance >>>>> To Win $500! >>>>> Tap into the largest installed PC base & get more eyes >>>>> on your game by >>>>> optimizing for Intel(R) Graphics Technology. Get started >>>>> today with the >>>>> Intel(R) Software Partner Program. Five $500 cash prizes >>>>> are up for grabs. >>>>> http://p.sf.net/sfu/intelisp-dev2dev >>>>> _______________________________________________ >>>>> Gramps-users mailing list >>>>> Gra...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>>> >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>>> Tap into the largest installed PC base & get more eyes on your game by >>>> optimizing for Intel(R) Graphics Technology. Get started today with the >>>> Intel(R) Software Partner Program. Five $500 cash prizes are up for >>>> grabs. >>>> http://p.sf.net/sfu/intelisp-dev2dev >>>> _______________________________________________ >>>> Gramps-users mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>> >>>> >>> >>> -- >>> Gerald Britton >>> >>> >>> ------------------------------------------------------------------------------ >>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>> Tap into the largest installed PC base & get more eyes on your game by >>> optimizing for Intel(R) Graphics Technology. Get started today with the >>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >>> http://p.sf.net/sfu/intelisp-dev2dev >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >> > > > > |
From: Gerald B. <ger...@gm...> - 2010-11-30 03:24:15
|
On Mon, Nov 29, 2010 at 7:31 PM, Nick Hall <nic...@ho...> wrote: > Gerald, > > I have a couple of comments (below) that are specific to census data. > > > Gerald Britton wrote: >> >> On Sat, Nov 27, 2010 at 4:15 AM, Benny Malengier >> <ben...@gm...> wrote: >> >>> >>> 2010/11/26 Gerald Britton <ger...@gm...> >>> >>>> >>>> Thanks all for the input. I believe that this is the approach I >>>> should use: (Looking for comments and answers to the two questions >>>> below.) >>>> >>>> 1. An Event (such as birth, death, marriage, census etc.) will have >>>> one or more supporting Source references (each of which refers to a >>>> Source object) >>>> >>>> 2. Use Source Reference attributes to collect data not in standard >>>> fields. (e.g. Certificate number) >>>> >>> >>> Data from the source, should be stored in the source. For certificates, >>> you >>> can make one source per certificate, and give a title which refers to the >>> book: Title: Baptize registry St Lawrence - John Do >>> Many people work like this and it works great. >>> If you create one big source, you must use an organization scheme inside >>> the >>> source: start pieces of John Do with the entry number. >>> >> >> This seems to be a workaround for gramps limitations (or our adherence >> to GEDCOM, more likely). If we had source reference attributes, this >> would be easier, I think. Also, for censuses it doesn't make >> sense(s...pun intended!) to have one source per...what? I started >> down this road while adding Canadian censuses to the Census Gramplet. >> The approach that plugin uses is to put all the data from one line of >> a census in the event reference attributes for that event for that >> individual. There is one source per census. Some Canadian censuses >> have as many as 140 pieces of data per individual (!) So there is one >> event (the census taker visits the household) shared by all members of >> the household and an event reference for each member (even those >> absent at the time) holding the specific data collected at that time. >> >> The problem I see is that event (reference) attributes are not the the >> ideal/logical place to store things like whether the house was brick >> or frame, how many pigs you had or the census-taker's comment that the >> 19-year-old daughter was very pretty. > > The idea was to put this type of data as attributes of the census event > object rather than attributes of the event reference objects. > > Recording data such as "whether the house was brick or frame, how many pigs" > as attributes on the event record is on my ToDo list. > > >> That is, that information >> existed before the event and continues after the event and would exist >> even if a census was never taken. So, I conclude that the event >> (reference) attributes is not the best choice. However, it appears to >> be the only practical choice in the current implementation. OTOH if >> we had attributes on source references, this is where I believe such >> data should go. >> >> >>> >>> Then the source ref contains the ref number, and you know what to look >>> for >>> in the source. This approach is the more 'official' one. >>> >> >> I have done something like that so far, but in light of my work on >> censuses, I now see its limitations. I don't want to go back to the >> source to see how many acres of land my ggg.grandfather told the >> census taker he had in 1881 -- I want to record it in the database as >> an attribute found in the census. >> >> >>> >>> Data of the event, you learn from the source, should be part of the >>> event, >>> with a source attached to it. You can repeat that info in the source if >>> that >>> is what you like. >>> >> >> This where I disagree I guess, since (in my mind) the event doesn't >> determine the data. The event caused the data to be recorded on the >> source. Also, conflicts are possible between two different sources >> for the same event (doesn't usually apply to censuses). > > Yes, for censuses there will be a one-to-one correspondence between the > source and the census event. > > Sources provide the data to be recorded against people and events. The data > itself should not be recorded on the source object. Yes, we're stuck with that because of current limitations of the source object > > Where the source provides data for one particular person for an event with > multiple participants, then the event reference object for the person/event > seems a reasonable place to store the data. There's really no other option at present, but see the discussion I've opened on the topic > > > Nick. > > >> Most often in >> the name (misspellings, abbreviations, etc.) but other things as >> well. Ideally, I'd want to record what I find in the sources and >> afterwards try to determine what is most likely the true (or best) >> information. >> >> >>>> >>>> Note: Previously I used Event Attributes for this, but I'm changing my >>>> mind. >>>> >>>> 3. For cyberspace sources, add a Source Reference attribute to hold >>>> the URL of the source (e.g. a PDF file at a government archive >>>> website) >>>> >>>> 4. When possible and practical, save copies of documents on my >>>> computer and create Media objects for them. Link the Media Objects to >>>> the Source gallery. (This way the Source object will have links to >>>> every document I have from that source.) >>>> >>>> Note: Previously I used the Event gallery for this, but I'm changing my >>>> mind. >>>> >>>> ***Question*** Should I store the URL to the archive in the Media >>>> Object Attributes as well? But then there will be two copies of the >>>> URL, since I saved one in step 3! Hmmmm.... >>>> >>> >>> I would not do that. The repository is sufficient. You will in the future >>> find a better repository (better scans, cheaper, ...), but the source >>> will >>> remain the same. >>> >>>> >>>> ***Question 2*** Do you put the same Source info for the Media object? >>>> But then you have it twice...once for the Event and once for the >>>> Media object. >>>> >>> >>> Sharing does not hurt. I add the source to as much as relevant. >>> >>> Note that the above problem with sources comes from the fact we track the >>> GEDCOM implementation. There have been ideas to work with source parts. >>> So >>> an entry in a source relevant would be a source part, and the source view >>> becomes a treeview. There are programs who use that approach, but >>> somebody >>> should put in the effort to see what is needed to do that, so also, how >>> we >>> import/export to GEDCOM in that case. >>> >> >> Something to think about.... >> >>> >>> Benny >>> >>>> >>>> 5. Source objects have one or more Repositories. >>>> >>>> On Thu, Nov 25, 2010 at 4:58 AM, jerome <rom...@ya...> wrote: >>>> >>>>> >>>>> +1 >>>>> http://gramps-project.org/wiki/images/2/22/Nouveau_d%C3%A9p%C3%B4t.png >>>>> >>>>> >>>>> --- En date de : Mer 24.11.10, Mary Lynch >>>>> <mar...@bl...> a écrit : >>>>> >>>>> >>>>>> >>>>>> De: Mary Lynch <mar...@bl...> >>>>>> Objet: Re: [Gramps-users] Where do you store web links for sources >>>>>> À: gra...@li... >>>>>> Date: Mercredi 24 novembre 2010, 20h30 >>>>>> I would consider the web-access >>>>>> portals to be repositories, and create a >>>>>> repository for each website. The repository editor dialog >>>>>> has a tab for >>>>>> internet, under which you can add any URL's you want to >>>>>> store for the >>>>>> site. You can add more than one repository to a source. >>>>>> >>>>>> Mary Lynch >>>>>> >>>>>> On 24/11/2010 16:51, Gerald Britton wrote: >>>>>> >>>>>>> >>>>>>> Hi all -- I'm looking for some input as to the best >>>>>>> >>>>>> >>>>>> place to store web >>>>>> >>>>>>> >>>>>>> links for sources. Consider this scenario: >>>>>>> >>>>>>> 1. You have a source (say, a marriage register) >>>>>>> 2. The source has one or more web-access portals >>>>>>> 3. You want to store the link(s) to the (those) >>>>>>> >>>>>> >>>>>> portal(s) in the source record. >>>>>> >>>>>>> >>>>>>> You could do this: >>>>>>> >>>>>>> 1. Create your source >>>>>>> 2. Add a Note to the source, with the link to the >>>>>>> >>>>>> >>>>>> portal (possibly one >>>>>> >>>>>>> >>>>>>> per portal) >>>>>>> >>>>>>> or: >>>>>>> >>>>>>> 2. Using the data tab, add one or more items with keys >>>>>>> >>>>>> >>>>>> like (URL, Web >>>>>> >>>>>>> >>>>>>> Link, ...) with the value being the URL >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Increase Visibility of Your 3D Game App & Earn a Chance >>>>>> To Win $500! >>>>>> Tap into the largest installed PC base & get more eyes >>>>>> on your game by >>>>>> optimizing for Intel(R) Graphics Technology. Get started >>>>>> today with the >>>>>> Intel(R) Software Partner Program. Five $500 cash prizes >>>>>> are up for grabs. >>>>>> http://p.sf.net/sfu/intelisp-dev2dev >>>>>> _______________________________________________ >>>>>> Gramps-users mailing list >>>>>> Gra...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>>>> Tap into the largest installed PC base & get more eyes on your game by >>>>> optimizing for Intel(R) Graphics Technology. Get started today with the >>>>> Intel(R) Software Partner Program. Five $500 cash prizes are up for >>>>> grabs. >>>>> http://p.sf.net/sfu/intelisp-dev2dev >>>>> _______________________________________________ >>>>> Gramps-users mailing list >>>>> Gra...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>>> >>>>> >>>> >>>> -- >>>> Gerald Britton >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! >>>> Tap into the largest installed PC base & get more eyes on your game by >>>> optimizing for Intel(R) Graphics Technology. Get started today with the >>>> Intel(R) Software Partner Program. Five $500 cash prizes are up for >>>> grabs. >>>> http://p.sf.net/sfu/intelisp-dev2dev >>>> _______________________________________________ >>>> Gramps-users mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>> >>> >>> >> >> >> >> > -- Gerald Britton |
From: Helge@Gramps <Helge.Privat@Kabelmail.de> - 2010-11-24 23:28:29
|
Here is the way which works fine for me. Please keep in mind, for me is each entry of register (e.g. a marriage register) one source! That's why, I want to have the shortest access to the copy or the picture or the PDF of each relevant entry within the marriage register. In this case I do: - I always generate a PDF from any web information concerning my research (may be the information will be lost in WEB next time) - the PDF file will be connected to a Media entry in Gramps - the Media entry will be connected to the Gallery tab of a Source entry (may be I add an additional text file to the Gallery with the transcribed text, e.g. from the old 'Sütterlin' to modern Latin characters.) - on the Note tab of the Source editor I place the complete link to the information printed to PDF --> up to Gramps 3.2.5 there is no way to use the link direct from the notes entry we have to use copy-paste into the browser for upcoming Gramps versions (may be in Gramps 3.3; today in the developer version from Trunk in SVN only) there is the possibility to define direct web links in notes!! --> I always uses Notes (no data, no attributes) for ALL additional information to have always one and the same logical place to store such additional information. - a Repository entry (connected to this Source entry) collects the information of the main web page (the portal) - the main link to the web page system the PDF information comes from (the portal, e.g. www.familySearch.org) will be used on the Internet tab of the Repository entry --> the Repository entry will be used for all Source entries collected from the some web page system DONE -Helge -- View this message in context: http://gramps.1791082.n4.nabble.com/Where-do-you-store-web-links-for-sources-tp3057695p3058250.html Sent from the GRAMPS - User mailing list archive at Nabble.com. |
From: jerome <rom...@ya...> - 2010-11-25 09:00:04
|
Hi, Note, for search links (urls), Doug made some addons like this 'pack': http://gramps-addons.svn.sourceforge.net/viewvc/gramps-addons/trunk/contrib/USWebConnectPack/ Maybe object could be a source or a note on the pack? Jérôme --- En date de : Mer 24.11.10, Gerald Britton <ger...@gm...> a écrit : > De: Gerald Britton <ger...@gm...> > Objet: [Gramps-users] Where do you store web links for sources > À: "Gramps users" <gra...@li...> > Date: Mercredi 24 novembre 2010, 17h51 > Hi all -- I'm looking for some input > as to the best place to store web > links for sources. Consider this scenario: > > 1. You have a source (say, a marriage register) > 2. The source has one or more web-access portals > 3. You want to store the link(s) to the (those) portal(s) > in the source record. > > You could do this: > > 1. Create your source > 2. Add a Note to the source, with the link to the portal > (possibly one > per portal) > > or: > > 2. Using the data tab, add one or more items with keys like > (URL, Web > Link, ...) with the value being the URL > > -- > Gerald Britton > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance > To Win $500! > Tap into the largest installed PC base & get more eyes > on your game by > optimizing for Intel(R) Graphics Technology. Get started > today with the > Intel(R) Software Partner Program. Five $500 cash prizes > are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |