SHARE Score

About
+ Add Repo
Coming Soon

AI-assisted pledge creation and signal mapping — planned for Q2 2027

SHARE Registry

Signal Mapping Interface

Repositories

ΓùÅ

Zenodo

21

ΓùÅ

Dryad

13

ΓùÅ

Figshare

14

ΓùÅ

+ Add Repository

Recent Activity

🔄 Zenodo pledge updated 2h ago

✅ H3 mapping approved 5h ago

💬 New discussion on S5 1d ago

Conversational Registry Interface

Query mappings, propose changes, and discuss with the community

🤖

Welcome to the SHARE Signal Registry. I can help you:

  • Query current signal mappings for any repository
  • Create a pledge to add a new repository to SHARE
  • Propose changes to existing mappings
  • Track status of pledges (Community-Assessed → Self-Attested → Verified)

Create new pledge

Show Zenodo mappings

What is a pledge?

Today at 9:00 AM

I want to create a pledge for OSF (Open Science Framework)

9:02 AM

U
🤖

Great! I'll help you create a pledge for OSF. A pledge is a JSON document that maps OSF's metadata fields to the 25 universal SHARE signals.

Pledge Lifecycle

1. Community-Assessed

→

2. Self-Attested

→

3. Verified

Only Verified pledges have been independently audited. All current pledges are Community-Assessed.

Let's start. What's the OSF API endpoint for fetching dataset metadata?

9:02 AM

https://api.osf.io/v2/registrations/{id}/

9:04 AM

U
🤖

I've analyzed OSF's API schema. Here's a draft mapping for the Stewardship (S) bucket:

SignalOSF FieldConfidence

S1_geo_spatial

ΓÇö

Not available

S2_temporal

attributes.date_created

High Γ£ô

S3_contributors

relationships.contributors

High Γ£ô

S4_subjects

attributes.subjects

High Γ£ô

S5_ethical

attributes.has_ethics_approval

Medium ΓÜá

ΓÜá S5 needs review: OSF has a boolean field, but SHARE expects a statement. Should we map it as "present" type?

Yes, map as present

Skip S5 for now

Continue to H bucket

9:04 AM

Map as present, then show me the full pledge

9:06 AM

U
🤖

Here's your complete draft pledge for OSF:

{
  "repository": "osf",
  "repository_url": "https://osf.io",
  "vocabulary_version": "1.0",
  "pledge_version": "1.0",
  "pledge_date": "2026-01-24",
  "status": "draft",
  "signals": {
    "S": {
      "S1_geo_spatial": null,
      "S2_temporal_context": {"field": "attributes.date_created", "type": "present"},
      "S3_contributor_roles": {"field": "relationships.contributors", "type": "present"},
      "S4_subject_classification": {"field": "attributes.subjects", "type": "present"},
      "S5_ethical_statement": {"field": "attributes.has_ethics_approval", "type": "present"}
    },
    "H": { ... },
    "A": { ... },
    "E": { ... },
    "R": { ... }
  },
  "scoring": {
    "signals_pledged": 18,
    "max_possible": 100
  }
}

18 of 25

Signals Pledged

100

Max Score

Draft

Status

Edit mappings

Download JSON

9:06 AM

Submit as Pull Request

9:08 AM

U
🤖

Your pledge has been submitted to the central registry.

PR #142: Add OSF pledge

Pending Review

File

pledges/osf.json

Submitted by

@you

Reviewers

@share-governance-panel

Auto-checks

Γ£ô JSON valid ┬╖ Γ£ô Schema valid ┬╖ Γ£ô 10 test samples pass

Next Steps to Verified Status

  1. Review ΓÇö Governance panel reviews your mappings (2-5 days)
  2. Self-Attested — Repository confirms the signal mappings
  3. Attestation ΓÇö OSF team attests via DNS or well-known URL
  4. Verified — Independent audit confirms accuracy, used for production scoring

9:08 AM

Create new pledge

Check my pending PRs

How do I get Verified status?

Compare repository ceilings