-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
model for person #15
Comments
These should actually be in the DocSouth database. Find the right glue to push/pull from that, please. |
Have a look at http://docsouth.unc.edu/unc/browse/person.html We want browsing by Personal Names, Place Names, Event, Organization, and Publication at a minimum. |
We also need to get some updated data into the DocSouth database, for example when new death dates became available. Three kinds of names: (1) people with no biography. These are in the XML, encoded as names. (2) people with biographies who are already in the DocSouth database and have information that needs to be updated. (3) People who are not in the database yet and have biographies. |
Updating people in the docsouth database:
The total number of new names to be loaded into the database is 789. That includes people with biographies and people without them. |
Clicking on people in the family tree should take the user to a page like:
/dusenbery/family/name/PERSONNAME
which should query the DB for all encoded documents matching PERSONNAME.
See Word docs in "P:\docsouth\Dusenbery\modules\Family". Links to individual objects should open a viewer like the main journal viewer. Everything has a page image and has been encoded.
The text was updated successfully, but these errors were encountered: