issues
search
FLOIP
/
flow-results
Open specification for the exchange of "Results" data generated by mobile platforms using the "Flow" paradigm
6
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Represent engagement with "informational messages" in Flow Results
#43
markboots
closed
2 years ago
5
Resolve Issues #37, #40, #41, #43. Bump version to 1.1.0 - minor increase for new backwards-compatible functionality
#42
markboots
closed
2 years ago
1
Optional fields to convey setting a contact property and a contact's group membership
#41
markboots
opened
2 years ago
0
Handling of PII fields
#40
rudigiesler
opened
3 years ago
3
Address Issue #38: Row IDs should be compared as strings for uniqueness
#39
markboots
closed
2 years ago
0
Uniqueness of row IDs within a Flow Results package should clarify: values compared as strings
#38
markboots
closed
2 years ago
0
Semantic coding of questions in Flow Results
#37
markboots
opened
3 years ago
2
Change api-data-url to api_data_url (Consistency with underscore convention in rest of spec; JS properties)
#36
markboots
closed
3 years ago
2
Change api-data-url to api_data_url (Consistency with underscore convention in rest of spec; JS properties)
#35
markboots
closed
3 years ago
0
Flow Results and RapidPro version management
#34
markboots
opened
5 years ago
31
The type for responses endpoint data is 'responses'
#33
ukanga
closed
2 years ago
1
Determine if question IDs can start with a digit
#32
markboots
opened
6 years ago
1
Determine required profile (e.g. "profile":"data-resource")
#31
markboots
opened
6 years ago
4
Determine restrictions on the resource name
#30
markboots
closed
6 years ago
2
Follow REST norms for updating package definitions via the API (Versioning system Option 2)
#29
markboots
opened
6 years ago
7
Add Session IDs
#28
markboots
closed
6 years ago
0
Add session ID column: Readme page
#27
markboots
closed
6 years ago
0
Sync proposals and master
#26
markboots
closed
6 years ago
0
Merge pull request #23 from FLOIP/api-spec
#25
markboots
closed
6 years ago
0
Internet of Things
#24
bengrubb
opened
6 years ago
0
Api spec
#23
markboots
closed
6 years ago
0
Proposals
#22
markboots
closed
6 years ago
0
Show api spec in proposals
#21
markboots
closed
6 years ago
0
Bring latest master into proposals
#20
markboots
closed
6 years ago
0
Add API endpoints specification
#19
markboots
closed
6 years ago
0
How do we specify the order of questions in the schema property?
#18
ukanga
opened
6 years ago
6
Clarify the meaning of `modified` to act as a version control indicator
#17
markboots
closed
6 years ago
0
Pull add-access-method into proposals
#16
markboots
closed
6 years ago
0
Add `access_method` to the Resource, to indicate api or file-mode access. Addresses #14
#15
markboots
closed
6 years ago
0
Clarify if file- or api- style access should be used for resources located at URL endpoints
#14
markboots
closed
6 years ago
3
Clarify the meaning of `modified` to act as a version control indicator
#13
markboots
closed
6 years ago
1
Version control for API access
#12
markboots
closed
6 years ago
3
Merging formatting work from Phase 1 milestones
#11
markboots
closed
6 years ago
0
Bring in formatting changes from master
#10
markboots
closed
6 years ago
0
Read output of spec results into Ona datasets
#9
pld
closed
6 years ago
2
Output results in the spec results format
#8
pld
closed
6 years ago
1
Convert a FLOIP spec into a restricted XForm/XLSForm
#7
pld
closed
6 years ago
1
API request and response format
#6
markboots
closed
6 years ago
6
Provide optional support for a Session ID
#5
markboots
closed
6 years ago
5
Add milliseconds to timestamps
#4
markboots
closed
6 years ago
5
Consider inline embedded media data in the JSON data file
#3
markboots
opened
6 years ago
5
Draft specification based on #1
#2
markboots
closed
6 years ago
5
Discuss and draft a concept specification
#1
markboots
closed
6 years ago
26