GCRI · Registry
기록 출처
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.
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.
측정되는 것과 그 정확도.
각 지표에는 단위, 주기, 그 뒤의 출처 종류, 값에 붙을 근거 표시가 있습니다. 값은 표시하지 않습니다. 값은 프로그램이 자체 권한으로 제공합니다.
| 지표 | 단위 | 주기 | 출처 유형 | 라벨 |
|---|---|---|---|---|
| Records with complete issuer, date and method | share of records | 월별 | Schema validation | 관측 |
| Lineage depth to a primary source | number of derivation steps | per record | Provenance graph | 관측 |
| Unresolved source references | 건수 | 매주 | Resolver checks | 관측 |
| Transformations without a recorded agent | 건수 | 월별 | Provenance graph audit | 관측 |
| Records with content hashes or signatures | share of records | 월별 | Integrity check | 관측 |
| Issuers with a persistent identifier | share of issuers | 분기별 | Identifier reconciliation | 관측 |
| Provenance inferred rather than declared | share of provenance statements | 분기별 | Curation review | 추정 |
근거의 출처.
이름이 명시된 공개 데이터셋과 기관 기록으로, 각각 라이선스 등급이 있습니다. 협약에 따른 출처는 그 조건에 따라서만 사용하며 결코 재게시하지 않습니다.
| 출처 | 제공하는 것 | 라이선스 등급 |
|---|---|---|
| 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 |
누가 결정하며 근거는 무엇에 쓰이는지.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| 결정 주체 | 질문 | 이 페이지가 제공하는 근거 |
|---|---|---|
| 데이터 관리자 | 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 |
| 연구 윤리 담당자 | 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 |
이 주제가 생산하는 산출물
- 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.
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 iD로 Zenodo에 직접 기록을 게시한 뒤, 그곳의 Reports 커뮤니티에 제출하십시오. 큐레이터가 검토하며, DOI는 귀하의 것으로 남습니다.
- 보고서GCRI모든 기여 방법 보기기여 유형, 각각의 검토 방식, 받게 되는 크레디트, 라이선스, 그리고 절대 받지 않는 것.
개인정보, 민감한 인프라 세부 정보, 공유할 권리가 없는 자료는 절대 보내지 마십시오. 기여물은 사용 전에 검토됩니다. 기여물을 보낸다고 해서 저작자 지위나 편집 권한이 부여되지 않으며, 후원으로 조사 결과를 얻을 수 없습니다.
방법, 데이터세트 또는 질문을 가져오십시오.
정보와 문의는 오늘부터 열려 있습니다. 문의에는 참조 번호가 부여되고 다음 단계가 안내됩니다. 신청, 결제, 컴퓨팅 할당, 등록은 해당 팀, 약관, 심사 역량이 갖추어졌을 때만 열립니다.
법률 문서.
이 사이트의 지도, 데이터와 그림은 맥락과 일반 정보로 제시됩니다. 조언, 예보 또는 경보가 아니며, 정보의 한계는 면책 고지와 데이터 고지에 나와 있습니다.