Concrete impact for you: I guess when displaying motions, you are currently fetching the linked proposal discussion's description.
Now, you'll need to display instead:
the summary_nl / summary_fr of the linked document () - if that is available. That will make you ready to display that, when we finish summarizing documents) instead of the linked proposal discussion. The summary will be more understandable for simple souls like us civilians to read.
() The linked document is found as the document object in documents.json where document.all_documents_reference == motion.documents_reference.
fallback, when the document summary is not (yet) available, to displaying the linked proposal discussion's description as before. This linked proposal discussion's description just has to be found now slightly differently:
1) Get the linked document, found as the document object in documents.json where document.all_documents_reference == motion.documents_reference. (same as above for summary fetching)
2) Get the proposal_discussion.description from plenaries.json, where proposal_discussion.id == linked_document.proposal_discussion_ids.
Note that similarly, if you would need it, you can also navigate from motion groups to linked proposal descriptions or proposals, or from motions to linked proposals, always via the documents.
Sorry for the long text. Take a cup of coffee/tea and read at ease. I tried to make it clear so you can continue asynchronously. But I'm also OK to discuss Sunday/Monday.
There is a new update of plenaries.json ready, and a new file documents.json.
This makes a lot of improvements on the linking of motions and proposals, but we've changed the data model slightly. We've put a DocumentsReference object now in between motion and proposal objects. For motivation of that, see https://github.com/transparentdemocracy/voting-data/issues/47#issue-2313856525.
Concrete impact for you: I guess when displaying motions, you are currently fetching the linked proposal discussion's description. Now, you'll need to display instead:
the summary_nl / summary_fr of the linked document () - if that is available. That will make you ready to display that, when we finish summarizing documents) instead of the linked proposal discussion. The summary will be more understandable for simple souls like us civilians to read. () The linked document is found as the document object in documents.json where document.all_documents_reference == motion.documents_reference.
fallback, when the document summary is not (yet) available, to displaying the linked proposal discussion's description as before. This linked proposal discussion's description just has to be found now slightly differently: 1) Get the linked document, found as the document object in documents.json where document.all_documents_reference == motion.documents_reference. (same as above for summary fetching) 2) Get the proposal_discussion.description from plenaries.json, where proposal_discussion.id == linked_document.proposal_discussion_ids.
Note that similarly, if you would need it, you can also navigate from motion groups to linked proposal descriptions or proposals, or from motions to linked proposals, always via the documents.
Sorry for the long text. Take a cup of coffee/tea and read at ease. I tried to make it clear so you can continue asynchronously. But I'm also OK to discuss Sunday/Monday.
:wave: