diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-20 20:55:43 -0700 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-20 20:55:43 -0700 |
| commit | acfb1fadb5ed51ba5fe6c217c9b15def72f9bb02 (patch) | |
| tree | 551c6d60aa047fc70325a9cd315f2f469becfaa1 /rfc.md | |
| parent | 2a1223c721c32b39670809a5eeb361fdc53d2d27 (diff) | |
| download | fatcat-acfb1fadb5ed51ba5fe6c217c9b15def72f9bb02.tar.gz fatcat-acfb1fadb5ed51ba5fe6c217c9b15def72f9bb02.zip | |
docs
Diffstat (limited to 'rfc.md')
| -rw-r--r-- | rfc.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -244,7 +244,7 @@ are: <found at> URLs <held-at> institution <with> accession - creator + contributor name <has> aliases <has> affiliation <for> date span @@ -292,9 +292,9 @@ Should `identifier` and `citation` be their own entities, referencing other entities by UUID instead of by revision? This could save a ton of database space and chunder. -Should creator/author contact information be retained? It could be very useful -for disambiguation, but we don't want to build a huge database for spammers or -"innovative" start-up marketing. +Should contributor/author contact information be retained? It could be very +useful for disambiguation, but we don't want to build a huge database for +spammers or "innovative" start-up marketing. Would general purpose SQL databases like Postgres or MySQL scale well enough told hold several tables with billions of entries? Right from the start there |