| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| blocks:app-note:collection-feed [2022-06-14 13:19] – typo admin | blocks:app-note:collection-feed [2025-12-09 07:41] (current) – admin |
|---|
| Blocks version 5 introduces support for external collection databases. This can be very useful for places like museums, often using such databases to keep track of descriptions, metadata, images and other content related to their artifacts and exhibits. Here's Hans Ruedisueli of Bureau Jorwert in The Netherlands – an expert in database-driven presentations – talking about how he uses this feature 5 to integrate external collection databases in presentations made with Blocks. | Blocks version 5 introduces support for external collection databases. This can be very useful for places like museums, often using such databases to keep track of descriptions, metadata, images and other content related to their artifacts and exhibits. Here's Hans Ruedisueli of Bureau Jorwert in The Netherlands – an expert in database-driven presentations – talking about how he uses this feature 5 to integrate external collection databases in presentations made with Blocks. |
| |
| {{vimeo>528378235}} | {{vimeo>528378235?full}} |
| |
| This application note provides an example of such a solution, showing a number of collections based on openly available data and images published by the [[https://maas.museum|Museum of Applied Arts & Sciences]] in Sydney, Australia. They provide an [[https://maas.museum/api-documentation/overview/graphql/|open API]] for accessing their collection database from anywhere in the world. More commonly, such a collection database is intended for internal access only, although some are open to the public, like this one. | This application note provides an example of such a solution, showing a number of collections based on openly available data and images published by the [[https://maas.museum|Museum of Applied Arts & Sciences]] in Sydney, Australia. They provide an [[https://maas.museum/api-documentation/overview/graphql/|open API]] for accessing their collection database from anywhere in the world. More commonly, such a collection database is intended for internal access only, although some are open to the public, like this one. |
| Watch this video to see some examples, and a brief overview of how to connect Blocks to an external collection database. | Watch this video to see some examples, and a brief overview of how to connect Blocks to an external collection database. |
| |
| {{vimeo>508779815}} | {{vimeo>508779815?full}} |
| |
| ===== Installation ===== | ===== Installation ===== |
| A feed script has many similarities with a network device driver in Blocks, and requires the same kind of [[blocks:drivers:tools|tools]] and [[blocks:drivers:concepts|skills]]. Thus, you may want to start by learning about how to develop device drivers and user scripts. The following description assumes such familiarity. | A feed script has many similarities with a network device driver in Blocks, and requires the same kind of [[blocks:drivers:tools|tools]] and [[blocks:drivers:concepts|skills]]. Thus, you may want to start by learning about how to develop device drivers and user scripts. The following description assumes such familiarity. |
| |
| To follow along with the descriptions below, open the script/feed/Maas.ts script included in this application note using a suitable code editor – such as Atom – as described in the wiki article linked in the previous paragraph. | To follow along with the descriptions below, open the script/feed/Maas.ts script included in this application note using a suitable [[blocks:drivers:tools|code editor]]. |
| |
| ==== Location and Name of a Feed Script ==== | ==== Location and Name of a Feed Script ==== |