Skip to main content

Drupal Family History Project - Content Types

Details on family history content types

Family History Item
fh_item This is the basic content type for the family history section. Fields used are:

  • Title: node title
  • Taxonomy: tag to vocabularies fh_topic, fh_person, fh_family, fh_content type, fh_free tags. fh_content type is required.
  • Body: regular node body.
  • Date: cck date field, for date of the item.
  • File: cck file field fh_pdffile. By default, these files are put in /sites/all/files/fhitems.
  • Path: Define alias through pathauto as /familyhistory/item/[title-raw]
  • Family History Photo
    fh_photo This is a special content type for photos related to family history. I added a separate content type rather than using the fh_item type since I needed different fields (thumbnail, etc) and the views are going to be different. It seemed easiest to create a new content type. Fields used are:

  • Title: node title
  • Taxonomy: tag to vocabularies fh_topic, fh_person, fh_family, fh_content type, fh_free tags. fh_content type is required.
  • Body: regular node body.
  • Date: cck date field, for date of the item.
  • File: cck imagefield. By default, these files are put in /sites/all/files/fhphotos.
  • Path: Define alias through pathauto as /familyhistory/photos/[title-raw]
  • Family History Person
    fh_person This is a content type for people. Fields include birthdate, date of death, etc, but the main idea is to embed a view in the node. Then I can use a view, filter by node fh_person, and when you click on a person, you see some basic facts plus the view. I decided to do it this way rather than a regular view with arguments because I wanted to add other fields and allow comments on the people. If this were a different type of site, where every person was a user on the system, you could use user profile, but in this case, since most of the people are ancestors, that doesn't work. Fields now are:

  • Title: node title. This is set to the exact same text as the person's name in the fh_person vocabulary.
  • Body: regular node body.
  • Birth: cck date field, field_fh_birthdate
  • Death: cck date field, field_fh_deathdate
  • Phpgedview link: cck link field to this person's profile on phpgedview at http://family.jeffmccoy.info. Field is field_fh_pgv_link
  • All Items: embedded view using viewfield, viewing all fh items tagged to this person. Field is field_fhview.
  • Photos: embedded view using viewfield, viewing all fh photos tagged to his person. Field is field_fh_photoview.
  • Drupal Family History Project - Content Types Family History Item fh_item This is the basic content type for the family history section. Fields used are:

    • Title: node title
    • Taxonomy: tag to vocabularies fh_topic, fh_person, fh_family, fh_content type, fh_free tags. fh_content type is required.
    • Body: regular node body.
    • Date: cck date field, for date of the item.
    • File: cck file field fh_pdffile. By default, these files are put in /sites/all/files/fhitems.
    • Path: Define alias through pathauto as /familyhistory/item/[title-raw]

    Family History Photo fh_photo This is a special content type for photos related to family history. I added a separate content type rather than using the fh_item type since I needed different fields (thumbnail, etc) and the views are going to be different. It seemed easiest to create a new content type. Fields used are:

    • Title: node title
    • Taxonomy: tag to vocabularies fh_topic, fh_person, fh_family, fh_content type, fh_free tags. fh_content type is required.
    • Body: regular node body.
    • Date: cck date field, for date of the item.
    • File: cck imagefield. By default, these files are put in /sites/all/files/fhphotos.
    • Path: Define alias through pathauto as /familyhistory/photos/[title-raw]

    Family History Person fh_person This is a content type for people. Fields include birthdate, date of death, etc, but the main idea is to embed a view in the node. Then I can use a view, filter by node fh_person, and when you click on a person, you see some basic facts plus the view. I decided to do it this way rather than a regular view with arguments because I wanted to add other fields and allow comments on the people. If this were a different type of site, where every person was a user on the system, you could use user profile, but in this case, since most of the people are ancestors, that doesn't work. Fields now are:

    • Title: node title. This is set to the exact same text as the person's name in the fh_person vocabulary.
    • Body: regular node body.
    • Birth: cck date field, field_fh_birthdate
    • Death: cck date field, field_fh_deathdate
    • Phpgedview link: cck link field to this person's profile on phpgedview at http://family.jeffmccoy.info. Field is field_fh_pgv_link
    • All Items: embedded view using viewfield, viewing all fh items tagged to this person. Field is field_fhview.
    • Photos: embedded view using viewfield, viewing all fh photos tagged to his person. Field is field_fh_photoview.