wilsonmcdade / tunnelvision

Source code for Tunnelvision: RIT's Overlooked Art Museum

Tunnelvision - An interactive catalog of RIT's Murals

Running Locally

(Reach out to a maintainer of this repo for credentials for the dev database)

• Fork the repo and run the following commands in that directory:
• python3 -m venv venv
• source venv/bin/activate
• pip3 install -r requirements.txt
• python3 app.py

tunnelvision's Issues

Allow non-CSHers to develop without ties to CSH

This is similar to my issue on the ScheduleMaker repo ComputerScienceHouse/schedulemaker#320

I notice the README includes this:

(Reach out to a maintainer of this repo for credentials for the dev database)

However I think it might be better to include instructions in the repo to allow people to set up a dev database without needing permission from CSH or a CSHer, such as by either:

• Including instructions to initialize a blank database for devs to populate their own sample data
  • ideally: also include a script to load some sample data
• Include a download link or instructions for where to acquire a database dump of the dev database

With all that said, realistically I'm not planning to contribute, so this is just a low priority issue to hopefully help make this project more friendly to the (growing) FOSS community at RIT who i imagine might like to contribute to this project once it hits a production state.

Have logging outputs in a JSON format for parsing by Datadog

CSH has a datadog instance linked to our OKD cluster, where Tunnelvision is running. Right now we have an issue that the default logs that are created by the webapp are in a weird format that datadog cannot parse. That means that looking at the logs can be quite a hassle.

It would also be cool to see some metrics being piped into datadog, I'm not sure how that would work though.

Add an export feature so users and researchers can more easily use our dataset

I think having some sort of export feature would be good for researchers or people interested in learning more about our dataset. This feature would:

• Compile all relevant tables with no PII (leave the feedback table out of the export)
• Simplify some of the data structures, convert to a CSV or similar simple filetype
• Compile the lower resolution photos of murals
• Provide a downloadable ZIP file including CSVs of tables and image references.