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

API not refreshing deletions/corrections? #69

Open npicardo opened 6 years ago

npicardo commented 6 years ago

An odd problem with Giza TMS media record ("CBE_I-018_record") makes us wonder if the database API refreshes are updating to reflect deletions along with additions. And also that it allows a TMS record to show up online in two versions – an original version and a subsequently corrected version.

Description: TMS media record ("CBE_I-018_record") was created by batch upload over the summer, but later a typo in its Department field (and the corresponding “Departments” Authority table in the Media Module) was corrected in TMS. The original record had Department = "Cairo University?Brown University Expedition" which was corrected to Department = "Cairo University-Brown University Expedition." The website currently shows two records, one for each spelling.

Possibly related? -- TMS only locates this (correct) media record if you type the full rendition number "CBE_I-018record" into the Media module search, but a broader search for all "CBE*" does NOT pull up this record with the all the other CBE media records.

Any idea what might happening? Could all of it come down to how the API handles the TMS "Departments" Authority Table for the Media Module?