As I have prior experience utilizing APIs, I decided to take on the research of DPAM’s current hosting platform and potential API connections that will allow us to transfer that data to 3DVista. You will find that I listed options for creating our own API, as well as potential CMS alternatives DPAM could use if CatalogIt HUB proved too difficult. However, after contacting CatalogIt’s support team, I was able to receive appropriate API documentation that will work exactly how we need it to (The resources that are no longer relevant to our team have strikethrough applied). The following shows the results of my research:

Art museum API example: Cleveland Museum of Art

• Link to their documentation site: https://openaccess-api.clevelandart.org/
• Sample visualization with this API: https://aaprilfoolss.github.io/cma/

CatalogIt Research

• DPAM is using CatalogIt HUB for CMS (https://www.catalogit.app/)

  • Option for JSON data export; could use this to build our own API connection, but would need to be updated every time the collection is updated

    • Insomnia, Postman are 2 REST API software (https://insomnia.rest/, https://www.postman.com/)

  • Received API documentation from support: https://api.catalogit.app/api/public/accounts/4598 for DPAM collection

    PUBLIC_API.pdf

  • Might make sense to curate collections in the HUB for each personality type, then use an API to pull data from those specific collections (rather than pulling data by tags within the entire collection)

• Potential alternative CMS: GallerySystems
  • API documentation: https://help.gallerysystems.com/emuseum/5.1/configuration/api-documentation
  • eMuseum digital publishing software: https://www.gallerysystems.com/solutions/online-collections/