Closed gjost closed 5 years ago
The error occurs in DDR.models.collection.Collection.children
in line 301.
It looks like ddr-densho-1000/files/ddr-densho-1000-452/entity.json
is unusual in having a child/segment record containing a signature_id
while the main entity does not have a signature_id
.
The children function is trying to be a bit too smart, to optimize by manually reading the JSON file instead of just loading the whole thing and parsing it. It tries to load title
and signature_id
lines as miniature JSON documents, and quits once it has both a title and a signature_id. In this case it doesn't have a signature_id until it's gotten into the child entities, and this line has a trailing comma and does not parse as legal JSON, triggering this error.
So basically this happens when you have an Entity without a signature, that has a segment with a signature.
Fixed in commit 03853c1.
@dana Getting this error: JSONDecodeError at /ui/collection/ddr-densho-1000/children/ when I click on the objects tab for densho-1000 (local version). Also if I navigate directly to an interview record and try to add a new segment under the children tab, I get this: JSONDecodeError at /ui/entity/ddr-densho-1000-452/new-idservice/. Tried this about 5 times for ddr-densho-1000-452, and the new segments are not visible, so I'm not sure if they've actually been created or not. @pkikawa on Dana's local densho-1000 comp. (v2.7.1MA) Densho-1000 in the idservice is missing a ton of IDs. densho-1000-1 through densho-1000-3 are present. densho-1000-440 through densho-1000-474 are present. no IDs between 3 and 440 are present. not all entity IDs that are present have their correct child entities present in the ID service (densho-100-442 is missing it's child entities) This error thrown from adding a child entity Also happens on /ui/collection/ddr-densho-1000/children/
May or may not be related: @pkikawa Densho-1000 in the idservice is missing a ton of IDs. densho-1000-1 through densho-1000-3 are present. densho-1000-440 through densho-1000-474 are present. no IDs between 3 and 440 are present. not all entity IDs that are present have their correct child entities present in the ID service (densho-100-442 is missing it's child entities) Dana says this behavior started sometime after 3pm yesterday