...
| Code Block |
|---|
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<ns2:intakes-common xmlns:ns2="http://services.collectionspace.org/intake">
<entryNumber>EV2010.2</entryNumber>
<depositor>Alfred L. Kroeber</depositor>
...
</ns2:intakes-common>
|
Read will return the above, plus additional fields (uri and csid) for accessfollowing schema:
| Code Block |
|---|
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <ns2:intakes_common xmlns:ns2="http://collectionspace.org/services/intake" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://collectionspace.org/services/intake http://services.collectionspace.org/intake/intakes_common.xsd"> <entryNumber>EV2010... <uri>/intakes/f0cf4c50-8f8a-4df0-869a</uri> <csid>f0cf4c50-8f8a-4df0-869a</csid>2</entryNumber> <depositor>Alfred L. Kroeber</depositor> ... </ns2:intakes-common> |
| Note |
|---|
The schemas above are severely abbreviated, and are thus illustrative. For a full list of the fields that may potentially be present in payloads when creating, updating, or reading individual Intake records, please see the Intake record schema for release 0.5. |
| Note |
|---|
More complete examples of these schemas will be added here in the near future. |
Intake schema
List (and variants) will return the following schema. This schema includes the additional fields uri and csid to help facilitate access to individual records:
| Code Block |
|---|
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<ns2:intakes-common-list xmlns:ns2="http://collectionspace.org/services/intake">
<intake-list-item>
<entryNumber>EV2010.2</entryNumber>
<depositor>Alfred L. Kroeber</depositor>
<uri>/intakes/b59d0c6f-08f2-4fb5-b5f7</uri>
<csid>b59d0c6f-08f2-4fb5-b5f7</csid>
</intake-list-item>
....
</ns2:intakes-common-list>
|