japonicusdb / japonicus-curation

Data files for JaponicusDB
0 stars 1 forks source link

New japonicus transposons #46

Open snezhkaoliferenko opened 2 years ago

snezhkaoliferenko commented 2 years ago

@ValWood @kimrutherford

Hey guys,

I'll reply to your other messages shortly (sorry for being a bit tardy but it's not good time for me at the moment, I feel like am behind on everything). Here I thought to ask how we deal with new element IDs. I am now curating https://journals.plos.org/plosgenetics/article?id=10.1371/journal.pgen.1010100 and they mention: "Multiple-sequence alignment of these regions allowed us to identify 10 new retrotransposon families, that we have named Tj12 to Tj21 (Table S2).

Could we assign those?

Thank you! S.

ValWood commented 2 years ago

Hi,

There are 397 features in this file. Some of them appear to be already annotated but some appear to be in contigs that we have not hosted (I can't remember what the decision was about this but there were 1000's of contigs If I remember correctly so I think we maybe only hosted contigs with annotated features).

What we would need is a mapping of these features to the Japonicus systematic IDs so that we do not create any duplicate features (maybe Liz can supply this?)

For example,

Tj10_partial_retrotransposon-10.1 | supercont5.10 | 331 | 5220 in the spreadsheet is SJATN_00206

snezhkaoliferenko commented 2 years ago

Hey Val,

Should we ask Liz then? I can forward her your letter.

Thank you, S.


From: Val Wood @.> Sent: 07 March 2022 16:40 To: japonicusdb/japonicus-curation @.> Cc: Oliferenko, Snezhana @.>; Author @.> Subject: Re: [japonicusdb/japonicus-curation] New japonicus transposons (Issue #46)

Hi,

There are 397 features in this file. Some of them appear to be already annotated but some appear to be in contigs that we have not hosted (I can't remember what the decision was about this but there were 1000's of contigs If I remember correctly so I think we maybe only hosted contigs with annotated features).

What we would need is a mapping of these features to the Japonicus systematic IDs so that we do not create any duplicate features (maybe Liz can supply this?)

For example,

Tj10_partial_retrotransposon-10.1 | supercont5.10 | 331 | 5220 in the spreadsheet is SJATN_00206

— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjaponicusdb%2Fjaponicus-curation%2Fissues%2F46%23issuecomment-1060891574&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fuk6vzgqigidjKQ5eslfdPOtRPlrs2XiXRc0byprC7E%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUYNMTZ56I4S6GLTTQRDFWTU6YWORANCNFSM5QDAA3PA&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dWXQbrCynyIpfeqHg%2FcMiqxU6m4ybE1DzvIVA2qrplA%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=yLQoVVo26qZwqWJUbDTShewmJ7j78MJd3cyEd4XUzUU%3D&reserved=0 or Androidhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4lKhk%2B5nXQrs7R17SfipzlsTj5xLGDO9obSlNEuB0QI%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

ValWood commented 2 years ago

Yes sure!

Val

On 07/03/2022 16:42, snezhkaoliferenko wrote:

Hey Val,

Should we ask Liz then? I can forward her your letter.

Thank you, S.


From: Val Wood @.> Sent: 07 March 2022 16:40 To: japonicusdb/japonicus-curation @.> Cc: Oliferenko, Snezhana @.>; Author @.> Subject: Re: [japonicusdb/japonicus-curation] New japonicus transposons (Issue #46)

Hi,

There are 397 features in this file. Some of them appear to be already annotated but some appear to be in contigs that we have not hosted (I can't remember what the decision was about this but there were 1000's of contigs If I remember correctly so I think we maybe only hosted contigs with annotated features).

What we would need is a mapping of these features to the Japonicus systematic IDs so that we do not create any duplicate features (maybe Liz can supply this?)

For example,

Tj10_partial_retrotransposon-10.1 | supercont5.10 | 331 | 5220 in the spreadsheet is SJATN_00206

— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjaponicusdb%2Fjaponicus-curation%2Fissues%2F46%23issuecomment-1060891574&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fuk6vzgqigidjKQ5eslfdPOtRPlrs2XiXRc0byprC7E%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUYNMTZ56I4S6GLTTQRDFWTU6YWORANCNFSM5QDAA3PA&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dWXQbrCynyIpfeqHg%2FcMiqxU6m4ybE1DzvIVA2qrplA%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=yLQoVVo26qZwqWJUbDTShewmJ7j78MJd3cyEd4XUzUU%3D&reserved=0 or Androidhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Csnezhana.oliferenko%40kcl.ac.uk%7C174e604be3f24c2a1f1908da00592487%7C8370cf1416f34c16b83c724071654356%7C0%7C0%7C637822680129533713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4lKhk%2B5nXQrs7R17SfipzlsTj5xLGDO9obSlNEuB0QI%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/japonicusdb/japonicus-curation/issues/46#issuecomment-1060893397, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYEWKFMZK6F55EENVZ7KXTU6YWWHANCNFSM5QDAA3PA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>