Skip to content

EPIC: Participatory Texts #3583

@carolromero

Description

@carolromero

This is an EPIC

Summary

EPIC description

This module enables discussion of large texts by importing structured and unstructured documents, breaking them down into Decidim cards (as happens with proposals or results) and also allows the opposite, the generation of a unified text based on a set of cards (proposals or results). Users can then browse the contents and interact with them (support, comment, share).

User story

Participant: I want to be able to interact with a collection of proposal ordered and organized as unified text document, where I can follow a linear composition, like a new law or a plan. I want to interact with the "units" that compose this text as I do with proposals: I want to be able to amend a paragraph, to comment, support, endorse, share, etc. I want to be able to export the full text to print and read it carefully.

Admin: I want to be able to create a collection of proposals out of a structured text document, e.g. a law or regulation in word or a plan in html (with the appropriate headers and sections), so I can save time creating them manually one by one. I want to be able to edit the result if it doesn't match with a correct split of proposals. I also want to be able to activate a view of a set of proposals that displays them as unified linear text so participants can interact with the set of proposals as a continuous text, and export it as such to be read.

Main related issues

General Specs

Breakdown of texts

Uploading a text in ODT, XDOC, MarkDown or HTML format via the admin panel and dividing it into proposals or results.

  • If the text is structured, a card will be created for each subsection of the text, with the title of the card being used as the title of the corresponding section or subsection.
  • If the text is unstructured, a card will be created from each paragraph. Each paragraph will be titled with its numbering.

After uploading the text via the admin panel, the following parameters (prior to breaking down the text) can be defined.

  • For structured texts: Levels of headers to be used in creating the card.
  • For unstructured texts: Minimum number of characters for a paragraph to be considered part of a card.

The cards may optionally be created, separated or merged manually.

For reference, see: https://www.discuto.io/en/consultation/16258

Composition of documents from cards

It must be possible to number the cards (weights) via the admin panel, in order to sort them.
After sorting, a unified view of all the titles and contents of the cards will be generated.
It must be possible to use categories and subcategories as section and subsection titles respectively.

Display and interaction with recomposed documents

The left margin of the text will include a drop-down index.
In the right margin, every piece of text that corresponds to a card will show the number of supports received and the support button, the number of comments and a comment button (with the option of having access to the complete child), a follow button, a share button and a direct link to the card. The buttons will be actionable and will directly execute the corresponding actions.
When the comment icon is clicked, the comments linked to this card will appear in the right-hand margin, just as in this case: https://mymadison.io/documents/constitution

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions