Difference between revisions of "Attributes in Gramps"
m (Protected "Attributes in GRAMPS" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))) |
m (Gramps) |
||
(6 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | {{languages| | + | {{languages|Attributes_in_Gramps}} |
− | “The thinking behind dividing things into [[Events in | + | “The thinking behind dividing things into [[Events in Gramps|events]] and '''attributes''' was the following: |
:The attributes are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a person/family/etc. | :The attributes are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a person/family/etc. | ||
Line 9: | Line 9: | ||
Does it make sense? I know this does not correspond 100% with | Does it make sense? I know this does not correspond 100% with | ||
GEDCOM, but we try to do what makes sense rather than just | GEDCOM, but we try to do what makes sense rather than just | ||
− | implementing a poorly written standard.” [http:// | + | implementing a poorly written standard.” [http://sourceforge.net/mailarchive/message.php?msg_id=10070987] -- Gramps-user mailing list |
In case the attribute needed is not present in the predefined selection list, it can be defined by typing its name in the attribute name field. There is no clear boundary between attributes and events. Some will prefer having "Occupation" as an attribute, with no timespan; others, or in other situations, might find using an event more convenient. | In case the attribute needed is not present in the predefined selection list, it can be defined by typing its name in the attribute name field. There is no clear boundary between attributes and events. Some will prefer having "Occupation" as an attribute, with no timespan; others, or in other situations, might find using an event more convenient. | ||
Line 15: | Line 15: | ||
== To Gramps attributes in general == | == To Gramps attributes in general == | ||
− | * http:// | + | * http://sourceforge.net/mailarchive/message.php?msg_id=10070976 |
− | * http:// | + | * http://sourceforge.net/mailarchive/message.php?msg_id=22940649 |
− | [[Category: | + | [[Category:Gramps terminology]] |
[[Category:Translators/Categories]] | [[Category:Translators/Categories]] | ||
[[Category:Tutorials]] | [[Category:Tutorials]] |
Revision as of 07:51, 25 January 2013
“The thinking behind dividing things into events and attributes was the following:
- The attributes are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a person/family/etc.
- In contrast, the events have a time frame associated with them. It does not have to be a fixed date, can be e.g. a span. So it is not unheard of people changing religion, property, and residence, etc. Each of those can be associated with the time period, and there can be many of the same type.
Does it make sense? I know this does not correspond 100% with GEDCOM, but we try to do what makes sense rather than just implementing a poorly written standard.” [1] -- Gramps-user mailing list
In case the attribute needed is not present in the predefined selection list, it can be defined by typing its name in the attribute name field. There is no clear boundary between attributes and events. Some will prefer having "Occupation" as an attribute, with no timespan; others, or in other situations, might find using an event more convenient.