cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.5281/zenodo.1626322
title: Wikipedia Edit Event Data 2018 (WikiEvent.2018)

description: The "Wikipedia Edit Event Data 2018 (WikiEvent.2018)" gives the time, user name, and article title of every edit that any registered and logged-in Wikipedia user performed on any article in the English-language edition of Wikipedia from January 15th, 2001 (the launch of Wikipedia) to January 1st, 2018. The edit event data has been extracted from the file 'enwiki-20180101-stub-meta-history.xml.gz'; which was at that time linked from 'https://dumps.wikimedia.org/enwiki/20180101/'. These files get deleted some months after data collection - however the information is still available in any file 'enwiki-&lt;date&gt;-stub-meta-history.xml.gz' where &lt;date&gt; is 20180101 or later. These data are provided by the Wikimedia Foundation licensed under the GNU Free Documentation License (GFDL) and the Creative Commons Attribution-Share-Alike 3.0 License. The Wikipedia Edit Event Data 2018 comprises one file ('WikiEvent.2018.csv') giving a table with 3 columns and more than 360 million rows in CSV format. Cell delimiter is semicolon (';') and strings are quoted by double-quotes ('"'). The table has a header given in the first row and the three columns are labeled 'time', 'user', and 'article' respectively. The uncompressed size of the file is about 17.1 GB. Time is given by integers representing milliseconds from January 1st, 1970 at 0:00 to the time of the edit. Precision of edit times, however, is given by the second so that the last three digits of every time value are equal to '000'. The edit events are given in ascending order with respect to time (older edits before younger edits). An article is a page in Namespace 0 (the 'main namespace' or 'article namespace') that is not a redirect. An edit (that is, a new revision of an article) is considered to be performed by a registered and logged-in user if the 'contributor' is given in an XML element &lt;username&gt;...&lt;/username&gt; in the referenced stub-file. (It is considered to be an anonymous edit if the 'contributor' is given in an XML element &lt;ip&gt;...&lt;/ip&gt;. Anonymous edits are not recorded in the table.) Triples (time,user,article) are unique by construction: if the same user edits the same article in the same second more than once, only one of these edits appears in the table. The WikiEvent.2018 data was originally used in: Lerner and Lomi (2020). <strong>Reliability of relational event model estimates under sampling: how to fit a relational event model to 360 million dyadic events.</strong> <em>Network Science</em>, 8(1):97-135. (DOI: https://doi.org/10.1017/nws.2019.57) How to analyze the WikiEvent Data with relational event models is explained in the eventnet tutorial at: https://github.com/juergenlerner/eventnet/wiki/Large-event-networks-(tutorial).
DOI: 10.6084/m9.figshare.13795589
title: Supplementary Material for: Daprodustat Compared with Epoetin Beta Pegol for Anemia in Japanese Patients Not on Dialysis: A 52-Week Randomized Open-Label Phase 3 Trial

description: <b><i>Background:</i></b> Daprodustat is an oral agent that stimulates erythropoiesis by inhibiting the prolyl hydroxylases which mark hypoxia-inducible factor for degradation through hydroxylation. Its safety and efficacy (noninferiority) were assessed in this 52-week, open-label study. <b><i>Methods:</i></b> Japanese patients not on dialysis (ND) (<i>N</i> = 299) with anemia of CKD (stages G3, G4, and G5) with iron parameters of ferritin &gt;100 ng/mL or transferrin saturation &gt;20% at screening were randomized to daprodustat or epoetin beta pegol (continuous erythropoietin receptor activator [CERA], also known as methoxy polyethylene glycol-epoetin beta). After initiation of the study, the daprodustat starting dose for erythropoiesis-stimulating agent (ESA)-naïve participants was revised, and daprodustat was started at 2 or 4 mg once daily depending on baseline hemoglobin. ESA users switched to daprodustat 4 mg once daily. CERA was started at 25 μg every 2 weeks for ESA-naïve patients and 25–250 μg every 4 weeks for ESA users based on previous ESA dose. In both treatment groups, dose was adjusted every 4 weeks based on hemoglobin level and changed according to a prespecified algorithm. The primary endpoint was mean hemoglobin level during weeks 40–52 in the intention-to-treat (ITT) population. ESA-naïve patients who entered before the protocol amendment revising the daprodustat starting dose were excluded from the ITT population. <b><i>Results:</i></b> Mean hemoglobin levels during weeks 40–52 were 12.0 g/dL in the daprodustat group (<i>n</i> = 108; 95% confidence interval [CI], 11.8–12.1) and 11.9 g/dL for CERA (<i>n</i> = 109; 95% CI 11.7–12.0); the difference between the groups was 0.1 g/dL (95% CI −0.1 to 0.3 g/dL). The lower limit of the 95% CI of the difference was greater than the prespecified margin of −1.0 g/dL. The mean hemoglobin level was within the target range (11.0–13.0 g/dL) during weeks 40–52 for 92% of participants in both groups. There was no meaningful difference in the frequencies of adverse events. <b><i>Conclusions:</i></b> Oral daprodustat was noninferior to CERA in achieving and maintaining target hemoglobin levels in Japanese ND patients. Daprodustat was well tolerated, with no new safety concerns identified.
DOI: 10.6084/m9.figshare.13736935
title: Residue-centric rate of sequence evolution according to Rate4Site on orthogroups of 14 fungal species

description: Overall, 42 descriptors (features) are mapped on 2129854 residues comprising 3797 unique proteins.The legend for each descriptor is given in the associated header file.<br><br>Columns 1-4 provide protein identifiers:<br>- SGD identifier,<br>- ORF,<br>- UniprotKB,<br>- PDB code and chain of closest structure<br><br>Columns 5-8 correspond to the length in number of residues for each of the previously defined identifiers:<br>Columns 9-12 contain the residue number of each aligned position within the full sequence.<br><br>Columns 13-14 contain the residue name of each aligned position in respectively the sequence and the structure.<br><br>Columns 15-16 indicates whether aligned position correspond to a gap (indel) position in the sequence and the structure.<br><br>Columns 17-20 indicates whether the protein has disorder predictions from IUPRED or D2P2, evolutionary rate from Rate4Site and a PDB structure matching the protein.<br><br>Columns 21-24 contain the raw and normalized evolutionary rates at each position as well as the min. and max. evolutionary rate in the proteins (from raw values).<br><br>Columns 25-31 correspond to the information relevant to the PDB structure:- Identity % <br>- Overlap %<br>- Resolution<br>- Number of PDB matched<br>- Number of subunits in closest structure<br>- QSBIO error probability on quaternary structure assignment<br><br>Columns 32-36 correspond to the geometric descriptor which indicate whether the residue is:<br>- surface exposed<br>- buried<br>- at the interface<br>- relative Accessible Surface Area in monomeric form<br>-relative Accessible Surface Area in Biological UnitColumn 37-42 are indicating the various biophysical features mapped to the residue:<br>- predicted disordered by IUPRED<br>- predicted NOT disordered by IUPRED<br>- predicted disordered by D2P2<br>- predicted NOT disordered by D2P2<br>- predicted to be in PFAM or SUPERFAMILY domain<br>- predicted NOT to be in PFAM or SUPERFAMILY domain<br>
DOI: 10.6084/m9.figshare.13736935.v2
title: Residue-centric rate of sequence evolution according to Rate4Site on orthogroups of 14 fungal species

description: Overall, 42 descriptors (features) are mapped on 2129854 residues comprising 3797 unique proteins.The legend for each descriptor is given in the associated header file.<br><br>Columns 1-4 provide protein identifiers:<br>- SGD identifier,<br>- ORF,<br>- UniprotKB,<br>- PDB code and chain of closest structure<br><br>Columns 5-8 correspond to the length in number of residues for each of the previously defined identifiers:<br>Columns 9-12 contain the residue number of each aligned position within the full sequence.<br><br>Columns 13-14 contain the residue name of each aligned position in respectively the sequence and the structure.<br><br>Columns 15-16 indicates whether aligned position correspond to a gap (indel) position in the sequence and the structure.<br><br>Columns 17-20 indicates whether the protein has disorder predictions from IUPRED or D2P2, evolutionary rate from Rate4Site and a PDB structure matching the protein.<br><br>Columns 21-24 contain the raw and normalized evolutionary rates at each position as well as the min. and max. evolutionary rate in the proteins (from raw values).<br><br>Columns 25-31 correspond to the information relevant to the PDB structure:- Identity % <br>- Overlap %<br>- Resolution<br>- Number of PDB matched<br>- Number of subunits in closest structure<br>- QSBIO error probability on quaternary structure assignment<br><br>Columns 32-36 correspond to the geometric descriptor which indicate whether the residue is:<br>- surface exposed<br>- buried<br>- at the interface<br>- relative Accessible Surface Area in monomeric form<br>-relative Accessible Surface Area in Biological UnitColumn 37-42 are indicating the various biophysical features mapped to the residue:<br>- predicted disordered by IUPRED<br>- predicted NOT disordered by IUPRED<br>- predicted disordered by D2P2<br>- predicted NOT disordered by D2P2<br>- predicted to be in PFAM or SUPERFAMILY domain<br>- predicted NOT to be in PFAM or SUPERFAMILY domain<br>
DOI: 10.6084/m9.figshare.13736935.v1
title: Residue-centric rate of sequence evolution according to Rate4Site on orthogroups of 14 fungal species

description: Overall, 42 descriptors (features) are mapped on 2129854 residues comprising 3797 unique proteins.The legend for each descriptor is given in the associated header file.<br><br>Columns 1-4 provide protein identifiers:<br>- SGD identifier,<br>- ORF,<br>- UniprotKB,<br>- PDB code and chain of closest structure<br><br>Columns 5-8 correspond to the length in number of residues for each of the previously defined identifiers:<br>Columns 9-12 contain the residue number of each aligned position within the full sequence.<br><br>Columns 13-14 contain the residue name of each aligned position in respectively the sequence and the structure.<br><br>Columns 15-16 indicates whether aligned position correspond to a gap (indel) position in the sequence and the structure.<br><br>Columns 17-20 indicates whether the protein has disorder predictions from IUPRED or D2P2, evolutionary rate from Rate4Site and a PDB structure matching the protein.<br><br>Columns 21-24 contain the raw and normalized evolutionary rates at each position as well as the min. and max. evolutionary rate in the proteins (from raw values).<br><br>Columns 25-31 correspond to the information relevant to the PDB structure:- Identity % <br>- Overlap %<br>- Resolution<br>- Number of PDB matched<br>- Number of subunits in closest structure<br>- QSBIO error probability on quaternary structure assignment<br><br>Columns 32-36 correspond to the geometric descriptor which indicate whether the residue is:<br>- surface exposed<br>- buried<br>- at the interface<br>- relative Accessible Surface Area in monomeric form<br>-relative Accessible Surface Area in Biological UnitColumn 37-42 are indicating the various biophysical features mapped to the residue:<br>- predicted disordered by IUPRED<br>- predicted NOT disordered by IUPRED<br>- predicted disordered by D2P2<br>- predicted NOT disordered by D2P2<br>- predicted to be in PFAM or SUPERFAMILY domain<br>- predicted NOT to be in PFAM or SUPERFAMILY domain<br>
DOI: 10.6084/m9.figshare.13735537.v1
title: Protein-centric rate of sequence evolution according to Rate4Site on orthogroups of 14 fungal species

description: Overall, 25 descriptors (features) are calculated for 3797 unique proteins.The legend for each descriptor is given in the associated header file.<br><br>Columns 1-5 provide protein identifiers:<br>- ORF, <br>- SGD Gene Name, <br>- UniprotKB, <br>- Matching PDB structure?<br>- PDB code of closest structure<br><br>Columns 6-8 correspond to protein expression:<br>- Integrated abundance in ppm,<br>- log10 abundance,<br>- bins of abundance (5 bins)<br><br>Columns 9-16 contain evolutionary rates averaged over:<br>- Full sequence<br>- Disordered residues<br>- Not Disordered residues<br>- Domain residues<br>- Not Domain residues<br>- Residues with PDB coordinates<br>- Surface residues (&gt;25% relative ASA)<br>- Buried residues (&lt;25% relative ASA)<br><br>Column 17 indicates whether both domains and disordered regions coexist (at least 20 residues for each)<br><br>Column 18-25 give the number of residues within each region considered for the average of evolutionary rates in column 9-16.<br><br><br>
DOI: 10.5281/zenodo.4522067
title: Wikipedia Edit Event Data 2021 (WikiEvent.2021)

description: The "Wikipedia Edit Event Data 2021 (WikiEvent.2021)" gives the time, user name, and article title of every edit that any registered and logged-in Wikipedia user performed on any article in the English-language edition of Wikipedia from January 15th, 2001 (the launch of Wikipedia) to January 2021. This dataset extends the older version WikiEven.2018 (https://zenodo.org/record/1626323). The edit event data has been extracted from the file 'enwiki-20210101-stub-meta-history.xml.gz'; which was at that time linked from 'https://dumps.wikimedia.org/enwiki/20210101/'. These files get deleted some months after data collection - however the information is still available in any file 'enwiki-&lt;date&gt;-stub-meta-history.xml.gz' where &lt;date&gt; is 20210101 or later. These data are provided by the Wikimedia Foundation licensed under the GNU Free Documentation License (GFDL) and the Creative Commons Attribution-Share-Alike 3.0 License. The Wikipedia Edit Event Data 2021 comprises the file ('WikiEvent.2021.csv') giving a table with 3 columns and more than 450 million rows in CSV format. Cell delimiter is semicolon (';') and strings are quoted by double-quotes ('"'). The table has a header given in the first row and the three columns are labeled 'time', 'user', and 'article' respectively. The uncompressed size of the file is about 23 GB. The small CSV file 'WikiEvent.2021_excerpt.csv' contains the first few lines of the larger file and serves to illustrate its structure. Time is given by integers representing milliseconds from January 1st, 1970 at 0:00 to the time of the edit. Precision of edit times, however, is given by the second so that the last three digits of every time value are equal to '000'. The edit events are given in ascending order with respect to time (older edits before younger edits). An article is a page in Namespace 0 (the 'main namespace' or 'article namespace') that is not a redirect. An edit (that is, a new revision of an article) is considered to be performed by a registered and logged-in user if the 'contributor' is given in an XML element &lt;username&gt;...&lt;/username&gt; in the referenced stub-file. (It is considered to be an anonymous edit if the 'contributor' is given in an XML element &lt;ip&gt;...&lt;/ip&gt;. Anonymous edits are not recorded in the table.) Triples (time,user,article) are unique by construction: if the same user edits the same article in the same second more than once, only one of these edits appears in the table. The related (older) WikiEvent.2018 data was originally used in: Lerner and Lomi (2020). <strong>Reliability of relational event model estimates under sampling: how to fit a relational event model to 360 million dyadic events.</strong> <em>Network Science</em>, 8(1):97-135. (DOI: https://doi.org/10.1017/nws.2019.57) How to analyze the WikiEvent Data with relational event models is explained in the eventnet tutorial at: https://github.com/juergenlerner/eventnet/wiki/Large-event-networks-(tutorial).
DOI: 10.5281/zenodo.4522066
title: Wikipedia Edit Event Data 2021 (WikiEvent.2021)

description: The "Wikipedia Edit Event Data 2021 (WikiEvent.2021)" gives the time, user name, and article title of every edit that any registered and logged-in Wikipedia user performed on any article in the English-language edition of Wikipedia from January 15th, 2001 (the launch of Wikipedia) to January 2021. This dataset extends the older version WikiEven.2018 (https://zenodo.org/record/1626323). The edit event data has been extracted from the file 'enwiki-20210101-stub-meta-history.xml.gz'; which was at that time linked from 'https://dumps.wikimedia.org/enwiki/20210101/'. These files get deleted some months after data collection - however the information is still available in any file 'enwiki-&lt;date&gt;-stub-meta-history.xml.gz' where &lt;date&gt; is 20210101 or later. These data are provided by the Wikimedia Foundation licensed under the GNU Free Documentation License (GFDL) and the Creative Commons Attribution-Share-Alike 3.0 License. The Wikipedia Edit Event Data 2021 comprises the file ('WikiEvent.2021.csv') giving a table with 3 columns and more than 450 million rows in CSV format. Cell delimiter is semicolon (';') and strings are quoted by double-quotes ('"'). The table has a header given in the first row and the three columns are labeled 'time', 'user', and 'article' respectively. The uncompressed size of the file is about 23 GB. The small CSV file 'WikiEvent.2021_excerpt.csv' contains the first few lines of the larger file and serves to illustrate its structure. Time is given by integers representing milliseconds from January 1st, 1970 at 0:00 to the time of the edit. Precision of edit times, however, is given by the second so that the last three digits of every time value are equal to '000'. The edit events are given in ascending order with respect to time (older edits before younger edits). An article is a page in Namespace 0 (the 'main namespace' or 'article namespace') that is not a redirect. An edit (that is, a new revision of an article) is considered to be performed by a registered and logged-in user if the 'contributor' is given in an XML element &lt;username&gt;...&lt;/username&gt; in the referenced stub-file. (It is considered to be an anonymous edit if the 'contributor' is given in an XML element &lt;ip&gt;...&lt;/ip&gt;. Anonymous edits are not recorded in the table.) Triples (time,user,article) are unique by construction: if the same user edits the same article in the same second more than once, only one of these edits appears in the table. The related (older) WikiEvent.2018 data was originally used in: Lerner and Lomi (2020). <strong>Reliability of relational event model estimates under sampling: how to fit a relational event model to 360 million dyadic events.</strong> <em>Network Science</em>, 8(1):97-135. (DOI: https://doi.org/10.1017/nws.2019.57) How to analyze the WikiEvent Data with relational event models is explained in the eventnet tutorial at: https://github.com/juergenlerner/eventnet/wiki/Large-event-networks-(tutorial).
DOI: 10.6084/m9.figshare.13735537
title: Protein-centric rate of sequence evolution according to Rate4Site on orthogroups of 14 fungal species

description: Overall, 25 descriptors (features) are calculated for 3797 unique proteins.The legend for each descriptor is given in the associated header file.<br><br>Columns 1-5 provide protein identifiers:<br>- ORF, <br>- SGD Gene Name, <br>- UniprotKB, <br>- Matching PDB structure?<br>- PDB code of closest structure<br><br>Columns 6-8 correspond to protein expression:<br>- Integrated abundance in ppm,<br>- log10 abundance,<br>- bins of abundance (5 bins)<br><br>Columns 9-16 contain evolutionary rates averaged over:<br>- Full sequence<br>- Disordered residues<br>- Not Disordered residues<br>- Domain residues<br>- Not Domain residues<br>- Residues with PDB coordinates<br>- Surface residues (&gt;25% relative ASA)<br>- Buried residues (&lt;25% relative ASA)<br><br>Column 17 indicates whether both domains and disordered regions coexist (at least 20 residues for each)<br><br>Column 18-25 give the number of residues within each region considered for the average of evolutionary rates in column 9-16.<br><br><br>
DOI: 10.6084/m9.figshare.13738657.v1
title: Abundance imparts evolutionary constraints of similar magnitude on the buried, surface, and disordered regions of proteins

description: Here, we integrate residue-level and protein-level data for different structural regions such as: disordered regions, structured domains, surface and buried residues. <br><br>These datasets serve the analysis of evolutionary constraints within-and-across structural regions of yeast proteins, and were analyzed in a manuscript submitted to Frontiers Molecular Biosciences entitled "Abundance imparts evolutionary constraints of similar magnitude on the buried, surface, and disordered regions of proteins"<br><br>The proteins sequences were taken from the reference S. cerevisiae proteome from SGD, filtering for proteins with known orthologs in 14 fungi species, as defined in Wapinsky et al., Nature (2007).<br><br>Two datasets were used for our analysis: - a protein-centric dataset (PROTEIN-EVORATE.tsv)<br>- a residue-centric dataset (RESIDUE-EVORATE.tsv)<br><br>Both datasets are available as regular data table formatted to Tab Separated Value (TSV). <br><br>At the residue level, 42 features are mapped on 2,129,854 residues comprising 3797 unique proteins.<br>At the protein level, 25 features are calculated for 3797 unique proteins.<br><br>Each feature is described in a text file distributed along the datasets (starting with "header-").<br>
DOI: 10.6084/m9.figshare.13200872
title: ESM1: Erebus Volcanic Province: petrology

description: Whole-rock, clinopyroxene, englacial tephra and marine drill core volcanic rock and glass chemistry ± isotopes ± chronology from published sources (referenced) and new data.
DOI: 10.6084/m9.figshare.13200872.v2
title: ESM1: Erebus Volcanic Province: petrology

description: Whole-rock, clinopyroxene, englacial tephra and marine drill core volcanic rock and glass chemistry ± isotopes ± chronology from published sources (referenced) and new data.
DOI: 10.6084/m9.figshare.13200872.v1
title: ESM1: Erebus Volcanic Province – II. Petrology

description: Whole-rock, clinopyroxene, englacial tephra and marine drill core volcanic rock and glass chemistry ± isotopes ± chronology from published sources (referenced) and new data.
DOI: 10.5281/zenodo.4519167
title: Dataset to "Atmospheric CO2 exchange of a small mountain lake: limitations of eddy covariance and boundary layer modeling methods in complex terrain."

description: Half-hourly data of eddy covariance CO2 flux measurements at a small mountain lake and auxiliary data (wind speed and direction at the east and west shore of the lake; air temperature; relative humidity; precipitation; incoming and outgoing shortwave and longwave radiation; water tempreature (temperature profile); pCO2 in water and air). Both CO2 fluxes calculated based on the Ogive Optimization method and based on standard EC processing are included.
DOI: 10.5281/zenodo.4519166
title: Dataset to "Atmospheric CO2 exchange of a small mountain lake: limitations of eddy covariance and boundary layer modeling methods in complex terrain."

description: Half-hourly data of eddy covariance CO2 flux measurements at a small mountain lake and auxiliary data (wind speed and direction at the east and west shore of the lake; air temperature; relative humidity; precipitation; incoming and outgoing shortwave and longwave radiation; water tempreature (temperature profile); pCO2 in water and air). Both CO2 fluxes calculated based on the Ogive Optimization method and based on standard EC processing are included.