API Standardising for the GLAM Sector - Workshop
summary
Short workshop that maps concrete issues and tools: points to the Australian design guide at api.gov.au/standards, discusses using Trove API and Wikidata for linking, recommends tooling like OpenRefine and Postman, and endorses the tidy data principles for payloads. Covers real risks (de‑identification failure of transport card data), licensing (prefer CC0 metadata), equity for small institutions, and a whiteboard output plus a proposal to continue work at future conferences.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 1:30Victorian Government API Standard
- 3:00Australian Government API Standard
- 4:00Thought Experiment
- 5:00Whiteboard Questions
- 8:50Disagreement
- 13:00Underpants Gnomes
- 15:00GLAM in Libraries
- 16:40Different kinds of collections
- 19:30The tension between privacy and research
- 22:40Anonymising data
- 31:50Clarification
- 33:10Not baking in everything
- 34:28OpenRefine
- 35:05API
- 35:40Tools
- 36:45Equity
- 38:36Training Documentation
- 39:16Learning Curve
- 39:58Easy to Understand
- 41:43Language
- 43:47Innovative Uses
- 44:44Institutions
- 45:44Internationalisation
- 46:53Assumptions
- 47:15Databasedisambiguation
- 48:11Feedback
- 48:42Postman for Web AP
- 49:07R to contribute
- 49:33Link back
- 50:25Browsing
- 51:25APIs
- 52:12Questions
- 56:06Data Structure
- 56:58Nested Data
- 57:13Third Normal Form
- 58:38Spacetime Field
related talks
50mAPI Government
35mOpenAPI for Documentarians
44mCrafting Great APIs with Domain-Driven Design
32mAPIs at the Crossroads From Integration Glue to Intelligence Infrastructure
01h 05mAPI design - tips from practice
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
06mKeynote: APIs, the Universe, and Everything
26mAPI data sharing legal practices for public sector