indentlabs / indentlabs/notebook

Export uses IDs in multiple places but does not include the IDs itself

Open
#1,074 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
410
Forks
78
Avg merge
1d
Merged PRs (30d)
9

Description

### Expected behavior

Personally, I have a strong preference for variant 1 in the following examples; names can be ambiguous.

Example (YML) with *added Id* entry in line 3:
```
- Gender: Male
Age: '60'
Id: Character-1035946
Name: Werner
Role: Innkeep
Motivations: Having a nice life with his wife.
Spouses: '["Character-1035947"]'
Occupation: Inn-Keeper in Gildan.
```

Example (YML) with dereferenced Id, i.e. *name* in Spouses-field.
```
- Gender: Female
Age: '60'
Name: Brunhild
Role: Innkeep
Motivations: Having a nice life with his wife.
Spouses: ["Werner"]
Occupation: Inn-Keeper in Gildan.
```

### Actual behavior

Like the first example above but without any way to find who `Character-1035947` is referring to.

The problem occurs for other references, e.g. Locations, too:
```
"Notes": "...[[Character-1035945]] wuchs mit [[Character-1035950]] in [[Location-219090]] auf. ...."
```
### Steps to reproduce the behavior

1. go to https://www.notebook.ai/my/data/export
2. export something (in this case YML).

As far as I can tell, this occurs for all export types.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the export page linked in the reproduction steps and reproduce the issue with YML, then check the other export types mentioned. Done means exported references such as Character and Location IDs can be resolved, either by including IDs in records or by dereferencing them consistently across formats.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.