The URI that displays at the bottom is an identifier for the digital object
record and is used internally by the ArchivesSpace API
<http://archivesspace.github.io/archivesspace/api/#archivesspace-rest-api>.
It isn't a location (a URL) so nothing is actually "stored" there. It's
just a way to reference a record and is available as an API endpoint via
various HTTP request methods (GET
<http://archivesspace.github.io/archivesspace/api/#get-a-digital-object>,
POST
<http://archivesspace.github.io/archivesspace/api/#update-a-digital-object>,
DELETE
<http://archivesspace.github.io/archivesspace/api/#delete-a-digital-object>).
/repositories/2/digital_objects is also an API endpoint (GET
<http://archivesspace.github.io/archivesspace/api/#get-a-list-of-digital-objects-for-a-repository>,
POST
<http://archivesspace.github.io/archivesspace/api/#create-a-digital-object>
).

For anyone building services that communicate with the ArchivesSpace API,
having the record URI available in the staff interface is handy. At NC
State we had been providing the URI on the front end via a plugin but it
was integrated into the core code in version 2.5.2.

On Thu, Sep 5, 2019 at 9:54 AM Busch, Ed <[email protected]> wrote:

> When you create a digital object instance, a line appears in the Basic
> Information under Restictions
>
> *Created by admin* 2019-09-05 13:48:44 +0000 | *Last Modified by admin* 
> 2019-09-05
> 13:49:08 +0000 | *URI:* /repositories/2/digital_objects/2
>
>
>
> Where is this /repositories/2/digital_objects space located at? What is
> actually store there?
>
>
>
> *Ed Busch*
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> [email protected]
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to