artshumrc / giza

JSON API (for TMS Database) and Django 2 application for Digital Giza
http://giza.fas.harvard.edu/
7 stars 5 forks source link

Automated data refresh? #52

Open raronin opened 7 years ago

raronin commented 7 years ago

Just wondering if there is a scheduled automated data refresh set-up for the prototype and, if so, how frequent it might be? We've noticed that changes we've making are not being reflected on the website and want to make sure nothing is wrong.

rsinghal commented 7 years ago

There isn't a cron job for that yet. The data was last updated in the afternoon of 4/4. Were the changes made before that date?

jkisala commented 7 years ago

They're showing up on the dev site, but not the production site - is there a way to automatically push the data updates to both sites? It'd be great to get this on a schedule.

rsinghal commented 7 years ago

I updated the dev site to reflect the changes to the image viewing. I never got a response from the team about those changes, so I haven't made the update to production.

raronin commented 7 years ago

Sorry, I don't think I realized that required a response! We'll take a closer look at image viewing and get back to you. We were actually talking about other changes, made back in March; for instance, a new constituent record was made for "Louis Earle Rowe" which shows up in the dev site, but not production (where we've been tending to work). Similarly, the reclassification of "Plans & Drawings" to "Maps & Plans" and "Drawings" is now complete and seems to be reflected on the dev site only.

rsinghal commented 7 years ago

I didn't want to push it to production if it was universally hated. I likely won't change much beyond what you see because many issues will be addressed by using Mirador, but if having the alternative viewer doesn't solve any problems, and only creates new ones, then I would rather revert that change than push it to production.

jkisala commented 7 years ago

Okay, stupid question, and feel free to tell me I don't know anything (because I don't, when it comes to this stuff) - is there a way to update the data that the production site is pulling from, without implementing functionality changes that might still be works in progress? Or is updating an all-or-nothing sort of deal? I totally understand wanting to be conservative about pushing new structural changes (though the new media viewer is looking great - from my first impressions, it should serve just fine until we get Mirador up and running), but it would be useful to be able to feed the most up-to-date information to the website without having to wait for us to remember to respond to our emails about features that are still in development.

rsinghal commented 7 years ago

Generally I can update the data without updating the code. But, there are sometimes code changes that affect how the data is pulled and stored. In those cases, I have to update the code in order to run the data properly. This is one of those cases. I would need to update the data for the images in order for the new code to run properly. So, I want the go ahead so I can pull the latest files and update everything because it is still being done manually and it's time consuming.

jkisala commented 7 years ago

Ah, gotcha. That makes perfect sense. We'll confer on this in the morning and get back to you ASAP - we're definitely in favor of making things less time-consuming!