Relation load issue #11

Open
opened 2025-04-23 14:10:12 +00:00 by mih · 3 comments
Owner

Demo clip below. On first edit attempt, the relation to the offices does not show. But after closing and reopening the dialog, it does.

Demo clip below. On first edit attempt, the relation to the `offices` does not show. But after closing and reopening the dialog, it does.
Owner

I have reproduced this. Seems like either an issue with when/how the records for e.g. Room are fetched and made available in the local graph store, or when/how the application components (specifically the InstancesSelectEditor and the NodeShapeViewer) try to find updates in the graph store.

I saw what I think is a related issue: the value of the Offices field is a URL on first load (see screenshot), and after opening and closing the form editor, it shows the specific office record's prefLabel.

Screenshot 2025-04-23 at 16.18.32.png

I have reproduced this. Seems like either an issue with when/how the records for e.g. `Room` are fetched and made available in the local graph store, or when/how the application components (specifically the `InstancesSelectEditor` and the `NodeShapeViewer`) try to find updates in the graph store. I saw what I think is a related issue: the value of the `Offices` field is a URL on first load (see screenshot), and after opening and closing the form editor, it shows the specific office record's prefLabel. ![Screenshot 2025-04-23 at 16.18.32.png](/attachments/a83396f5-3204-4e3c-88d8-2b9e568952ed)
Author
Owner

Ha ok! I reported this last behavior in #10 (comment) -- apparently misinterpreting the cause.

Ha ok! I reported this last behavior in https://hub.psychoinformatics.de/inm7/annotate.inm7.de-simplesubmit/issues/10#issuecomment-3669 -- apparently misinterpreting the cause.
Owner

Once the update proposed and proofed here: #37 (comment) is deployed, the reported issue should be resolved.

The "related" issue of the office pid showing up at first, and only afterwards the preflabel, is related to when exactly specific records are fetched. Currently, the NodeShapeViewer component does not fetch records that are related to it. The simplest option I can think of here is to fetch the individual records related to the pid when a given NodeShapeViewer is rendered.

Once the update proposed and proofed here: https://hub.psychoinformatics.de/inm7/annotate.inm7.de-simplesubmit/issues/37#issuecomment-3985 is deployed, the reported issue should be resolved. The "related" issue of the office pid showing up at first, and only afterwards the preflabel, is related to when exactly specific records are fetched. Currently, the `NodeShapeViewer` component does not fetch records that are related to it. The simplest option I can think of here is to fetch the individual records related to the `pid` when a given `NodeShapeViewer` is rendered.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
inm7/annotate.inm7.de-simplesubmit#11
No description provided.