Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://github.com/codemeta/codemeta
13 November 2025, 10:56:53 UTC
  • Code
  • Branches (12)
  • Releases (3)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/0.1
    • refs/heads/BibTeX-sssom-mapping
    • refs/heads/agent-context
    • refs/heads/develop
    • refs/heads/force16
    • refs/heads/master
    • refs/heads/patch-travis
    • refs/heads/sssom-methodology
    • refs/tags/0.1-alpha
    • refs/tags/1.0
    • refs/tags/2.0
    • refs/tags/2.0-rc
    • 3.1
    • 3.0
    • 2.1
  • 777a765
  • /
  • README.md
Raw File Download
Take a new snapshot of a software origin

If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.

Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
swh spinner

Processing "take a new snapshot" request ...

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
  • revision
  • snapshot
origin badgecontent badge Iframe embedding
swh:1:cnt:20fe4e776726f099b7a4efcfad3483076b77c2ff
origin badgedirectory badge Iframe embedding
swh:1:dir:777a765fa0bfed9c8df96e49f08c1e35fa508761
origin badgerevision badge
swh:1:rev:a4e10e80913c428af432c2624ed0454ed472f2e9
origin badgesnapshot badge
swh:1:snp:c579cbdc9a58e855921c3616eb869ba8f99efb8f

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
  • directory
  • revision
  • snapshot
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Tip revision: a4e10e80913c428af432c2624ed0454ed472f2e9 authored by Matt Jones on 17 April 2016, 07:23:56 UTC
Add use case slide.
Tip revision: a4e10e8
README.md
CodeMeta
========
[![Join the chat at https://gitter.im/codemeta/codemeta](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/codemeta/codemeta?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

[CodeMeta](https://codemeta.github.io) is creating minimal metadata schemas for science software and code, in JSON and XML.

This is an extension of the work done by [@arfon](http://github.com/arfon/), [@hubgit](https://github.com/hubgit/), [@kaythaney](https://github.com/kaythaney/) and others on [Code as a Research Object](https://github.com/mozillascience/code-research-object) / [fidgit](https://github.com/mozillascience/fidgit). **Code as a research object** is a [Mozilla Science Lab](http://mozillascience.org) ([@MozillaScience](https://github.com/mozillascience/)) project working with community members to explore how we can better integrate code and scientific software into the scholarly workflow. Out of this came **fidgit** - a proof of concept integration between Github and figshare, providing a [Digital Object Identifier](http://en.wikipedia.org/wiki/Digital_object_identifier) (DOI) for the code which allows for persistent reference linking.

With codemeta, we want to formalize the schema used to map between the different services (Github, figshare, Zenodo) to help others plug into existing systems. Having a standard software metadata interoperability schema will allow other data archivers and libraries join in. This will help keep science on the web shareable and interoperable!

JSON-LD schema: https://github.com/codemeta/codemeta/blob/master/codemeta.jsonld

Example instance: https://github.com/codemeta/codemeta/blob/master/example-codemeta.json

Comparison of current APIs in this space: https://github.com/codemeta/codemeta/blob/master/crosswalk.csv


How you can help
================

We need help formalizing a schema and creating mappings between existing software metadata schemas and the proposed schema.

* Send us a pull request if you have any updates to our [schema](https://github.com/codemeta/codemeta/blob/master/codemeta.jsonld) or [mappings](https://github.com/codemeta/codemeta/blob/master/codemeta-crosswalk.md)!
* Take a look at the [issue tracker](https://github.com/codemeta/codemeta/issues)
* Join the discussion!
    * [(JSON-LD) Metadata for software discovery](https://github.com/mozillascience/code-research-object/issues/15)
    * [How should software be cited?](https://github.com/mozillascience/code-research-object/issues/12)
    * [What information is needed to reuse code?](https://github.com/mozillascience/code-research-object/issues/2)


Organizers
==========

* Matt Jones
* Arfon Smith
* Abby Cabunoc Mayes
* Carl Boettiger

Links
=====

* **Code as a Research Object** blog posts:
    * [Code as a research object: updates, prototypes, next steps](http://mozillascience.org/code-as-a-research-object-updates-prototypes-next-steps/)
    * [What else is needed for code reuse](http://mozillascience.org/what-else-is-needed-for-code-reuse/)
    * [JSON-LD for software discovery, reuse and credit](http://www.arfon.org/json-ld-for-software-discovery-reuse-and-credit)

* [JSON-LD.org](http://json-ld.org/)
* [Schema.org](http://schema.org/)

back to top

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API