Skip to content

v1.21.0

Choose a tag to compare

@thobgg thobgg released this 14 Oct 14:50
· 8 commits to main since this release

API levels 34 to 36: the GEDCOM-L addendum, read completely, three parts of it writable – and nothing of it lost when
writing; who may see each fact.
Additive.

  • Level 36 – access at every fact, person (Individual, Export, all person summaries) and family: the lowest role
    that may see it – visitor, member or manager – decided by webtrees itself (RESN, the tree's privacy rules per fact
    type and person, the rules for living people; a family is hidden as soon as one member is). Person summaries also get
    nameAccess (who may see the name – for living people this follows the tree setting “show living names”) and
    restricted: the life events (BIRT, CHR, BAPM, DEAT, BURI, CREM, OCCU) a visitor would not see although the person
    itself is visible; linked godparents and witnesses (associates) carry access too. Clients can thus produce books for a wider audience from a manager's login (issue 21 of the apps).
  • Level 35 – gedcomValue at every fact: the value as stored in GEDCOM when value shows it translated
    (1 _STAT NOT MARRIED → “not married”), else null. Clients need it to write the value back; the family status is
    written with the existing POST Fact.
  • Level 35 – POST PrimaryMedia also sets the GEDCOM-L mark 2 _PRIM Y at the chosen media link and removes _PRIM
    from the other links, so other programs show the same main picture as webtrees.
  • Level 35 – POST Task takes the GEDCOM-L fields description, category, priority (0–8), taskType (0–2),
    status (open/completed/auto), reminder, completed (GEDCOM dates), solution and repository (xref). Only the
    keys sent change; an empty value removes the line.
  • extras at every fact (Individual, Family, Export): the GEDCOM-L items that have no field of their own – at the
    place the GOV identifier (PLAC:_GOV), postal code (PLAC:_POST, with date) and Maidenhead locator
    (PLAC:_MAIDENHEAD), at the address the name of the addressee (ADDR:_NAME). Each as {tag, value, date}.
  • uids at Individual and Family: the record's 1 _UID values.
  • highlighted at every media link of a person or family: _PRIM Y at the link or at the file – the image other
    programs show as the main picture (primary stays webtrees' own choice, the first image).
  • Research tasks (Tasks, tasks at Individual/Family) with description (DESC), category (_CAT), priority
    (_PRTY 0–8), taskType (TYPE), status (STAT), reminder (_RDATE), completed (_CDATE), solution (DATA) and
    repository (REPO, {xref, name}).
  • Location record (Place → location) with names (all NAME lines with date, language, abbreviation), types
    (all TYPE lines with date and GOV type number), postalCodes (with date), adminIds (_AIDN with type, e.g. AGS),
    demographics (_DMGD with type), maidenhead, religion and uids.
  • Fix: changing a research task (POST Task with factId) no longer drops what the route does not set itself.
    Up to 1.20 the task was rewritten from text, date, user and note, and the GEDCOM-L items (DESC, _CAT, _PRTY, TYPE,
    STAT, _CDATE, _RDATE, DATA, REPO, _UID) and source citations were lost.
  • Test tree gedcoml.ged with every item of the addendum; a test sends it through all write routes the apps use
    (event, name, godparents, citation, task, media object, source, repository, place, rename) and checks that every
    GEDCOM-L line survives.