Sample ID from catalogue

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, typescript
Domain
api, frontend

Research direction

The issue names no files, tests, or entry points. Inspect the sample ID input and the existing API boundary first, then determine whether catalogue searching belongs in JavaScript or Python; done requires an agreed implementation direction for searching samples without unnecessary API calls.

Written by the indexing model from the issue text.

Description

enhancement

We can search for samples in the sample id input. But that requires API calls. Should we do that in JS or Py?

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
3d 1h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

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.

More from SciCatProject/scicat_widget

All issues in SciCatProject/scicat_widget

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.