GCRI · ثبتخانه
خاستگاه سابقه
Provenance is the account of where a record came from: who issued it, when, by what method, from which sources and through which transformations it passed before reaching the reader. Without it a record cannot be checked, weighed or corrected, only trusted or ignored. This page sets out how provenance is captured and expressed, why lineage chains break, and what the people who rely on registry records need to see before they do.
Record provenance on the record.
Record provenance: how the risk develops.
Issuer, date, method and source lineage. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Lineage breaks at hand-offs
Records pass between spreadsheets, databases, aggregators and exports. Each step can drop the issuer, the source reference or the method note. Once the chain is cut, later copies look authoritative while nothing connects them to what they were derived from.
Issuer ambiguity
Organisation names change, merge and are spelt many ways, and people share names. Without persistent identifiers for issuers, two bodies are recorded as one or one as two, and responsibility for an assertion can no longer be established.
Method drift
The method behind a field changes, through a new coding rule, a new instrument or a revised definition, while the field name stays the same. A series then joins incompatible values, and no reader can see where the join is.
Laundering through aggregation
An unsourced claim is copied by an aggregator, quoted in a report and indexed by search engines. Each reuse adds apparent authority and removes context, until the claim is cited back to its origin as if it were independent confirmation.
How record provenance is modelled, measured and tested.
مدل، مفروضات، دادهها و عدم قطعیت آن، به شکلی که دانشمند یا مهندس بررسی میکند. ساختارها از روشهای منتشرشده پیروی میکنند. مقادیر ترسیمشده تبیینیاند، نه یافته.
مجموعهدادهها و خاستگاه
The data classes behind record provenance and what is recorded about each before it is used.
| طبقهٔ داده | خاستگاه ثبت شد | وضوح اعلامشده | پروانه بررسی شد |
|---|---|---|---|
| تصاویر ماهوارهای، نوری و راداری | حسگر، سطح پردازش، تاریخ برداشت | اندازهٔ پیکسل و بازدید مجدد | بهازای هر صحنه |
| بازتحلیل و خروجی مدل اقلیمی | مدل، آزمایش، عضو، نسخه | شبکه و گام زمانی | بهازای هر انتشار |
| حسگرها و سنجههای درجا | ایستگاه، ابزار، سابقهٔ واسنجی | نقطه و نرخ نمونهبرداری | بهازای هر شبکه |
| مواجهه جمعیت و دارایی | روش، سال تولید، منابع ورودی | اندازهٔ سلول و یکا | بهازای هر انتشار |
| مرزها و جغرافیای مرجع | تولیدکننده، ویراست، تاریخ | مقیاس | بهازای هر ویراست |
- تبارنامه
- سابقهٔ W3C PROV از منبع تا شکل
- اصول
- FAIR: یافتنی، دسترسپذیر، همکنشپذیر، بازاستفادهپذیر
- شکافها
- بهصورت ناموجود نشان داده میشود، هرگز بیصدا پر نمیشود
Provenance lets a reader trace a figure in any domain to its source.
- آبIn practiceA flow series traces to gauge, rating curve and agency.What a reader can checkLineage chain
- غذاIn practiceA yield estimate traces to survey or model.What a reader can checkSource and method
- تنوع زیستیIn practiceA species record traces to its collector and dataset.What a reader can checkOccurrence provenance
Provenance underpins every edition of گزارشها. It follows W3C PROV-O (2013) and the record identifiers of NS-3 in the proposed Nexus Standards.
- Gaps in a lineage chain.
- Source agencies’ own provenance records.
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | برچسب |
|---|---|---|---|---|
| Records with complete issuer, date and method | share of records | monthly | Schema validation | مشاهدهشده |
| Lineage depth to a primary source | number of derivation steps | per record | Provenance graph | مشاهدهشده |
| Unresolved source references | count | weekly | Resolver checks | مشاهدهشده |
| Transformations without a recorded agent | count | monthly | Provenance graph audit | مشاهدهشده |
| Records with content hashes or signatures | share of records | monthly | Integrity check | مشاهدهشده |
| Issuers with a persistent identifier | share of issuers | quarterly | Identifier reconciliation | مشاهدهشده |
| Provenance inferred rather than declared | share of provenance statements | quarterly | Curation review | برآوردشده |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| منبع | What it gives | Licence class |
|---|---|---|
| W3C PROV-O and PROV-DM | The standard vocabulary of entities, activities and agents for expressing provenance graphs | W3C document licence, free to implement |
| DataCite Metadata Schema | Creator, contributor, date, relation and related-identifier fields for research outputs | CC0 for metadata |
| ROR (Research Organization Registry) | Persistent identifiers for research organisations, with name variants, relationships and succession | CC0, no restrictions |
| ORCID public data file | Persistent identifiers for researchers, with linked works, affiliations and funding | CC0 |
| GLEIF Legal Entity Identifier data | Identifiers, legal names and parent relationships for legal entities | CC0, no restrictions |
| PREMIS Data Dictionary | Preservation metadata for events, agents and rights on digital objects | Free to use, maintained by the Library of Congress |
| RO-Crate | A specification for packaging research data with its provenance in JSON-LD | Open specification, attribution |
Who decides, and what the evidence serves.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| چه کسی تصمیم میگیرد | The question | Evidence this page serves |
|---|---|---|
| Data stewards | Whether a record’s lineage is complete enough to publish or must be held for curation | Provenance completeness, unresolved references and transformations without a recorded agent |
| Journal and report editors | Whether a cited registry record can support a claim in a manuscript | Issuer identity, method, date and the depth of lineage to a primary source |
| Research integrity officers | Whether an assertion was altered, misattributed or fabricated | Time-stamped provenance graph, content hashes and the full edit history |
| National statistics offices | Whether administrative or registry records can enter published statistics | Source lineage, method stability over time and documented transformations |
Outputs this topic produces
- Record views listing issuer, issue date, method and source references for each assertion
- Provenance graphs tracing derived records back to their primary sources
- A provenance completeness check applied to every record before publication
- Method change notes marking where a field’s definition or instrument changed
What provenance research asks.
- What is the smallest set of facts that lets a reader judge a record’s origin?
- How much lineage should be captured automatically, and how much asserted by people?
- How can provenance survive when records are copied, transformed or merged?
- How do we record a source that cannot be disclosed?
- How can a lineage claim itself be verified rather than trusted?
How lineage is lost.
Lineage is usually lost at boundaries: when a dataset is exported to a spreadsheet, when a figure is retyped into a report, when two sources are merged without recording which value came from where. Each step can be innocent, yet together they produce numbers whose origin no one can reconstruct. Archival science calls the related principle respect for provenance: records keep their link to the body that created them and to their original order.
Modern provenance models describe three kinds of thing: entities such as datasets and reports, activities such as a model run or a review, and agents such as people, institutions and software. The W3C PROV family of specifications expresses these relationships in a form machines can read, and the Registry’s lineage design is intended to follow it, as described on provenance and attribution.
Capturing and checking lineage.
- 01
Issuer and authority
Each record names who issued it and under what authority, so a reader knows whose word it is.
- 02
Activity records
Transformations, model runs and reviews are recorded with their method version and date.
- 03
Integrity checks
Cryptographic hashes can show that a file has not changed since it was recorded, a technique from امنیت سایبری و رمزنگاری.
- 04
محدودیتها
Provenance shows where a record came from, not whether its content is right. Lineage is only as complete as the steps that were captured, and self-declared provenance can be false. Restricted sources can be named but not inspected.
How it is studied, and what the methods cannot say.
- 01مهندسی داده، همکنشیپذیری و تولیتSchema-validated ingestion · Persistent identifier reconciliation · Lineage capture in pipelinesApplied here
- 02امنیت سایبری و رمزنگاریTamper-evident record history · Signed exports and releases · Threat modelling of edit pathsApplied here
- 03هویت دیجیتال و نظامهای دیجیتال عمومیIssuer authentication and authority · Contributor disambiguation by the personApplied here
Where this page’s references lead.
نهادها و اسنادی که این صفحه بر پایهٔ آنها خوانده میشود. وضعیت و ویراستها تغییر میکنند؛ هر پیوند به نهاد صادرکننده میرود.
پرسش و پاسخ.
What is the difference between provenance and a source?
What happens to records with incomplete provenance?
Does a digital signature make a record true?
Why do issuers need persistent identifiers?
Is provenance the same as citation?
What happens when a source is corrected?
Can provenance include restricted sources?
شواهد را از همین صفحه ارسال کنید.
گزارشها is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- ایمیلدرگاه GW-GCRIاز همین صفحه ارسال کنیدشواهد، یک اصلاحیه، یک مورد، یک روش، یک داوری، یک ترجمه یا ورودی نمایه. با برچسب این صفحه میرسد تا ویراستار مسئول آن را دریافت کند.
- Zenodoسپردهٔ بازآن را واگذار کنید و به جامعه ارائه دهیدسابقهٔ خود را با شناسهٔ ORCID خود در Zenodo منتشر کنید و سپس آن را در همانجا به جامعهٔ Reports ارسال کنید. گزینشگران آن را داوری میکنند؛ DOI از آنِ شما میماند.
- گزارشهاGCRIهمهٔ راههای مشارکت را ببینیدانواع مشارکت، نحوهٔ بررسی هر یک، اعتباری که دریافت میکنید، مجوز و آنچه هرگز پذیرفته نمیشود.
هرگز داده شخصی، جزئیات حساس زیرساخت یا چیزی را که حق اشتراکش را ندارید نفرستید. هر مشارکت پیش از استفاده داوری میشود؛ ارسال آن حق مؤلفی یا ویرایشی نمیدهد و حمایت مالی هرگز یافتهای را نمیخرد.
یک روش، یک مجموعهداده یا یک پرسش بیاورید.
اطلاعات و درخواستها امروز باز است. هر درخواست یک شمارهٔ پیگیری میگیرد و گام بعدی را مشخص میکند؛ درخواستهای عضویت، پرداختها، تخصیص رایانش و ثبتنامها تنها زمانی باز میشوند که تیم، شرایط و ظرفیت داوری آنها فراهم باشد.
اسناد حقوقی.
نقشهها، دادهها و ارقام این سایت برای زمینه و اطلاعات عمومی نشان داده میشوند. توصیه، پیشبینی یا هشدار نیستند؛ حدود این اطلاعات در سلب مسئولیتها و اعلامیههای داده بیان شده است.
