Closed jonathancrabtree closed 3 years ago
This may not require any changes to the API specification per se (as the spec is silent on the question of what exactly the DCC "moniker" translates to) but if it does then it should be split into two issues for consistency with the others (e.g., #19 and #21)
It doesn't look like these new ids are suitable to use as a DCC "moniker", so the API will probably need to be extended to distinguish between DCC internal id and DCC human-readable moniker/abbreviation:
There's a new dcc table with an id column that contains stable DCC identifiers. These should be used as the "moniker" described in the dashboard API spec, rather than the primary_dcc_contact.abbreviation. See https://github.com/nih-cfde/cfde-deriva/issues/200