openactive-archive developer-microsite issues

openactive-archive / developer-microsite

ARCHIVE: Microsite for the OpenActive Developer engagement, archived from 2018

0 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

caption and copyrightHolder

#43 nickevansuk opened 6 years ago
0
Fixes openactive/data-model-validator#101 - adds a 'how to validate y…

#42 petewalker closed 4 years ago
0
Fixes openactive/data-model-validator#65 - microsite uses data-models

#41 petewalker closed 4 years ago
0
Do not include time component in startDate and endDate for all-day events

#40 nickevansuk opened 6 years ago
4
Lat/lng insufficiently accurate to be useful

#39 nickevansuk opened 6 years ago
1
Use activity values from the activity list

#38 nickevansuk opened 6 years ago
1
Integers should be represented as number

#37 nickevansuk closed 6 years ago
1
The "amenityFeature" property should be inside the "location" object

#36 nickevansuk closed 6 years ago
1
Ensure AggregateRating includes bestRating / worstRating if ratingValue is outside of 1-5 default

#35 nickevansuk opened 6 years ago
0
Expected to see at least one deleted item in the feed

#34 nickevansuk opened 6 years ago
0
genderRestriction should always use one of the enum values, instead of any variation of male, female or mixed

#33 nickevansuk closed 6 years ago
1
Include either both afterId and afterTimestamp parameters in the next URL, or afterChangeNumber

#32 nickevansuk opened 6 years ago
0
afterTimestamp and modified must be integer

#31 nickevansuk opened 6 years ago
0
GeoCoordinates must be specified as decimal values

#30 nickevansuk closed 6 years ago
1
Boolean values should be boolean

#29 nickevansuk closed 6 years ago
1
Include isAccessibleForFree for universally free events

#28 nickevansuk opened 6 years ago
1
For ageRange, at least one of minValue or maxValue must be supplied

#27 nickevansuk opened 6 years ago
1
Do not include endDate or duration for zero duration

#26 nickevansuk opened 6 years ago
0
duration should not contain day component, unless MultidayEvent

#25 nickevansuk opened 6 years ago
1
Update README.md

#24 ldodds closed 6 years ago
0
Event should include "duration" property

#23 nickevansuk closed 6 years ago
2
URL property is mandatory when describing an event

#22 nickevansuk closed 6 years ago
1
Include genderRestriction wherever possible

#21 nickevansuk closed 6 years ago
0
Include level wherever possible

#20 nickevansuk opened 6 years ago
1
Missing details in the PostalAddress may result in the event not being listed in Google Reserve

#19 nickevansuk opened 6 years ago
2
ageRange should contain a QuantifiedValue object

#18 nickevansuk opened 6 years ago
0
For multi-day events, such as holiday camps, use MultidayEvent

#17 nickevansuk closed 6 years ago
1
"offer" property should be named "offers"

#16 nickevansuk opened 6 years ago
0
Price should always be a string with 2 decimal places

#15 nickevansuk opened 6 years ago
1
If providing a programme, always try to include a logo, a url and a video

#14 nickevansuk closed 6 years ago
1
"programme" should be used instead of "superEvent" when the information relates to a programme type

#13 nickevansuk opened 6 years ago
1
Use "programme", in combination with "activity"

#12 nickevansuk closed 6 years ago
1
givenName should not be two words, if no familyName is provided consistently, and vice versa. "name" should be used instead to represent full name.

#11 nickevansuk closed 6 years ago
1
Empty strings and unknown values should be treated as null properties and not included for the items where they are null

#10 nickevansuk closed 6 years ago
1
null properties or objects that contain only null values should not be included

#9 nickevansuk closed 6 years ago
1
"addressCountry" must always be provided

#8 nickevansuk closed 6 years ago
1
"name", "streetAddress", "addressLocality" and "addressRegion" must not have trailing commas

#7 nickevansuk opened 6 years ago
0
"addressRegion" must be a string

#6 nickevansuk closed 6 years ago
1
category should not be a recommended field

#5 nickevansuk closed 6 years ago
0
leader. jobTitle and leader.telephone should both be included in the models

#4 nickevansuk opened 6 years ago
2
"superEvent is not yet represented in the Open Active models. Please check if a suitable field exists."

#3 nickevansuk opened 6 years ago
0
each X should be have a url based id

#2 nickevansuk opened 6 years ago
1
GDPR compliance - do you have explicit consent from the individual

#1 nickevansuk opened 6 years ago
1