NFDI4Energy / NFDI4Energy/SMECS

Add metadata schema selection to the landing page

Open
#315 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13
Forks
1
Avg merge
22h 24m
Merged PRs (30d)
1

Description

Currently, SMECS supports curation workflows for both CodeMeta and ERSmeta schemas, but these functionalities are implemented and accessed separately.

We want to introduce a metadata schema selection step on the landing page, allowing users to choose which schema they want to use before starting the curation process.

The selected schema should determine how the curation page is structured. This should also provide an extensible foundation for adding more metadata schemas in the future.

Desired behavior:

  1. On the landing page, the user can select a metadata schema.
  2. Initially, the available options are:
  • CodeMeta
  • ERSmeta
  • Later (ConnOSS schema)
  1. The selected schema is carried into the curation workflow.
  2. The curation page is structured according to the selected schema (tabs).

This issue can be done in parallel to https://github.com/NFDI4Energy/SMECS/issues/312.

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 at the landing page and trace how the curation workflow reaches the curation page and its tabs, then inspect the existing CodeMeta and ERSmeta implementations. Done means users can select CodeMeta or ERSmeta before curation, the choice is carried through the workflow, and the curation tabs follow that schema while leaving room for additional schemas.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.