datanav / docs Goto Github PK

Consider moving/including this under Architecture & Concepts > Naming conventions.

ldap examples

Entities in the same dataset which can have different meaning.

Ex: Employees can have different Status based on attributes such as "isOnVacataion" or "Resigned" or if "resignedDate" is in the future or past.

It can be tedious to have logic for such things in multiple places, so adding an attribute "sesam-employee:status" which can have the values "working", "not working" or "left" can be useful for filtering in downstream pipes.

Should they be in the start or the end?

I can't find any documentation on where and how to create long lasting JWTs.

Looks like gdpr subject consent part of docs a bit incomplete and don't have description for all required properties needed to handle custom consent changes.

Why does this error occur? Has this line recently changed?

On @endbro PR, the error is
/home/travis/build/datanav/docs/DTLReferenceGuide.rst:: ERROR: Line 5171 exceeds the line-length-limit.

fix figure endpoint typo

Change topic title to Naming Conventions

https://github.com/datanav/docs/blob/training/training/010_architecture_and_concepts/020_Beginner.rst#namegiving-conventions

Guidelines for writing in RST should be included in README.md

https://sesamdata.sharepoint.com/sites/Training/_layouts/OneNote.aspx?id=%2Fsites%2FTraining%2FShared%20Documents%2FGeneral%2FKursutvikling&wd=target%28Retningslinjer.one%7CEAF06DA0-4215-4515-838B-CFE94CAB4FFE%2FSkriving%20i%20RST%7CCCE673F8-FC5F-47DF-88A7-3EC7063D5A73%2F%29
onenote:https://sesamdata.sharepoint.com/sites/Training/Shared%20Documents/General/Kursutvikling/Retningslinjer.one#Skriving%20i%20RST&section-id={EAF06DA0-4215-4515-838B-CFE94CAB4FFE}&page-id={CCE673F8-FC5F-47DF-88A7-3EC7063D5A73}&end

It looks like when you push data to REST sink it will process deleted entities. This behavior is not described in documentation and may follow to confusing situations.

3.1.5