Date: Thu, 28 Mar 2024 08:06:17 -0400 (EDT) Message-ID: <214845395.27664.1711627577407@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27663_2114372287.1711627577407" ------=_Part_27663_2114372287.1711627577407 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Much of the functionality that is exposed through the RESTful HTTP API is also ava=
ilable using an HTML user interface interpreted by your favorite web browse=
r. Whether your request for particular HTTP API endpoints results in =
an HTML UI or more machine-readable formats is based on content negotiation=
headers. This tour walks you through the major user interface compon=
ents when accessing the HTTP API through a web browser.
When you access the root path of the RESTful HTTP API you are pres= ented with a rendering of the root level of your Fedora repository.
From here you can:
The user interface is divided into regions.
The navigation bar, which appears at the top of each page, includes link= s to the following:
Information about the resource requested is disp= layed below the navigation bar, filling the left two thirds of interface.= span>
If a title (either http://www.w3.org/2000/01/rdf-schema#label or <=
em>http://purl.org/dc/element=
s/1.1/title) is available, it is displayed here. If=
no title has been assigned, the resource URI is displayed in this location=
.
With respect to how resources are or=
ganized in the repository, Fedora 5 is identical to Fedora 4, maintaining a=
tree hierarchy to the repository. Fedora 5=
, however, is different from Fedora 3, which supported a flat structure. Th=
e path (list of ancestors) for the viewed resource is presented below the o=
bject title. Performance is expected to be better with a deeper hierar=
chy, with fewer items per level, versus a shallow hierarchy, where each lev=
el has a larger number of siblings. The automatic ID (and path) genera=
ted by Fedora is meant to optimize performance, but you may use your own or=
ganizational strategy when creating resources.
In this particular example, the container was created =
with a fully qualified name including a namespace and local name (separated=
by a colon), but Fedora 5 neither requires nor recommends identifiers have=
namespaces.
Very basic metadata such as the creation and modification times and user= s are presented below the resource path.
Any children that the container has will be listed and linked here.
All properties of the resource are presented here. Hove=
r your mouse over the namespace prefix to see the full namespace.
A subset of properties from the parent resource. If th=
ere are any, a gray box will be present. Click on the gray box to exp=
and the list of properties or the label text to view that resource directly=
.
Each page below describes actions that can be performed for the Resource at a given cu= rrent path.
These may include: