collection VS lazy-json

I took the official dataset () from MoMA and visualized the artists who have at least one drawing in the museum's collection and lived in 20 century.

The X axis represents the year of birth, Y — lifespan, size — count of works, color — gender.

() https://github.com/MuseumofModernArt/collection/tree/master

Portico takes published museum collection data and turns it into a virtual gallery/viewing room dynamically. This example is the first few items from the published MOMA collection ((https://github.com/MuseumofModernArt/collection).

The collection includes two datasets - ‘Artist’ and ‘Artwork’ available in both CSV and JSON formats. The data can either be forked or downloaded directly from the GitHub page. However, the dataset has incomplete information and should only be used for research purposes. That is why it’s the perfect candidate as it resembles a real-world scenario where data is often missing.

On GitHub, MoMA publishes and periodically updates a public dataset which contains ~140,000 records, representing all of the works that have been accessioned into MoMA’s collection and cataloged in our database. It includes basic metadata for each work (e.g., title, artist, date made, medium, dimensions, and date of acquisition). This dataset is placed in the public domain using a CC0 License (so we're free to use it in this tutorial) and available in CSV and JSON formats.

Hello everybody, happy to share that Lazy JSON has been released.

Lazy JSON is a framework agnostic package that loads heavy JSON in Laravel lazy collections to limit memory usage and allow a fluent syntax to work with the JSON data.