Skip to content

GCRI · ثبت‌خانه

مهندسی داده در Registry

Data engineering, interoperability and stewardship are the working base of a registry: the schemas that define a record, the pipelines that ingest and transform it, the identifiers and crosswalks that link it to other سامانه‌ها, and the stewardship that keeps it accurate over time. Every provenance, correction and rights commitment on this platform depends on them.

ثبت پرس‌وجو Back to STEM foundation of Registry
01ثبت‌خانه

Data engineering at Registry on the record.

Method recordSTEM method
  1. روشمهندسی داده، هم‌کنشی‌پذیری و تولیت
  3. Applied inثبت
  4. داده5 inputs
  6. Canonical pageSTEM Commons
02Application

What data engineering, interoperability and stewardship does here.

Data engineering, interoperability and stewardship cover the pipelines, standards and governance that make data usable and trustworthy. They determine whether information from different sectors can be combined for joint ارزیابی ریسک. In governance and institutions and research and evidence, sound data engineering allows hazard, exposure and financial data to be linked consistently. It supports transparent and repeatable analysis of interconnected risk. The canonical description is on STEM Commons.

Schema-validated ingestion

Incoming records are validated against a versioned schema before they enter the registry. Records that fail are quarantined with the reasons, not partially loaded, so a malformed field never reaches a public view.

Persistent identifier reconciliation

Free-text names of people, organisations and works are matched to ORCID, ROR and DOI records. The match method and confidence are stored with each link, and uncertain matches are routed to a steward.

Lineage capture in pipelines

Each transformation records its inputs, code version, responsible agent and time as PROV statements, so any published field can be traced back to the source rows that produced it.

03روش‌ها و شواهد

How Data engineering at Registry is modelled, measured and tested.

مدل، مفروضات، داده‌ها و عدم قطعیت آن، به شکلی که دانشمند یا مهندس بررسی می‌کند. ساختارها از روش‌های منتشرشده پیروی می‌کنند. مقادیر ترسیم‌شده تبیینی‌اند، نه یافته.

مجموعه‌داده‌ها و خاستگاه

The data classes behind Data engineering at Registry and what is recorded about each before it is used.

طبقهٔ دادهخاستگاه ثبت شدوضوح اعلام‌شدهپروانه بررسی شد
تصاویر ماهواره‌ای، نوری و راداریحسگر، سطح پردازش، تاریخ برداشتاندازهٔ پیکسل و بازدید مجددبه‌ازای هر صحنه
بازتحلیل و خروجی مدل اقلیمیمدل، آزمایش، عضو، نسخهشبکه و گام زمانیبه‌ازای هر انتشار
حسگرها و سنجه‌های درجاایستگاه، ابزار، سابقهٔ واسنجینقطه و نرخ نمونه‌برداریبه‌ازای هر شبکه
مواجهه جمعیت و داراییروش، سال تولید، منابع ورودیاندازهٔ سلول و یکابه‌ازای هر انتشار
مرزها و جغرافیای مرجعتولیدکننده، ویراست، تاریخمقیاسبه‌ازای هر ویراست
تبارنامه
سابقهٔ W3C PROV از منبع تا شکل
اصول
FAIR: یافتنی، دسترس‌پذیر، هم‌کنش‌پذیر، بازاستفاده‌پذیر
شکاف‌ها
به‌صورت ناموجود نشان داده می‌شود، هرگز بی‌صدا پر نمی‌شود
ردهٔ داده‌ها و میدان‌های خاستگاهِ ثبت‌شده برای هر یک؛ یک مجموعه‌داده تنها زمانی با نام فهرست می‌شود که پروانهٔ آن استفاده را بپذیرد.
اصول راهنمای FAIR · GO FAIR و FORCE11W3C PROV · کنسرسیوم وب جهانیGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
04داده

What the method consumes.

Datasets and records used by data engineering, interoperability and stewardship on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

دادهنقشبرچسب
Crossref and DataCite metadataReference metadata for registered works and outputsگزارش‌شده
ORCID recordsContributor identity and linked worksDECLARED
ROR registryOrganisation identifiers, name variants and relationshipsگزارش‌شده
Partner programme recordsIngested programme and participation recordsگزارش‌شده
Pipeline run logsLineage and transformation historyمشاهده‌شده
05فرایند

نحوهٔ اجرای فرایند.

Process explorer · Process

Data engineering at Registry: Build, sign and accept

10 steps4 مرحله2 دروازه

فرایند

Data engineering at Registry: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.

  1. 01 Request and sources

    1. 01Admitted mission becomes a cycle projectسابقه · جهان to FoundryAn admitted mission becomes a cycle project with a decision case.
    2. 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.

  2. 02 Build and verify

    1. 03Source snapshotسابقه · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
    2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
    3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
    4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.

  3. 03 Sign and admit

    1. 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
    2. 08Package admissionگام · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.

  4. 04 Accept

    1. 09گزارش ساخت هستهسابقه · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
    2. 10⁨G3⁩ · ساخت برای تمرین پذیرفته شددروازه · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.

سال برنامه · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.

06اعتبارسنجی

How results are checked.

Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source سامانه‌ها confirms completeness.

بررسیHow it is done
Schema validationEvery record is validated against the published schema version; failures are counted and reported, never dropped silently
Reconciliation against sourceRecord counts and checksums are compared with the source system after every load
Lineage auditA sample of published fields is traced back through the provenance graph to its source rows
Round-trip testRecords are exported, re-imported and compared field by field to expose lossy mappings

Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.

07Connections

Topics that rely on this method.

08تولیت

Who maintains the method.

داده و محاسبات stewards data engineering, interoperability and stewardship for the Consortium and reviews how it is applied across platforms.

Canonical page: Data engineering, interoperability and stewardship

09متصل

جایی که این صفحه در سراسر کنسرسیوم به آن می‌رسد.

10پرسش‌ها

پرسش و پاسخ.

What are the limits of data engineering, interoperability and stewardship in this field?
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
How are results checked?
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method’s use, not a run; no result is reported here.
Where else is this method applied?
رصدخانهٔ canonical method page lists every platform that applies it.
گزارش‌هامشارکت

شواهد را از همین صفحه ارسال کنید.

گزارش‌ها 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.

GCRIثبتروش‌ها و فنی

هرگز داده شخصی، جزئیات حساس زیرساخت یا چیزی را که حق اشتراکش را ندارید نفرستید. هر مشارکت پیش از استفاده داوری می‌شود؛ ارسال آن حق مؤلفی یا ویرایشی نمی‌دهد و حمایت مالی هرگز یافته‌ای را نمی‌خرد.

ثبت

یک روش، یک مجموعه‌داده یا یک پرسش بیاورید.

اطلاعات و درخواست‌ها امروز باز است. هر درخواست یک شمارهٔ پیگیری می‌گیرد و گام بعدی را مشخص می‌کند؛ درخواست‌های عضویت، پرداخت‌ها، تخصیص رایانش و ثبت‌نام‌ها تنها زمانی باز می‌شوند که تیم، شرایط و ظرفیت داوری آن‌ها فراهم باشد.

پیشنهاد یک روش دیدن همهٔ مسیرهای تماس
حقوقی

نقشه‌ها، داده‌ها و ارقام این سایت برای زمینه و اطلاعات عمومی نشان داده می‌شوند. توصیه، پیش‌بینی یا هشدار نیستند؛ حدود این اطلاعات در سلب مسئولیت‌ها و اعلامیه‌های داده بیان شده است.