Open jhpoelen opened 4 months ago
https://sandbox.zenodo.org/records/28829
points to:
Ale-Rocha, R., Freitas, G., & Mathis, W. N. (2014). Revision of the Neotropical genus Marbenia Malloch (Diptera: Periscelididae). Zootaxa, 3872, 365–375. https://doi.org/10.11646/zootaxa.3872.4.3
and
https://zenodo.org/records/225270 point to non-sandbox record, non-TaxoDros literature record,
Ale-Rocha, R., Freitas, G., & Mathis, W. N. (2014). Revision of the Neotropical genus Marbenia Malloch (Diptera: Periscelididae). Zootaxa, 3872(4), 365–375. https://doi.org/10.11646/zootaxa.3872.4.3
I can see how it would be good to connect TaxoDros derived literature records to other records derived from the underlying literature (e.g., both https://zenodo.org/records/225270 https://sandbox.zenodo.org/records/28829 are derived from https://doi.org/10.11646/zootaxa.3872.4.3 so, they are derived from the same source). However, the records themselves carry different metadata.
Aside from having the record carry different metadata, aligning the TaxoDros literature records with non-TaxoDros records is expected to take quite some time, and goes beyond the task of preserving the TaxoDros corpus. Also, I am not quite sure what the plan would be for records that are both in TaxoDros and elsewhere in BLR/Zenodo.
There is in fact not much metadata in Taxodros, unless we start to add keywords. The value we generate here is that Taxodros points to a publiction and we make it accessible in BLR/Taxodros.
The idea behind building this PDF corpora in BLR is to see this as a first step. The second is to convert them into a format that can be further processed by machine, to extract bibliographic records, figures, and to extract from taxonomic publications treatments as well and make them available as FAIR data in BLR.
Thus any taxodros publication that is already in BLR is step 2 and the only thing we need to do is to add the respective links to the taxodros corpus, and in the taxodros corpus link the publication to the respective Zenodo deposition.
The idea behind building this PDF corpora in BLR is to see this as a first step. The second is to convert them into a format that can be further processed by machine, to extract bibliographic records, figures, and to extract from taxonomic publications treatments as well and make them available as FAIR data in BLR.
Yes, in my understanding, this first step is the one we are working on here.
Thus any taxodros publication that is already in BLR is step 2 and the only thing we need to do is to add the respective links to the taxodros corpus, and in the taxodros corpus link the publication to the respective Zenodo deposition.
I can see how linking the TaxoDros records to other non-TaxoDros record is valuable. And, in my mind, especially given the variation in bibliographic citations (and other metadata) and the sheer size of both corpora, adding links from TaxoDros derived records/pdfs to non-TaxoDros records is a project on its own.
it is NOT about linking taxodros record to non-taxodros records, but linking taxodros records for which already a PDF-deposit in Zenodo BLR exists.
Thanks for your prompt reply. I think we may have to discuss in person, please suggest date/time.
Tonight 9pm to 11pm.
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Jorrit Poelen @.> Sent: Wednesday, February 21, 2024 4:46:17 PM To: TaxoDros/TaxoDros.github.io @.> Cc: Donat Agosti @.>; Mention @.> Subject: Re: [TaxoDros/TaxoDros.github.io] Are you sure, you do not upload articles that are already in Zenodo? https://sandbox.zenodo.org/records/28829 has https://zenodo.org/records/225270 (Issue #10)
EXTERNAL SENDER
Thanks for your prompt reply. I think we may have to discuss in person, please suggest date/time.
— Reply to this email directly, view it on GitHubhttps://github.com/TaxoDros/TaxoDros.github.io/issues/10#issuecomment-1957012593, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABDFPJEBWGWATQFEXAEHCUTYUYJETAVCNFSM6AAAAABDRLP4JWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGAYTENJZGM. You are receiving this because you were mentioned.Message ID: @.***>
as mentioned by @myrmoteras in https://github.com/TaxoDros/TaxoDros.github.io/issues/5