inab / inab/github-metadata-api

[Question] Process for converting JSON response from `metadata/user` endpoint to JSON-LD in Bioschema format for FAIRsoft evaluator

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Question:
What is the process used for converting the JSON output from the metadata/user endpoint in the Metadata Extractor into a JSON-LD file in Bioschema format that can be used as input in the FAIRsoft evaluator?

Description and Context:
I am investigating programmatically using the FAIRsoft evaluator and would like to understand the specific steps or logic used to transform JSON output into a compliant JSON-LD file that adheres to the Bioschema format. Understanding this process will help ensure my integration of metadata follows best practices and is aligned with the tool’s intended usage.

Attempts:
I have reviewed this repository and also explored the Node-API repository on GitLab for any relevant endpoints or code that handles this conversion but have not yet found a detailed explanation or working solution.

Additional Context:
Any specific code references, guidelines, or examples of converting the JSON output from the metadata/user endpoint to JSON-LD and then inputting this in the FAIRsoft evaluator would be very helpful.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the metadata/user endpoint in this repository and reviewing the linked Node-API repository for any conversion or export logic. Compare the endpoint’s JSON output with the Bioschema JSON-LD expectations and the FAIRsoft evaluator’s accepted input. Done means documenting the conversion steps with relevant code references or an example.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
api, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.