This site uses cookies. By continuing to browse the site, you agree to our use of cookies. Find out more about cookies.
Skip to main content
Metadecidim's official logo
  • English Triar la llengua Elegir el idioma Choose language
    • Català
    • Castellano
Sign Up Sign In
  • Home
  • Processes
  • Assemblies
  • Initiatives
  • Consultations
  • Conferences
  • Help

Propose new functionalities for Decidim software

#DecidimRoadmap Designing Decidim together

Phase 1 of 1
Open 2019-01-01 - 2030-12-31
Process phases Submit a proposal
  • The process
  • Debates
  • Propose new features
  • News
chevron-left Back to list

Order and visualization of meetings

Avatar: Platoniq Platoniq verified-badge
20/04/2021 09:40  

Is your feature request related to a problem? Please describe.
When visiting a meetings component it is not clear whether an event has already taken place or is in the future. Furthermore, the order of events is always the same, sorted by start_date from in reverse order (this change has been done recently), meaning the further in time an event happens, the sooner appears in the list.

Describe the solution you'd like
We propose 3 improvements to the meetings components:

Divide the default sorting of proposals into 2 categories:

  1. if it's in the past, order them by start_date in ascendant mode (user sees first what happened more recently).
  2. If it's in the future, order them in descendent mode (user sees first the next coming event first).

This casuistic raises the question on what happens when the user want's to see all events, past and future. In this case I'd maintain the described order and put the future events in top ordered ASC and then the past ones ordered DESC (technically, this would mean to merge to queries to sort them differently).

In addition, we would like to also improve the visualization these two types of events (past and future) by adding the success and muted classes to the card--meeting so the user has quick visual clue on what's more relevant.

This would look like this:

Describe alternatives you've considered
Instead of using colors to differenciate the past and future meetings, use a separator element between them (for instance a bar or an hr html element).

Additional context

The third improvement is to add images to the meeting card (as already happens in proposals). This just uses the current system of attachments and, if one of them is a photo, uses it as a card-image:

Does this issue could impact on users private data?

NO

Funded by

Yes, Som Energia & Platoniq

  • Filter results for category: Meetings Meetings

List of Endorsements

Avatar: Fundació Francesc Ferrer i Guàrdia Fundació Francesc Ferrer i Guàrdia verified-badge
Avatar: Ajuntament de Barcelona Ajuntament de Barcelona verified-badge
Avatar: Pau Parals Pau Parals verified-badge
Avatar: Marta Anducas Marta Anducas verified-badge
Avatar: Vera Rojman Vera Rojman
Avatar: Ivan Vergés Ivan Vergés verified-badge
Avatar: Mònica Gifreu Mònica Gifreu
Avatar: Arnau Arnau
Avatar: JosanFFiG JosanFFiG
Avatar: Eva Gómez Eva Gómez
Avatar: Ariadna Vila Ariadna Vila
and 8 more people (see more) (see less)
Endorsements count11
Order and visualization of meetings Comments 6

Reference: MDC-PROP-2021-04-16327
Version number 2 (of 2) see other versions
Check fingerprint

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: 869293af5c8cb3ac69631a0a0446848fb5af1199bf9d3e6bf15c38d247c035c0

Source: {"body":{"en":"<p><strong>Is your feature request related to a problem? Please describe.</strong><br>When visiting a meetings component it is not clear whether an event has already taken place or is in the future. Furthermore, the order of events is always the same, sorted by start_date from in reverse order (this change has been done recently), meaning the further in time an event happens, the sooner appears in the list.</p><p><strong>Describe the solution you'd like</strong><br>We propose 3 improvements to the meetings components:</p><p>Divide the default sorting of proposals into 2 categories:</p><ol><li>if it's in the past, order them by start_date in ascendant mode (user sees first what happened more recently).</li><li>If it's in the future, order them in descendent mode (user sees first the next coming event first).</li></ol><p>This casuistic raises the question on what happens when the user want's to see all events, past and future. In this case I'd maintain the described order and put the future events in top ordered ASC and then the past ones ordered DESC (technically, this would mean to merge to queries to sort them differently).</p><p>In addition, we would like to also improve the visualization these two types of events (past and future) by adding the <em>success</em> and <em>muted</em> classes to the <em>card--meeting</em> so the user has quick visual clue on what's more relevant.</p><p>This would look like this:</p><p><img src=\"https://user-images.githubusercontent.com/1401520/115354661-2adc4600-a1ba-11eb-8b29-af37874b706f.png\"></p><p><strong>Describe alternatives you've considered</strong><br>Instead of using colors to differenciate the past and future meetings, use a separator element between them (for instance a bar or an hr html element).</p><p><strong>Additional context</strong></p><p>The third improvement is to add images to the meeting card (as already happens in proposals). This just uses the current system of attachments and, if one of them is a photo, uses it as a card-image:</p><p><img src=\"https://user-images.githubusercontent.com/8806781/110646272-081c4200-81b7-11eb-9a19-ae3ed862941b.png\"></p><p><strong>Does this issue could impact on users private data?</strong></p><p>NO</p><p><strong>Funded by</strong><br></p><p>Yes, Som Energia &amp; Platoniq</p>"},"title":{"en":"Order and visualization of meetings"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Share:

link-intact Share link

Share link:

Please paste this code in your page:

<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16327/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16327/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Related images

Screenshot_2021-04-20 Sessions participatives - Clavegueram - decidim barcelona(2).png

Report inappropriate content

Is this content inappropriate?

Reason

Comment details

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed
You are seeing a single comment

View all comments

Conversation with Arnau
Avatar: Arnau Arnau
20/04/2021 23:17
  • Get link Get link

There is another solution which is to come back to radio buttons and show past OR future events but never together, This facilitates the navigation and the comprehension of the event list.

Avatar: Ivan Vergés Ivan Vergés verified-badge
21/04/2021 07:44
  • Get link Get link

True, but that would break the overall design consistency with other component visualization? We might eve just get rid of the "show all" button to achieve the same thing.
Personally I don't mind having a "all" view, as long as it is not the default.

Loading comments ...

  • Terms and conditions of use
  • About the community
  • Download Open Data files
  • Metadecidim at Twitter Twitter
  • Metadecidim at Instagram Instagram
  • Metadecidim at YouTube YouTube
  • Metadecidim at GitHub GitHub
Creative Commons License Website made with free software.
Decidim Logo

Confirm

OK Cancel

Please sign in

decidim Sign in with Decidim
Or

Sign up

Forgot your password?