You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that's weird. i'm sure i've seen both examples or Last, First on the meditor (which is based on json). perhaps it was adjusted sometime because of keeping the variable description more consistent. we should check.
which is the base class for Person where we restrict name to follow the Last, First convention. And as Contributor could also be the Organization where indeed it doesn't make sense to enforce Last, First -- it is all "ok"
but also we have
classRelatedParticipant(DandiBaseModel):
identifier: Optional[Identifier] =Field(
None, json_schema_extra={"nskey": "schema"}
)
name: Optional[str] =Field(
None,
title="Name of the participant or subject",
json_schema_extra={"nskey": "schema"},
)
where hopefully we would not need Last, First and it could potentially be the animal name I guess..
But I think in general we are ok, sorry for the noise!
Similarly we likely to pursue it at the level of BIDS:
since without that, it is impossible to separate full name into First and Last for a more detailed schema, as e.g. in openMINDS (@lzehl).
ATM we have also just
and just a "convention" stated somewhere to possibly enter as "Last, First".
WDYT @satra -- should we aim to harmonize or at least going forward to more explicitly encourage
Last, First
form?The text was updated successfully, but these errors were encountered: