-
Notifications
You must be signed in to change notification settings - Fork 165
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
Consult attributes whilst doing a search #572
Comments
). Co-authored-by: Matthieu DUFON [email protected]
). Co-authored-by: Matthieu DUFON [email protected]
Co-authered by : Maxime MACREZ <[email protected]> Co-authered by : Thibault Pavee <supertibodor1gmail.com>
Point d'avancement du 28/04
Autre : Reformuler le titre. |
Co-authored-by: Callista Spiteri [email protected] Quelle partie du code sera impactée (classes, méthodes) ? Utilisez les React DevTools (extensions de Chrome ou Firefox) pour faire le lien entre la structure de la page et celle du code.
Y aura-t-il des difficultés d'un point de vue algorithmique ? Avez-vous des pistes pour les résoudre ? Les données dont vous avez besoin sont-elles déjà chargées par la page ? Si oui, quelle est la structure des données et comment allez-vous récupérer précisément celles qui vous intéressent ? Si non, quelle sera la requête la plus efficace et comment allez-vous récupérer dans la structure de données précisément celles qui vous intéressent ? Existe-t-il des bibliothèques qui pourraient simplifier l'implémentation ? Quelles sont celles que vous choisirez et pourquoi ? Doit-on intégrer des services extérieurs (ex : cartographie) ? De quelles fonctionnalités en particulier aura-t-on besoin ? Est-ce que le service choisi les propose ou doit-on passer chez un concurrent ? Comment s'utilisent ces fonctionnalités ? avec quels paramètres ? |
Co-authored by: Maxime MACREZ <[email protected]> Co-authored by: Thibault Pavee <supertibodor1gmail.com>
). Co-authored-by: Matthieu DUFON [email protected]
). Co-authored-by: Matthieu DUFON [email protected]
Co-authered by : Maxime MACREZ <[email protected]> Co-authered by : Thibault Pavee <supertibodor1gmail.com>
Co-authored by: Maxime MACREZ <[email protected]> Co-authored by: Thibault Pavee <supertibodor1gmail.com>
Co-authored-by: Callista Spiteri <[email protected]> Co-authored-by: Maxime Macrez <[email protected]>
). Co-authored-by: Matthieu Dufon <[email protected]>
Co-authored-by: Maxime MACREZ <[email protected]> Co-authored-by: Thibault Pavee <[email protected]> Co-authored-by: Callista Spiteri <[email protected]> Co-authored-by: Matthieu Dufon <[email protected]>
Co-authored-by: Callista Spiteri <[email protected]> Co-authored-by: Maxime Macrez <[email protected]>
Merged as c60eb1f. Well done 🎉 |
Don't forget to record a screencast of this feature on your application domain, and post it in this thread. |
2022-06-09.14-47-08_Trim.mp4Screencast explaining the feature. Recorded by Matthieu Dufon and Callista Spiteri |
Description
The attributes of the items should be accessible to the users. They should be able to make a research on the value of an attribute.
What is the valuable outcome that cannot be achieved with current features?
The valuable outcome is that the user can search data by attribute values and compare them with other data (other attribute values or topics)
For which stakeholder (people, role, project, domain) is it important?
It is important for people who need to compare data, in our case, researchers.
Which user action should be enabled (or restricted)? For who?
It should be accessible to all users, logged in or not.
Additional details (solutions you think about, or workarounds you tried)
Deliverables status
Phase 1
Phase 2
Phase 3
The text was updated successfully, but these errors were encountered: