-
·
Call for Translations: i18n in Openverse
The OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org. codebase is now prepared to handle translations! The #polyglots community has already done tremendous work to provide translations for Openverse in over 18 different languages, and we are excited to make this search engine for openly-licensed…
-
·
A Week in Openverse: August 30-September 3rd
#openverse, #week-in-openverse Login to Reply
-
·
A Week In Openverse: August 23-27th
#openverse, #week-in-openverse Login to Reply
-
·
A Week In Openverse: August 16-20th
#openverse, #week-in-openverse Login to Reply
-
·
A Week in Openverse: August 9th-13th
Welcome to the first of many A Week in OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org. posts. In this weekly series, we’ll highlight work completed through the week by Openverse contributors. This will always include a changelog of closed issues per-repository, and may occasionally…
-
·
Provider API – Wikimedia Commons
We call the following endpoints from Wikimedia Commons: https://commons.wikimedia.org/w/api.php?action=query&generator=allimages&prop=imageinfo&gailimit=40&gaisort=timestamp&gaistart=YYYY-MM-DDT00:00:00Z&gaiend=YYYY-MM-DDT00:00:00Z&iiprop=url|user|dimensions|extmetadata&iiurlwidth=300&format=json https://commons.wikimedia.org/w/api.php?action=query&generator=allimages&prop=imageinfo&gailimit=40&gaisort=timestamp&gaistart=YYYY-MM-DDT00:00:00Z&gaiend=YYYY-MM-DDT00:00:00Z&iiprop=url|user|dimensions|extmetadata&iiurlwidth=300&format=json&gaicontinue=SOME_PICTURE.jpg For both of these, we replace YYYY-MM-DD with dates (we only pull data for images uploaded/updated between these dates). We use the second query if there are more than 40 images between the specified dates, giving a continue location as the next picture (represented by SOME_PICTURE.jpg). These requests each…
-
·
Provider API – Thingiverse
The Thingiverse API is queried in a number of different ways. First, to get a list of ‘things’ to retrieve, and then in a series of steps for each ‘thing’ in the list. Initial API Query The initial query sends a GET of the form https://api.thingiverse.com/newest?access_token=REDACTED&per_page=30&page=1 This returns the following JSON: [ { “id”: 4002927,…
-
·
Provider API – RawPixel
We call the following endpoint from rawpixel.com: https://api.rawpixel.com/api/v1/search?freecc0=1&html=0&page=X Here X is a page offset. Such a request returns a JSON of the following form: { “html”: “”, “spellcheck”: [], “total”: 20586, “uid”: 0, “context”: { “context”: “”, “masterContext”: “” }, “results”: [ { “sort”: “[739,154,1,1571387376]”, “nid”: 1232608, “id”: 1232608, “view_mode”: “photo_grid”, “attributes”: “”, “keywords_raw”: “antique, art, arts, artwork,…
-
·
Provider API – Phylopic
We call the Phylopic API in two different ways: http://phylopic.org/api/a/image/list/modified/YYYY-MM-DD http://phylopic.org/api/a/image/ITEM_UUID?options=credit+licenseURL+pngFiles+submitted+submitter+taxa+canonicalName+string+firstName+lastName We extract a list of UUIDs from the response to the first request, which we then use to construct subsequent requests (of the form shown second above filling in an extracted UUID for ITEM_UUID). The response to a UUID-specified request is a JSON with the…
-
·
Provider API – Met Museum
We call the objects endpoint from the Met Museum’s API in two ways: https://collectionapi.metmuseum.org/public/collection/v1/objects/?metadataDate=YYYY-MM-DD https://collectionapi.metmuseum.org/public/collection/v1/objects/XXXXX The only information we use from the first type of call is a list of object IDs, which we use in the second call in place of XXXXX. The second type of call returns a JSON of the following form: { “objectID”: 786829,…