Issue 51 in gref-mvz: Not refreshing corrected data

[codesite...@google.com]

Issue 51: Not refreshing corrected data
http://code.google.com/p/gref-mvz/issues/detail?id=51

New issue report by carlacic:
What steps will reproduce the problem?

1. Find a mistake in Arctos and fix it (e.g., change collector number)
2. Link back to GReF page from Arctos

What is the expected output? What do you see instead?

You should see the corrected data. For example, we just changed collector
number for MVZ Mamm 12787 from 1339 to 1353 (Louise Kellogg). Refreshed all
pages, emptied cache and cookies, etc. The GReF reference still shows 1339
as the collector number, although when you link back to the db, it
shows 1353.

Issue attributes:
Status: Accepted
Owner: carlacic
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 51: Not refreshing corrected data
http://code.google.com/p/gref-mvz/issues/detail?id=51

Comment #1 by carlacic:
Changed to high priority.

Issue attribute updates:
Labels: -Priority-Medium Priority-High

[codesite...@google.com]

Issue 51: Not refreshing corrected data
http://code.google.com/p/gref-mvz/issues/detail?id=51

Comment #2 by eightysteele:
gref stores reference data in gref-specific tables. this results in out
of sync
issues when things change in the production database.reference data
should store fk
or pk instead of values.