You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/_index.md
+18-15Lines changed: 18 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,7 @@ layout: landing
5
5
6
6
## Introducing CodeMeta
7
7
8
-
Software development creates changes, and scientific research requires
9
-
reproducibility. Since software is routinely used in research projects,
10
-
this can cause problems.
8
+
CodeMeta provides a shared, minimal metadata vocabulary for software, designed to support research, discovery, citation, and interoperability across platforms. It is currently being used in major initiatives such as FAIRCORE4EOSC to make research software FAIR (Findable, Accessible, Interoperable, Reusable).
11
9
12
10
_**CodeMeta acts as a vital bridge between these disciplines.**_
13
11
@@ -29,21 +27,26 @@ recommendations:
29
27
30
28
{{< rsmd >}}
31
29
32
-
## Use Cases
30
+
## Why CodeMeta? — Key Use Cases
33
31
34
-
Credit
35
-
: CodeMeta's _citation_ metadata is useful for ensuring that authors get
36
-
credit for their software, when it is used for published research.
32
+
Enabling Reliable Software Citation
33
+
: Consistent software citation remains a challenge in scholarly communication. CodeMeta supports structured metadata that enables software to be cited, indexed, and credited correctly. This aspect is highlighted by FAIRCORE4EOSC’s integration of CodeMeta into software archival and citation workflows.
37
34
38
-
Reproducibility
39
-
: Tracking the software libraries and applications used in research, using
40
-
CodeMeta's _versions_ and _dependencies_ metadata, ensures that important
41
-
findings can be reviewed and verified with greater accuracy.
35
+
Standardizing Software Metadata
36
+
: Software metadata is often scattered across incompatible formats and tools. CodeMeta defines a common, machine-readable vocabulary (JSON-LD) that enables software metadata to be shared consistently across repositories, registries, and platforms — making it possible for large infrastructures like EOSC to standardize metadata at scale.
42
37
43
-
Discovery
44
-
: Finding software is easier with CodeMeta's _keywords_ and _descriptions_
45
-
metadata. These terms allow everyone to discover relevant software, and use
46
-
or contribute to it.
38
+
Improving Discovery and Reuse
39
+
: By using a common metadata schema, software becomes easier to discover both by humans and machines. CodeMeta metadata in APIs and connectors improve interoperability, discovery and sharing of research software across repositories and services.
40
+
41
+
Supporting Interoperability Between Systems
42
+
: CodeMeta acts as a “metadata exchange layer” linking diverse systems. This enables metadata to flow between repositories, publishers and aggregators, improving exchange and integration without bespoke converters.
43
+
44
+
Enhancing Transparency and Reproducibility
45
+
: Clear software metadata helps others understand what software does, how it was created, and how it can be used — which is critical for reproducible science. Users can now leverage standardized metadata for archiving, describing, and citing software artifacts in a FAIR-compliant ecosystems.
46
+
47
+
##### **Learn more**: For a full list of CodeMeta use cases
48
+
* See: Full list of CodeMeta [use cases](/use-cases/)
49
+
* See also:FAIRCORE4EOSC – [Core Components for a FAIR EOSC](https://faircore4eosc.eu/)
0 commit comments