Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat : catalog grid content #96

Closed
MdechampG opened this issue Mar 13, 2023 · 11 comments
Closed

Feat : catalog grid content #96

MdechampG opened this issue Mar 13, 2023 · 11 comments
Assignees
Labels
feature 🤌 new features

Comments

@MdechampG
Copy link
Member

MdechampG commented Mar 13, 2023

Feature: Catalog grid content

As a user of the portal on the catalog
I want to see all the resources of the catalog
So that I can explore the dataverse

Acceptance criteria

Scenario: default display (desktop)

Given that I am a user of the web portal,
When I am on the catalog page (authenticated or unauthenticated)
Then I should see 20 cards of dataverse items displayed in a 4-column grid (see mock up) without any filter
And each card should be labelled according to the type (Data space, Dataset, Service)
And each card contains the title and the topic (for data spaces and datasets) or the category (for services)
And cards are sorted ‘by date of last update’
When I scroll down
Then the resources load 20 by 20 (infinite scroll, load as you go)

Scenario: Internationalization

Given that I am a user of the web portal on the catalog page,
When the selected language is English
Then metadata of the resources (title and category) should be displayed in English

Given that I am a user of the web portal on the home page,
When the selected language is French
Then metadata of the resources (title and category) should be displayed in French if available or English by default

Given that I am a user of the web portal on the home page,
When the selected language is German
Then metadata of the resources (title and category) should be displayed in German if available or English by default

Requirements

The content should be fetched from the ontological database.

Resources

Mockups

Mock up :
image

Environment

Additional informations

None.

@fredericvilcot
Copy link
Contributor

@MdechampG @ChaimaaZaoui
To update the views and implement the "infinite scroll" mechanism, I need two elements:

  • a loader under the cards in the dataverse view to indicate to the user that more cards are loading
  • how do we sort the dataverse? For now we could sort by: type, title or description. Please tell me.

Thx

@ChaimaaZaoui
Copy link

@fredericvilcot

  • I'll work on the loader with lisa asap and give you its UX
  • The order on the dataverse should be following the alphabetical order of titles

@ChaimaaZaoui
Copy link

@ChaimaaZaoui
Copy link

OS : Windows / iOS
Browsers : Firefox / Safari
Scenario: default display (desktop) => Failed

  • each card must contain the title and the topic (for data spaces and datasets) or the category (for services), whereas it shows the title and the description see bug Catalog grid content - Card content #272

  • And cards are sorted ‘by date of last update’ => I don't have access to ontology to verify the order

@ChaimaaZaoui
Copy link

ChaimaaZaoui commented Jun 8, 2023

OS : Windows / iOS
Browsers : Firefox / Safari
Scenario: default display (desktop) => Successful

  • each card must contain the title and the topic (for data spaces and datasets) or the category (for services), whereas it shows the title and the description see bug Catalog grid content - Card content #272

  • And cards are sorted ‘by date of last update’ => I don't have access to ontology to verify the order

@ChaimaaZaoui
Copy link

@ccamel or @amimart can one of you please test if the order in is good. That way I can close the ticket. Thank you.

@MdechampG
Copy link
Member Author

Test on the sort of cards failed ❌ it is sorted by alphabetical order and not by date of last update, implying that it's not the same order according to the language.

image image

@fredericvilcot
Copy link
Contributor

@MdechampG
I will make the changes as requested.
FYI, I implemented this comment: #96 (comment)

@MdechampG
Copy link
Member Author

@fredericvilcot ah I haven't seen it. It's because until we have the search bar, it will be easier to find an element if it is sorted by alphabetical order.
So can you keep it like that and we will discuss it with @ChaimaaZaoui. If necessary we'll do a separate issue.
Thank you

@fredericvilcot
Copy link
Contributor

@MdechampG
Sure, let me know if I have to make modifications after your discussion with @ChaimaaZaoui .

@ChaimaaZaoui
Copy link

All good, we keep the alphabetical order

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🤌 new features
Projects
None yet
Development

No branches or pull requests

3 participants