-
Notifications
You must be signed in to change notification settings - Fork 59
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
upload RIKEN_ReSpect MS2 #82
Conversation
Thank you for this new contribution. Could you please give a short introduction about the source of these spectra and who contributed them. You have already contributed a number of records, some in the RIKEN directory and some in some directories which start with RIKEN and then have something like a project tag (RIKEN_IMS, RIKEN_NPDepo). For the older content of MassBank we maintain a list if contributors (https://github.com/MassBank/MassBank-data/blob/master/List_of_Contributors_Prefixes_and_Projects.md) and I would like to put some entries for your contributions in this list. Do you want to mark these contribution with a specific poject tag and thats why you use RIKEN _ReSpect? I would like to put this topic up for discussion to some of the senior MassBank member. How should we handle different projects coming from a certain institution? How should we handle new prefixes for accessions? |
For the description of these RIKEN_ReSpect record: At this time, these data come from one institute (if you see closer into the data, you will find records from different experiment, year and authors...) So that is why I would like to request for a independent directory. As I know, Riken have several affiliate institute. Many of them be able to carry experiments. There should be a rule to how to handle the new prefix. Also tell the new contributor when and how to use a new prefix. |
@tsufz and I will be in the same physical location for the next few days so I will put this on the list to discuss. We have had a parallel email discussion regarding new contributors as well, as well as relaxing the accession ID requirements. @meier-rene do you want to start a separate issue (or issues if needed) to discuss this in an overarching manner? We may need to cross-ref with MassBank-web. Please break issues down into topics if this is logical for you. Re ReSpect I have some concerns as the original ReSpect dataset was imported from a fixed set that was published. http://spectra.psc.riken.jp/ It is plausible that other RIKEN groups will contribute too. Also note for Eawag we have mulitple letter combinations but in one directory (EA = Orbitrap and EQ = QExactive, for instance), with the tentative spectra separated out into a different directory as they were made differently (with ET or ETS prefix). |
I suggest 2 ways how to use prefix:
This is only my suggestion only for your information. I am dealing with a dataset from a joint research by Karolinska institute (Sweden)and Gunma University(Japan). The author requests me to use a new directory named "KI_Gumma"... What should we do with joint contributors? Previously I upload RIKEN PlaSMA records to "RIKEN" directory (trying to reduce the number of the folder...). The author request me to separate these records from RIKEN, for PlaSMA is a group... |
We totally understand your point here. Please give us a little bit of time to come up with a feasible solution which makes everyone happy |
I made some research about the data you submitted and found out, that they are from independent institutions. Thats why I took over your naming scheme and I will enter some information in the table of contributors. |
Dear Rene Meier ,
Thank you very much for the information.
If you need any other information, please feel free to contact me.
LI
René Meier <notifications@github.com> 于2019年8月6日周二 下午9:04写道:
… I made some research about the data you submitted and found out, that they
are from independent institutions. Thats why I took over your naming scheme
and I will enter some information in the table of contributors.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AGN6RSOSHFAVN3R4PNWAPYTQDFSDVA5CNFSM4H3YGKD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3U5F2A#issuecomment-518640360>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGN6RSNJPSZO2B6GJ2XP43LQDFSDVANCNFSM4H3YGKDQ>
.
|
No description provided.