Difference between revisions of "Attributes in Gramps"

From Gramps
m
m (list predefined Attribute types)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{languages|Attributes_in_Gramps}}
 
{{languages|Attributes_in_Gramps}}
 
{{stub}}
 
{{stub}}
''The thinking behind dividing things into [[Events in Gramps|events]] and '''attributes''' was the following:
+
'''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.
+
:In contrast, the [[Events in Gramps|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.
  
: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.
+
[[File:AttributeEditor-dialog-default-60.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Attribute Editor" - dialog - default]]
 
 
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.'' [http://sourceforge.net/mailarchive/message.php?msg_id=10070987 Re: (Gramps-users) Events & Attributes, and column widths.] From: Alex Roitman - 2006
 
  
 
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.
  
* The advantage of an attribute is that you can attach source citations to it.
+
* The advantage of an attribute is that you can attach source citations to it as Tags are not really intended to store genealogical data.  
: Tags are not really intended to store genealogical data.  
 
  
 
== Strategies for leveraging Attributes ==
 
== Strategies for leveraging Attributes ==
Line 19: Line 16:
 
*Customize reports to include leverage [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_2#Attributes|Attributes]]. Learn to use [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_2#Rules_for_groups|Rules for groups]] to avoid the "underscored blank" placeholder for when an Attribute is absent.
 
*Customize reports to include leverage [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_2#Attributes|Attributes]]. Learn to use [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_2#Rules_for_groups|Rules for groups]] to avoid the "underscored blank" placeholder for when an Attribute is absent.
  
== Discussions about Gramps attributes in general ==
+
=== Predefined Attribute types ===
 +
Some predefined attributes are present because they are defined tags in the GEDCOM standard.
  
 +
{| class="wikitable"
 +
|+ GEDCOM Attribute Subfields and Tags
 +
! Attribute subfield !! Description !! Tag type
 +
|-
 +
| Age || How old a person was at the time of an event, subordinate to events like BIRT or DEAT. || Subordinate value (AGE)
 +
|-
 +
| Agency || Responsible institution or person for an event or record, under events like CENS or OCCU. || Event tag (AGNC)
 +
|-
 +
| Caste || Social or cultural strata of an individual. || Individual attribute (CAST)
 +
|-
 +
| Cause || Cause of death or event, subordinate to DEAT or similar. || Event subordinate (CAUS)
 +
|-
 +
| Description || Free-text description of physical characteristics or attributes. || Individual attribute (DSCR)
 +
|-
 +
| Father Age || Father's age at child's event (e.g., birth); uses generic AGE in role context. || Program-level (AGE with role)
 +
|-
 +
| Identification Number || Personal ID or registry number. || Individual attribute (IDNO)
 +
|-
 +
| Mother Age || Mother's age at child's event; uses generic AGE in role context. || Program-level (AGE with role)
 +
|-
 +
| National Origin || Nationality or national origin. || Individual attribute (NATI)
 +
|-
 +
| Nickname || Familiar or descriptive name. || Name tag (NICK)
 +
|-
 +
| Number of Children || Count of known children. || Individual/Family attribute (NCHI)
 +
|-
 +
| Occupation || Trade or profession. || Individual attribute (OCCU)
 +
|-
 +
| Social Security Number || National social insurance ID (e.g., SSN). || Individual attribute (SSN)
 +
|-
 +
| Time || Time of day for an event. || Date subordinate (TIME)
 +
|-
 +
| Unknown || Not a standard tag; used as value or custom _UNKNOWN extension. || Custom/Enumeration (_UNK)
 +
|-
 +
| Witness || Person observing an event; custom or role-based in GEDCOM 7. || Custom/Role (_WITN or participant)
 +
|}
 +
 +
== See also ==
 +
* [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Attributes]]
 +
* [http://sourceforge.net/mailarchive/message.php?msg_id=10070987 Re: (Gramps-users) Events & Attributes, and column widths.] From: Alex Roitman - 2006 - ''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.''
 
* [https://sourceforge.net/p/gramps/mailman/message/10070976/ (Gramps-users) Events & Attributes, and column widths.] - 2006
 
* [https://sourceforge.net/p/gramps/mailman/message/10070976/ (Gramps-users) Events & Attributes, and column widths.] - 2006
 
* [https://sourceforge.net/p/gramps/mailman/message/22940649/ (Gramps-devel) Proposal for a GEDCOM change] - 2009
 
* [https://sourceforge.net/p/gramps/mailman/message/22940649/ (Gramps-devel) Proposal for a GEDCOM change] - 2009
 
* [https://sourceforge.net/p/gramps/mailman/message/33221254/ (Gramps-users) Re: No children, as opposed to unfound children?] - 2015
 
* [https://sourceforge.net/p/gramps/mailman/message/33221254/ (Gramps-users) Re: No children, as opposed to unfound children?] - 2015
 +
* {{bug|2051}}:  Attribute - possibility to set predefined values
 +
** {{bug|7441}}: Suppress printing of attributes with leading underscore in name eg: GEDCOM "_UID" tags
 +
* [https://wikipedia.org/wiki/Attribute_(computing) Attribute (computing)] From Wikipedia, the free encyclopedia
 +
* [https://wikipedia.org/wiki/Ontology_components#Attributes Attribute (knowledge representation)] From Wikipedia, the free encyclopedia
  
 
[[Category:Gramps terminology|A]]
 
[[Category:Gramps terminology|A]]

Latest revision as of 23:40, 1 January 2026

Gramps-notes.png

This article's content is incomplete or a placeholder stub.
Please update or expand this section.


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.
Fig. .1 "Attribute Editor" - dialog - default

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.

  • The advantage of an attribute is that you can attach source citations to it as Tags are not really intended to store genealogical data.

Strategies for leveraging Attributes

  • Use Custom Filters in combination the Set Attribute Tool (a third-party addon) to migrate data to Attributes. (Example: search Event descriptions for 'influenza', 'grippe', 'pneumonia'. Set an 'epidemic' attribute to 'possible')
  • Types Cleanup Tool (a third-party addon) Attributes are organized with Custom Types. Periodically consolidate Attributes labeled with synonymous (or misspelled) Custom Types.
  • Customize reports to include leverage Attributes. Learn to use Rules for groups to avoid the "underscored blank" placeholder for when an Attribute is absent.

Predefined Attribute types

Some predefined attributes are present because they are defined tags in the GEDCOM standard.

GEDCOM Attribute Subfields and Tags
Attribute subfield Description Tag type
Age How old a person was at the time of an event, subordinate to events like BIRT or DEAT. Subordinate value (AGE)
Agency Responsible institution or person for an event or record, under events like CENS or OCCU. Event tag (AGNC)
Caste Social or cultural strata of an individual. Individual attribute (CAST)
Cause Cause of death or event, subordinate to DEAT or similar. Event subordinate (CAUS)
Description Free-text description of physical characteristics or attributes. Individual attribute (DSCR)
Father Age Father's age at child's event (e.g., birth); uses generic AGE in role context. Program-level (AGE with role)
Identification Number Personal ID or registry number. Individual attribute (IDNO)
Mother Age Mother's age at child's event; uses generic AGE in role context. Program-level (AGE with role)
National Origin Nationality or national origin. Individual attribute (NATI)
Nickname Familiar or descriptive name. Name tag (NICK)
Number of Children Count of known children. Individual/Family attribute (NCHI)
Occupation Trade or profession. Individual attribute (OCCU)
Social Security Number National social insurance ID (e.g., SSN). Individual attribute (SSN)
Time Time of day for an event. Date subordinate (TIME)
Unknown Not a standard tag; used as value or custom _UNKNOWN extension. Custom/Enumeration (_UNK)
Witness Person observing an event; custom or role-based in GEDCOM 7. Custom/Role (_WITN or participant)

See also