Open yroskov opened 2 years ago
Global Lepidoptera Index 1.1.23.336 / 2023-12-02; imported 2023-12-02
[x] Imported: 160,582 spp (vs 160,300 spp)
[x] Metadata: OK (long & detailed abstract)
[x] Sector: OK, order Lepidoptera (in the Sectors report)
[x] Blocked taxa in the Assembly (superfam Alucitoidea, fam Sesiidae in Cossoidea, fam Hepialidae in Hepialoidea, fam Gelechiidae in Gelechioidea, fam Gracillariidae in Gracillarioidea, superfam Nepticuloidea, fam Papilionidae & fam Pieridae in Papilionoidea, superfam Pterophoroidea, fam Tineidae in Tineoidea, superfam Tortricoidea) = Now taxa arranged in the tree in non-alphabetical order. Very inconvenient for editorial data management purposes: for attention of @mdoering & @thomasstjerne
[ ] All nested sectors are in correct positions in the Tree (check after sync of GLI)
[x] Names with genus in [...] (>1K; settings 100 names p/p; acc; reverse) = NO SUCH CASES ANYMORE DUE TO CHANGES IN CLB BEHAVIOR
[x] Names with portion [GENUS NOT SPECIFIED] (both acc & syn): 2 new
TASKS
Resolved 2023-12-12:
Synced 2023-12-12
Global Lepidoptera Index 1.1.24.013 / 2024-01-13; imported 2024-01-13
TASKS
Synced 2024-01-17
The sequence is as expected, reflecting standard arrangements for species lists. Maybe there should be a toggle in views that allows a user to force alphabetical order if they require it.
We might need to think about managing the order of names when we sync from sources. What happens if
We should at least provide a sector option to remove taxon ordinals during a sync. I'll work on that, no matter what we decide to do in this specific case.
@mdoering The main other thing I can imagine is what happens if a project replaces a sequenced node with the node for the corresponding taxon in another source dataset. When this happens, does the merged node retain the sequence position it had in the higher classification, or is the sequence index supplied by the lower classification? The former is what I would want to see happening (since the higher classification is asserting the order in which the children, including the merged node, should appear. But I could imagine that this could get altered by the lower classification node's setting.
It depends on how the sector is setup. If it is an ATTACH sector the root itself is copied, if it is a UNION it is not, only the descendants. Synced taxa from sources bring their own sequence ordinal, they won't inherit sth from the target.
So imagine we had an entire order A from the primary source with ordinals for sorting all its families.
a) If we'd block one of the families (F) and attach that family F from a different source to the order A. In that case family F would not have any ordinal any more and sort last.
b) you could also leave the family, block its children and use a UNION to merge the descendants from the new source into the family. That would retain the sequence, but it requires all children from the primary source to be blocked. Currently these are individual decisions which is a pain.
To better support this case we would could 1) offer an update decision to set a specific ordinal - which might be useful in its own right 2) provide a new block descendants but keep this taxon decision which would allow to use a UNION sector.
Both isn't that hard, so maybe we should implement both options?
Global Lepidoptera Index ver. 1.1.24.028 / 2024-01-28; imported 2024-01-28
TASKS
Resolved 2024-02-02:
Synced 2024-02-02
@yroskov Large update today - mostly cleaning work in Notodontidae
Global Lepidoptera Index ver. 1.1.24.035 / 2024-02-04; imported 2024-01-28
TASKS
Resolved 2024-02-05:
Synced 2024-02-05
Global Lepidoptera Index ver. 1.1.24.040 / 2024-02-09; imported 2024-02-08
Synced 2024-02-21
Global Lepidoptera Index ver. 1.1.24.040 / 2024-02-09; imported 2024-03-17
Synced 2024-03-18
Global Lepidoptera Index ver. 1.1.24.106 / 2024-04-15; imported 2024-04-14
Metrics:
ISSUES assessed 2024-04-18 (with minor fixes)
TASKS
Resolved 2024-04-18:
Synced 2024-04-18
Global Lepidoptera Index ver. 0.41.1 1.1.24.134 / 2024-05-13; imported 2024-05-14
Metrics:
ISSUES assessed 2024-05-14
TASKS
Resolved 2024-05-14:
Synced 2024-05-14
Sorry. I want at home so I uploaded a TaxonWorks ZIP without my normal preprocessing. Fixed the version now.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: yroskov @.> Sent: Wednesday, May 15, 2024 1:35:55 AM To: CatalogueOfLife/testing @.> Cc: Donald Hobern @.>; Mention @.> Subject: Re: [CatalogueOfLife/testing] GLI, Global Lepidoptera Index (id 55434): test report (Issue #195)
Global Lepidoptera Index ver. 0.41.1 / 2024-05-13; imported 2024-05-14
Metrics:
image.png (view on web)https://github.com/CatalogueOfLife/testing/assets/28574252/4c20977f-b2bf-461f-bed9-fdd957d2c5ae
ISSUES assessed 2024-05-14
image.png (view on web)https://github.com/CatalogueOfLife/testing/assets/28574252/3f6de3ff-86d2-4c99-867c-9f7d06297501
— Reply to this email directly, view it on GitHubhttps://github.com/CatalogueOfLife/testing/issues/195#issuecomment-2110608449, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHP4ZWNVCYMHU7VKIYGW4TZCIY6HAVCNFSM5VGFCS62U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJRGA3DAOBUGQ4Q. You are receiving this because you were mentioned.Message ID: @.***>
Thanks!
TASKS 2024-05-15 = no changes
@dhobern, I am cleaning duplicated taxa across whole CoL. It looks like Rougeotiana pseudonoctua Herbulot, 1983 is present in both GLI & Geometridae checklists.
Thanks - a good catch, and a multipartite fix. This species was described in a new genus Rougeotiana which unfortunately is a homonym. GLI has all species under the senior homonymous genus. I can remove it. Meanwhile, a replacement name has been published for the genus and missed by the Geometridae authors. I'll notify them and make the change manually for now.
Donald
--
Donald Hobern / @. / +61 420511471 Araba Bioscan Project https://stangeia.hobern.net/araba-bioscan-project/ / Pterophoroidea https://pterophoroidea.hobern.net/ / Alucitoidea https://alucitoidea.hobern.net/ / BOLD Australia https://bold-au.hobern.net/ ORCID: 0000-0001-6492-4016 https://orcid.org/0000-0001-6492-4016 / Blog https://stangeia.hobern.net/ / iNaturalist https://inaturalist.ala.org.au/people/dhobern / Flickr https://www.flickr.com/photos/dhobern// GitHub https://github.com/dhobern / Mastodon @.>
On Thu, 6 Jun 2024 at 02:34, yroskov @.***> wrote:
@dhobern https://github.com/dhobern, I am cleaning duplicated taxa across whole CoL. It looks like Rougeotiana pseudonoctua Herbulot, 1983 is present in both GLI & Geometridae checklists.
— Reply to this email directly, view it on GitHub https://github.com/CatalogueOfLife/testing/issues/195#issuecomment-2150493854, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHP4ZWZJSK5MQ4ANVL7HZTZF442TAVCNFSM5VGFCS62U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJVGA2DSMZYGU2A . You are receiving this because you were mentioned.Message ID: @.***>
The Geometridae part is now fixed. Downloading a new copy of GLI from TW so I can fix the other part.
And now the GLI part is also fixed.
Global Lepidoptera Index ver. 0.41.1 / 2024-06-06; imported 2024-06-06
Metrics
ISSUES assessed 2024-06-06
TASKS no new issues
Synced 2024-06-06
@yroskov New update
@dhobern, I'll sync all updated Lep checklists for CoL of July on Thursday, Jul 18th, if you have no objections
Thanks - that will be great
Global Lepidoptera Index ver. 1.1.24.199 / 2024-07-17; imported 2024-07-16
Metrics
TASKS
Resolved 2024-07-18:
Synced 2024-07-18
@yroskov New updates in GLI
@yroskov New updates today
LepIndex ver. "2022-04-39 / 2022-04-30" on PROD: https://www.checklistbank.org/dataset/55434/classification