Project: Cape of Good Hope - Kaap de Goede Hoop (1652-1806)/Project Profiles

Categories: The Dutch Cape Colony 1652-1806 | Cape of Good Hope - Kaap de Goede Hoop (1652-1806) Project

Process & Project Profiles
Home Page Process & Project Profiles COGH Stamouers-Progenitors Resources To Do Lists COGH Template Needs System Numbering and Naming Systems Admin Suid Afrikaanse Portaal


Alphabetical List of Project Profiles

Alphabetical List

Surname List

Surname List


When you identify a profile that needs Project Protection or belongs to the project, contact Susanna (Coetsee) de Bruyn, André Laubscher or Ronel Olivier so that the profile can be reviewed, and after the evaluation proces be included and / or protected. You can also place the templates including maintenance categories yourself. See below which when.
A WikiTree Leader will after evaluation and / or validation Project Profile Protect (PPP) the profile, so that it's WikiTree ID cannot be changed by either editing or merging. This means that the Project itself is the custodial manager so that both the LNAB and the parent-connections too will be protected. In order to change that protection, a certain amount of collaborative agreement will have to be reached.
Profiles in this project should have the project box added at the top of their biography.
Adding {{Dutch_Cape_Colony}} to a profile will include it the list of project profiles and add the following project box:
Table Bay, South Africa (1762)
... ... ... was part of the settlement of the Dutch Cape Colony.
Join: Cape of Good Hope - Kaap de Goede Hoop (1652-1806) Project
Discuss: dutch_cape_colony
The Dutch Cape Colony 1652-1806 maintenance categories can be found here. (The South African Roots Project for post 1806 South African profiles and it's maintenance categories can be found here)
  • Do not remove the [[Category: Cape of Good Hope Ready]] category when a profile has been validated and protected. This category serves as the administrative tag for all the {primarily} validated profiles in the project.
  • Do not place this template {{Unsourced}} on {{Dutch_Cape_Colony}} profiles because that is what the maintenance categories are for.
  • Do not place this sticker {{South African Roots Sticker}} on {{Dutch_Cape_Colony}} profiles because the post-1806 profiles all fall under the South African Roots Project and they - unlike the pre-1807 profiles - do not eventually get profile protected. This sticker serves as the administrative tag for all the post-1806 profiles.


Specific goals: any improvements we can make to the profiles of the Dutch Cape Colony families are welcome, but here are some specific goals we're working toward:
For each person (profile):
  1. All duplicates merged into the final profile ID
  2. Final ID locked, marking the profile as project protected (must be done by one of the Leaders)
  3. Cape of Good Hope template included on the page
  4. Parents are correct
  5. The Project Profile is at least co-manager if not full custodial manager of the profile (see in this regard the next section)
  6. Bio is cleaned up, free of any GEDCOM junk, unnecessary Ancestry trees (leave them if they are the only source available), etc., and ideally has an actual written bio.
Process: In order to get to a well researched, edited and narrated profile, the following process has to be followed (steps 1-4, even 5 can be done at the same time):
  1. We first collect all the [basic] data and information with a healthy amount of distrust - not all data is valid - nonetheless we collect it [but in doing so we avoid duplication and aim for validation - i.e. we do not merely copy / paste information where a simple working link [Afrikaans transl. = "skakel"] and we find and merge duplicates, always taking care that the LNAB is merged into a lower number except when a higher number has the valid or more correct spelling of the LNAB of the time (the Dutch, South-African and French conventions were to write the suffixes [if any] between the first/middle names and the last part of the surname with lower case characters - small 'v' and 'd' for van der Walt and du Toit as examples).
  2. Then we create order in the bio and do it so that we know who did what when and if need be why - at this stage we do not yet wipe the junk from GEDCOM, just trim it slightly - it still holds clues. For more information on 'reading' and editing GEDCOM-info, see: GEDCOM-created biographies.
  3. We find the primary sources for the LNAB' - those are primarily the baptismal records for the Last Name At Baptism, and other primary records for the other names used for example marriage records, death records etc. - we know that Hans Christoffel Snyder aka Schneider / Snijder / Snyman (to use an example) came from the Palatinate and was probably called Schneider - that would be the LNAB but finding a baptismal record might be impossible so we turn to the shipping lists or other primary sources that bear his name (in this regard see Wikipedia for more information on the distinction between primary and secondary sources). Those names might be in Dutch (or another language) and have varying spellings - most often phonetically spelled - but it will be the nearest best thing. Of course we do a search in Germany or a global search as well (bearing in mind that many records did not survive the ravages of time or were not even made to begin with).
  4. We upload as much 'evidence' in the form of photo's / transcripts to the profile itself, taking the utmost care to make sure that they are not copyright infringed and that the objects are properly sourced and cited.
    1. Guidelines for uploading images as primary images (in order of preference):
      1. A picture of the person him-/herself
      2. If that is unavailable only a digital (properly sourced & cited) image of the baptismal record of the person self [not of the parents or of the witnesses]
      3. If only a transcription of the baptismal record is available then any other image [not a baptismal record of a child of that particular person] will do
      4. Or an image of a gravestone (the latter is more appropriate for people who had passed in the last 200 years).
    2. Guidelines for the inclusion of profiles (Wiki-ID's) in an uploaded image:
      1. Do not include witnesses or parents to baptism image (but do include them in the transcripts of the baptism entries)
      2. If it is a document include as many relevant profiles as are deemed important
    3. Guidelines for uploading images to this project in general:
      1. Preferably should all images including (source) images and documents only be uploaded once ... with titles of a much shortened version of the source stating for example (click to open): Death registers Tulbagh (1744-1750) for the Dutch Reformed Church at Tulbagh or Tulbagh, Baptism register 1743 - 1815 image 347 or Parish registers for the Dutch Reformed Church at Tulbagh, Marriages 1744-1922.
  5. A final LNAB is decided - this is the name as it appears on the baptismal record, and if that is not available, any other primary record such as a marriage record, death record etc. At times it is needed that consensus be reached over spelling or other circumstantial issues (patronymics etc.) in either a G2G-discussion or email correspondence. Variations can be AKA'd. Decisions can always be revisited once new evidence that makes an valid argument for another choice of spelling of the LNAB can be found. See Wikipedia for more information the Dutch naming system, and for information on the distinction between primary and secondary sources. See also the Dutch Roots Project.
  6. The LNAB gets protection - the |Needs PPP is added to the template or as a category to the profile in order to get the profile (LNAB) Project Protected (which means that all the duplicate profiles with variations in the spelling of the LNAB but still pertaining to the same person, will have to be merged into this target profile).
  7. Final editing and the eventual creation of a narrative if necessary - only after the stage Project Profile Protection (PPP) will the profiles be ready for narration and editing (when as much of the 'facts' have been collated).
Example: a well researched and decently organized biography will look something like this: Dirck (Couché) Coetzee; a well researched and narrated profile will look something like this: Chrétien Du Bois (the French spelling of the LNAB in this case would follow the Canadian conventions and if the records show it to be this way). See the page for this project with Editing Instructions and Examples. Also see the WikiTree Editing Tips.
At no stage do we:
  1. Merely interpret facts or only collect information that support our view of what might have been and then forcefully edit data to fit that (if we need to make comments we do it with footnotes, adding the sources appropriately, accompanied by our WikiTree names, the dates we have seen the sources and the dates that we have done the editing).
  2. Disrespect the contributions of others by removing it (or parts of it) or vandalizing what they have already contributed. As merged profiles tend to grow larger and bulkier in time, it will be necessary to trim and edit though. Again, we strive to uphold the integrity of the text and narrative by taking a neutral but critical stance and try and edit in such a way that the editing does not compromise the contributions of others.
We abide by the Honour Code at all times.
See for further important info our Project Needs (Maintenance) Template System and Categories

Project as co-manager

As soon as a profile has attained Profile Protected Status (PPP), the Project Profile or Account: gets added to the trusted list (if not already done) and then gets activated as active manager (if not already done).
No active managers will be removed, (unless managers are ok with this when properly asked [when there are too many active managers on a profile] or don't respond/ are inactive, it is an option that will be considered though and the project leader does it)
The reasoning behind this:
  1. Massively merged profiles (i.e. the result of numerous mergers) need the Project Profile as custodial manager in order to monitor edits and changes to the data and / or biography.
  2. Parent profiles cannot be merely edited away by dis-connection and / or re-connection - a certain amount of collaborative consultation will be necessary after which the Project Research Coordinator have to follow the democratic vote and evidence based sources and change the parents or have the LNAB corrected or changed all together.
  3. As these profiles are all older than 200 years, it has a leveling effect - no one in his / her own can own a Project managed profile - the profile is under custodial management of the project itself, while editing and enhancement (with due attention to style and standards) can still be performed by anyone with the correct WikiTree credentials (Honor Code Signatory, Pre-1700 or even Pre-1500 test passed).
  4. All project members are kept informed through the Google-group news feeds, the project profile Google-group is in fact the watchlist of the project profile, so it's similar to the feed you receive from all profiles you are managing (your own watchlist), with the advantage we now have a way to share thousands of profiles with hundreds or thousands of members (everyone who joins the project and/or project google group) without our own watchlist becoming way too large to handle.
Managers of this specific Project Profile is reserved for those most active, experienced and knowledgeable (as the content of this project goes).

This page was last modified 14:42, 5 April 2022. This page has been accessed 3,307 times.