Project

General

Profile

« Previous | Next » 

Revision 7648

mappings/VegCore.htm: Regenerated from wiki. Forming IDs: Added instructions for making a local ID global. Added note that these globally unique IDs are not the same as UUIDs. Forming preferred IDs: Reworded as a set of instructions rather than a definition. Clarified that this becomes the database primary key.

View differences:

VegCore.htm
6 6
<meta name="description" content="Redmine" />
7 7
<meta name="keywords" content="issue,bug,tracker" />
8 8
<meta content="authenticity_token" name="csrf-param" />
9
<meta content="6XL3ojOwWNQ0htv8dZx9CYnUtPxNsAGvBLvuaivJefo=" name="csrf-token" />
9
<meta content="eNtcHcnpOkN4Wa2v2PxUb/HB+QTLb0hMxjg6JeGzcF4=" name="csrf-token" />
10 10
<link rel='shortcut icon' href='/nceas/favicon.ico?1347421715' />
11 11
<link href="/nceas/stylesheets/jquery/jquery-ui-1.8.21.css?1357775071" media="all" rel="stylesheet" type="text/css" />
12 12
<link href="/nceas/stylesheets/application.css?1357775071" media="all" rel="stylesheet" type="text/css" />
......
375 375

  
376 376

  
377 377
	<ul>
378
	<li>An ID should always be <em>globally</em> unique to allow appending data from arbitrary datasets</li>
379
		<li>An ID must <em>permanently</em> and <em>unambiguously</em> identify the record.<br />Domain identifiers are usually permanent, while autogenerated primary keys often aren't.</li>
378
	<li>An ID should always be <em>globally</em> unique to allow appending data from arbitrary datasets.<br />A local ID can be made global by prepending the institution's ID.</li>
379
		<li>An ID must <em>permanently</em> and <em>unambiguously</em> identify the record
380
	<ul>
381
	<li>Domain identifiers are usually permanent, while autogenerated primary keys often aren't.<br />However, domain identifiers are sometimes duplicated, in which case another ID, such as a primary key, must be used to distinguish them.</li>
380 382
	</ul>
383
	</li>
384
		<li>When multiple IDs are available, include all of them (in separate columns) to allow looking up the record by any of them</li>
385
	</ul>
381 386

  
382 387

  
388
	<p style="padding-left:2em;"><em>Note that these globally unique IDs are not the same as <a href="http://en.wikipedia.org/wiki/Globally_unique_identifier" class="external">UUIDs</a>, which are randomly generated</em></p>
389

  
390

  
383 391
	<a name="Forming-preferred-IDs"></a>
384 392
<h3  style="padding-left:1em;">Forming preferred IDs<a href="#Forming-preferred-IDs" class="wiki-anchor">&para;</a></h3>
385 393

  
386 394

  
387 395
	<ul>
388
	<li>The <em>preferred ID</em> is the ID which is most directly associated with the identified object.<br />Choose from ID values in the following order:
396
	<li>Choose one ID to serve as the <em>preferred ID</em>. This becomes the database primary key.</li>
397
		<li>Choose the ID which is most directly associated with the identified object:
389 398
	<ol>
390 399
	<li>a domain identifier</li>
391 400
		<li>a permanent URL</li>
392 401
		<li>a <em>permanent</em> primary key</li>
393 402
	</ol>
394 403
	</li>
395
		<li><em>Within</em> these categories, it should be the <em>shortest</em> string which is globally unique</li>
404
		<li><em>Within</em> these categories, choose the <em>shortest</em> string which is globally unique</li>
396 405
	</ul>
397 406

  
398 407

  

Also available in: Unified diff