Skip to content

Note where the old enhanced query drops references (#760) - #761

Closed
adamjohnwright wants to merge 1 commit into
mainfrom
enhanced-v1-note
Closed

adamjohnwright wants to merge 1 commit into
mainfrom
enhanced-v1-note

Conversation

@adamjohnwright

Copy link
Copy Markdown
Contributor

This adds comments only, so the new site doesn't copy the fault behind #760.

The fault: /ContentService/data/query/enhanced/{id} is kept byte for byte as Java answers it.

  • An object is written in full only once, and after that as its bare dbId.
  • Since graph-core bb5e0ca0 (Aug 2025), an event's parent pathways (eventOf) come before its own lists.
  • So a reference the parent pathway also cites is a bare number in the event's literatureReference.
  • Production's pathway browser drops those numbers, which is literature references missing from live site despite being in curator tool record. #760. On beta both reactions show every reference.

The note goes on the node endpoint's definition (tools/content-node/data-query-endpoints.ts) and on the site's Event model. It says to read an event's lists from /enhanced/v2, which writes every object in full, as the details pages already do.

No behaviour changes. The endpoint stays byte-identical to Java, as the port requires. The other places that read the old form (the entity popup, the IDG panel's summation, the schema browser's instance view) read no references. The instance view also turns a bare dbId into a link.

Refs #760.

🤖 Generated with Claude Code

/data/query/enhanced keeps Java's answer byte for byte, including a bare
dbId for an object written earlier; since graph-core bb5e0ca0 an event's
parent pathways come first, so references its parent also cites are bare
numbers in its own list. Production's browser loses them (#760). The
endpoint and the event model now say to read an event's lists from
/enhanced/v2, as the details pages do, so the new site does not copy the
fault.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adamjohnwright

Copy link
Copy Markdown
Contributor Author

Replaced by the next PR, which corrects what this one said about v2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant