LP DB
From LiquidPubWiki
Contents |
TODO
1. See TODO-NICK and TODO-MARIO in the text
2. Add storing homonyms and synonyms - describe as use cases
3. Provide materialized views for ResEval and GroupComparison
4. Contribution date - need to see how to use dates table in case we have only year and-or month
5.
doi - sth to be added to http://dx.doi.org/ for resolution. For example, to resolve the DOI name 10.1000/182, enter the address: "http://dx.doi.org/10.1000/182".
Common tables
informationsources
Contains names and URLs of the websources we use for loading data.
| ID | Name | URL |
|---|---|---|
| 1 | DBLP | http://www.informatik.uni-trier.de/~ley/db/ |
| 2 | Google scholar | http://scholar.google.com/ |
| 3 | Scopus | http://info.scopus.com/ |
| 4 | Springerlink | http://www.springerlink.com/home/main.mpx |
| 5 | ACM | http://portal.acm.org/ |
| 6 | ePrints | http://eprints.biblio.unitn.it/perl/oai2 |
| 7 | ePrints-phd | http://eprints-phd.biblio.unitn.it/cgi/oai2 |
dates
Contains dates splitted into year/month/day for easier sorting, reporting, etc.
People Tables
persons
Contains first, middle, last, and full name of a person, also gender.
gender is M/F/null
provenance_person
Contains timestamp of last load of data of a person from a certain information source. For instance, (1,id_of_JohnSmith,id_of_ePrints-phd,2009-11-11 20:38) says that the data about John Smith was last time loaded on 11/11/2009 at 20:38. It is possible to have such records about the same person form more than one source.
person_contacts
Contains contact information of a person
person_ids
Contains IDs of the person in different datasets. To be used for loading data and disambiguation. This table allows for storing different persons with the same OKKAM ID, e.g. J Smith and John Smith.
dblp_id - ex: homepages/a/ShoshanaAnily - if you add http://dblp.uni-trier.de/rec/bibtex/ before the key, you will get bibtex with the data about the person, like at http://dblp.uni-trier.de/rec/bibtex/homepages/a/ShoshanaAnily.
acm_id - #TODO-NICK
okkam_id - ex: http://www.okkam.org/ens/id1a90fb5c-b40e-4a5f-9491-b5f323db0b7e - a canonical identifier for each entity. OKKAM project will provide possibility to map other identifiers (dblp, acm, etc) to OKKAM ID.
users
display_name - a name under which the user wishes to appear in the LP pages when logged in. Example: mario
username - unique text string identifying the user in the system. It is needed when users authenticate themselves providing standard "username/password" authentication tokens. Example: mpassamani
password - hashed version of user password, which is a secret string known only to the user. Allows authentication procedure to take place. Example: s3cret
provider_id - an unique ID identifying the authentication provider for this user. User must have a valid account on that provider, which will authenticate it on behalf of our system. Example: https://<<any-openidprovider.net>>
user_provider_id - the parameter identifying the user account on the authentication provider system. In most cases, this would be just the login name on that system. Example: https://<<any-openidprovider.net>>/mario
persons_users
links persons and users, each user can correspond to several persons, but each person should (in theory) correspond to only one user
