Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data needs some more information and more structure #1

Open
tomoakley opened this issue Nov 23, 2016 · 0 comments
Open

Data needs some more information and more structure #1

tomoakley opened this issue Nov 23, 2016 · 0 comments

Comments

@tomoakley
Copy link

tomoakley commented Nov 23, 2016

Hi there

Been looking through your session data to hopefully use on GetActive London through the imin platform; however I've come across some issues which would need resolving before this happens. I've listed these below as well as some questions and comments about the data:

Stuff we need to go live on GetActive:

  • Timestamps - the data needs timestamps. Currently you have the date field, but this has no timestamp, and you have the entry_times field, which is just a String (and is empty on quite a lot of the items). On GetActive/the imin platform, we parse the datetime field of each session then show the date, time and if possible a duration (which we couldn't do with just a String). So ideally, we'd need it to look something like this:
start_date: '2016-10-02T11:00:00';
end_date: '2016-10-02T16:00:00';
  • Cost - couldn't find any mention of the registration cost in the data. On the session webpages you have the various payments for different groups (junior, student, senior, etc) but this doesn't seem to be in the data. It'd be cool if it was something like this:
cost: {
  junior: 1.50,
  student: 2.50,
  adult: 3.50
}

You could also add member pricing in as well, either as a nested structure (e.g adult: { member: 2.50; non_member: 3.50 } or just a different field (adult_member: 2.50; adult_standard: 3.50;).

  • Session URL - simple one hopefully - a URL to the session on the British Orienteering site. We could do this manually (by appending the ID to the session URL) but it would probably be more scalable if you included it. You have the details_website field but in all the items I've looked at this just seems to be null or goes to the same location as website.

And now some stuff which is either questions about orienteering or extra data:

  • Minimum age - what's the minimum age that someone can do the sessions on their own? Maybe 16 or 18? Would be great to have some clarification on this.
  • Further disability support - what other disabilities does Orienteering support? You've already included wheelchairs in your data; would be great to see what others you can support, e.g deafness, learning disabilities.
  • Controllers, Organisers, Mappers - what's the difference between these three fields?

I've found that the data is quite unstructured and often ambiguous in places: it could do with either renaming some fields to make it clear what they're for (e.g website could be club_website), or use some nesting (like above) for related attributes, (club: { name: 'BKO', website: 'bko.org.uk' }) and the postal_entry and online_entry fields.
The contact details are a little confusing; are the email and phone fields for the session leader, or for the club? If a user wanted to find out some more details about the session, who could they contact? If someone was at the venue but couldn't find your group, which number could they call which would put them through to the leader/organiser who could tell them where to go?

Your data for various sessions is highly variable in quality - some have quite a lot of information but others have very little. Is this due to the clubs adding them but not giving enough information? Is there any way it could be improved?

I'd recommend going to look at some of the other OpenActive implementations to see how they've implemented their data; GoodGym and Open Sessions are good examples.
I hope that's all ok, sorry for the rather long list. We're super excited about getting your data on our platform!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant