Is it ok to self-host images / data?

[esDotDev]

We have an app that hard-codes the IDs of some pre-selected MET API objects to use as hidden collectibles.

We're having an issue where sometimes an object may go offline and the ID is no longer valid. It seems the API cycles objects in and out from time to time.

We're wondering if there would be any licensing/copyright issues with us self-hosting these artifacts (images + data) on our own servers, to ensure that our chosen items will always be available for the lifetime of the app.
Thanks!

[stephenhmarsh]

@esDotDev our policy on that is explained here: https://metmuseum.github.io

The Metropolitan Museum of Art provides select datasets of information on more than 470,000 artworks in its Collection for unrestricted commercial and noncommercial use. To the extent possible under law, The Metropolitan Museum of Art has waived all copyright and related or neighboring rights to this dataset using the Creative Commons Zero license. This work is published from the United States of America. These select datasets are now available for use in any media without permission or fee; they also include identifying data for artworks under copyright. The datasets support the search, use, and interaction with the Museum’s collection.

The Met’s Open Access datasets are available through our API. The API (RESTful web service in JSON format) gives access to all of The Met’s Open Access data and to corresponding high resolution images (JPEG format) that are in the public domain.

Please let us know if you are unsure if a particular artwork or its data are OpenAccess/CC0/public domain.

[esDotDev]

Thanks! We had read that section, but were unsure if that allowed us to copy the assets onto a different server.

Regarding public domain, we're assuming we can use the publicDomain=true flag in the data to indicate this?