Service error with Amend function

[jpk96]

@vkuznet

On the web interface, submitting an amended record using "Amend" function results in service error.

See below for the error message.

Service error
Record /beamline=3b/btr=koerner-4218-c/cycle=2025-2/spec_datafile_location=/peek_cf_175_1/peek_cf_175_1 update fails with error=unable to update metadata record in FOXDEN server, {"http_code":500,"service_code":111,"service":"MetaData","status":"error","error":"record key 'doi_parents_dids' is not known","service_query":{"query":"","spec":null,"projection":null,"sql":"","idx":0,"limit":0,"sort_keys":null,"sort_order":0},"results":{"nrecords":0,"records":null},"timestamp":"2025-10-22 11:44:48.418093801 -0400 EDT m=+1625010.234332601"}

[vkuznet]

thanks for reporting this, as I explained in this comment #20 (comment), we added few things to support new feature (like composite datasets) and as side effect didn't test amend feature. This should be fixed once we introduce common schemas and embed them to beamline schemas. Here is current DOI schema which needs to be embedded to existing beamline schemas. But before doing that we need to review and agree on these new set of embeded schemas. So far I committed the following "new" embedable schemas:

• did.json
• beamline.json
• doi.json

I hope we will find time for their review and move forward with them which will allow to fix this issue.

@fyi: @wernersun , @keara-soloway , @rolfverberg we need to present and discuss embedable schemas to CHESS scientists.

[jpk96]

I am tagging @ksg52, @adas42, @suchismitasarker, @kenygren for visibility. While much of the content in beamline.json appears applicable to 3B, there are a few keys that will likely need to be modified, made optional, or removed entirely in most cases specific to 3B.

[vkuznet]

Meanwhile, I added the missing doi key doi_parents_dids reported originally into skip list on FOXDEN production instance and the issue itself should be solved for now. But as I explained we should converge on embedded schemas to properly address this issue.