Skip to content

Deposit: putting-a-fault-in-a-mesh - #55

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
deposit/putting-a-fault-in-a-mesh-35503029305-1
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
deposit/putting-a-fault-in-a-mesh-35503029305-1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

putting-a-fault-in-a-mesh is published and has no archival record. A figshare draft has been created and 10.6084/m9.figshare.33944806 reserved for it. Neither is public yet.

Merging this publishes the record at that DOI. The deposit workflow rebuilds the PDF so the DOI is on its title page, uploads the PDF and the archive package, and publishes. The identifiers are already in this pull request, so nothing has to be recorded afterwards.

A published DOI cannot be withdrawn, only superseded — and because figshare versions, a mistake is a new version rather than a lost identifier.

Not ready? Close this. The reserved draft is then unused and shows up in the weekly outstanding issue, where pixi run deposit -- --slug putting-a-fault-in-a-mesh --live --delete-draft clears it.

Underworld development team with AI support from Claude Code

A draft and a DOI are reserved for this note; neither is public. The
identifiers are in its metadata.yml, so merging this approves the
deposit and records it in one step.

Opened automatically because the note is on main without a record.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants