Application Programming Interface - Bewerkingsoverzicht

Rrr: /* application developers */

2020-02-26T12:34:56Z

‎application developers

2018-03-08T15:16:46Z

2017-11-03T09:15:15Z

voor de Fryske websites!

2017-10-28T22:46:19Z

2017-10-25T14:01:33Z

‎researchers

2017-10-25T14:01:11Z

‎governments: status change

2017-10-23T14:27:07Z

‎researchers

2017-10-23T14:26:50Z

‎other petitioning website

2017-10-23T14:03:34Z

‎researchers

2017-10-23T14:02:48Z

‎researchers: queries for researchers

@@ Regel 310: / Regel 310: @@
 Third party developers with a need for a certain new query should contact us and bring in the budget to adapt the application programming interface. Examples of potential new queries in the future:
-* a generated petition coming using a template based on big data coming from certain aggregated complaints
+* a generated petition using a template based on big data coming from certain aggregated complaints
 * submitting a url of a webpage with an essay that an certain number of readers recommend to reformulate as a petition, for example a newspaper article or blog posting, immediately inserting the readers as new_signatories
 * a location based augmented reality app showing petitions, current and old, based on GPS-data

← Oudere versie		Versie van 8 mrt 2018 om 15:16
Regel 3:		Regel 3:
	Eventually all data which is not privacy senstive can be read and to some extent written to the database.		Eventually all data which is not privacy senstive can be read and to some extent written to the database.

−	When petitions are presented as the main feature of the application or the petities.nl brand is prominent, there should be no advertising in that same application. Advertisements are not an issue in an application or website which is mainly about something else (the subject of a certain petition for example) with petitions as an added bonus feature.	+	Below a design (in Dutch) with certain roles the API could and should serve. Currently (March 2018) not fully implemented. Contact webmaster@petities.nl if you intend to use the API and would like a key.
−
−	It is no problem to ask money for or in an application which connects to the API. Donations to petities.nl are always much appreciated and especially when users pay or donate because of a petitioning feature.
−
−	Below a design (in Dutch) with certain roles the API could and should serve. Currently not fully implemented. Contact webmaster@petities.nl if you intend to use the API.

@@ Regel 321: / Regel 321: @@
 ==media==
-Similar to the previous category of user, but with the distinction that these website are interested to offer relevant free content repackaged to the end-user. The goals is to sell the content with advertising or to further their activistic goals. For example a local blog (geography) or a animal rights community (thematic).
+Similar to the previous category of user, but with the distinction that these website are interested to offer relevant free content repackaged to the end-user. The goals is to sell the content with advertising or to further their activistic goals. For example a local blog (geography) or a animal rights community (thematic) or the language/dialect of a petition.
 These users will probably be best served with a RSS-feed of petitions with a certain geographic identified (recipient of petition for example) or thematic keyword ([[tag]]). A widget that can easily embed in an existing website will serve even more. This is similar to a feature for the [[Application_Programming_Interface#petitioners]] but with a different appearance. They show all the petitions relevant to a certain query, without a form to sign, but with the name and the number of signatures.

← Oudere versie		Versie van 28 okt 2017 om 22:46
Regel 76:		Regel 76:
	\|}		\|}

		+	The base URI for an API call is to be announced, but the call itself (for API version 1) will start with /api/v1/ followed by the actual POST or GET command. The commands in the table below are referring to the database queries for which the precise API call is not yet known.

	==petitioners==		==petitioners==

@@ Regel 582: / Regel 582: @@
 |-
-|23
+|24
 |API key
 |GET petitions.id, signatures_count, +time since first signature
@@ Regel 588: / Regel 588: @@
 |-
-|24
+|25
 |API key
 |GET petitions, status, +date +tag +recipient +time

@@ Regel 203: / Regel 203: @@
 * show petitions in an app or website specific for some locality/recipient (BASIC FEATURE)
 * embed petitions for the citizenry of a locality on a website
 * link existing formal documents as related to the petition
@@ Regel 290: / Regel 292: @@
 |-
 |19
 |organisation.id in API key
 |POST newsitems.title, newsitems.text, newsitems.petition_id, newsitems.officeid
@@ Regel 295: / Regel 303: @@
 |-
-|20
+|21
 |organisation.id in API key, time>now
 | POST petitions.id, petitions.date_projected

@@ Regel 326: / Regel 326: @@
 Investigative journalists might have more complicated (historical) queries to the database. For them the profile 'researcher' is more fit.
-==European partners==
+==Other petitioning websites==
-Petities die op petities.nl beginnen moeten ook gedeeld kunnen worden met andere petitiesites in Europa. [http://europetition.petities.nl Europetition] zorgt voor de vertaling. Petities op andere sites moeten ook zichtbaar zijn op petities.nl met naam, tekst en het totale aantal ondertekenaars elders. Ondertekeningen hier worden weer doorgegeven aan Europetition (maar niet de ondertekenaars, alleen het aantal).
+In collaboration with other petitioning website in other European member states, petitions can be connected and cross-promoted. Read-only data is exchanged and added to each other's databases, but the number of signatures can be modified. Signatures are not exchanged in order to protect the privacy. Petitions should be manually connected after the site's moderator confirms the petitions are translated copies of one another with the same recipient.
 ==researchers==

@@ Regel 338: / Regel 338: @@
 They do not write to the database.
 {|class=wikitable
@@ Regel 453: / Regel 449: @@
 |-
-|19
+|21
 |API key
 |GET petitions.id, signatures_count, +time since first signature
@@ Regel 459: / Regel 455: @@
 |-
-|20
+|22
 |API key
 |GET petitions, status, +date +tag +recipient +time

@@ Regel 333: / Regel 333: @@
 ==researchers==
-Zijn geïnteresseerd in trends en het verzamelen van data. Privacy van ondertekenaars moet wel beschermd blijven.
+Are interested in quantative and qualitative historical trends and patterns. Unlike journalists they are not interested in the individual petitioners and signatories. The privacy of users should be sufficiently masked.
 # GET met (petition) id + updated_at de laatste bewerking van de petitionaris in de petitie, hoe actief een petitionaris is
 # GET met (petition) id + status geeft voor een bepaalde petitie de status weer, of een petitie al ondertekenbaar is bijvoorbeeld
 * GET met status <concept,live,draft,rejected> geeft de lijst met petities weer voor een bepaalde status
 [[Category:developer]]