codemetagenerator

This project is a CodeMeta project description generator written in Go.

Installation

Manually

To install this project, you need to have Go installed on your machine. Once you have Go installed, you can clone this repository and build the project.

bash git clone https://github.com/cacoco/codemetagenerator.git cd codemetagenerator go build

Then install via go install

Via Homebrew

bash brew tap cacoco/tap brew install codemetagenerator

Usage

To run this project, you can use the following commands:

bash codemetagenerator --help

Commands

bash Available Commands: add Adds resources [authors, contributors, keywords] to the in-progress codemeta.json file clean Clean the $HOME/.codemetagenerator directory delete Delete an arbitrary key and its value from the in-progress codemeta.json file generate Generate the resultant 'codemeta.json' file to the optional output file or to the console help Help about any command licenses List or refresh cached SPDX (https://spdx.org/licenses/) license IDs new Start a new codemeta.json file for editing. When complete, run "codemetagenerator generate" to generate the resultant 'codemeta.json' file set Set the value of an arbitrary key in the in-progress codemeta.json file validate Validates a codemeta.json file

New

'New' will walk you through an interactive session and will store an "in-progress" codemeta.json file. To start a new codemeta.json file:

bash codemetagenerator new [-i | --input]

The expectation is that you will continue to add more metadata, e.g., author, contributor, or keyword.

Optionally, the -i | --input flag can be passed with a path to an input file to load as a "new" starting point. This allows for editing and updating an existing file that you can then 'generate' into the original location.

Add

'Add' helps with the addition of 3 specific fields: author, contributor, or keyword. The command provides a wizard for adding these values.

For example to add an author:

bash codemetagenerator add author

will walk you through an interactive session to create a Person or Organization author. This command can be run multiple times to add more authors. This can also be done to add one or more contributors:

bash codemetagenerator add contributor

Again, this command can be run multiple times to add more contributors.

To add one or more keywords:

bash codemetagenerator add keyword 'Java' 'JVM' 'etc'

The keyword command accepts multiple terms but can also be run multiple times to add more keywords.

Delete

'Delete' removes properties or values. This allows for removing any property or value in the codemeta.json file for a given property key specified via the Path Syntax.

bash codemetagenerator delete 'version'

Set

'Set' edits existing or inserts new properties or values in the codemeta.json file. Property keys must be specified via the Path Syntax.

bash codemetagenerator set 'relatedLink' 'https://thisisrelated.org'

Note that values can be JSON objects or arrays. E.g.,

bash codemetagenerator set 'author.-1' '{"@type":"Person", "@id":"https://orcid.org/0000-0000-1642-999Y", "givenName":"Alice", "familyName":"Smith", "email":"asmith@person.org"}'

In the Path Syntax, -1 denotes appending to an array. Thus this will append the given JSON object to the author JSON array. Note that if the given input cannot be parsed into a JSON object or array it will be treated as a string.

Similarly, to set a JSON array value:

bash codemetagenerator set 'processorRequirements' '["IA64", "IA32"]'

Will set the given JSON array as the value for the property key. Then you could append a value to the array:

bash codemetagenerator set 'processorRequirements.-1' 'x86'

Generate

'Generate' produces a resultant codemeta.json file. Optionally, the -o | --output flag can be passed which allows for specifying an output file. If this flag is not provided, the output is generated to the console.

bash codemetagenerator generate [-o | --output]

Validate

'Validate' will determine if a file is a valid CodeMeta-3.0: https://w3id.org/codemeta/v3.0 codemeta.json file based on the https://schema.org defintions and CodeMeta terms.

bash codemetagenerator validate [-i | --input]

Licenses

'Licenses' will display the list of SPDX licenses downloaded from https://spdx.org/licenses/. The list is cached and can be refreshed by passing the refresh argument.

bash codemetagenerator licenses [refresh]

Clean

'Clean' deletes the codemetagenerator tool working directory (default location is $HOME/.codemetagenerator).

bash codemetagenerator clean

Path Syntax

The path syntax for property keys follows the Syntax from the excellent tidwall/sjson project.

CodeMeta

CodeMeta is a JSON-LD file format used to describe software projects.

CodeMeta Metadata Usage

A CodeMeta instance file describes the metadata of a software object using JSON-LD notation. An instance file is typically located at the root of your repository and can contain any of the properties described on the CodeMeta terms page. The instance file is generally named, codemeta.json.

JSON-LD uses a context file to associate JSON names with IRIs (Internationalized Resource Identifier). The JSON names then serve as abbreviated, local names for the IRIs that are universally unique identifiers for concepts from widely used schemas such as schema.org.

The context file codemeta.jsonld contains the complete set of JSON properties adopted by the CodeMeta project.

Example

A full example can be seen in the ropensci/codemeter GitHub project page: https://github.com/ropensci/codemetar/blob/main/codemeta.json.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate.

License

Apache License 2.0

Copyright 2024 Christopher Coco

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.