Open kmartinez834 opened 1 week ago
We discussed during the General meeting today. We want to add a column to the Glycan details expression section with an icon that enables user to select publication with abundance info.
Need to decide if this will be implemented by front end or back end.
@sujeetvkulkarni Is this information client or server side paginated?
@ReneRanzinger Both expression table entries (tissue and cell line) are server side paginated.
In that case the duplication needs to happen server side. To be able to make the icon we will have to add new properties in the JSON:
@ReneRanzinger @rykahsay A property with paper list, having evidence data will be good. As we can display list of paper ids (with links to publication details page) in the Abundance column. Array can be empty if there is no abundance data.
abundance: [
{
"id": "33167210",
"database": "PubMed",
"url": "https://glygen.org/publication/PubMed/33167210"
},
{
"id": "10.1016/j.talanta.2020.121495",
"database": "DOI",
"url": "https://glygen.org/publication/DOI/10.1016/j.talanta.2020.121495"
}
]
Am I missing something? Why a simple addition of "abundance" column to the table in the frontend cannot address this? Why do we need to change the data model?
All of the P07288-1 Asn69 rows appear to be identical: https://www.glygen.org/glycan/G59655SA#Expression
However, the API includes abundance information, so these are separate objects. Add abundance to glycan details page or remove redundant rows from expression section?