Politik im Blick

Politik im Blick möchte Transparenz in Gemeindepolitik in Österreich fördern und durch freie Software unterstützen

  • 0 Open
    0 Closed

    Collection of notes when working on mapping the data to OParl.

    Notes

    Meeting

    • participant is just a list of references. It is impossible to determine the role of the participant. I can imagine that a person works as a minute taker for some time and participates in meetings in that role, and a few months later participates in the role of a municipality politician. Reflecting that in the data structure might be useful, maybe by transforming the participant field into a list of objects that can have vendor extensions. Also in Austria, protocols frequently contain a list of people who were absent, either excused or not. This can not be reflected in the structure at all.

    Body

    • ags and rgs demand the usage of a specific number pattern (achtselliger Amtlicher Gemeindeschlüssel, zwöflstelliger Regionalschlüssel). These exist in Germany, but when followed striclty, prohibit the use in other countries such as Austria or Switzerland. I think an object in a field identifiers might be better here, then the bodies can contain the relevant identifiers for the corresponding country.
  • 0 Open
    0 Closed

    We would like to provide useful services to visitors of the website so that they immediately recognize the advantage it provides. Some ideas of what we could provide on the long run:

    • Feeds for documents at
      • Municpality level
      • District level
      • State level
      • Country level
    • ICS files for upcoming sessions
    • Notification whenever the website sees a new document, e.g. by mail (could be based on the feed for simplicity of implementation)
    • Download of archives for all session documents at
      • Municipality level
      • District level
      • State level
      • Country level
    • If we want, we could also provide downloads of archives per year for each of these levels
    • Structured information in machine-readable formats at well-known endpoints
    • Information page about "Gemeinderat" in general, describing what the tasks are etc... (https://www.raaba-grambach.gv.at/index.php/politik/titelgemeinde can serve as inspiration)
  • 0 Open
    0 Closed

    The minimum functionality that should be provided by the website.

    • A clear indication telling the visitor that this is not the official municipality website
    • Imprint
    • About the project
    • Landing page with links to the Austrian states
    • FAQ mentioning at least:
      • Which kind of data we want (namely the original public session protocols as demanded by law, published by the municipality themselves, not a 3rd party; not summary reports, announcements or some other documents, because they don't provide the insights we would like to provide)
      • Links and citations of the laws demanding the creation of the public session protocols, one link for each state
        • Burgenland
        • Kärnten
        • Niederösterreich
        • Oberösterreich
        • Salzburg
        • Steiermark
        • Tirol
        • Vorarlberg
        • Wien
    • One overview page for each state with links to the districts
    • One overview page for each district with links to the municipalities
    • One page for each municipality, with some general information and links to:
      • Municipality website
      • Page where the session protocols are provided (if available)
      • Wikipedia page of the municipality
      • (possibly also Wikidata page?, maybe a little less prominent or hidden somewhere in a collapsible section)
  • 0 Open
    0 Closed

    We would like to introduce badges for highlighting features of session protocols beneficial for transparency.

    Ideas for badges:

    • Organizational stuff
      • Published regularly
      • Published timely (no long waiting period after the session was held)
    • Format
      • File format has text representation included (e.g. PDF with OCR data inside)
      • File format has structured text representation included (e.g. HTML or text document such as odt/docx, allowing to identify paragraphs, sections, headings, listings etc.)
      • File format is intended for machine processing (some structured format, to be defined; Must be easily available before we can properly use this badge)
    • Licensing
      • Published protocols have a license on them
      • Published protocols are under an appropriate license, so that further use is possible without risking legal violations
    • Abilities to follow
      • Livestream of the session (audio/video)
      • Recordings of the session (audio/video)
      • Higher ranks of the badge for:
        • Hosting/streaming on a platform that is available without registration (e.g. not Facebook)
        • Hosting/streaming on a platform (or the municipality page) where no ads are shown (e.g. neither Facebook nor Youtube)
        • Hosting recordings on a platform (or the municipality page) that allows direct file download of the recordings
    • Archiving
      • Keeps protocols online for a very long time (e.g. bronze: 5 years, silver 10 years, gold 15 or 20 years could make sense here)
    • Structured presentation of different session aspects:
      • Participants
      • Agenda items
      • Attached documents
      • ...