Data Modelling and APIs for the Waste Services Standards Project | Paul Mackay | January 2016
•Download as PPTX, PDF•
1 like•607 views
Presentation on data modelling and APIs for the Waste Services Standards Project. Presented by Paul Mackay, Technical Lead for the Waste Service Standards Project. Presented at the Local Waste Service Standards Front End Integration Workshop held on 8 January 2016 in London.
Recommended
More Related Content
Similar to Data Modelling and APIs for the Waste Services Standards Project | Paul Mackay | January 2016
Similar to Data Modelling and APIs for the Waste Services Standards Project | Paul Mackay | January 2016 (20)
More from Department for Communities and Local Government Local Digital Campaign
More from Department for Communities and Local Government Local Digital Campaign (20)
Recently uploaded
Recently uploaded (20)
Data Modelling and APIs for the Waste Services Standards Project | Paul Mackay | January 2016
- 1. Local Digital Programme Local Waste Service Standards Project Frontend Workshop#LocalDigital @LDgovUK
- 2. Data models Taxonomies APIs Data formats
- 3. Existing software systems What others? Smart Cities Concept Model Data models APIs
- 4. Status update • Added generic API elements: • Feature and FeatureType • Added Site derived from Place • Re-implemented as simplest possible adaptation layer • Left out some aspects related to materials, items, contact info
- 5. Outstanding issues • Capturing why collections have moved for unusual reasons • Handling sites that are not basic properties or streets
- 6. API design • REST - Representational State Transfer • architecture of the Web
- 8. API design: data • JSON - JavaScript Object Notation • JSON-LD - JSON for Linked Data • Is XML required?
- 9. Linked Data
- 10. Defining services services: - id: 1 name: Refuse esd_url: http://id.esd.org.uk/service/524 feature_types: - name: Black 240L description: - id: 2 name: Recycling esd_url: http://id.esd.org.uk/service/1130 feature_types: - name: Green 240L description: - id: 3 name: Garden waste esd_url: http://id.esd.org.uk/service/530 feature_types: - name: Brown 240L description: - id: 4 name: Glass collection esd_url: http://id.esd.org.uk/service/1130 feature_types: - name: Black Box 55L description:
- 11. Demo API • Subset of documented API • Authorisation is disabled for now • Connected to Bartec Collective test database for Luton http://waste-demo-api.herokuapp.com
- 14. WasteService
- 18. Different ways to describe services: - Date first - Materials first
- 19. • Can front-end implementations be shared? • What are the implications of different council policies? • How to manage content displayed to users? • What technologies are used? Issues
- 20. Sorry we didn't empty your bins – they were contaminated with food waste, so could not be collected. Contaminated: Food waste CONTAMINATED: FOOD [BROWN] Citizen CSR In-cab
Editor's Notes
- Data models and taxonomies relatively abstract. Need applying to things. APIs exchange objects in format of models. Data files matching a format capture certain fields or taxonomy values.
- For data modelling, referenced several inputs. Concept model - high level view existing schemas, mostly schema.org. Supplier software systems.
- Takes time to work through issues. Sometimes features not available.
- Also matches GDS Service Manual guidelines.
- Place is basic model for a “thing with location”. It may have an Address, which is based on BS7666 definition. Aim for general model that can be widely applied across services. Luton’s data pulled from a test Bartec Collective database. Could be pulled from shared council LLPG system or other API. Could work differently if people logged into an account.
- Issues arising during rounds recorded against property or street. Note this is a mockup. Have data via API. Also photos dependent on the ability to record them.
- What UI elements are needed?
- What’s the preferred way to model your services? Does API cover this? Do front end systems present any issues?
- Mapping events to content on screen.