archivesspace-api-workshop/58-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
32
<!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="57-ArchivesSpace-API-Workshop.html" title="Previous slide">Prev</a>
<a id="next-slide" rel="nav" href="59-ArchivesSpace-API-Workshop.html" title="Next slide">Next</a>
	</nav>
	<section><h1>5. Working with Agents</h1>

<h2>create_agent concerns</h2>

<p>If the API docs for models/schema are not available look at the
web UI for agents.  The required fields will in the form will be
the ones we want to handle. Sometimes you may have to experiment
and guess.</p>

<p>The API validates the requests. The response case from the API
will often hint at what we&rsquo;re missing.  <em>curl</em> can be a real help
here as the error response in JSON wil give us clues to what is
missing. Sometimes that is not as visible from the Python shell.</p>

<p>Relying on the API validation does allow us to simplify our client
code but we need to do more in our tests sorting out the right
structure to send.</p>
</section>
   <script type="text/javascript" src="js/keyboard-nav.js"></script>
</body>
</html>