{"doi":"10.1007/s12013-024-01455-x","title":"Effects of Aging on Intrinsic Protein Disorder in Human Lenses and Zonules","abstract":"This study aims to compare the levels of intrinsic protein disorder within the human lens and zonule proteomes and investigate the role of aging as a potential influencing factor on disorder levels. A cross-sectional proteomic analysis was employed, utilizing a dataset of 1466 proteins derived from the lens and zonule proteomes previously published by Wang et al. and De Maria et al. Bioinformatics tools, including a composition profiler and a rapid intrinsic disorder analysis online tool, were used to conduct a comparative analysis of protein disorder. Statistical tests such as ANOVA, Tukey's HSD, and chi-squared tests were applied to evaluate differences between groups. The study revealed distinct amino acid compositions for each proteome, showing a direct correlation between aging and increased protein disorder in the zonular proteomes, whereas the lens proteomes exhibited the opposite trend. Findings suggest that age-related changes in intrinsic protein disorder within the lens and zonule proteomes may be linked to structural transformations in these tissues. Understanding how protein disorder evolves with age could enhance knowledge of the molecular basis for age-related conditions such as cataracts and pseudoexfoliation, potentially leading to better therapeutic strategies.","journal":"Cell Biochemistry and Biophysics","year":2024,"id":468793,"datarank":0.20794415416798362,"base_score":1.3862943611198906,"endowment":1.3862943611198906,"self_citation_contribution":0.20794415416798362,"citation_network_contribution":0.0,"self_endowment_contribution":0.20794415416798362,"citer_contribution":0.0,"corpus_percentile":35.18991258606018,"corpus_rank":8206,"citation_count":3,"citer_count":2,"citers_with_citation_signal":0,"citers_with_endowment":0,"datacite_reuse_total":0,"is_dataset":true,"is_dataset_confidence":0.6266,"is_data_producer":false,"deposit_databanks":null,"is_oa":true,"file_count":0,"downloads":0,"has_version_chain":false,"published_date":"2024-01-01","fair_score":45.8333,"fair_percentile":59.49250993579945,"algorithm_id":"datarank_citation_only_1hop_v6","ranking_scope":"data_only","authors":[{"id":1102626,"name":"Colin K. Kim","orcid":null,"position":1,"is_corresponding":false},{"id":756976,"name":"Mak B. Djulbegovic","orcid":"0000-0002-4149-7450","position":2,"is_corresponding":false},{"id":1076949,"name":"David J. Taylor Gonzalez","orcid":"0009-0001-2089-6153","position":3,"is_corresponding":false},{"id":1268389,"name":"Jason Greenfield","orcid":"0000-0001-8801-1588","position":4,"is_corresponding":false},{"id":168286,"name":"Vladimir N. Uversky","orcid":"0000-0002-4037-5857","position":5,"is_corresponding":false},{"id":364899,"name":"Allister Gibbons","orcid":"0000-0001-5747-6059","position":6,"is_corresponding":false},{"id":378463,"name":"Carol L. Karp","orcid":"0000-0002-6452-7181","position":7,"is_corresponding":false},{"id":1076950,"name":"Michael Antonietti","orcid":"0000-0001-5526-1396","position":0,"is_corresponding":true}],"reference_count":42,"raw_metadata":null,"created_at":"2026-07-19T02:05:23.500722Z","pmid":"39117985","pmcid":"PMC11576620","fwci":null,"citation_percentile":null,"influential_citations":0,"oa_status":null,"license":null,"views":0,"total_file_size_bytes":0,"version_count":0,"fair_f":33.3333,"fair_a":62.5,"fair_i":60.0,"fair_r":50.0,"fair_zscore":0.4506,"fair_rationale":{"fair_score":45.83,"has_llm":true,"taxonomy_version":"fair_taxonomy_v5","dimensions":{"F":{"name":"Findable","score":33.33,"criteria":[{"key":"f_dataset_pid","label":"Persistent identifier for the data","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"Neither a PID-scheme string nor a data URL is given for the study's own dataset.","anchors":["RDA-F1-01D — FAIR Data Maturity Model: 'Data is identified by a persistent identifier' (priorit","RDA-F1-02D — FAIR Data Maturity Model: 'Data is identified by a globally unique identifier'","FsF-F1-02D — F-UJI/FAIRsFAIR: 'Data is assigned a persistent identifier'"],"scored":true,"signal":null},{"key":"f_repository_named","label":"Named repository","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No repository is named as the holder of the data; the data are stated to be within the manuscript or supplementary files. [majority verdict 'no' (3/5 passes agreed)]","anchors":["RDA-F4-01M — FAIR Data Maturity Model: metadata is offered so it can be harvested and indexed (","NIH DMS Policy Element 4 (NOT-OD-21-014) — name the repository where data will be archived","NSTC Desirable Characteristics of Data Repositories (2022) — 'Long-Term Sustainability', 'Reten"],"scored":true,"signal":null},{"key":"f_data_availability_statement","label":"Data-availability statement","kind":"llm","weight":2.0,"fraction":0.5,"verdict":"partial","evidence":"Data is provided within the manuscript or supplementary information files.","grounded":true,"rationale":"The statement points to the article and supplementary files (Colavizza category 2), not a repository record.","anchors":["Colavizza, Hrynaszkiewicz, Staden, Whitaker & McGillivray (2020), 'The citation advantage of li","Springer Nature research data policy — Data Availability Statements: standard statement templat","RDA-F3-01M — metadata clearly and explicitly includes the identifier of the data it describes"],"scored":false,"signal":null},{"key":"f_discovery_metadata","label":"Description of the dataset as an object","kind":"llm","weight":2.0,"fraction":1.0,"verdict":"yes","evidence":"Supplementary S2 Zonule Fasta File Supplementary S3 25-37 year old Lens Fasta Supplementary S4 58 year old Lens fasta Tukey HSD S1","grounded":true,"rationale":"The supplementary information section lists the deposited files by name, constituting an itemised inventory of the dataset. [majority verdict 'yes' (3/5 passes agreed)]","anchors":["RDA-F2-01M — 'Rich metadata is provided to allow discovery' (priority Essential)","FsF-F2-01M — F-UJI: 'Metadata includes descriptive core elements to support data findability'","FsF-R1-01MD — F-UJI: 'Metadata specifies the content of the data'"],"scored":false,"signal":null},{"key":"f_dataset_cited","label":"Dataset formally cited","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No identifier for the dataset appears anywhere in the paper, neither in the body nor in the reference list. [majority verdict 'no' (4/5 passes agreed)]","anchors":["FORCE11 Joint Declaration of Data Citation Principles (2014) — data should be cited as a first-","RDA-F3-01M — metadata clearly and explicitly includes the identifier of the data it describes","FsF-F3-01M — F-UJI: 'Metadata includes the identifier of the data it describes'"],"scored":true,"signal":null}]},"A":{"name":"Accessible","score":62.5,"criteria":[{"key":"a_data_openly_accessible","label":"Access route free of preconditions","kind":"llm","weight":2.0,"fraction":1.0,"verdict":"yes","evidence":"Data is provided within the manuscript or supplementary information files.","grounded":true,"rationale":"The statement gives a route to the data with no precondition; the data are included in the article and supplementary files.","anchors":["RDA-A1.1-01D — 'Data is accessible through a free access protocol'","FsF-A1-01M — F-UJI: 'Metadata contains access level and access conditions of the data'","NSTC Desirable Characteristics of Data Repositories (2022) — 'Free and Easy Access'"],"scored":true,"signal":null},{"key":"a_access_conditions_stated","label":"Access level labelled","kind":"llm","weight":1.0,"fraction":0.5,"verdict":"partial","evidence":"Data is provided within the manuscript or supplementary information files.","grounded":true,"rationale":"The text describes an action (data is in the manuscript or supplementary files) but does not label the access level with a standard vocabulary term. [majority verdict 'partial' (4/5 passes agreed)]","anchors":["FsF-A1-01M — F-UJI: 'Metadata contains access level and access conditions of the data'","RDA-A1-01M — metadata contains information to enable the user to get access to the data","COAR Controlled Vocabularies — Access Rights v1.0 (open / embargoed / restricted / metadata-onl"],"scored":false,"signal":null},{"key":"a_controlled_access_for_sensitive","label":"Gatekeeper for sensitive data","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No gatekeeper of any kind is named; the data are not described as sensitive and no controlled-access procedure is mentioned.","anchors":["NIH Genomic Data Sharing Policy (NOT-OD-14-124) — controlled-access via a Data Access Committee","RDA-A1.2-01D — 'Data is accessible through an access protocol that supports authentication and ","NIH DMS Policy Element 5 (NOT-OD-21-014) — Access, Distribution, or Reuse Considerations (conse"],"scored":false,"signal":null},{"key":"a_timeline_retention","label":"Availability timing & retention","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No sentence in the paper addresses when the data become available or how long they will persist. [majority verdict 'no' (4/5 passes agreed)]","anchors":["NIH DMS Plan Element 4 (NOT-OD-21-014) — Data Preservation, Access, and Associated Timelines","NSTC Desirable Characteristics (2022), Organizational Infrastructure: 'Retention Policy'","RDA-A2-01M — 'Metadata is guaranteed to remain available after data is no longer available'"],"scored":false,"signal":null}]},"I":{"name":"Interoperable","score":60.0,"criteria":[{"key":"i_open_nonproprietary_format","label":"Open file format","kind":"llm","weight":1.0,"fraction":1.0,"verdict":"yes","evidence":"The corresponding protein sequences were downloaded from UniProt in FASTA format","grounded":true,"rationale":"FASTA is an open, community-standard format and is named for the data (the supplementary files are FASTA).","anchors":["FsF-R1.3-02D — F-UJI: 'Data is available in a file format recommended by the target research co","RDA-R1.3-02D — data is expressed in a machine-understandable community standard","RDA-I1-01D — data uses a knowledge representation expressed in a standardised format"],"scored":true,"signal":null},{"key":"i_community_standard_vocabulary","label":"Community standard / vocabulary","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No data or metadata community standard (e.g., MIAME, OBO ontology) is named; the only standards invoked are disorder prediction tools, not data standards.","anchors":["RDA-R1.3-01M — 'Metadata complies with a community standard' (priority Essential)","RDA-R1.3-01D — 'Data complies with a community standard'","RDA-I2-01M — '(Meta)data use vocabularies that follow FAIR principles'"],"scored":false,"signal":null},{"key":"i_qualified_references","label":"Identifiers for the resources the data depend on","kind":"llm","weight":0.5,"fraction":1.0,"verdict":"yes","evidence":"10.1167/iovs.12-11168","grounded":true,"rationale":"The paper references the source datasets (Wang et al. and De Maria et al.) with DOIs in the reference list, which are identifiers for resources other than the study's own data. [majority verdict 'yes' (4/5 passes agreed)]","anchors":["RDA-I3-01M — '(meta)data include references to other (meta)data'","RDA-I3-03M — 'metadata includes qualified references to other metadata'","FsF-I3-01M — F-UJI: 'Metadata includes links between the data and its related entities'"],"scored":false,"signal":null}]},"R":{"name":"Reusable","score":50.0,"criteria":[{"key":"r_reuse_license","label":"Reuse licence","kind":"llm","weight":2.0,"fraction":1.0,"verdict":"yes","evidence":"This article is licensed under a Creative Commons Attribution 4.0 International License","grounded":true,"rationale":"The article's CC BY 4.0 license covers the supplementary materials containing the data. [majority verdict 'yes' (4/5 passes agreed)]","anchors":["RDA-R1.1-01M — 'Metadata includes information about the licence under which the data can be reu","RDA-R1.1-02M — 'Metadata refers to a standard reuse licence'","RDA-R1.1-03M — 'Metadata refers to a machine-understandable reuse licence'"],"scored":true,"signal":null},{"key":"r_provenance_methods","label":"Provenance of the data","kind":"llm","weight":1.0,"fraction":0.5,"verdict":"partial","evidence":"PONDR ® VSL2, PONDR ® VL3, PONDR ® VLXT, PONDR ® FIT, and IUPred Short and Long","grounded":false,"rationale":"The text names the specific software tools used to produce the disorder predictions. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (2/5 passes agreed)]","anchors":["RDA-R1.2-01M — 'Metadata includes provenance information according to community- specific standa","FsF-R1.2-01M — F-UJI: 'Metadata includes provenance information about data creation or generati","W3C PROV-O (W3C Recommendation, 2013) — the entity/activity/agent model of provenance"],"scored":false,"signal":null},{"key":"r_documentation_codebook","label":"Documentation / codebook","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No documentation object (README, codebook, data dictionary) is named as accompanying the data. [majority verdict 'no' (4/5 passes agreed)]","anchors":["RDA-R1-01M — '(Meta)data are richly described with a plurality of accurate and relevant attribu","FsF-R1-01MD — F-UJI: 'Metadata specifies the content of the data'","NIH DMS Policy Element 3 (NOT-OD-21-014) — Standards (documentation and metadata to accompany t"],"scored":false,"signal":null},{"key":"r_versioning","label":"Snapshot identified","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"Neither a version token nor a date is given for the dataset; the data are referred to as static supplementary files.","anchors":["DataCite Metadata Schema 4.6 — the 'Version' property","RDA-R1.2-01M — provenance information (which version was used is provenance)","NSTC Desirable Characteristics of Data Repositories (2022) — 'Provenance', 'Retention Policy'"],"scored":true,"signal":null},{"key":"x_code_availability","label":"Analysis code available","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No code availability is mentioned; the study used online tools but no custom code is provided.","anchors":["NIH DMS Policy Element 2 (NOT-OD-21-014) — 'Related Tools, Software and/or Code'","FAIR4RS Principles v1.0 (Chue Hong et al., 2022; RDA/FORCE11/ReSA) — FAIR Principles for Resear","FORCE11 Software Citation Principles (Smith, Katz & Niemeyer, 2016, PeerJ CS 2:e86)"],"scored":true,"signal":null},{"key":"x_funding_attribution","label":"Funder and award number","kind":"llm","weight":0.5,"fraction":1.0,"verdict":"yes","evidence":"NIH Center Core Grant P30EY014801","grounded":true,"rationale":"An award number is stated for one of the funders.","anchors":["DataCite Metadata Schema 4.6 — 'FundingReference' property (funderName, funderIdentifier, award","Crossref Funder Registry — canonical funder identifiers for funding metadata","RDA-F2-01M — rich metadata provided to allow discovery (funding is part of the descriptive reco"],"scored":true,"signal":null}]}},"actions":[{"key":"f_dataset_pid","dimension":"F","label":"Persistent identifier for the data","action":"Mint or cite a persistent identifier for the dataset — a repository DOI or an accession from a registered repository — and print it in the paper. A bare URL is not persistent: it is the single most common cause of a dead data link five years after publication. For proteomics data, deposit in PRIDE (PXD accession) or ProteomeXchange.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"Neither a PID-scheme string nor a data URL is given for the study's own dataset.","gain":16.67,"priority":"essential","scored":true},{"key":"f_repository_named","dimension":"F","label":"Named repository","action":"Deposit the data in a repository registered in re3data/FAIRsharing (a domain repository such as GEO, SRA, dbGaP, PRIDE, or a generalist such as Zenodo, Dryad, Dataverse) and name it explicitly in the paper. A lab website is not an archive: it has no retention commitment and no accession. For proteomics data, deposit in PRIDE (PXD accession) or ProteomeXchange.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No repository is named as the holder of the data; the data are stated to be within the manuscript or supplementary files. [majority verdict 'no' (3/5 passes agreed)]","gain":16.67,"priority":"essential","scored":true},{"key":"f_dataset_cited","dimension":"F","label":"Dataset formally cited","action":"Cite the dataset in the reference list like a publication — creator, year, title, repository, DOI/accession — and cite it in-text where it is used. Only a reference- list entry is machine-readable to Crossref/DataCite, and only a citation lets the data earn credit. Cite the proteomics repository accession (e.g. from PRIDE (PXD accession) or ProteomeXchange) in the reference list.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No identifier for the dataset appears anywhere in the paper, neither in the body nor in the reference list. [majority verdict 'no' (4/5 passes agreed)]","gain":8.33,"priority":"important","scored":true},{"key":"x_code_availability","dimension":"R","label":"Analysis code available","action":"Publish the analysis code in a public forge, archive a tagged release with a DOI (Zenodo/Software Heritage), and cite that DOI in the paper. NIH DMS Element 2 asks for the tools and code, not only the data — and 'available on request' is not a locator. Archive the analysis code in a versioned repository (GitHub + a Zenodo release DOI).","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No code availability is mentioned; the study used online tools but no custom code is provided.","gain":8.33,"priority":"important","scored":true},{"key":"r_versioning","dimension":"R","label":"Snapshot identified","action":"Version the deposit and cite the exact version analysed (a version-specific DOI, or an accession with its version suffix). A reader reproducing your work against 'the current release' is reproducing it against a different dataset.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"Neither a version token nor a date is given for the dataset; the data are referred to as static supplementary files.","gain":4.17,"priority":"useful","scored":true},{"key":"f_data_availability_statement","dimension":"F","label":"Data-availability statement","action":"Replace the statement with the repository template: name the repository and give the accession or DOI (Colavizza category 3). This is the only DAS class associated with a measured citation advantage; 'available on reasonable request' and 'within the article' are not.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"Data is provided within the manuscript or supplementary information files.","why":"The statement points to the article and supplementary files (Colavizza category 2), not a repository record.","gain":0.0,"priority":"essential","scored":false},{"key":"a_access_conditions_stated","dimension":"A","label":"Access level labelled","action":"State the access level in words, using the standard vocabulary: 'These data are open access' / 'These data are controlled access'. A reader — and a harvester — should not have to infer the access level from the presence of a download link.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"Data is provided within the manuscript or supplementary information files.","why":"The text describes an action (data is in the manuscript or supplementary files) but does not label the access level with a standard vocabulary term. [majority verdict 'partial' (4/5 passes agreed)]","gain":0.0,"priority":"important","scored":false},{"key":"i_community_standard_vocabulary","dimension":"I","label":"Community standard / vocabulary","action":"Adopt and NAME your domain's data standard — the minimum-information checklist, metadata schema, or ontology your community uses (MIAME/MINSEQE, ISA-Tab, BIDS, an OBO ontology, HL7 FHIR/OMOP) — and say which one you followed. A reporting checklist standardises your paper; it does nothing for your data. In proteomics, describe the data with mzML or MIAPE.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No data or metadata community standard (e.g., MIAME, OBO ontology) is named; the only standards invoked are disorder prediction tools, not data standards.","gain":0.0,"priority":"important","scored":false},{"key":"r_provenance_methods","dimension":"R","label":"Provenance of the data","action":"Name the instruments, kits, and software — with versions — that produced the data, not just the verbs. 'Reads were aligned' is not provenance; 'aligned with STAR v2.7.9a to GRCh38' is, because someone else can rerun it.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"PONDR ® VSL2, PONDR ® VL3, PONDR ® VLXT, PONDR ® FIT, and IUPred Short and Long","why":"The text names the specific software tools used to produce the disorder predictions. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (2/5 passes agreed)]","gain":0.0,"priority":"important","scored":false},{"key":"r_documentation_codebook","dimension":"R","label":"Documentation / codebook","action":"Ship a README and a data dictionary IN the deposit — every file, every variable, its units, its allowed values, its missing-value codes. It is the cheapest single thing that makes a dataset usable by someone who was not in the lab, and a table buried in the article does not travel with the data.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No documentation object (README, codebook, data dictionary) is named as accompanying the data. [majority verdict 'no' (4/5 passes agreed)]","gain":0.0,"priority":"important","scored":false},{"key":"a_controlled_access_for_sensitive","dimension":"A","label":"Gatekeeper for sensitive data","action":"Route sensitive data through an institutional gatekeeper — deposit in a controlled- access repository (dbGaP, EGA) with a Data Access Committee and a published DUA — rather than through the corresponding author's inbox. An author-gated dataset dies with the author's email address, and 'on reasonable request' has been shown repeatedly not to yield data.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No gatekeeper of any kind is named; the data are not described as sensitive and no controlled-access procedure is mentioned.","gain":0.0,"priority":"useful","scored":false},{"key":"a_timeline_retention","dimension":"A","label":"Availability timing & retention","action":"State when the data become available AND how long they will be retained — cite the repository's preservation policy. NIH DMS Element 4 asks for both; most papers give neither.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No sentence in the paper addresses when the data become available or how long they will persist. [majority verdict 'no' (4/5 passes agreed)]","gain":0.0,"priority":"useful","scored":false}],"suggestions":["Mint or cite a persistent identifier for the dataset — a repository DOI or an accession from a registered repository — and print it in the paper. A bare URL is not persistent: it is the single most common cause of a dead data link five years after publication. For proteomics data, deposit in PRIDE (PXD accession) or ProteomeXchange.","Deposit the data in a repository registered in re3data/FAIRsharing (a domain repository such as GEO, SRA, dbGaP, PRIDE, or a generalist such as Zenodo, Dryad, Dataverse) and name it explicitly in the paper. A lab website is not an archive: it has no retention commitment and no accession. For proteomics data, deposit in PRIDE (PXD accession) or ProteomeXchange.","Cite the dataset in the reference list like a publication — creator, year, title, repository, DOI/accession — and cite it in-text where it is used. Only a reference- list entry is machine-readable to Crossref/DataCite, and only a citation lets the data earn credit. Cite the proteomics repository accession (e.g. from PRIDE (PXD accession) or ProteomeXchange) in the reference list.","Publish the analysis code in a public forge, archive a tagged release with a DOI (Zenodo/Software Heritage), and cite that DOI in the paper. NIH DMS Element 2 asks for the tools and code, not only the data — and 'available on request' is not a locator. Archive the analysis code in a versioned repository (GitHub + a Zenodo release DOI).","Version the deposit and cite the exact version analysed (a version-specific DOI, or an accession with its version suffix). A reader reproducing your work against 'the current release' is reproducing it against a different dataset."],"model":"deepseek/deepseek-v4-flash","agent_version":"fair_agent_v8","fulltext_source":"epmc_xml"},"fair_model":"deepseek/deepseek-v4-flash","fair_agent_version":"fair_agent_v8","fair_fulltext_source":"epmc_xml","fair_has_llm":true,"fair_computed_at":"2026-07-20T13:11:20.814793Z","clinical_trials":[],"software_tools":[],"db_accessions":[],"linked_datasets":[],"topics":[]}