FIX: use identifiable instead of record

The crawler has internal checks in order to decide whether a Record can be checked for existence with the server. For this, all identifying properties need to be existent and all references of those need to be resolved or also records that can be checked themselves (so that they can be checked first).

Previously, the crawler required that ALL reference Properties can be checked or are resolved in order decide that the Record at hand can be checked.

Example: RT A with properties b and c

The registered identifiable is A with b

Record A
  b = 1234

can be checked (but the old code assumed it cannot.)

Record A
  c = 2344

cannot be checked since the identifying prop is missing.

Please consider !56 (merged)

assigned to @salexan

marked this merge request as draft

added 12 commits

• d70fc968...865686b1 - 10 commits from branch dev
• 0b09ca14 - Merge branch 'dev' into f-identifiable
• f464b3db - Merge branch 'dev' into f-identifiable

Compare with previous version

added 1 commit

• be7f26b1 - WIP

Compare with previous version

resolved all threads

added 1 commit

• d3e673d7 - WIP

Compare with previous version

added 239 commits

• d3e673d7...e676caee - 238 commits from branch dev
• 8d7aef7a - Merge branch 'dev' into f-identifiable

Compare with previous version

added 1 commit

• 1908020d - DOC: refined doc

Compare with previous version

@henrik I think we need to review this once more carefully.

added 191 commits

• 1908020d...b67e5edb - 190 commits from branch dev
• f1882a4f - Merge branch 'dev' into f-identifiable

Compare with previous version