-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try renaming submissionId
to id
for input
#3711
base: main
Are you sure you want to change the base?
Conversation
39e8342
to
7c7e241
Compare
@@ -150,8 +151,8 @@ function getAccessionInputField(): InputField { | |||
|
|||
function getSubmissionIdInputField(): InputField { | |||
return { | |||
name: SUBMISSION_ID_FIELD, | |||
displayName: 'Submission ID', | |||
name: SUBMISSION_ID_INPUT_FIELD, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't add the _INPUT
part to this field name - why did you think of doing that? Other fields are also inputs possibly, and the don't have this.
Looks all very sensible, nice! I would like to have two more backend tests:
If that's there and tests are green I think I would approve. EDIT: Oh yes, probably also some docs. - |
I've removed the preview label here for now, feel free to add it back! Just a bit many small PRs going on at the moment (I created a lot of them 😬 ) |
resolves #2404
preview URL: https://submissionid2id.loculus.org/
Summary
Asking users to supply a metadata file with a "submissionId" for each sequence is confusing. The ID here is actually likely to be the user's own sample ID, as used in their FASTA file. "SubmissionID" implies an association specifically with the Loculus submission - maybe an ID for submission that you get from Loculus.
Here we rename this input field to a bare
id
, and also adjust the templates accordingly. We have back-compatibility that also supportssubmissionId
(we can potentially remove that after a while).This does not rename the field downstream. After submission this name does make more sense, it distinguishes the name that Loculus assigned (the accession) from the one the user used at submission (the
submissionId
)PR Checklist