Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que acceptes la nostra política de cookies. Per a més informació consulta aquí.
Vés al contingut principal
Logo oficial de Metadecidim
  • Català Triar la llengua Elegir el idioma Choose language
    • Castellano
    • English
Registra't Entra
  • Inici
  • Processos
  • Assemblees
  • Iniciatives
  • Consultes
  • Jornades
  • Ajuda

Proposa noves funcionalitats

#DecidimRoadmap Dissenyant el Decidim entre totes

Fase 1 de 1
Obert 01-01-2019 - 31-12-2030
Veure les fases Envia una proposta
  • El procés
  • Debats
  • Proposa noves funcionalitats
  • Novetats
chevron-left Torna al llistat

Complete the Api

Avatar: Ivan Vergés Ivan Vergés verified-badge
29/10/2018 12:43  
Finalitzada

Currently the GraphQL Api in decidim lacks of many desired features.

1. Lots of fields (publicly available in the web) are not available if asked via API. For example, description field for a participatory process.
2. Components needs more specific-type definitions (i.e: you cannot extract pages component content from a participatory space).
3. Individual participatory spaces and components should be searchable via slug as well (when applicable).
4. Listing participatory processes and attributes should be searchable via many attributes: find by scope, find by hashtag, etc.
5. Listing elements should be ordered in a consistent way. Ideally this order should be specified by the query.

I intent (as Platoniq organization) to continue improve the API. I'll try to stick the the contribution rules and, of course, let me know anything that you want me to improve in order to accept this and subsequents pull-requests.

  • Resultats al filtrar per la categoria: API API

El desenvolupament d'aquesta proposta ha finalitzat

  • Has been reviewed by Decidim Product and complies with the Social Contract
  • It is funded by Generalitat de Catalunya
  • Developed by Platoniq
  • Available in release 0.21

Llistat d'adhesions

Avatar: olivier olivier
Avatar: Ivan Vergés Ivan Vergés verified-badge
Avatar: Pablo Aragón Pablo Aragón verified-badge
Avatar: Robert Garrigós Robert Garrigós
Avatar: Alex Garcia Alex Garcia
Avatar: Javier Carrillo Javier Carrillo verified-badge
Avatar: Oliver Valls Oliver Valls
Avatar: Xabier Xabier verified-badge
Avatar: Virgile Deville Virgile Deville
Avatar: Daniel Daniel verified-badge
Avatar: Antti Hukkanen Antti Hukkanen
Avatar: agustibr ☂️ agustibr ☂️ verified-badge
Avatar: Pau Parals Pau Parals verified-badge
Avatar: Alain Buchotte Alain Buchotte
Avatar: Leo Leo
Avatar: Kris De Winter Kris De Winter
Avatar: Arnau Arnau
Avatar: Pauline Bessoles Pauline Bessoles verified-badge
Avatar: Armand Armand
Avatar: Aram L. Roca Aram L. Roca
Avatar: mbonnin mbonnin
Avatar: Andrés Andrés verified-badge
Avatar: Hadrien Froger Hadrien Froger verified-badge
Avatar: Alexander Rusa Alexander Rusa
i 21 persones més (veure més) (veure menys)
Número d'adhesions24
Complete the Api Comentaris 7

Referència: MDC-PROP-2018-10-13308
Versió 3 (de 3) veure altres versions
Verifica l'empremta digital

Empremta digital

El text següent és una representació abreviada i hashejada d'aquest contingut. És útil per garantir que el contingut no hagi estat alterat, ja que una única modificació provocaria un valor totalment diferent.

Valor: babf84119150fa2e2174c9e5d610208befdce3cd17768cc496177afe873dcadb

Origen: {"body":{"en":"Currently the GraphQL Api in decidim lacks of many desired features.\r\n\r\n1. Lots of fields (publicly available in the web) are not available if asked via API. For example, description field for a participatory process.\r\n2. Components needs more specific-type definitions (i.e: you cannot extract pages component content from a participatory space).\r\n3. Individual participatory spaces and components should be searchable via slug as well (when applicable).\r\n4. Listing participatory processes and attributes should be searchable via many attributes: find by scope, find by hashtag, etc.\r\n5. Listing elements should be ordered in a consistent way. Ideally this order should be specified by the query.\r\n\r\nI intent (as Platoniq organization) to continue improve the API. I'll try to stick the the contribution rules and, of course, let me know anything that you want me to improve in order to accept this and subsequents pull-requests."},"title":{"en":"Complete the Api"}}

Aquesta empremta digital es calcula mitjançant un algoritme de hash SHA256. Per reproduir-lo tu mateix, pots utilitzar una Calculadora MD5 en línia i copiar-hi les dades d'origen.

Compartir:

link-intact Compartir l'enllaç

Compartir l'enllaç:

Si us plau, enganxa aquest codi a la teva pàgina:

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

Reportar contingut inapropiat

Aquest contingut no és apropiat?

Motiu

7 comentaris

Ordenar per:
  • Més antic
    • Més ben valorats
    • Recent
    • Més antic
    • Més discutit
Avatar: Xabier Xabier verified-badge
11/02/2019 19:07
  • Obtenir enllaç Obtenir enllaç
A favor  

This is VERY VERY MUCH needed @microstudi thanks so much!

Conversa amb Virgile Deville
Avatar: Virgile Deville Virgile Deville
14/05/2019 09:03
  • Obtenir enllaç Obtenir enllaç

@microstudi @xabier we've had a few request from our clients about this. The use case case for it is of course open data but also for external analysis also. In the case of the grand débat, where a lot of contributions are to be analyzed, more and more experiments are being implemented using maching learning and NLP to assist the synthesis. Coverage will of course be key here.

But also, we were thinking that creating private access to a more powerful API that would allow intensive request and provide access to more sensitive data to authorize users would be necessary to work on exhaustive synthesis.

Would love to have your feedback.

Pinging @moustachu too, so that he can step in the conversation.

Avatar: Alain Buchotte Alain Buchotte
14/05/2019 10:03
  • Obtenir enllaç Obtenir enllaç

To be more precise :

We do feel that identifying users when requesting the API could provide :
- a complete access to the content visible to the user (even in private space)
- a way to detect, authorize, block intensive usage of the API

Limitations on this matter should only be considered regarding GPDR.

Avatar: Ivan Vergés Ivan Vergés verified-badge
14/05/2019 17:02
  • Obtenir enllaç Obtenir enllaç

This is exactly the types of cases we have in mind as well.

This proposal talks only about extending coverage so, at least, the content that is displayed as html is available in the API too. Plus adding search capabilities. We think to provide authenticated access to private zones would be the second phase. A nice addition in this regard would be to create a user page where to generate private access keys for the API.

Intensive request could be approached maybe in the server side, providing some cache methods probably. If it's just a matter of limit requests, then there are good gems for R&R that can be useful.

We (as @Platoniq) tried to raise fundings to develop the first phase but it has been withdrawn (for the moment). I'll try to update the status of this development the moment I have more information. In the meantime we probably contribute when we need some specific feature for our needs.

Avatar: Kris De Winter Kris De Winter
24/09/2019 14:34
  • Obtenir enllaç Obtenir enllaç

I endorse the above requests. What I miss most at the moment is all content from assemblies. I'd like to be able to query all components that are used in an assembly and access all their content. Right now you can only get the title/description of some components.

Conversa amb Ivan Vergés
Avatar: Ivan Vergés Ivan Vergés verified-badge
10/12/2019 13:53
  • Obtenir enllaç Obtenir enllaç

For those following this proposal. I just want to announce that this is currently work in progress and will be ready for the next Decidim (presumably) version. Coverage will include all available (read-only) public content and some search capabilities.

Avatar: agustibr ☂️ agustibr ☂️ verified-badge
10/12/2019 15:01
  • Obtenir enllaç Obtenir enllaç

👏🎉

Deixa el teu comentari

Inicia la sessió amb el teu compte o registra't per afegir el teu comentari.

Carregant els comentaris ...

  • Termes i condicions d'ús
  • Sobre la comunitat
  • Descarrega els fitxers de dades obertes
  • Metadecidim a Twitter Twitter
  • Metadecidim a Instagram Instagram
  • Metadecidim a YouTube YouTube
  • Metadecidim a GitHub GitHub
Amb llicència Creative Commons Web creada amb programari lliure.
Logo Decidim

Confirmar

D'acord Cancel·lar

Si us plau, inicia sessió

decidim Inicia sessió amb Decidim
O

Registra't

Has oblidat la teva contrasenya?