-
Notifications
You must be signed in to change notification settings - Fork 23
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
indicating release dates to NCBI in CEDAR metadata #143
Comments
Hi John,
Thanks for spotting this issue. I think it is crucial that no submitter is surprised of realizing their data! Many researcher are very sensitive about that and sometimes there can be month between initial submission and public release of the data.
The single clear annotated release data sounds good to me. It avoids also misunderstanding or mistakes during the submission process. At least as the default option for now. If there is a need to separate publish some parts of it it may can be later incorporated?
Best,
Florian
|
Yes, I agree this is the best solution as the outcome of setting the release date will be obvious to everyone. |
OK, we will implement it as I proposed. I believe (based on testing) we can just change add that field to the current template and the (two or three) existing in-progress instances will pick up the changes gracefully. We also will change the documentation of the existing Expected Release Data attribute in the BioSample part to make clear that is not used for setting any of the release dates in NCBI. |
In the CEDAR template there is only one field to indicate "Expected Release Date", and it has no impact on whether the submission is made public or not. I'm not sure what its purpose is (any thoughts?).
There are 2-3 different submission types created by the template: BioProject (if it doesn't already exist); BioSample; and SRA. The latter 2 can each have multiple instances.
NCBI interpretation of release dates is complicated; they release 'parent' items like BioProject if the (any!) BioSample or SRA submission is released.
For simplicity we propose a optional single release date for the whole CEDAR collection, which may include any number of BioSample or SRA submissions. The release date field would be at the top of the template.
Is this agreeable?
If not, we could add release dates to each section, but we would not add code to check that no unexpected consequence will ensue. (We can document the understood behavior in the help text for each release date though.
The text was updated successfully, but these errors were encountered: