DOI representation in cell cards needs to be more understandable and consistent

Open
#187 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by locating the Detail Card, grid-view filter sidebar, and Source Publication widget mentioned in the issue, then compare how each currently formats DOI and publication information. Implement the agreed interim formatting consistently across those views; done means the DOI is recognizable, journal names are omitted where requested, and "et al.," punctuation matches.

Written by the indexing model from the issue text.

Description

DOI is not really a human readable thing. I don't memorize DOIs, convention is (first author, year) or (first author et al., year)

In Detail Cards, the DOI isn't the full doi, which makes it hard to even recognize that it's a DOI. (green box, image 1). it's missing the journal's identifier in the part of the URI (e.g., it's not sciadv.adj9173, it's 10.1126/sciadv.adj9173.

In the filter sidebar of the grid view, Image, it would be best to have the same formatting.

In the Source Publication widget of the Cell Card, It's not clear how this information is retrieved. Do not display the journal name. Also, ensure that formatting for "et al.," is "et al.," not "et al" see purple box, image 2.

In our lab meeting, we discussed 2 fixes (interim and full):
Interim fix:.
change what is displayed on the detail card, and grid view filter side panel to match what is displayed in the "other cells from this source" widget. [see picture 2, orange box)

Image

Full fix: Tom will implement the lookup for DOIs within Interlex. {to be more fully described by him}

Dominant language
JavaScript
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

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.

More from MetaCell/interlex

All issues in MetaCell/interlex

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.