archivesspace-api-workshop/74-ArchivesSpace-API-Workshop.html at master · rockivist/archivesspace-api-workshop · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
<!DOCTYPE html>
<html>
<head>
   <link href="css/slides.css" rel="stylesheet" />
</head>
<body>
	<nav>
<a id="start-slide" rel="nav" href="00-ArchivesSpace-API-Workshop.html" title="Return to start of presentation">Start</a>
<a id="prev-slide" rel="nav" href="73-ArchivesSpace-API-Workshop.html" title="Previous slide">Prev</a>
<a id="next-slide" rel="nav" href="75-ArchivesSpace-API-Workshop.html" title="Next slide">Next</a>
	</nav>
	<section><h1>6. Accessions</h1>

<h2>The minimal accession record</h2>

<p>Unlike our friend the agent_person, the minimal accession record boils
down to three fields</p>

<ul>
<li>title (actually optional, but you should have one that is human friendly)</li>
<li>identifier (i.e. id_0, id_1, id_2, id_3)</li>
<li>accession_date</li>
</ul>

<p>Everything else is optional. The Accession record can be quite detailed.
I suggest experimenting by filling out an example in the web UI and
viewing the results via a python script using list_accession().</p>
</section>
   <script type="text/javascript" src="js/keyboard-nav.js"></script>
</body>
</html>